Description of problem: Ejected a USB drive via nautilus. Inserted a new USB drive. Opened gnome-disks. Saw drive 1 still in the list of drives. Clicked "Eject" on drive 1. Crash. This happens every time I try to 'ejected' the disk that isn't there. Version-Release number of selected component: gnome-disk-utility-3.12.1-7.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-disks crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks kernel: 3.17.0-300.fc21.x86_64 runlevel: 3 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_dbus_object_get_interface at gdbusobject.c:142 #1 udisks_object_get_partition_table at udisks-generated.c:31231 #2 gdu_utils_is_in_use_full at gduutils.c:894 #3 unuse_data_iterate at gduutils.c:1086 #4 gdu_utils_ensure_unused_list at gduutils.c:1150 #5 gdu_window_ensure_unused_list at gduwindow.c:3969 #6 gdu_window_ensure_unused at gduwindow.c:4004 #7 _g_closure_invoke_va at gclosure.c:831 #10 gtk_button_do_release at gtkbutton.c:1890 #11 gtk_real_button_released at gtkbutton.c:2008 Potential duplicate: bug 984427
Created attachment 947332 [details] File: backtrace
Created attachment 947333 [details] File: cgroup
Created attachment 947334 [details] File: core_backtrace
Created attachment 947335 [details] File: dso_list
Created attachment 947336 [details] File: environ
Created attachment 947337 [details] File: exploitable
Created attachment 947338 [details] File: limits
Created attachment 947340 [details] File: maps
Created attachment 947342 [details] File: open_fds
Created attachment 947343 [details] File: proc_pid_status
Created attachment 947345 [details] File: smart_data
Created attachment 947347 [details] File: var_log_messages
Another user experienced a similar problem: I think I first used a quit button on my removable flash drive, and then eject button. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: gnome-disks crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks kernel: 3.17.4-301.fc21.x86_64 package: gnome-disk-utility-3.14.0-1.fc21 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: A device is shown in disks with details as follows: Model: USB DISK 30X (1.00) Size: 8.1GB Serial No: 000000000000 When trying to eject it. It Closes. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: gnome-disks crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks kernel: 3.18.9-200.fc21.x86_64 package: gnome-disk-utility-3.14.0-1.fc21 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.