trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: November 2014

Re: [trinity-users] Desktop Icons + Lock button = what to restart?

From: Gerhard Zintel <gerhard.zintel@...>
Date: Sat, 8 Nov 2014 21:56:53 +0100
On Monday 27 October 2014, Timothy Pearson wrote:
> > ------------- snip ------------------
> > konqueror: WARNING: failed to obtain ELF icon: ELF resource section not
> > found
> > TQClipboard: Unknown SelectionClear event received.
> > .
> > .
> > .
> > [kdesktop_lock] Warning: unable to create control socket
> > '/tmp/tdesocket-global/
> > kdesktoplockcontrol-0'.  Interactive logon modules may not function
> > properly.
> > [twin] X_SetInputFocus(0x1c00096): BadMatch (invalid parameter attributes)
> > .
> > .
> > .
> > X Error: BadWindow (invalid Window parameter) 3
> >   Major opcode:  19
> >   Minor opcode:  0
> >   Resource id:  0x1c00096
> > TQClipboard: Unknown SelectionClear event received.
> > [twin] X_SetInputFocus(0x3a6ebaa): BadMatch (invalid parameter attributes)
> > kmail: WARNING: FolderStorage::getMsg was asked for an invalid index. idx
> > =0 count()=0
> > ------------- snip ------------------
> > All errors are displayed more often before without the above described
> > desktop problem (no icons, no middle and right mouse button menu).
> > Process kdesktop is running but there is additionally a "[kdesktop_lock]
> > <defunct>" process. Might this be the culprit? I do not lock my desktop
> > normally.
> > I can not kill the <defunct> process but killing kdesktop process and
> > relaunching it restores all to normal.
> >
> > now I have a running
> > 21927 pts/4    S      0:00 kdesktop
> > 21928 pts/4    S      0:00 /opt/trinity/bin/kdesktop_lock --internal 21927
> >
> > process again.
> >
> > Gerhard
> 
> Sounds almost like kdesktop is deadlocked.  Next time it happens can you
> break into kdesktop with gdb (gdb --pid `pidof kdesktop`), execute "thread
> apply all bt", and post the output?
> 
> Thanks!
> 
> Tim
Today it happened again - and yes, I installed tdebase-trinity-dbg.

Output is not much. Here you are:
(gdb) thread apply all bt

Thread 1 (Thread 0xb588a980 (LWP 2802)):
#0  0xb7789424 in __kernel_vsyscall ()
#1  0xb75f3ce1 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0xb757031b in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


Don't know if this helps for anything. I try again next time.
Gerhard