how to install kwin decoration slackware 12.1 kde 3.5.9
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
how to install kwin decoration slackware 12.1 kde 3.5.9
I downloaded a window decoration from kde-look.org, called crystal (http://kde-look.org/content/show.php...?content=13969). I have extracted the files from the archive, ran (in the directory) ./configure --prefix=/usr
make
sudo make install
with no apparent warnings or errors, but nothing has changed in kcontrol. I have restarted kde a few times. I must be missing something obvious, can anybody tell me what I am not doing or doing wrong?
This is Slackware 12.1 with KDE 3.5.9 and QT 3.3.8b
Last edited by pauledwards03; 09-04-2008 at 10:43 AM.
If you really did it all ok, maybe it's just that make install is installing the binary files on a different location than this of kde, and so it can't find them.
You can use something like this to -hopefully- find the binary .so file for the theme:
Code:
find / -name 'crystal*.so'
Then you can do the same for a known theme like plastik or whatever, and check if the directory is the same. If it's not, then that might be the problem. Remember that when doing ./configure there are many parameters to specify where the things will go. Probably just using a correct --prefix will help to solve the issue.
Remember to do make uninstall before installing on a different prefix, just to clean a bit. However this theme is well known and old, are you sure that there's no slackware package for it?
Thanks for the reply. I tried the slackware package I found for it but it does not work either. I have also been unable to get deKorator to show up in the list either through a slackware package or compiling it. I have searhced for crystal*.so like this:
I assume that you already checked that the other window decos are on that same directory. If affirmative, then the only explanation I can think of is that the binaries can't be correctly loaded (due to some api inconsistency probably). But that wouldn't explain why the self compiled versions do not work (in this case the api should be consistent, or compilation would just fail).
I would also try an alternate user with a clean kde config, just in case.
I got a slackbuild for crystal 1.0.6 from slackbuilds.org and even that is not working? is there a file somewhere that you can change to force the window decoration?
just so people know .. I got it working, though it didn't show in kcontrol, if you edit ~/.kde/share/config/kwinrc to show the name of the decoration you want, it will work. (For me at least) Now it does show up in my decoration list and so do a bunch of others (B II Glow) that weren't there before but I did see the files in my travels..
Last edited by pauledwards03; 09-04-2008 at 12:24 PM.
You see the same theme in two places. This can only cause trouble. It seems you need to do some cleaning, and use only ONE method of installation at a time. If you are going to compile manually, first uninstall any slack package, or vice-versa.
It seems that plastik resides there, so, my guess is that crystal should be there as well, and not in /opt. Try --prefix=/usr. You might need to adjust some more path(s). Use ./configure --help to see the available options.
You see the same theme in two places. This can only cause trouble. It seems you need to do some cleaning, and use only ONE method of installation at a time. If you are going to compile manually, first uninstall any slack package, or vice-versa.
It seems that plastik resides there, so, my guess is that crystal should be there as well, and not in /opt. Try --prefix=/usr. You might need to adjust some more path(s). Use ./configure --help to see the available options.
I think he's already aware of that.
/opt/kde was created at some point when I was going through all this, I have since deleted it.. I have a bad habit of not cleaning up after myself when it comes to compiling, installing packages, or my office for that matter ... Every time I try a new distro or just do a reinstall I say to my self "this time I am going to keep it clean".. never happens.
/opt/kde was created at some point when I was going through all this, I have since deleted it.. I have a bad habit of not cleaning up after myself when it comes to compiling, installing packages, or my office for that matter ... Every time I try a new distro or just do a reinstall I say to my self "this time I am going to keep it clean".. never happens.
Yup. It's hard to keep it clean if you use manually compiled stuff, it requires a bit of discipline.
However, if you do this very often, then it's normal to have weird problems without even noticing where they come from. Note that when program search for a given library they will use the first instance they find most times, so old cruft might take precedence over new stuff, no matter how many times you reinstall.
If there's a native package, it's always better to use it, if it fails, complain to the maintainer of your distro. If you are not happy with the way that your distro manages this, and you have to compile a lot of packages by hand, then it's a sign that something is not going ok, and maybe it's also a sign that it's time to migrate to some other distro that suits your needs better.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.