jlsalvador
Yes, using xrandr in the /etc/sddm.conf
(https://man.archlinux.org/man/sddm.conf.5#DisplayCommand=) /usr/share/sddm/scripts/Xsetup
.
Hahaha. Common problem with multiscreen with different resolutions. Your laptop screen is below and left of your main display, and X11 renders this black “virtual screen”.
There are multiple solutions:
a) Set your screen resolution and position through KDE Plasma SystemSettings and push the button “apply to SDDM configuration” (I think Plasma 6.0 removed this option, try to find it in the SystemSettings KCM SDDM section).
b) The another solution is the old one. Create a file into /etc/X11/xorg.conf/display.conf
with the proper values of position and resolution. Search in a wiki about examples (archlinux wiki?).
c) There is a third one that I used few years ago. SDDM allows you run any command after the screen initialization. So you can exec your xrand command here. Search about /etc/sddm.conf
When you create a filesystem, there is a parameter named as “block percent free”. This parameter should be “5%”, so a 5% of your partition size can only be written by the “root” user.
You can decrease this value or just free some space. You can try to create files or folders as root as well.
I think that the reason is the same for “why is XMPP mentioned more than IRC?”. IRC has more clients, it’s less resources hungry and simpler than XMPP.
I think that the reason is because it is old-fashione, and it’s clients feel outdated and (native) “lacking features” compared to more popular clients like Discord, WhatsApp, Messenger, Telegram or Signal. 🤷♂️
I can imagine my cousins using any of the clients I mentioned before, but not IRC, XMPP, or any protocol from my era. Life and traditions, isn’t it?
The last year 2023 was incredible (providing a lot of good games).
Fils Aime: ‘Thank you, but I want more.’ ‘Thank you, but give me more.’ I mean, it is insatiable. 2012 https://kotaku.com/the-trouble-with-the-never-satisfied-gamer-5920572
#!/usr/bin/env bash
A folder dotfiles
as git repository and a dotfiles/install
that soft links all configurations into their places.
Two files, ~/.zshrc
(without secrets, could be shared) and another for secrets (sourced by .zshrc
if exist secrets).
I used Tekton for the last two years, and I didn’t like it. One of the reasons is the community split around Tekton Hub between versions 3 and 4. Another reason is that it’s not very Kubernetes native. While you write YAML, there are a subset of instructions that limit you regarding mundane things you can do on Kubernetes but Tekton doesn’t support, such as mounting different PersistentVolumeClaims or setting tasks by platforms or nodes (amd64, arm64, etc).
I was so frustrated that I created my own Kubernetes-native CI/CD solution. Currently in development phases (when it is done, I will publish it here). This one uses real native Kubernetes components (jobs). You create Webhooks that launch Workflows, and Workflows can launch other Workflows or Jobs. You can do anything in a Job with no limitations other than Kubernetes itself. Take a look if you want: https://github.com/jlsalvador/simple-cicd