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
Anyone here compared XLibre to regular X yet? Hard to find any reports on it since most of the news is full of whining about the dev not marching in lockstep and Phoronix is full of people dicklicking RHE as usual.
 
Enig said:
Anyone here compared XLibre to regular X yet? Hard to find any reports on it since most of the news is full of whining about the dev not marching in lockstep and Phoronix is full of people dicklicking RHE as usual.
Click to expand...
There's an ebuild for Gentoo and I intend to get to it at some point. Will report back after. Old man just got out of the hospital this weekend so shit's been hella busy.
 
Enig said:
Anyone here compared XLibre to regular X yet? Hard to find any reports on it since most of the news is full of whining about the dev not marching in lockstep and Phoronix is full of people dicklicking RHE as usual.
Click to expand...
Gentoo has a thread and a port for it right now in testing. Of course it's developed into the "muh right hwite anti vaxx retardation". How far the mighty have fallen.
We are working on making an overlay for Xlibre.
Right now, I advise against using xlibre.
All the commits I made on the Xlibre X11 server were fixes for various regressions, caused mostly by various symbols being unexported.
Unless you want to work on xlibre, I recommend saying on Xorg. Xlibre is far too unstable and has far to many regressions for me to recommend to average users
Click to expand...
One of the Romanian users is working on Xlibre too. He did also update tinyx and GTK2. I checked his github profile, he's a mathmatics major so it shouldn't be too bad right?
napalm.webp
:ow:(:_(
STEM to troon pipeline at work here folks
 
Darkholme's Dungeon said:
Gentoo has a thread and a port for it right now in testing. Of course it's developed into the "muh right hwite anti vaxx retardation". How far the mighty have fallen.

One of the Romanian users is working on Xlibre too. He did also update tinyx and GTK2. I checked his github profile, he's a mathmatics major so it shouldn't be too bad right?
View attachment 7545634
:ow:(:_(
STEM to troon pipeline at work here folks
Click to expand...
Lol @ the guy in the thread saying he should have used Codeberg instead, guess he didn't get the memo about Codeberg standing up against right wingers because someone said nigger balls.
 
volatile puar said:
Lol @ the guy in the thread saying he should have used Codeberg instead, guess he didn't get the memo about Codeberg standing up against right wingers because someone said nigger balls.
Click to expand...
Honestly, at this stage host your own Fossil/SVN instance. Then get hacked by loony troons, and when you fight back the FBI arrests you for daring to stop their DDOSing by crashing the botnet controller.
 
ToroidalBoat said:
Thanks. So looks like the biggest offender is some kind of logging, with "systemd-jornald" and "rsyslogd"...

There's also "jbd2" doing some constant writing, though not as much. So what's this BS and how do I stop it?

View attachment 7545259
(Pic is thumbnail. Censored SSD name after "jbd2" and other personal info further down.)
Click to expand...
Things in [square brackets] are kernel threads doing work for the kernel. In this case jbd2 takes filesystem data from the filesystem journal onto the proper place on the disk and handles safe recovery in case of power off. Most kernel threads don't do anything on their own, lvm will take the writes to /dev/mapper and similar and send them to the proper /dev/sd* or /dev/nvm*, same for md and the [md#_raid#] threads.
 
DavidS877 said:
Things in [square brackets] are kernel threads doing work for the kernel. In this case jbd2 takes filesystem data from the filesystem journal onto the proper place on the disk and handles safe recovery in case of power off. Most kernel threads don't do anything on their own, lvm will take the writes to /dev/mapper and similar and send them to the proper /dev/sd* or /dev/nvm*, same for md and the [md#_raid#] threads.
Click to expand...
@ToroidalBoat You need to see what's causing the massive log writes. Systemd is doing something stupid per usual again would be my guess. Instead of supressing the error it's writing them all with all the errors in queue. If you can't tell from the log, pass
Code: 
tail /var/log/messages
(or similar) and see what retardation is going on in real time.


Yes. rsyslog + systemd = resource exaustion because bad cert. Lmao.
Here's another example of systemd retardation:
journald duplicate message ID bug causes rsyslog to peg CPU at 100% and spam /var/log/messages until hard disk is full (and breaks journalctl)
Click to expand...
"better solution to sysvinit" :story:
 
Darkholme's Dungeon said:
Gentoo has a thread and a port for it right now in testing. Of course it's developed into the "muh right hwite anti vaxx retardation". How far the mighty have fallen.

One of the Romanian users is working on Xlibre too. He did also update tinyx and GTK2. I checked his github profile, he's a mathmatics major so it shouldn't be too bad right?
View attachment 7545634
:ow:(:_(
STEM to troon pipeline at work here folks
Click to expand...
There are weebs in Romania. I met some of them and they were alright, not cringe. I think it is far from being as obnoxious as western weebs, since there is much more shaming on weird behaviour (and I was kind of a target because I liked rock music in middle school). And if I am not mistaken, drawn child pornography is illegal, but I don't know if it is enforced or not.
 
Last edited:
ToroidalBoat said:
Thanks. So looks like the biggest offender is some kind of logging, with "systemd-jornald" and "rsyslogd"...

There's also "jbd2" doing some constant writing, though not as much. So what's this BS and how do I stop it?

View attachment 7545259
(Pic is thumbnail. Censored SSD name after "jbd2" and other personal info further down.)
Click to expand...
if its systemd you can just change the setting in /etc/systed/journald.conf

put
storeage=volatile

that will keep the logs in memory

also. obviously. actually take a look in the log and see what it's logging in case their is some other issue you need to take care of,
 
Enig said:
Anyone here compared XLibre to regular X yet? Hard to find any reports on it since most of the news is full of whining about the dev not marching in lockstep and Phoronix is full of people dicklicking RHE as usual.
Click to expand...
I use KDE on my work laptop, and logged in to find that I had updated prior to leaving work and had unknowingly updated to a version of KDE that no longer supports X11. I figured it's as good a time as any to figure out the jump to Xlibre. Turned out all I had to do was install plasma-x11-session and kwin-x11, but now I'm learning to appreciate XFCE's cute mouse.

What gave it away I was in Wayland was none of my monitors were behaving. Every time my screen locked I would lose monitor positioning, scaling would jump to 150% for some reason. Getting Xlibre off the AUR was easy enough using the commands pinned on the AUR (have to use a bootstrap package first to avoid dependency loops), and after I figured out the missing packages for KDE it was exactly how I left it on Friday.

For reference I've got a Lenovo ThinkPad E16 with a Ryzen 7730U.

How would I even notice a difference? Is it just performance? Is an update to my Xorg server supposed to be noticeable without the desktop environment to do something like take advantage of new features?
 
DavidS877 said:
In this case jbd2 takes filesystem data from the filesystem journal onto the proper place on the disk and handles safe recovery in case of power off.
Click to expand...
So if I disable "system-journald" and "rsyslogd", that shouldn't cause any major issues with the OS working?
 
I gave a second laptop to a relative and installed Cosmic Desktop. I had to use Arch because Alpine was doing some weird stuff with the wifii card, and I didn’t want to waste any more time troubleshooting it. I tested it out, and overall, it worked pretty well. One thing that really annoyed me, though, was that their file manager doesn’t support “Extract to” for 7z files. I had to use PCManFM instead. For someone like me, that’s not a big deal since I don’t typically use graphical file managers. But I can see how little things like that might frustrate normies who just want things to work. A lot of small stuff like that can prevent adoption.
 
ToroidalBoat said:
So if I disable "system-journald" and "rsyslogd", that shouldn't cause any major issues with the OS working?
Click to expand...
Journald and jbd2 are totally different things and unrelated.

The best solution is to check the logs and see why they're being written so much and fix the underlying problems, if any.
You can run "journalctl -b" to see all messages since last boot. You can check for large files in /var/log and /var/log/journal, if you find a large *.journal file you can use "journalctl --file FILENAME" to see what's in it and if something is going horribly wrong.

Amusingly, I have some large files in journal due to some containers I run which process PDFs and the log stores all the PDF data. This is unlikely to be your problem.
 
ghastlyretard said:
How would I even notice a difference? Is it just performance? Is an update to my Xorg server supposed to be noticeable without the desktop environment to do something like take advantage of new features?
Click to expand...
You will notice that you are running XLibre if you are protected from deliberate malicious regressions plotted by Red Hat (IBM) to protect Microsoft.
 
DavidS877 said:
The best solution is to check the logs and see why they're being written so much and fix the underlying problems, if any.
Click to expand...
A recurring things I'm seeing is "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)", but dunno if those are issues. For now I disabled the systemd journal thing.

BTW what's considered alarmingly huge? There's syslog.1 that's almost 10 MB, but I've been using this system for years.
 
Last edited:
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?
 
You must log in or register to reply here.
Back
Top Bottom