The menu items for shutting down, restarting and logging out don't do anything when I click on them. They used to work. I created a new user and the menu items for that user do work. I'm thinking the problem exists in a corrupt file under my user's .kde directory. Does anyone know what config files I might look at to get my shutdown/logout buttons to work, or any other ideas?

I assume this problem is persistent across reboots?

I have this failure sometimes. After a reboot (sudo shutdown -r now) the buttons work as expected.

Compare viewtopic.php?f=17&t=119788
Do you have _IceTransSocketUNIXConnect: Cannot connect to non-local host strings in ~/.xsession-errors ?

luebking wrote:Compare viewtopic.php?f=17&t=119788
Do you have _IceTransSocketUNIXConnect: Cannot connect to non-local host strings in ~/.xsession-errors ?

Not anywhere in there.

apparently not the changin hostname issue then.
what's your DisplayManager (kdm, gdb, ldm, mdm, xdm ....) and the outputs of

Code: Select all

kdmctl caps
qdbus org.kde.ksmserver /KSMServer


Today it is happend again:

No such Strings in ~/xsession-errors.

Outputs:

Code: Select all

$ kdmctl caps
ok      kdm     list    local   activate        shutdown        shutdown ask    nuke    reserve 3       lock    suicide

Code: Select all

$ qdbus org.kde.ksmserver /KSMServer
signal void org.kde.KSMServerInterface.subSessionCloseCanceled()
signal void org.kde.KSMServerInterface.subSessionClosed()
signal void org.kde.KSMServerInterface.subSessionOpened()
method bool org.kde.KSMServerInterface.canShutdown()
method QString org.kde.KSMServerInterface.currentSession()
method void org.kde.KSMServerInterface.logout(int, int, int)
method void org.kde.KSMServerInterface.restoreSubSession(QString)
method void org.kde.KSMServerInterface.resumeStartup(QString)
method void org.kde.KSMServerInterface.saveCurrentSession()
method void org.kde.KSMServerInterface.saveCurrentSessionAs(QString)
method void org.kde.KSMServerInterface.saveSubSession(QString, QStringList, QStringList)
method QStringList org.kde.KSMServerInterface.sessionList()
method void org.kde.KSMServerInterface.suspendStartup(QString)
method void org.kde.KSMServerInterface.wmChanged()
method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name)
method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString interface_name)
method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value)
method QString org.freedesktop.DBus.Introspectable.Introspect()
method QString org.freedesktop.DBus.Peer.GetMachineId()
method void org.freedesktop.DBus.Peer.Ping()

If i try to shutdown with the Dbus-method logout from KSMServer:

Code: Select all

$ dbus-send --print-reply --dest=org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout int32:0 int32:2 int32:2
method return sender=:1.10 -> dest=:1.1693 reply_serial=2

Up to the last line nothing happend.

Here i am using kdm on an ach-linux, but i know that some people do have similiar problems with kubuntu (lightdm) too.

In addition the output from today, when shutdown works fine:

Code: Select all

$ dbus-send --print-reply --dest=org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout int32:1 int32:2 int32:2
method return sender=:1.10 -> dest=:1.158 reply_serial=2

Could the logout be inhibited? Can you still interact normally with the system after the failed logout attempt?

Maybe its a problem with polkit authentication agent? Studiing the logs i found:

Boot without shutdownoptions:

Code: Select all

Mär 15 17:43:16 kaputtnik-arch systemd[1]: Started Authorization Manager.
Mär 15 17:43:16 kaputtnik-arch polkitd[322]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Mär 16 00:06:49 kaputtnik-arch systemd[1]: Stopping Authorization Manager...
Mär 16 00:06:49 kaputtnik-arch systemd[1]: Stopped Authorization Manager.

A normal boot looks like this:

Code: Select all

Mär 16 09:34:19 kaputtnik-arch systemd[1]: Started Authorization Manager.
Mär 16 09:34:33 kaputtnik-arch polkitd[337]: Registered Authentication Agent for unix-session:1 (system bus name :1.29 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Mär 16 09:37:37 kaputtnik-arch polkitd[337]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.29, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Mär 16 09:37:38 kaputtnik-arch systemd[1]: Stopping Authorization Manager...


But i am not sure if this is the right track. And because it happens to me only sometimes, it is not easy to stay at this failure. In case of polkit: i do not need this agent really. As i understoud, it is there to bring superuser rights for Packagemanagement or something else, which needs such rights in a graphical environment. But i do not need this graphical superuser-environment (or really rare).

It would be great, if vayu could answer some questions:
1. Persists the problem between boots?
2. What is the output from

Code: Select all

dbus-send --print-reply --dest=org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout int32:0 int32:2 int32:2

3. is the polkitdaemon running and is "polkit-kde-authetication-agent-1" loaded?

Polkit has no involvement in logout/shutdown/restart - that indication of it going down is likely the agent exiting as part of the logout process, or because it crashed.

Ok, this evening it happens again. I noticed the mousecursor jumping a lot of time and klipper did not start. At this point i know that the shutdownbuttons do not work. I tried to find something, which would help to investigate whats going wrong, but i do not find anything, except that the "polkit-kde-authentication-agent" is not running. I found a hint on this in https://bugzilla.redhat.com/show_bug.cgi?id=983110

Next time i will try to start this agent manually, before i reboot the the system.

Okay. If I recall correctly, this has historically been an extremely difficult issue to troubleshoot. Hopefully it doesn't resurface.

Hm, sounds bad I will report any results further which i could find.

Last time it happens as i add a bootoption to /etc/default/grub and updatet grub. The reboot results in a "shutdownbutton-not-working" situation. But i dont think, that something like this will cause the failure.

"polkit-kde-authentication-agent" could be startet without errors.

Listing procecces (with "ps axjf") shows something strange:

Code: Select all

    1  1157   286   286 ?           -1 Sl    1000   0:00 /usr/bin/knotify4
    1  1158  1158  1158 ?           -1 Ss    1000   0:00 kdeinit4: kdeinit4 Runnin e
 1158  1160  1158  1158 ?           -1 S     1000   0:00  \_ kdeinit4: klauncher [kdei e
 1158  5299  1158  1158 ?           -1 Sl    1000   1:18  \_ /usr/bin/qupzilla -p=original
 1158  8378  1158  1158 ?           -1 S     1000   0:00  \_ kdeinit4: kio_http [kdein e
 1158  8379  1158  1158 ?           -1 S     1000   0:00  \_ kdeinit4: kio_http [kdein e
 1158  8393  1158  1158 ?           -1 S     1000   0:00  \_ kdeinit4: kio_http [kdein e
 1158  8990  1158  1158 ?           -1 S     1000   0:00  \_ kdeinit4: kio_http [kdein e
 1158  8996  1158  1158 ?           -1 S     1000   0:00  \_ kdeinit4: kio_http [kdein e

Some procecces are not shown correctly, they are cropped. The misbehaved rows are only those which originally look like this:

Code: Select all

[...]
  334  1644   334   334 ?           -1 Sl    1000   0:00  \_ kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-user
[...]

I dont know, where the misbahved rows come from. A failure of ps, bash or konsole?

Next time i will look into the /proc/-folder, to investigate the appropriate processfolder.

Any other hints, where i could look at?

Did we determine whether it could be a hidden window that inibits logout?
see https://git.reviewboard.kde.org/r/115955/