On Mon, Aug 27, 2012 at 9:11 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
In my case, vcxsrv crashes whenever I try to access the proxy settings in Chrome, see my message from back in May: https://lists.berlios.de/pipermail/x2go-dev/2012-May/003991.html
I'd be interested to know if you're using Chromium from the stock Debian Squeeze repository or if you're on Wheezy or using a totally different repository for it.
Also, could you check what happens in Chromium when you try to access the proxy settings? I'm curious if it works with Chromium, but not with Chrome.
It may be I am seeing similar crashes to you. When I said Xorg locked up, I only meant that nothing in my x2go session would respond (not only chromium, but all mouse clicks were ignored). It may very well be that VcXsrv on the client is crashing, since I was able to recover by quitting and restarting x2go. I think I may even have had to use Windows task manager to kill VcXsrv, but I don't remember (it has been a while since it last happened).
I am using the Chromium x86_64 package from the Archlinux "extra" repository. Currently it is at version 21.0.1180.81-2.
I never use proxy settings, so I was unsure what exactly you wanted me to test. I just accessed Chromium:
Settings...Network...Change proxy settings...
and I was shown this message in a new tab:
"When running Chromium under a supported desktop environment, the system proxy settings will be used. However, either your system is not supported or there was a problem launching your system configuration.
But you can still configure via the command line. Please see man chromium for more information on flags and environment variables."