| Summary: | closing kate: signal 11; called with sudo - system fries when shutdown/reboot | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | ffab <ffab> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Error messages
attachmet comment #3 and terminal dialog sudo kate |
||
|
Description
ffab
2009-05-11 20:10:08 UTC
Created attachment 33555 [details]
Error messages
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdesdk-dbg", "kdelibs5-dbg" packages Thanks Reproducing the crash after installing the two "-dbg" modules. Some mor system informations: Kubuntu 9.04, KDE 4.2.3, installed in logical partition, bootloader "grub", bug was reproduced on different systems: NoName, Fujitsu-Siemens, Medion". Case 1: opening a terminal, starting kate, closing kate using file-menu: Terminal dialog: admin1000@pcag-nb1:~$ kate KCrash: Application 'kate' crashing... sock_file=/home/admin1000/.kde/socket-pcag-nb1/kdeinit4__0 crashmanager report - see attachment kate.crash1 After closing kate going on working was possible. Case 2 (sudo-case): opening a terminal, changing directory, starting kate with sudo kate The behavior differes from that without the installed debugging modules. The terminal dialog behaves as usual - see attachmet terminal_dialog. Now system creates an x-message: "Could not start ksmserver. Check your installation" Closing the x-message - (okay button) system logs out and a new login window is created. Now shutting down and rebooting is no problem. Created attachment 33576 [details] attachmet comment #3 and terminal dialog sudo kate sudo dialog admin1000@pcag-nb1:~$ cd /boot/grub admin1000@pcag-nb1:/boot/grub$ sudo kate [sudo] password for admin1000: Error: "/var/tmp/kdecache-admin1000" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-admin1000" is owned by uid 1000 instead of uid 0. Error: "/tmp/ksocket-admin1000" is owned by uid 1000 instead of uid 0. kate(3535) KToolInvocation::klauncher: klauncher not running... launching kdeinit Error: "/tmp/kde-admin1000" is owned by uid 1000 instead of uid 0. Error: "/tmp/ksocket-admin1000" 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-admin1000" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-admin1000" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/bin/kded4 Error: "/var/tmp/kdecache-admin1000" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-admin1000" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... Error: "/var/tmp/kdecache-admin1000" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... Error: "/var/tmp/kdecache-admin1000" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-admin1000" is owned by uid 1000 instead of uid 0. kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update kdeinit4: preparing to launch This was fixed recently on trunk. (it was a Qt bug fixed when using Qt4.5.1+) Marking as duplicate of bug 185708 Thanks. You can explain the other issue in a different report against the "kde" product. *** This bug has been marked as a duplicate of bug 185708 *** |