Arch Linux

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!
Tasklist

FS#13907 - libwebkit 1.1.0 segfaults

Attached to Project: Arch Linux
Opened by Alexandre Bique (babali) - Saturday, 21 March 2009, 20:50 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 March 2009, 10:05 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Use a webkit browser, for example midori and enter the '/' url.
We should update libwebkit to 1.1.3 at least.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 March 2009, 10:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  libwebkit-1.1.3-1
Comment by Alessandro Doro (adoroo) - Saturday, 21 March 2009, 21:36 GMT
Arora works fine.
Midori crashes with file URLs
/
file://
file:///
Comment by Alessandro Doro (adoroo) - Saturday, 21 March 2009, 21:41 GMT
... if the URL points to a directory, not a regular file.
Comment by christopher rogers (godane) - Sunday, 22 March 2009, 00:48 GMT
This is maybe fixed with libwebkit 1.1.3-1 and midori 0.1.4-1 from testing.

Midori doesn't crash with file URLs
/
file://
file:///

PS / goes to file:/// in midori 0.1.4-1. I believe thats normal but I thought I should tell you.
Comment by Alessandro Doro (adoroo) - Sunday, 22 March 2009, 02:58 GMT
Sorry, arora-git isn't build against libwebkit (and with "works fine" I meant "doesn't crash"; it isn't able to show directory listings).

PS2: / goes to file:/// just like www.archlinux.org goes to http://www.archlinux.org; it is normal though some browser prefers file://localhost/.
Comment by JM (fijam) - Sunday, 22 March 2009, 09:42 GMT
confirming that it is fixed in 1.1.3-1

Loading...