Description of problem: I've just discovered that I have to click File->Quit twice for drakdisk to exit when it is opened through drakconf->Local disks->Manage disk partitions. Log from console: $ drakconf Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257. Ignore the following Glib::Object::Introspection & Gtk3 warnings Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm line 525. Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257. Ignore the following Glib::Object::Introspection & Gtk3 warnings Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm line 525. (diskdrake:16701): Gtk-WARNING **: Theme parsing error: diskdrake.css:86:25: The style property GtkPaned:handle-size is deprecated and shouldn't be used anymore. It will be removed in a future version (diskdrake:16701): Gtk-WARNING **: Theme parsing error: diskdrake.css:86:25: The style property GtkPaned:handle-size is deprecated and shouldn't be used anymore. It will be removed in a future version Version-Release number of selected component (if applicable): How reproducible: I've tried several times and see the same result. Steps to Reproduce: 1. Open drakconf from command line 2. Go to Local disks, Manage disk partitions 3. Click Continue, then File->Quit twice.
Confirming the issue. It's also true for when using the "x" in the upper right to close disdrake. I don't know when this regression appeared, I do usually start diskdrake from the command line and then clicking "x" works immediately. Suspecting new gtk+3, though
Summary: Have to click File-Quit twice in diskdrake opened from drakconf => Have to click File-Quit or upper right "x" twice in diskdrake opened from drakconfSource RPM: drakconf-13.15-1.mga6.noarch => drakconf-13.15-1.mga6, drakxtools-17.82-1.mga6, gtk+3.0-3.22.15-1.mga6CC: (none) => marja11, olavAssignee: bugsquad => mageiatools
dupe. *** This bug has been marked as a duplicate of bug 20387 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE