>> This does not happen with current xpra v1.0.3-r15051 from xpra
repository.
>I have to correct myself: Now it happens with xpra v1.0.3, too. I'm not
sure why I didn't have the error the first time I checked this.
Update: xpra v1.0.3 only has problems in virtualbox with guest additions
install
I'm pretty sure the bug is not within xpra but within debian.
I have reported a related bug:
#856662 xorg: starting X within X without specifying -vt destroys
current X session
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856662
I believe fixing #856662 also fixes this xpra bug as the sym
On Wednesday, 1 March 2017 3:23:34 PM AEDT mviereck wrote:
> The above steps destroy current X session, leaving a black screen with some
> startup messages. This does not happen with current xpra v1.0.3-r15051
> from xpra repository.
I've seen that before -- it started to happen at some point afte
Hi!
> I recommend to include current xpra version v1.0.3.
That's not possible at this stage of the Stretch freeze.
Either cherry-pick the patch which fixes this problem or the package
gets removed from testing. Importing a new upstream release is not
allowed at by the release team at this point.
Package: xpra
Version: 0.17.6+dfsg-1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
steps to reproduce:
1. start xpra server
xpra start :20 --start-child=xterm --exit-with-children
2. attach to server
xpra attach :20
3. terminate xpra server (in this case by closi
5 matches
Mail list logo
