| Summary: | Upgrading to KDE 4.4.4 kills amarok 2.3.1-r1 tray icon | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Quasimodo <quasi> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Quasimodo
2010-06-29 22:21:55 UTC
This is probably caused by an upgrade of libpng I didn't noticed before. Recompiling 62 packages... Likely indeed... :) Please just reopen the bug if the problem persists. After rebuilding all the broken packages my revdep-rebuild is now clean. Sadly enough, the problem persists even after rebuilding amarok again and a restart. Also, on my secondary system I have the same problem despite it is x86, where there is no update of libpng yet. Try the following:
- open terminal
- kquitapp plasma-desktop (will terminate plasma)
- rm -fr /var/tmp/kdecache-${USER}/kpc (will remove icon cache)
- plasma-desktop (will start plasma again)
You will most likley have to do it after every KDE upgrade as KDE has broken icon cache invalidation mechanism and upstream frankly doesn't care.
See https://bugs.kde.org/show_bug.cgi?id=205257
(In reply to comment #4) > Try the following: > - open terminal > - kquitapp plasma-desktop (will terminate plasma) > - rm -fr /var/tmp/kdecache-${USER}/kpc (will remove icon cache) > - plasma-desktop (will start plasma again) > > You will most likley have to do it after every KDE upgrade as KDE has broken > icon cache invalidation mechanism and upstream frankly doesn't care. > See https://bugs.kde.org/show_bug.cgi?id=205257 > Nice idea but obviously not a solution to my problem because my temp directories are all on an tmpfs so there will be no cache after reboot. Also, I don't use kdw as a desktop (I'm using gnome) so there is no plasma-desktop running. In that case I'm closing this bug as a dupe of bug 325371 *** This bug has been marked as a duplicate of bug 325371 *** |