On Thursday, 26 December 2019 12:31:41 PM AEDT Paul Szabo wrote:
> I just upgraded from stretch to buster, using xpra version 2.4.3+dfsg1-1
Thanks. I can not reproduce on 3.x from buster-backports so I reckon the
problem is already fixed in a newer release.
--
All the best,
Dmitry Smirnov.
Dear Dmitry,
>> I seem to get good results by modifying script /usr/bin/xpra as below.
>
> Is this still necessary with the latest release from backports?
> Which reproducer command exhibits this problem?
I just upgraded from stretch to buster, using xpra version 2.4.3+dfsg1-1
(in buster, not
On Thursday, 26 December 2019 11:21:47 AM AEDT Paul Szabo wrote:
> I seem to get good results by modifying script /usr/bin/xpra as below.
Is this still necessary with the latest release from backports?
Which reproducer command exhibits this problem?
Thanks.
--
Regards,
Dmitry Smirnov.
---
I seem to get good results by modifying script /usr/bin/xpra as below.
Cheers, Paul
--- /usr/bin/xpra.bak 2019-01-20 17:23:10.0 +1100
+++ /usr/bin/xpra 2019-12-26 11:17:42.455901905 +1100
@@ -1,5 +1,14 @@
#! /usr/bin/python2
+# PSz 26 Dec 2019
+# Avoid error like:
+#
Hi.
It seems to work, but still logs an error about the directory to stdout:
Warning: cannot use the system proxy for 'start' subcommand,
failed to connect to '/run/xpra/system':
[Errno 2] No such file or directory
more information may be available in your system log
2018-09-22 00:08:12,217
On Friday, 7 September 2018 5:07:22 AM AEST Alex wrote:
> xpra in debian buster does not work anymore. The error messages when
> trying to start it from another host with xpra start are:
>
> $ xpra start ssh:remotehost:10 --encoding=vp9 --min-quality=50
> --start=konsole
Does it work with
Package: xpra
Version: 2.3.3+dfsg1-1
Severity: important
Dear Maintainer,
xpra in debian buster does not work anymore. The error messages when
trying to start it from another host with xpra start are:
$ xpra start ssh:remotehost:10 --encoding=vp9 --min-quality=50 --start=konsole
2018-09-01
7 matches
Mail list logo
