Summary: | xfce-base/xfdesktop-4.10.2 - icons missing (Action Buttons, Launcher, etc.) in panel/menu | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sphakka <marcoep> |
Component: | Current packages | Assignee: | XFCE Team <xfce> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | grknight |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
xfdesktop emerge --info
panel2 screenshot |
Description
sphakka
2014-01-11 21:55:24 UTC
Created attachment 367662 [details]
xfdesktop emerge --info
Created attachment 367664 [details]
panel2 screenshot
Hi, this has happened to me after I update a few days back. The problem was that the icon files were there, but I was not able to load any .png or .jpg file at all! It took me one whole day to figure out which package is the problematic one and emerge the ~amd64 version which resolved the problem for me. So if your image viewer applications are also not able to load existing .png files, you can try emerging gdk-pixbuf-2.30.1.ebuild. HTH, -Nikolay (In reply to Nikolay Kichukov from comment #3) > the icon files were there, but I was not able to load any .png or .jpg file > at all! It took me one whole day to figure out which package is the Mmh, I have no problems with viewing/editing PNG & Co -- I regularly use 'ristretto' and 'gimp'. So I guess the problem is elsewhere... > .png files, you can try emerging gdk-pixbuf-2.30.1.ebuild. I might try that anyway, though I see that gdk-pixbuf-2.30.1 is hard [M]asked. Is it safe? I can't afford to break my only system... Hi, this may not be related to the bug I experienced then. If you prefer to stay 'stable', do not install the masked package then. Cheers, -N you tried re-emerging the current gdk-pixbuf, right? (In reply to Samuli Suominen from comment #6) > you tried re-emerging the current gdk-pixbuf, right? I did (version 2.28.2). Icons are still missing :-( try `gtk-update-icon-cache -f /usr/share/icons/hicolor` and perhaps check for garbage in home directory's ~/.icons and ~/.local/share/icons i'm going to have to ask you to update gdk-pixbuf, like in Comment #3, if you can't figure out any other reason yourself, just to narrow this down (In reply to Samuli Suominen from comment #8) > try `gtk-update-icon-cache -f /usr/share/icons/hicolor` and perhaps check > for garbage in home directory's ~/.icons and ~/.local/share/icons That didn't work. > i'm going to have to ask you to update gdk-pixbuf, like in Comment #3 I recall I had the some problem on an Arch box which went away at a point, and indeed now gdk-pixbuf-2.30 is installed there. But the problem here is that it wants to pull in a major upgrade: # emerge -uDpv x11-libs/gdk-pixbuf These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U #] dev-libs/glib-2.38.2:2 [2.36.4-r1:2] USE="-debug (-fam) (-selinux) -static-libs -systemtap {-test} -utils -xattr" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 -python2_6" 6,561 kB [ebuild U #] x11-libs/gdk-pixbuf-2.30.1:2 [2.28.2:2] USE="X jpeg tiff -debug -introspection -jpeg2k {-test}" 1,265 kB [blocks B ] <dev-libs/gobject-introspection-1.38 ("<dev-libs/gobject-introspection-1.38" is blocking dev-libs/glib-2.38.2) ...plus the block caused by dev-python/pygobject-3.8.3 (>=dev-libs/gobject-introspection-1.34.2) I'm definitely reluctant in venturing in what seems an unmask cascading nightmare, unless there's a safe profile that I can't use without too much tinkering -- I'm currently with "default/linux/amd64/13.0/desktop". Good news! After a huge system cleanup + 'emerge --depclean' + reinstallation of x11-themes/hicolor-icon-theme x11-themes/gnome-icon-theme everything is back to normal :-) I couldn't actually trace to where the breakage happened but I suspect a nasty mix of gtk and gtk3 USE flags (now they're both globally disabled). In particular I removed "x11-themes/gtk-engines-xfce". Also, gdk-pixbuf had nothing to do with this issue... I guess this bug can now be marked as RESOLVED. (In reply to sphakka from comment #10) > I guess this bug can now be marked as RESOLVED. agreed. however, too bad we never figured out the root cause. |