Summary: | Crash Dolphin after right click mouse | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | antonioramon |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | frank78ac, wbauer1 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 15.12.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | video of reported bug |
Description
antonioramon
2016-01-22 17:35:25 UTC
Thanks for the bug report. Please try to disable some context menu plugins (Services section in the Settings dialog) and check if that fixes the problem. Created attachment 96815 [details]
video of reported bug
This is a video of the bug. It happens if i select a file and even if i don't select nothing.
Please see comment 1 for information on how you can help to debug this problem. If i disable the context menu plugins "Attività " (i don't know the correspondent term used in the english version) dolphins work without crash as you can see in the first 15 seconds of the video attached in comment 2. If i enable the context menu plugins "Attività " as you can see at second 00:16 of the video attached in comment 2, when the mouse hovers over the context menu "Attività " the application crashes even though i don't click on the context menu, as you can see at the end of the video in comment 2,. The application crash anyway, whether the menu appears after you select a file, or if the menu appears without you select anything. That seems to be the same as Bug#351485 then, which has been fixed recently. We already released a kactivities5 update for Leap 42.1 with this fix. So can you confirm that dolphin doesn't crash any more even if the context menu plugin is enabled and you hover over it? Yes i confirm that after the update dolphin doesn't crash any more even if the context menu plugin is enabled and i hover over it. Thanks for the quick reply! It's good to know that it works now :-) *** This bug has been marked as a duplicate of bug 351485 *** |