When running KDE and letting the session run for several days (i.e. no 
restart/logout, just locking the screen over night), I get a kdeinit.code 
after ~5-6 days in my $HOME, and the system behaves weird (screenlock
doesn't act properly, etc.). The best way to fix this is to log out and 
log in again, effectively restarting KDE.

Has anyone seen this before? Is there a known fix?

Just asking before I go through the pain of finding the cause for this... 
gdb tells me the following stacktrace of the kdeinit.core file:

 	(gdb) bt
 	#0  0x4926ffeb in kill () from /usr/lib/libc.so.12
 	#1  0x492e4a47 in abort () from /usr/lib/libc.so.12
 	#2  0x4871a4fb in kDebugBackend(unsigned short, unsigned, char const*) ()
 	   from /usr/pkg/lib/libkdecore.so.4
 	#3  0x4871b032 in kdbgstream::flush() () from /usr/pkg/lib/libkdecore.so.4
 	#4  0x48088faa in endl(kdbgstream&) () from /usr/pkg/lib/libkparts.so.2
 	#5  0x493ce81e in kdemain () from /usr/pkg/lib/libkdeinit_kded.so
 	#6  0x493bc7d6 in kdeinitmain () from /usr/pkg/lib/kde3/kded.so
 	#7  0x0804cfb0 in execpath_avoid_loops(QCString const&, int, char const*, bool)
 	    ()
 	#8  0x0804f6e0 in main ()
 	#9  0x0804b992 in ___start ()
 	(gdb)

FWIW, this is kde-3.4.1 on NetBSD 2.0.2.


  - Hubert