The Linux Thread - The Autist's OS of Choice

  • Twórca wątku Twórca wątku tehpope
  • Data rozpoczęcia Data rozpoczęcia
  • 🇵🇦 Nuestro primer dominio localizado está en español en kiwifarms.pa. Our first localized domain is on Spanish on kiwifarms.pa.
  • 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
Wyróżnienie
You people and your displays with more than 256 colors. Luxury.
Debian_TWM_Maroon.png
 
Betonhaus powiedział(a):
I might be wrong, but isn’t any app with the org.freedesktop.*.* nomenclature a flatpak?
Kliknij, aby rozwinąć...
Not exclusively.

I have also since learned a little more about this issue. I am fairly certain now that the issue is due to systemd changing their defaults. If you look at how open_temporary_icon_file() works upstream it utilizes g_get_tmp_dir(), which the glib docs mentions uses TMPDIR and falls back to /tmp if it isnt set. So unless AccountsService sets its own TMPDIR (it doesnt), then this naturally lands in your shared /tmp which doesn't work anymore for reasons stated previously.

But there's no need to rewrite the entire thing to set a custom directory for this, after skimming the source I found that you can actually fix this by changing a single line of code; that being g_get_tmp_dir() with get_icondir() This is an internal helper thats already defined in accountsservice's util.c that retrieves the static icon directory variable. This base path is /var/lib/AccountsService/icons, which is a fixed directory exposed to accountsservices. So basically a patch can have it stage icons right there instead.

I wrote one to test this and can confirm it fixes the problem without the need for an override exposing your system's /tmp

Dread First powiedział(a):
Yall niggas need to put more respect on Openbox's name. I reject your tiling modernity in favour of stacking tradition.
Kliknij, aby rozwinąć...
Ran Openbox on Debian for a while with tint2 taskbar, jgmenu startmenu and PCmanFM for desktop icons. It was the most stable system I have ever used. Shoutouts to IceWM too:

hzx8uzbqr9ue1.png
 
Ostatnio edytowane:
Sneed Chuckson powiedział(a):
Why do people like tiling window managers? I don't really get it. I usually don't want to see applications that I'm not using, so why have them take up screen real estate? There are relatively few scenarios where I'd want a screen split between several applications.
Kliknij, aby rozwinąć...
Use one only on my work computer. ultrawide, I simply want three quadrants.
 
Sneed Chuckson powiedział(a):
Why do people like tiling window managers? I don't really get it. I usually don't want to see applications that I'm not using, so why have them take up screen real estate? There are relatively few scenarios where I'd want a screen split between several applications.
Kliknij, aby rozwinąć...
It's really nice on ultrawide monitors, it can be a bit of an annoyance whenever you want to see a picture or something and you quickly open it only for it to screw up your entire workspace. I don't prefer one over the other, they're just different.
 
@Ferryman so i see in the exwm tutorial they want me to use their systemcrafters config
im kind of skipping around i got through some of the emacs from scratch and im moving onto exwm
it says to install fonts-cantarell and fira-code
i see fira-code in the guix repo and gnome presumably comes with cantarell but i want to have that in my config.scm separate from gnome so when i eventually uninstall it ill still have the font
i see the a cantarell font here but im not sure if its the same font
 
acid_ra1n powiedział(a):
@Ferryman so i see in the exwm tutorial they want me to use their systemcrafters config
im kind of skipping around i got through some of the emacs from scratch and im moving onto exwm
it says to install fonts-cantarell and fira-code
i see fira-code in the guix repo and gnome presumably comes with cantarell but i want to have that in my config.scm separate from gnome so when i eventually uninstall it ill still have the font
i see the a cantarell font here but im not sure if its the same font
Kliknij, aby rozwinąć...
Ye you can just install them either through config.scm or home.scm and instead of installing an entirely new package it will just use the one already on your system thanks to GNOME, so when you eventually uninstall the GNOME suite your font doesn't get garbage collected. I don't use EXWM myself but the guides and streams from SystemCrafters are super legit.
 
Ferryman powiedział(a):
Ye you can just install them either through config.scm or home.scm and instead of installing an entirely new package it will just use the one already on your system thanks to GNOME, so when you eventually uninstall the GNOME suite your font doesn't get garbage collected. I don't use EXWM myself but the guides and streams from SystemCrafters are super legit.
Kliknij, aby rozwinąć...
speaking of i found their config is a bit outdated. package dired-single was removed from melpa so you have to git clone it into emacs.d/lisp and add this to your init.el

(add-to-list 'load-path "~/.emacs.d/lisp/")

(require 'dired-single)

(autoload 'dired "dired" nil t)
(autoload 'dired-jump "dired" nil t)


i doubt anyone will read this on a mongolian basketweaving forum but there it is for future generations
 
Whoever it is that pushed a regressed fontmanager for Arch should go take a long leap off a bridge, KDE's now throwing fits and refusing to launch random programs over font setting strings having too many 0s meaning all my system fonts are currently stuck at semibold and I had to run font caching commands I last had to deal with three or four years ago or otherwise Dolphin for some stupid reason would straight up crash while also having a fit with ffmpeg thumbnails.
 
Enig powiedział(a):
Whoever it is that pushed a regressed fontmanager for Arch should go take a long leap off a bridge, KDE's now throwing fits and refusing to launch random programs over font setting strings having too many 0s meaning all my system fonts are currently stuck at semibold and I had to run font caching commands I last had to deal with three or four years ago or otherwise Dolphin for some stupid reason would straight up crash while also having a fit with ffmpeg thumbnails.
Kliknij, aby rozwinąć...
Yes, but just think about all the advantages from running a rolling-release distro that you would have missed out on by using software that has undergone a minimum of quality control. Why, Dolphin 26.04 fixed '514209 preventted flickrering when holding F5 key, by Ritchie Frodomar,' Don't we all just hold down the F5 key constantly? It's so frustrating when you hold the key to refresh things and the screen refreshes. Very important to avoid that. Why, it only made it into Debian testing a couple weeks after release, imagine waiting that long to be able to hold down the F5 key like a deranged spastic and not have your screen update each time the file manager reloaded files in a directory.
 
This seems like something from 10+ years ago mixed with the modern Linux zeitgeist.

wobble3.gif
 
Ostatnio edytowane:
Sperg_rancher powiedział(a):
Wyświetl załącznik 9206788
https://youtube.com/watch?v=2YibAiSQxwA
Kliknij, aby rozwinąć...
It's amusing how KDE became the devil, when i got into Linux 6 years ago it was universally loved and recommended.

I never got the appeal.
Sneed Chuckson powiedział(a):
Why do people like tiling window managers? I don't really get it. I usually don't want to see applications that I'm not using, so why have them take up screen real estate? There are relatively few scenarios where I'd want a screen split between several applications.
Kliknij, aby rozwinąć...
Let's you not use the mouse. Also you're supposed to use multiple virtual desktops, rather than minimizing. Basically GNOME 40 for men.

The song itself slaps.
 
Dead Lion powiedział(a):
It's amusing how KDE became the devil, when i got into Linux 6 years ago it was universally loved and recommended.
Kliknij, aby rozwinąć...
It's way more than that. It was good then bad over and over.

I remember it was all *box style WMs and kde was a huge honking slow DE. Gnome was the lighter DE if you were such a pleb to use a DE back then.

Round and round we go.
 
Dead Lion powiedział(a):
It's amusing how KDE became the devil, when i got into Linux 6 years ago it was universally loved and recommended.
Kliknij, aby rozwinąć...
I've used KDE since KDE 3 (KDE 2 if you count the SuSE 7.3 disk I took from work that was already way outdated when I installed it). They have a habit of getting their DE perfect by the x.3 release and everything goes well for a few years, then releasing a major x.0 release that feels like a beta. They track Qt so they don't have a choice when going from 5.27 to 6.0, but I really think a lot of the issues are on them. The move from 3 to 4 was brutal, 4.0 felt like an alpha release, more recent ones have been better. It's also been one of the more resource-heavy DEs. This was of vital importance back in 2005 and may be important again as RAM gets expensive, and I don't think there's an excuse to not be conscious of that kind of thing even when everything is cheap.
 
Magicicada_septendecula powiedział(a):
They track Qt so they don't have a choice when going from 5.27 to 6.0, but I really think a lot of the issues are on them.
Kliknij, aby rozwinąć...
I don't think it's all on them, though. Some of it is also due to Qt. A good example of this is how you literally have to patch the entirety of Qt6 itself to get Qt6 based applications to display animations at higher refresh rates than 60. No, I am not joking. If you ever noticed Dolphin or System Settings scrolling choppily on your high refresh rate monitors, this is literally why:

Qt is old. It was created when no one could ever imagine surpassing that framerate, hence the animations are implemented in a way that is tied to a single unified timer that ticks every 16 ms, which is nothing but slightly above 60 times a second. This timer is called the default timer interval, which is nothing but how often the animation updates are triggered globally.

And guess what? That timer is hardcoded at compilation time. There's no way to change it at runtime. Not even Kwin developers have figured out how to change it without doing hacky stuff like these patched versions of kwin and qt6-base do.

According to the very same KWin developers in said thread, including me, there's a theoretical architectural redesign needed for animations to actually work perfectly synchronized by getting rid of the default timer interval - or at least make it not hardcoded - but that's out of our hands and only Qt can make these changes themselves because the animations API code is private and a change like this is definitely not trivial to do.
Kliknij, aby rozwinąć...
(src)

I noticed this too and was going to wire up my own patch for it, but before I could I googled to see if anyone already had worked on it and found that someone already did all the work for a change. Here is the OP with the post I quoted above that has more info and the patch is available here. I don't think it is available on any other distro than Arch atm, but its not a massive patch as I am sure you can see even if you are not a programmer. All it does is change a single number from 16 to 4.

Would be nice if they made an environmental variable for this so that you literally didn't have to recompile the entire base of Qt6 just to change one single number, but alas. I thought of researching to see if I could build something that exposed such an environmental variable instead, as I think that would have a higher chance of getting merged. But for now you should maintain your own patch or use this third party package which if updated out of sync with the rest of the system is sure to lead to unbootable systems (see top comment on the AUR package for an example :story: )
 
Wyróżnienie
Musisz się zalogować lub zarejestrować, aby odpowiedzieć.
Wstecz
Top Na dole