Am Donnerstag, den 03.03.2016, 15:07 +0100 schrieb 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
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
signature.asc
Description: This is a digitally signed message part
