Bug 198333
Summary: | KDE update loses Control Centre | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike Cohler <mdc1> |
Component: | kdebase | Assignee: | Than Ngo <than> |
Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | arequipeno |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-11 13:42:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Cohler
2006-07-11 06:56:21 UTC
It seems your local setting has caused this problem. Please try following steps to fix this problem: - remove the directory $HOME/.config - restart KDE, you should probably start kbuildsycoca afterthat Does it work again? I followed your instructions - and removed the directory .config and restarted KDE This did not fix the problem, but after running kbuildsycoca then the K menu seems better apart from the fact that IO now no longer have my Crossover menu nor the associated Menu for Windows apps. Also this did not re-create the .config directory. Mike The control centre menu was there after running kbuildsycoca but I had to re-install Crossover to get the Crossover menu back. There seems to be a problem with this KDE update release - but also an incompatibility with Crossover which has never occurred before now. However perhaps others are seeing this problem even without Crossover being installed. I therefore think this is quite urgently in need of a fix. Your menu setting has been lost in this case after removing the directory $HOME/.config. I will push new kdelibs package into fc5-update-testing today. It should resolve this issue. Thanks for your report, The new kdelibs package (vers 0.4) fixes this and all is now well - so this bug can be closed. Thanks Mike |