Bug 3899 - [beagleboard] No icons on the desktop
Summary: [beagleboard] No icons on the desktop
Status: RESOLVED WORKSFORME
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 1.4
Hardware: Beagleboard arm
: Undecided normal
Target Milestone: ---
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-02-18 05:00 UTC by Yi Zhao
Modified: 2013-02-22 10:09 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
beagleboard (33.46 KB, image/png)
2013-02-18 05:00 UTC, Yi Zhao 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2013-02-18 05:00:46 UTC 
Created attachment 1074 [details]
beagleboard

Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130213-3/machines/beagleboard/

Git rev:
master:3ec4df57540421df2cda6b83c615bfb7cebccefd

When the system boot up, there is no icons on the desktop. Please see the attachment. 

The error log when booting:
##################
(matchbox-desktop:552): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
##################

After running "gdk-pixbuf-query-loaders > /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache", the icons restore after reboot.
Comment 1 Ross Burton 2013-02-18 10:58:21 UTC 
Broken pixbuf cache...  Assigning to Laurentiu.
Comment 2 Laurentiu Palcu 2013-02-18 12:28:34 UTC 
This should be retested with later builds. This might be a sstate issue since the build was made right after the latest intercept fall-back procedures were merged. Secondly, pixbuf cache is generated in an intercept hook, offline, and if it fails it will be created at first boot. So, basically, with the intercepts falling-back to running the postinstalls at first boot, this issue should not exist.

I built a core-image-sato for beagleboard myself, on master, and the loaders.cache is created offline.

Please retest with a newer build and let me know if it still happens.
Comment 3 Yi Zhao 2013-02-22 07:00:48 UTC 
With the 1.4 rc1 20130220 build (git rev:7d22ef28e64de06b6238d0ef9b664c0bee6efa46), there is no this issue.
Comment 4 Laurentiu Palcu 2013-02-22 10:09:16 UTC 
I have also tested with the latest core-image-sato, 7d22ef28e64de06b6238d0ef9b664c0bee6efa46, and it looks to be working just fine. I'm closing this bug as WORKSFORME since I'm not able to reproduce it anymore.