FS#74589 - [thunar] core dump after pressing Delete on a folder

Attached to Project: Arch Linux
Opened by Eduard de Jong (jongeduard) - Friday, 29 April 2022, 20:57 GMT
Last edited by Toolybird (Toolybird) - Monday, 09 October 2023, 20:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I pressed Delete to remove a folder, Thunar crashed. I am using a trash bin so I expected it to go there.
It was just after exiting my QEMU session with the image in that folder. It was a copy for testing so that's why I decided to remove it.

Seemed worth to me to check journalctl after the crash and report this core dump, hoping it may be helpful for any developer to improve things. It's not completely the first time that I notice such a crash, which is a motivation for reporting as well.

Attached is a text file with the the core dump in question.
What I notice in the core dump output is that on the 4th line of the stack trace is thunar-media-tags-plugin.so mentioned.
So thunar-media-tags-plugin seems involved as well.

Additional info:
* The mounted filesystem that I was performing the delete action on is an NTFS filesystem, using the ntfs-3g driver.
* My desktop environment is xfce4 with xfce4-goodies installed.
* Package versions:
- linux: 5.17.4.arch1-1
- ntfs-3g: 2021.8.22-1
- thunar: 4.16.11-1
- thunar-media-tags-plugin: 0.3.0-2
   Thunar-core-dump_2022-04-29.t... (23.5 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 09 October 2023, 20:23 GMT
Reason for closing:  Upstream
Additional comments about closing:  This doesn't appear to an Arch packaging issue. If still reproducible, please provide a fresh backtrace with debug info and report upstream.
Comment by Eduard de Jong (jongeduard) - Friday, 29 April 2022, 21:25 GMT
Small correction: thunar-media-tags-plugin was not in the stack trace, but just a mentioned laoded module. My eyes finished reading too quickly I think.
Comment by Evangelos Foutras (foutrelis) - Saturday, 30 April 2022, 03:26 GMT
Enabled debug symbols in thunar 4.16.11-2. If it crashes again (and you're running the new version), you should be able to install debuginfod and get a symbolized backtrace with `coredumpctl gdb` and then `bt` in gdb.
Comment by Eduard de Jong (jongeduard) - Tuesday, 03 May 2022, 19:46 GMT
Thanks and nice to learn new things everyday. I got a new crash now, both the coredump and the backtrace with the source code line numbers are in the attached file now (I just copied the text form the terminal again), and I also have some extra information:
I extracted an archive with Thunar archive plugin first (it's in the backtrace), then in another Thunar window I copied a folder with a large QEMU image inside it, but it was not my intention to copy that so I cancelled that.
And then I decided to delete that what was already copied by pressing delete. This made Thunar crash, both my Thunar windows closed instantly (so it's the same process).

Again nice to learn how to do this.
I also use a gnome desktop, on another computer, I have had crashes there too (entire desktop) and maybe i'll report that as well, as I see that the the gnome-shell has been added to the list on https://debuginfod.archlinux.org as well. Although I know that currently a lot of attention already goes to gnome (due to the new ubuntu and fedora releases).
   Thunar_core-dump_and_backtrac... (25.8 KiB)
Comment by Evangelos Foutras (foutrelis) - Wednesday, 04 May 2022, 03:00 GMT
Added debugging information to thunar-archive-plugin too. Let's see if it crashes again in the same spot and what the trace looks like.
Comment by Eduard de Jong (jongeduard) - Saturday, 07 May 2022, 20:08 GMT
I now did something in a different way, I tried extracting an XZ file of 3.4 GB big (containing a downloaded FreeBSD image) by right click, I didn't see much response so I cancelled it, an I got an error dialog that the command failed and I had to click that away, and I got this dialog twice. After clicking cancel for the third time the extraction dialog itself finally closed.

But Thunar crashed as well. Debug output:

#0 g_type_check_instance_cast (type_instance=0x7fd594083240, iface_type=0x557834cbd8e0 [None])
at ../glib/gobject/gtype.c:4125
#1 0x00007fd59db3c1d5 in tap_provider_child_watch_destroy (user_data=<optimized out>)
at /build/thunar-archive-plugin/src/thunar-archive-plugin-0.5.0/thunar-archive-plugin/tap-provider.c:609
#2 0x00007fd5a859d003 in g_source_callback_unref (cb_data=0x557835337e60) at ../glib/glib/gmain.c:1702
#3 g_source_callback_unref (cb_data=0x557835337e60) at ../glib/glib/gmain.c:1695
#4 0x00007fd5a85a161a in g_source_destroy_internal (source=0x5578352f4800, context=0x5578349c39b0, have_lock=1)
at ../glib/glib/gmain.c:1367
#5 0x00007fd5a85a3298 in g_main_dispatch (context=0x5578349c39b0) at ../glib/glib/gmain.c:3447
#6 g_main_context_dispatch (context=0x5578349c39b0) at ../glib/glib/gmain.c:4135
#7 0x00007fd5a85f99e9 in g_main_context_iterate.constprop.0
(context=context@entry=0x5578349c39b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
at ../glib/glib/gmain.c:4211
#8 0x00007fd5a85a06c5 in g_main_context_iteration (context=context@entry=0x5578349c39b0, may_block=may_block@entry=1)
at ../glib/glib/gmain.c:4276
#9 0x00007fd5a87be80e in g_application_run (application=application@entry=0x5578349db0f0, argc=-693651036,
argc@entry=2, argv=argv@entry=0x7fffd6a7bb48) at ../glib/gio/gapplication.c:2569
#10 0x00005578337a917d in main (argc=2, argv=0x7fffd6a7bb48) at /usr/src/debug/thunar-4.16.11/thunar/main.c:86

If new things happen I will report it here as well if it serves extra info.

Loading...