hello when i look for k3b, and other apps which names i dont remember just now, in Kickoff panel dissapear and desktop crash, i did still can using open windows, but i didnt see anything else. THZ i writte in this Component category becouse i don't where to put it.
CC: (none) => isde115
we need more info, backtrace if you have any, ~/.xsession-errors or anything else I don't remember.
Component: Installer => RPM Packages
hello, i atach xsession diff after error > KCrash: Attempting to start /usr/bin/plasma-desktop from kdeinit > KCrash: Application 'plasma-desktop' crashing... > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > QSocketNotifier: Invalid socket 8 and type 'Read', disabling... > QSocketNotifier: Invalid socket 5 and type 'Read', disabling... > QSocketNotifier: Invalid socket 11 and type 'Read', disabling... > QSocketNotifier: Invalid socket 15 and type 'Exception', disabling... > QSocketNotifier: Invalid socket 18 and type 'Read', disabling... > QSocketNotifier: Invalid socket 22 and type 'Read', disabling... > QSocketNotifier: Invalid socket 24 and type 'Read', disabling... > QSocketNotifier: Invalid socket 26 and type 'Read', disabling... > QSocketNotifier: Invalid socket 28 and type 'Read', disabling... > QSocketNotifier: Invalid socket 30 and type 'Read', disabling... > QSocketNotifier: Invalid socket 32 and type 'Read', disabling... > QSocketNotifier: Invalid socket 34 and type 'Read', disabling... > QSocketNotifier: Invalid socket 36 and type 'Read', disabling... > QSocketNotifier: Invalid socket 38 and type 'Read', disabling... > QSocketNotifier: Invalid socket 40 and type 'Read', disabling... > QSocketNotifier: Invalid socket 42 and type 'Read', disabling... > QSocketNotifier: Invalid socket 44 and type 'Read', disabling... > QSocketNotifier: Invalid socket 46 and type 'Read', disabling... > QSocketNotifier: Invalid socket 48 and type 'Read', disabling... > QSocketNotifier: Invalid socket 50 and type 'Read', disabling... > QSocketNotifier: Invalid socket 52 and type 'Read', disabling... > QSocketNotifier: Invalid socket 60 and type 'Read', disabling... > plasma-desktop: Fatal IO error: client killed > plasma-desktop(3595): Communication problem with "plasma-desktop" , it probably crashed. > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " > > sock_file=/home/israeldeago/.kde4/socket-PCA/kdeinit4__0 > sock_file=/home/israeldeago/.kde4/socket-PCA/kdeinit4__0 > drkonqi(3596): Unable to find an internal debugger that can work with the KCrash backend > drkonqi(3596): The specified process does not exist. Thz
CC: (none) => balcaen.john, lmenut, nicolas.lecureuil
i don't reproduce, what would be useful would be to attach plasma-desktop to gdb and then make it crash, so we would have a backtrace. can you do that ?
(In reply to comment #3) > i don't reproduce, what would be useful would be to attach plasma-desktop to > gdb and then make it crash, so we would have a backtrace. > > can you do that ? hello, sorry about this, but i had never use gdb before, and i read about it, but when i use "gdb plasma-desktop #PID" i can't click plasma buttons. And when i only use "gdb plasma-desktop", i cant take backtrace, with killing or not. Could you recomend me a gdb tuto for this, or con you give the comand. THZ and sorry
No comment in over 2 years. Report was not reproduced so close old.
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => OLD