Hi Neal, hi Daniel,

On Di 24 Dez 2013 16:06:06 CET, Neal Becker wrote:

Neal Becker wrote:

...

Just trying x2go on fedora 20.

Starting a kde session, the display size is ignored. It takes the entire display. xdpyinfo reports: screen #0: dimensions: 1920x1200 pixels (423x264 millimeters) resolution: 115x115 dots per inch

The physical screen is (local X): screen #0: dimensions: 1680x1050 pixels (371x232 millimeters) resolution: 115x115 dots per inch

Found my answer (note: the x2go FAQ says to remove kscreen. This is a non- starter (would remove many other dependent packages). Here's the correct answer:

Daniel Vrátil 2013-04-29 15:06:20 UTC Hi,

unfortunately, I don't think there is a easy way to solve this.

In general, this is not a bug. Using two applications that handle display resolution is not supported, as it can lead to many unexpectable
situations and race conditions.

In your case I would suggest you disable KScreen KDED module (System
Settings -> Startup and Shutdown -> Service Manager, uncheck "KScreen 2"), since x2go handles resolution switches for you and only use the KScreen KCM to manually change output settings (rotation, enabling/disabling outputs etc).

@Daniel: thanks for providing this piece of information!!!

I updated the FAQ item in the wiki...

http://wiki.x2go.org/doku.php/doc:faq:start#ubuntu_s_and_fedora_s_kde_won_t_...

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...

Roderick Johnstone wrote:

Neal

I fought this for a while. Its the kscreen daemon thats resizing the desktop. Go into system settings / startup and shutdown / service manager and uncheck the kscreen daemon. That fixed it for me. There is an issue at bugs.kde.org for it.

Roderick

PS Now I'm fighting wrong keyboard mappings (see my post to the Fedora kde list). I managed to get x2go to set the correct type and layout but I think kde is overriding it. I got this all working in the beta, but its broken again in the F20 release.

I did notice this in the x2go log, maybe related?

nxagentXkbGetRules: WARNING! Failed to stat file [/usr/lib64/nx/X11/xkb/rules/xorg]: Unknown error -1.

Hi Roderick,

On Mi 25 Dez 2013 01:13:08 CET, Roderick Johnstone wrote:

On 24/12/13 19:10, Neal Becker wrote:

...

...

PS Now I'm fighting wrong keyboard mappings (see my post to the Fedora kde list). I managed to get x2go to set the correct type and layout but I think kde is overriding it. I got this all working in the beta, but its broken again in the F20 release.

I did notice this in the x2go log, maybe related?

nxagentXkbGetRules: WARNING! Failed to stat file [/usr/lib64/nx/X11/xkb/rules/xorg]: Unknown error -1.

Yes, I noticed that too. I think that is fixed by touching the file usr/share/X11/xkb/keymap.dir. Anyway, touching the keymap.dir file
seems to be needed for the keyboard mapping to work at all.

Actually there are three cases of different settings in the client.
Currently I only have the case of setting the keyboard type and
layout explicitly, working. I will be reporting the non-working
cases, but need some time for more testing to be sure of whats not
working.

By putting some debugging into /usr/bin/startkde I can see that the
keymap is set correctly before starting kde but once the session is
established its changed to a us keyboard layout.

Roderick

Please try X2Go Client from our nightly builds [1] with your testings.
The keyboard setup method has slightly changed there.

Mike

[1] http://wiki.x2go.org/doku.php/wiki:development:nightly-builds

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...

Hi Roderick,

I am the current maintainer of the windows builds.

There are no nightly windows builds because the windows builds are not automated. they are done manually by me according to the instructions here: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient?s[]=win32 Other people can follow those instructions too. They could use some clarifications, but they are accurate.

Automating the windows builds and producing nightly builds is something I would like to accomplish in the future, but I cannot make any commitments at this time.

I will do a few windows builds over the next several days. If they're not going to be posted on the downloads site under "previews", I'll put them on a file hosting site so you and everyone else can try them.

-Mike

On Sun, Dec 29, 2013 at 10:27 AM, Roderick Johnstone <rmj@ast.cam.ac.uk>wrote:

On 28/12/13 21:20, Mike Gabriel wrote:

...

Hi Roderick,

On Mi 25 Dez 2013 01:13:08 CET, Roderick Johnstone wrote:

On 24/12/13 19:10, Neal Becker wrote:

...

...

...

PS Now I'm fighting wrong keyboard mappings (see my post to the Fedora kde list). I managed to get x2go to set the correct type and layout but I think kde is overriding it. I got this all working in the beta, but its broken again in the F20 release.

I did notice this in the x2go log, maybe related?

nxagentXkbGetRules: WARNING! Failed to stat file [/usr/lib64/nx/X11/xkb/rules/xorg]: Unknown error -1.

Yes, I noticed that too. I think that is fixed by touching the file usr/share/X11/xkb/keymap.dir. Anyway, touching the keymap.dir file seems to be needed for the keyboard mapping to work at all.

Actually there are three cases of different settings in the client. Currently I only have the case of setting the keyboard type and layout explicitly, working. I will be reporting the non-working cases, but need some time for more testing to be sure of whats not working.

By putting some debugging into /usr/bin/startkde I can see that the keymap is set correctly before starting kde but once the session is established its changed to a us keyboard layout.

Roderick

Please try X2Go Client from our nightly builds [1] with your testings. The keyboard setup method has slightly changed there.

Mike

[1] http://wiki.x2go.org/doku.php/wiki:development:nightly-builds

Mike

Thanks for your interest in this. Getting this working is a high priority for me.

I checked out the link that you posted. I am interested in Windows and Macos Clients. Currently I've been testing the Windows client but can't see any nightly builds for that OS on that page. Can you provide a more specific link please?

I did check the preview releases but dont ee anything newer than the 4.0.1.2 version that I have.

Many thanks.

Roderick

---

X2Go-User mailing list X2Go-User@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-user

On Sun, Dec 29, 2013 at 12:39 PM, Mike Gabriel < mike.gabriel@das-netzwerkteam.de> wrote:

We have a Windows 7 VM on japsand.x2go.org that could be propped up as a jenkins node. Only requirement for Jenkins would be a script that can build the setup.exe with one command line call.

Sounds good,

I probably won't have time today, but I would like to set this up by next Sunday. I am on vacation this entire week.

Yes, let's take the discussion of the win32 builds to another thread and/or IRC.

Watch for an announcement on x2go-dev.

On Sun, Dec 29, 2013 at 12:51 PM, Roderick Johnstone <rmj@ast.cam.ac.uk>wrote:

I wonder if we should take this discussion to another thread as the subject here is misleading now (my fault for mentioning the keyboard issue in this thread.)

@Mike(DePaulo) Many thanks. I'll look out for the new Windows client builds.

@Mike(Gabriel) Am I going to need recent nightly builds of the server as well? I'm currently using the RPMS from the Fedora 20 repository maintained by Orion. Current version is x2goserver-4.0.1.9-2.fc20.x86_64.

Thanks both.

Roderick

On 29/12/13 17:28, Michael DePaulo wrote:

...

Hi Roderick,

I am the current maintainer of the windows builds.

There are no nightly windows builds because the windows builds are not automated. they are done manually by me according to the instructions here: http://wiki.x2go.org/doku.php/wiki:development:build-howto- mswin:x2goclient?s[]=win32 Other people can follow those instructions too. They could use some clarifications, but they are accurate.

Automating the windows builds and producing nightly builds is something I would like to accomplish in the future, but I cannot make any commitments at this time.

I will do a few windows builds over the next several days. If they're not going to be posted on the downloads site under "previews", I'll put them on a file hosting site so you and everyone else can try them.

-Mike

On Sun, Dec 29, 2013 at 10:27 AM, Roderick Johnstone <rmj@ast.cam.ac.uk <mailto:rmj@ast.cam.ac.uk>> wrote:

On 28/12/13 21:20, Mike Gabriel wrote:

    Hi Roderick,

    On  Mi 25 Dez 2013 01:13:08 CET, Roderick Johnstone wrote:

        On 24/12/13 19:10, Neal Becker wrote:


                PS Now I'm fighting wrong keyboard mappings (see my
                post to the Fedora
                kde list). I managed to get x2go to set the correct
                type and layout but
                I think kde is overriding it. I got this all working
                in the beta, but
                its broken again in the F20 release.


            I did notice this in the x2go log, maybe related?

            nxagentXkbGetRules: WARNING! Failed to stat file
            [/usr/lib64/nx/X11/xkb/rules/__xorg]: Unknown error -1.



        Yes, I noticed that too. I think that is fixed by touching
        the file
        usr/share/X11/xkb/keymap.dir. Anyway, touching the
        keymap.dir file
        seems to be needed for the keyboard mapping to work at all.

        Actually there are three cases of different settings in the
        client.
        Currently I only have the case of setting the keyboard type
        and layout
        explicitly, working. I will be reporting the non-working
        cases, but
        need some time for more testing to be sure of whats not

working.

        By putting some debugging into /usr/bin/startkde I can see
        that the
        keymap is set correctly before starting kde but once the
        session is
        established its changed to a us keyboard layout.

        Roderick


    Please try X2Go Client from our nightly builds [1] with your
    testings.
    The keyboard setup method has slightly changed there.

    Mike

    [1]
    http://wiki.x2go.org/doku.php/__wiki:development:nightly-__builds<

http://wiki.x2go.org/doku.php/wiki:development:nightly-builds>

Mike

Thanks for your interest in this. Getting this working is a high
priority for me.

I checked out the link that you posted. I am interested in Windows
and Macos Clients. Currently I've been testing the Windows client
but can't see any nightly builds for that OS on that page. Can you
provide a more specific link please?

I did check the preview releases but dont ee anything newer than the
4.0.1.2 version that I have.

Many thanks.


Roderick
_________________________________________________
X2Go-User mailing list
X2Go-User@lists.berlios.de <mailto:X2Go-User@lists.berlios.de>
https://lists.berlios.de/__mailman/listinfo/x2go-user
<https://lists.berlios.de/mailman/listinfo/x2go-user>