Guix 1.2.0 installer 'auto-partition!' crash

  • Done
  • quality assurance status badge
Details
5 participants
  • Josselin Poiret
  • Gavaskar Kanagaraj
  • Ludovic Courtès
  • Mathieu Othacehe
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Gavaskar Kanagaraj
Severity
important
G
G
Gavaskar Kanagaraj wrote on 27 Nov 2020 11:57
quix installation bugs
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)(name . Umut Durak)(address . umut.durak@tu-clausthal.de)
fa9cdcf3179a460fb38467a56cd7758b@tu-clausthal.de
hello,


I found bugs,


Installation options using iso: Does not boot using dual boot or standalone boot. stucks with automatic reboot. I tried in 3 different computers using 2 different pendrives.


installation options using vmware:

The installer has encountered an unexpected problem. The backtrace is displayed
below.

In ./gnu/installer/newt/partition.scm
766:33 19 (run-partitioning-page

In ./gnu/installer/parted.scm
894:17 18 (auto-partition! #f #:scheme _)

In parted/structs.scm:
639:23 17 (disk-device #f)

In ice-9/boot-9.scm:

1669:16 16 (raise-exception _ #:continuable?

1667:16 15 (raise-exception continuable?

1667:16 14 (raise-exception _ #:continuable?

1667:16 13 (raise-exception _ #:continuable?

1667:16 12 (raise-exception continuable?

1667:16 11 (raise-exception continuable?

1667:16 10 (raise-exception _ #:continuable?

1667:16 9 (raise-exception _ #:continuable?

1667:16 8 (raise-exception _ #:continuable?

1667:16 7 (raise-exception _ #:continuable? _

1764:13 6 (_ #<&compound-exception components: (#<&assertion-failure> #<6origin
origin: "struct-vtable"> #<&message message: "Wrong type argument in position 1
(expecting struct): ~S"> #<@irrit.>
In ice-9/eval.scm:

619:8 5 (_ #(#(#<directory (guile-user) 7fce091d9f00> #<<installer> name
newt init: #<procedure init ()> exit: #<procedure exit ()> exit-error: #<procedure
exit-error (file key args)> f..>) .))

619:8 4 (_ #(#(#(#<directory (guile-user) 7fce091d9f00> #<<installer> name
newt init: #<procedure init ()> exit: #<procedure exit ()> exit-error: #<procedure
exit-error (file key arg..>) ..) #))

In ice-9/ports.scm:

[cid:5bb3afc3-1a99-4cf8-a4a4-4e1f7c324061]
[cid:1404e5ea-4a8f-426a-8dde-e061f3d6211c]



installation using binary, only binary installation over Linux works, but guix pull does work and also could not able to re configure and not able to proceed further for writing scripts.

thanks,


regards,
Gavaskar kanagaraj
Attachment: file
Attachment: bug_guix.png (.12 MiB)
Attachment: buig_guix1.png (.13 MiB)
M
M
Mathieu Othacehe wrote on 27 Nov 2020 21:02
control message for bug #44903
(address . control@debbugs.gnu.org)
87pn3yr2j8.fsf@cervin.i-did-not-set--mail-host-address--so-tickle-me
severity 44903 important
quit
L
L
Ludovic Courtès wrote on 3 Dec 2020 18:01
(address . control@debbugs.gnu.org)
87h7p2ddrv.fsf@gnu.org
retitle 44903 Guix 1.2.0 installer 'auto-partition!' crash
quit
M
M
Maxim Cournoyer wrote on 8 Oct 2022 04:53
Re: bug#44903: Guix 1.2.0 installer 'auto-partition!' crash
(name . Mathieu Othacehe)(address . othacehe@gnu.org)
8735bz3u18.fsf@gmail.com
Hello,

Gavaskar Kanagaraj <gavaskar.kanagaraj@tu-clausthal.de> writes:

[...]

Toggle quote (18 lines)
> 1764:13 6 (_ #<&compound-exception components: (#<&assertion-failure> #<6origin
> origin: "struct-vtable"> #<&message message: "Wrong type argument in position 1
> (expecting struct): ~S"> #<@irrit.>
> In ice-9/eval.scm:
>
> 619:8 5 (_ #(#(#<directory (guile-user) 7fce091d9f00> #<<installer> name
> newt init: #<procedure init ()> exit: #<procedure exit ()> exit-error: #<procedure
> exit-error (file key args)> f..>) .))
>
> 619:8 4 (_ #(#(#(#<directory (guile-user) 7fce091d9f00> #<<installer> name
> newt init: #<procedure init ()> exit: #<procedure exit ()> exit-error: #<procedure
> exit-error (file key arg..>) ..) #))
>
> In ice-9/ports.scm:
>
> [cid:5bb3afc3-1a99-4cf8-a4a4-4e1f7c324061]
> [cid:1404e5ea-4a8f-426a-8dde-e061f3d6211c]

Mathieu, do you think this bug can still exist in 1.3.0 or our current
snapshot installer images? If not, we should close it, as it's gone
stale and reported against 1.2.0.

--
Thanks,
Maxim
J
J
Josselin Poiret wrote on 8 Oct 2022 19:59
87zge642oi.fsf@jpoiret.xyz
Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

Toggle quote (4 lines)
> Mathieu, do you think this bug can still exist in 1.3.0 or our current
> snapshot installer images? If not, we should close it, as it's gone
> stale and reported against 1.2.0.

Just my 2 cents: I think this issue was fixed with
0a74509a696671580c8a7dc768d26f414748bab5. Sometimes, devices are so
small you can't even create a new partition table on them, and we used
to not detect this failure and instead return #f for the disk. That or
ped_disk_new fails for some reason but I wouldn't know why without more
info.

Best,
--
Josselin Poiret
M
M
Maxim Cournoyer wrote on 10 Oct 2022 05:09
(name . Josselin Poiret)(address . dev@jpoiret.xyz)
87r0zg2x3a.fsf@gmail.com
Hi,

Josselin Poiret <dev@jpoiret.xyz> writes:

Toggle quote (15 lines)
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Mathieu, do you think this bug can still exist in 1.3.0 or our current
>> snapshot installer images? If not, we should close it, as it's gone
>> stale and reported against 1.2.0.
>
> Just my 2 cents: I think this issue was fixed with
> 0a74509a696671580c8a7dc768d26f414748bab5. Sometimes, devices are so
> small you can't even create a new partition table on them, and we used
> to not detect this failure and instead return #f for the disk. That or
> ped_disk_new fails for some reason but I wouldn't know why without more
> info.

Thanks for the heads-up. I'm tentatively closing the bug.

--
Thanks,
Maxim
Closed
?