http://qa.mandrakesoft.com/show_bug.cgi?id=4377
Product: mdkkdm
Component: mdkkdm
Summary: after clicking reboot mdkkdm shows empty list of lilo
entries
Product: mdkkdm
Version: 9.1-24mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mdkkdm
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
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.
--
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.
