Applications (Pluma / Thunar) crash on "drag and drop"
Hello:
Running on an up to date Devuan Beowulf:
groucho@devuan:~$ uname -a
Linux devuan 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
groucho@devuan:~$
My xorg is 1:7.7+19 amd64 and the video drivers are nvidia-legacy-340xx. I don't use nouveau drivers as they don't work properly with three monitors.
I started with this happening with Thunar and after not being able to debug the problem and moving to PCManFM, discovered it also happens with Pluma.
It does not happen with PCManFM.
See here: https://gitlab.xfce.org/xfce/thunar/-/issues/532
For the time being, I cannot say if it happens with other programs.
Basically, it boils down to this:
I. in Thunar 1.8.4 from Xfce 4.12.
Crashes when I want to "drag and drop" a file from a folder into another folder. Does not crash if I want to "drag and drop" a file from the desktop to a Thunar window.
The crash occurrs the very instant I move the mouse to "drag" the file I am "holding" by depressing the mouse's right button.
ie:
- Open Thunar.
- Select a folder or file (any/anywhere).
- Place the mouse pointer on it and press the left button.
Note: up to this point nothing has happened.
- With the pointer on the selected folder/file and left button still pressed, at the very instant I (minimally) move the mouse, Thunar crashes. ie: if I don't move the mouse, Thunar does not crash.
Happens always. If I turn compositing off ... ie: Applications > Settings > Window Manager Tweaks > Compositor and check "Enable display compositing". ... it does no happen.
Starting Thunar from a terminal and generating the crash shows me this output:
groucho@devuan:~$ thunar
(thunar:11542): Gdk-ERROR **: 11:30:45.053: The program 'thunar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 12824 error_code 3 request_code 141 (Composite) minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
groucho@devuan:~$
II. in Pluma
- Open a *.txt file in Pluma.
- Paint a character or a set of characters, no difference.
- Place the mouse pointer on it and press the left button.
Note: like with Thunar, up to this point nothing has happened.
- Now, just like with Thunar, with the pointer on the selected text and the left button still pressed, at the very instant I (minimally) move the mouse, Pluma crashes.
It's not that I was intent on moving text anywhere by means of "Drag and Drop". I was doing a "Paint and Cut/Copy" and accidentally "Dragged" after "Paint" but before "Cut/Copy".
Happens always.
Like with Thunar, if I don't move the mouse pointer, Pluma does not crash and if I turn compositing off, it does not happen.
Starting Pluma from a terminal and generating the crash shows me this output:
groucho@devuan:~$ pluma
(pluma:20299): Gdk-ERROR **: 18:19:08.594: The program 'pluma' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 4809 error_code 3 request_code 141 (Composite) minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
groucho@devuan:~$
As you can see, the text "error_code 3 request_code 141 (Composite) minor_code 8)" is common to both printouts.
/var/log/kern.log has this type of entries each time.
Mar 21 18:19:08 devuan kernel: [ 6403.316130] traps: pluma[20299] trap int3 ip:7f7c1bd3dc75 sp:7ffc5303a700 error:0 in libglib-2.0.so.0.5800.3[7f7c1bd05000+7e000]
All make reference to "trap int3" and "error:0 in libglib-2.0.so.0.5800.3".
I installed gdb to try to get a trace but running as a user did not produce a result. I then followed the instructions in case no trace was obtained and tried to run it gdb as root.
As a result, my mouse pointer froze into a 'clenched hand' and everything else was unresponsive. ie: did not get to run '(gdb) thread apply all bt full' or 'bt'.
In both cases the only way to regain control of my box was to kill the session (ctrl+alt+bcksp) and log in again or drop into a virtual console, log in and kill the application and xfce-terminal.
Please let me know if you need more data.
Thanks in advance,
Best.