Announcement

Collapse
No announcement yet.

Chrome Remote Desktop display failure on freshly installed Kubuntu 16.04.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Chrome Remote Desktop display failure on freshly installed Kubuntu 16.04.

    For me, chrome remote desktop has proven to be an invaluable tool for allowing me to deal with issues at work while travelling remotely. Think VNC managed by Chrome (heck, it might actually be VNC under the covers).

    I have a dedicated "remote gateway" desktop computer at work to which I connect remotely. After doing a new install of Kubuntu 16.04 on this box, I'm getting a strange issue when attempting a remote connection to this box. The connection is successfully established and I get a graphical session started but I get a krunner segfault error message, the an error about "All shell packages missing. This is an installation issue, please contact your distribution." (Hello, may I please speak to Kubuntu? This is Tom).

    Sometimes I get a ksplashqml error (which I've seen on some of my other Kubuntu 16.04 installations. On all my new 16.04 systems, not just the remote system, once I get the first ksplashqml error, it seems to cascade into a series of different errors at about 30 second intervals, sometimes its a message about ballo, or about appport, or systray or some other KDE resource but these second issues will only happen after the first ksplashqml error.)

    I've seen other forum and problem reporting entries about ksplashqml and segfaults if there are no themes loaded but I don't know what this means. But that's not the theme for this posting; I'll post another message asking what the heck ksplashqml is and how to load themes for it.

    Any help with resolving the krunner segfault problem when connecting remotely would be greatly appreciated.

    Edit:
    I think my problem is related to successfully starting a plasma 5 desktop after I make the chrome remote desktop. I successfully installed xscreensavers (using instructions in this posting https://lists.fedoraproject.org/pipe...il/014545.html). When I make the initial chrome remote desktop connection, I can see the xscreensaver stuff running but it's not able to start a plasma desktop.
    Last edited by tomwitt; May 26, 2016, 12:23 PM. Reason: Added more information

    #2
    The remote control app in this case does not know how to start the new plasma session correctly.
    I am getting the same plasma fail result with x2go unless I take control of the existing logged in console desktop session.
    x2go lists 16.04 as unsupported for now due to the change from lightdm to sddm.
    Kubuntu 18.04 on AMD

    Comment

    Working...
    X