FS#8304 - GDM has wrong 'reboot' path
Attached to Project:
Arch Linux
Opened by Jefferson Caldeira (Jefones) - Sunday, 14 October 2007, 14:16 GMT
Last edited by Jan de Groot (JGC) - Saturday, 11 October 2008, 23:23 GMT
Opened by Jefferson Caldeira (Jefones) - Sunday, 14 October 2007, 14:16 GMT
Last edited by Jan de Groot (JGC) - Saturday, 11 October 2008, 23:23 GMT
|
Details
Hi,
In reboot the show message: ... gdm-binary[4262]: WARNING: Command failed /usr/bin/reboot ... ... Package version is 2.20.0-1 |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 11 October 2008, 23:23 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.20.8 in testing.
Saturday, 11 October 2008, 23:23 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.20.8 in testing.
RebootCommand=/usr/bin/reboot;/sbin/reboot;/sbin/shutdown -r now;/usr/sbin/shutdown -r now
by
RebootCommand=/sbin/reboot;/sbin/shutdown -r now;/usr/sbin/shutdown -r now
/usr/bin/reboot;
/usr/bin/poweroff;
There's no point in Arch providing this file, and having it contain invalid file references.
This bug is not fixed. There are also some other gdm bugs which are not fixed such 8409, 8125, 8428 and probably others.
Those bugs are not critical.
The question is that there is a new gdm which is actively developed (and even used in Fedora 9).
I am wondering whether we should spend time fixing those bugs for a software which will die (new gdm is another branch with massive changes) or if we wait for the new gdm (next Gnome release probably) and see if those bugs are still valid ?
What is devs opinion about this ?
I see there's a gdm 2.22.0 package available. It's not officially part of gnome 2.22 because the 2.21 series had too many regressions that were unfixable before the official GNOME 2.22 release. I haven't read the news or changelog files, but I guess 2.22.0 is usable. I'll investigate updating gdm to 2.22.0 in a while when I have time and resources to play with gdm.