Application: dolphin (15.12.0) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I tried to change permisions on folder recrusivelly, and Dolphin crashed -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f34f9a8c800 (LWP 23854))] Thread 3 (Thread 0x7f34e186e700 (LWP 23855)): #0 0x00007f34f932dc1d in poll () at /lib64/libc.so.6 #1 0x00007f34ec2ef422 in () at /usr/lib64/libxcb.so.1 #2 0x00007f34ec2f100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007f34e41f53c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007f34f347832f in () at /usr/lib64/libQt5Core.so.5 #5 0x00007f34eda34754 in () at /usr/X11R6/lib64/libGL.so.1 #6 0x00007f34eef2b0a4 in start_thread () at /lib64/libpthread.so.0 #7 0x00007f34f933604d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f34d6ca4700 (LWP 23856)): #0 0x00007f34f9329ced in read () at /lib64/libc.so.6 #1 0x00007f34eda3373c in () at /usr/X11R6/lib64/libGL.so.1 #2 0x00007f34ea03ebf7 in () at /usr/lib64/tls/libnvidia-tls.so.304.128 #3 0x00007f34ee3e6b60 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007f34ee3a5999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #5 0x00007f34ee3a5df8 in () at /usr/lib64/libglib-2.0.so.0 #6 0x00007f34ee3a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x00007f34f36aad8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #8 0x00007f34f3651d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #9 0x00007f34f347361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #10 0x00007f34f347832f in () at /usr/lib64/libQt5Core.so.5 #11 0x00007f34eda34754 in () at /usr/X11R6/lib64/libGL.so.1 #12 0x00007f34eef2b0a4 in start_thread () at /lib64/libpthread.so.0 #13 0x00007f34f933604d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f34f9a8c800 (LWP 23854)): [KCrash Handler] #6 0x0000000000000000 in () #7 0x00007f34f366450d in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at /usr/lib64/libQt5Core.so.5 #8 0x00007f34f7940304 in KDialogJobUiDelegate::Private::next() () at /usr/lib64/libKF5JobWidgets.so.5 #9 0x00007f34f3684ac6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x00007f34f47c8e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x00007f34f47cdcc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x00007f34f3653e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x00007f34f3656057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #14 0x00007f34f36ab8f3 in () at /usr/lib64/libQt5Core.so.5 #15 0x00007f34ee3a5c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x00007f34ee3a5ed8 in () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f34ee3a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x00007f34f36aad6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #19 0x00007f34f3651d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #20 0x00007f34f36598f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #21 0x00007f34f96585f1 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so #22 0x00007f34f9272b05 in __libc_start_main () at /lib64/libc.so.6 #23 0x00000000004007ee in _start () Possible duplicates by query: bug 352141. Reported using DrKonqi
Duplicate of 357884? - Has the same backtrace.
(In reply to Emmanuel Pescosta from comment #1) > Duplicate of 357884? - Has the same backtrace. Yes, most likely. I found a few more reports with the same backtrace. *** This bug has been marked as a duplicate of bug 353462 ***