Skip to content
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

xpra won't start (after update?) #4376

Closed
angus73 opened this issue Oct 8, 2024 · 6 comments
Closed

xpra won't start (after update?) #4376

angus73 opened this issue Oct 8, 2024 · 6 comments
Labels
bug Something isn't working invalid This doesn't seem right packaging

Comments

@angus73
Copy link

angus73 commented Oct 8, 2024

Describe the bug
Maybe after some recent update (unfortunately I am not able to say if so, nor which one), my xpra doesn't work any more: on the client I see
Error: failed to receive anything, not an xpra server? could also be the wrong protocol, username, password or port or the session was not found
and in the server I find
Xorg-for-Xpra-S42843: ../../../include/privates.h:121: dixGetPrivateAddr: Assertion 'key->initialized' failed.[...] (EE) Please also check the log file at "/run/user/1000/xpra/S42843/Xorg.log" for additional information.

To Reproduce
Steps to reproduce the behavior:

  1. server command
    xpra start :666

  2. client command
    xpra attach ssh://myserver/666 --start=xterm

  3. specific action to trigger the bug
    the bug triggers without any specific action

System Information (please complete the following information):

  • Server OS: Fedora 39
  • Client OS: Ubuntu 22.04
  • Xpra Server Vesion 6.1.3-r0
  • Xpra Client Version 6.1.3-r0

I did try many ways to get this solved by myself, including removing xpra from both the client and the server, and also removing all files named xpra in the whole system, to have a clean configuration, but didn't help.

Additional context
I have two physical screens on the server, don't know if it can be related. It can be true that the problem appeared after I connected the second screen (on a second PCI display adapter, which I installed for the purpose), but I cannot be sure about that.

Many thanks in advance

client.txt
server.txt

@angus73 angus73 added the bug Something isn't working label Oct 8, 2024
@totaam
Copy link
Collaborator

totaam commented Oct 8, 2024

Please also check the log file at "/run/user/1000/xpra/S42843/Xorg.log

You probably won't find anything interesting there anyway. This is not an xpra error.

This is usually caused by driver or system updates messing up Xorg.
Rebooting usually fixes these issues.
Or applying more system updates.

@totaam totaam closed this as not planned Won't fix, can't repro, duplicate, stale Oct 8, 2024
@totaam totaam added invalid This doesn't seem right packaging labels Oct 8, 2024
@angus73
Copy link
Author

angus73 commented Oct 8, 2024

Thanks, I tried again just after updating and rebooting both client and server and it still fails. Is there any hint I can follow? Do you think there's anything relevant in the attached logfiles, which I can use to go further in the right direction and ask for help to the right people, group, forum, etc? Many many thanks

@totaam
Copy link
Collaborator

totaam commented Oct 9, 2024

and rebooting both client and server and it still fails

This is a server problem.

Is there any hint I can follow?

This could be caused by gstreamer so this may work:
#3964 (comment)
Start your server with --video-encoders=all,-gstreamer --video-decoders=all,-gstreamer - though this should already be the default in 6.1.x
Or even removing the gstreamer bindings altogether.


This may be caused by: dri2: Protect against dri2ClientPrivate assertion failures or xorg-server-1.20.{7,8} crash with dixGetPrivateAddr: Assertion `key->initialized' failed when starting spice-gtk


By far, the easiest solution is to switch to Xvfb in

# xvfb = Xvfb -nolisten tcp -noreset \

@angus73
Copy link
Author

angus73 commented Oct 10, 2024

By far, the easiest solution is to switch to Xvfb in

# xvfb = Xvfb -nolisten tcp -noreset \

That worked, thank you very much!
(Are there any drawbacks in it?)

@totaam
Copy link
Collaborator

totaam commented Oct 10, 2024

(Are there any drawbacks in it?)

Too many to list, some can be found here https://github.com/Xpra-org/xpra/blob/master/docs/Usage/Xdummy.md

@totaam
Copy link
Collaborator

totaam commented Oct 10, 2024

FWIW: I've installed xpra latest stable (6.1.3 at time of writing) in a F39 VM and dummy worked out of the box - no need to switch to Xvfb.
So there must be something different on your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working invalid This doesn't seem right packaging
Projects
None yet
Development

No branches or pull requests

2 participants