search

kasmtech / KasmVNC

Modern VNC Server and client, web based and secure
GNU General Public License v2.0
3.56k stars 317 forks source link

Conflicts on Fedora with package `tigervnc-server-minimal`, prevents use of `xrdp` #291

Open gbraad opened 4 weeks ago

gbraad commented 4 weeks ago

Describe the bug Since the package kasmvncserver conflicts with tigervnc-server-minimal, it is not possible to install this alongside the use of xrdp. This is however possible on Debian/Ubuntu.

System Description Fedora 40

KasmVNC Details 1.3.2 (rpm)

Installation Details

$ rpm -ivh kasmvnc...

Additional context The use of xrdp allows a vnc connection to be forwarded over rdp, when for example x11vnc is used.

The conflict prevents other applications/package that rely on the existence of tigervnc-server-minimal.

Note: It does not feel like a good idea to conflict with base packages. This most likely also applies to RHEL and other compatible distros. Though they might use EPEL for this, so the impact is minimal.

Note 2: I know it is a deliberate choice: https://github.com/kasmtech/KasmVNC/blob/a89f71d98d97d8551119f8a48de3699cdd8c86e8/fedora/kasmvncserver.spec#L11

but if the vncserver binary is not even compatible with legacy clients (and therefore not a drop-in replacement), do not call it vncserver, but instead use kasmvncserver as other files are already called this way, like kasmvncpasswd

https://github.com/kasmtech/KasmVNC/blob/a89f71d98d97d8551119f8a48de3699cdd8c86e8/fedora/kasmvncserver.spec#L47

gbraad commented 3 weeks ago

I have created a rebuild of the RPMs for Fedora 40, but this needs a manual change as the binary Xvnc is hardcoded in vncserver: https://github.com/spotsnel/AltRPMS-KasmVNC/issues/2