| Summary: | Dolphin freezes if trying to read a dubious file | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Anne Wilson <cannewilson> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | cannewilson, peter.penz19 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandriva RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Anne Wilson
2008-11-09 17:26:07 UTC
Thanks for the report. Would it be possible that you attach a small damaged file to this bug report? Does Dolphin "recover" from the freeze after some seconds or does it really crash? Also do you have the information panel open? I have some problems here - the jpg files are not small, so I've uploaded a couple of damaged ones to http://tinyurl.com/645drx together with a crash report. The problem occurs when reading these files from CD, and it took many tries to get them copied to HDD. However, when I managed it, they are quite readable (though obviously damaged) from the HDD. Dolphin freezes, and so far as I can tell does not recover at all - After a good 2 minutes it was totally frozen. On re-opening dolphin on the CD content some time later I get instant previews of the file up to and including the damaged ones - just the point at which it froze before. No further previews are shown. Today I had the Information panel open. I don't think I had discovered the Information panel when I first reported this, but I am not certain of that. I can confirm the freeze on trunk and 4.2 when using the damaged JPEGs from http://tinyurl.com/645drx, it seems to be related with the preview generator for JPEGs... Hi, kdelibs (version 4 and earlier) is no longer maintained since a few years. KDE Frameworks 5 or 6 might already have resolved this bug. If not, please re-open against the matching framework if feasible or against the application that shows the issue. We then can still dispatch it to the right Bugzilla product or component. Greetings Christoph Cullmann |