After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701006 - gparted crashes just after loading drives has finished
gparted crashes just after loading drives has finished
Status: RESOLVED INVALID
Product: gparted
Classification: Other
Component: application
0.16.1
Other Linux
: Normal critical
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2013-05-25 15:28 UTC by Milan
Modified: 2013-06-13 20:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan 2013-05-25 15:28:24 UTC
Gparted prompts root autentification. After sucessfull authentification it shows dialog with progressbar saying "loading /dev/sda partitions" after loading is complete gparted crashes saying:

======================
libparted : 3.1
======================

** (gpartedbin:856): CRITICAL **: atk_object_get_role: assertion `ATK_IS_OBJECT (accessible)' failed

** (gpartedbin:856): CRITICAL **: atk_object_get_role: assertion `ATK_IS_OBJECT (accessible)' failed

** (gpartedbin:856): CRITICAL **: atk_object_set_parent: assertion `ATK_IS_OBJECT (accessible)' failed

(gpartedbin:856): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed

(gpartedbin:856): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
/usr/bin/gparted: line 99:   856 Segmentation fault      (core dumped) $BASE_CMD

Sometimes you can see loaded partitions for a fraction of second before crash.
Comment 1 Mike Fleetwood 2013-05-25 16:43:30 UTC
Hi Milan,

Can you answer the following questions please:

1) What distribution, version and desktop (GNOME/KDE/...) do you use?
2) Can you show me the zdisk layout using the commands:
      fdisk -s -l
      parted /dev/sda print
      blkid
3) Is there anything else that is unusual that might be relevant?

Thanks,
Mike
Comment 2 Milan 2013-05-25 17:31:27 UTC
1) I use ArchLinux, I ran pacman -Suy (system update) recently so all packages should be latest versions, as they are in repositories.
2) fdisk:
Disk /dev/sda: 750.2 GB, 750156374016 bytes, 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0xa82b0268

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/sda2         1026048    97656831    48315392   83  Linux
/dev/sda3       292972542  1465147391   586087425    5  Extended
Partition 3 does not start on physical sector boundary.
/dev/sda4        97656832   200065023    51204096   8e  Linux LVM
/dev/sda5       292972544   683595775   195311616   83  Linux
/dev/sda6       683597824   878899199    97650688    7  HPFS/NTFS/exFAT
/dev/sda7       878909440   917968895    19529728   82  Linux swap / Solaris
/dev/sda8       917970944  1465147391   273588224   83  Linux

Partition table entries are not in disk order

Disk /dev/mapper/fedora-root: 52.4 GB, 52428800000 bytes, 102400000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

parted:
Model: ATA Hitachi HTS54757 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  106MB   105MB   primary   ntfs            boot
 2      525MB   50.0GB  49.5GB  primary   ext4
 4      50.0GB  102GB   52.4GB  primary                   lvm
 3      150GB   750GB   600GB   extended
 5      150GB   350GB   200GB   logical   ext4
 6      350GB   450GB   100GB   logical   ntfs
 7      450GB   470GB   20.0GB  logical   linux-swap(v1)
 8      470GB   750GB   280GB   logical

blkid:

/dev/sda1: LABEL="VyhradenM-CM-) systM-CM-)mom" UUID="54AEFBA4AEFB7CB4" TYPE="ntfs"
/dev/sda2: LABEL="arch" UUID="4d97ab7a-4550-4ad8-a01f-0ba29eadc523" TYPE="ext4"
/dev/sda4: UUID="kQ9EAa-H7os-gdaY-c4m1-rDdB-DflP-zHVjOL" TYPE="LVM2_member"
/dev/sda5: LABEL="arch home" UUID="c2fdd3d1-d0ae-4e4f-86f9-e6f976ad1c85" TYPE="ext4"
/dev/sda6: UUID="58841E22841E02E4" TYPE="ntfs"
/dev/sda7: UUID="2cf774b4-b964-45ed-9f69-21474dd0bceb" TYPE="swap"

3) I dont suspect that its because of my partitioning gparted tools on fedora live CD and ubuntu are just fine.
After said system upgrade I noticed that another app Inkscape segfolds on me as well
in debug it trows similar error, comlaning about nore or less g_object functions. Therefore I think it maight be gtk+ related issue, but I dont really see into that. But those errors could have something in common.

Good luck,
Milan
Comment 3 Mike Fleetwood 2013-05-26 10:11:36 UTC
Hi Milan,

Can you produce a backtrace from the core file.
   script
   gdb /usr/sbin/gpartedbin core
   set pagination off
   list
   backtrace
   backtrace full
   thread apply all backtrace
   info registers
   x/16i $pc
   quit
   exit
You may need to install debugging symbol packages for all the gtk/gtkmm/
glib/glibmm libraries and gparted.

Thanks,
Mike
Comment 4 osmank3 2013-05-30 09:49:08 UTC
Downgrade to gtkmm-2.24.2-2 solved this problem.
Comment 5 Mike Fleetwood 2013-06-13 20:43:53 UTC
Closing this bug report with RESOLVED, INVALID.  It's the closest I can
find for not a bug with GParted, fixed by downgrading component gtkmm.