-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
<snip>
| In the mean time, can you try the following things:
| 1) install the debug symbols as said above and provide the updated | stack frames
done, above.
Thanks, it adds some more information, which may always come useful sooner or later.
| 2) kill kdesktop and run it again (or reboot your system, even | better). From CLI (outside TDE), run: | ps aux |grep kdesktop | Take note of the kdesktop_lock pid. Run: | gdb --pid=<kdesktop_lock pid> | After gdb attaches to the process, continue execution with: | c | At this stage kdesktop_lock should be running normally. Leave | everything running until kdesktop_lock crashes again. At this point | gdb should provide some info about the crash (perhaps a segmentation | fault - SIGSEGV). When it happens you should be able to get the stack | frame for kdesktop_lock (again thread apply all bt) since gdb is still | attached to the process. Do not exit gdb after that, not sure what | else we may need. All this is somehow experimental, if something | doesn't go to plan, please let me know.
will do.
Ok, let's take this as further step, see if we can find out what crashed kdesktop_lock first.
thanks very much for taking time to dig into this.
No problem, it's an interesting bug and may be a good way to learn something new, whether I am able to fix it or not :-)
Cheers Michele