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#78127 - [xpra] glib seg fault

Attached to Project: Community Packages
Opened by Thomas Weingartner (weingo2) - Wednesday, 05 April 2023, 16:14 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 10 May 2023, 22:55 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When running xpra I am getting a core dump when opening and closing a new windows. This problem has been occurring since I updated the glib2 package about a month ago. I am running glib2 2.74.0-2
I'm assuming this should be reported to the upstream, but I am not sure where to report this bug upstream. Does the package maintainer know where I can report it?
Here is the stack trace in case someone has a fix:
Stack trace of thread 1457:
#0 0x00007f76553d01f1 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0 + 0x391f1)
#1 0x00007f76553b67e3 g_object_ref (libgobject-2.0.so.0 + 0x1f7e3)
#2 0x00007f7653547d01 gdk_x11_window_foreign_new_for_display (libgdk-3.so.0 + 0x9ad01)
#3 0x00007f76553934f6 n/a (libffi.so.8 + 0x74f6)
#4 0x00007f765538ff5e n/a (libffi.so.8 + 0x3f5e)
#5 0x00007f7655392b73 ffi_call (libffi.so.8 + 0x6b73)
#6 0x00007f76555ca941 n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x2b941)
#7 0x00007f76555cb57a n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x2c57a)
#8 0x00007f76555c9290 n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x2a290)
#9 0x00007f76555bc37e n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x1d37e)
#10 0x00007f76502db896 n/a (gdk_bindings.cpython-310-x86_64-linux-gnu.so + 0x25896)
#11 0x00007f76502e002b n/a (gdk_bindings.cpython-310-x86_64-linux-gnu.so + 0x2a02b)
#12 0x00007f76502d8cb5 n/a (gdk_bindings.cpython-310-x86_64-linux-gnu.so + 0x22cb5)
#13 0x00007f7653530b0f n/a (libgdk-3.so.0 + 0x83b0f)
#14 0x00007f765353883f n/a (libgdk-3.so.0 + 0x8b83f)
#15 0x00007f76534de029 gdk_display_get_event (libgdk-3.so.0 + 0x31029)
#16 0x00007f7653538a68 n/a (libgdk-3.so.0 + 0x8ba68)
#17 0x00007f765547653b g_main_context_dispatch (libglib-2.0.so.0 + 0x5a53b)
#18 0x00007f76554d3219 n/a (libglib-2.0.so.0 + 0xb7219)
#19 0x00007f7655475c7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
#20 0x00007f76529d8e4f gtk_main (libgtk-3.so.0 + 0x1d8e4f)
#21 0x00007f76553934f6 n/a (libffi.so.8 + 0x74f6)
#22 0x00007f765538ff5e n/a (libffi.so.8 + 0x3f5e)
#23 0x00007f7655392b73 ffi_call (libffi.so.8 + 0x6b73)
#24 0x00007f76555ca941 n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x2b941)
#25 0x00007f76555c9290 n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x2a290)
#26 0x00007f7656762f9c PyObject_Call (libpython3.10.so.1.0 + 0x162f9c)
#27 0x00007f7656748e4b _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x148e4b)
#28 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#29 0x00007f765674ae89 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14ae89)
#30 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#31 0x00007f765674676a _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14676a)
#32 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#33 0x00007f765674676a _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14676a)
#34 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#35 0x00007f7656746336 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x146336)
#36 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#37 0x00007f7656746336 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x146336)
#38 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#39 0x00007f7656746336 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x146336)
#40 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#41 0x00007f7656746336 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x146336)
#42 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#43 0x00007f7656746336 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x146336)
#44 0x00007f76567570e9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1570e9)
#45 0x00007f7656746336 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x146336)
#46 0x00007f7656744f80 n/a (libpython3.10.so.1.0 + 0x144f80)
#47 0x00007f76567f39e4 PyEval_EvalCode (libpython3.10.so.1.0 + 0x1f39e4)
#48 0x00007f7656804383 n/a (libpython3.10.so.1.0 + 0x204383)
#49 0x00007f76567ffaea n/a (libpython3.10.so.1.0 + 0x1ffaea)
#50 0x00007f76566a223f n/a (libpython3.10.so.1.0 + 0xa223f)
#51 0x00007f76566a1ef0 _PyRun_SimpleFileObject (libpython3.10.so.1.0 + 0xa1ef0)
#52 0x00007f76566a28a3 _PyRun_AnyFileObject (libpython3.10.so.1.0 + 0xa28a3)
#53 0x00007f7656810b5d Py_RunMain (libpython3.10.so.1.0 + 0x210b5d)
#54 0x00007f76567e4f3b Py_BytesMain (libpython3.10.so.1.0 + 0x1e4f3b)
#55 0x00007f765643c790 n/a (libc.so.6 + 0x23790)
#56 0x00007f765643c84a __libc_start_main (libc.so.6 + 0x2384a)
#57 0x000055b1f0e2b045 _start (python3.10 + 0x1045)

Steps to reproduce:
1. Run xpra and attach to the session
2. Open and close windows until a core dump occurs

This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 10 May 2023, 22:55 GMT
Reason for closing:  Upstream
Comment by Toolybird (Toolybird) - Wednesday, 05 April 2023, 21:37 GMT
> I am running glib2 2.74.0-2

Your glib2 is *very* out of date. We are currently on 2.76.1-1. Please bring your system *fully* up-to-date, reboot, then try again. Also, your backtrace is missing debug symbols. Please follow the instructions at [1] to produce a proper backtrace, and as already mentioned in your other ticket ( FS#77968 ) you might have to report this upstream to the xpra developers.

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod
Comment by Thomas Weingartner (weingo2) - Thursday, 06 April 2023, 13:52 GMT
My bad, I copied the wrong version number I am on 2.76.1-1. Sorry, I thought the maintainer here would be different. I'll probably end up having to report this to the xpra developers, but I was trying to get an opinion from the package that is producing the seg fault this time.
When I try and run debuginfod-find on xpra I get the following error:
Cannot extract build-id from /usr/bin/xpra: invalid `Elf' handle
Comment by Thomas Weingartner (weingo2) - Thursday, 06 April 2023, 14:10 GMT
Never mind, I figured out the full trace, and I attached the file.
   gdb.txt (379.5 KiB)
Comment by Toolybird (Toolybird) - Tuesday, 11 April 2023, 07:09 GMT
There's some deep python/gobject stuff going on in there. Please open an upstream issue and attach the trace there. Hopefully upstream can make some sense out of it.
Comment by Thomas Weingartner (weingo2) - Tuesday, 11 April 2023, 11:48 GMT
Yeah, that was a much deeper stack frame than I typically look at. Thank you for your help; I will open upstream at Xpra. Thank you for your patience and for working on Arch Linux!
Comment by Toolybird (Toolybird) - Wednesday, 10 May 2023, 22:54 GMT

Loading...