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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If you accidentally (or not) click/hold and drag the left mouse button from the inner area ("client" or "any empty area") in a KDE/QT window, it starts to be dragged/moved along, but it's not dropped when you release the button, unlike the behavior with GTK windows (at least GTK2, I guess). You got to press "enter" or "esc", I guess.
Presumably that doesn't happen under KDE proper/kwin, maybe not even with other window managers, but I didn't...
At least in Ubuntu wily, it doesn't seem to allow you to chose the default application to open a file type. You try to do it, but it "magically" restores the previous default association before your eyes. Even if you chanced the config file, somehow. (I'm assuming it's mimeapps.lst, but I'm not sure. It seems that it's cool nowadays to have cryptic, hidden config files, avoiding to mention them unless strictly necessary, pretending it's all magic and config files don't exist)
Whereas gtk-qt-engine doesn't work very well, that is, GTK can't be easily made to "simulate" QT/KDE themes, the converse seems to work very well, and apparently no additional package is needed for that, but QT alone, or actually just qtconfig-qt4, in order to set the QT/KDE* theme as "GTK+".
So one third of the problem of desktop uniformity is solved if you have one GTK2 (I believe it's GTK2, not 3, I'm not sure) theme that you find good enough to have both in...