Red Hat Bugzilla – Bug 863814
[abrt] gparted-0.12.0-2.fc17: gdk_window_set_geometry_hints: Process /usr/sbin/gpartedbin was killed by signal 11 (SIGSEGV)
Last modified: 2013-03-12 04:46:53 EDT
Description of problem:
1. create partition table of type GPT
2. create a new partition without filesystem, because it will be marked with flag lvm or raid later.
3. finalize action 2, it will reload the disk layout.
The system contains further disks with msdos partition tables. The disks are used in two (auto-)raid devices. The software reports errors during startup that it is not able to analyse these two devices.
Version-Release number of selected component:
libreport version: 2.0.14
:Thread no. 1 (10 frames)
: #0 gdk_window_set_geometry_hints at gdkwindow-x11.c:2361
: #1 gtk_window_move_resize at gtkwindow.c:6219
: #2 gtk_window_check_resize at gtkwindow.c:5408
: #4 _g_closure_invoke_va at gclosure.c:840
: #7 gtk_container_idle_sizer at gtkcontainer.c:1357
: #12 g_main_context_iteration at gmain.c:3207
: #13 gtk_main_iteration_do at gtkmain.c:1358
: #14 Gtk::Main::iteration_impl at main.cc:549
: #15 GParted::Win_GParted::show_pulsebar at Win_GParted.cc:628
: #16 GParted::Win_GParted::menu_gparted_refresh_devices at Win_GParted.cc:1193
Created attachment 623000 [details]
Created attachment 623001 [details]
Created attachment 623002 [details]
Created attachment 623003 [details]
Created attachment 623004 [details]
Created attachment 623005 [details]
Created attachment 623006 [details]
Created attachment 623007 [details]
Created attachment 623008 [details]
gparted-0.14.1-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gparted-0.14.1-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
gparted-0.14.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.