NoisyFlake

joined 1 year ago
[–] [email protected] 2 points 3 days ago (1 children)

No, LTSC only receives security updates, not feature updates.

[–] [email protected] 46 points 4 days ago (34 children)

I'm running Windows 10 LTSC with a custom start menu (StartIsBack). So far I have avoided all of Microsoft’s nonsense.

As long as I’m not ready to switch to Linux 100%, this is probably the best possible solution.

[–] [email protected] 9 points 1 week ago

Not in Germany, they renamed it to MS Anne.

[–] [email protected] 6 points 2 weeks ago (1 children)

Isn’t yay just a wrapper for pacman?

[–] [email protected] 6 points 3 weeks ago

I’ve never seen a video THIS relatable.

[–] [email protected] 23 points 4 weeks ago (4 children)

So what? I'm not a fan of Fortnite as well, but let people enjoy what they want.

[–] [email protected] 8 points 4 weeks ago (1 children)

Apple TV is a bit pricey, but at least it’s ad-free. Connect it to a modern TV without internet access, stream your Jellyfin (or Plex) media via Infuse and you are good to go.

[–] [email protected] 0 points 1 month ago

I suppose you're talking about a 32-bit app that wasn't updated for the newer 64-bit architecture. If yes, then there's actually a technical reason behind it, not just Apple being dicks. Because other than 32-bit apps, every app that received a 64-bit update should still work on the latest iOS.

[–] [email protected] 2 points 1 month ago

Full desktop environment with decent window tiling.

[–] [email protected] 18 points 2 months ago (2 children)

I love the long german shortcut names. ALTERNATIVER WEB-BROWSER MOZILLA! DEBIAN-ANWENDERHANDBUCH! ADMINISTRATIONS PASSWORT EINSTELLEN!

[–] [email protected] 3 points 2 months ago (3 children)

Jesus, UI design was terrible back then. I'm not talking about technical limitations, I don't need fancy transparency effects or something like that, but I'm sure that you could come up with something much better using the old UI libraries as long as you follow modern design principles.

[–] [email protected] 12 points 2 months ago

Maybe that’s why he became a dentist.

38
submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]
 

Hi everyone,

ever since I switched to Arch about two months ago, most applications segfault multiple times a day. There doesn't seem to be any pattern for the crashes, sometimes it's even happening while idling (e.g. reading a news article).

Things I've tried without any luck so far:

  • Running Firefox in safe-mode without any extensions
  • Switching from regular to LTS kernel
  • Disable Hardware Acceleration in Firefox
  • Change RAM speed and timings
  • Run Memtest successfully
  • Replace entire RAM with a new certified kit
  • Use only a single RAM slot
  • Apply Ryzen fixes (iommu=soft, limit c-states)
  • Use only a single CPU core (maxcpus=1)
  • Downgrade Nvidia driver to 535xx
  • Use Nouveau instead of the nvidia driver
  • Use Openbox instead of KDE
  • Disable zswap and THP

Here's full journalctl from a day where both Spotify and Firefox crashed at the end, a few seconds after each other:

https://pastebin.com/BH0LMnD9

Some more info about my system:

  • Ryzen 5 3600X
  • MSI B450M PRO-VDH Max
  • 32GB RAM @ 3200MHz
  • Geforce RTX 2070 SUPER (using nvidia-dkms)
  • Plasma 5.27.10 on X11

I'm pretty sure that it's not hardware related, because I've booted up a Debian 12 live image where everything ran for several hours without a crash. But it seems to be Arch related, as I also booted up a fresh EndeavourOS live image (so basically Arch), where applications also randomly segfaulted. Any idea why everything works fine on Debian but not on Arch? Debian uses the 6.1 kernel, which I already tried, so that's not it.

Let me know if you need any more information that might help solve this issue. Thanks!

Edit [solved]: It looks like disabling PBO in the UEFI/BIOS did the trick. The strange thing is, after enabling it again, it's still not crashing again. Someone suspected that the MoBo default/training settings were faulty, so I guess this was a very rare case here. That's probably why it took so long to find a solution. Thanks everyone for helping me out!

view more: next ›