blobjim [he/him]

  • 0 Posts
  • 23 Comments
Joined 5 years ago
Cake day: July 29th, 2020
  • blobjim [he/him]@hexbear.nettoLinux@lemmy.ml•SssEnglish
    5·
    13 days ago

    DRI_PRIME is an environment variable. DRI_PRIME=1 gimp is a bash syntax for setting an environment variable for a specific command execution, Whisker probably doesn’t use shell commands, it’s expecting an executable. So it’s trying to look up a file named DRI_PRIME=1 in your PATH.

    You’re going to need to figure out if whisker has a way to set env vars for a command (I don’t use it so not sure what it shows when you click the “Help” button). If not, you’ll need to create an executable script file which executes your command with the environment variable set like you’re attempting to do (DRI_PRIME=1 gimp), and then point whisker at your script.

  • blobjim [he/him]@hexbear.nettoLinux@lemmy.ml•What are the best reasons people have given you for not wanting to try Linux?English
    71·
    21 days ago

    I did an update or something and it corrupted the bootloading for Fedora Silverblue. Had to just reinstall everything. Also was a time when the update url or something was broken and I couldn’t update. That remains the biggest issue. But it might not be an issue for a professionally maintained distro like Ubuntu that has a company backing it. I feel like it’s safe to recommend Ubuntu but not any other distros.

    And it’s definitely true that the average user has more control on Windows. You can download installers and random zip files with executables and they’ll just work. Linux has such a messed up model for executables and libraries that they usually have to be recompiled for every Linux distro unless you use flatpak.

    But I think it’s mostly the learning curve of getting used to how linux desktops work and their idiosyncrasies that makes it hard for people. And tons of bad advice online telling you to run commands.

    Linux actually has lots of GUI apps that can help fix issues and do things in Linux but people keep offering outdated advice about using command line tools and editing brittle config files.

    And some things are distro-specific.

  • blobjim [he/him]@hexbear.nettoLinux@lemmy.ml•Linux Tablet?English
    3·
    3 months ago

    Searching for “tablet PC” or “Windows tablet” instead of just “tablet” will probably help in your search. Most computers with x86_64 CPUs (Intel or AMD) should be able to run Linux distros fine.

    But tablets don’t seem to be a common form factor for PCs. It seems like the term has really been narrowed down to mean one that runs Android or iOS. Very frustrating.

    If you can’t find anything that doesn’t have an ARM SoC, you can try postmarketOS, but it will require more work and risk than a “PC” that is a tablet. https://wiki.postmarketos.org/wiki/Devices

  • blobjim [he/him]@hexbear.nettoLinux@lemmy.ml•Can't update to Fedora Silverblue 42English
    1·
    8 months ago

    Do you have “dnf” installed specifically? What layered packages do you have? I ran rpm -qa on my system and didn’t find any packages containing “dnf”

    Also not sure if it’s useful but here’s my ostree remote list --show-urls output:

    fedora          https://ostree.fedoraproject.org/
fedora-compose  https://kojipkgs.fedoraproject.org/compose/ostree/repo/

    I also always have the same issue trying to use the UI. I had to use rpm-ostree rebase for the upgrade to 41 and 42, but it worked for me with no issues.

  • blobjim [he/him]@hexbear.nettoLinux@lemmy.ml•What are the major components of any Linux distribution?English
    2·
    2 years ago

    I don’t know how helpful it is to split stuff out like that. Especially grouping so many things under “default applications and daemons”, which is most of what a desktop distro is. Also depends largely on a PC vs server setup.

    should list an init system as its own bullet, which others have mentioned.

    “one or more shells” doesn’t mean that much. Yes, every distro includes one but the only difference between a terminal and any other application is that a terminal needs to be able to escalate to root privileges. You can think of it as just another default (but special) application. A lot of stuff that people think about when they think of Linux distros is just various clever mechanisms for supporting the terminal shell. Like the PATH environment variable. If you are using actual desktop applications other than a terminal, there isn’t any interaction with the terminal shell application.

    There’s also fwupd, for updating firmware (your hardware is gonna be running out of date/buggy/insecure code if you don’t have this).

    The dbus daemon falls under the “daemons” bullet but it’s pretty important, like wayland/x11 it’s another IPC mechanism you need for programs to work correctly.

    There’s also the sound system. PipeWire is the modern one that implements the interfaces of various other sound systems so existing applications work with it. https://pipewire.org/ (PipeWire also has its own IPC protocol like dbus/wayland/x11).

    flatpak, snap, distrobox, toolbox, docker, podman, etc. for running sandboxed PC/server applications. I assume there are some programs that are flatpak-only these days.

    gsettings/dconf for Windows-registry like config that many programs use.

    There’s also plugging in an implementation of the glibc Name Service Switch, which allows libc to use a mechanism other than /etc/passwd and related files for user accounts, internet service names, DNS resolution, etc. . systemd can provide NSS implementations using its own user account mechanism.