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.
KDE has a long history of re-inventing, so I'm certain there is a file which does the same as .xinitrc and/or .xsession, only it's named differently.
Thats unfortunate, but that brings me to the rabbit whole of why the hell do we now have multiple gtk versions along with QT and probably other libraries. Sucks that there is no one stop shop for a toolkit, as this is the downside - inconsistency.
Quote:
Originally Posted by elcore
Only KDE devs can recommend this to you. Slackware just ships what they shared on kde.org.
If it were up to me, which is not, I'd tell you it's best to rewrite a /usr/bin/startkde script from scratch.
But that's just my opinion because I'm not a kde user, if you want official recommendation it's probably best to look at kde.org.
Well then I am shit-out-of-luck then, as I have no clue how to write a script and me deep diving into the internals of a DE just to write scripts is not up my alley, nor do I have the interest or time to learn it. I am in the end a user, and I am willing to go so far... Oh well.
Thats unfortunate, but that brings me to the rabbit whole of why the hell do we now have multiple gtk versions along with QT and probably other libraries. Sucks that there is no one stop shop for a toolkit, as this is the downside - inconsistency.
tell me about it... I use a GTK2 theme and have made both QT4 and QT5 inherit it, so I achieve an almost consistent desktop. What leaves me speechless is that QT4/5 can use GTK2 themes, but GTK3 cannot.
tell me about it... I use a GTK2 theme and have made both QT4 and QT5 inherit it, so I achieve an almost consistent desktop. What leaves me speechless is that QT4/5 can use GTK2 themes, but GTK3 cannot.
That is probably an issue with how gtk3 works? Also isn't gtk up to version 5 or even 6? Not like it matters, because I don't know of many or any apps that uses that; and even worse, there is no compatibility with gtks , it all is broken - as the devs do not see the need or just do not want to implement compatibility between versions. So thats why i can see projects like GNOME trying to break away from gtk and use something like libadwaita; sure downside is maybe no more themes or it is more difficult - but now you have a guaranteed standard to just work and important of all, consistency.
My issue is that modern apps, seem to just have ....regressed - I see this now even in Windows 10, even Microsoft's own utilities do not respect its own themes. You can be in dark mode, but the Microsoft Management Console is STILL bright , so you have that clashing with your dark theme......
Also case in point, look at clipgrab - and the bright part...
I imagine this is something with QT5 , but again this to me is just unacceptable in "current year"...... And why I keep wishing for the good old days of the Windows 9X style....everything for the most part back then .... was at least consistent. Oh well, I am just ranting and pissing in the wind with this post obviously.
Already got one of those, background thing is defined somewhere in source code I just haven't bothered to find it.
Why should you though? This proves my point - yes yes I know, open-source and all - but not everyone of us is inclined to just fudge with the code. It just seem almost low-effort on the devs part if indeed it is something this trivial as you seem to imply.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.