GNU bug report logs - #70021
6f9d844 causes system hang right before GDM supposed to start

Previous Next

Package: guix;

Reported by: aurtzy <aurtzy <at> gmail.com>

Date: Tue, 26 Mar 2024 22:39:02 UTC

Severity: normal

Done: aurtzy <aurtzy <at> gmail.com>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#70021; Package guix. (Tue, 26 Mar 2024 22:39:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to aurtzy <aurtzy <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 26 Mar 2024 22:39:02 GMT) Full text and rfc822 format available.

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

From: aurtzy <aurtzy <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: 6f9d844 causes system hang right before GDM supposed to start
Date: Tue, 26 Mar 2024 18:38:33 -0400
Hi!

I recently encountered an issue with my system hanging during the 
startup process, where it halts just before GDM is supposed to start.

Bisect has led to commit 6f9d844 (related issue: 
https://issues.guix.gnu.org/67649 ) being the culprit.

Context/workaround:

This appears to be an issue with code relating to mapped drives. Further 
inspection reveals my `device-mapping-cryptstorage` service fails to 
start, which is supposed to map my secondary encrypted drive. I 
currently work around this by commenting out the `file-system` entry 
that depends on this mapping before mounting it.

I managed to find the following line in /var/log/messages, which - if I 
understand the change correctly - points to `bytevector?` being now 
unavailable, causing the device mapping service to fail (and take the 
system with it?):

Mar 26 17:50:27 localhost vmunix: [   24.680761] shepherd[1]: Exception 
caught while starting device-mapping-cryptstorage: (unbound-variable #f 
"Unbound variable: ~S" (bytevector?) #f)

Best,

aurtzy





Reply sent to aurtzy <aurtzy <at> gmail.com>:
You have taken responsibility. (Mon, 01 Apr 2024 08:32:02 GMT) Full text and rfc822 format available.

Notification sent to aurtzy <aurtzy <at> gmail.com>:
bug acknowledged by developer. (Mon, 01 Apr 2024 08:32:02 GMT) Full text and rfc822 format available.

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

From: aurtzy <aurtzy <at> gmail.com>
To: 70021-done <at> debbugs.gnu.org
Subject: Closing: Duplicate report
Date: Mon, 1 Apr 2024 04:31:44 -0400
Another report which looks to be the same issue was also submitted here: 
https://issues.guix.gnu.org/70051

That one is more active, so I'll close this one and move my discussion 
there.





bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 29 Apr 2024 11:24:07 GMT) Full text and rfc822 format available.

This bug report was last modified 5 days ago.

Previous Next


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