Application: kvpnc (0.9.6) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.0.0-13-generic-pae i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: first time trying to establish an vpn-connection to my univerisities vpn. I only get this far. The program always crashes right after starting. I was executing firefox, thunderbird and rhythmbox at the same time. The crash can be reproduced every time. -- Backtrace: Application: KVpnc (kvpnc), signal: Segmentation fault [Current thread is 1 (Thread 0xb4541930 (LWP 3088))] Thread 2 (Thread 0xb29ffb70 (LWP 3090)): #0 0xb76ec424 in __kernel_vsyscall () #1 0xb567d40e in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0xb4f3034b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4f21896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb4f21f9b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb4039cea in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #6 0xb4f485f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb63b0d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #8 0xb568c0ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb4541930 (LWP 3088)): [KCrash Handler] #7 0x0817768e in KVpncConfig::loadOptions (this=0x9f89370) at /build/buildd/kvpnc-0.9.6a/src/kvpncconfig.cpp:1016 #8 0x08204de5 in KVpnc::KVpnc (this=0x9f3eaa8, parent=0xbf8b2a18, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /build/buildd/kvpnc-0.9.6a/src/kvpnc.cpp:180 #9 0x0824cc28 in main (argc=1, argv=0xbf8b2dc4) at /build/buildd/kvpnc-0.9.6a/src/main.cpp:121 Possible duplicates by query: bug 286699, bug 282594, bug 274427, bug 272848, bug 271594. Reported using DrKonqi
Can you try to reproduce the crash without the background applications ? To rule out the possibility of an external issue.
No need, the bug is long fixed, but Ubuntu still ships the old version. *** This bug has been marked as a duplicate of bug 256013 ***