Application: krusader (2.4.0-beta3 "Single Step") KDE Platform Version: 4.14.1 Qt Version: 4.8.6 Operating System: Linux 3.16.6-200.fc20.x86_64 x86_64 Distribution: "Fedora release 20 (Heisenbug)" -- Information about the crash: - What I was doing when the application crashed: Kde apps like krusader, kate etc crash when accessing (viewing) files on samba shares. Apps started to crash when samba was upgraded to 3.6.23 (CentOS 6.6). Apps usually crash when viewing/editing php,html and simple txt files. No crash when viewing jpegs or .bak files strangely enough. To make the irony greater, kde crash reporting assistant can't login to kde bugtracking system :) The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f3ec3d618c0 (LWP 14379))] Thread 2 (Thread 0x7f3eb799f700 (LWP 14380)): #0 0x00000036b3eea71d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00000036b66495b4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f3eb0002bb0, timeout=-1, context=0x7f3eb00009a0) at gmain.c:4007 #2 g_main_context_iterate (context=context@entry=0x7f3eb00009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3708 #3 0x00000036b66496dc in g_main_context_iteration (context=0x7f3eb00009a0, may_block=1) at gmain.c:3774 #4 0x00000036bebb543e in QEventDispatcherGlib::processEvents (this=0x7f3eb00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x00000036beb8538f in QEventLoop::processEvents (this=this@entry=0x7f3eb799ecc0, flags=...) at kernel/qeventloop.cpp:149 #6 0x00000036beb856dd in QEventLoop::exec (this=this@entry=0x7f3eb799ecc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x00000036bea79e5f in QThread::exec (this=this@entry=0x29c1070) at thread/qthread.cpp:538 #8 0x00000036beb65de3 in QInotifyFileSystemWatcherEngine::run (this=0x29c1070) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x00000036bea7c69f in QThreadPrivate::start (arg=0x29c1070) at thread/qthread_unix.cpp:349 #10 0x00000036b4207ee5 in start_thread (arg=0x7f3eb799f700) at pthread_create.c:309 #11 0x00000036b3ef4b8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f3ec3d618c0 (LWP 14379)): [KCrash Handler] #6 0x00000036b3e35877 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00000036b3e36f68 in __GI_abort () at abort.c:89 #8 0x00000036b6e60dd5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x00000036b6e5ed46 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38 #10 0x00000036b6e5ed73 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48 #11 0x00000036b6e5efe9 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:125 #12 0x00000036beb858ce in QEventLoop::exec (this=this@entry=0x7fff166871f0, flags=...) at kernel/qeventloop.cpp:218 #13 0x00000036beb8ada9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00000036c1bc94dc in QApplication::exec () at kernel/qapplication.cpp:3823 #15 0x000000000044da49 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/krusader-2.4.0-beta3/krusader/main.cpp:324 Possible duplicates by query: bug 336621, bug 334929, bug 332381, bug 328903, bug 327844. Report to https://bugs.kde.org/ Reproducible: Always
The backtrace indicate an exception raised. Could you please run the application in a Konsole, and check which exception is printed before it dies?
Not ATM. This version on samba was on a development server and I had to fix it ASAP. This stoped happening after samba was upgraded to v4. This bug was confirmed on 3 workstations, two of those are fedora 20 and the third is a centos 7 ws. If I have some spare time later I will run a new centos VM and test this once more.
Please try again with Krusader 2.5 or higher.
This report is 3.5 years old, did you comment on a wrong one by mistake?
@Dragan No. In fact i wanted to point out that even though this bug wasn't addressed directly the development of Krusader and it's environment (e.g. KDE libs) moved forward. And therefore this bug is probably already fixed.
Probably. Anyway that server (and company) is long gone by now so no way to test it.