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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

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.
Comment by Smith Dhumbumroong (zodmaner) - Sunday, 14 October 2007, 14:52 GMT
I also got this error message when reboot on Arch 64 bit.
Comment by Sebastian Vandekerckhove (ptitfox) - Monday, 15 October 2007, 13:37 GMT
You must edit your "/usr/share/gdm/defaults.conf" and replace :
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
Comment by Riri (chicha) - Wednesday, 21 November 2007, 21:30 GMT
Also replace /usr/bin/poweroff by /sbin/poweroff in HaltCommand variable
Comment by Paul Bredbury (brebs) - Friday, 21 December 2007, 21:59 GMT
defaults.conf in the PKGBUILD dir should have the following removed:

/usr/bin/reboot;
/usr/bin/poweroff;

There's no point in Arch providing this file, and having it contain invalid file references.
Comment by Greg (dolby) - Saturday, 17 May 2008, 09:46 GMT
Has this been fixed?
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 17 May 2008, 09:56 GMT
I just reinstall gdm and it still have wrong reboot and shutdown path.
Comment by Riri (chicha) - Saturday, 17 May 2008, 11:59 GMT
Hello dolby,

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 ?
Comment by Jan de Groot (JGC) - Saturday, 17 May 2008, 17:33 GMT
The reboot path is not a critical bug. The reason for not updating or fixing gdm is that I'm using it at this machine to power a whole network of terminal clients. Stopping and starting gdm will disconnect those clients. As the current version still works, I've always postponed updates or fixes to the gdm package.

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.

Loading...