Ticket #638 (closed defect: THERE IS NO BUG STOP REOPENING)
Chromium doesn’t work in AFS
| Reported by: | andersk | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Upstream Utopia |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: | http://code.google.com/p/chromium/issues/detail?id=44606 |
Description
Apparently Chromium doesn’t work in AFS because it wants to create a socket in $HOME.
*stab*
Change History
comment:2 in reply to: ↑ 1 Changed 14 years ago by andersk
Replying to geofft:
- get Chromium to support an environment variable to tell it where to put the socket, and write a wrapper script like the one that Linerva has around elinks.
That isn’t a safe option; it will probably lead to Chromium profile corruption. It’s not even really safe for elinks, as was explained by the author.
comment:3 Changed 14 years ago by davidben
As I mentioned on Zephyr, this isn't actually the same for Chromium. The profile itself is locked via a separate file. I believe the socket currently still has a role to play, but may be possible to safely move the socket elsewhere without having to rely on your home directory being proper. I'll look into it...
comment:4 Changed 14 years ago by jdreed
The upstream bug claims this has been fixed. If we care, we should get it into Maverick. And possibly SRU'd for Lucid.
comment:5 Changed 14 years ago by davidben
It is indeed fixed, as far as I have tested. There hasn't been a stable release with the change yet (it made the M7 branch), but you can verify it with the nightlies. Looking at Omaha proxy, I believe it is also in the latest dev channel release.
But it hasn't hit even the beta channel yet, so I don't know how willing Ubuntu would be to patch things in this far ahead of schedule (or how much I would approve, as a Chromium developer :-D). M7 will probably hit the stable channel on the order of 6 weeks after M6 was released, which was September 2nd.
To document the options available to us, we could