I have a small gtk-based program which puts up buttonbars on my desktop. I have used it in both Crux and Debian and have never had any problems with it. But since upgrading to Crux-2.6, I have had intermittent aborts. The traceback (attached) suggests that the problem is inside libc, specifically in malloc. Once the program has aborted, it aborts each time it is restarted. But weirdly I was able to break this cycle simply by altering the order in which buttons were created, via the program's config file. For example, this version - (Files) </home/data/icons/file-manager.png> {gksu-not|sudo -S emelfm2} (Terminal) </home/data/icons/root-term.png> {gksu-not|sudo -S xterm -font 10x20} (Editor) </usr/share/pixmaps/vim32x32.png> {gksu-not|sudo -S gvim} (Other apps) </home/hazel/icons/applications-other.png> {bbrun -w} (Reboot) </home/data/icons/reboot.png> {gksu-not|sudo -S /sbin/shutdown -r now} (Shutdown) </home/data/icons/gnome-logout.png> {gksu-not|sudo -S /sbin/shutdown -h now} caused the program to abort yesterday (though not on previous days), but this one - (Files) </home/data/icons/file-manager.png> {gksu-not|sudo -S emelfm2} (Editor) </usr/share/pixmaps/vim32x32.png> {gksu-not|sudo -S gvim} (Terminal) </home/data/icons/root-term.png> {gksu-not|sudo -S xterm -font 10x20} (Other apps) </home/hazel/icons/applications-other.png> {bbrun -w} (Reboot) </home/data/icons/reboot.png> {gksu-not|sudo -S /sbin/shutdown -r now} (Shutdown) </home/data/icons/gnome-logout.png> {gksu-not|sudo -S /sbin/shutdown -h now} allowed it to run again. Is this a bug or am I doing something wrong? -- Hazel Russman <hazel_russman@yahoo.co.uk>