https://raymii.org/s/tags/desktop.xml RSS feed for tag desktop on Raymii.org https://raymii.org/s/blog/Using_IceWM_and_sharing_my_config_and_tips_tricks.html?utm_medium=rss&utm_source=raymii&utm_campaign=tagrss https://raymii.org/s/blog/Using_IceWM_and_sharing_my_config_and_tips_tricks.html KDE is my desktop environment of choice. KDE5 is rock-solid, configurable in any way possible and works great. It treats you like a responsible adult instead of a child like GNOME does these days, and after XFCE switched to GTK3, the RAM usage is on-par, more often than not a bare KDE install (Debian or Arch) uses around 300MB ram. This is with Baloo (search indexer) and Akonadi (PIM database backend) disabled. Great default behaviour, low resource usage and enourmous configurability, so why is this post then titled 'IceWM'? At home I'm using a small ARM device (Raspberry Pi 4 with an SSD) as my main computer, and there resources are limited. KDE runs fine, but you notice that it is a bit slower than on my work computer. IceWM on the other hand, uses less than 30 MB of RAM and even less CPU. The program that gives you a desktop background, icewmbg, uses double the RAM of IceWM itself! IceWM, next to Awesome, is one of my favorite window managers, very configurable and provides all I need. This PC doesn't have multiple screens, which would be a bit more of a hassle than with KDE. After switching, the machine feels a lot faster. It's the small details in which I notice it, like text input, a few seconds of lag here and there. This post shows my IceWM config including some options explained, my IceWM theme and a few tips and tricks to configure the rest of the desktop. Sat, 10 Jul 2021 00:00:00 GMT Sat, 10 Jul 2021 00:00:00 GMT https://raymii.org/s/snippets/Record_your_Linux_Desktop_with_ffmpeg_and_slop.html?utm_medium=rss&utm_source=raymii&utm_campaign=tagrss https://raymii.org/s/snippets/Record_your_Linux_Desktop_with_ffmpeg_and_slop.html This two-line shell script allows you to record a region of your linux desktop to a video file, or a `.gif`, using `slop` and `ffmpeg`. I use it often when a screenshot is not enough, or when you need to explain a sequence of events to someone. Wed, 17 Mar 2021 00:00:00 GMT Wed, 17 Mar 2021 00:00:00 GMT https://raymii.org/s/articles/Limit_specific_process_memory_on_desktop_linux_with_cgroups.html?utm_medium=rss&utm_source=raymii&utm_campaign=tagrss https://raymii.org/s/articles/Limit_specific_process_memory_on_desktop_linux_with_cgroups.html On my laptop I recently had trouble with out of memory issues when running `clion`, `firefox`, `thunderbird`, `teams` and a virtualbox VM. To combat this, I've setup cgroups to limit how much RAM specific applications can use and configured `earlyoom`, a very nifty tool that checks available memory and kills the process with the highest `oom_score` if available memory falls below 5%. Otherwise, my laptop would first grind to a halt (even without swap) and only after half an hour of seemingly being stuck would the OOM killer kick in. With `earlyoom` this hanging behavior is gone, although sometimes applications get killed when I don't expect it. I've given firefox, thunderbird and teams a cgroup with memory limit and clion and virtualbox use their own configuration to limit their RAM usage.This post details how to setup `cgroups` to limit memory of specific processes including automatically placing process inside a cgroup. Sat, 13 Feb 2021 00:00:00 GMT Sat, 13 Feb 2021 00:00:00 GMT