Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77968 - [xpra] 4.4.4-1 Crashing upon windows opening and closing

Attached to Project: Community Packages
Opened by Thomas Weingartner (weingo2) - Thursday, 23 March 2023, 13:11 GMT
Last edited by Toolybird (Toolybird) - Saturday, 25 March 2023, 20:53 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Hello,
This package is one of my most utilized packages on my arch system. About two weeks (~ week of March 6th) ago I upgraded xpra and this bug appeared. I use xpra to host a xwin server on my main machine and mainly run xterm with command line tools that bring up plot windows. I also normally bind the xpra session to localhost and tunnel the connection over ssh. Since updating xpra, the xpra xserver has been crashing and going into an UNKNOWN state. This happens when I spawn a window from the command line or close a window. Xpra does not crash happen every time a window is opened or closed. It is frequent enough that if I am using my current setup I am guaranteed to see a crash sometime during an hour of work.

I appreciate the time of anyone that works on this. If more specific information of my system is needed, please let me know.

Additional info:
* package version(s) : 4.4.4-1
* config and/or log files etc.
command: xpra start --start=xterm --bind-ws=localhost:10001 --system-tray=yes --webcam=yes --bell=yes

Steps to reproduce:
1. Spawn an xpra server using the command in additional info
2. connect to the server using xpra on another machine (another arch machine or windows machine)
3. open and close windows from xterm, eventually the whole xserver should crash
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 25 March 2023, 20:53 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by Toolybird (Toolybird) - Friday, 24 March 2023, 03:09 GMT
The Arch packaging update to 4.4.4-1 was minor so this suggests an upstream issue. Have you reported it upstream? When you say "crash", is anything recorded in the system journal/log files or does "coredumpctl" report anything? You'll need to better debug this somehow.
Comment by Thomas Weingartner (weingo2) - Friday, 24 March 2023, 13:24 GMT
I checked the journalctl log and found a systemd-coredump entry for the xpra process. Does a core dump suggest anything to you? I am not sure how to get more debug info from systemd. I commonly use the debugger on code but don't do system level programming.

My arch knowledge is decent but not great; what does it mean to report to upstream?
Comment by Antonio Rojas (arojas) - Friday, 24 March 2023, 13:34 GMT
It means you need to report this to the xpra developers at https://github.com/Xpra-org/xpra/issues

And, since it is a crash, you need to attach a backtrace. https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment by Thomas Weingartner (weingo2) - Saturday, 25 March 2023, 12:59 GMT
Oh wow, I did not realize there was all this debug functionality for packages in arch. This is cool. I realized that the seg faults I am getting are for the python3.10 binary and not the xpra binary. Looks like the binary is dumping inside a gdk_x11_window_foreign_new_for_display
function which tells me its something wrong with the gdk python binding on my system.

Thank you very much for your help with basic arch information, I will report this issue elsewhere now that I have a better understanding of the problem.

Loading...