Registered Member
|
OK, is there an easy way for me to tell that? I am not very familiar with Linux systems 'under the covers'! BTW next reboot everything started and menu items are functioning again.
Stuart |
Registered Member
|
Just to say that I still have all the debug options activated and my problem has not surfaced again. I am wondering if this could be a timing issue and the debug being on just tips it towards working?
Stuart |
Administrator
|
I would suggest using the "All Processes, Tree" view in the "System Activity" utility to view the list of processes launched by KSMServer.
This can be accessed from KRunner (Alt + F2). Please note that it is normal for KWin to be launched from KSMServer.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I have the same problem on F19 and KDE 4.11.1 and as mentioned above i ran the command as root and got the following error:
qdbus org.kde.ksmserver /KSMServer 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. I deleted .xsession-errors and performed a hard boot and I get the following exerpt from .xsession-errors: startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kbuildsycoca4(1614) KConfigGroup::readXdgListEntry: List entry MimeType in ".hidden/kmdr-executor.desktop" is not compliant with XDG standard (missing trailing semicolon). kbuildsycoca4(1614) KConfigGroup::readXdgListEntry: List entry Keywords in "/usr/share/applications/kde/kresources.desktop" is not compliant with XDG standard (missing trailing semicolon). kbuildsycoca4(1614)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/kde/kresources.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. Agent registered kded(1611) LayoutMemoryPersister::restoreFromFile: Failed to open layout memory xml file for reading "/home/shayne/.kde/share/apps/kded/session/keyboard/layout_memory.xml" error: 5 QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.19' QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.38' kwin(1662): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed" kwin(1662): ""fsrestore2" - conversion of "0,0,0,0" to QRect failed" QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL version string: 3.0 Mesa 9.2.0 OpenGL shading language version string: 1.30 Driver: Intel GPU class: IvyBridge OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 9.2 Linux kernel version: 3.11.1 Direct rendering: yes Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no QDBusObjectPath: invalid path "" plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(1673)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability QGraphicsLinearLayout::insertItem: cannot insert null item plasma-desktop(1673)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType "SolidModemManager" not found Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QGraphicsLinearLayout::removeAt: invalid index 0 ========================> 7 0 static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower. kded(1611)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType "SolidModemManager" not found kded(1611)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting "802-1x" not initialized kded(1611)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting "802-11-wireless-security" not initialized kded(1611)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting "802-1x" not initialized kded(1611)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting "802-1x" not initialized kded(1611)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting "802-11-wireless-security" not initialized Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) file:///usr/lib64/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: TypeError: Result of expression 'listView' [null] is not an object. file:///usr/lib64/kde4/imports/org/kde/plasma/components/SectionScroller.qml:175: ReferenceError: Can't find variable: sectionsRepeater file:///usr/lib64/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: Error: Cannot assign [undefined] to QString file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill. file:///usr/share/kde4/apps/plasma/plasmoids/battery/contents/ui/CompactRepresentation.qml:81:9: QML Column: Cannot specify top, bottom, verticalCenter, fill or centerIn anchors for items inside Column file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill. file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill. could this be related to the inoperable shutdown buttons? |
Administrator
|
The above output looks fine. The qdbus command I posted is intended to be run as your normal user, not root.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Well this is happening once again. the qdbus command does not cause the logout function to come up. I have all the debug options set and there are no references to shutdown in .xsession-errors. Looking in the System Monitor I can see the only thing related to the KDSMServer is Kwin, nothing else is linked to that in all processes.
The menu item Leave still does nothing, no window opens with the options to select Logout/Shutdown/Restart so I have to issue the command from the Run Command option and this will then effect the shutdown command immediately. One thing I did notice was that some items which should have started when I booted the system did not autostart, kmix ksensors both had to be started manually. Stuart |
Registered Member
|
Now I have turned off debug and stopped a whole bunch of stuff autostarting and leave now does what it should. The stuff I autostart is only stuff I have running anyway like Thunderbird and Firefox so no difference really except what starts them.
So go figure... I am more lost than ever to know what might be causing it. Also I have another PC which runs Fedora 19 like this one and it does not seem to have the sme problem, that PC is an Intel Core 2 Duo and this is an AMD Quad core. Stuart |
Administrator
|
Unfortunate - i've no idea why this doesn't work at all times i'm afraid. It is certainly supposed to work. I do know that KRunner has some involvement in this area, so ensuring it is running/restarting it could be another point to look into.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I am experiencing the same problem. So, I am very interested in a solution
One additional data point is that some of the Leave options work, but others don't. I can't Logout, Restart, or Shutdown, but I can Lock, Switch User, Sleep, and Hibernate. It appears that any of the options that want to start the dialog with the countdown timer are the ones that fail to work. I checked and krunner was not running, so I started it at the command line, but although it is now running, I still can't get nothing from Logout, Restart, or Shutdown from the Application Launcher. |
Registered Member
|
Another piece of follow-up information.
When I switch user and logout, then try to run "poweroff" from the command line I get a mssage that the other users is still logged in on seat0. A ps -ef shows that the other user still has a "vmtoolsd -n vmusr" comm command running. Going through the switch user/logout cycle again adds another another vmtoolsd command. |
Administrator
|
That is quite odd - vmtoolsd is related to VMWare's Tools, which should only be installed in guests. Is this system a VM, or a physical system?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Just an fyi, installing libdbusmenu-qt-dev fixed this issue for me
|
Administrator
|
Interesting observation - a developer package shouldn't include anything a running system needs, and libdbusmenu-qt is also unrelated to the shutdown process as it isn't used by KSMServer. Is anyone else able to confirm this?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
installing libdbusmenu-qt-dev also fixed this problem for me...
thanks |
Administrator
|
Are you both using the same distribution by any chance?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft