Dear x2go-user,
I bought a big 2560x1440 screen (big in my world). Remote system have a 1920x1200 screen. I tried to go full screen but noticed that I can't change the remote desktop resolution to more than 1920x1200. So I can't really go full screen. Is there something I haven't noticed? Where does that limit come from? Is it really the size of the remote physical screen or just coincidentally the same geometry?
Now, that I'm practically forced to work in a window, I'm really missing a feature like there is in VirtualBox: You can grab mouse and keyboard into the virtual desktop. I'm mostly missing ALT-TAB functionality inside the remote desktop window. I wish that some day someone have the time and interest to code such a feature.
Despite of those little annoyances X2Go have served me very nicely quite a long time now - thanks.
--
Timo
Probably I should have told that my client system is
Ubuntu 12.04 GNOME3 Classic (no effects) X2Go Client V. 4.0.1.1
and the remote is
Linux Mint 12 x2goagent 2:3.5.0.20-0~340~oneiric1 GNOME3 (Command: gnome-session --session=gnome-fallback)
Is it the remote system's GNOME3 that is the culprit here? I didn't have resolution problems when my local screen was 1680x1050.
--
Timo
Hi Timo,
On Fr 27 Sep 2013 12:56:12 CEST, Timo wrote:
Probably I should have told that my client system is
Ubuntu 12.04 GNOME3 Classic (no effects) X2Go Client V. 4.0.1.1
and the remote is
Linux Mint 12
Linux Mint with X2Go is not a good idea. See [1, 2].
x2goagent 2:3.5.0.20-0~340~oneiric1 GNOME3 (Command: gnome-session --session=gnome-fallback)
GNOME3 xrandr is broken with X2Go. See [3].
Is it the remote system's GNOME3 that is the culprit here? I didn't
have resolution problems when my local screen was 1680x1050.
[1] http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=287 [2] https://bugs.launchpad.net/linuxmint/+bug/1213435 [3] http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=42
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 27.09.2013 14:02, Mike Gabriel wrote:
On Fr 27 Sep 2013 12:56:12 CEST, Timo wrote:
Linux Mint 12
Linux Mint with X2Go is not a good idea. See [1, 2].
Thanks for the pointers. Good to know but seems not to be an issue in my system. The 'xhost +' call seems to be absent. My system might be too old.
GNOME3 (Command: gnome-session --session=gnome-fallback)
GNOME3 xrandr is broken with X2Go. See [3].
Yes, I have read about that but this is a little different, I think. I have noticed that resizing does not work as expected but I have got along by changing resolution in System Settings -> Displays. But now there is not big enough geometry to go full screen.
I tried XFCE and yes, resizing works and I can go full screen alright. Interestingly, what I'm used to do with GNOME doesn't work with XFCE. If I change resolutions in Settings-> Display, the size of the X2Go window changes but the size of the XFCE desktop does not.
In display settings XFCE shows 2560x1440. Why GNOME settings doesn't?
[1] http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=287 [2] https://bugs.launchpad.net/linuxmint/+bug/1213435 [3] http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=42
--
Timo
On 27/09/2013 20:56, Timo wrote:
Yes, I have read about that but this is a little different, I think. I have noticed that resizing does not work as expected but I have got along by changing resolution in System Settings -> Displays. But now there is not big enough geometry to go full screen.
Use 'cvt' or 'gtf' to compute en new Modeline for X11
Feed 'xrandr' with it xrandr --newmode <MODE-NAME> <MODELINE> xrandr --addmode "default" <MODE-NAME>
Edit ~/.config/monitors.xml Look at <output name="default"> then change <width> , <height> and
<rate> with values of your new ModelineThen ask gnome-settings-daemon to apply changes: dbus-send --session --print-reply --dest=org.gnome.SettingsDaemon /org/gnome/SettingsDaemon/XRANDR org.gnome.SettingsDaemon.XRANDR_2.ApplyConfiguration int64:0 int64:0
Scrip it, or forget gnome ;-)
Regards Christophe
Hi Christophe,
On Mo 30 Sep 2013 09:16:07 CEST, Christophe Lohr wrote:
On 27/09/2013 20:56, Timo wrote:
Yes, I have read about that but this is a little different, I
think. I have noticed that resizing does not work as expected but I
have got along by changing resolution in System Settings ->
Displays. But now there is not big enough geometry to go full screen.
Use 'cvt' or 'gtf' to compute en new Modeline for X11
Feed 'xrandr' with it xrandr --newmode <MODE-NAME> <MODELINE> xrandr --addmode "default" <MODE-NAME>
Edit ~/.config/monitors.xml Look at <output name="default"> then change <width> , <height>
and <rate> with values of your new ModelineThen ask gnome-settings-daemon to apply changes: dbus-send --session --print-reply --dest=org.gnome.SettingsDaemon
/org/gnome/SettingsDaemon/XRANDR
org.gnome.SettingsDaemon.XRANDR_2.ApplyConfiguration int64:0 int64:0Scrip it, or forget gnome ;-)
I forwarded the above message to issue #42 [1] in X2Go BTS.
Thanks for sharing! Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 30.09.2013 10:16, Christophe Lohr wrote:
- Use 'cvt' or 'gtf' to compute en new Modeline for X11 ...
Okay, that is extreme magic. I'll try it when I next time stumble into the problem. Thanks.
- Scrip it, or forget gnome ;-)
But if I had gave in too quickly with gnome, I wouldn't have learned that nice piece of magic. The ideas of it probably proves to be useful in other occasions too.
--
Timo
Hi, Attached is a shell script that does the job (more or less) (note: install 'xmlstarlet' first) I hope it can help until the gnome developers do better;-)
Regards Christophe
On 30/09/2013 10:29, tike64@gmail.com wrote:
- Use 'cvt' or 'gtf' to compute en new Modeline for X11 ... Okay, that is extreme magic. I'll try it when I next time stumble into
On 30.09.2013 10:16, Christophe Lohr wrote: the problem. Thanks.
- Scrip it, or forget gnome ;-) But if I had gave in too quickly with gnome, I wouldn't have learned that nice piece of magic. The ideas of it probably proves to be useful in other occasions too.
--
Timo
X2Go-User mailing list X2Go-User@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-user
On Fri, 27 Sep 2013 13:56:12 +0300 Timo <tike64@gmail.com> wrote:
Probably I should have told that my client system is
Ubuntu 12.04 GNOME3 Classic (no effects) X2Go Client V. 4.0.1.1
and the remote is
Linux Mint 12 x2goagent 2:3.5.0.20-0~340~oneiric1 GNOME3 (Command: gnome-session --session=gnome-fallback)
Is it the remote system's GNOME3 that is the culprit here? I didn't have resolution problems when my local screen was 1680x1050.
On my systems (debian squeeze) gnome doesn't like the screen-resize of x2go and simply refuses. You can work around it by manually setting the screen size through gnomes randr frontend but that doesn't help when the new session is smaller and you can't reach the menu-bar. Anyway, we are using KDE with X2Go and are very happy with that.
Have fun,
Arnold
On 27.09.2013 21:17, Arnold Krille wrote:
On my systems (debian squeeze) gnome doesn't like the screen-resize of x2go and simply refuses. You can work around it by manually setting the screen size through gnomes randr frontend...
If you mean System Settings -> Displays yes, I have used that when my client screen was 1680x1050. Now when I have 2560x1440 client screen, there is no such selection in the list. The list ends with 1920x1200.
--
Timo
On 27.09.2013 13:28, Timo wrote:
... I can't change the remote desktop resolution to more than 1920x1200...
This turned out to be only half way true. I had started the session at work (at the remote system) and now terminated it and tried again by starting a new session from home. Now I could select a correct resolution. So I suspect that when I start again a new session at work and suspend it and try to restore it at home, I will face the problem again.
This is not a major issue but I find it a little bit puzzling that the X2Go desktop size seems to be somehow dependent on physical screen size.
Resizing seems to work fine with XFCE but is there a possibility that if I start a XFCE session in 1920x1200 system, it refuses to resize bigger than that afterwards. I can't test that right now.
--
Timo
-
Arnold Krille -
Christophe Lohr -
Mike Gabriel -
tike64＠gmail.com -
Timo