Version-Release number of selected component: gvfs-1.17.91-1.fc20 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor crash_function: g_realloc executable: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 3.11.0-300.fc20.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 g_realloc at gmem.c:169 #5 array_resize at gdbusmessage.c:276 #6 g_memory_buffer_write at gdbusmessage.c:320 #7 g_memory_buffer_put_uint32 at gdbusmessage.c:417 #8 append_value_to_blob at gdbusmessage.c:2336 #12 append_body_to_blob at gdbusmessage.c:2542 #13 g_dbus_message_to_blob at gdbusmessage.c:2711 #14 g_dbus_connection_send_message_unlocked at gdbusconnection.c:1662 #15 g_dbus_connection_send_message at gdbusconnection.c:1776 #16 g_dbus_connection_emit_signal at gdbusconnection.c:5336 Potential duplicate: bug 995503
Created attachment 813571 [details] File: backtrace
Created attachment 813572 [details] File: cgroup
Created attachment 813573 [details] File: core_backtrace
Created attachment 813574 [details] File: dso_list
Created attachment 813575 [details] File: environ
Created attachment 813576 [details] File: exploitable
Created attachment 813577 [details] File: limits
Created attachment 813578 [details] File: maps
Created attachment 813579 [details] File: open_fds
Created attachment 813580 [details] File: proc_pid_status
Another user experienced a similar problem: I disconnected the disk while loading filesystem after connect it to the computer. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gvfs-udisks2-volume-monitor crash_function: g_realloc executable: /usr/libexec/gvfs-udisks2-volume-monitor kernel: 3.14.4-200.fc20.x86_64 package: gvfs-1.18.3-2.fc20 reason: gvfs-udisks2-volume-monitor killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.