[Pkg-chromium-maint] Bug#700001: Bug#704492: Bug#704492: Acknowledgement (chromium: seeing the exactly same thing :()

Cristian Ionescu-Idbohrn cristian.ionescu-idbohrn at axis.com
Sat May 4 18:08:53 UTC 2013


On Wed, 3 Apr 2013, Michael Gilbert wrote:
>
> > And assumes the WM (gnome?) magic would know about/serve all those
> > things?  Sounds insane.  Please note (#704492) that it seems to _screw
> > up my profile_ too.
> [...]
> > Can you suggest some way to attempt to find out what's really failing?
> > What log-files are most probable to show the real error?
>
> I don't respond well to unkindness,

You don't.  It's still just a package.  Nothing presonal.

> so I guess you're on your own.

Thanks anyway :/

FWIW, there seems to be (at least) 2 problems here:

1. "Your profile could not be opened correctly"
   I followed the hint here:
	http://www.fourleaftechnology.com/index.php/General/google-chrome-profile-could-not-be-opened-correctly-error.html
   and removed the Web\ Data* files
2. I'm using privoxy and run chromium (among other options) with:
	--proxy-server=localhost:8118
   * that gave me a confusing error message about not being able to
     connect to that proxy
   * changing the /etc/privoxy/config:
	listen-address localhost:8118 -> listen-address 127.0.0.1:8118
     made chromium behave;
   * looks like privoxy may be at fault here, but I didn't dig

The error message:
	Failed to get name owner. Got
	org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of
	name 'org.chromium.Mtpd': no such name
is still there, but does not seem to affect functionality.


Cheers,

-- 
Cristian



More information about the Pkg-chromium-maint mailing list