The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
ToroidalBoat said:
So looks like the biggest offender is some kind of logging, with "systemd-jornald"
Click to expand...
Sounds about right...
9yb7zj2.webp
Welcome to Linux!
:story:
(slight edit)
 
Last edited:
ToroidalBoat said:
There's also "jbd2" doing some constant writing, though not as much. So what's this BS and how do I stop it?
Click to expand...
jbd2 is the journaling part of ext4. You can disable this with:

Code: 
sudo mke2fs -t ext4 -O ^has_journal /dev/drivename

But this will make the drive less resilient to corruption.

I also considered something that's probably causing some writes, if you're really trying to decrease writes: mount the drive with the "noatime" flag. "atime" records every time the file is accessed.
 
Betonhaus said:
What would be needed to install Xlibre on Linux Mint? Would the Linux Mint devs be forced to maintain it themselves if Debian and Ubuntu refuse to add it to their repositories?
Click to expand...
If you know how to compile a package it shouldn't be too difficult to start using it right now, but if you don't already know how to compile an application I would advise against trying to use XLibre at this early stage of development. It will take relatively no effort for Mint or any other distro to make their own XLibre package whenever they want to do that, they are not reliant on Ubuntu or Debian for this at all, although Debian will probably adopt XLibre eventually.
 
Just had to install a Win10 VM and icue to disable my corsair keyboard rgb after it reset itself. I tried openrgb and ckb-next, but neither recognized my K70. If anyone knows something I might have missed I'd appreciate it in case I have to do this again
 
analrapist said:
"atime" records every time the file is accessed.
Click to expand...
relatime has been the default for a very long time.
Code: 
relatime
      Update inode access times relative to modify or change time. Access
      time is only updated if the previous access time was earlier than
      the current modify or change time. (Similar to noatime, but it
      doesn’t break mutt(1) or other applications that need to know if a
      file has been read since the last time it was modified.)
Basically, atime is only updated one time after the file is modified and not on every access. And it looks like once per day after that.
Since kernel 2.6.30, so, 2009.

Anti Snigger said:
Just had to install a Win10 VM and icue to disable my corsair keyboard rgb after it reset itself. I tried openrgb and ckb-next, but neither recognized my K70. If anyone knows something I might have missed I'd appreciate it in case I have to do this again
Click to expand...
Couldn't you just use Fn + Keyboard keys to turn RGB on and off?
On mine it's just Fn + F3 to dim, then just dim to 0. I personally just use Fn + 0(zero) to set it to solid red.
 
Last edited:
ToroidalBoat said:
So does turning logging off help? 🤔

(also lol)
Click to expand...
@prollyanotherlurker 's idea of switching it to RAM only by setting storage=volatile is probably saner, just in case to want to look at it at some point later. But if the only sign of something going wrong is that systemd is vomiting out gibberish then why not?
 
Last edited:
ToroidalBoat said:
So does turning logging off help? 🤔

(also lol)
Click to expand...
Vesperus said:
@prollyanotherlurker 's idea of switching it to RAM only by setting storage=volatile is probably saner, just in case to want to look at it at some point later. But if the only sign of something going wrong is that systemd is vomiting out gibberish then why not?
Click to expand...
Turning it off solves the symptom not the root cause. 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.

RuntimeDirectory + LoadCredential memory leak on crash loop​

Click to expand...
 
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...
 
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
 
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:
You must log in or register to reply here.
Back
Top Bottom