WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
23527
Update breaks Webkit
https://bugs.webkit.org/show_bug.cgi?id=23527
Summary
Update breaks Webkit
Juan Taylor
Reported
2009-01-25 02:53:28 PST
This morning I was prompted by Webkit to install a new update. I forget what the build number was on the dialog. I accepted. After that when I launched Webkit a message was displayed: "Unable to launch Safari Webkit is located at a path containing an unsupported character. Please move Webkit to a different location and try again." I checked, but webkit was still in my "Applications" folder. I downloaded the dmg file manually from the webkit site using Firefox and replaced my current app. Now it works again. Not sure if the next auto update will break it again.
Attachments
For bug 23527
(21.17 KB, image/jpeg)
2009-01-25 02:54 PST
,
Juan Taylor
no flags
Details
this is what happens to the webkit icon after the error
(6.88 KB, image/png)
2009-01-25 04:36 PST
,
Juan Taylor
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Juan Taylor
Comment 1
2009-01-25 02:54:59 PST
Created
attachment 27011
[details]
For
bug 23527
Mark Rowe (bdash)
Comment 2
2009-01-25 03:05:16 PST
That error will be displayed if the path where your copy of WebKit lives contains a ":" character. The ":" character is used as a delimiter so cannot appear in the path to the WebKit application. This is not new behaviour, it has been present in the nightly builds since day zero.
Juan Taylor
Comment 3
2009-01-25 04:36:01 PST
Created
attachment 27017
[details]
this is what happens to the webkit icon after the error
Mark Rowe (bdash)
Comment 4
2009-01-25 04:39:42 PST
I don't know what you've done, but that's clearly not the WebKit icon. I suspect you've somehow copied another application over WebKit in some manner.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug