Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc3.4.1 OS: Linux Kuser crash at startup almost without any messages: KCrash: Application 'kuser' crashing... Unable to start Dr. Konqi gdb says: [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11956)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 11956)] 0x414f1649 in free () from /lib/i686/libc.so.6 Current language: auto; currently c
I am using kuser from kdeadmin 3.3.1 (compiled from source), Red Hat 9, gcc 3.2.2, qt 3.3.3. When attempting to start kuser, I get the following: Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1095226752 (LWP 15701)] [KCrash handler] #4 0x08078b14 in ~SID (this=0xbffff884) at qshared.h:50 #5 0x080641f0 in ~KUser (this=0xbffff820) at kuser.cpp:123 #6 0x40848705 in KStandardDirs::addCustomized () from /usr/lib/libkdecore.so.4 #7 0x40832482 in KConfig::KConfig () from /usr/lib/libkdecore.so.4 #8 0x40834140 in KSharedConfig::KSharedConfig () from /usr/lib/libkdecore.so.4 #9 0x40833f7f in KSharedConfig::openConfig () from /usr/lib/libkdecore.so.4 #10 0x408ade31 in KInstance::config () from /usr/lib/libkdecore.so.4 #11 0x408a61b4 in KGlobal::config () from /usr/lib/libkdecore.so.4 #12 0x408fec4b in KClipboardSynchronizer::KClipboardSynchronizer () from /usr/lib/libkdecore.so.4 #13 0x408feb1f in KClipboardSynchronizer::self () from /usr/lib/libkdecore.so.4 #14 0x4080590c in KApplication::init () from /usr/lib/libkdecore.so.4 #15 0x4080481b in KApplication::KApplication () from /usr/lib/libkdecore.so.4 #16 0x0806b98e in main (argc=1082422411, argv=0x4084748b) at main.cpp:53 #17 0x42015704 in __libc_start_main () from /lib/tls/libc.so.6 #18 0x08059b81 in _start () at ../sysdeps/i386/elf/start.S:81 If I can do anything to provide further information, then please let me know, as this is a VERY serious issue for my company.
What backend did you configure (files,ldap or system - the default is files)? What happens if you delete the kuserrc file (maybe it's corrupted)?
Deleting the kuserrc had no effect (still exactly the same crash). Following is the configure options that I used in building kdeadmin: --disable-rpath \ --with-rpm \ --with-qt-libraries=$QTDIR/lib \ --with-private-groups \ --with-shadow I have been using these same option since about KDE 3.2.0
> What backend did you configure (files,ldap or system - the > default is files)? No configuration - files probably. > What happens if you delete the kuserrc file (maybe > it's corrupted)? Always the same: segmentation fault at start-up.
*** This bug has been marked as a duplicate of 115359 ***