1. I suppose both Cubieboard2 and your pc with qemu-arm installation have newer kernels than 2.6.28?
Are you able to install second kernel on your pc, preferably 2.6.28?
Googling told me Cubieboard2 supports 3.something (3.4?) kernels only, so I guess downgrading that one is not possible.
2. Again very remote guess, but could you try running gparted from console with "LD_PRELOAD=/path/to/libstdc++.so" ?
# ls -l /usr/lib/arm-linux-gnueabihf/libstdc++.so.6* lrwxrwxrwx 1 root root 19 Jan 8 2013 /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 -> libstdc++.so.6.0.17 -rw-r--r-- 1 root root 641216 Jan 8 2013 /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.17 # export LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/libstdc++.so.6 # echo $LD_PRELOAD /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 # export LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/libstdc++.so.6 # gparted ====================== libparted : 2.3 ====================== *** glibc detected *** /usr/sbin/gpartedbin: free(): invalid pointer: 0x00287210 *** Aborted
Maybe comparing "ldd /usr/sbin/gpartedbin" from Cubieboard2, from qemu-armel environment on pc and from n900 in both armel and armhf image would also show something suspicious or give any clues (it would be nice if you could also post them here for reference).