The Linux Thread - The Autist's OS of Choice

Darkholme's Dungeon said:
It could be something extremely stupid like misconfigured wifi/net settings, or it could be extremely complex and totaly not malicious bullshit written by pottering that's just buggy.
Click to expand...
Is that "gnome-system-monitor.desktop[2583]: glibtop(c=2583): [WARNING] statvfs '/run/user/1000/doc' failed: Operation not permitted" and stuff like "Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12)" some things really bad? Those were what seemed to be the recurrent issues. Also, it's just logging, so deactivating that alone doesn't cause any major issues? I doubt the OS can actually read the logs and do stuff with them to automatically correct issues like a person can...
 
  • Thunk-Provoking
Reactions: Vesperus
ToroidalBoat said:
Is that "gnome-system-monitor.desktop[2583]: glibtop(c=2583): [WARNING] statvfs '/run/user/1000/doc' failed: Operation not permitted" and stuff like "Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12)" some things really bad? Those were what seemed to be the recurrent issues. Also, it's just logging, so deactivating that alone doesn't cause any major issues? I dunno if the OS can read the logs and do stuff with them to automatically correct issues -- logs are for people.
Click to expand...
Not to be a jackass, I don't use systemd or GNOME :stress:. I think it should be safe to ignore. The issue is when you need logs to figure out what went wrong (like a failing RAM stick), and then you forget you don't keep logs...

2nd bug:
Here are the bugs though. Seems like GNOME needs to be whipped again.

First error is related to your task manager display. Seems like a regression (again) since they've patched it twice lmao. Try killing that app.

For the second error, try following this and rebinding whatever keysym 39 is.
 
Darkholme's Dungeon said:
First error is related to your task manager display. Seems like a regression (again) since they've patched it twice lmao. Try killing that app.
Click to expand...
Is that the System Monitor? At least neither issue looks serious.

Oh yeah, and is editing that one file with #storeage=volatile all it takes to switch logging to RAM?
 
ToroidalBoat said:
Is that the System Monitor? At least neither issue looks serious.

Oh yeah, and is editing that one file with #storeage=volatile all it takes to switch logging to RAM?
Click to expand...
Yeah its the system monitor. And I think so for the latter. You'll still need to address the root cause eventually.
You can also filter out those errors on Rsyslog supposedly. Might be a better solution to filter out the spam log errors since they're mostly harmless.
 
Not sure if this is the place but,
Does anyone else just Hate (capital H) that Brodie Robertson faggot?
Talk about ticking the boxes. Big fat sweaty literal neckbeard aaaaaand furry tranime avatar twitter account. Every time!
Fuck him for smearing more shit over my YouTube feed with his endless stream of daily Linux sloppa. Van de Paar quality content. His thumbnails also manage to grate me more than Mister Beast's creepy dead eyed ones.
Look at this shit! What the hell is going on with this mans face? Why do his eyebrows look like a 50 year old French bordello workers drawn on ones? Who does he think he is hiding his sweaty fat ass neck from with this wtf angle? God Damn It I just hate the sight of him and you cant get away from the cunts face if you go within 50 miles of a linux video on YouTube.
wtfisthis?.webp
 
  • Agree
  • Like
  • Informative
Reactions: Dread First, Wright, Ibanez RG 350EX and 20 others
ToroidalBoat said:
At least it's nothing serious (or so you say from what I gather anyway).
Click to expand...
Looking it up make sure you have xdg-desktop-portal installed. Maybe xdg-desktop-portal-gtk and xdg-desktop-portal-gnome installed too (I'm guessing you are running gnome or something) because that looks to be the root of the issue.

Or something along those lines

Or I should say it's potentially the cause of the /run/user/1000/doc one.

The other. You might be able to just lower the log level or something else to not get those keysym ones depending on what you are using. And also just keep the journal in memory.

For ext4 stuff. I always change my mount options to the ones suggested in the ext4 arch wiki where it talks about performance improvements. Maybe some of those could help slightly. With less frequent disk I/O

Almost forgot to post this. 😂
 
Last edited:
  • Informative
  • DRINK!
Reactions: Akerman, woowie queen, ⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛ and 1 other person
Geno Dolphin said:
Does anyone else just Hate (capital H) that Brodie Robertson faggot?
Click to expand...

He comes across as a dork who doesn't say what he means, and in the rare moment that he does, his takes are typical of a disingenuous asshole. You know how YouTubers catch onto people not looking past the title/thumbnail? They miss the popular sentiment that they come across as a fucking faggot right out the gate.
 
prollyanotherlurker said:
Almost forgot to post this. 😂
Click to expand...
I'd like to mention that it doesn't look like the domain blogs.gnome.org represents the opinions of the GNOME project itself, but instead that of individual contributors. SOMETHING THAT THEY SEEM TO NOT GIVE A FUCK TO ACTUALLY PUT ON THERE, BECAUSE FOSS TRANNIES ARE GENUINELY FUCKING RETARDED.

The author of those posts is the contributor Jordan Petridis. I can't even see what their contributions are because their gitlab profile is private. https://gitlab.gnome.org/alatiera

Supposedly, they are a """release engineer"""
1750798294332.webp
https://mastodon.social/@alatiera (Archive)


1750798238931.webp
1750798159629.webp

Fuck these people. My patience is at it's limits for these fucking want to be "thought leaders".

edit: some truly, 900000 IQ takes (he retweeted his own post a year later for some reason, thats the level of virtue signalling we are on that he mentally catalogs them. fatrick levels of cringe)
1750798581704.webp

oh and they transheart systemd. these people are fucking possessed man
1750798708990.webp
 
Last edited:
  • Lunacy
Reactions: HalHalliday and Anti Snigger
systemd is nice when it works but it's a pain in the ass when it has a tism fit. A good example is if you modify your grub entry for linux with init=/bin/bash, once you're done, if you try to reboot or shutdown via the shell, the kernel panics because of systemd and you have to power the system down.
 
  • Agree
  • Like
  • Informative
Reactions: Another Char Clone, Hieronymus Lex, Verpa Teutonica Ingens and 2 others
Anti Snigger said:
systemd is nice when it works but it's a pain in the ass when it has a tism fit. A good example is if you modify your grub entry for linux with init=/bin/bash, once you're done, if you try to reboot or shutdown via the shell, the kernel panics because of systemd and you have to power the system down.
Click to expand...
You sure that's a systemd issue? Because I've had the same thing happen with other init systems.
 
Anti Snigger said:
My sample size is 1 so no :jaceknife:
Click to expand...
Just thinking about it.

You probably need to put the root filesystem you want it to boot into, and the filesystem type. So the kernel will know what filesystem it needs to boot into. Then it can find the /use/bin/bash program to run.

All of that stuff is nornally taken care of by systemd and the initramfs (depending how you have stuff setup). I would add those to the kernel command line and see if that changes anything.
 
You must log in or register to reply here.
Back