Version: (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages Compiler: gcc 4 OS: Linux I am running Debian Testing (currently Lenny) on my AMD64 machine, under kernel 2.6.21. I was out for 2 months due to hospitalization. When I returned, I did the massive update that was waiting for me. Immediately afterward, Korganizer started crashing every time the machine starts up. Actually, that wa one of two casualties: the other was hal, a problem I have just resolved. At first I was convinced that Korganizer's failure was due to hal's -- but not so. Fixing hal did not help Korganizer at all. The only other detail I can think of to report is that Korganizer will not even try to start manually after this crash has happened. I.e., every attempt to start it manually results in total lack of results. Thank you *VERY* much!! :)
Oh, yes -- I forgot the original crash handler's message: "The application KOrganizer Reminder Daemon (korgac) crashed and caused the Signal 11 (SIGSEGV)." That is probably a very important detail, so I hasten to include it now. Thanks very much! :)
A BIT LATER ... Here is a transcript of what happens if I try to start korgac in root mode: Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kded: cannot connect to X server :0.0 kded: ERROR: KUniqueApplication: Registering failed! kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified korgac: cannot connect to X server :0.0 ERROR: KUniqueApplication: Registering failed! ERROR: Communication problem with korgac, it probably crashed. (It did indeed.)
The output in comment 2 is normal behaviour, nothing wrong with that. Please include the actual contents of the backtrace, only a sig 11 doesn't help us much. Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports for more information.
Hi there! I tried to follow the instructions in your website address. It wasn't easy, because there is no korganizer-dbg package. So I installed kdepim-dbg, since korganizer is described as a component of kdepim. Alas, it is still impossible to generate a backtrace. I went so far as to invoke gdb on the thing. Here is the entire transcript of the session: gdb korgac GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/korgac BFD: /lib64/ld-linux-x86-64.so.2: don't know how to handle OS specific section `.gnu.hash' [0x6ffffff6] warning: Unable to grok dynamic linker /lib64/ld-linux-x86-64.so.2 as an object file warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. warning: shared library handler failed to enable breakpoint Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kded: cannot connect to X server :0.0 DCOP aborting call from 'anonymous-4051' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified korgac: cannot connect to X server :0.0 ERROR: KUniqueApplication: Registering failed! ERROR: Communication problem with korgac, it probably crashed. Program exited with code 0377. (gdb) backtrace No stack. (gdb) q So I executed valgrind korgac. Here is the transcript of that session: valgrind korgac ==5570== Memcheck, a memory error detector. ==5570== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==5570== Using LibVEX rev 1732, a library for dynamic binary translation. ==5570== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==5570== Using valgrind-3.2.3-Debian, a dynamic binary instrumentation framework. ==5570== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==5570== For more details, rerun with: -v ==5570== Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified kded: cannot connect to X server :0.0 kded: ERROR: KUniqueApplication: Registering failed! kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified korgac: cannot connect to X server :0.0 ==5586== ==5586== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 5) ==5586== malloc/free: in use at exit: 5,633 bytes in 88 blocks. ==5586== malloc/free: 3,979 allocs, 3,891 frees, 158,148 bytes allocated. ==5586== For counts of detected errors, rerun with: -v ==5586== searching for pointers to 88 not-freed blocks. ==5586== checked 2,138,424 bytes. ==5586== ==5586== LEAK SUMMARY: ==5586== definitely lost: 0 bytes in 0 blocks. ==5586== possibly lost: 0 bytes in 0 blocks. ==5586== still reachable: 5,633 bytes in 88 blocks. ==5586== suppressed: 0 bytes in 0 blocks. ==5586== Rerun with --leak-check=full to see details of leaked memory. DCOP aborting call from 'anonymous-5570' to 'korgac' ERROR: Communication problem with korgac, it probably crashed. ==5570== ==5570== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 5) ==5570== malloc/free: in use at exit: 1,633 bytes in 52 blocks. ==5570== malloc/free: 3,856 allocs, 3,804 frees, 131,358 bytes allocated. ==5570== For counts of detected errors, rerun with: -v ==5570== searching for pointers to 52 not-freed blocks. ==5570== checked 2,134,368 bytes. ==5570== ==5570== LEAK SUMMARY: ==5570== definitely lost: 0 bytes in 0 blocks. ==5570== possibly lost: 0 bytes in 0 blocks. ==5570== still reachable: 1,633 bytes in 52 blocks. ==5570== suppressed: 0 bytes in 0 blocks. ==5570== Rerun with --leak-check=full to see details of leaked memory. This is the best I can do. I hope it helps. Thank you again, very much!! On Saturday 04 August 2007 05:10, Bram Schoenmakers wrote: [bugs.kde.org quoted mail]
Do you still have this issue ? If so, could you please provide a backtrace ?
You probably want kdepimlibs-dbg to go with the kdepims-dbg btw. Is this still an issue in a newer version?
On Wednesday 30 July 2008, A.Spehr wrote: [bugs.kde.org quoted mail] Nsy -- not for me. Thank you very much!
Excellent! ...and thanks for using KDE. ;)