Summary: | after removing kdm, the kcm_kdm systemsetings icon is still present | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Christian González <christian.gonzalez> |
Component: | general | Assignee: | System Settings Bugs <sourtooth+ssbugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | cfeck, kde |
Priority: | NOR | ||
Version First Reported In: | 4.9.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christian González
2012-08-16 12:05:30 UTC
Does running "kbuildsycoca4 --noincremental" between removing kdm and starting System Settings help? 2012/8/16 Christoph Feck <christoph@maxiom.de> > https://bugs.kde.org/show_bug.cgi?id=305253 > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |christoph@maxiom.de > > --- Comment #1 from Christoph Feck <christoph@maxiom.de> --- > Does running "kbuildsycoca4 --noincremental" between removing kdm and > starting > System Settings help? Yes, perfectly. after running "kbuildsycoca4 --noincremental" the kdm entry is gone. So where is the problem? Is this a packaging bug - there seems to be this command missing in the postrm script of apt in (K)ubuntu (what I'm using)? Normally after removing a kde component that has a link in systemsettings there should be run this command, right? Should I report it in Launchpad/Ubuntu? > So where is the problem?
I have no idea. Normally, I would expect that removing files from the service directories would trigger an sycoca refresh, but it could also be a bug in System Settings itself.
Reassigning.
How can I help? kded4 is responsible for firing the kbuildsycoca4 process off. System Settings will need to be restarted however for old modules to disappear. KDM no longer exists in Plasma 5 |