• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • As much as I like the idea behind Pine64, make sure you understand what you’re doing - their devices usually need some time before they’re useful, they might underperform, etc.
    On the other hand, they’re usually priced well for what they offer, and I think the ARM model of new PineTab might look better than their usual new offerings. Make sure to find out, how polished it is before you buy.


  • sado1@kbin.socialtoLinux@lemmy.mlHyprland is a toxic community
    link
    fedilink
    arrow-up
    18
    arrow-down
    4
    ·
    1 year ago

    It’s the moderation staff’s responsibility. Sorry for nitpicking, I understand in this case it’s likely the same people.

    I just get triggered when I hear that an open source software developer should have any responsibilities at all (maybe apart from some extreme examples), and I wouldn’t like this idea to stick in anyone’s head.





  • I looked through the posts.
    Explanation of the issue: the userspace implementation of OpenGL for Xorg, called GLX,does not work, maybe it isn’t loaded. From what I see, /usr/lib/nvidia/xorg/libglx.so is no longer included in nvidia-utils package, the new name for it is probably libglxserver_nvidia.so

    Did you have any lines with (EE) in Xorg.0.log?
    Do you see if this log says, if libglxserver_nvidia.so was loaded correctly?
    Wouldn’t hurt to check, if nvidia kernel module is loaded: lsmod | grep nvidia
    Maybe reinstallation of nvidia-utils package could help, although I am pretty sure this was done already when you removed and added nVidia driver again.

    Feel free to PM me, whenever you give it another go, even if it’s half a year from now :) I’ll do my best to provide you some advice.
    (‘nv’ is an old driver for old nVidia cards, you shouldn’t look in that direction, it’s normal that it doesn’t load, if nvidia driver does)


    • KeepassXC should just work, if the browser’s key was added to your KDBX database successfully. Other than that, I am surprised.
    • Yup, the motherboard clock thingy is a consequence of Windows storing local time, vs Linux storing UTC. It’s a minor thing to fix in any of these systems, though.
    • Shortcuts thingy - never had a problem, although I did have a problem with KDE’s keyboard shortcuts to run a program, which may be related workflow and maybe both were/are broken.
    • KDE Connect is surprising, as at least for me it worked flawlessly
    • The reboot thingy must be related to Linux Mint. I saw similar thing in EndeavourOS. One nice thing that some distributions implemented, is the ability to apply updates when you poweroff - from my point of view it’s a less annoying solution than what you describe.
    • I can’t comment on the ‘cherry on top’ one without more details.
      I had a somewhat similar issue on my work laptop a short while ago, when I installed a program, which included a bugged XML settings file, then ran system update. When the updater tried to rebuild some caches (related to ie. icons, MIME etc.), some programs which use these caches simply stopped working. Reinstalling all packages with apt was the only thing that helped, to this day I do not even know all of the parts of my system that were broken.
      But this was one of these issues that happen once per 5 years, and leave you scratching your head and asking “what the hell is going on here?”. The difference from Windows is that in Linux, you can have a high understanding of system’s internal modular components (at the cost of time needed to learn it), and regular system issues can be identified after a few minutes of Googling.



  • Oh, and as for the touch UIs, not much luck if GNOME doesn’t work well enough. KDE can be made to run well with touch input, but for me it needed some work to configure it. But I liked it afterwards.

    There are Mobile Linux UIs (which might run better on tight resources) but I am afraid they might not be good for multitasking on a tablet screen.