Roderick Johnstone wrote:

On 24/03/15 21:36, Luigi Toscano wrote:

...

Roderick Johnstone ha scritto:

...

Hi

I'm interested to find out whether the remote desktop system x2go (http://wiki.x2go.org/doku.php), is going to work in F22 under KDE.

x2go is documented to be incompatible with 'KDE 5' (http://wiki.x2go.org/doku.php/doc:de-compat) but I notice that there are still seem to be (at least) parts of KDE 4 in F22.

According the description, it seems incompatible with the desktop Plasma 5. The parts you mention are the kdelibs4-based applications available in F22, which don't have a Frameworks-based release.

Ciao

Luigi

Thanks for your comment.

Thats a pity. Our research group are long time KDE on Fedora users and its good if people can have the same desktop experience both on remote (x2go) and local (desktop) logins.

I did notice that the development/22/x86_64/os/Packages tree has the packages: kde-workspace-common-4.11.16-7.fc22.noarch.rpm kde-workspace-devel-4.11.16-7.fc22.x86_64.rpm

and had hoped that there might there be some legacy kde4 desktop support.

On closer examination now I see that the common package only contains a few text files and there is no kde-workspace package as such.

Oh well, I guess there is always F21 to keep us going for a few more months. From what I read on the x2go lists (IIRC) there will be a big project to update the X11 server in x2go to something modern which will support KDE 5 but there is no timescale for that as of now.

Roderick

Oh that's unfortunate - I really depend on x2go. There are alternatives, but not nearly as nice.

On 25/03/2015 12:02, Neal Becker wrote:

Neal Becker wrote:

...

Roderick Johnstone wrote:

...

On 24/03/15 21:36, Luigi Toscano wrote:

...

Roderick Johnstone ha scritto:

...

Hi

I'm interested to find out whether the remote desktop system x2go (http://wiki.x2go.org/doku.php), is going to work in F22 under KDE.

x2go is documented to be incompatible with 'KDE 5' (http://wiki.x2go.org/doku.php/doc:de-compat) but I notice that there are still seem to be (at least) parts of KDE 4 in F22.

According the description, it seems incompatible with the desktop Plasma 5. The parts you mention are the kdelibs4-based applications available in F22, which don't have a Frameworks-based release.

Ciao

Luigi

Thanks for your comment.

Thats a pity. Our research group are long time KDE on Fedora users and its good if people can have the same desktop experience both on remote (x2go) and local (desktop) logins.

I did notice that the development/22/x86_64/os/Packages tree has the packages: kde-workspace-common-4.11.16-7.fc22.noarch.rpm kde-workspace-devel-4.11.16-7.fc22.x86_64.rpm

and had hoped that there might there be some legacy kde4 desktop support.

On closer examination now I see that the common package only contains a few text files and there is no kde-workspace package as such.

Oh well, I guess there is always F21 to keep us going for a few more months. From what I read on the x2go lists (IIRC) there will be a big project to update the X11 server in x2go to something modern which will support KDE 5 but there is no timescale for that as of now.

Roderick

Oh that's unfortunate - I really depend on x2go. There are alternatives, but not nearly as nice.

I looked at the compat chart here: http://wiki.x2go.org/doku.php/doc:de-compat

Is this talking about the client-side or server-side? I want to run kde on my client (my laptop) - don't care that much about the remote server.

Neal

Based on the context of the first paragraph of that page I had read it as saying that you cannot cannot connect to a server that runs a KDE 5 session.

Roderick

On 25/03/15 17:27, Roderick Johnstone wrote:

On 25/03/15 15:54, Kevin Kofler wrote:

...

Roderick Johnstone wrote:

...

x2go is documented to be incompatible with 'KDE 5' (http://wiki.x2go.org/doku.php/doc:de-compat) but I notice that there are still seem to be (at least) parts of KDE 4 in F22.

Hmmm, is GLX needed even when using llvmpipe? If not, exporting LIBGL_ALWAYS_SOFTWARE or QT_XCB_FORCE_SOFTWARE_OPENGL should work around the problem.

There are also some general Qt 5 compatibility issues reported, but those seem fixed now according to: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=637#33

Another workaround would be to try LXQt instead (assuming the Qt 5 issues are really solved now, see above). KDE applications should run fine under LXQt, or any other desktop (e.g. Xfce) even.

     Kevin Kofler

Kevin

Thanks! I was wondering if there might be some work around by setting some environment variables.

I'll give it a try when I finally get my F22 alpha test system installed.

Roderick

I finally got around to trying KDE with x2go on F22 using:

export QT_XCB_FORCE_SOFTWARE_OPENGL=1

I can log in ok now, but its a bit slow, although my testing machine is rather old.

Can someone advise the 'right' place to put the export line please.

x2goagent sits there consuming between 50-100% cpu all the time. I'm not sure that that is expected and might be the cause of the slowness. Not sure how to diagnose this.

I found I needed to remove package kscreen to prevent the x2go window being resized automatically.

So, when I log in I get a single konsole window. The panel comes up momentarily but then appears to die.

How do I restart the panel from a terminal and where would I check for errors?

Also, resizing the x2go window makes konsole disappear. Its still running though and the x2go window eventually goes black.

Did anyone else try this yet? Anyone have any insight as to whats happening.

Thanks

Roderick

On 02/04/2015 19:32, Rex Dieter wrote:

Roderick Johnstone wrote:

...

I finally got around to trying KDE with x2go on F22 using:

export QT_XCB_FORCE_SOFTWARE_OPENGL=1

I can log in ok now, but its a bit slow, although my testing machine is rather old.

Can someone advise the 'right' place to put the export line please.

I'd suggest in a *.sh snippet under ~/.config/plasma-workspace/env/ (per user) or /etc/xdg/plasma-workspace/env/ for all users

Thanks Rex, I'm using the second form and that works well.

How can I start the panel from the command line? Maybe doing that will give me a clue as to why its dying on session startup.

Thanks again.

Roderick

On 25/03/15 15:54, Kevin Kofler wrote:

Roderick Johnstone wrote:

...

x2go is documented to be incompatible with 'KDE 5' (http://wiki.x2go.org/doku.php/doc:de-compat) but I notice that there are still seem to be (at least) parts of KDE 4 in F22.

Hmmm, is GLX needed even when using llvmpipe? If not, exporting LIBGL_ALWAYS_SOFTWARE or QT_XCB_FORCE_SOFTWARE_OPENGL should work around the problem.

There are also some general Qt 5 compatibility issues reported, but those seem fixed now according to: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=637#33

Another workaround would be to try LXQt instead (assuming the Qt 5 issues are really solved now, see above). KDE applications should run fine under LXQt, or any other desktop (e.g. Xfce) even.

     Kevin Kofler

By setting: export QT_XCB_FORCE_SOFTWARE_OPENGL = 1 export LIBGL_ALWAYS_SOFTWARE=1

I have KDE running in an x2go session in my F22 test system (installed from the development/22 tree) but there is no panel visible.

kscreen was resizing my x2go window after a few seconds and xdpyinfo was reporting it as 1920x1080. I have removed the kcreen package and the x2go window is now no longer resized and is reported by xdpyinfo as 800x600 which is what I asked for in the xc2go client.

Now the panel comes up and is visible, but only for a short while and before disappearing.

plasmashell is still running so I'm guessing that the panel was relocated off the display window somewhere.

Resizing the x2go window in order to look for the missing panel does not reveal anything and causes a black border around the desktop background where the window has been enlarged.

After a minute or so the konsole, which was started as part of the session, disappears, but the konsole process is still running, so maybe it got relocated elsewhere too.

Any ideas on how to find my panel or stop it moving or any insight on whats happening would be appreciated.

Thanks

Roderick Johnstone

On 14/04/15 03:05, Kevin Kofler wrote:

Roderick Johnstone wrote:

...

By setting: export QT_XCB_FORCE_SOFTWARE_OPENGL = 1 export LIBGL_ALWAYS_SOFTWARE=1

It doesn't make sense to set both of these. QT_XCB_FORCE_SOFTWARE_OPENGL is the same as LIBGL_ALWAYS_SOFTWARE, but for Qt 5 applications only.

     Kevin Kofler

Thanks Kevin

I'm just using: export LIBGL_ALWAYS_SOFTWARE=1 in the x2go session now.

Roderick