Description of problem: Baobab closes as soon as it's opened. Opened in terminal and it says "Segmentation fault (core dumped)". Seems to work when ran with - sudo baobab. Version-Release number of selected component: baobab-48.0-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: baobab killed by SIGSEGV journald_cursor: s=4ce78fb25bbe4a519f01ebec2ba8d2a5;i=1bfb95;b=b7cbed8a18984a01a37443dbe670de93;m=1c5fdfd7e;t=632eb6af76a3f;x=dbea88b87620efff executable: /usr/bin/baobab cmdline: /usr/bin/baobab --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.baobab rootdir: / uid: 1000 kernel: 6.14.2-300.fc42.x86_64 package: baobab-48.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: baobab_location_list_volume_changed Truncated backtrace: Thread no. 1 (12 frames) #0 baobab_location_list_volume_changed at ../src/baobab-location-list.vala:160 #1 baobab_location_list_mount_added at ../src/baobab-location-list.vala:217 #4 signal_emit_valist_unlocked at ../gobject/gsignal.c:3534 #6 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910 #7 _g_closure_invoke_va at ../gobject/gclosure.c:896 #8 signal_emit_valist_unlocked at ../gobject/gsignal.c:3438 #10 signal_emit_in_idle_do at ../monitor/proxy/gproxyshadowmount.c:546 #13 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #14 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #15 g_main_context_iteration at ../glib/gmain.c:4379 #16 g_application_run at ../gio/gapplication.c:2715 #17 _vala_main at ../src/main.vala:27
Created attachment 2085266 [details] File: proc_pid_status
Created attachment 2085267 [details] File: maps
Created attachment 2085268 [details] File: limits
Created attachment 2085269 [details] File: environ
Created attachment 2085270 [details] File: open_fds
Created attachment 2085271 [details] File: mountinfo
Created attachment 2085272 [details] File: os_info
Created attachment 2085273 [details] File: cpuinfo
Created attachment 2085274 [details] File: core_backtrace
Created attachment 2085275 [details] File: exploitable
Created attachment 2085276 [details] File: dso_list
Created attachment 2085277 [details] File: backtrace
This appears to only happen when Google Drive is mounted. Unmounting google drive stops it from crashing.
*** Bug 2360977 has been marked as a duplicate of this bug. ***
*** Bug 2361557 has been marked as a duplicate of this bug. ***
Thanks for a bug report. There is an upstream bug about the same [1], which has a pending fix [2]. It'll get to Fedora once they merge the fix and create a release with it. I backported the change into Fedora, an update will be filled shortly. [1] https://gitlab.gnome.org/GNOME/baobab/-/issues/175 [2] https://gitlab.gnome.org/GNOME/baobab/-/merge_requests/100
FEDORA-2025-583feff2c3 (baobab-48.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-583feff2c3
FEDORA-2025-583feff2c3 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-583feff2c3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-583feff2c3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-583feff2c3 (baobab-48.0-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.