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 see there are some additions in the x86_64 folder. Maybe its time to give these packages another spin. I had a few problems when I first tried them. They were not show stoppers, but did create some problems between dolphin and konqueror.
I do think it could go without the above irony. Anyway, some packages should be removed from the stock slackware installation before upgradepkg --install-new *.t?z
I do think it could go without the above irony. Anyway, some packages should be removed from the stock slackware installation before upgradepkg --install-new *.t?z
It was written without irony in mind. Also, why do you think some packages would need to be removed?
Also, why do you think some packages would need to be removed?
Eric
Because maybe two versions of KDE could not be present concurrently on the same system, could they? I think it should be necessary to first remove KDE-4.2 and then install the packages from KDE-4.3.
Because maybe two versions of KDE could not be present concurrently on the same system, could they? I think it should be necessary to first remove KDE-4.2 and then install the packages from KDE-4.3.
And what happens if there is in KDE-4.2 some package that is no longer present in KDE-4.3?
In that case there would have been a README to explain in what order to remove and install packages... you are trying very hard to make things more difficult than needed - I am unsubscribing from this thread. Good luck.
Hi, I'm also trying currently these packages, and seems to work good, but not all features are complete, I think.
KDE wasn't able to install new icon themes, and other features from kdelook.org while using built-in dialogs.
Right after install, there was complete lack of icons on desktop, sidebars and in menus. I was able to restore those icons using Control Center, and now it's look good, but I was confused if the system is crashing, or just hang up...
It's important to remember with KDE 4.x that, whenever you upgrade it, you have to delete your old preferences and start from scratch! (rm -r ~/.kde) I have experimented with using preferences from, for example, 4.2 in 4.3, and I see lots of crashes and erratic behavior as described in this post and others. If I start with fresh prefs, I see none of it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
32 bit packages
).
