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.
For example, try to configure into Konsole to use the BOLD fonts, then go to KDE Settings and within Fonts page, change something. You will notice that Konsole will not show the consoles in BOLD anymore.
More importantly, same misfeature manifests within editors, i.e. Kate or KWrite, regarding their syntax highlighting where some keywords should be rendered in bold.
The solution which I found for fixing this crappy behavior is to manually edit the Plasma5 configuration files, and to remove the trailing ",Regular" from the font options, then to restart the Plasma5.
It is not our fault that KDE4 is "obsolete" today, while Plasma5 is not ready yet.
And there is is an entire World full of software which does not depends on Qt5 or Qt4. However, I believe is nothing wrong to adopt Qt5 - BUT only that, nothing more.
To be honest, I am of opinion to go back to roots and to remember the old good Slackware slogan: it is ready when it is ready.
Last edited by Darth Vader; 07-02-2018 at 08:08 AM.
It is not our fault that KDE4 is "obsolete" today while Plasma5 is not ready yet.
And there is is an entire World full of software which does not depends on Qt5 or Qt4. However, I believe is nothing wrong to adopt Qt5 - BUT only that, nothing more.
To be honest, I am of opinion to go back to roots and to remember the old good Slackware slogan: it is ready when it is ready.
It is ready. Except for you and your shitty graphics card.
For example, the font issues from Plasma5 has no connection with the graphics card which is used.
Its a known bug and you know how to work around it. This is not the first time a buggy software can be included in Slackware. Use another terminal. I know about four that is included in Slackware. You need a editor? Use Emacs, also included in Slackware.
This is not the first time a buggy software can be included in Slackware.
What other buggy software is in Slackware? Are there issue reports for these? Ideally buggy software should be fixed or replaced by something less buggy. Also one program with bugs is never a good argument to add other software with bugs.
What other buggy software is in Slackware? Are there issue reports for these? Ideally buggy software should be fixed or replaced by something less buggy. Also one program with bugs is never a good argument to add other software with bugs.
Thunderbird does not remember the last window position
Could you please take your conversation somewhere else Darth Vader and stoffepojken? This thread is for requests not arguing about Plasma and "buggy software". TIA
Could you please take your conversation somewhere else Darth Vader and stoffepojken? This thread is for requests not arguing about Plasma and "buggy software". TIA
Agreed. I'm getting really sick of reading this stuff in every thread.
Any chance of getting AlienBOB's multilib glibc/gcc, and compat32-tools merged into slackware64 proper?
I do get why Slack would want to steer clear of merging something like slackpkg+ and all of the pre-built *-compat32-* libraries into the main tree, although it does simplify the process of getting multilib up and running - it would add a whole load of new baggage into slackware proper.
But AlienBOB's multilib gcc/glibc and compat32-tools are absolutely invaluable for getting a multilib system up and running. The user would then still be required to convert the 32-bit packages from slackware(-32) into their own system anyway, in that instance.
Any chance of getting AlienBOB's multilib glibc/gcc, and compat32-tools merged into slackware64 proper?
Patrick Volkerding said multiple times that he does not intend to transform the Slackware64 in a Multilib solution, so it will stay pure 64-bit, and that's a design choice made even before the creation of Slackware64.
I bet that Slackware64 will be always a pure 64-bit operating system.
Last edited by Darth Vader; 07-02-2018 at 02:34 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.