The last few days, Kpatience crashes randomly on me, during play. The latest update of the program itself was in april, so probably due to an update of some dependent library. > kpat KCrash: Application 'kpat' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/hendrik/.kde4/socket-madsen/kdeinit4__0 QSocketNotifier: Invalid socket 9 and type 'Read', disabling... kpat: Fatal IO error 9 (Ongeldige bestandsdescriptor) on X server :0. Unable to start Dr. Konqi Reproducible: Always
Seems like Gypsy is the culprit, Mod 3 works without crashing.
If the crash only happens in Gypsy that it's probably Bug 283191. Without a proper backtrace, though, we can't be sure. For instructions on how to produce a useful backtrace see here: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
I do not know how to find out whether it’s a dup of 283191, so here’s a backtrace: Thread 31 (Thread 0xb2a81b70 (LWP 25611)): #0 MemoryManager::new_from_block (this=0xa, s=48) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/memory.cpp:164 #1 0x0807d452 in Solver::pack_position (this=0x85a90a0) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/patsolve.cpp:369 #2 0x0807ddca in Solver::insert (this=0x85a90a0, cluster=0xb2a81238, d=88, node=0xb2a8123c) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/patsolve.cpp:1046 #3 0x0807de92 in Solver::new_position (this=0x85a90a0, parent=0xb07276c0, m=0xb0cc1238) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/patsolve.cpp:1077 #4 0x0807e2f6 in Solver::solve (this=0x85a90a0, parent=0xb07276c0) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/patsolve.cpp:739 #5 0x0807e532 in Solver::doit (this=0x85a90a0) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/patsolve.cpp:664 #6 0x0807e59c in Solver::patsolve (this=0x85a90a0, _max_positions=-1, _debug=false) at /usr/src/debug/kdegames-4.7.2/kpat/patsolve/patsolve.cpp:958 #7 0x08069c23 in SolverThread::run (this=0x85b4630) at /usr/src/debug/kdegames-4.7.2/kpat/dealer.cpp:114 #8 0xb71ca613 in QThreadPrivate::start (arg=0x85b4630) at thread/qthread_unix.cpp:331 #9 0xb5dbaa7d in start_thread () from /lib/libpthread.so.0 #10 0xb6506abe in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5212710 (LWP 25520)): #0 0xb64fbbb4 in poll () from /lib/libc.so.6 #1 0xb5abcf7b in g_poll () from /usr/lib/libglib-2.0.so.0 #2 0xb5aae466 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0xb5aae7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0xb72f3847 in QEventDispatcherGlib::processEvents (this=0x8163268, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #5 0xb68b0b1a in QGuiEventDispatcherGlib::processEvents (this=0x8163268, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #6 0xb72c445d in QEventLoop::processEvents (this=0xbfffed74, flags=...) at kernel/qeventloop.cpp:149 #7 0xb72c46a1 in QEventLoop::exec (this=0xbfffed74, flags=...) at kernel/qeventloop.cpp:201 #8 0xb72c8dfa in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #9 0xb67fada4 in QApplication::exec () at kernel/qapplication.cpp:3755 #10 0x0805c7f1 in main (argc=Cannot access memory at address 0x6 ) at /usr/src/debug/kdegames-4.7.2/kpat/main.cpp:329
Thanks a lot for the quick response with a complete backtrace. It is indeed a duplicate. It has been fixed in the latest KDESC 4.8.x and 4.9 releases. *** This bug has been marked as a duplicate of bug 283191 ***