| Summary: | Dolphin crashed when opening file properties of non UTF8 file. | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | andrepontes |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | andrepontes, arjunak234, frank78ac, markhkamp, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.14.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=343887 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
file for testing
valgrind output valgrind again.. valgrind |
||
|
Description
andrepontes
2014-12-12 20:29:29 UTC
Created attachment 89944 [details]
file for testing
this file has encoding "ANSI Latin 1" encoding - it crashes with this file.
Thanks for the bug report, but I cannot reproduce the problem. I'm not sure if the encoding is preserved when you attach the file here. Maybe putting the file into an archive and uploading that would be better? I'm not sure. In any case, you might want to install debugging packages to get a more detailed backtrace, and ideally use Valgrind to obtan additional information which might be useful. See https://community.kde.org/Dolphin/FAQ/Crashes for details. Thanks for your help! I'll reassign to KIO - according to the backtrace, the problem might be there, or in kdecore. Created attachment 89955 [details]
valgrind output
Thanks for the quick response, but could you please try to install debugging packages and then create a new Valgrind log? See https://community.kde.org/Dolphin/FAQ/Crashes https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Thanks. Created attachment 89957 [details]
valgrind again..
I've already installed all kdelib*debug*, and dolphin*debug*, what are the packages that I am missing ?
(using opensuse 13.2)
Opensuse has some info about the repositories which have debugging packages: https://en.opensuse.org/Package_repositories#Debug Maybe you have to enable some of these in the package manager. It seems that at least some parts of kdelibs do not have debugging info yet in your Valgrind log. In particular KIO would be interesting. I don't know if there is a separate debuginfo package for that, or if it is part of a kdelibs-debuginfo package. Created attachment 89984 [details]
valgrind
debug info after installing kio*debug* packages.
This could be related to bug 340657, if ksycoca uses memory mappings. Were you using BTRFS filesystem? Yes - I'm using btrfs. *** Bug 343887 has been marked as a duplicate of this bug. *** I'm also on 64-bit openSUSE 13.2 with btrfs and I had Dolphin crash on right-click -> Properties on another file type. That bug (bug 343887) was closed as a duplicate of this bug, but I can't reproduce this bug. Can you please describe how, in Kwrite or another text editor, to make the file that causes this crash? I tried saving as encoding "cp 1252" per somewhat confusing search results for "ANSI Latin 1", but Dolphin happily displays the properties without error or crash. As for bug 340657, the openSUSE bug report it mentions says that it should be fixed as of kernel 3.16.7, which my machine is running. However, bug 343571 (the most recent duplicate of 340657, and yet another related bug which I can't reproduce) still recommends updating to kernel 3.17.3 or above. I can try updating to a newer kernel to see if it fixes things, but first I need to be able to reproduce an open bug. I don't have the machine where the problem was occuring. but I also could not reproduce it locally, currently using 3.16.7-7-desktop.thx. (In reply to andrepontes from comment #12) > I don't have the machine where the problem was occuring. but I also could > not reproduce it locally, currently using 3.16.7-7-desktop.thx. Hmm. Can you try downloading the .amr file attached to bug 343887 and see if right-click -> properties on that file causes a crash in Dolphin? If so, then maybe that would provide some insight on how to reproduce this bug. (In reply to Mark Haferkamp from comment #13) > Hmm. Can you try downloading the .amr file attached to bug 343887 and see if > right-click -> properties on that file causes a crash in Dolphin? Never mind. It turns out the first 6 bytes of that file are sufficient to crash Dolphin when opening Properties, and those bytes are in the ASCII range of UTF-8 (representing "#!AMR\n"), so that bug is almost certainly different from this one. Crash in old unmaintained KF4 software with no duplicates from any Qt5/KF5 versions. If anyone can still reproduce using recent KF5 versions of KIO and Dolphin, please file a new bug. Thanks! |