| Summary: | gdk-pixbuf: hundreds of warnings on boot | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Tom Zanussi <tom.zanussi> | ||||||
| Component: | core | Assignee: | Scott Garman <scott.a.garman> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium+ | CC: | corneliux.stoicescu, jfabernathy, meta.mr.watcher, meta.watcher, richard.purdie, ross.burton, sgw, song.liu | ||||||
| Version: | 1.2.1 | ||||||||
| Target Milestone: | 1.2.2 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | --- | |||||||
| Attachments: |
|
||||||||
|
Description
Tom Zanussi
2012-05-03 04:03:32 UTC
*** Bug 2663 has been marked as a duplicate of this bug. *** The patches for postinst improvements (bug #1621) will fix this issue too. The problem was the the loaders.cache was not generated for target when the target rootfs was constructed. With the fixes for #1621, this issue will dissapear. Since we are not pulling in the rootfs gen patches, is there a way to fix this when running directly on the target? Tom, how would I get a bootlog easily? I don't have a bootlog when I boot up a qemux86 image. Not sure with qemu - the bootlog referred to was just a serial capture. Maybe /var/log/messages... Nothing in messages. I'll dig out a serial cable... Just maybe an obvious note that I think this will only be seen on the first boot. Yep, this was first boot. gdkpixuf loaders and icon themes all postinit'd without a warning. The X server taking over meant I missed the last few lines. If you can replicate easily with a recent image that would be much appreciated. OK, I'll hopefully be booting a fresh emenlow image ;-) and will capture the serial if I still see the problem. Created attachment 864 [details]
new bootlog (serial capture) of an emenlow boot
meta-intel/master: 50ac6e8785c167ea4aa4601fd690ef783151853d
poky/master: 0ca8b6248e5d00351e8a35c87037cc47945e436b
poky/master had the following revert in order to get a bootable test image:
Revert "initrd: Spawn an emergency shell when something goes wrong"
This reverts commit ffb6928f5783e5202d9849c3a185e29be1d41c63.
Heh, so I don't get any warnings but I do see what packages are being postinstalled. You get warnings but no hint as to what is failing. Okay, interesting that all of those warnings come from a single PID. I wish there was an easy way to find out what package installed /etc/rpm-postinsts/102. Created attachment 867 [details]
Potential fix
I've a hunch this is sato-icon-theme, so try this.
That seems to have done the trick - no more gdkpixbuf warnings seen here on emenlow. Revised patch sent to oe-core. Merged in OE-Core rev: 8848ea6793ddaab61c9dad250ec578d68d7d087d. I meant oe-core 9d98dbdae4c05fcf50d546f554a04dc3f0bd66c3. Issue fixed in master and danny, but still present in denzil, commit: 846b7c388738f382e83576e77b705aa547c1dd9b Re-assigning to Scott, as it's his call if this gets fixed in Denzil or not. It doesn't make sense to backport this to 1.2 at this point unless there is significant community demand. |