Dear Maintainers,

This application crashes with a SIGSEGV when attempting to start it while a MTP
device is mounted through GVFS. When the device is plugged but not mounted, the
application starts, but crashes when attempting to mount the device by clicking
on it. I did not try to reproduce the issue with a different device.

Below is a crash report of starting baobab with the device already mounted.

==========

Thread 1 "baobab" received signal SIGSEGV, Segmentation fault.
baobab_location_list_volume_changed (self=0x555555762950,
volume=0x55555572a910) at src/baobab.p/baobab-location-list.c:881
warning: 881    src/baobab.p/baobab-location-list.c: No such file or directory
(gdb) bt
#0  baobab_location_list_volume_changed (self=0x555555762950,
volume=0x55555572a910) at src/baobab.p/baobab-location-list.c:881
#1  0x000055555556c99d in baobab_location_list_mount_added
(self=0x555555762950, mount=0x555555ce9290) at src/baobab.p/baobab-location-
list.c:1142
#2  0x00007ffff7c07950 in g_closure_invoke () from /lib/x86_64-linux-
gnu/libgobject-2.0.so.0
...
#14 0x00007ffff7d3dedd in g_application_run () from /lib/x86_64-linux-
gnu/libgio-2.0.so.0
#15 0x0000555555563e9f in _vala_main (args=0x7fffffffdfa8, args_length1=1) at
src/baobab.p/main.c:58
#16 main (argc=1, argv=0x7fffffffdfa8) at src/baobab.p/main.c:67

==========

   0x000055555556c672 <+306>:   call   0x555555570460 <baobab_location_unref>
   0x000055555556c677 <+311>:   mov    0x8(%rbx),%rbx
   0x000055555556c67b <+315>:   test   %rbx,%rbx
   0x000055555556c67e <+318>:   je     0x55555556c6a1
<baobab_location_list_volume_changed+353>
=> 0x000055555556c680 <+320>:   mov    (%rbx),%r14
   0x000055555556c683 <+323>:   test   %r14,%r14
   0x000055555556c686 <+326>:   jne    0x55555556c600
<baobab_location_list_volume_changed+192>
   0x000055555556c68c <+332>:   xor    %edi,%edi
   0x000055555556c68e <+334>:   call   0x55555556fdc0
<baobab_location_get_mount>

==========
gio mount -l

...
Volume(0): SAMSUNG Android
  Type: GProxyVolume (GProxyVolumeMonitorMTP)
  Mount(0): SAMSUNG Android -> mtp://SAMSUNG_SAMSUNG_Android_XXXXXXXXXXX/
    Type: GProxyShadowMount (GProxyVolumeMonitorMTP)
Mount(1): mtp -> mtp://SAMSUNG_SAMSUNG_Android_XXXXXXXXXXX/
  Type: GDaemonMount

==========

Best regards,

The issue seems to be reproducible with other devices:

[11:11] <sre4ever> hello there, could someone on gnome try to start
baobab (disk usage) with a MTP device mounted to confirm it crashes?
[11:12] <Wulf> ** (baobab:2927904): CRITICAL **: 13:12:22.108:
baobab_scanner_results_get_parent: assertion 'self != NULL' failed
[11:12] <Wulf> Segmentation fault
[11:13] <Wulf> but it wasn't mounted yet. It displayed my mobile phone
that I just connected through usb and said "unmounted". I clicked it ->
segfault.

Best regards,

I see this issue - segmentation fault - with Google Drive mounted.


Regards

Marc

I installed version 49.0-1 from Testing/Unstable and, I see the same
issue - segmentation fault - with Google Drive mounted.

Regards

Marc

Dear Maintainer,

It seems this bug was fixed by https://gitlab.gnome.org/GNOME/baobab/-/commit/c190448f4a1b0d98d3c43f5558bff8bb78d0c5bc ?
At least, testing the flatpak of version 50.0, I'm indeed able to see a mounted mtp device without crash.
Could that patch be ported to the trixie package ?

Best regards