Summary: | dolphin crash with SIGABRT with preview and details/column view selected | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Rich Lott <rl6> |
Component: | general | Assignee: | Peter Penz <peter.penz19> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | frank78ac |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Rich Lott
2008-11-12 18:52:00 UTC
Thanks for the bug report. Does it really crash in any folder for you? The backtrace looks very much like the one of bug 170547 (fixed in KDE 4.1.3), and this crash occurs if an image with a width that differs very much from the height is in the directory (e.g., 4x500 pixels). Could you check if this is also the case in the directories where you get crashes? Thanks! Yeah, I think you're probably right. Certainly I can confirm that bug is alive in my version of dolphin! I think the confusion (which may help?) is that if ~/badImage.gif exists then dolphin also crashed trying to view ~/emptyDirectory/ But I cannot now get this to be reproducable. Anyway, happy for you to close this. BTW: Any idea when kde4.1.3 will be out in http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu ? (sorry, but don't know where else to ask) OK, I'll close this then because it looks like a duplicate. Please file a new report if you find any problems in KDE 4.1.3 or later. (In reply to comment #2) > Anyway, happy for you to close this. BTW: Any idea when kde4.1.3 will be out in > http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu ? (sorry, but don't know > where else to ask) This repository is probably for Kubuntu 8.04, right? I don't know, but maybe they do not update it any more because Kubuntu 8.10 is the current version? In this version, you can update to KDE 4.1.3 by enabling "Unsupported updates", see http://www.kubuntu.org/news/kde-4.1.3 To get more information, you might want to ask on some Kubuntu mailing list or IRC channel. *** This bug has been marked as a duplicate of bug 170547 *** |