Description of problem: I believe I hit eject/stop button on a device which showed to be present, but was not actually there. Version-Release number of selected component: gnome-disk-utility-3.18.0-3.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 8562 kernel: 4.2.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_dbus_object_get_interface at gdbusobject.c:149 #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:1089 #4 gdu_utils_ensure_unused_list at gduutils.c:1152 #5 gdu_window_ensure_unused_list at gduwindow.c:4016 #6 do_power_off at gduwindow.c:3265 #7 on_devtab_drive_power_off_button_clicked at gduwindow.c:3288 #8 _g_closure_invoke_va at gclosure.c:864 #11 gtk_button_do_release at gtkbutton.c:1899 Potential duplicate: bug 984427
Created attachment 1083680 [details] File: backtrace
Created attachment 1083681 [details] File: cgroup
Created attachment 1083682 [details] File: core_backtrace
Created attachment 1083683 [details] File: dso_list
Created attachment 1083684 [details] File: environ
Created attachment 1083685 [details] File: exploitable
Created attachment 1083686 [details] File: limits
Created attachment 1083687 [details] File: maps
Created attachment 1083688 [details] File: mountinfo
Created attachment 1083689 [details] File: namespaces
Created attachment 1083690 [details] File: open_fds
Created attachment 1083691 [details] File: proc_pid_status
Created attachment 1083692 [details] File: smart_data
Another user experienced a similar problem: An unusual situation that probably can't be reproduced: 1. A USB flash drive was inserted with three partitions (old Linux install). The drive was to have its partitions removed/be reformatted. The OS automatically mounted the first two existing but didn't complete mounting the third. 2. Attempts to cancel the mounting and perform other actions in gnome-disk-utility didn't seem to have an effect. Utility didn't respond to clicks on eject drive or power off drive. 3. USB drive was unplugged. 4. Drive was still listed in gnome-disk-utility after unplugging. Clicking power off in gnome-disk-utility crashed the application. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 2940 kernel: 4.2.5-300.fc23.x86_64 package: gnome-disk-utility-3.18.1-1.fc23 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: No idea what happened here. The program just crashed during normal use. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 4032 kernel: 4.2.6-301.fc23.x86_64 package: gnome-disk-utility-3.18.3.1-1.fc23 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was powering off a USB stick reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 20165 kernel: 4.3.4-300.fc23.x86_64 package: gnome-disk-utility-3.18.3.1-1.fc23 reason: gnome-disks killed by SIGSEGV runlevel: N 5 smart_data: type: CCpp uid: 5160
*** Bug 1318405 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I powered off a USB card reader before unplugging it from the system. A few minutes later, I noticed that the reader was still in the device list (though with no media present) and I clicked on the "eject" button, thinking that it might get removed. That's when the crash happened. After the crash, I restarted gnome-disks and the card reader entry was still there. This has happened 5-6 times in the past couple of months with other removable devices (I think that they were all connected over USB). reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 24673 kernel: 4.4.8-300.fc23.x86_64 package: gnome-disk-utility-3.18.3.1-1.fc23 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was unmounting an USB stick. But it happened slightly after I removed the stick. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 21074 kernel: 4.4.8-300.fc23.x86_64 package: gnome-disk-utility-3.18.3.1-1.fc23 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: i turned off my usb device and afterwards i did it again. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-disks --gapplication-service crash_function: g_dbus_object_get_interface executable: /usr/bin/gnome-disks global_pid: 14191 kernel: 4.5.7-200.fc23.x86_64 package: gnome-disk-utility-3.18.3.1-1.fc23 reason: gnome-disks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1363912 has been marked as a duplicate of this bug. ***
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.