emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#56581: closed (1.3.0 F1 reboot bug)


From: GNU bug Tracking System
Subject: bug#56581: closed (1.3.0 F1 reboot bug)
Date: Fri, 15 Jul 2022 21:38:02 +0000

Your message dated Fri, 15 Jul 2022 23:22:17 +0200
with message-id <87y1wuf46d@nckx>
and subject line Re: bug#56581: 1.3.0 F1 reboot bug
has caused the debbugs.gnu.org bug report #56581,
regarding 1.3.0 F1 reboot bug
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
56581: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56581
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 1.3.0 F1 reboot bug Date: Fri, 15 Jul 2022 16:01:11 -0400
Hi,

On the 1.3.0 image, F1 to reboot just locks up the computer with a black screen. Necessary to hold down power button to force-power-off computer to restart it.

Using the GUIX snapshot image does not have this issue, reboot works normally with the later image.

Best,
Peter

--- End Message ---
--- Begin Message --- Subject: Re: bug#56581: 1.3.0 F1 reboot bug Date: Fri, 15 Jul 2022 23:22:17 +0200
Hi again!

Peter 写道:
On the 1.3.0 image, F1 to reboot just locks up the computer with a black screen. Necessary to hold down power button to force-power-off computer
to restart it.

Ouch.  Thanks for taking the time to report this bug.

Using the GUIX snapshot image does not have this issue, reboot works normally with the later image.


Unfortunately, the 1.3.0 image is just as much of a ‘snapshot’, although it was tested and presumably rebooted some (most?) hardware at the time.

It does not receive backported fixes or updates. That would require volunteer effort we currently lack. The good news is that the next (1.4.0) installer will equally be a tested snapshot of master, and hence should contain whatever fix makes the ‘latest’ ISO reboot properly for you.

Since there's nothing actionable to ‘fix’ within our current release workflow, I'm closing this bug, although does illustrate one weakness in said workflow.

Kind regards,

T G-R

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]