GNOME Bugzilla – Bug 84644
Ugly error on first time change of background properties
Last modified: 2004-12-22 21:47:04 UTC
Upon firing up Gnome2 for the first time with a clean home dir, I get presented with a very disconcerting error dialog as per the attched screenshot. Can we get of this so as to make things look a bit more professional for the first time user? Also, in my .xsession-errors I see:- (gnome-settings-daemon:32478): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. (gnome-background-properties:32502): capplet-common-WARNING **: Could not load pixbuf ""; disabling wallpaper. After changing the background, everything is ok from that point onwards.
Created attachment 9085 [details] Of course I meant "get rid of"... Here's the attachment.
Jody: is this always the case with the 'fix' for the default background stuff? I wish I had had time to do a complete reinstall from scratch...
i assume this was with a very recent build? ie, not one a month old? after nuking my ~ i couldn't reproduce this...
i can't find that error message in the sources since my commit on may 16: 2002-05-16 jacob berkman <jacob@ximian.com> * applier.c (bg_applier_apply_prefs): don't spew a warning when files can't be loaded (helps fix #76993)
1.99.10 was before the fix went in, so going to close this as a dup. *** This bug has been marked as a duplicate of 76993 ***