Hide Forgot
Description of problem: While ejecting a USB drive (actually a sony camera), after having deleted some files off it (the deletion may still have been in progress as I got a "this drive is in use" message) Version-Release number of selected component: gvfs-1.26.2-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor crash_function: unmount_cb executable: /usr/libexec/gvfs-udisks2-volume-monitor global_pid: 8031 kernel: 4.2.8-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 unmount_cb at gvfsudisks2mount.c:876 #1 g_task_return_now at gtask.c:1106 #2 g_task_return at gtask.c:1164 #3 reply_cb at gdbusproxy.c:2579 #4 g_task_return_now at gtask.c:1106 #5 g_task_return at gtask.c:1164 #6 g_dbus_connection_call_done at gdbusconnection.c:5704 #7 g_task_return_now at gtask.c:1106 #8 complete_in_idle_cb at gtask.c:1120 #13 g_vfs_proxy_volume_monitor_daemon_main at gvfsproxyvolumemonitordaemon.c:2009
Created attachment 1115209 [details] File: backtrace
Created attachment 1115210 [details] File: cgroup
Created attachment 1115211 [details] File: core_backtrace
Created attachment 1115212 [details] File: dso_list
Created attachment 1115213 [details] File: environ
Created attachment 1115214 [details] File: exploitable
Created attachment 1115215 [details] File: limits
Created attachment 1115216 [details] File: maps
Created attachment 1115217 [details] File: mountinfo
Created attachment 1115218 [details] File: namespaces
Created attachment 1115219 [details] File: open_fds
Created attachment 1115220 [details] File: proc_pid_status
Created attachment 1115221 [details] File: var_log_messages
Thanks for your bug report. Are you able to reproduce it again? Could you provide detailed steps to reproduce? Did you see "Don't unplug until finished" notification, or "One or more applications are keeping the volume busy." dialog? Did you press "Cancel", or "Unmount Anyway" in case of the dialog?
I am pretty sure I did not get one of those messages when I saw this crash. I have tried a few times to reproduce it, but so far have not managed. If it is some sort of race, I guess it is rare. Some things that might contribute is that I often have SSH shares mounted (using caja file browser) and the sony camera exposes 2 drives over USB (one for documentation and one for the sd card). [181130.504401] usb 1-1.4.1: new high-speed USB device number 57 using xhci_hcd [181130.581117] usb 1-1.4.1: New USB device found, idVendor=054c, idProduct=060b [181130.581123] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [181130.581126] usb 1-1.4.1: Product: HDR-AS15 [181130.581129] usb 1-1.4.1: Manufacturer: Sony [181130.581132] usb 1-1.4.1: SerialNumber: ########## [181130.582427] usb-storage 1-1.4.1:1.0: USB Mass Storage device detected [181130.583712] scsi host20: usb-storage 1-1.4.1:1.0 [181131.585657] scsi 20:0:0:0: Direct-Access Sony Camcorder 1.00 PQ: 0 ANSI: 0 [181131.629462] scsi 20:0:0:1: Direct-Access Sony Camcorder 1.00 PQ: 0 ANSI: 0 [181131.630052] sd 20:0:0:0: Attached scsi generic sg2 type 0 [181131.630300] sd 20:0:0:1: Attached scsi generic sg3 type 0 [181131.694047] sd 20:0:0:0: [sdc] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) [181131.695006] sd 20:0:0:1: [sdd] 43008 512-byte logical blocks: (22.0 MB/21.0 MiB) [181131.696258] sd 20:0:0:0: [sdc] Write Protect is off [181131.696263] sd 20:0:0:0: [sdc] Mode Sense: 03 00 00 00 [181131.697391] sd 20:0:0:1: [sdd] Write Protect is on [181131.697395] sd 20:0:0:1: [sdd] Mode Sense: 03 00 80 00 [181131.698955] sd 20:0:0:0: [sdc] No Caching mode page found [181131.698960] sd 20:0:0:0: [sdc] Assuming drive cache: write through [181131.700025] sd 20:0:0:1: [sdd] No Caching mode page found [181131.700029] sd 20:0:0:1: [sdd] Assuming drive cache: write through [181131.721666] sdc: sdc1 [181131.724244] sdd: sdd1 [181131.734460] sd 20:0:0:1: [sdd] Attached SCSI removable disk [181131.735925] sd 20:0:0:0: [sdc] Attached SCSI removable disk
Thanks for your feedback. It looks like from the backtrace that it crashed before showing the notification... Did you hard unplug the device?
I've just had this when copying files to an external usb drive. 1. plug in USB drive 2. drag and drop files (large enough to take a few seconds) 3. click unmount in nautilus (while copy is still busy) 4. get a message "volume is busy; unmount anyway?" 5. hit cancel 6. crash The crash is reported by gnome-abrt, so it's a few seconds slow, and it may have happened during steps 4 or 5. the USB drive is still attached.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.