xpra icon
Bug tracker and wiki

Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#1303 closed defect (fixed)

fedora 24 beta install dependency issue

Reported by: alas Owned by: alas
Priority: major Milestone: 1.0
Component: server Version: trunk
Keywords: Cc:


After installing the winswitch/xpra repos on a new fedora 24 and installing - getting an 'lsb_release' error.

[patron@Fedora24-Server-374 ~]$ xpra --version
error running (['lsb_release', '-cs'],),{'stderr': -1, 'stdout': -1}: [Errno 2] No such file or directory
Warning: failed to detect OS release using lsb_release -cs:
xpra v1.0

Some help from smo pointed me to the need to install redhat-lsb-core ... after which the errors went away and fedora 24 server became a much happier camper.

Probably needs to be added as a dependency.

Change History (3)

comment:1 Changed 2 years ago by Antoine Martin

Owner: changed from Antoine Martin to alas

AFAIK, this is just a harmless warning, now hidden in r13650.
lsb packages are not strictly required, they just make it easier to guess which linux distribution we're running on so we can activate workaround (ie: no Xdummy with Ubuntu).

comment:2 Changed 2 years ago by alas

Resolution: fixed
Status: newclosed

Hmm... testing by trying to install 1.0 r13671 on a fresh fedora 24 vm, I'm no longer seeing the above warning, but without installing the redhat-lsb-core library I keep failing to get past a bus connection error when I try to start a server... but only when connecting to the server vm as root and then using su - [not-root-user].

With a user called maint, if I log in with root and then run su - maint, followed by an attempt to start the server, I get the following.

[maint@Fedora24-Server-378 ~]$ xpra --no-daemon --bind-tcp= --start-child=xterm --mdns=no --start-new-commands=yes start :13 -d server
using systemd-run to wrap 'start' server command
'systemd-run' '--scope' '--user' '/usr/bin/xpra' '--bind-tcp=' '--start-child=xterm' '--mdns=no' '--start-new-commands=yes' 'start' ':13' '-d' 'server' '--daemon=no'
Failed to create bus connection: No such file or directory

For some reason though, if I just go ahead and connect with the maint user, then the server launches just fine ... and the redhat-lsb-core packages do indeed seem to be not strictly required.

And, with that probably more verbose than necessary comment, I'll close this.

comment:3 Changed 2 years ago by Antoine Martin

but only when connecting to the server vm as root and then using su - [not-root-user]

for systemd-run issues, see #1129 - I don't think this has anything to do with lsb.

Last edited 2 years ago by Antoine Martin (previous) (diff)
Note: See TracTickets for help on using tickets.