Red Hat Bugzilla – Bug 854904
Quitting Anaconda in LiveCD reboots machine
Last modified: 2015-11-01 20:36:39 EST
Description of problem:
Quitting Anaconda when running liveinst from LiveCD displays a dialog that states "Are you sure you wish to quit the installation process?". Clicking "Quit" does not quit the installation process (Anaconda) but reboots the machine.
The dialog should either state that quitting Anaconda will reboot the machine or Anaconda should just quit without rebooting.
The same situation occurs when Anaconda crashes and you quit the bug-reporting dialog. This prevents users from effectively searching for possible solution for the crash from the liveCD session.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start liveinst
2. Click QUIT
3. Confirm dialog that "Installation process will quit"
Only Anaconda quits
Fedora 18 Alpha TC6
Ah, this was a workaround for gnome not providing an easily discoverable quit/reboot button, but there appears to be one now. I guess this can go.
*** Bug 855645 has been marked as a duplicate of this bug. ***
There are two different cases:
1. If user quits anaconda (because he started it by mistake, or it reported an error, etc), it should not restart the whole computer.
2. If anaconda completes installation, the last button should be called Reboot, and it should reboot the whole computer. (But if user closes anaconda using close button, it should not reboot, because he probably wants to work further even though the installation is complete.)
That should be very easy to implement - always close, just in case of Reboot button do reboot.
*** Bug 857380 has been marked as a duplicate of this bug. ***
*** Bug 859423 has been marked as a duplicate of this bug. ***
Quit button now doesn't reboot Live system, which is great. But the Reboot button now doesn't reboot either!
Guys, let's Quit button quit, and Reboot button reboot, sounds good? :)
In what version of anaconda, in what product?
Dan says "Fedora 18 Alpha TC6" in the description. My comment 6 talks about F18 Beta TC2, which is anaconda 18.12.
I can confirm that with Fedora 18 Beta TC2 the "Quit" button in Anaconda installer only quits and does not reboot (on both Desktop and KDE Spin).
However, when a crash occurs, the "Quit" button in the "An error occurred" dialog still causes the live system to reboot. This is reproducible only on KDE spin, on Desktop the button works as expected.
I can't confirm whether "Reboot" button works or not, because I'm unable to start/complete installation on both Desktop and KDE spin.
I can confirm that with Fedora 18 Beta TC6 the "Quit" button in Anaconda installer only quits and does not reboot (tested KDE Spin only).
And when a crash occurs, the "Quit" button in the error dialogue did *not* cause the live system to reboot.
As per the "Reboot" button, I still didn't ever try to go as far as installing, so I won't tell either :)
Note that 18.31 is a post-Beta build: don't expect this fixed in Beta. It should be fixed in post-Beta nightlies and Final TC1 onwards.
*** Bug 880683 has been marked as a duplicate of this bug. ***
*** Bug 882964 has been marked as a duplicate of this bug. ***
I got this (reboot button does nothing) in Fedora 18 Beta x86-64 Live.
Apart from that, Anaconda works pretty good .. don't know what
everyone was complaining 'bout :-)
Discussed at 2012-12-12 NTH review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-12/f18final-blocker-review-4.2012-12-12-17.01.log.txt . Accepted as NTH, it's a very annoying issue for live installs that cannot be fixed with an update.
In Final TC1, I see only a 'Quit' button at the end of live anaconda, and it quits, it doesn't reboot. Is anything still broken here? kparal seems to think so, but I can't see anything.
setting ON_QA as this was allegedly fixed in 18.31, which is long before the build in TC1 (18.36 has gone stable, so if no-one can point out broken behaviour in TC1, we can close this.)
Reboot has been renamed to Quit in TC1. Quit quits. Fixed in a different way than supposed, but still fixed.
*** Bug 889742 has been marked as a duplicate of this bug. ***
*** Bug 889741 has been marked as a duplicate of this bug. ***