Description of problem: Dunno whether it can be reproduced. Returned from lunch, wanted to unplug an external USB HDD since a file transfer had been completed, opened Nautilus and clicked the eject arrow next to the device id. Version-Release number of selected component: gvfs-1.15.4-2.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor crash_function: unmount_cb executable: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (8 frames) #0 unmount_cb at gvfsudisks2mount.c:844 #1 g_simple_async_result_complete at gsimpleasyncresult.c:777 #2 reply_cb at gdbusproxy.c:2632 #3 g_simple_async_result_complete at gsimpleasyncresult.c:777 #4 g_dbus_connection_call_done at gdbusconnection.c:5339 #5 g_simple_async_result_complete at gsimpleasyncresult.c:777 #6 complete_in_idle_cb at gsimpleasyncresult.c:789 #11 g_vfs_proxy_volume_monitor_daemon_main at gvfsproxyvolumemonitordaemon.c:2004 Potential duplicate: bug 832737
Created attachment 718284 [details] File: backtrace
Created attachment 718285 [details] File: cgroup
Created attachment 718286 [details] File: core_backtrace
Created attachment 718287 [details] File: dso_list
Created attachment 718288 [details] File: environ
Created attachment 718289 [details] File: limits
Created attachment 718290 [details] File: maps
Created attachment 718291 [details] File: open_fds
Created attachment 718292 [details] File: proc_pid_status
Created attachment 718293 [details] File: var_log_messages
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
umount btrfs external usb hdd. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor crash_function: unmount_cb executable: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 3.11.1-200.fc19.x86_64 package: gvfs-1.16.3-2.fc19 reason: Process /usr/libexec/gvfs-udisks2-volume-monitor was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 500
Same issue happened to me while trying to copy some files to an SD card. Hardware is Asus UX31A, the device is the following: Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
See also bug #1109563.
This bug might be related to: Bug 1103166 - [abrt] WARNING: CPU: 3 PID: 31028 at fs/btrfs/super.c:257 __btrfs_abort_transaction+0x50/0x110 [btrfs]() Bug 987281 - [abrt] gvfs-1.16.3-2.fc19: g_malloc: Process /usr/libexec/gvfs-udisks2-volume-monitor was killed by signal 11 (SIGSEGV)
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.