gnome-settings-daemon 2.14.1 isn't starting

Joe Marcus Clarke marcus at
Sat Apr 29 15:34:29 UTC 2006

On Sat, 2006-04-29 at 10:50 -0400, michael johnson wrote:
> #6  0x00000000456229d8 in __printf_render_str (io=0x7fdffffb050, 
>     pi=0x7fdffffaaa0, arg=0x1)
> at /usr/src/lib/libc/stdio/xprintf_str.c:142
> #7  0x000000004562521c in __v2printf (fp=0x7fdffffb6b0, 
>     fmt0=0x3b88 <Error reading address 0x3b88: Bad address>,
> pct=1081297756, 
>     ap=0x7fdffffba48) at /usr/src/lib/libc/stdio/xprintf.c:554
> #8  0x00000000456253dc in __xvprintf (fp=0x0, 
>     fmt0=0x3b88 <Error reading address 0x3b88: Bad address>,
> ap=0x7fdffffba48)
>     at /usr/src/lib/libc/stdio/xprintf.c:622 

This is the xprint crash that was discussed on the freebsd-gnome mailing
list.  There is a patch floating around to fix this in gstreamer.  I
have asked anyone that can reproduce this to send a backtrace to phk.
He added the xprint code, and I have yet to reproduce this crash.  The
thread on freebsd-gnome sums up everything, but the long and short of it
is, gstreamer will use xprint if available.  Once the xprint code is
enabled, bad things start to happen.


PGP Key :
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url :

More information about the freebsd-gnome mailing list