Bug 460071 - Shutdown fails in GNOME (GDM), errors from console-kit-daemon
Summary: Shutdown fails in GNOME (GDM), errors from console-kit-daemon
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: jmccann
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-08-25 22:08 UTC by Charlweed Hymerfan
Modified: 2015-01-14 23:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 14:15:06 UTC
Type: ---

Attachments (Terms of Use)

Description Charlweed Hymerfan 2008-08-25 22:08:55 UTC
Description of problem:
Shutdown fails in GNOME (GDM), errors from console-kit-daemon

Version-Release number of selected component (if applicable):
Fedora 9

How reproducible:
Every time

Steps to Reproduce:
1. Select "shutdown" on Gnome system menu, OR
 Click "shutdown" on gdm greeter screen 
Actual results:
System does not shut down.
Warning is logged in /var/log/messages
console-kit-daemon[1846]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL

Expected results:
System shuts down

Additional info:

I think this is a GNOME, GDM or console-kit-daemon bug, but I can't get better diagnostics.

If Shutdown is selected from the System menu, then I get logged off, but the system does NOT restart or reboot.
If I click the shutdown button on the GDM login screen, I get a dialog "failed to stop computer". If I click restart the dialog says "failed to restart".

I consistently get a message logged in /var/log/messages:

console-kit-daemon[1846]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL

I get nothing in secure or audit/audit.log. Turning selinux to permissive has no effect.

If I use KDE as a desktop, but GDM as the display manager, the "Leave" buttons fail in the same way, the system cannot be shut down. However, If I use KDM, then the system can be shutdown from the greeter AND from the "Leave" buttons.

Linux mawu.hymesruzicka.org #1 SMP Mon Aug 4 14:08:11 EDT 2008 i686 i686 i386 GNU/Linux
GNOME 2.22.0

Comment 1 Amanda Christensen 2008-09-18 02:39:39 UTC
I, too, am having a similar problem.  When I select shutdown the system waits for a few minutes and then will give me a message that it could not shutdown the system.

Comment 2 Bug Zapper 2009-06-10 02:33:00 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2009-07-14 14:15:06 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.