Version-Release number of selected component: gvfs-1.50.5-1.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=9e34d0bfe6cb491c8e386cea9e3ec08d;i=7b57;b=3174d0f0e0484dc7b896b4c0fdf5debb;m=169eac54a;t=5ff83c7d35acf;x=53b634c9c2972d24 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice Truncated backtrace: Thread no. 1 (13 frames) #0 g_mount_operation_get_choice at ../gio/gmountoperation.c:823 #1 unmount_notify_op_reply at ../monitor/udisks2/gvfsudisks2utils.c:695 #2 g_cclosure_marshal_VOID__ENUMv at ../gobject/gmarshal.c:1028 #3 _g_closure_invoke_va at ../gobject/gclosure.c:895 #6 g_mount_operation_reply at ../gio/gmountoperation.c:984 #7 on_name_owner_vanished at ../monitor/proxy/gvfsproxyvolumemonitordaemon.c:460 #8 actually_do_call at ../gio/gdbusnamewatching.c:197 #10 do_call at ../gio/gdbusnamewatching.c:250 #11 call_vanished_handler at ../gio/gdbusnamewatching.c:275 #13 on_name_owner_changed at ../gio/gdbusnamewatching.c:378 #14 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:3802 #18 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #20 g_vfs_proxy_volume_monitor_daemon_main at ../monitor/proxy/gvfsproxyvolumemonitordaemon.c:2072
Created attachment 1973765 [details] File: proc_pid_status
Created attachment 1973766 [details] File: maps
Created attachment 1973767 [details] File: limits
Created attachment 1973768 [details] File: environ
Created attachment 1973769 [details] File: open_fds
Created attachment 1973770 [details] File: mountinfo
Created attachment 1973771 [details] File: os_info
Created attachment 1973772 [details] File: cpuinfo
Created attachment 1973773 [details] File: core_backtrace
Created attachment 1973774 [details] File: exploitable
Created attachment 1973775 [details] File: dso_list
Created attachment 1973776 [details] File: backtrace
I ejected and unplugged a USB drive. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=06c1ed82b7f040fa82eac855f895b288;i=8607e5;b=954f5a9f9d5346a283c018cd31cc95fd;m=788218f1;t=5ff8576057d33;x=14360e28a784c772 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: I ejected and unplugged a USB drive.
no idea what is or that it happened or when...sorry, just hearing about it now from your popup reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=779273126b8d4d53a593d65048f74b70;i=2a6f28;b=15d443d57ebe4546849e2575ed757d42;m=479a0ee60;t=5ff86249354f7;x=8df1f4416f8ec88f executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: no idea what is or that it happened or when...sorry, just hearing about it now from your popup
I was copying data from one usb disk to another (1TB samsung T5 to 2TB samsung T7). After the transfer finished I unmounted the two disks via nautilus and afterwards also clicked the "safely remove ..." button. Then I unplugged both disks. After a few seconds I plugged in both disks again, which is when the SIGSEV occured. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=c3e36eca495540f0aa5a02197efc8ff7;i=25baaf;b=fe8d9cfb99d34258a1510c42316bd2e1;m=40e3555f4;t=5ff944e304773;x=7885b286f18d9d94 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
Dual monitor system. Two PDF files opened one on each display. Files opened on primary display. Opened meld on primary display to compare directories containing C source code. Used directory compare as follows: Drag folder from Files to first folder location in meld new comparison display Clicked button on second folder location, picked a recent folder then navigated to desired folder. Used meld's feature to insert changes from one file to another. Opened new comparison Closed current comparison Repeat moving small changes. None of the C source files is large. NOTE: have observed in the past if meld is open on primary display and Files on secondary display I have great difficultly dragging a file or folder from secondary display to the proper location in meld. What happens is meld will take the new file/folder and open another tab. Has meld been fully ported to Gtk4? The meld I'm using is from the @System repo not a flatpak. Finished using meld and closed it. Dragged one of the opened PDF's to secondary display Opened a terminal window on first display Observed notification of GVFS failure. Opened Abrt to report. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=6d01d849967b400782e3b3dea92e7f3c;i=2f0a7;b=7c548eaef3e94786b8041d7eb308b13a;m=169c05f89;t=5ff957b99a10f;x=b1d9157b39e9c8a5 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
This problem occurs after unmounting the external hard drive. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=1f06982d9e7a4f2e94a267b3d1b4379b;i=20353f;b=073d5b0bf7f047ce88e777247ba647b4;m=10d39811dd;t=5ffa4eeee6c8a;x=6f8db487f4360abe executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: This problem occurs after unmounting the external hard drive.
Dismounted a drive through the eject function of Cinnamon's Nemo file browser reporter: libreport-2.17.11 package: gvfs-1.50.5-1.fc38 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service runlevel: N 5 reason: gvfs-udisks2-volume-monitor killed by SIGSEGV crash_function: g_mount_operation_get_choice cmdline: /usr/libexec/gvfs-udisks2-volume-monitor executable: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 6.3.8-200.fc38.x86_64 comment: Dismounted a drive through the eject function of Cinnamon's Nemo file browser rootdir: / uid: 1000 type: CCpp journald_cursor: s=b722878de2714be29594d6aa26d91e27;i=18a697;b=fe8037ea88c74828833679af25450cc2;m=2a2762809;t=5ffa6dedfef58;x=c58c3cfe4d101821
I just ejected a USB-card - clicked before that 'empty trash' reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=f948f003a0784f59bfc324caa89caa15;i=dd76297;b=a4950c66dc1441ad81b5ba283245c272;m=1d82928e60;t=5ffa9fa0e015d;x=362f1b63c6d0c2dd executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-7412.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 7412 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 comment: I just ejected a USB-card - clicked before that 'empty trash' backtrace_rating: 4 crash_function: g_mount_operation_get_choice
Probably while ejecting a USB flash drive. I noticed the abrt report only while scrolling in Firefox. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=09aa17212080470b90ca1924b04aa72e;i=825c7;b=a3c8877ec44b4a64b0895ff123a6cb6d;m=a9d96801a;t=5ffae01f51827;x=73f3c70a4fa3d33b executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-4210950.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 4210950 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
I use a Kinesis Advantage 2 keyboard that mounts a virtual drive for remapping keys through a text file. I mounted this drive, configured my keyboard then as directed by Kinesis I ejected the drive through Nautilus then closed the drive with the keyboard shortcut, gvfs proceeded to crash. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=72e0243b58274bf38e949ec55c0c2866;i=d04b;b=edc01736d1cf49d59da5a87f8d02e8e9;m=2620aeef9;t=5ffd5c70cb830;x=b59ab77b9c5dd78e executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
Closed Anaconda with remote sftp connections open (but not active) reporter: libreport-2.17.11 crash_function: g_mount_operation_get_choice cgroup: 0::/user.slice/user-1601400001.slice/user/session.slice/gvfs-udisks2-volume-monitor.service runlevel: N 5 journald_cursor: s=0919bf1d997742f1843efc01e2ae6ca5;i=35ab05;b=448fa3209db847b0a714f6f444fa4457;m=39ace6c6e;t=5ffde9387107b;x=2d623764b3c3931f reason: gvfs-udisks2-volume-monitor killed by SIGSEGV package: gvfs-1.50.5-1.fc38 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor backtrace_rating: 4 comment: Closed Anaconda with remote sftp connections open (but not active) type: CCpp kernel: 6.3.11-200.fc38.x86_64 rootdir: / executable: /usr/libexec/gvfs-udisks2-volume-monitor uid: 1601400001
1. ejected a usb-c dock (HP USB-C Universal Dock) in Gnome "Files" app, but did not physically disconnect it. 2. Gnome "Problem Reporting" was raised. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=e4b113c8876a4e7397162f6bc4cc9c0f;i=4a7d6;b=819598f02d3d466cba1716001f4e0b3a;m=bf1c1a2;t=5fffac9f91b4b;x=390582b88d2229d9 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
ejected an usb key. did see a message telling me it was safe to remove. but i did get a SIGSEGV error later reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=b03d67841e974f1db543425d6b912d63;i=2285ca;b=0bb5493c3a854e7e8dba7ced46efb238;m=78e7c8bb9;t=60025cf364efe;x=3353ca4e9b74f2d7 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
crash when playing m3u list inside VLC reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=54f671b53dbf440dbf318f4110be0f6c;i=1ce26;b=fbdf1c1b675b43589ede8c9a65fdc5d6;m=30fa54793;t=6005dcd90f423;x=df300ff5eaf411ec executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: crash when playing m3u list inside VLC
Recreate the problem thusly: 1) Insert USB drive 2) Using Thunar, click the eject icon next to the USB drive 3) Close Thunar The following similar steps do NOT produce the error: 1) Insert USB drive 2) Using Thunar, click the eject icon next to the USB drive 3) Physically remove the USB drive 4) Close Thunar This error only happens with Thunar. If I use RemoveableDriveMenu extension to remove the USB drive, I do not get an error. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=c4f41e4bfb9d4ac68d9cadfb52cc8aad;i=10e937a;b=be5709ac5d36445f8bbd864e74e2c508;m=29c358f2f5;t=6005ea6dd06a2;x=5e8b3d8ddbd3b061 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-113809.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 113809 kernel: 6.3.11-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice
I do not know what triggered this problem. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=9ae38ba57ca746d68798e9a302a9c882;i=5d374f;b=093825b6341644f1beee38c8fb9c8270;m=50dcd9783;t=60062642a30a3;x=c3ce3bbf44da27b3 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: I do not know what triggered this problem.
Unknown, the error popped without direct relation to any known gvfs activity. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=171b81e04ea54d21968215c044fd1813;i=4dd566;b=d0e0a14c66f2446f92a37f9d409df9af;m=a0b8a609;t=6006d2b11fe09;x=4da1491e3c32da1f executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: Unknown, the error popped without direct relation to any known gvfs activity.
Plugged in mobile phone at usb port for charging. Phone was automounted. When I unmounted it through nautilus clicking on icon in sidebar, gvfs crashed. reporter: libreport-2.17.11 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 6.3.11-200.fc38.x86_64 rootdir: / backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user/session.slice/gvfs-udisks2-volume-monitor.service uid: 1001 type: CCpp journald_cursor: s=2af075beb4884d5aa440c003a4fd90f9;i=1810a1;b=6b118e896731471dadb9777db1a4d74e;m=a5d5ab17;t=6006dbda67d4b;x=6534bb52b67f4258 runlevel: N 5 comment: Plugged in mobile phone at usb port for charging. Phone was automounted. When I unmounted it through nautilus clicking on icon in sidebar, gvfs crashed. crash_function: g_mount_operation_get_choice reason: gvfs-udisks2-volume-monitor killed by SIGSEGV executable: /usr/libexec/gvfs-udisks2-volume-monitor package: gvfs-1.50.5-1.fc38
FEDORA-2023-5a1beaba59 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5a1beaba59
It seems to happen every time right after disconnecting an USB Flash drive. reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=7bd08b3959474fc4a288c6e685e3ec9d;i=1374563;b=e03d0ef9952a46eebc2f79e7443de015;m=ad00e24;t=600736b73bba0;x=28c2531ec31ada28 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: It seems to happen every time right after disconnecting an USB Flash drive.
FEDORA-2023-5a1beaba59 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5a1beaba59` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5a1beaba59 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thanks for all those reports. Can you please test the update? Comment 26 helped me to reproduce the issue, though not reliably.
An external USB disk was removed and I got this crash report reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=65bee9936be34e3e81b4913855749b74;i=198bbb;b=c965c43e38bc4e3090183f908fa0b4a6;m=1356a4b68;t=60088c9c2d53e;x=157b76148857be44 executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 comment: An external USB disk was removed and I got this crash report backtrace_rating: 4 crash_function: g_mount_operation_get_choice
FEDORA-2023-5a1beaba59 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
using the disk formater reporter: libreport-2.17.11 type: CCpp reason: gvfs-udisks2-volume-monitor killed by SIGSEGV journald_cursor: s=dc427790843443198dfd5f7ed6c759d9;i=4e161;b=ac05931781fe46b5a5aea59e8cb0e646;m=daae0769;t=6010cba71f1f0;x=499a60dc9695e3ff executable: /usr/libexec/gvfs-udisks2-volume-monitor cmdline: /usr/libexec/gvfs-udisks2-volume-monitor cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-udisks2-volume-monitor.service rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: gvfs-1.50.5-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_mount_operation_get_choice comment: using the disk formater