Hi List, hi Alex & Mike,
we're seeing issues with Flash and Iceweasel when x2go or nx are part of the equation.
A thorough description including videos showing the issue is available here: http://ionic.de/~sbaur/ (Hosting space kindly provided by Mihai Moldovan)
Please fix this as soon as possible, running a 3.5 or 3.6 Firefox simply isn't safe any more, we need to be able to run at least the ESR version.
This issue already appeared back in Mid-April and hasn't been fixed since: https://lists.berlios.de/pipermail/x2go-dev/2012-April/003861.html
Others saw it too... https://lists.berlios.de/pipermail/x2go-dev/2012-April/003924.html
...and were also able to confirm that it doesn't occur when x2go/nx is not involved: https://lists.berlios.de/pipermail/x2go-dev/2012-May/003945.html
And a few days ago, an ew report of the same issue cropped up: https://lists.berlios.de/pipermail/x2go-dev/2012-August/004152.html
If a sponsorship is required to prioritize the issue, please publicly name your price, so possible donators/sponsors can join forces.
If access to test systems is required, that could be arranged, too.
-Stefan
On Thu, Aug 2, 2012 at 8:30 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
we're seeing issues with Flash and Iceweasel when x2go or nx are part of the equation.
A thorough description including videos showing the issue is available here: http://ionic.de/~sbaur/ (Hosting space kindly provided by Mihai Moldovan)
I switched from Firefox to Chromium months ago because of this issue. But I was browsing nomachines website, and they have a workaround that solved the problem for me in Firefox.
Specifically, I opened the Firefox configuration settings (about:config), and then added a new string with name "plugins.force.wmode" and value "transparent". That did the trick for me.
Here is the nomachine workaround:
http://www.nomachine.com/tr/view_notes.php?commid=180&id=TR04J02675
It has been reported that two more workarounds are possible:
adding the "render=0" and "defer=2" options to the AgentExtraOptions key in the node.cfg configuration file (this could affect the overall performance);
adding the "plugins.force.wmode = transparent" or the "plugins.force.wmode = opaque" option to firefox in the "about:config" URL.
Am 26.08.2012 21:07, schrieb John Williams:
I switched from Firefox to Chromium months ago because of this issue.
Interesting. I tried Chrome and have been seeing other issues (X-Server crashing) when using the Windows X2Go Client, so that didn't seem like a solution to me. Are you using the Windows Client?
But I was browsing nomachines website, and they have a workaround that solved the problem for me in Firefox.
With the link you provided, I found http://www.nomachine.com/tr/view.php?id=TR04J02675 - that page doesn't seem to offer a workaround, but links to the page you mentioned.
What's confusing me here is that that page says "two *more* workarounds", which means there should be three.
Any idea what number three might be?
Anyways, thanks for the hint, I'll try the about:config change. Sounds like something that might even be added into /etc/iceweasel/pref/iceweasel.js so it (positively) affects all users without having to mess with their individual configuration files.
-Stefan
Hello,
The about:config change works at least for Flash player. If you use Ubuntu/Firefox you can make the fix global by putting in /etc/firefox/syspref.js the following:
// prevent flash player windows from overlapping other tabs pref("plugins.force.wmode", "opaque");
Now I don't know the difference between "opaque" or "transparent" and I haven't spent much today to find it out (first google hits didn't help).
What I did notice is that this fix doesn't prevent adobe acrobat reader from still having a similar behaviour but I can live without it as it's a horrible browser plugin and there are open source alternatives as long as you don't need pdf forms in the browser.
-----Original message----- From:Stefan Baur <newsgroups.mail2@stefanbaur.de> Sent:Mon 27-08-2012 09:18 Subject:Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel To:x2go-dev@lists.berlios.de; Am 26.08.2012 21:07, schrieb John Williams:
I switched from Firefox to Chromium months ago because of this issue.
Interesting. I tried Chrome and have been seeing other issues (X-Server crashing) when using the Windows X2Go Client, so that didn't seem like a solution to me. Are you using the Windows Client?
But I was browsing nomachines website, and they have a workaround that solved the problem for me in Firefox.
With the link you provided, I found http://www.nomachine.com/tr/view.php?id=TR04J02675 - that page doesn't seem to offer a workaround, but links to the page you mentioned.
What's confusing me here is that that page says "two *more* workarounds", which means there should be three.
Any idea what number three might be?
Anyways, thanks for the hint, I'll try the about:config change. Sounds like something that might even be added into /etc/iceweasel/pref/iceweasel.js so it (positively) affects all users without having to mess with their individual configuration files.
-Stefan
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Am 27.08.2012 09:14, schrieb Stefan Baur:
Anyways, thanks for the hint, I'll try the about:config change. Sounds like something that might even be added into /etc/iceweasel/pref/iceweasel.js so it (positively) affects all users without having to mess with their individual configuration files.
Just played around with this for a bit and it seems to work:
grep -q 'lockPref("plugins.force.wmode", "transparent");'
/etc/iceweasel/pref/iceweasel.js ||
echo 'lockPref("plugins.force.wmode", "transparent");' \
/etc/iceweasel/pref/iceweasel.js
More info regarding this parameter can be found here: http://helpx.adobe.com/flash/kb/flash-object-embed-tag-attributes.html
-Stefan
On Mon, Aug 27, 2012 at 12:14 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 26.08.2012 21:07, schrieb John Williams:
Interesting. I tried Chrome and have been seeing other issues (X-Server crashing) when using the Windows X2Go Client, so that didn't seem like a solution to me. Are you using the Windows Client?
Yes, Windows client 3.99.2.2.
I am using Chromium on linux, not Chrome. I have occasionally had Chromium crash and lockup Xorg, but not very often. I assumed that was just a Chromium issue (it doesn't receive a lot of testing), but I suppose it could be x2go related.
With the link you provided, I found http://www.nomachine.com/tr/view.php?id=TR04J02675 - that page doesn't seem to offer a workaround, but links to the page you mentioned.
What's confusing me here is that that page says "two *more* workarounds", which means there should be three.
Any idea what number three might be?
I saw that too. I can only guess that it is the way their bug tracking system works, but they are not using it correctly. I don't think there is a third workaround. I could be wrong.
Am 27.08.2012 17:32, schrieb John Williams:
On Mon, Aug 27, 2012 at 12:14 AM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
Am 26.08.2012 21:07, schrieb John Williams:
Interesting. I tried Chrome and have been seeing other issues (X-Server crashing) when using the Windows X2Go Client, so that didn't seem like a solution to me. Are you using the Windows Client?
Yes, Windows client 3.99.2.2.
I am using Chromium on linux, not Chrome. I have occasionally had Chromium crash and lockup Xorg, but not very often. I assumed that was just a Chromium issue (it doesn't receive a lot of testing), but I suppose it could be x2go related.
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.
-Stefan
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."
Am 27.08.2012 18:21, schrieb John Williams:
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).
No, not the same, see below...
I am using the Chromium x86_64 package from the Archlinux "extra" repository. Currently it is at version 21.0.1180.81-2.
Hmm. Debian Wheezy has Chromium-Browser 20.0.1132.57. I might try that soon.
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...
Indeed that is what I meant, only that back when I last tried it, Chrome had an option like "advanced settings" that you had to click before the change proxy settings button becomes available.
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."
And this is the tab I only get to see after killing all x2go-related processes on the client and reconnecting, as in the very moment when I click the button, vcxsrv goes "zap" on me and dies with the error message shown in my message from back in May.
Well, since I have one box running Wheezy, I guess I'm going to give both the latest Chrome and Wheezy's Chromium-Browser a try soon.
Again, thanks for the information you gathered and shared.
-Stefan
Am 27.08.2012 18:52, schrieb Stefan Baur:
Well, since I have one box running Wheezy, I guess I'm going to give both the latest Chrome and Wheezy's Chromium-Browser a try soon.
And here are the results: Both chromium-browser from Wheezy as well as the latest Google Chrome crash as soon as I click on the "close tab" icon on the first of the two tabs that are shown directly after installation. To be precise, "crash" means vcxsrv.exe dies, not Chromium/Chrome. The session itself remains active.
I'm using X2Go Client for Windows, 3.99.2.2 on Windows 7, 32-Bit.
Server side is Debian Wheezy, obviously. The x2go packages are being pulled from: # X2go Repository deb http://packages.x2go.org/debian wheezy main # X2go Repository (sources) deb-src http://packages.x2go.org/debian wheezy main
-Stefan
On Mon, Aug 27, 2012 at 1:22 PM, Stefan Baur <newsgroups.mail2@stefanbaur.de> wrote:
And here are the results: Both chromium-browser from Wheezy as well as the latest Google Chrome crash as soon as I click on the "close tab" icon on the first of the two tabs that are shown directly after installation. To be precise, "crash" means vcxsrv.exe dies, not Chromium/Chrome. The session itself remains active.
I'm using X2Go Client for Windows, 3.99.2.2 on Windows 7, 32-Bit.
Server side is Debian Wheezy, obviously. The x2go packages are being pulled
I was wondering what differences between our systems might account for yours crashing and mine not. Here are some possibilities:
I'm using windows 7 64-bit for client 3.99.2.2
It is possible we have different chromium versions, I have 21.0.1180.81-2 (I did not see you specify your version)
I have cairo and lib32-cairo version 1.10.2 , maybe you have a newer version?
something else?
-
Alexandru Ionica -
John Williams -
Stefan Baur