Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Veyon Community Forum

  1. Home
  2. Help & Troubleshooting
  3. Veyon Service works only when run manually from X Windows session

Veyon Service works only when run manually from X Windows session

Scheduled Pinned Locked Moved Help & Troubleshooting
1 Posts 1 Posters 42 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    AlexDesyatnik
    wrote on last edited by
    #1

    Hi, I've run into this problem. Journalctl logs show the following:

    июл 31 13:29:59 localhost.localdomain systemd[1]: Started veyon.service - Veyon Service.
    июл 31 13:29:59 localhost.localdomain veyon-service[10174]: No protocol specified
    июл 31 13:29:59 localhost.localdomain veyon-server[10174]: qt.qpa.xcb: could not connect to display :1
    июл 31 13:29:59 localhost.localdomain veyon-server[10174]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
    июл 31 13:29:59 localhost.localdomain veyon-server[10174]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                                                  
                                                                  Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
    
    

    Systemctl shows that service is working, but it doesn't accept incoming connections when tested with telnet IPADDR 11100. When I start veyon-service manually from X Windows session (MATE if that matters), all works just fine so it isn't misconfigured firewall. Disabling X Damage in Veyon Configurator changes nothing.

    1 Reply Last reply
    0

    Powered by NodeBB | Contributors
    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups