A system settings module is orphaned

[molloollom]

I just went over to disk and filesystems in the system settings app and I'm getting an error, it won't load. The error message is that it's not there or something. I ran kcontrol and I can't bring it up from there either. I don't know what happened, but I'd like it back. How do I do that? what do I need to search for in synaptic?

[SheeEttin]

Re: A system settings module is orphaned

Make sure the package "kde-guidance" is installed. If it is, try reinstalling it.

[molloollom]

Re: A system settings module is orphaned

It was there. I reinstalled it, no good. I completely uninstalled it and installed it again, still no good.

[Qqmike]

Re: A system settings module is orphaned

Hmmm. In 7.04, I got this, if it's what you are talking about:
K > System Settings > Advanced > Disks & Filesystems,
then the message:
The module Disk & Filesystems could not be loaded.
An error occurred during you last KDE upgrade leaving an orphaned module.
Or, You have old third party modules lying around.

I tried re-installing:
kde-guidance
kubuntu-desktop
I even tried re-installing KDE (107 MB).

I found nothing that helped. I finally gave up and installed 7.10, which means you would re-install. Unless someone has found a solution.

Good luck.

[molloollom]

Re: A system settings module is orphaned

I figured it out. The diagnostics thing that came up threw me off, because that was totally not what was wrong at all. Turns out it was a missing language pack.

Earlier in the week I had been having a problem with certain parts of the OpenOffice suite showing up options menus and the like with some kind of weird non-english language, and nothing I did would change it, so I uninstalled practically every language pack and re-installed openoffice. That fixed the problem there but gave me this one. After installing practically every language pack in synaptic that had -en in it, the module now works. Go figure.

The diagnostics ought to mention that in the error output, if it really does make that much of a dealbreaker. Would have figured it out sooner, but that was the only module that had any such error after messing with the language stuff.