Closed Bug 322473 Opened 19 years ago Closed 19 years ago

Opening URLs via Services-Menu does not work anymore

Categories

(Camino Graveyard :: OS Integration, defect)

Product:
Camino Graveyard
Component:
OS Integration
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: rrrrrrt, Assigned: mikepinkerton)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2 When trying to open an URL from an external Application, neither the default shortcut cmd-shift-U, nor selecting Camino > Services > Open URL in Camino works. Reproducible: Always Steps to Reproduce: 1. Open a textfile containing an URL with e.g. Textedit.app 2. Highlight the URL 3. Press cmd-shift-U Actual Results: Nothing happens. Expected Results: Camino should open the URL. There is a similar bug (322044) open, but there it works somehow at least. IIRC I noticed this bug the first time with Camino 1.0.b1.
Tomas, does it make any difference if there's an "http://" or "https://" in front of the URL? cl
This could be -getFrontmostBrowserWindow again, possibly.
(In reply to comment #1) > Tomas, does it make any difference if there's an "http://" or "https://" in > front of the URL? No, I just tried, and it doesn't make any difference.
It works for me with Camino 1.0b2 and Mac OS X 10.4.3 (by creating a URl with/without http://) I tried www.bbc.co.uk and www.google.com
I suppose there's an outside possibility it could also be some sort of LaunchServices issue, too (like the default browser bug 289020). Tomas, do you have more than one copy of Camino on your Mac?
Unfortunately it doesn't work for me when I try it without http(s):// It's the only copy of Camino I have on my harddrive too...hhm.
This is happening to me now, too. In my case, it's definitely connected to the LaunchServices issue (LS holding a stale reference to a now-gone Camino?). I've had a copy of 0.8.4 around as CaminoStable for a while, running with a separate profile for some testing using the hack smfr mentioned in another bug. This week, the service started opening 0.8.4 instead of my nightly (or in addition to, if the nightly was already open). I then deleted all copies of Camino except the nightly, and now the service refuses to work at all. Downloading a new branch nightly and replacing the existing one doesn't seem to restore things.... I also took a few of kreeger's builds for a spin in that period, so I wonder if the higher version number of the trunk is somehow also involved?
(In reply to comment #5) > I suppose there's an outside possibility it could also be some sort of > LaunchServices issue, too (like the default browser bug 289020). > > Tomas, do you have more than one copy of Camino on your Mac? Ok, I'm not surprized that installing RC1 didn't help (as I *think* that the bug is related to the LaunchServices Database). Could executing /System/Library/Frameworks/ApplicationServices.framework/\ Frameworks/LaunchServices.framework/Support/lsregister \ -kill -r -domain local -domain system -domain user help? I don't wanna mess around with my system if it's not necessary..
If the source of the problem really is the LaunchServices DB, then that could help. Unfortunately, it will also reset all sorts of document associations, "this is the first time launching this app" dialogues, and other things :-( At this point, it's only a hunch that the LaunchServices DB is the problem.
(In reply to comment #8) > /System/Library/Frameworks/ApplicationServices.framework/\ > Frameworks/LaunchServices.framework/Support/lsregister \ > -kill -r -domain local -domain system -domain user Ok, it does not seem to be related. I run the above command today (as normal user first, then as admin) and it changed nothing.
Did installing 1.0 help here? If not, try throwing Camino in the trash, emptying it, and then dragging 1.0 from the disk image anew.
(In reply to comment #11) > If not, try throwing Camino in the trash, emptying it, and then dragging 1.0 > from the disk image anew. Thanks a lot, that did the trick! Should the bug stay open or is it an Apple-related bug?
Today I feel like this is a "LaunchServices is sucky" bug ;) I should have had you look at the Console.log to see if there was anything interesting there (or should have looked myself...I just went back through my console.log and didn't see anything interesting.) This is probably ultimately the same thing as bug 289020, but for now, let's call it INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.