| Summary: | OpenSuse 42.1 plasma desktop crash | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | RichT <rtpema> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | 129492de, bhush94, dad1968, dutchgigalo, faure, iaivier, irisglp, mikebrooks44, nothreek, plasma-bugs, shakti.rg, staudth, sudhir, wbauer1, xa.kasprzyk |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.4.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kjobwidgets/e984dab0a6cd9541ae178c104f0228ae264284a6 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
KIO versions
valgrind log when trying to reproduce the crash in dolphin valgrind log with "--num-callers=50" |
||
|
Description
RichT
2015-12-05 19:39:23 UTC
getting the same when creating a new shortcut to program/file, no backtrace..... Can you give full steps to reproduce the problem. What exactly were you dragging? and from and to where? I right-clicked on desktop and picked 'create new' -> 'link to application'. The dlg appeared but had 2 tabs - no tab to enter a program name. If I cancel, then its OK. If I said OK, to see what happened, that's when crash occurred. Thanks Can you tell me what verison of frameworks-kio you have? Same problem. KIO Version: 5.16.0-3.2 / x86_64 Created attachment 96126 [details]
KIO versions
hopefully this is what you were asking for
*** Bug 357172 has been marked as a duplicate of this bug. *** *** Bug 357094 has been marked as a duplicate of this bug. *** *** Bug 358182 has been marked as a duplicate of this bug. *** *** Bug 358196 has been marked as a duplicate of this bug. *** *** Bug 358825 has been marked as a duplicate of this bug. *** I don't think this is a specific problem in plasmashell. Dolphin crashes as well when creating a new "link to application", with a different backtrace though of course. Wolfgang, can you get me a valgrind trace of the crash in dolphin? Created attachment 97054 [details] valgrind log when trying to reproduce the crash in dolphin (In reply to David Edmundson from comment #14) > Wolfgang, can you get me a valgrind trace of the crash in dolphin? Hm, dolphin did not crash when running it in valgrind. I attached the log anyway, and hope it helps. Note that the crash normally happens when "Create New"->"Link to application" fails, immediately after you press "OK" in the error dialog. (In reply to Wolfgang Bauer from comment #15) > Hm, dolphin did not crash when running it in valgrind. PS: the crash is reliably reproducible otherwise. I now let drkonqi search for duplicates and got 11 results, from dolphin *and* systemsettings... And now that I look again at the backtrace in comment#0, it is actually similar: Thread 1 (Thread 0x7f3d4e7b37c0 (LWP 26632)): [KCrash Handler] #5 0x00007f3d483aefab 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 #6 0x00007f3d4c6b5724 in KDialogJobUiDelegate::Private::next() () at /usr/lib64/libKF5JobWidgets.so.5 #7 0x00007f3d483cf4f6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #8 0x00007f3d49517eec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #9 0x00007f3d4951cd38 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #10 0x00007f3d4839e935 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #11 0x00007f3d483a0af7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #12 0x00007f3d483f6303 in () at /usr/lib64/libQt5Core.so.5 #13 0x00007f3d43374a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #14 0x00007f3d43374c48 in () at /usr/lib64/libglib-2.0.so.0 #15 0x00007f3d43374cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #16 0x00007f3d483f577c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #17 0x00007f3d4839c803 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #18 0x00007f3d483a4396 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #19 0x00007f3d4e3d13f7 in kdemain(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/dolphin-15.12.1/src/main.cpp:150 #20 0x00007f3d4dfebb05 in __libc_start_main () at /lib64/libc.so.6 #21 0x00000000004007be in _start () at ../sysdeps/x86_64/start.S:122 Valgrind trace is useful And I can definitely come up with two different guards that would fix this from that, but neither /should/ be needed. but can I be a pain and ask you to re-run with valgrind --num-callers=50 so I can see the full trace of the initial delete. (I did try myself, but I don't get the problem here) Created attachment 97058 [details] valgrind log with "--num-callers=50" (In reply to David Edmundson from comment #17) > but can I be a pain and ask you to re-run with > valgrind --num-callers=50 > > so I can see the full trace of the initial delete. Attached. > (I did try myself, but I don't get the problem here) The crash happens when reproducing Bug#356198. If you have the corresponding template files in /usr/share/templates/, that doesn't happen. I had to remove that folder to even see that problem, as I have a git version of kde-baseapps installed that still has those files. Thanks so much. https://git.reviewboard.kde.org/r/126999/ if you're able to try patches. (In reply to David Edmundson from comment #20) > https://git.reviewboard.kde.org/r/126999/ if you're able to try patches. Yes, it seems to fix the crash. With that patch I am not able to reproduce it with neither plasmashell nor dolphin, while it did occur every single time without it. *** Bug 359105 has been marked as a duplicate of this bug. *** Git commit e984dab0a6cd9541ae178c104f0228ae264284a6 by David Edmundson. Committed on 08/02/2016 at 15:13. Pushed by davidedmundson into branch 'master'. Fix crash in KJob dialogs. Guard "this" being deleted whilst running new eventloop KMessageBox spawns a new event loop, during which the parent kjob can be completed and deleted, deleting the UIDelegate with it. Related: bug 356964, bug 355052, bug 355525, bug 353462, bug 358954, bug 346215 REVIEW: 126999 M +9 -0 src/kdialogjobuidelegate.cpp http://commits.kde.org/kjobwidgets/e984dab0a6cd9541ae178c104f0228ae264284a6 Fix included in KF 5.19 *** Bug 359391 has been marked as a duplicate of this bug. *** *** Bug 359623 has been marked as a duplicate of this bug. *** *** Bug 359622 has been marked as a duplicate of this bug. *** *** Bug 362320 has been marked as a duplicate of this bug. *** *** Bug 386230 has been marked as a duplicate of this bug. *** |