Hi, > Debian's bugtracker didn't forward me the emails,
This has happened to me, too. But today it worked for me. > ==2799== Conditional jump or move depends on uninitialised value(s) > ==2799== at 0x7201FC8: ??? (in > /usr/lib/powerpc-linux-gnu/gtk-2.0/2.10.0/engines/libmurrine.so) Hard to say whether this is a true bug. Google libmurrine ... "Murrine GTK2 cairo theme". Maybe one can choose a different theme and avoid the library in order to see whether xfburn still crashes. > ==2799== Invalid read of size 4 > ==2799== at 0x53EDD90: ??? (in > /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) > [... no xfburn code to see ...] > ==2799== by 0x53F712B: g_signal_emit_valist (in > /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0.4200.0) > ==2799== Address 0x4 is not stack'd, malloc'd or (recently) free'd Well, this seems to be the immediate cause of the SIGSEGV. Like with the i386-Ubuntu occasion half a year ago, we see no accusations against the xfburn code before this happens. The normal ways how an application can spoil a library are supposed to get detected by valgrind. Do i get it right that this is 32 bit code ? Something seems to be wrong with xfburn and XFCE+GTK on 32 bit systems. But what ? And why rather rarely ? Is everybody else on 64 bit ? Have a nice day :) Thomas _______________________________________________ Pkg-xfce-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xfce-devel
