Bug#816533: [xpra] Does not start: Error starting Xvfb: [Errno 2] No such file or directory

[Bruno Kleinert]

Package: xpra
Version: 0.15.8+dfsg-1+b1
Severity: grave

--- Please enter the report below this line. ---
Hi there,

xpra fails to start for me since a couple of days:

(0)fuddl@flutschi:~$ xpra start --no-daemon  --start=/usr/bin/gnome-terminal
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Failed to rename log file "/home/fuddl/.xpra/Xorg.S14576.log" to "/home/fuddl/.xpra/Xorg.S14576.log": No such file or directory

X.Org X Server 1.18.1
Release Date: 2016-02-08
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux flutschi 4.4.0-1-amd64 #1 SMP Debian 4.4.2-3 (2016-02-21) x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-1-amd64 root=/dev/mapper/vg0-root ro splash
Build Date: 09 February 2016  11:06:03AM
xorg-server 2:1.18.1-1 (http://www.debian.org/support) 
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/home/fuddl/.xpra/Xorg.S14576.log", Time: Wed Mar  2 17:58:53 2016
(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Using display number provided by Xorg: :1
2016-03-02 17:58:53,290 Error starting Xvfb: [Errno 2] No such file or directory

This drops me back to the prompt with an Xorg process running in the
background. Installing the package xvfb does not help.

Greetings - Fuddl

--- System information. ---
Architecture: amd64
Kernel:       Linux 4.4.0-1-amd64

Debian Release: stretch/sid
  500 unstable        ftp.uni-erlangen.de 
    1 experimental    ftp.uni-erlangen.de 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

[Dmitry Smirnov]

On Wed, 2 Mar 2016 06:13:56 PM Bruno Kleinert wrote:
> Severity: grave

Please don't panic and use correct severity levels:

https://www.debian.org/Bugs/Developer#severities

> xpra fails to start for me since a couple of days:

There were no recent upload of Xpra so the problem is likely to be somewhere
else...

--
All the best,
Dmitry Smirnov.

[Bruno Kleinert]

Am Donnerstag, den 03.03.2016, 08:39 +1100 schrieb Dmitry Smirnov:
> On Wed, 2 Mar 2016 06:13:56 PM Bruno Kleinert wrote:
> >
> > Severity: grave
> Please don't panic and use correct severity levels:
>
>     https://www.debian.org/Bugs/Developer#severities

Well, it was unusable for using it on sid machines at the time I
reported the bug, until I found a workaround, today :)

> > xpra fails to start for me since a couple of days:
> There were no recent upload of Xpra so the problem is likely to be
> somewhere 
> else...

I noticed that and thought that one can just forward the bug report to
another package that could possibly be the culprit. Unfortunately, I
can't retrace which other package update broke xpra.

My current workaround is to install the package xvfb and start the xpra
server with the following command:
xpra start --no-daemon --xvfb="/usr/bin/Xvfb +extension  Composite -screen 0 3840x2560x24+32 -nolisten tcp -noreset" --start=/usr/bin/gnome-terminal

As far as I understood it, the standard (and intended?) way is to have
xpra start an Xorg server using the void input in and dummy video
output modules instead of Xvfb.

Cheers - Fuddl

[Bruno Kleinert]

Hi Dmitry,

a couple of days ago I used xpra and this issue has disappeared, i.e. I
could run an xpra server with its default settings and I did not have
to apply the workaround from above. From my point of view the bug is
fixed and could be closed.

Cheers - Fuddl