[Cooker] [Bug 4377] [mdkkdm] after clicking reboot mdkkdm shows empty list of lilo entries
http://qa.mandrakesoft.com/show_bug.cgi?id=4377 --- Additional Comments From [EMAIL PROTECTED] 2003-23-09 07:34 --- this problem seems to be fixed in version 9.2-9mdk. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I can reproduce this with 100% on a laptop, where I'm using mdkkdm and LILO: 1) Boot Linux 2) Wait for dm to start 3) Click 'Reboot' And empty list of lilo entries shows up, so I cannot reboot. When I login from text console as root and restart dm: # /etc/init.d/dm restart , then the list is there when I click 'Reboot'. It seems that this is some sort of race condition - mdkkdm receives an empty listing from lilo because it starts too early in the process of booting services. When I change the chkconfig line in the startup script in /etc/init.d/dm from this: # chkconfig: 5 30 09 to this: # chkconfig: 5 98 09 , then mdkkdm starts later after most services and after rebooting the list of LILO entries is OK. So the workaround is to delay the startup of dm service. However, there should be some failover code in mdkkdm to allow the user not select any entry nad still reboot the machine. My suggestion: change the mdkkdm code so that when: 1) the user is on the list of bootmanager entries (after clicking 'Reboot'), 2) no entry is selected, 3) he clicks on the 'Ok' button then the ordinary, parameterless reboot is executed (as with CTRL-ALT-DELETE, "shutdown -r", "reboot" or "init 6"). Currently clicking on 'Ok' causes no action when there's no bootmanager entry selected, and if the list of entries is empty, reboot is impossible.
[Cooker] [Bug 4377] [mdkkdm] after clicking reboot mdkkdm shows empty list of lilo entries
http://qa.mandrakesoft.com/show_bug.cgi?id=4377 [EMAIL PROTECTED] changed: What|Removed |Added Version|9.2-2mdk|9.2-1mdk --- Additional Comments From [EMAIL PROTECTED] 2003-01-09 19:23 --- I still do see the problem with the version 9.2-1mdk, shipped with Mandrake 9.2 RC1. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I can reproduce this with 100% on a laptop, where I'm using mdkkdm and LILO: 1) Boot Linux 2) Wait for dm to start 3) Click 'Reboot' And empty list of lilo entries shows up, so I cannot reboot. When I login from text console as root and restart dm: # /etc/init.d/dm restart , then the list is there when I click 'Reboot'. It seems that this is some sort of race condition - mdkkdm receives an empty listing from lilo because it starts too early in the process of booting services. When I change the chkconfig line in the startup script in /etc/init.d/dm from this: # chkconfig: 5 30 09 to this: # chkconfig: 5 98 09 , then mdkkdm starts later after most services and after rebooting the list of LILO entries is OK. So the workaround is to delay the startup of dm service. However, there should be some failover code in mdkkdm to allow the user not select any entry nad still reboot the machine. My suggestion: change the mdkkdm code so that when: 1) the user is on the list of bootmanager entries (after clicking 'Reboot'), 2) no entry is selected, 3) he clicks on the 'Ok' button then the ordinary, parameterless reboot is executed (as with CTRL-ALT-DELETE, "shutdown -r", "reboot" or "init 6"). Currently clicking on 'Ok' causes no action when there's no bootmanager entry selected, and if the list of entries is empty, reboot is impossible.
