Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20787 - [pcmanfm] crash while type a invalid path in address bar
Attached to Project:
Arch Linux
Opened by Athurg Gooth (athurg) - Thursday, 09 September 2010, 10:00 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 30 October 2010, 08:09 GMT
Opened by Athurg Gooth (athurg) - Thursday, 09 September 2010, 10:00 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 30 October 2010, 08:09 GMT
|
DetailsDescription:
when input a invalid path(such as '//usr/' '/usr//') into address bar of pcmanfm, it will crash. Additional info: * package version(s) 0.9.7-1 Steps to reproduce: open pcmanfm type a invalid path (such as '//usr/') in 'address bar' |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Saturday, 30 October 2010, 08:09 GMT
Reason for closing: Fixed
Additional comments about closing: pcmanfm 0.9.8-1
Saturday, 30 October 2010, 08:09 GMT
Reason for closing: Fixed
Additional comments about closing: pcmanfm 0.9.8-1
Comment by Andrea Scarpino (BaSh) -
Thursday, 09 September 2010, 10:47 GMT
- Field changed: Summary (pcmanfm crash while type a invalid path in address bar → [pcmanfm] crash while type a invalid path in address bar)
- Field changed: Status (Unconfirmed → Assigned)
- Field changed: Category (Packages: Extra → Upstream Bugs)
- Field changed: Architecture (i686 → All)
- Field changed: Severity (Critical → Medium)
- Task assigned to Jürgen Hötzel (juergen)
upstream: http://sourceforge.net/tracker/index.php?func=detail&aid=3028981&group_id=156956&atid=801864
Comment by Mihai Militaru (akephalos) -
Friday, 29 October 2010, 20:56 GMT
I request closure since this error can't be reproduced at me with the last version (0.9.8-1) - seems to be fixed.