New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting xpra server... #298
Comments
I want to report the same issue when trying to start KeepassX from the default repo. |
Well it looks like this is a known bug, now I just need to reproduce it
on my machine and ship an updated package...
https://bugzilla.redhat.com/show_bug.cgi?id=1393114
…On 12/16/2016 04:34 PM, DonHugo69 wrote:
I want to report the same issue when trying to start KeepassX from the
default repo.
OS: up-to-date Manjaro Linux KDE
GPU:AMD R9 290, using amdgpu module + Mesa 13
Dual monitor setup
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-EHe6ElhaMnW40KdUdZgiSVqXW5Xks5rIq9_gaJpZM4LOtph>.
|
I updated all my subusers yesterday and didn't get this error. I'll be
having to dig deeper.
…On 12/16/2016 04:34 PM, DonHugo69 wrote:
I want to report the same issue when trying to start KeepassX from the
default repo.
OS: up-to-date Manjaro Linux KDE
GPU:AMD R9 290, using amdgpu module + Mesa 13
Dual monitor setup
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-EHe6ElhaMnW40KdUdZgiSVqXW5Xks5rIq9_gaJpZM4LOtph>.
|
Can one of you please try running "subuser update all" and tell me if it
changes the outcome?
…On 12/16/2016 04:34 PM, DonHugo69 wrote:
I want to report the same issue when trying to start KeepassX from the
default repo.
OS: up-to-date Manjaro Linux KDE
GPU:AMD R9 290, using amdgpu module + Mesa 13
Dual monitor setup
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-EHe6ElhaMnW40KdUdZgiSVqXW5Xks5rIq9_gaJpZM4LOtph>.
|
Unfortunately I get still the same error. |
WTF, no markdown in email replies and no way to turn that off...
…On 12/18/2016 09:02 PM, DonHugo69 wrote:
Unfortunately I get still the same error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-AA3Kq7TJLXLhbWG0G9vQoOFCTQlks5rJZFigaJpZM4LOtph>.
|
Somehow, this is violating one of three assumptions that I'm making:
I'm guessing that we've run into the later. So in order to test this hypothesis, first I run:
To find my xterm xpra subuser's that make the xterm xpra-bridge on my Then I run:
And then I look at the subuser default repositories base image to remind It is debian:strech As a sanity check, I cat Now I look at https://packages.debian.org/stretch/xpra to see what the I see that I have my work cut out for me... |
Well, today I played with this more, and it looks like I haven't proven that the subuser update mechanism is broken. When I ran |
I updated, and have v0.17.6.
Interesting part of the ensuing output:
Went to bed, turned my computer on again today and ran:
which still hangs at "Starting xpra server..."
|
OK, so I grant that the "change in permissions" thing is a bug in
subuser, but I don't get why debian isn't updating XPRA in my xpra
containers when I run apt-get update. I'll bet a million bucks this
isn't a bug in apt, given that apt has been rock solid for like a decade
now, but what else can this be...
But you still cannot start up xterm with xpra 0.17.6? Is that correct?
And I CAN start it with 0.17.4...
…On 12/20/2016 07:47 PM, libben wrote:
I updated, and have v0.17.6.
|% sudo pip3 uninstall subuser % sudo pip3 install subuser % subuser
update all A (accept and apply changes to xterm's permissions) |
Interesting part of the ensuing output:
|... New images for the following subusers need to be installed:
!service-subuser-xterm-xpra-server !service-subuser-xterm-xpra-client
... |
Went to bed, turned my computer on again today and ran:
|% subuser run xterm |
which still hangs at "Starting xpra server..."
|% subuser run --entrypoint=/bin/bash
\!service-subuser-xterm-xpra-server ***@***.***:~$ xpra --version
xpra v0.17.6 ***@***.***:~$ exit exit % subuser run
--entrypoint=/bin/bash \!service-subuser-xterm-xpra-client
***@***.***:~$ xpra --version xpra v0.17.6 |
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-FiZmNqKLK2pYTi05-d0MFGcvDVzks5rKCK-gaJpZM4LOtph>.
|
Yep, that's correct: I cannot start it with 0.17.6. |
For comparison with your sha256sums and hashes: the installed-images.json file in /home/ben/.subuser has the contents
|
Sadly, the hashes don't help with subuser, because the "file modify
times" and the exact build logs won't be the same... :( I'm working with
the repeatr project to try to remedy that, but it is a major surgery
that probably involves replacing Docker...
…On 12/20/2016 08:25 PM, libben wrote:
For comparison with your sha256sums and hashes: the
installed-images.json file in /home/ben/.subuser has the contents
|{
"sha256:ee45ba6fbb60a5e3a7c6c0d3a1d98060c6bb8e9f69fe41359ec01ca0c1f6693e":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:51bb1f569146e525ccd2db9d9a043d5f5c19c482edffc94e6415a428f2e428f4":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:c230b2806699b95d9974cf9ba2f93a2b8976b1d6992335f85aeb068f2061ef4d":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" },
"sha256:63227a51d70b0b6e83b2da8cb8d22cb82f42cdc467eccf408129c3a933e1f7aa":
{ "image-source-hash": "7e679272789c7fc81c7f25ac6b1eca48e102a5ac",
"source-repo": "default", "image-source": "xterm" },
"sha256:09f4a0db3e6306926305a83f41c5ef1eae58f3364c56cdd96d3716b0b84d828f":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:3b8eaa3bcd43df8f474e3502b9d8e6ce8c3a643d1553eae477433ae5924aec31":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" },
"sha256:0564044bdecd3af917c0f68920569da9037033447dd7e719c280555fa7136e44":
{ "image-source-hash": "e59d0543cf7fb71ea0f1fbaa3e35c6aa77fe9990",
"source-repo": "default", "image-source": "libdebian" },
"sha256:009fc5d1d49cdeea44776e29468fb470c4cb66bf4e267c9b67fd76b5bd540a0c":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:e2866b6d689a62770b1d1b06fb773cb78f0a4db0d7db45b4c77de7decd4e6a5d":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:74d3750334db59cbb718c141e754603aca025f93350c9327e0074ca834213d73":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:0c8e037d7abb41e77d77b52cb04a2911f2969f949186b51e364e6a35f86e224d":
{ "image-source-hash": "b1968d5e991596e5adfd0099604e45d343908245",
"source-repo": "default", "image-source": "libx11" },
"sha256:3a29930c21987a82d89216dcaa50cd14d6809f5b9de8ccd7a3f5cb95865dd1e7":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" } } |
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-NwrSdZn56SVv3dJJblZ0R6zr1B6ks5rKCusgaJpZM4LOtph>.
|
I've written to the xpra mailing list to see if Antonine can't get the
xpra package fixed...
…On 12/20/2016 08:25 PM, libben wrote:
For comparison with your sha256sums and hashes: the
installed-images.json file in /home/ben/.subuser has the contents
|{
"sha256:ee45ba6fbb60a5e3a7c6c0d3a1d98060c6bb8e9f69fe41359ec01ca0c1f6693e":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:51bb1f569146e525ccd2db9d9a043d5f5c19c482edffc94e6415a428f2e428f4":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:c230b2806699b95d9974cf9ba2f93a2b8976b1d6992335f85aeb068f2061ef4d":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" },
"sha256:63227a51d70b0b6e83b2da8cb8d22cb82f42cdc467eccf408129c3a933e1f7aa":
{ "image-source-hash": "7e679272789c7fc81c7f25ac6b1eca48e102a5ac",
"source-repo": "default", "image-source": "xterm" },
"sha256:09f4a0db3e6306926305a83f41c5ef1eae58f3364c56cdd96d3716b0b84d828f":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:3b8eaa3bcd43df8f474e3502b9d8e6ce8c3a643d1553eae477433ae5924aec31":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" },
"sha256:0564044bdecd3af917c0f68920569da9037033447dd7e719c280555fa7136e44":
{ "image-source-hash": "e59d0543cf7fb71ea0f1fbaa3e35c6aa77fe9990",
"source-repo": "default", "image-source": "libdebian" },
"sha256:009fc5d1d49cdeea44776e29468fb470c4cb66bf4e267c9b67fd76b5bd540a0c":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:e2866b6d689a62770b1d1b06fb773cb78f0a4db0d7db45b4c77de7decd4e6a5d":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:74d3750334db59cbb718c141e754603aca025f93350c9327e0074ca834213d73":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:0c8e037d7abb41e77d77b52cb04a2911f2969f949186b51e364e6a35f86e224d":
{ "image-source-hash": "b1968d5e991596e5adfd0099604e45d343908245",
"source-repo": "default", "image-source": "libx11" },
"sha256:3a29930c21987a82d89216dcaa50cd14d6809f5b9de8ccd7a3f5cb95865dd1e7":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" } } |
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-NwrSdZn56SVv3dJJblZ0R6zr1B6ks5rKCusgaJpZM4LOtph>.
|
This should be fixed soon, but I don't know how soon:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845728
…On 12/20/2016 08:25 PM, libben wrote:
For comparison with your sha256sums and hashes: the
installed-images.json file in /home/ben/.subuser has the contents
|{
"sha256:ee45ba6fbb60a5e3a7c6c0d3a1d98060c6bb8e9f69fe41359ec01ca0c1f6693e":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:51bb1f569146e525ccd2db9d9a043d5f5c19c482edffc94e6415a428f2e428f4":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:c230b2806699b95d9974cf9ba2f93a2b8976b1d6992335f85aeb068f2061ef4d":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" },
"sha256:63227a51d70b0b6e83b2da8cb8d22cb82f42cdc467eccf408129c3a933e1f7aa":
{ "image-source-hash": "7e679272789c7fc81c7f25ac6b1eca48e102a5ac",
"source-repo": "default", "image-source": "xterm" },
"sha256:09f4a0db3e6306926305a83f41c5ef1eae58f3364c56cdd96d3716b0b84d828f":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:3b8eaa3bcd43df8f474e3502b9d8e6ce8c3a643d1553eae477433ae5924aec31":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" },
"sha256:0564044bdecd3af917c0f68920569da9037033447dd7e719c280555fa7136e44":
{ "image-source-hash": "e59d0543cf7fb71ea0f1fbaa3e35c6aa77fe9990",
"source-repo": "default", "image-source": "libdebian" },
"sha256:009fc5d1d49cdeea44776e29468fb470c4cb66bf4e267c9b67fd76b5bd540a0c":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:e2866b6d689a62770b1d1b06fb773cb78f0a4db0d7db45b4c77de7decd4e6a5d":
{ "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
"source-repo": "default", "image-source": "xpra" },
"sha256:74d3750334db59cbb718c141e754603aca025f93350c9327e0074ca834213d73":
{ "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-client" },
"sha256:0c8e037d7abb41e77d77b52cb04a2911f2969f949186b51e364e6a35f86e224d":
{ "image-source-hash": "b1968d5e991596e5adfd0099604e45d343908245",
"source-repo": "default", "image-source": "libx11" },
"sha256:3a29930c21987a82d89216dcaa50cd14d6809f5b9de8ccd7a3f5cb95865dd1e7":
{ "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
"source-repo": "default", "image-source":
"subuser-internal-xpra-server" } } |
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABU7-NwrSdZn56SVv3dJJblZ0R6zr1B6ks5rKCusgaJpZM4LOtph>.
|
Looks like it'll be another 3 or 4 days. The Debian package tracker says the fix has been in Unstable for 6 out of 10 days, after that it will land in Testing.
…On December 21, 2016 4:19:53 AM CST, Timothy Hobbs ***@***.***> wrote:
This should be fixed soon, but I don't know how soon:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845728
On 12/20/2016 08:25 PM, libben wrote:
>
> For comparison with your sha256sums and hashes: the
> installed-images.json file in /home/ben/.subuser has the contents
>
> |{
>
"sha256:ee45ba6fbb60a5e3a7c6c0d3a1d98060c6bb8e9f69fe41359ec01ca0c1f6693e":
> { "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
> "source-repo": "default", "image-source":
> "subuser-internal-xpra-client" },
>
"sha256:51bb1f569146e525ccd2db9d9a043d5f5c19c482edffc94e6415a428f2e428f4":
> { "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
> "source-repo": "default", "image-source": "xpra" },
>
"sha256:c230b2806699b95d9974cf9ba2f93a2b8976b1d6992335f85aeb068f2061ef4d":
> { "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
> "source-repo": "default", "image-source":
> "subuser-internal-xpra-server" },
>
"sha256:63227a51d70b0b6e83b2da8cb8d22cb82f42cdc467eccf408129c3a933e1f7aa":
> { "image-source-hash": "7e679272789c7fc81c7f25ac6b1eca48e102a5ac",
> "source-repo": "default", "image-source": "xterm" },
>
"sha256:09f4a0db3e6306926305a83f41c5ef1eae58f3364c56cdd96d3716b0b84d828f":
> { "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
> "source-repo": "default", "image-source":
> "subuser-internal-xpra-client" },
>
"sha256:3b8eaa3bcd43df8f474e3502b9d8e6ce8c3a643d1553eae477433ae5924aec31":
> { "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
> "source-repo": "default", "image-source":
> "subuser-internal-xpra-server" },
>
"sha256:0564044bdecd3af917c0f68920569da9037033447dd7e719c280555fa7136e44":
> { "image-source-hash": "e59d0543cf7fb71ea0f1fbaa3e35c6aa77fe9990",
> "source-repo": "default", "image-source": "libdebian" },
>
"sha256:009fc5d1d49cdeea44776e29468fb470c4cb66bf4e267c9b67fd76b5bd540a0c":
> { "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
> "source-repo": "default", "image-source": "xpra" },
>
"sha256:e2866b6d689a62770b1d1b06fb773cb78f0a4db0d7db45b4c77de7decd4e6a5d":
> { "image-source-hash": "949e1a552e7b967cea2a786ade0b0a827bf49f45",
> "source-repo": "default", "image-source": "xpra" },
>
"sha256:74d3750334db59cbb718c141e754603aca025f93350c9327e0074ca834213d73":
> { "image-source-hash": "37a5d89fcc9938d5be62e8ea153bdcafe086398d",
> "source-repo": "default", "image-source":
> "subuser-internal-xpra-client" },
>
"sha256:0c8e037d7abb41e77d77b52cb04a2911f2969f949186b51e364e6a35f86e224d":
> { "image-source-hash": "b1968d5e991596e5adfd0099604e45d343908245",
> "source-repo": "default", "image-source": "libx11" },
>
"sha256:3a29930c21987a82d89216dcaa50cd14d6809f5b9de8ccd7a3f5cb95865dd1e7":
> { "image-source-hash": "04d06871700f77ca9d2be1303089b0aecd7c798d",
> "source-repo": "default", "image-source":
> "subuser-internal-xpra-server" } } |
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
>
<#298 (comment)>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ABU7-NwrSdZn56SVv3dJJblZ0R6zr1B6ks5rKCusgaJpZM4LOtph>.
>
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#298 (comment)
|
Yes, I can confirm it now works with keepassX and my own GnuCash subuser. |
I tried running iceweasel@default and xterm@default. Both hang with "Starting xpra server..."
I am on Parabola GNU/Linux-libre.
Commands entered, exactly:
Results of the last command:
Attached is /home/ben/.subuser/volumes/xpra/xterm/xpra-home/.xpra/Xorg.:100.log, renamed because Github won't upload .log files.
Xorg.:100.log.txt
The text was updated successfully, but these errors were encountered: