I like the plethora of packages Debian offers. From what I recall, Debian Testing and Ubuntu are of the same caliber?
Normally I run Fedora, but I had a hiccup on my (primary) workstation. I was planning on trying Ubuntu to see if the same hiccup happened, but got side tracked (Debian Testing). Forgot about my initial trek (until today, right now, when you criticized me ).
Moved to Solus in an attempt to repair my Debian install (Solus was already on a live USB). Just went ahead and installed it.
Iāll typically rock Fedora or Solus (Arch if Iāve stayed up past my bedtime) for reasons. Speaking from my experiences, Fedora handles Gnome a lot better than Debian or Ubuntu (I get the ungodly ārunning a stop jobā very often on those, whereas I get it once upon first reboot on Fedora, and then never again).
PHP 7.x, Golang 10.x, and JDK 10 seems to run better on the later kernels, but that may just be because I use those more frequently than I do the Debian 4.9 or Ubuntu 4.(14?).
My CentOS boxes are on 4.18 now, so when I do something on Fedora itās damn near close to how Iām going to run it in production. Amazon Linux is its own thing, but CentOS is tweaked to our personality.
So, yeah, I tried Debian Testing because of the later kernel and abundance of packages (that may be an old setup, Iāve not looked at Ubuntu versus Debian packages in a while. But Debianās use to dwarf Ubuntu).
If that gets even close to answering your question o_o
For Clementineās issue with playing/buffering .wma files, I tried installing the latest developer build to see if itās been fixed.
The .rpm packages are only built for up to Fedora 26. I tried installing it anyways and it seems to depend on some older librariesā¦
So I tried building from source instead. It fails to run. Apparently it requires building sqlite with some special flags for it to workā¦ not really interested in doing that. What a pain.
Generally youāre going to get mfg/software support on ubuntu first. Updating the kernel is easy. I like to keep the old kernels installed so I can easily revert with a reboot and select the old kernel in grub menu. For instance sometimes new kernels wont play nice with nvidia until they update their driverā¦
Yeah, Iām a huge fan, you can see my gushing (and not well received LOL) review below
Iāll consider that the next time Iām looking for a .deb/apt distro to install on the battlestation. I believe Iām running on 2014(ish) knowledge (whenever Backbox started gaining popularity).
I need to evaluate AMD drivers versus Nvidia long term (on Linux). Right now, Iāve been mostly happy with how it works on Linux.
Sadly, TearFree and TripleBuffer (canāt recall the exact command) never worked for me, AMD or Nvidia.
Well, lies, I think it worked on Antergos. Other than that I saw no effect.
Iāll have to buy a mid tower and see how it works as a standalone card these days. I used it for passthrough a while back, but other than that itās not seen any action
@anon79053375 Thatās too bad. It worked like a champ for my RX 580 on Fedora 28. The tearing was epilepsy inducing until I edited my xorg.conf (well actually I created 20-amdgpu.conf in /etc/X11/xorg.conf.d.)
[WARNING: anecdotal evidence unless noted otherwise, take with a grain of salt]
Just to contribute a bit, Iām not too fond of Debian Testing.
Initially, the FAQ says that when a package on Testing breaks, it might stay a long time broken (see 3.1.5), while Unstable gets fixed swiftly. I then ended up suffering from the issue first-hand, when a package I needed to install was not available due to unmet dependencies, and some other package needed a more recent kernel version. I could not wait for those issues to be fixed because I needed those packages for a uni project, so I upgraded to Sid and, strangely (and happily) enough, Iāve been having way less issues now. Actually, the only time an upgrade ābrokeā my system was when upgrading from Buster to Sid: for some reason my graphics driver disappeared and had to install it through apt (my laptop uses AMD so that didnāt give me too much trouble).
As for kernel versions, Sid runs 4.17 and Ubuntu 18.04.1 is on 4.15 , so, if youāre feeling adventurous, Sid might be a good fit for you (but I donāt have much experience with Nvidia, so that part might vary wildly.)
So, weird quirk. On reboot, I get insane lag on 144hz. I flick the mouse and there is a 3 to 5 second delay, then the mouse jumps. Typing is NOT impacted.
If I start Nvidia-Settings, the problem goes away. When I close Nvidia-Settings, the problem stays away. I lock my computer over night, put it to sleep, etc. The problem stays gone until the next reboot.
Iāve looked at Nvidia settings and it doesnāt look like it starts a daemon or anything.
For now, I have a startup script that runs Nvidia settings, stores the pid in a variable, and kills it immediately. Havenāt tested it yet, because now I donāt want to reboot
Funny you mention that, we just blasted on Twitter that weāre now a patron of Solus Project. I was going to do a bit about our inspiration and what not on Sundayās intro. Might discuss my head scratching issues too
Sure, current weird issue system (this was Fedora Netinst, Debian Buster, and currently Solus)
Gigabyte GA-Z97X-SLI
Intel i7 4790k
16GB Crucial Ballistix 1600
EVGA Nvidia GTX 1080
Corsair K95
Corsair M65
Solus 3.9999
Budgie (system calls it Gnome 3.28.2)
Asus ROG 27" 1440p @ 144hz (the monitor with issues)
NOTE that my other system is near identical to do this one, with a newer Intel processor and 1080Ti, has run 95%-99% without issue on Fedora, it has a 1440p monitor at 60Hz.
I donāt know if G-Sync/144hz is causing my issues here or not, but I figure itās worth mentioning.
To be honest Iāve not checked in a long timeā¦ I can look into that tonight. Ugh. Hopefully itās not one of those firmware updates that requires Windows
Shows how long Iāve been out of āreal I.T.ā. Jesus. No, I didnāt think of that
Add that to the list of things I need to do tonight.
Is it possible to update a docker container when a docker image is updated?
I have a container for phoronix test suiteās (pts) docker image with a bunch of additional tests installed. There is a new pts version now, and I did a docker pull, but of course my existing container is still based on the old image. Can I avoid redownloading/reinstalling all the tests?