[SOLVED] GUI shutdown dialog not appearing

[MrTempleDene]

This is an intermittant problem, sometimes when I try to shut down nothing brings up the gui dialog for either shutdown, restart or logout

Launcher>Leave>Shutdown doesn't bring up anything
[CRTL]+[ALT]+[DELETE] doesn't work

etc.

I can open a terminal and issue a shutdown command from there, which works, but of course this wont save my KDE desktop for the next session.

It's a minor annoyance but I would like to sort it out, or at the very least know what shell command might bring it up or let me exit KDE and shutdown gracefully.

I am running Mageia 4 fully updated with KDE 4.12, again, fully updated.

[doktor5000]

The command to shutdown would be the following, to run as the regular user who is logged in:

Code: Select all

qdbus org.kde.ksmserver /KSMServer logout 0 2 2

https://forum.kde.org/viewtopic.php?f=66&t=88022

Is there anything in ~/.xsession-errors at the time you try to shutdown via the menu buttons? Or anything in

Code: Select all

journalctl -b

[MrTempleDene]

Thank you, I'll have to wait until the condition hits again before I can try that.

I did try this command I found while trying to solve the problem myself

Code: Select all

qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout 0 0 0

It's a little different, but it did nothing so it was probably slightly off in syntax

journalctl -b returns nothing at the moment, but at the moment it is, of course, behaving itself.

[MrTempleDene]

Right, finally, my computer is exhibiting this condition again. So:-

I tried this and here are the results

Code: Select all

qdbus org.kde.ksmserver /KSMServer logout 0 2 2
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Then this.

Code: Select all

qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout 0 0 0
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


So as requested

Last half hour of journalctl -b (there's a lot in there)

Code: Select all

May 24 03:01:01 localhost.localdomain crond[10093]: pam_tcb(crond:session): Session opened for root by (uid=0)
May 24 03:01:01 localhost.localdomain CROND[10094]: (root) CMD (nice -n 19 run-parts --report /etc/cron.hourly)
May 24 03:01:01 localhost.localdomain anacron[10098]: Can't chdir to /var/spool/anacron: No such file or directory
May 24 03:01:01 localhost.localdomain crond[6961]: sendmail: fatal: chdir /var/spool/postfix: No such file or directory
May 24 03:01:01 localhost.localdomain postfix/sendmail[10099]: fatal: chdir /var/spool/postfix: No such file or directory
May 24 03:01:01 localhost.localdomain CROND[10093]: (root) MAIL (mailed 160 bytes of output but got status 0x004b
                                                    )
May 24 03:01:01 localhost.localdomain CROND[10093]: pam_tcb(crond:session): Session closed for root
May 24 03:09:01 localhost.localdomain crond[10181]: pam_tcb(crond:session): Session opened for root by (uid=0)
May 24 03:09:01 localhost.localdomain CROND[10182]: (root) CMD ([ -d /var/lib/php ] && find /var/lib/php/ -type f -depth -m
May 24 03:09:01 localhost.localdomain CROND[10181]: pam_tcb(crond:session): Session closed for root
May 24 03:17:09 localhost.localdomain sensord[5487]: Chip: radeon-pci-0008
May 24 03:17:09 localhost.localdomain sensord[5487]: Adapter: PCI adapter
May 24 03:17:09 localhost.localdomain sensord[5487]: temp1: 57.0 C
May 24 03:17:09 localhost.localdomain sensord[5487]: Chip: k10temp-pci-00c3
May 24 03:17:09 localhost.localdomain sensord[5487]: Adapter: PCI adapter
May 24 03:17:09 localhost.localdomain sensord[5487]: temp1: 57.6 C
May 24 03:37:09 localhost.localdomain sensord[5487]: Chip: radeon-pci-0008
May 24 03:37:09 localhost.localdomain sensord[5487]: Adapter: PCI adapter
May 24 03:37:09 localhost.localdomain sensord[5487]: temp1: 55.0 C
May 24 03:37:09 localhost.localdomain sensord[5487]: Chip: k10temp-pci-00c3
May 24 03:37:09 localhost.localdomain sensord[5487]: Adapter: PCI adapter
May 24 03:37:09 localhost.localdomain sensord[5487]: temp1: 57.4 C
May 24 03:37:39 localhost.localdomain su[10528]: pam_tcb(su:auth): Authentication passed for root from pete(uid=500)
May 24 03:37:39 localhost.localdomain su[10528]: (to root) pete on pts/1
May 24 03:37:39 localhost.localdomain su[10528]: pam_tcb(su:session): Session opened for root by pete(uid=500)


Last part of ~/.xsession-errors (not sure if I have got enough of this, but I have saved a sanpshot if needed)

Code: Select all

Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory

(evolution:8875): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Migrating cached data
Migrating config data
  mv /home/pete/.evolution/addressbook/views/custom_view-file:___home_pete_.evolution_addressbook_local_system.xml /home/pete/.config/evolution/addressbook/views/custom_view-file:___home_pete_.local_share_evolution_addressbook_local_system.xml
  FAILED: Destination file already exists
  mv /home/pete/.evolution/addressbook/views/current_view-file:___home_pete_.evolution_addressbook_local_system.xml /home/pete/.config/evolution/addressbook/views/current_view-file:___home_pete_.local_share_evolution_addressbook_local_system.xml
  FAILED: Destination file already exists
  mv /home/pete/.evolution/addressbook/searches.xml /home/pete/.config/evolution/addressbook/searches.xml
  FAILED: Destination file already exists
  mv /home/pete/.evolution/calendar/views/current_view-.xml /home/pete/.config/evolution/calendar/views/current_view-.xml
  FAILED: Destination file already exists
  mv /home/pete/.evolution/calendar/searches.xml /home/pete/.config/evolution/calendar/searches.xml
  FAILED: Destination file already exists
  mv /home/pete/.evolution/calendar/config/TaskPad /home/pete/.config/evolution/calendar/TaskPad
  FAILED: Destination file already exists
  rmdir /home/pete/.evolution/addressbook/views
  FAILED: Directory not empty (contents follows)
          current_view-file:___home_pete_.evolution_addressbook_local_system.xml
          custom_view-file:___home_pete_.evolution_addressbook_local_system.xml
  rmdir /home/pete/.evolution/calendar/config
  FAILED: Directory not empty (contents follows)
          TaskPad
  rmdir /home/pete/.evolution/calendar/views
  FAILED: Directory not empty (contents follows)
          current_view-.xml
Migrating local user data
  mv /home/pete/.evolution/signatures/signature-0 /home/pete/.local/share/evolution/signatures/signature-0
  FAILED: Destination file already exists
  mv /home/pete/.evolution/signatures/signature-1 /home/pete/.local/share/evolution/signatures/signature-1
  FAILED: Destination file already exists
  mv /home/pete/.evolution/signatures/signature-2 /home/pete/.local/share/evolution/signatures/signature-2
  FAILED: Destination file already exists
  mv /home/pete/.evolution/signatures/signature-3 /home/pete/.local/share/evolution/signatures/signature-3
  FAILED: Destination file already exists
  rmdir /home/pete/.evolution/signatures
  FAILED: Directory not empty (contents follows)
          signature-1
          signature-2
          signature-0
          signature-3
  rmdir /home/pete/.evolution/addressbook
  FAILED: Directory not empty (contents follows)
          views
          searches.xml
  rmdir /home/pete/.evolution/calendar
  FAILED: Directory not empty (contents follows)
          views
          searches.xml
          config
  rmdir /home/pete/.evolution/signatures
  FAILED: Directory not empty (contents follows)
          signature-1
          signature-2
          signature-0
          signature-3
kded(7129) ContactRequestHandler::onNewAccountAdded:

(evolution:8875): camel-WARNING **: Cannot load summary file: Success

(evolution:8875): camel-WARNING **: Cannot load summary file: Success

(evolution:8875): camel-WARNING **: Unable to load store summary: Expected version (1), got (0)

(evolution:8875): camel-WARNING **: Cannot load summary file: Success

(evolution:8875): camel-WARNING **: Cannot load summary file: Success

(evolution:8875): camel-WARNING **: Cannot load summary file: Success
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:209:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:209:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/LastNotificationPopup.qml:355: TypeError: Result of expression 'notificationsModel.get((notificationsView.count-1)-notificationsView.currentIndex)' [undefined] is not an object.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:209:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:209:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:209:21: QML TextEdit: Possible anchor loop detected on fill.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:163:13: QML Item: Binding loop detected for property "height"
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: Possible anchor loop detected on fill.
Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
KDirWatch: /home/pete/.xsession-errors is a file. Use addFile!
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)


I have no idea if any of that can help, I am out of my depth here now.

[MrTempleDene]

A shutdown command will work but it's not clean, I like having my desktop saved for my next session.

[doktor5000]

Right, finally, my computer is exhibiting this condition again. So:-

I tried this and here are the results

Code: Select all

qdbus org.kde.ksmserver /KSMServer logout 0 2 2
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Then this.

Code: Select all

qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout 0 0 0
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


Hmmm, seems dbus is completely broken or does not reply. Can you please show the output as root of

Code: Select all

journalctl -b /usr/bin/dbus-daemon

(you might need to adjust -b to the boot where the problems occured. -b is the current boot, -b-1 is the last boot, -b-2 is the second-to-last boot.)
I'll try to find out more about that errors in the meantime.

Last half hour of journalctl -b (there's a lot in there)

Code: Select all

May 24 03:01:01 localhost.localdomain anacron[10098]: Can't chdir to /var/spool/anacron: No such file or directory
May 24 03:01:01 localhost.localdomain crond[6961]: sendmail: fatal: chdir /var/spool/postfix: No such file or directory
May 24 03:01:01 localhost.localdomain postfix/sendmail[10099]: fatal: chdir /var/spool/postfix: No such file or directory


Nope, not really much in there. You should check those missing directories, might lead to a deeper problem.

Last part of ~/.xsession-errors (not sure if I have got enough of this, but I have saved a sanpshot if needed)

Code: Select all

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)


Also not really anything interesting in there, except the last line. But seems it's harmless: https://forum.kde.org/viewtopic.php?f=66&t=85531

[doktor5000]

Found a pretty old thread with similar issues: viewtopic.php?f=15&t=1400 Although no solution ...

Would probably be the best idea to try to reproduce this issue with a newly created user.

[jiml8]

FWIW (probably not much...) I see a similar problem much of the time. I have never attempted to debug it because of the complexity of my system, and because usually I am only trying to shut down KDE so that I can restart it...which is necessary every week or so because gradually my environment becomes corrupted.

I run TOR with Vidalia, and Vidalia will often cancel my logout (for reasons of its own), so I usually terminate Vidalia before attempting to logout. I also run compiz and vmware workstation. If the system has been up for only a few hours, it will log out without incident. But after a week or so, things start to get tangled up so I shut down Vidalia, suspend all virtual machines, then attempt a logout (and usually wind up just killing the dm service from a console because the logout hangs), then stop and restart all the vmware services (often manually killing vmware functions that don't die when I do this), then restart dm and log back in.

I have no idea if any of this information is at all useful in trying to determine the nature of OP's problem. For my own case, I have long assumed that bugs eventually were leading to memory corruption that kept things from working. It practically never crashes, but performance suffers badly enough that I have to clean it up from time to time by restarting my X session.

[doktor5000]

FWIW (probably not much...) I see a similar problem much of the time. I have never attempted to debug it because of the complexity of my system, and because usually I am only trying to shut down KDE so that I can restart it...which is necessary every week or so because gradually my environment becomes corrupted.

FWIW, if you only want to restart/reload your plasma session, you could also use

Code: Select all

kquitapp plasma-desktop && plasma-desktop &

but that will not work if you need to relaunch your whole desktop session.

Also, the OP seems to have slightly different problems, as the logout dialog itself doesn't even show up. Does that also apply for you?

[MrTempleDene]

OK, I'm in "luck" as it's just failed again, here are the results from "journalctl -b /usr/bin/dbus-daemon"

Code: Select all

journalctl -b /usr/bin/dbus-daemon
-- Logs begin at Mon 2015-05-25 09:58:11 BST, end at Mon 2015-05-25 13:39:47 BST. --
May 25 09:59:47 localhost.localdomain dbus[10673]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
May 25 09:59:48 localhost.localdomain dbus[10673]: [system] Successfully activated service 'org.freedesktop.systemd1'
May 25 09:59:48 localhost.localdomain dbus[10673]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May 25 09:59:49 localhost.localdomain dbus[10673]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
May 25 09:59:49 localhost.localdomain dbus[10673]: [system] Successfully activated service 'org.freedesktop.ColorManager'
May 25 10:02:34 localhost.localdomain dbus[10673]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 25 10:02:35 localhost.localdomain dbus[10673]: [system] Successfully activated service 'org.freedesktop.UDisks2'
May 25 10:02:36 localhost.localdomain dbus[10673]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
May 25 10:02:36 localhost.localdomain dbus-daemon[10673]: no kernel backlight interface found
May 25 10:02:36 localhost.localdomain dbus[10673]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 25 10:02:51 localhost.localdomain dbus[10673]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
May 25 10:02:51 localhost.localdomain dbus[10673]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'


[jiml8]

Also, the OP seems to have slightly different problems, as the logout dialog itself doesn't even show up. Does that also apply for you?

Sometimes yes, else I would not have mentioned it. But not every time.

In my own case, I am quite sure that over time memory corruption is occurring, particularly associated with video memory. I am inclined to blame vmware workstation and flashplayer for this, although compiz might also play a role. Also, of course, there's that closed-source blob known as the Nvidia video driver which doubtless has a hand in the problem. I normally will try to log out only after a week or more when I have more than 2 and sometimes more than 3 GB of memory used up on the video card (and much of that is lost), and X is taking too much processor time, and the display is sometimes hanging for several seconds at a time.

Upon logout, typically the GUI will hang. Sometimes this is before the requester appears; usually it is after I have clicked on the requester.

So, I cannot say this is the same thing OP sees. If OP only sees the symptoms after a long period of login time, then it might be the same problem. Also, if OP is using nvidia, then the problem could be there too.

[MrTempleDene]

I don't tend to be logged in as long as that, I shutdown my computer when I don't need it and it doesn't run any servers or anything, it's just the machine I use for my everyday work and leisure. I's unlikely it's on for more than 10-12 hours at a stretch.

I have a laptop with Mageia on it, the same, all fully patched and up to date, and that has never had this issue, so I suspect it could well be related to hardware drivers somewhere along the lines.

[doktor5000]

Well, the journal excerpts don't show anything obvious or bad. What you could try is if you can still login via ssh or something, and try to kill kdeinit4 process so the KDE session will be shutdown, and you can safely reboot.

Code: Select all

pkill kdeinit4

should help with that if you can't use dbus commands. Not sure if kquitapp would work without an X/dbus session or if it would be sufficient to only specify DISPLAY.
But you should ask upstream about that issue in KDE forums for further debugging: https://forum.kde.org/ and please post back the link here so others could follow up on that.

First bet would probably be to enable more debug messages via kdebugdialog and at least enable everything kdecore* and ksmserver or simply enable everything.

[doktor5000]

In my own case, I am quite sure that over time memory corruption is occurring, particularly associated with video memory. I am inclined to blame vmware workstation and flashplayer for this, although compiz might also play a role. Also, of course, there's that closed-source blob known as the Nvidia video driver which doubtless has a hand in the problem. I normally will try to log out only after a week or more when I have more than 2 and sometimes more than 3 GB of memory used up on the video card (and much of that is lost), and X is taking too much processor time, and the display is sometimes hanging for several seconds at a time.
[...]
So, I cannot say this is the same thing OP sees. If OP only sees the symptoms after a long period of login time, then it might be the same problem. Also, if OP is using nvidia, then the problem could be there too.

Well, I also use the proprietary driver, and flash. And I've not yet seen similar corruption, althoughuptime is mostly between 1 week and 2 or 3 weeks so not always that long.
But I don't use compiz, only the built-in KDE desktop effects.

[MrTempleDene]

I decided as Mageia 5 was coming out, I'd wait and see if that solved the problem. It's been installed for a few days now, and so far so good. I think I can declare this [SOLVED]