SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently upgraded KDE with Swaret using the current and now have some errors.
when trying to change clock or trying to change things in Control Center, I get an error:
"---The diagnostics is:
Possible reasons:error loading the module.
An error occurred during your last KDE upgrade leaving an orphaned control module
You have old third party modules lying around.
Check these points carefully and try to remove the module mentioned in the error message. If this fails, consider contacting your distributor or packager---"
Please help give me some clue where to look or begin cleaning old modules. I don't know what to remove in opt/kde oe is it possible to do I have to do a swaret --remove kde3.1**?
Any hints would be appreciated. It also happens in root. I did not change anythin initially in swaret-- the new kde packages were just recently there.
Also: on a 2nd update-upgrade it gave me KDE packages again the next day i686 kde packages appeared. Are these really different from i486 packages: what is optimized for my system?
Either way the error mentioned appeared on the 1st upgrade. I since removed kde and reinstalled with the same problem.
I would suggest maybe to try pkgtool from the terminal while logged in to another environemnt (i.e. Gnome, Ice, etc). Have pkgtool remove ALL KDE (any version) first, then, after all KDE traces are removed, fire up Swaret and do swaret --update firt to download the lates list and then install all KDE, Qt, and ArTS from that list. All should be ok then.
Well, I've found that if I try to upgrade the KDE 3.1x series to KDE 3.2x series, that I have to also upgrade the Glibc libraries........
you might try upgrading the kernel "modules" package too.......
I've went round and round with some of these issues for my Juke box with Slack 9.0, I ended up just doing the kernel and modules upgrade and leaving KDE as it is.....
Thanks a bunch.
going down the package list I see i have 2 versions of qt installed and some other estras i will remove first.
My qt version installed is less than the latest one for kde 3.2.
I tried removing all packages with pkgtool and then using swaret again. When I triy to change my clock.
Same problem below:
error kde control module :error loading the module.
"he diagnostics is:
Possible reasons:
An error occurred during your last KDE upgrade leaving an orphaned control module
You have old third party modules lying around.
Check these points carefully and try to remove the module mentioned in the error message. If this fails, consider contacting your distributor or packager."
What i just would do (and I've done that) is download all the slackpacks for the kde things (new QT and dependencies included, and don't forget "fam-2.6.10-i486-1rob.tgz") you want to upgrade and then get out of kde, do an "upgradepkg" of each one of them, and then re-log in to kde.
Arrrggh!
It's worse when I don't understand how something fixed.
I turned on my computer this morning and all works. I rebooted last night, but it was still the same and had changed nothing.
Now I only get a font error when opening a shell: Font `-misc-console-medium-r-normal--16-160-72-72-c-80-iso10646-1' not found.
Swaret --dep gives me this:
% (libiconv.so.2) from Package 'fvwm-2.5.8-i486-3dms' NOT FOUND!
% (libgda-2.so.1) from Package 'glade-2.0.1-i486-1rob' NOT FOUND!
% (libgdasql.so.0) from Package 'glade-2.0.1-i486-1rob' NOT FOUND!
% (libgnomedb-2.so.3) from Package 'glade-2.0.1-i486-1rob' NOT FOUND!
% gnome-media-2.4.1.1-i486-1 (libgstreamer-0.6.so.0) requires at least gstreamer-0.6.4-i486-1!
% (libiconv.so.2) from Package 'gstreamer-0.7.4-i686-1pez' NOT FOUND!
% nautilus-media-0.3.3.1-i486-1 (libgstreamer-0.6.so.0) requires at least gstreamer-0.6.4-i486-1!
% (libbfd-2.14.90.0.5.so) from Package 'oprofile-0.6-i486-1' NOT FOUND!
% (libgtkspell.so.0) from Package 'pan-0.14.2.91-i686-1jto' NOT FOUND!
% (libmp3lame.so.0) from Package 'sox-12.17.4-i686-1' NOT FOUND!
% xpdf-3.00-i486-1rem (libXm.so.3) requires at least openmotif-2.2.2-i486-1!
Listing all available Packages to Get...
gstreamer-0.6.4-i486-1 (465 kB)
openmotif-2.2.2-i486-1 (4041 kB)
Originally posted by notAcoolNick check change log in slackware-current. i vaguely remember something about going back to previous version of Qt to be able to run latest KDE.
Here's the revelent portion of the slackware-current changelog notAcoolNick was talking about. It also talks about a font problem when upgrading to qt-3.2.3. Anyway, the changelog recommends reverting back to qt-3.2.2:
Quote:
kde/qt-3.2.2-i486-2.tgz: Reverted to Qt-3.2.2. I noticed (and it was also
reported by Peter Christy) that upgrading to Qt-3.2.3 breaks konsole's font
handling in exactly the same way as happened over the summer. I never did
find out how that was fixed (and couldn't find it myself last time) or I'd
see if I could fix it again. In any case, Qt is probably OK, but until KDE
syncs up to it we should probably use version 3.2.2. Most of the bugfixes in
Qt-3.2.3 were for other platforms, and AFAIK Qt 3.2.2 was working and finally
fixed some keyboard problems people were having.
IMPORTANT NOTE: If you're using an auto-update utility to keep your
Slackware system up to date, there's a chance it might take the opinion that
a larger version number is always better and will fail to revert to
qt-3.2.2-i486-2.tgz automatically. If you run into this, IMHO it should be
reported as a bug. Such an algorithm would make it impossible to ever revert
from a buggy upstream release to the previous one. Depending on the reason
for the package retraction (and there always is one on the rare occasions
it happens), leaving the package in place could be a security issue as well
as failing to address the problems leading to the package retraction. The
default behavior for such utilities should always be to keep in sync with the
online package set.
HTH
---thegeekster
------------------------------------
PS: Bottom line is to upgrade everything _except_ qt......
Last edited by thegeekster; 02-16-2004 at 07:37 AM.
Thanks for the help.
Qt is the culprit:
I needed to do a pkgtool remove qt(the newer version). It seems I had 2 of them on there.
Love the new kde and fluxbox.
One stupid question:
Is there any "real difference" between packages i386 or i686 on linuxpackages.net?
There is KDE for i686 if I remember correctly. Does anyone know a change in all this?
Originally posted by thom ...One stupid question:
Is there any "real difference" between packages i386 or i686 on linuxpackages.net?
There is KDE for i686 if I remember correctly. Does anyone know a change in all this?...
Actually, not as stupid as you may think. Technically, it depends on the '-march' flag used when compiling the source to make use of the instruction sets hardwired into each type CPU. i686 is for the modern processor which has enhancements not found on the older i486 processors. But whether it was actually implemented correctly or not, one can never be sure on precompiled packages, unless from the distributor itself. That's one of the reasons why I prefer to make my own packages.
I just upgraded to KDE 3.2 myself, and now I have a KMixCtrl problem when restarting KDE. It seems to be looking for ALSA, which I'm not using anymore (a topic for another post). .........................Other than that, it does seem to be rather nice.......
Sorry to switch back to the original topic, but I'm having the original problem. That is, upon trying to "adjust the date & time" in the KDE Panel clock, and subsequently entering the root password when prompted to, I encounter the error: "There was an error loading the module". The "possible solutions" suggested in the "Details" frame are identical to Thom Nuz posted in his first message.
I recently installed Slackware 9.1 on this computer and just upgraded KDE from version 3.1 to version 3.2. Because adjusting the clock time was broken in KDE 3.1, it was one of the first things I tried in KDE 3.2 . . . and now I find it still doesn't work. Agghhhh. . .
I first upgraded using the files in slackware-current/slackware/kde.
I used "upgradepkg *.tgz" followed by "installpkg *.tgz", as recommended in the install-package script in the kde directory, although I realized afterwards that I had misinterpreted Patrick Volkerding's recommendation and should have run only the upgradepkg utility.
Anyway, to my knowledge, I never had qt-3.2.3 on my computer and I don't have it there now, so I don't think that's the culprit in my case. (Slackware 9.1 comes with qt-3.2.1 and I have now upgraded to qt-3.2.2 with the above commands.)
When I encountered the problem with setting the clock, I installed swaret and used the "swaret --reinstall kde -a" command. This approach resulted in some library files being updated, but did not change the clock setting issue.
"swaret --dep" shows that "(libbfd-2.14.90.0.5.so), needed by 'oprofile-0.6-i486-1' NOT FOUND".
However, libbfd-2.14.90.0.6.so is present. I doubt this missing library has anything to do with kclock. There were no other dependencies shown as unfulfilled by "swaret --dep".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.