Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
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
Re: [X2Go-Dev] /usr/sbin/x2gocleansessions does not properly quit
Hi Benjamin, On Mo 27 Aug 2012 02:24:02 CEST Benjamin Shadwick wrote: Is there an advantage to allowing multiple copies of the daemon to run, instead of having it do one of the following: - Either kill previous instance(s) of the daemon and replace it with a new running instance, or - Abort the start of the new instance when a previous running instance is detected? Yes, the lower solution has just appeared on my todo list. If you have time to provide a patch, feel free to deliver on. Otherwise, I will see to it during the next couple of days. Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpKBBjSlgXto.pgp Description: Digitale PGP-Unterschrift ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] /usr/sbin/x2gocleansessions does not properly quit
Hi Paul, On So 26 Aug 2012 21:51:05 CEST Paul Menzel wrote: Dear Mike, as always, thank you for your fast response! Am Sonntag, den 26.08.2012, 21:31 +0200 schrieb Mike Gabriel: On So 26 Aug 2012 15:15:40 CEST Paul Menzel wrote: > Dear X2Go folks, > > > while looking into sessions which are still active on the server after > the client was suspended and could not reconnect after resume, I noticed > that `/usr/sbin/x2gocleansessions` seems to not properly exit. It is > somehow run in background and does not exit. > > $ /usr/sbin/x2gocleansessions --help > $ echo $? > 0 > $ /usr/sbin/x2gocleansessions --version > $ echo $? > 0 > > They are still listed by `ps aux | grep x2go`. X2Go clean sessions script is a daemon script. It should be possible to execute multiple instances, but it should fork into background. There is no --help and --version available, so these optioned commands will just start another instance of the daemon. Interesting, thank you for the explanation. Is there an advantage over letting the user to decide to start in the foreground or in the background by using the ampersand »&«? The script needs root privileges on the file system and it is launched via invoke-rc.d x2goserver start It is not supposed to run with user privileges. Please read the script's Perl code for further insights. Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp4IggKaBpwf.pgp Description: Digitale PGP-Unterschrift ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] /usr/sbin/x2gocleansessions does not properly quit
Am 27.08.2012 09:39, schrieb Mike Gabriel: On Mo 27 Aug 2012 02:24:02 CEST Benjamin Shadwick wrote: - Abort the start of the new instance when a previous running instance is detected? Yes, the lower solution has just appeared on my todo list. If you have time to provide a patch, feel free to deliver on. Otherwise, I will see to it during the next couple of days. Hi Mike, das ist Bash und nicht Perl, und außerdem nicht sonderlich hübsch, aber vielleicht als Anregung... #!/bin/bash PSOUTPUT=$(ps --no-headers -C $(basename $0)) COUNT=$(echo -e "$PSOUTPUT" | wc -l) if [ "$COUNT" -gt "1" ] ; then echo "Already running." exit 1 else echo "Running..." sleep 30 echo "Done." fi Gruß Stefan ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] /usr/sbin/x2gocleansessions does not properly quit
Whoops, sorry. Not enough caffeine this morning. Am 27.08.2012 10:39, schrieb Stefan Baur: Hi Mike, das ist Bash und nicht Perl, und außerdem nicht sonderlich hübsch, aber vielleicht als Anregung... This translates to: "Hi Mike, this is Bash, not Perl, and not exactly elegant, but might serve as an inspiration. #!/bin/bash PSOUTPUT=$(ps --no-headers -C $(basename $0)) COUNT=$(echo -e "$PSOUTPUT" | wc -l) if [ "$COUNT" -gt "1" ] ; then echo "Already running." exit 1 else echo "Running..." sleep 30 echo "Done." fi -Stefan ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
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
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
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
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
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
On Mon, Aug 27, 2012 at 12:14 AM, Stefan Baur 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. ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
Am 27.08.2012 17:32, schrieb John Williams: > On Mon, Aug 27, 2012 at 12:14 AM, Stefan Baur > 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 ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
On Mon, Aug 27, 2012 at 9:11 AM, Stefan Baur 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." ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
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 ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2Go-Dev] Attention @Alex, @Mike: Urgent problem with Flash and Iceweasel
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 ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
