View Single Post
Posts: 915 | Thanked: 3,209 times | Joined on Jan 2011 @ Germany
#2894
Originally Posted by Estel View Post
gParted and glibc error:

Code:
[root@EasyDebian: /]gparted
======================
libparted : 2.3
======================
*** glibc detected *** /usr/sbin/gpartedbin: free(): invalid pointer: 0x40c67514 ***
I can confirm this behavior. Unfortunately I have no idea how to fix it or what may be the cause.

Originally Posted by Estel View Post
GIMP error:
Code:
(gimp:14480): Gdk-WARNING **: /build/buildd-gtk+2.0_2.24.10-2-armel-Vet_Aw/gtk+2.0-2.24.10/gdk/x11/gdkdrawable-x11.c:874 drawable is not a pixmap or window

(script-fu:14484): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
Memory protection violation
I can confirm this too. And have no solution either.
There are multiple similar descriptions out there which all suggest a problem with glibc or scim.
When I first reproduced this error I hadn't even scim installed. So I installed it, hoping it was just a broken dependency. But the error remained the same.
If your suspicion is true that this is due to the semi-transparent font panel then it should occur with other gimp tools as well, right?
I also read somewhere that it might be related to the fonts used by the application. So if there's a way to change the fonts gimp uses this problem might disappear. Unfortunately I have no idea how to do that.


Originally Posted by gm90_blackmamba View Post
Sulu, does you upgrade with qemu, right?
Right! My N900's watchdog is way too snappish for larger upgrades (even with using nice and ionice). Others seem to be more lucky. So I'd suggest to make a backup of your image/partition and try the dist-upgrade directly on device. Since at the moment the differences between testing and unstable are quite marginal due to the freeze it should work. If your device reboots nevertheless, try to do it on another computer (another armel-capable device without a watchdog would be ideal, but since I have none I use qemu).

Originally Posted by gm90_blackmamba View Post
p.s. Anyone can use last version of chromium (24.XXXX)?
I tried version 22.x some time ago, but something is broken in chromium's armel/hf build.
I filed a bug report [1], but since its severity is only "important" I expected that it won't be fixed during the Wheezy freeze.
It might be helpful if somebody who has another armel/hf machine could reproduce the problem and add info to the bug report.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696196
 

The Following 2 Users Say Thank You to sulu For This Useful Post: