Created attachment 55819 [details] gdb backtrace Version: 4.4 (using KDE 4.5.5) OS: Linux Any KDE Application crashes sometimes while auto completion when entering a local path in the address line. See attached gdb backtrace. Reproducible: Sometimes Steps to Reproduce: Enter a local path in address line. Actual Results: SIGSEV Expected Results: Auto completion of local path.
[Thread 0xb1d5bb70 (LWP 22324) exited] QThread: Destroyed while thread is still running Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xaed6eb70 (LWP 22317)] QMutex::lock (this=0x50) at thread/qmutex.cpp:150 150 thread/qmutex.cpp: Datei oder Verzeichnis nicht gefunden. in thread/qmutex.cpp Current language: auto The current source language is "auto; currently c++" (gdb) thread apply all backtrace Thread 104 (Thread 0xaed6eb70 (LWP 22317)): #0 QMutex::lock (this=0x50) at thread/qmutex.cpp:150 #1 0xb70c2ade in QThreadPrivate::finish (arg=0x95f4638) at thread/qthread_unix.cpp:270 #2 0xb70c2fc6 in ~__pthread_cleanup_class (arg=0x95f4638) at /usr/include/pthread.h:535 #3 QThreadPrivate::start (arg=0x95f4638) at thread/qthread_unix.cpp:253 #4 0xb60b1955 in start_thread () from /lib/i686/cmov/libpthread.so.0 #5 0xb7e72e7e in clone () from /lib/i686/cmov/libc.so.6 Thread 58 (Thread 0xb1531b70 (LWP 21717)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb7e6c011 in select () from /lib/i686/cmov/libc.so.6 #2 0xb719a24c in QProcessManager::run (this=0xb72d6390) at io/qprocess_unix.cpp:245 #3 0xb70c2fbe in QThreadPrivate::start (arg=0xb72d6390) at thread/qthread_unix.cpp:248 #4 0xb60b1955 in start_thread () from /lib/i686/cmov/libpthread.so.0 #5 0xb7e72e7e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb5c4a710 (LWP 21241)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb7e65696 in poll () from /lib/i686/cmov/libc.so.6 ---Type <return> to continue, or q <return> to quit--- #2 0xb602106b in g_poll () from /lib/libglib-2.0.so.0 #3 0xb6013dbc in ?? () from /lib/libglib-2.0.so.0 #4 0xb60141c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0xb71eb075 in QEventDispatcherGlib::processEvents (this=0x804dc08, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0xb674eed5 in QGuiEventDispatcherGlib::processEvents (this=0x804dc08, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #7 0xb71bdae9 in QEventLoop::processEvents (this=0xbffff0c4, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #8 0xb71bdf3a in QEventLoop::exec (this=0xbffff0c4, flags=...) at kernel/qeventloop.cpp:201 #9 0xb71c316f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #10 0xb6690667 in QApplication::exec () at kernel/qapplication.cpp:3581 #11 0xb7fc79ff in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_konqueror.so #12 0x080485fb in _start ()
Here's a backtrace of _dolphin_ crashing, when I was typing in the location bar: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb3a9bb70 (LWP 6076)] QMutex::lock (this=0x50) at thread/qmutex.cpp:150 150 thread/qmutex.cpp: Datei oder Verzeichnis nicht gefunden. in thread/qmutex.cpp Current language: auto The current source language is "auto; currently c++". (gdb) thread apply all bt Thread 144 (Thread 0xb3a9bb70 (LWP 6076)): #0 QMutex::lock (this=0x50) at thread/qmutex.cpp:150 #1 0xb706fade in QThreadPrivate::finish (arg=0x88d8408) at thread/qthread_unix.cpp:270 #2 0xb706ffc6 in ~__pthread_cleanup_class (arg=0x88d8408) at /usr/include/pthread.h:535 #3 QThreadPrivate::start (arg=0x88d8408) at thread/qthread_unix.cpp:253 #4 0xb5d21955 in start_thread (arg=0xb3a9bb70) at pthread_create.c:300 #5 0xb63cee7e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 26 (Thread 0xb329ab70 (LWP 5939)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb63c8011 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xb714724c in QProcessManager::run (this=0xb7283390) at io/qprocess_unix.cpp:245 #3 0xb706ffbe in QThreadPrivate::start (arg=0xb7283390) at thread/qthread_unix.cpp:248 #4 0xb5d21955 in start_thread (arg=0xb329ab70) at pthread_create.c:300 #5 0xb63cee7e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb55eb710 (LWP 5889)): #0 0xb7fe2424 in __kernel_vsyscall () #1 0xb63c1696 in *__GI___poll (fds=0xb6444ff4, nfds=8, timeout=268) ---Type <return> to continue, or q <return> to quit--- at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb5c8c06b in g_poll () from /lib/libglib-2.0.so.0 #3 0xb5c7edbc in ?? () from /lib/libglib-2.0.so.0 #4 0xb5c7f1c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0xb7198075 in QEventDispatcherGlib::processEvents (this=0x80d1330, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0xb6773ed5 in QGuiEventDispatcherGlib::processEvents (this=0x80d1330, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #7 0xb716aae9 in QEventLoop::processEvents (this=0xbffff314, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #8 0xb716af3a in QEventLoop::exec (this=0xbffff314, flags=...) at kernel/qeventloop.cpp:201 #9 0xb717016f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #10 0xb66b5667 in QApplication::exec () at kernel/qapplication.cpp:3581 #11 0x0807bc3f in _start ()
Created attachment 61558 [details] New crash information added by DrKonqi kate (3.6.2) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2 - What I was doing when the application crashed: I was typing an directory path into the directory path bar of the open file dialog as usual and kate crashed. -- Backtrace (Reduced): #6 QMutex::lock (this=0x90) at thread/qmutex.cpp:151 #7 0x00007f39654427f9 in QThreadPrivate::finish (arg=<value optimized out>) at thread/qthread_unix.cpp:342 #8 0x00007f396544303d in ~__pthread_cleanup_class (arg=0x2457250) at /usr/include/pthread.h:535 #9 QThreadPrivate::start (arg=0x2457250) at thread/qthread_unix.cpp:325 #10 0x00007f39651b7914 in start_thread (arg=<value optimized out>) at pthread_create.c:297
*** Bug 281560 has been marked as a duplicate of this bug. ***
Feel free to reopen the report if the problem still happens in recent versions ( KDE SC 4.8.4 or higher). Thanks.