| Summary: | KDE 4.6.4 displays generic icon for all app menus | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin von Gagern <Martin.vGagern> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Martin von Gagern
2011-06-17 09:15:57 UTC
I suffered from the same problem and running kbuildsycoca4 --noincremental as the affected user fixed the problem immediately. (In reply to comment #1) > kbuildsycoca4 --noincremental Thanks! That made the menu entries appear immediately. The Alt+F2 runner required a logout+login to work as expected; it probably had things cached somewhere. Now the only remaining issue that I can see on my system is that the menus in the K Menu application list have no individual icons, but instead all share an icon that looks like "unknown document type", i.e. a question mark on a blank sheet of paper. Should I file a separate bug report for this? Is there some way you can force automatic execution of the kbuildsycoca4 command? So that users won't behit by this once you stabilize it? I guess you could simply "rm -f /var/tmp/kdecache-*/ksycoca4*" in pkg_postinst. Ideally using EAPI=4 and checking REPLACING_VERSIONS first. Not sure what that would do to currently active sessions. Perhaps you have a better idea. Never heard about the icon problem, do you still have it? You can also try re-emerging kde-env, rebooting your system and then re-running kbuildsyscoca4 (but unless you have been using very early preversions from the kde overlay, that should not be necessary)... (In reply to comment #3) > Never heard about the icon problem, do you still have it? Yes. It's only affect ing menus, mind, not the apps themselves. > You can also try > re-emerging kde-env, rebooting your system and then re-running kbuildsyscoca4 > (but unless you have been using very early preversions from the kde overlay, > that should not be necessary)... Have never used the kde overlay (kde-sunset only), but will give it a try nevertheless. As you've changed the subject of this report here to only match the icon issue, have you dealt with the original problem in some way that won't force every user to run kbuildsycoca4 manually? (In reply to comment #4) > Have never used the kde overlay (kde-sunset only), but will give it a try > nevertheless. You dont have to... there was a buggy ebuild in the overlay once that might have caused similar problems. I was just asking to check... > As you've changed the subject of this report here to only match the icon issue, > have you dealt with the original problem in some way that won't force every > user to run kbuildsycoca4 manually? Not so far... it's a well-known problem, mentioned in the Gentoo KDE guide and for sure in quite some forum posts. Should (I think) also just be solved by logging out and in in some cases. (In reply to comment #3) > Never heard about the icon problem, do you still have it? You can also try > re-emerging kde-env, rebooting your system and then re-running kbuildsyscoca4 Did that, and problem persists. (In reply to comment #5) > Not so far... it's a well-known problem, mentioned in the Gentoo KDE guide and > for sure in quite some forum posts. OK, I guess I never really read that one... have you ever discussed automatic removal of outdated databases, as suggested in comment #2? > Should (I think) also just be solved by logging out and in in some cases. I believe I had logged out and in before posting this report, so that didn't do the trick for me. How about kde-4.6.5 or 4.7.0? Specifically 4.6.4 was broken in many ways... No change with KDE 4.7.0 and after running kbuildsycoca4 --noincremental. :-( Can you give feedback for kde 4.7.2? (In reply to comment #9) > Can you give feedback for kde 4.7.2? Appears to be resolved there. Feel free to mark this bug OBSOLETE. Done. |
