icon in nautilus only one plain (BadMatch)

[TiloBunt]

every now and then the icon's in nautilus are just plain once.

see attached screen shot.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Dec 20 19:12:39 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Sebastien Bacher (seb128)]

The issue is usually due to gnome-settings-daemon hitting a bug, could you add your .xsession-errors next time you get the bug?

[TiloBunt (til0)]

Hi Seb, =)

thanks for working on this.
The issue occur like every 1 of 10 boots or so.

1. Not controlled reproducible
2. Folder and file icon show different (see working screenshot)
3. Folder and file icon just plain (see other screenshot)

please let me know what else you need, I believe my initial post contains the xsession-errors?

Cheers

[Sebastien Bacher (seb128)]

The version attached by apport is not the full log but a "smart filtering for common errors" to avoid privacy issues (we are not 100% sure of what is in the log and that there is no infos the user don't want to send to a bug so we limit the infos attached by default), it would be useful to have the full version

[TiloBunt (til0)]

copied it via: tilo@t-ubuntu:~$ cp ~/.xsession-errors x.session-errors.log
see attached.

have a lot's of: (nautilus:1685): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

[TiloBunt (til0)]

today again,

might be related to this issue?

(gnome-settings-daemon:1666): Gdk-WARNING **: The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 1437 error_code 8 request_code 3 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Initializing scale options...done

[TiloBunt (til0)]

Hi Sebastian (and/or others)

can I provide anything else to make this bug report "complete"

Thanks
Tilo

[Sebastien Bacher (seb128)]

Thanks, it's likely that BadMatch error indeed

[Sebastien Bacher (seb128)]

seems similar to bug #890905

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Philipp Bohn (philipp-bohn)]

Hi,

I recognized a change back to the normal look of nautilus (compare Nautilus missing theme - Bug #925134). I am pretty sure this happend when I changed my desktop background image. The first occurence of this issue might have come up, when i changed the desktop background image before. A reboot did not have any effect on this issue.

I add the .xsession-errors file again, now the issue disappeared (compare Nautilus missing theme - Bug #925134).

[Sebastien Bacher (seb128)]

the new log has no error