![](https://programming.dev/pictrs/image/5ea7b5e4-e2b5-49be-9d4c-3abd01c3d317.jpeg)
![](https://programming.dev/pictrs/image/028151d2-3692-416d-a8eb-9d3d4cc18b41.png)
Sure, but even in those “few cases” Testing will get them soon.
I did read at some point that Testing may receive security updates later than stable, might be in those cases in which backports come straight from unstable.
Sure, but even in those “few cases” Testing will get them soon.
I did read at some point that Testing may receive security updates later than stable, might be in those cases in which backports come straight from unstable.
I don’t recommend going for (Debian’s/Devuan’s) testing (branch) as it targets a peculiar niche that I fail to understand; e.g. it doesn’t receive the security backports like Stable does nor does it receive them as soon as Unstable/Sid does. Unstable/Sid could work, but I would definitely setup (GRUB-)Btrfs + Timeshift/Snapper to retain my sanity.
From https://backports.debian.org/ :
Backports are packages taken from the next Debian release (called “testing”), adjusted and recompiled for usage on Debian stable
So by definition, security backports in stable are present in Testing in the form of regular packages, right?
I remember having some issue like that, but I’m not sure if this was the fix.
Try unchecking “Show desktop notifications when the song changes” on Spotify’s settings (right now it’s under the Display section).
The band played 2 early albums + their latest one in sequence. Listening to whole albums in one go was great for many reasons.
May be a coincidence, but it stopped launching for me too. Worked Monday and Tuesday, yesterday I didn’t try to play, today it didn’t work.
Tried:
Makes sense, thank you for the clarification.
It is also a file browser.
And apparently also supports FTP/SFTP, quite nifty.
I’m new-ish to Linux and new to Debian, but I literally just did a (second) Debian 12 install, so I have one note about your Firefox’s documentation, specifically about “chromium’s suggestion” when uninstalling Firefox. https://makedebianfunagainandlearnhowtodoothercoolstufftoo.computer/doku.php?id=start:firefoxesr
Besides Firefox ESR, it came bundled with “Konqueror”. Don’t know if it depends on your installation’s configuration, though. I selected to install “non-free” software, if it helps. So for me it didn’t complain when I uninstalled Firefox ESR, it just set Konqueror as the default web browser
I don’t know if we’re discussing semantics. A performance score is attributed, and before the fix their scores were all 166. It doesn’t work, as you said. So the consequence is the preferred core being “random”, isn’t it?
Apparently there’s a bug in an AMD’s driver. It was supposed to assign processes based on each core’s self reported performance, but because of the bug it was random.
This “self reported performance” is based on evaluation done to the cores in the fab process, by AMD. Meaning, due to imperfections some cores are a bit better than others.
Ok, I understand what you meant, thanks.
Yeah, I wouldn’t run it in a production environment.