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.
But im not have multimonitor , i read other commit , talking some break when resize windows size, i see the ramdom glitches , in that exactly case, resize to make big or small , but very random nor ever , i see 3 or 4 times only , the other symptom , when open browser i see ever , fixed all this on 5.23.1
ark 21.04 branch , works well , i can downgrade and all works nice again.
to test this , on dolphin , disable the option , "open new folders in tab"
If you have this enabled , when extract/compress something , you got a new tab , if extract again , same content but another one tab ...every time, one more tab , if you uncheck the option , the result , is new instances of dolphin every time to extract/compress something.
Last edited by USUARIONUEVO; 10-19-2021 at 04:31 PM.
Since the 25th Anniversary edition seems to have made it into RC1, I decided to check the memory usage again, and it is back down to the acceptable levels when going into Plasma5 - yes I still refused Akonadi , and I did exclude the kde4libs support - not sure if that has any bearing, but I am curious as to why that is there; as I haven't run into any issues with no kde4 lib support. Free shows 520M of usage, and htop 523M - much better, rather than almost 900M or so that it was last time.
Since the 25th Anniversary edition seems to have made it into RC1, I decided to check the memory usage again, and it is back down to the acceptable levels when going into Plasma5 - yes I still refused Akonadi , and I did exclude the kde4libs support - not sure if that has any bearing, but I am curious as to why that is there; as I haven't run into any issues with no kde4 lib support. Free shows 520M of usage, and htop 523M - much better, rather than almost 900M or so that it was last time.
slackyd , is nice tool to track missing things , nice for test when remove something , whats broke.
If i not remember bad , kmix use some time ago , but not now ...its incredible how some things continue needing libs from kde4 , cause not 100% ported.
khotkeys ,is for custom actions from combined keys , configured by user , the other 2 plugins from plasma , im not sure what do.
More packages use it ,but im not have installed , for a guide can see archlinux list for packages depends on kdelibs4
I installed the kde4 support package, luckily free and htop reports no increase in usage, so I'll leave that installed --- but Akonadi can still go fsck itself
So I switched to inittab 4, and chose the "maya" sddm theme (which is included), and instead of a normal login screen, I am greeted with the onscreen keyboard:
-edit
If I click the keyboard icon itself I am greeted with the login:
But still begs the question, why does the onscreen keyboard show up in the first place, I don't want it to at all.
-edit2
Instead of logging in, I opted to reboot on that screen - and now I am just greeted with a black screen after the reboot
Rebooted again, and now the onscreen keyboard popped up, and I was able to login after forcing it to use my real keyboard, but why does it exhibit this behavior ? I don't want / need the onscreen virtualkeyboard, this is dumb.
Rebooted again, and now the onscreen keyboard popped up, and I was able to login after forcing it to use my real keyboard, but why does it exhibit this behavior ? I don't want / need the onscreen virtualkeyboard, this is dumb.
Because you have not full install , use a tool to see what things you have broken , start installing vulkan.
Because you have not full install , use a tool to see what things you have broken , start installing vulkan.
it is now installed, and i am still getting this behavior , the only thing i still refuse to install is Akonadi - I still get a blank screen and if I click i get the login finally, but the onscreen keyboard still shows up at random ...
it is now installed, and i am still getting this behavior , the only thing i still refuse to install is Akonadi - I still get a blank screen and if I click i get the login finally, but the onscreen keyboard still shows up at random ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.