Summary: | sudo kate in yakuake starts kate and msg "could not start ksmserver. Check your instalation" | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | Jacek <jacek> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, bugs.kde.org, domlyons, echidnaman, faure, jacek, kdelibs-bugs, mutlu_inek, thoosle, untitled.no4 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jacek
2009-05-08 21:07:22 UTC
More info - In terminal it shows the same message. Maybe this will help: sudo kate [sudo] password for jacoor: Error: "/var/tmp/kdecache-jacoor" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-jacoor" is owned by uid 1000 instead of uid 0. Error: "/tmp/ksocket-jacoor" is owned by uid 1000 instead of uid 0. kate(8711) KToolInvocation::klauncher: klauncher not running... launching kdeinit Error: "/tmp/kde-jacoor" is owned by uid 1000 instead of uid 0. Error: "/tmp/ksocket-jacoor" is owned by uid 1000 instead of uid 0. kdeinit4: Shutting down running client. kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher Error: "/tmp/ksocket-jacoor" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-jacoor" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/bin/kded4 Error: "/var/tmp/kdecache-jacoor" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-jacoor" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... Error: "/var/tmp/kdecache-jacoor" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... Error: "/var/tmp/kdecache-jacoor" is owned by uid 1000 instead of uid 0. kbuildsycoca4(8752) KConfigGroup::readXdgListEntry: List entry MimeType in ".hidden/gmplayer.desktop" is not compliant with XDG standard (missing trailing semicolon). kbuildsycoca4(8752) KConfigGroup::readXdgListEntry: List entry MimeType in "/home/jacoor/.local/share/applications/firefox.desktop" is not compliant with XDG standard (missing trailing semicolon). kbuildsycoca4(8752) KConfigGroup::readXdgListEntry: List entry MimeType in "/home/jacoor/.local/share/applications/thunderbird.desktop" is not compliant with XDG standard (missing trailing semicolon). Error: "/var/tmp/kdecache-jacoor" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update kdeinit4: preparing to launch Can you detail "crashes KDE" ? Thanks Hi. By crash I mean fast close of KDE without any notification. It just closes all aplication and shows me login screen.. I'm not sure if it reload whole KDE (90 % sure it does) but I can't check it right now... Looks like the whole X session is crashing I'm running Kubuntu 9.04 and also just upgraded KDE from 4.2.2 to 4.2.3 and see this behavior as described by Jacek on two different machines. I also noticed the kate directory under ~/,kde/share/apps had owner and group set to root. I set these back to the proper user and group. Also, I noticed that /usr/bin/sudo and /usr/bin/sudoedit showed 1 link instead of two. I reinstalled sudo and corrected this. Unfortunately, none of these fixed the problem. However, since kdesudo launches kate ok, while using sudo results in the xmessage, it seems like this must be related to file permissions. The same happens with the 4.2.3 packages on Archlinux. It worked with 4.2.2. Now, however, running an application by issuing "sudo $appname" from konsole pops up an X window claiming ksmserver could not be started. Clicking on that notification to close it immediately shuts down the KDE session. Possibly related: running "kdesu dolphin" launches dolphin, but makes it unusable as any attempts to show files or folders fails with the error message "Could not start Process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files." I forgot to add that this is not restricted to either kate nor yakuake. As I explained, it happens when executing e.g. "sudo dolphin" on konsole as well. The bug should be assigned to a different product. Any suggestions? @mutlu inek: your case may be not related as the original reporter said it only happens with Kate. and it is getting a different error message. This happens to me too (Kubuntu 9.04, KDE 4.2.3). This is not specific to Kate, as it happens with Dolphin or Konqueror too. However, it doesn't happen with Kwrite or Okular. What happens is that the Kate/Dolphin/Konqueror window does open but the error message described above pops up. It is possible to work with the application anyway, but clicking the Okay button on the error message crashes X. Yes, I can confirm this with Konqueror. Reassigning to kdelibs What does and does not work (for launching dolphin): sudo {-H,} dolphin --> An X window with error message "Could not start Process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files." pops up and kills KDE when clicked. Moreover, in the case of dolphin, the program is not able to communicate via dbus and thus does not show files or folders at all. [Another user observed permission changes in ~/.kde4/{cache,socket,tmp}-$HOSTNAME from $USER to root when using sudo which might be related to KDE exiting when the X window message is clicked upon.] kdesu dolphin --> Dolphin is launched, but, again, dolphin does not show files or folders. su - dolphin --> Creating a new login shell works. Dolphin is launched and works. Moreover, from now on now running "kdesu dolphin" works, too (in the sense that it can communicate with dbus and show files and folders). Did anyone tried to use "dbus-launch application" instead of just "application" in all the "su/sudo/kdesu" situations ? Thanks sudo dbus-launch kate results the same as sudo kate - just checked. Some more possibly related information. While trying to get usb device to work in VirtualBox, I got the same error message. Removing myself from vboxusers have sorted this out. I see the following when I try dbus-launch kate which also results in the xmessage then crash behavior. kate(22833) KToolInvocation::klauncher: klauncher not running... launching kdeinit kdeinit4: Shutting down running client. kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update kded(22845) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "HAL-Power" kded(22845) XSyncBasedPoller::XSyncBasedPoller: 3 0 kded(22845) XSyncBasedPoller::XSyncBasedPoller: XSync seems available and ready Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection kded(22845) XSyncBasedPoller::setUpPoller: XSync Inited kded(22845) XSyncBasedPoller::setUpPoller: Supported, init completed kded(22845) PowerDevilDaemon::profileFirstLoad: Profile initialization X Error: XSyncBadAlarm 170 Extension: 152 (Uknown extension) Minor opcode: 11 (Unknown request) Resource id: 0x0 kded(22845) KDEDModule::setModuleName: registerObject() successful for "powerdevil" X Error: XSyncBadAlarm 170 Extension: 152 (Uknown extension) Minor opcode: 11 (Unknown request) Resource id: 0x0 I believe that this could possibly be related to bug 194607 and is perhaps fixed with svn revision 973813 (http://websvn.kde.org/?view=rev&revision=973813) Could anybody test this with KDE 4.2.4? I have just tested it with KDE 4.2.4 on Kubuntu and the bug is still there. *** This bug has been confirmed by popular vote. *** I checked with KDE SC 4.4 beta 2. All issues are gone: No more crashes when executing "sudo $appname". When executing "sudo dolphin" or "kdesu dolphin", Dolphin can actually browse the file system. I consider this bug fixed. Can anyone confirm? Yes, at least the ksmserver error message when restarting kdeinit4 was fixed in r957485 in April 2009. Yeah, this is fixed in 4.3 onwards. |