#justlinuxthings — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #justlinuxthings, aggregated by home.social.
-
My package manager: you need to update your Mother
Me: I'm sorry, *what*?
Me, rereading the message: Oh, #Mutter has an update -
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.
-
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.
-
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 aSIGSTOP.
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 bysysconf(_SC_CLK_TCK)to get seconds.
But wait, it gives you the start time in ticks since boot. So you must useclock_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.
-
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 aSIGSTOP.
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 bysysconf(_SC_CLK_TCK)to get seconds.
But wait, it gives you the start time in ticks since boot. So you must useclock_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.
-
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 aSIGSTOP.
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 bysysconf(_SC_CLK_TCK)to get seconds.
But wait, it gives you the start time in ticks since boot. So you must useclock_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.
-
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 aSIGSTOP.
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 bysysconf(_SC_CLK_TCK)to get seconds.
But wait, it gives you the start time in ticks since boot. So you must useclock_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.
-
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 aSIGSTOP.
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 bysysconf(_SC_CLK_TCK)to get seconds.
But wait, it gives you the start time in ticks since boot. So you must useclock_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.
-
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??? -
@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
-
@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
-
@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
-
@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
-
@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
-
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
-
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)
-
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.
-
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 -
So, disabling #plasma extension on chromium made sound work again on #archlinux.
🫣😭😮💨😩
-
find doesn't fail if -exec fails with rc != 0
-
```
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.
