GNU bug report logs - #44903
Guix 1.2.0 installer 'auto-partition!' crash

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44903 in the body.
You can then email your comments to 44903 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gavaskar Kanagaraj <gavaskar.kanagaraj <at> tu-clausthal.de>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Cc: Umut Durak <umut.durak <at> tu-clausthal.de>
Subject: quix installation bugs
Date: Fri, 27 Nov 2020 10:57:42 +0000

[Message part 1 (text/plain, inline)]

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

[Message part 2 (text/html, inline)]

[bug_guix.png (image/png, inline)]

[buig_guix1.png (image/png, inline)]

Message #12 received at 44903 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Mathieu Othacehe <othacehe <at> gnu.org>
Cc: Gavaskar Kanagaraj <gavaskar.kanagaraj <at> tu-clausthal.de>,
 Umut Durak <umut.durak <at> tu-clausthal.de>, 44903 <at> debbugs.gnu.org
Subject: Re: bug#44903: Guix 1.2.0 installer 'auto-partition!' crash
Date: Fri, 07 Oct 2022 22:53:39 -0400

Hello,

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

[...]

> 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

Message #15 received at 44903 <at> debbugs.gnu.org (full text, mbox):

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>, Mathieu Othacehe
 <othacehe <at> gnu.org>
Cc: Gavaskar Kanagaraj <gavaskar.kanagaraj <at> tu-clausthal.de>,
 Umut Durak <umut.durak <at> tu-clausthal.de>, 44903 <at> debbugs.gnu.org
Subject: Re: bug#44903: Guix 1.2.0 installer 'auto-partition!' crash
Date: Sat, 08 Oct 2022 19:59:09 +0200

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer <at> 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.

Best,
-- 
Josselin Poiret

Message #20 received at 44903-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: Gavaskar Kanagaraj <gavaskar.kanagaraj <at> tu-clausthal.de>,
 Mathieu Othacehe <othacehe <at> gnu.org>, Umut Durak <umut.durak <at> tu-clausthal.de>,
 44903-done <at> debbugs.gnu.org
Subject: Re: bug#44903: Guix 1.2.0 installer 'auto-partition!' crash
Date: Sun, 09 Oct 2022 23:09:45 -0400

Hi,

Josselin Poiret <dev <at> jpoiret.xyz> writes:

> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.