xpra icon
Bug tracker and wiki

Custom Query (1813 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (10 - 12 of 1813)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ticket Resolution Summary Owner Reporter
#2025 fixed client hangs handling popup window Antoine Martin Antoine Martin
Description

Running the commented out example from r20917 then stopping it with a control-c can hang the client (fedora 29 + gnome shell), most of the time... and enabling -d all makes the crash disappear.

The window that's causing this hang is:

process_new_common: [22, 0, 0, 52, 12, \
    {'xid': '0xe0001c', 'title': 'min=(50, 10) - max=(50, 10)', 'client-machine': 'desktop', \
     'pid': 31727, 'group-leader-xid': 14680065, 'window-type': ('NORMAL',), 'override-redirect': True}], \
    metadata={'window-type': ('NORMAL',), 'xid': '0xe0001c', 'title': 'min=(50, 10) - max=(50, 10)', \
    'override-redirect': True, 'client-machine': 'desktop', 'pid': 31727, 'group-leader-xid': 14680065}, OR=True
#2024 fixed xpra crashes when showing File Dialog of Mono Applications Alexey Stukalov Alexey Stukalov
Description

I am trying to run MaxQuant (as LD_PRELOAD=/usr/lib/libasan.so xpra start :69 --start=/usr/bin/maxquant), which is .NET Framework 4.5 application, under ArchLinux using Mono 5.16. Locally it runs fine, but under both xpra 2.3.4 and 2.4 it crashes when I try to open "File..." dialog. Here's the stack trace:

AddressSanitizer:DEADLYSIGNAL
=================================================================
==12405==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7fb953f1a715 bp 0x7ffc5e85aad0 sp 0x7ffc5e85a248 T0)
==12405==The signal is caused by a READ memory access.
==12405==Hint: address points to the zero page.
    #0 0x7fb953f1a714 in __strlen_avx2 (/usr/lib/libc.so.6+0x15f714)
    #1 0x7fb95405950b in __interceptor_strlen /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:299
    #2 0x7fb953a2e510 in PyString_FromString (/usr/lib/libpython2.7.so.1.0+0xb6510)
    #3 0x7fb9465b82b2 in __pyx_pf_4xpra_3x11_8bindings_13core_bindings_16_X11CoreBindings_12XGetAtomName xpra/x11/bindings/core_bindings.c:3496
    #4 0x7fb9465b7cf7 in __pyx_pw_4xpra_3x11_8bindings_13core_bindings_16_X11CoreBindings_13XGetAtomName xpra/x11/bindings/core_bindings.c:3437
    #5 0x7fb953a5e6d6 in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe66d6)
    #6 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #7 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #8 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #9 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #10 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #11 0x7fb953a6397e in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xeb97e)
    #12 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #13 0x7fb953a6397e in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xeb97e)
    #14 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #15 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #16 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #17 0x7fb953a63dbe in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xebdbe)
    #18 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #19 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #20 0x7fb953a4ae0e in function_call.lto_priv.233 (/usr/lib/libpython2.7.so.1.0+0xd2e0e)
    #21 0x7fb953a020e2 in PyObject_Call (/usr/lib/libpython2.7.so.1.0+0x8a0e2)
    #22 0x7fb953a6e49e in instancemethod_call.lto_priv.148 (/usr/lib/libpython2.7.so.1.0+0xf649e)
    #23 0x7fb953a020e2 in PyObject_Call (/usr/lib/libpython2.7.so.1.0+0x8a0e2)
    #24 0x7fb953aa6de3 in slot_tp_init.lto_priv.1132 (/usr/lib/libpython2.7.so.1.0+0x12ede3)
    #25 0x7fb953a202c4 in type_call.lto_priv.59 (/usr/lib/libpython2.7.so.1.0+0xa82c4)
    #26 0x7fb953a020e2 in PyObject_Call (/usr/lib/libpython2.7.so.1.0+0x8a0e2)
    #27 0x7fb953a6380d in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xeb80d)
    #28 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #29 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #30 0x7fb953a4ae0e in function_call.lto_priv.233 (/usr/lib/libpython2.7.so.1.0+0xd2e0e)
    #31 0x7fb953a020e2 in PyObject_Call (/usr/lib/libpython2.7.so.1.0+0x8a0e2)
    #32 0x7fb953a6e49e in instancemethod_call.lto_priv.148 (/usr/lib/libpython2.7.so.1.0+0xf649e)
    #33 0x7fb953a020e2 in PyObject_Call (/usr/lib/libpython2.7.so.1.0+0x8a0e2)
    #34 0x7fb953ab87d0 in PyEval_CallObjectWithKeywords (/usr/lib/libpython2.7.so.1.0+0x1407d0)
    #35 0x7fb94a8f0cdb  (/usr/lib/python2.7/site-packages/gobject/_gobject.so+0x17cdb)
    #36 0x7fb94a8b33d4 in g_closure_invoke (/usr/lib/libgobject-2.0.so.0+0x303d4)
    #37 0x7fb94a89f99e  (/usr/lib/libgobject-2.0.so.0+0x1c99e)
    #38 0x7fb94a8a66df in g_signal_emitv (/usr/lib/libgobject-2.0.so.0+0x236df)
    #39 0x7fb94a8e9337  (/usr/lib/python2.7/site-packages/gobject/_gobject.so+0x10337)
    #40 0x7fb945ebb644 in __Pyx_PyObject_Call xpra/x11/gtk2/gdk_bindings.c:21153
    #41 0x7fb945e66299 in __pyx_f_4xpra_3x11_4gtk2_12gdk_bindings__maybe_send_event xpra/x11/gtk2/gdk_bindings.c:11188
    #42 0x7fb945e6ed34 in __pyx_f_4xpra_3x11_4gtk2_12gdk_bindings__route_event xpra/x11/gtk2/gdk_bindings.c:12154
    #43 0x7fb945e80d40 in __pyx_f_4xpra_3x11_4gtk2_12gdk_bindings_x_event_filter xpra/x11/gtk2/gdk_bindings.c:13863
    #44 0x7fb949b45e1e  (/usr/lib/libgdk-x11-2.0.so.0+0x56e1e)
    #45 0x7fb949b4717f  (/usr/lib/libgdk-x11-2.0.so.0+0x5817f)
    #46 0x7fb949b48c89  (/usr/lib/libgdk-x11-2.0.so.0+0x59c89)
    #47 0x7fb949b48d2e  (/usr/lib/libgdk-x11-2.0.so.0+0x59d2e)
    #48 0x7fb94adda3ce in g_main_context_dispatch (/usr/lib/libglib-2.0.so.0+0x6b3ce)
    #49 0x7fb94addbf88  (/usr/lib/libglib-2.0.so.0+0x6cf88)
    #50 0x7fb94addcf61 in g_main_loop_run (/usr/lib/libglib-2.0.so.0+0x6df61)
    #51 0x7fb949ecedf2 in gtk_main (/usr/lib/libgtk-x11-2.0.so.0+0x12bdf2)
    #52 0x7fb94a5688c9  (/usr/lib/python2.7/site-packages/gtk-2.0/gtk/_gtk.so+0x1888c9)
    #53 0x7fb953a63a42 in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xeba42)
    #54 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #55 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #56 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #57 0x7fb953a63dbe in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xebdbe)
    #58 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #59 0x7fb953a6397e in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xeb97e)
    #60 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #61 0x7fb953a63dbe in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xebdbe)
    #62 0x7fb953a5e9cf in PyEval_EvalFrameEx (/usr/lib/libpython2.7.so.1.0+0xe69cf)
    #63 0x7fb953ab90d9 in PyEval_EvalCodeEx (/usr/lib/libpython2.7.so.1.0+0x1410d9)
    #64 0x7fb953ad8309 in PyEval_EvalCode (/usr/lib/libpython2.7.so.1.0+0x160309)
    #65 0x7fb953ae3a80 in run_mod (/usr/lib/libpython2.7.so.1.0+0x16ba80)
    #66 0x7fb953ae5396 in PyRun_FileExFlags (/usr/lib/libpython2.7.so.1.0+0x16d396)
    #67 0x7fb953ae5c83 in PyRun_SimpleFileExFlags (/usr/lib/libpython2.7.so.1.0+0x16dc83)
    #68 0x7fb953ac1082 in Py_Main (/usr/lib/libpython2.7.so.1.0+0x149082)
    #69 0x7fb953ddf222 in __libc_start_main (/usr/lib/libc.so.6+0x24222)
    #70 0x55eecd54b779 in _start (/usr/bin/python2.7+0x779)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/usr/lib/libc.so.6+0x15f714) in __strlen_avx2
==12405==ABORTING

So it seems X11's XGetAtomName() returns NULL, which crashes v[:]. Indeed, when I tried to fix it by returning None for v==NULL, the crash was gone. But neither I see the dialog window (the UI goes into modal mode for the invisible window, which I can close by pressing "Esc" on the keyboard).

#2021 fixed Automated tests: On server shutdown, Xpra GUI is launched J. Max Mena J. Max Mena
Description

As the title states, when running the automated tests (once you get them to the state that they can successfully spin up a server and attach the client), after each test run completes, the tests then spawn the Xpra GUI. To me, it looks like the command that is supposed to stop the server is actually stopping the server, but is also somehow launching the Xpra GUI simultaneously.

Some background info:

The machine in question is a Fedora 28 VM running the latest Beta package from /beta. No OpenGL for now, so I'm only running the A/V tests for now to make sure I can get a successful run with some kind of output data.

I'm running the tests by spinning up a start-desktop session like so:

xpra start-desktop --bind-ssh=0.0.0.0:20000 --start="xrandr -s 1280x720" --start="xterm -e 'python ./test_measure_perf.py config_just_av ./myfirst.csv 1 2 > ./myfirst.log'" --no-daemon

Upon completion of each test run, I end up in a situation where the tests are still running but not going anywhere because it's waiting on...something? If I attach a session to the start-desktop wrapper, I see that there's an Xterm running and the Xpra GUI. The Xterm indicates the tests have paused while it waits for the GUI to disappear. If I kill the GUI's PID, the next round of tests start and everything continues normally, until that runs completion. At which point it spawns a new GUI and waits on it, over and over again.

So I'm not sure if I haven't ended up in a weird corner case, or there's a bug in the tests as this is a totally new situation. I'll attach a screenshot in a minute to show you what I'm seeing.

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Note: See TracQuery for help on using queries.