Summary: | Dolphin crahes when i open sync folder from MEGASync Client | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Till Seifert <till.seifert> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | elvis.angelaccio, kfm-devel |
Priority: | NOR | Keywords: | drkonqi |
Version: | 19.12.3 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Till Seifert
2020-03-18 16:09:34 UTC
Since you can reproduce the crash, please provide a valgrind log as described here: https://community.kde.org/Dolphin/FAQ/Crashes > Since you can reproduce the crash, please provide a valgrind log as
> described here: https://community.kde.org/Dolphin/FAQ/Crashes
i prepared that, but since MEGA is starting Dolphin I can not manually start it with Valgrind.
Is there a way i can "capture" the exact command line that MEGA is using to start dolphin? So i can reproduce from Konsole.
Note: my running Dolphin windows are not affected. It seems to start a new instance which immediately crashes.
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! (In reply to Justin Zobel from comment #3) > 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? I just tried it with 22.08.1 and the current MEGA client and it did not crash! 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! |