| Summary: | Dolphin crashes when copying files between tabs | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Angel <angelbravo> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | elvis.angelaccio, mail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 17.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | valgrind log | ||
|
Description
Angel
2018-04-18 12:12:53 UTC
Thanks for reporting this crash! The backtrace looks a bit weird to me (many threads with driver related stuff...). Does this issue only happen when dragging files between tabs? (In reply to Julian Schraner from comment #1) > Thanks for reporting this crash! The backtrace looks a bit weird to me (many > threads with driver related stuff...). Does this issue only happen when > dragging files between tabs? You are welcome...and yes. Not always, but it happens very often in this single situation, drag & drop between tabs. Dolphin is stable and it's the only noticeable bug that I could ever find. Thanks for the quick response, I edited the title to be more accurate. Even though it's not easy to fix crashes that only appear at random, we'll surely try to look into this bug. (In reply to Julian Schraner from comment #3) > Thanks for the quick response, I edited the title to be more accurate. Even > though it's not easy to fix crashes that only appear at random, we'll surely > try to look into this bug. I saw you and Elvis Angelaccio comment others bug I published here -Bugs 363131 and 364038-, it could be related? in all these cases -always from the user's perspective, I'm not computer engineer- I was basically trying to do the same thing. Hmm, actually all of these bugs might have the same root cause. I suspect that they are all duplicates of bug 368199, but I am not entirely sure... The backtraces look similar & the same action caused the crash. @Elvis, could you confirm that the three bugs Angel mentioned (this one, bug 363131 & bug 364038) are dups of bug 368199? If that would be the case, it'd be helpful to have a valgrind log available. (In reply to Julian Schraner from comment #5) > Hmm, actually all of these bugs might have the same root cause. I suspect > that they are all duplicates of bug 368199, but I am not entirely sure... > The backtraces look similar & the same action caused the crash. > @Elvis, could you confirm that the three bugs Angel mentioned (this one, bug > 363131 & bug 364038) are dups of bug 368199? > > If that would be the case, it'd be helpful to have a valgrind log available. Ok, now valgrind is installed and waiting for a crash. This one could be a duplicate of bug 368199 (even though the stacktrace is different), the other two look unrelated to me. Created attachment 113410 [details]
valgrind log
After a long time trying, I think this may be the bug log which we were waiting for.
Almost there. Please install debug symbols for dolphin and then try to get a new valgrind log. Thanks! Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. (In reply to Justin Zobel from comment #10) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. > > I have set the bug status to "needsinfo" pending your response, please > change back to "reported" or "resolved/worksforme" when you respond, thank > you. I haven't seen it again for a long time. 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! Thanks for the update; changing status. |