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.

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

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.

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.

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

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

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

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