Jure Repinc

Digital and software freedom/rights advocate from Slovenia, Europe. Also a member of the Pirate party. You can find me on Mastodon: @JRepin@mstdn.io

  • 158 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle






  • I am also gaming a lot and used nvidia in the past and by the description you give I would say openSUSE Tumbleweed is the one. It is rolling release, but they also have extensive QA tests before letting packages get released as updates so it is very stable for a rolling release. And another thing that openSUSE is awesome for is that they have BTRFS snappshotting very nicely configured out of the box so before and after each update it creates a snappshot and if something goes wrong you can just select an old working snappshot from GRUB boot menu. And with Nvidia this breakage was happening well more often the I would like. I also like their Open Build Service where you can find many additional packages which might not be packaged by distro people themselves.







  • Jure Repinc@lemmy.mltoLinux@lemmy.mlWhat desktop enviroment do you use and why?
    link
    fedilink
    English
    arrow-up
    44
    arrow-down
    1
    ·
    edit-2
    6 days ago

    KDE Plasma on all my computers and also as desktop mode on Steam Deck. because it supports the latest technologies especially when it comes to graphics (HDR, VRR) also has best support for Wayland and multi-monitors. It looks great out of the box and it has a lot of features out of the box and I do not need to battle with adding some extensions that break with almost every update. KDE Plasma is also the most flexible desktop and I can set the workflow really to fit my desires and I can actually set many options and settings. And despite all these built-in features and configurability it still uses very few system resources and is very fast and smooth. Oh and the KDE community is one of the most welcoming I have met in FOSS world, and they listen to their users instead of the our way or the high way mentality I have so often encountered in GNOME for example. So yeah TLDR KDE Plasma is the one I like the most of all in the industry, even when compared to proprietary closed alternatives.







  • Jure Repinc@lemmy.mltoLinux@lemmy.mlKiosk Mode and Linux
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 days ago

    KDE Plasma desktop and apps also have a Kiosk mode/framework for deployment and lockdown built-in, that can come in handy

    Kiosk - Simple configuration management for large deployment

    The Kiosk framework provides a set of features that makes it possible to easily and powerfully restrict the capabilities of a KDE environment.

    Introduction

    The Kiosk framework provides a set of features that makes it possible to easily and powerfully restrict the capabilities of a KDE environment based on user and group credentials. In addition to an introductory overview, this article covers configuration setting lock down, action and resource restrictions, assigning profiles to users and groups and more.














  • Jure Repinc@lemmy.mlOPtoLinux@lemmy.mlLinux 6.11 released
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    Anyone else having the problem with the new kernel that graphics in games/benchmarks is quite a lot slower (about 15-20%) then with older kernel (I used 6.10.7 before I upgraded). This is with Powercolor Hellhound AMD Radeon RX 7900 GRE? Even Einstein@Home GPU tasks take about 20% longer now (28 min with previous kernel to about 34 min now).



  • From my experince AMD drivers are pretty close, I’d even say slightly better on GNU/Linux, definitely more stable and consistent. For Nvidia, yeah they are bad at supporting GNU/Linux. Improved a lot through the years but still not there. For Intel, well not exactly an option for gaming, at least not the integrated GPUs I have used so far, but still better than in Windows in a similar way as in AMD case.

    P.S. Another great thing with libre/opensource GNU/Linux drivers: When you report a bug with Mesa3D drivers the bug is quite quickly fixed, especially when you can provide them with backtrace and/or Vulkan/OpenGL API trace. Doing a bisect of source code commits amd identifying the commit that introduced a regression also help a great deal. Good luck doing the same with closed/Windows drivers: you can wait for years and no fix.