Summary: | zip:/ kioslave crashes konqueror when it accesses a path with "[" or "]" characters | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | David Lee <davidomundo> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
David Lee
2007-02-04 11:07:41 UTC
I think this might have something to do with konqueror escaping paths which have a protocol attached (ie: http:, ftp:, zip:). I saw that in a filename containing "]", the "]" character gets translated to "%5D" in the address bar. Perhaps this is causing trouble for the zip:/ ioslave. Look at Bug #141157. I cannot reproduce the crash. Do you have a backtrace? Sorry, I don't have a backtrace because I'm not running a debug version of konqueror. I put the wrong address in the original report. The addresses should contain the zip:/ protocol. So the one that crashes should be: zip:/any/path/with/characters[]/file.zip the one that doesn't crash: zip:/any/file/with/characters[].zip I know, I tested that exactly like that with SVN 629k. No luck. Can you check Bug #141157 and see if you get the same symptoms? I'm wondering whether it's the zip ioslave's fault, or if Konqueror's file handling got fixed. I just updated to KDE 3.5.6, and can confirm that the bug still exists. I'm in UTF-8 locale. I can't reproduce either with KDE 3.5.6. But bug 141167 is reproducible, I left a comment there. Would you please install debug symbols (or compile with them) so there's something to step on? ;) I double checked this report and still cannot reproduce. I was able to reproduce bug 141157 though. But I'll close this one. Please reopen if you are somehow able to produce a detailed backtrace of the crash. I installed Gentoo and tried it there and I could not reproduce the bug either. Either it got fixed upstream during my distribution change, or it's a Ubuntu specific bug. |