Bug 414482 is now fixed, but when I actually create a file on the samba share, Dolphin instantly crashes. I don't know how I missed this in the review for the patch that fixed that bug, or if anything changed since then. But it is 100% reproducible for me. Everything from git master. Here's the not-very-useful-looking backtrace: #0 doActivate<false> (sender=0xdd0a40, signal_index=17, argv=0x0) at kernel/qobject.h:132 #1 0x00007ffff5b5921f in QMetaObject::activate (sender=sender@entry=0xdd0a40, m=m@entry=0x7ffff65457e0 <QWindow::staticMetaObject>, local_signal_index=local_signal_index@entry=14, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #2 0x00007ffff5feead3 in QWindow::activeChanged (this=this@entry=0xdd0a40) at .moc/moc_qwindow.cpp:811 #3 0x00007ffff5fe7c1c in QGuiApplicationPrivate::processActivatedEvent ( e=<optimized out>) at kernel/qguiapplication.cpp:2450 #4 0x00007ffff5feca9c in QGuiApplicationPrivate::processWindowSystemEvent ( e=e@entry=0xd5f420) at kernel/qguiapplication.cpp:1962 #5 0x00007ffff5fc653b in QWindowSystemInterface::sendWindowSystemEvents ( flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1163 #6 0x00007ffff10b4a6a in xcbSourceDispatch (source=source@entry=0x519b70) at qxcbeventdispatcher.cpp:105 #7 0x00007ffff3f06ff8 in g_main_dispatch (context=0x7fffec005000) at ../glib/gmain.c:3179 #8 g_main_context_dispatch (context=context@entry=0x7fffec005000) at ../glib/gmain.c:3844 #9 0x00007ffff3f07380 in g_main_context_iterate (context=context@entry=0x7fffec005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:3917 #10 0x00007ffff3f0740f in g_main_context_iteration (context=0x7fffec005000, may_block=may_block@entry=1) at ../glib/gmain.c:3978 #11 0x00007ffff5b80c4e in QEventDispatcherGlib::processEvents (this=0x529c30, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #12 0x00007ffff5b28bfb in QEventLoop::exec (this=this@entry=0x7fffffffd520, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #13 0x00007ffff5b309d2 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #14 0x00007ffff5fdf56c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1866 #15 0x00007ffff66dbc25 in QApplication::exec () at kernel/qapplication.cpp:2824 #16 0x00007ffff7f276ee in kdemain (argc=<optimized out>, argv=<optimized out>) at /home/nate/kde/src/dolphin/src/main.cpp:188 #17 0x00007ffff539ae0b in __libc_start_main (main=0x401040 <main>, argc=1, argv=0x7fffffffd768, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd758) at ../csu/libc-start.c:308 #18 0x000000000040107a in _start () at ../sysdeps/x86_64/start.S:120
Cannot reproduce. I suggested to valgrind dolphin. That crash looks like memory management snafu somewhere. Specifically this looks like it's trying to call a slot and explodes while trying to figure out what to call (e.g. because the what has been deleted). A quick grep didn't yield anything of note connecting to activeChanged though :|
Created attachment 126797 [details] Dolphin valgrind log This is still 100% reproducible for me. Unfortunately, running Dolphin in valgrind causes it to crash immediately, which does not happen when I run Dolphin outside of valgrind. :/ I'm attaching the output anyway in case it's helpful.
Created attachment 126798 [details] Maybe better valgrind log Maybe this one with `--track-origins=yes --leak-check=full` is better
@Nate: the valgrind log seems to point to the dropbox plugin. Can you try to disable it?
Indeed, disabling that plugin resolves the issue. Nice catch!
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!