LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   All Things KDE5/Plasma for Slackware Users. (https://www.linuxquestions.org/questions/slackware-14/all-things-kde5-plasma-for-slackware-users-4175670109/)

Jeebizz 09-25-2021 10:58 AM

Quote:

Originally Posted by z80 (Post 6286825)
This is not a problem with Plasma. I get similar memory usage when starting XFCE.

Really?! And XFCE is supposed to be 'lightweight' compared to something like KDE. I wonder if MATE 1.26 will be this heavy on Slackware 15... I'll have to then probably take a look again at LXQT then even. I'm kinda in the middle, much too lazy to use something like xmonad or other tiling WMs, and even too lazy for Fluxbox or OpenBox - for a time LXDE was a good compromise I felt, not too heavy and for me offered the full "desktop experience." Hell I'll have to even look at Cinnamon now if / when there are packages available for 15.0 when it is ready.

Again if I wouldn't mind even using MWM, doesn't even reach 200MB of usage, but customizing and configuring it again seems like a pain, and tried to follow the man pages but..... tl;dr , mostly.

cwizardone 09-25-2021 11:24 AM

This week's new features, bug fixes and improvements,
https://pointieststick.com/2021/09/2...a-on-the-move/

enorbet 09-26-2021 08:33 PM

Anybody know why some Plasma "get new features foo" in System Settings fails with QT error
Code:

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-fooUser
when /tmp/runtime-User exists?

LuckyCyborg 09-27-2021 01:58 AM

Quote:

Originally Posted by enorbet (Post 6287146)
Anybody know why some Plasma "get new features foo" in System Settings fails with QT error
Code:

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-fooUser
when /tmp/runtime-User exists?

Because you have somehow XDG_RUNTIME_DIR not set? How you managed this?

Code:

vanya@darkstar:~# echo $XDG_RUNTIME_DIR
/run/user/1000
vanya@darkstar:~#


pm_a_cup_of_tea 09-27-2021 02:59 AM

Keyboard layout
 
Hi, I am sorry if this is a bit of a stupid question but I am having trouble with changing my keyboard layout in KDE.

Usually I am an XFCE4 user but yesterday I decided to spend an evening having a look at KDE. I went through all the settings, playing around with how I could configure it. All was going smoothly until I got to "Input Devices". I changed my layout from English(US) to English(UK) and removed the (US) entry but I'm still stuck on a US keyboard. I added a shortcut too thinking it might prompt KDE to switch layouts but no success. Outside of X11, on a tty, my keyboard is as it should be and XFCE4 is happy for it to be British.

Am I missing something really simple?

pm_a_cup_of_tea 09-27-2021 05:44 AM

Quote:

Originally Posted by pm_a_cup_of_tea (Post 6287177)
Am I missing something really simple?

It would seem I needed to activate 'Startup and Shutdown' > 'Background Services' > 'Keyboard Deamon'...

...I think...

..Nevertheless its working. My apologies for the interrupt

enorbet 09-27-2021 09:06 AM

Quote:

Originally Posted by LuckyCyborg (Post 6287172)
Because you have somehow XDG_RUNTIME_DIR not set? How you managed this?

Code:

vanya@darkstar:~# echo $XDG_RUNTIME_DIR
/run/user/1000
vanya@darkstar:~#


I didn't originally know to do that (if I'm not mistaken XDG is new with Pam/elogind) but I don't ask questions here without researching first so I have run that exact command and still on some apps get that error message. In researching it I see that the problem isn't very common but it does exist. It doesn't prevent anything crucial so far but it is a wrinkle I prefer to iron out.

FWIW I'm far more concerned why in Dolphin and System Settings trying to do something that requires elevated privileges, a login prompt is not popped up... but that, too, isn't a huge deal... there are workarounds. It's just curiosity.

Jeebizz 10-01-2021 12:19 PM

So I accept that KDE is just going to start with 1GB from a cold start sooner or later, after startx finishes - right now it clocks in at 915M according to htop.

I just checked XFCE, cold started again - start x , and htop reports 835M -- I think at this point XFCE can no longer be considered "lightweight" as it seems just barely below Plasma5.

This is all on --Current all up to day's updates on Fri Oct 1. I'll have to now look back to MATE 1.24 (no 1.26 packages I have seen yet), or reluctantly go to LXQT.

marav 10-01-2021 12:35 PM

Quote:

Originally Posted by Jeebizz (Post 6288159)
So I accept that KDE is just going to start with 1GB from a cold start sooner or later, after startx finishes - right now it clocks in at 915M according to htop.

I just checked XFCE, cold started again - start x , and htop reports 835M -- I think at this point XFCE can no longer be considered "lightweight" as it seems just barely below Plasma5.

This is all on --Current all up to day's updates on Fri Oct 1. I'll have to now look back to MATE 1.24 (no 1.26 packages I have seen yet), or reluctantly go to LXQT.

After a cold boot:
Code:

blackstar :: ~ free -m                   
              total      used      free    shred  cached  available
Mem:          15417        679      13973          13        764      14449

just by disabling some unwanted stuff under plasma settings / autostart and akonadi

Jeebizz 10-01-2021 12:41 PM

Quote:

Originally Posted by marav (Post 6288167)
After a cold boot:
Code:

blackstar :: ~ free -m                   
              total      used      free    shred  cached  available
Mem:          15417        679      13973          13        764      14449

just by disabling some unwanted stuff under plasma settings / autostart and akonadi

I always remove Akonadi (advanced slackware install and uncheck Akonadi) - but I am keen to ask, what did you disable to slim down KDE ?

marav 10-01-2021 01:21 PM

3 Attachment(s)
Quote:

Originally Posted by Jeebizz (Post 6288170)
I always remove Akonadi (advanced slackware install and uncheck Akonadi) - but I am keen to ask, what did you disable to slim down KDE ?


mainly, in my .config/autostart/ (Hidden=true)
Code:

fcitx-autostart.desktop
org.kde.korgac.desktop

in /etc/rc.d : nothing more than a fresh&clean install

And from plasma settings /startup & shutdown / background service:
Code:

free space notifier
input actions
kmix daemon
ksysguard
network proxy
plasma browser integration
remote url
removable device
wacom tablet
write daemon

My autostart programs:
a very small conky (showing only the slackware logo at the bottom right + kernel version + ram used)
yakuake

EDIT : the 2nd screenshot, after a restart (661 Mo)
the conky memory command line:
Code:

free -h | awk '/Mem/,$0=$3' | sed 's/\(.\)i$/ \1/'
EDIT2 : ps faux in attach.

As you can see I like things uncluttered...
I trust Patrick to do things cleaner than me. So I try to keep the installation as close as possible to a fresh install

cwizardone 10-02-2021 06:53 AM

"Getting Plasma 5.23 Ready For Release"
This week's new features, bug fixes and improvements,
https://pointieststick.com/2021/10/0...y-for-release/

enorbet 10-02-2021 11:28 AM

It really matters little which DE one chooses regarding resource usage. Far more important and effective is what services one allows or desires. It's not at all difficult to get KDE pared WAY down, even below 500MB, as long as you don't want or use such services. In my case, I do hover around 1GB at idle because I keep akonadai, Time and Date, Weather, NM, Notifications,and ballo on autostart and add HP printing, Corsair keyboard lighting control, Conky, and more. I consider 1GB pretty light when compared to 16GB system RAM. 1/16th isn't too high a cost for those services to me.

I can still configure, compile and install a custom kernel in about 15 minutes on an i5 boxen.

Jeebizz 10-02-2021 12:22 PM

Quote:

Originally Posted by enorbet (Post 6288414)
It really matters little which DE one chooses regarding resource usage. Far more important and effective is what services one allows or desires. It's not at all difficult to get KDE pared WAY down, even below 500MB, as long as you don't want or use such services. In my case, I do hover around 1GB at idle because I keep akonadai, Time and Date, Weather, NM, Notifications,and ballo on autostart and add HP printing, Corsair keyboard lighting control, Conky, and more. I consider 1GB pretty light when compared to 16GB system RAM. 1/16th isn't too high a cost for those services to me.

I can still configure, compile and install a custom kernel in about 15 minutes on an i5 boxen.

Overall I agree; but then again some services to me are superfluous and I can live without - such as the bluetooth service on my desktop - I don't have bluetooth anything , so ... I don't need it. I am legit interested in trimming down KDE - and yes I realize that also kinda might go against the idea of a "fully featured" desktop environment - but at the same time - if there is something there that I don't use ever, well why shouldn't I get rid of it? I mean I also don't see myself using the kfloppy utility - sure its not using any memory other than disk space, unless I obviously launch it - but I don't have any kind of floppy drive so, bye to kfloppy. I realize also the next thing to eat RAM obviously is the god damned web browser, but oh well. I don't see myself using lynx or something like Midori either because unfortunately the web is bloated and just might not even work well in Midori or other more lightweight browsers.

-edit

I still wish I could just not have baloo installed - but Dolphin complains; but at least balooctl disable suffices. Still, at least I can still get away with just outright not installing Akonadi - because again, Akonadi can go fsck itself.

Jeebizz 10-04-2021 01:13 PM

Alright so dumb question then , why is there such a discrepancy between the memory usage displayed of htop or top vs free ? I went back in, and also confirmed that free shows around 600M used, but htop shows almost 1GB (1GiB) - so what gives? :scratch:


All times are GMT -5. The time now is 07:32 PM.