Summary: | Dolphin Crashes in UpdateItemStatesThread::run() After opening a *.heic Image in Dropbox | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Samuel Rüegger <samuel> |
Component: | plugins: dropbox | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kfm-devel, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 20.12.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Samuel Rüegger
2021-03-25 17:08:12 UTC
Crash is in versioncontrol/updateitemstatesthread.cpp:41, which has this: const KVersionControlPlugin::ItemVersion version = m_plugin->itemVersion(item); Is this image in a git repo or another kind of source control system? Do you have dolphin's source control integration plugin installed? 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! Sorry for my late Response. The Image was not in a GIT Folder. But in a Dropbox Sync Folder with Running Dropbox Client and installed Dolphin Dropbox Plugin. I'm not sure if Dropbox is using Git or some form of version control system. Ah, it's probably using the same versioning code for dropbox, which also does versioning. Could you attach the file, or any HEIC file that can be used to reproduce the crash? This time I respond faster ;) I can't attach the image, but would have to edit it as it is around 48MB. But just noticed that the problem no longer occurs. When I open the image now, the image opens and Dolphin does not crash. Wow that's a big image. Maybe something deeper in the stack fixed this. Let's re-open if it happens again. |