#justlinuxthings — Public Fediverse posts

Ok, ich habe gerade das Cosmic Terminal gegen Ptyxis (aka Gnome Terminal) ausgetauscht. Das Cosmic Terminal lässt doch einiges an Komfort vermissen. 🙁

#JustLinuxThings #CosmicDesktop #Gnome

Ok, ich habe gerade das Cosmic Terminal gegen Ptyxis (aka Gnome Terminal) ausgetauscht. Das Cosmic Terminal lässt doch einiges an Komfort vermissen. 🙁

#JustLinuxThings #CosmicDesktop #Gnome

Okay today I managed to accidentally trigger “locked” function keys on my rather new M70 RK Royal Kludge. There is a modifier hotkey for this that I didn’t know of before (FN + LEFT CTRL) and I was lost for a hot minute how to turn it off again. Ah well, we’re still getting to know each other.

Anyway, I know from a previous attempt that RKGaming offers a webapp to configure the keyboard (especially it’s macro keys) on https://drive.rkgaming.com/. This works to this date only in Google Chrome (Webserial in Firefox is coming though). Here we can click a button and connect to the wireless receiver and… nothing. Ah yes, we’re on Linux PC and random browsers shall not write to our hardware devices. This is in principle a good idea and I did encounter this before with my Viture XR glasses so I had an idea where to start poking.

First things first: Confirming my theory I checked the browser console and sure enough it was not allowed to open the device:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:1 NotAllowedError: Failed to open the device.

There is also this special chrome://device-log/ address in Chrome that has some more details:

HIDEvent[12:08:56] Failed to open '/dev/hidraw10': FILE_ERROR_ACCESS_DENIED
HIDEvent[12:08:56] Access denied opening device read-write, trying read-only.

With this information we do have the Vendor ID (0x3554) the Product ID (0xfa09) and the subsystem (hidraw) in question. This is btw the dmesg output for the connected device, confirming what we know already:

new full-speed USB device number 17 using xhci_hcd
New USB device found, idVendor=3554, idProduct=fa09, bcdDevice= 1.02
New USB device strings: Mfr=1, Product=2, SerialNumber=0
Product: 2.4G Wireless Receiver
Manufacturer: CX

And a quick check on /dev/hidraw10 confirms that we simply to not have permission to read or write to this hidraw device, since it belongs to root.

crw-rw----. 1 root root 241, 9  8. Jun 12:05 /dev/hidraw10

Now a quick and dirty fix for the current session would be to simply change the ownership of that device but I really want this to stick around after the next reboot so I created the udev rule file /usr/lib/udev/rules.d/72-rk-royal-kludge.rules:

# Udev processes rules in alphabetical/numerical order. The actual
# application of the uaccess tag happens in systemd's built-in
# 73-seat-late.rules so make sure this is run *before* by saving 
# this as e.g. 72-rk-royal-kludge.rules
# uaccess tag means that logind assigns the permissions to users
# dynamically via ACLs according to which session is currently active
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"
SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"

Changes in such files have to be reloaded with e.g. udevadm control --reload. After that… nothing happens. This is because the device exists already so it’s time to unplug that receiver briefly. Now udev kicks in and creates the device files with the new rules applied. There is now a slight difference:

crw-rw----+ 1 root root 241, 10  8. Jun 12:34 /dev/hidraw10

The “+” indicates additional ACL rules. If you did not know about ACLs before: Oh boy, you’re in for a ride. Anyway, I confirmed that I now have access to this by checking the ACLs with e.g. getfacl /dev/hidraw10

# file: dev/hidraw10
# owner: root
# group: root
user::rw-
user:beko:rw-
group::rw-
mask::rw-
other::---

And presto. My user beko has read-write access. Another visit to https://drive.rkgaming.com/ yields a far better result:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:2388 Device [2.4G Wireless Receiver] is open

Now I can configure my keyboard on Linux PC via a gorram web application like any other cool kid in 2026. I say this because the app will probably have a half-life of 2 years and stop working soon enough again.

What a time to be alive.

#Linux #JustLinuxThings #udev #keyboard #RoyalKludge

This content is licensed under a Creative Commons Attribution 4.0 International license.

Okay today I managed to accidentally trigger “locked” function keys on my rather new M70 RK Royal Kludge. There is a modifier hotkey for this that I didn’t know of before (FN + LEFT CTRL) and I was lost for a hot minute how to turn it off again. Ah well, we’re still getting to know each other.

Anyway, I know from a previous attempt that RKGaming offers a webapp to configure the keyboard (especially it’s macro keys) on https://drive.rkgaming.com/. This works to this date only in Google Chrome (Webserial in Firefox is coming though). Here we can click a button and connect to the wireless receiver and… nothing. Ah yes, we’re on Linux PC and random browsers shall not write to our hardware devices. This is in principle a good idea and I did encounter this before with my Viture XR glasses so I had an idea where to start poking.

First things first: Confirming my theory I checked the browser console and sure enough it was not allowed to open the device:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:1 NotAllowedError: Failed to open the device.

There is also this special chrome://device-log/ address in Chrome that has some more details:

HIDEvent[12:08:56] Failed to open '/dev/hidraw10': FILE_ERROR_ACCESS_DENIED
HIDEvent[12:08:56] Access denied opening device read-write, trying read-only.

With this information we do have the Vendor ID (0x3554) the Product ID (0xfa09) and the subsystem (hidraw) in question. This is btw the dmesg output for the connected device, confirming what we know already:

new full-speed USB device number 17 using xhci_hcd
New USB device found, idVendor=3554, idProduct=fa09, bcdDevice= 1.02
New USB device strings: Mfr=1, Product=2, SerialNumber=0
Product: 2.4G Wireless Receiver
Manufacturer: CX

And a quick check on /dev/hidraw10 confirms that we simply to not have permission to read or write to this hidraw device, since it belongs to root.

crw-rw----. 1 root root 241, 9  8. Jun 12:05 /dev/hidraw10

Now a quick and dirty fix for the current session would be to simply change the ownership of that device but I really want this to stick around after the next reboot so I created the udev rule file /usr/lib/udev/rules.d/72-rk-royal-kludge.rules:

# Udev processes rules in alphabetical/numerical order. The actual
# application of the uaccess tag happens in systemd's built-in
# 73-seat-late.rules so make sure this is run *before* by saving 
# this as e.g. 72-rk-royal-kludge.rules
# uaccess tag means that logind assigns the permissions to users
# dynamically via ACLs according to which session is currently active
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"
SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"

Changes in such files have to be reloaded with e.g. udevadm control --reload. After that… nothing happens. This is because the device exists already so it’s time to unplug that receiver briefly. Now udev kicks in and creates the device files with the new rules applied. There is now a slight difference:

crw-rw----+ 1 root root 241, 10  8. Jun 12:34 /dev/hidraw10

The “+” indicates additional ACL rules. If you did not know about ACLs before: Oh boy, you’re in for a ride. Anyway, I confirmed that I now have access to this by checking the ACLs with e.g. getfacl /dev/hidraw10

# file: dev/hidraw10
# owner: root
# group: root
user::rw-
user:beko:rw-
group::rw-
mask::rw-
other::---

And presto. My user beko has read-write access. Another visit to https://drive.rkgaming.com/ yields a far better result:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:2388 Device [2.4G Wireless Receiver] is open

Now I can configure my keyboard on Linux PC via a gorram web application like any other cool kid in 2026. I say this because the app will probably have a half-life of 2 years and stop working soon enough again.

What a time to be alive.

#Linux #JustLinuxThings #udev #keyboard #RoyalKludge

This content is licensed under a Creative Commons Attribution 4.0 International license.

My package manager: you need to update your Mother
Me: I'm sorry, *what*?
Me, rereading the message: Oh, #Mutter has an update

#justlinuxthings #gnome #foss

My package manager: you need to update your Mother
Me: I'm sorry, *what*?
Me, rereading the message: Oh, #Mutter has an update

#justlinuxthings #gnome #foss

did some troubleshooting on my smb issues and it turns out it might be a kde bug: https://bugs.kde.org/show_bug.cgi?id=494981

i say might because all of this goes over my head and i cant do shit anyways since im on an immutable distro.

#JustLinuxThings

did some troubleshooting on my smb issues and it turns out it might be a kde bug: https://bugs.kde.org/show_bug.cgi?id=494981

i say might because all of this goes over my head and i cant do shit anyways since im on an immutable distro.

#JustLinuxThings

so i ran a live environment on @viz suggestion and enabling hdr was possible.

unfortunately couldnt test video file playback since the wifi driver didnt work and the video player would crash everytime i tried playing a video from external storage.

#JustLinuxThings

Ah yes.

#snap #JustLinuxThings

Ah yes.

#snap #JustLinuxThings

TIL on Linux you cannot rely on the timestamps of files in /proc/<pid> to give you information about a process start time: those might be reset on suspend of if a process gets a SIGSTOP.
Instead, one should look at the 22nd field of /proc/pid/stat: starttime.
But it gives you the process start time in system clock ticks, not seconds. So you must divide it by sysconf(_SC_CLK_TCK) to get seconds.
But wait, it gives you the start time in ticks since boot. So you must use clock_gettime(CLOCK_BOOTTIME, ...) to get a usable comparison to the current time.

Anyway, now progressrm should be more accurate at guessing the file arguments progression (and remaining time) of rm commands.

#Linux #ProcPid #uapi #JustLinuxThings

TIL on Linux you cannot rely on the timestamps of files in /proc/<pid> to give you information about a process start time: those might be reset on suspend of if a process gets a SIGSTOP.
Instead, one should look at the 22nd field of /proc/pid/stat: starttime.
But it gives you the process start time in system clock ticks, not seconds. So you must divide it by sysconf(_SC_CLK_TCK) to get seconds.
But wait, it gives you the start time in ticks since boot. So you must use clock_gettime(CLOCK_BOOTTIME, ...) to get a usable comparison to the current time.

Anyway, now progressrm should be more accurate at guessing the file arguments progression (and remaining time) of rm commands.

#Linux #ProcPid #uapi #JustLinuxThings

#justlinuxthings

#justlinuxthings

Oh, wow that one very specific problem I noticed with QT6 (but not QT5) KDE applications that everyone blamed the Nvidia driver for got resolved with a QT update.
WHO WOULD HAVE THOUGHT???

#JustLinuxThings

Oh, wow that one very specific problem I noticed with QT6 (but not QT5) KDE applications that everyone blamed the Nvidia driver for got resolved with a QT update.
WHO WOULD HAVE THOUGHT???

#JustLinuxThings

@peppe thaks man... it feels good, as I'm on the suck train for a while now 😅

Since I've switched themes, LightDM stopped working, and I can't log in until I first log in on an other TTY in text mode... Apparently opening the #LightDM greeter settings app screwed everything up? Now I'm looking for an alternative, but nothing else seem to support a "switch user" type feature?

#justLinuxThings I guess...

smh

#Linux #ArchLinux #ScreenLock #SSDM #DisplayManager

@peppe thaks man... it feels good, as I'm on the suck train for a while now 😅

Since I've switched themes, LightDM stopped working, and I can't log in until I first log in on an other TTY in text mode... Apparently opening the #LightDM greeter settings app screwed everything up? Now I'm looking for an alternative, but nothing else seem to support a "switch user" type feature?

#justLinuxThings I guess...

smh

#Linux #ArchLinux #ScreenLock #SSDM #DisplayManager

because #gimp 3.0 looks hideous with the (absolutely outdated) GTK theme I'm using, I wanted to change the system theme...

the issue is, I'm in #DWM on #ArchLinux, and I use the #XFCE bar, so I have the XFCE settings app installed, but the icon theme and gtk theme can not be changed from there.

luckily, I have #Cinnamon also installed, so I can log in there, use the settings app there, and that works.

why though?! #JustLinuxThings

#Linux #FreeSoftware

because #gimp 3.0 looks hideous with the (absolutely outdated) GTK theme I'm using, I wanted to change the system theme...

the issue is, I'm in #DWM on #ArchLinux, and I use the #XFCE bar, so I have the XFCE settings app installed, but the icon theme and gtk theme can not be changed from there.

luckily, I have #Cinnamon also installed, so I can log in there, use the settings app there, and that works.

why though?! #JustLinuxThings

#Linux #FreeSoftware

who up updating their kernel rn in the vague hopes it'll fix bluetooth pairing issues #justlinuxthings

@puppygirlhornypost2 #justlinuxthings (I'm assuming linux just from my own experiences haha)

@puppygirlhornypost2 #justlinuxthings (I'm assuming linux just from my own experiences haha)

Ach gucke man schau, mein #Manjaro hat mich vor x Zeiteinheiten automatisch von den testing-Paketquellen zu den stable-Paketquellen rübergeschoben.

Und ich wunderte mich schon, warum die Updates in letzter Zeit so spärlich kamen und ich noch nich in den Genuss von Xfce 4.20 kam.

#JustLinuxThings

Upon further investigations I unintentionally set up #Howdy to work with the regular video camera and not the IR sensor/blaster. I have since rectified the situation, with the help of the ‘linux-enable-ir-emitter’ utility.

#JustLinuxThings

Upon further investigations I unintentionally set up #Howdy to work with the regular video camera and not the IR sensor/blaster. I have since rectified the situation, with the help of the ‘linux-enable-ir-emitter’ utility.

#JustLinuxThings

My laptop had this weird issue where periodically start garbling all audio into like a weird metallic tone? It would just randomly crop up and off now and then, so I assumed it was like a hardware issue

today I decided to search for it just in case, and wow.

it turns out there's some software called speach-dispatcher? idk what it does, but apparently whenever it gets activated it screws up audio.

#justlinuxthings omg fml I hate linux so much

Everybody: Help! suspend isn’t working

Me: Help! Suspend _is_ working

So… today I noticed that I forgot something on my Fedora Workstation at home. No problem, we have Wireguard, no? So I asked a family member to start my computer at home, which they did, and I logged into my box via ssh.

After that I had to install a programm first before starting my work so I installed it via sudo. The dnf command succeeded and directly after that – to my _utter_ surprise – did the terminal print the message “The system is going into suspend NOW”.

And it was gone. Just like my family members, who left the building in the meantime. WoL didn’t succeed. Work delayed 🤷

I was flabbergasted. And I tried it again later at home. If I do not login via gdm… the system suspends on it’s own again!

What on earth is doing this and how can I stop this from happening again???

Update:

As mentioned in the comments this is a setting of Gnome but for the `gdm` user. “sudo -u gdm dbus-run-session gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep sleep” list all options and removing the timeout should prevent this: “sudo -u gdm dbus-run-session gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0”

This crept back in during one of the last dist upgrades though and failed with a permission error on the not existing path “/var/lib/gdm/.config/dconf/”. I just created the folder and set it’s permission to readwrite for “gdm”. After that I could set the ac-timeout to 0 again.

So, disabling #plasma extension on chromium made sound work again on #archlinux.

🫣😭😮‍💨😩

#JustLinuxThings

So, disabling #plasma extension on chromium made sound work again on #archlinux.

🫣😭😮‍💨😩

#JustLinuxThings

find doesn't fail if -exec fails with rc != 0

#justlinuxthings #linux

#justLinuxThings

```
Gesamtgröße des Downloads: 1739,11 MiB
Gesamtgröße der installierten Pakete: 5005,81 MiB
Größendifferenz der Aktualisierung: -190,72 MiB
```

Ich liebe #Linux manchmal.

I switched off iGPU in the BIOS because I saw a tip somewhere on the internets.

I can finally see boot messages on the console, but now lightdm won't start because Xorg fails with "No screens found". Log complains about /dev/dri/card0 not existing, but I have /dev/dri/card1

#JustLinuxThings

My bluetooth mouse only works if I have something (anything) plugged into the USB port... #JustLinuxThings

#GRUB taucht auf: :blobcatsunglasses:

#Linux Kernel nicht gefunden: :blobcattableflip:

#LFS #LinuxFromScratch #JustLinuxThings #LinuxExperience

Natürlich crashed die #Gentoo LiveCD kurz vor der Zielgeraden. Immerhin kann ich noch den Kernel im chroot bauen, aber ich brauche die Terminalcommands zum Kopieren. Das heißt, ich darf neustarten und alles neu mounten. :blobcattableflip:

#LFS #LinuxFromScratch #Linux #JustLinuxThings #LinuxExperience

Právě jsem viděla v gnome terminálu nastavení "povolit horké klávesy". Nemají hotkeys ustálený překlad něco jako "klávesy rychlé volby"? #JustLinuxThings