Thanks, those stack traces are exactly what we needed. I can't find any
other reports of those crashes, but that's likely just because nobody
else had debugged it with GDK_SYNCHRONIZE yet...
Next please report the bug to the developers at
https://gitlab.gnome.org/GNOME/gtk/-/issues and remember
** Summary changed:
- GDK/GTK app crash when performing drag operation
+ GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <-
gdk_window_cache_get <- drag_context_find_window_cache <-
gdk_x11_drag_context_find_window)
--
You received this bug notification because you
** Attachment added: "--gtk-debug=all output from thunar"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467187/+files/thunar-debug3.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's the gdb & gtk-debug=all output from thunar.
** Attachment added: "thunar gdb output"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467186/+files/thunar-gdb.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm planning on rebooting soon which will hopefully fix whatever is
preventing thunar from displaying. I'll that output as well, if I can.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
** Attachment added: "--gtk-debug=all output from gucharmap"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467105/+files/gucharmap-debug.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ah, gotcha. My gdb skills are a bit rusty.
For some reason, thunar wouldn't come up so I used gucharmap. I'm
attaching the output as well from using --gdk-debug=all.
** Attachment added: "gdb backtrace output"
... then type 'cont' in gdb, then crash thunar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash when performing drag operation
To manage notifications about this bug
I mean start thunar graphically, then attach to it with gdb from ssh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash when performing drag operation
To manage
I tried that as I mentioned above. It doesn't crash in that scenario.
I can ssh in from another computer and run thunar but I can't reproduce
the crash this way. This is why I think it might have to do with the
X11 server or lightdm.
I can see if I can mess with xauth to run via ssh and keep it
Try running gdb from within ssh :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash when performing drag operation
To manage notifications about this bug go to:
Hi Daniel,
I never removed GDK_SYNCHRONIZE from /etc/environment. It's been set
that way for a few reboots. In addition, I confirmed it was set to 1
before running gdb.
I'm wondering if you're not getting as much as you'd expect from the
backtrace because I had to kill the thunar process.
Please remember to keep GDK_SYNCHRONIZE=1 in your /etc/environment so we
can see the proper stack trace of each crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash
Strangely that backtrace is incomplete. There should be more than two
frames...
(gdb) bt
#0 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
#1 0x14698a9c in g_log_writer_default (log_level=6,
fields=0x7fffc920, n_fields=6, user_data=0x0) at
I tried install all the debug (dbg), dev and source packages I could
find for each of the libraries that might be an issue. I attached the
result of running thunar through gdb. FYI, the crash hangs mouse in the
display manager, forcing me to kill the subprocess via ssh. The kill
takes place
Thanks for those crash reports. Unfortunately they don't have any stack
traces for some reason...
Since you seem to be pretty technical, the next steps I suggest are:
1. Install the debug symbols for gtk and apps like thunar.
2. Attach 'gdb' to thunar or any affected app.
3. Reproduce the
** Attachment added: "--gtk-debug=all output from gucharmap"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5466345/+files/gucharmap-debug.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "--gtk-debug=all output from thunar"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5466346/+files/thunar-debug.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "--gtk-debug=all output from font-manager"
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5466344/+files/font-manager-debug.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Daniel,
I've been digging a little deeper on this issue. First, I look for
other binaries in /usr/bin that dynamically link to either libgtk or
libgdk (at least for starters). In short, I found other binaries that
exhibit the same issue. I may have narrowed it down to possibly
Unfortunately the link in comment #9 shows no usable details, only that
'thunar' crashed with signal 5 on Tue Jan 12 20:19:56 2021
Please attach links to new crash reports as you find them, although it
appears the machine that last crash report came from has not reported
any crashes since
Hi,
Is there any other information I can provide to help resolve this issue?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash when performing drag operation
Hi Daniel,
Here's the latest crash file:
https://errors.ubuntu.com/oops/3cd6616e-554e-11eb-8c66-fa163e6cac46
Let me know if you have any trouble accessing it.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, the result of GDK_SYNCHRONIZE=1 would be just better quality crash
reports. No extra logging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash when performing drag
Hi Daniel,
I figured as much given I was adding it to a file in /etc rather than a
home shell rc file. I added it before I rebooted earlier. I'm just not
sure where I'm supposed to look for the extra logging, presuming that's
the intended result.
Thank.
--
You received this bug notification
After adding GDK_SYNCHRONIZE=1 to /etc/environment you will probably
need to reboot before it takes effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911036
Title:
GDK/GTK app crash when
Hi Daniel,
I was able to get a few minutes to reboot. I also applied all the
latest updates and created a new user with only the default home
directory contents. I was able to reproduce the issue with thunar.
Hopefully, you can see the crash file here:
It appears that crash report has not been retraced so does not have any
useful debug info in it. I don't know if that's because of a missing
core dump or because the infrastructure has failed (both are equally
likely in my experience).
If you would like to get to the bottom of the issue then I
As this server is used heavily used, rebooting is not that convenient.
Is there a way to force crashdb.conf to be reloaded? I tried restarting
apport & whoopsie services with systemctl but not sure if that worked.
There's a recent crash file for thunar that may or may not have been
produced from
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
30 matches
Mail list logo
