• 2 Posts
  • 29 Comments
Joined 3 months ago
cake
Cake day: April 2nd, 2025

help-circle

  • I would be interested in a project like this if it were a distributed network.

    It’s important to ensure that accumulated community knowledge will survive, and conversations can continue, when an instance dies or becomes intolerable. (Reddit and Stack Exchange have recently brought this into sharp focus.) It’s so important that I no longer contribute to sites like this unless they provide those assurances.

    So I hope this one develops into something that meets that need.




  • One thing that would be helpful about not using drop-down boxes for static options: Fewer clicks required to set up a search. Each of the drop-down boxes in use now requires the user to:

    • Read the text on the drop-down box to decide whether it’s relevant
    • Move the mouse to the drop-down box
    • Click to open it
    • Read the options within
    • Move the mouse to the best fitting option
    • Click to choose the option

    The first drop-down box (search type) contains only five options, which could be replaced by buttons like the existing Subscribed/Local/All buttons. It would make discovering the available options easier because they would no longer be hidden behind a drop-down, and it would reduce the number of actions required of the user.

    The second drop-down box (sort type / time frame) might be a good candidate for this change, too.

    As for whether tabs would be a better choice than the button-style approach currently used by Subscribed/Local/All: I’m not sure right now, as I haven’t had much time to consider it. But I think things would get messy and possibly confusing if more than one of these input elements were converted to tabs, because it would mean nesting tabs within tabs. On the other hand, using a row of buttons for each category would allow them to coexist neatly, fit the existing visual style, and avoid adding the complexity of another widget type for users to navigate.


  • So I’ve been using rootless podman-compose

    when a new folder is created or an existing folder’s contents are modified, it seems to be setting the files and their folder’s owner to “52587”

    Rootless Docker and Podman run their applications within a user namespace. This means most of the user IDs within the container are mapped to a different uid range on the host, often called a subuid. It’s part of how “rootless” mode can allow an unprivileged user to run software that expects to have privileged IDs.

    https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration

    which does not exist.

    Are you sure it doesn’t exist? Have you looked at the ranges defined in /etc/subuid on the host?

    My first thought is that the uid numbers you see might be some of your host user’s subuids. If so, they will appear as different uids (perhaps with usernames) within the container. Try launching a shell within the container and examining the same files, to see what their owners appear as there.

    If this is what’s happening, it’s normal. As long as the software trying to access the files and the software creating the files are both in the same container, it should be fine. If it doesn’t work, there’s probably another problem in play.

    By the way, Podman almost certainly has a way to map certain container uids to host uids of your choice, which can be convenient when you want to share files between containers or between a container and the host.






  • the amdgpu-pro drivers are only available on LTS releases and on a few selected distros

    Are you sure? I would expect AMD to have their own download & install instructions that could be used on any distro. That would be more work for you than just installing a package directly from your distro, of course.

    Curiously, I just found a comment from last year claiming that amf-amdgpu-pro now works with Mesa’s RADV. So maybe this approach could work without AMD’s proprietary driver?

    Mostly BluRay rips, so movies and TV-Shows

    By rips, do you mean your source media is already in a container, like a .mkv or .mp4 file? Or are you encoding directly from optical discs? If it’s the latter, then using a tool other than HandBrake for the encode might also require finding a disc ripping tool. (Not all encoding tools can decrypt and demux discs.)

    I actually was not. Is it any good? But Handbrake does not support that either, does it?

    I haven’t used Vulkan Video. It’s just an API, so I would expect the video quality to depend on your hardware’s encoder, just as it would with VAAPI or any other API.

    I don’t think Handbrake supports it yet, so until they do, I think you would have to use some other encoding tool.

    for anything involving multiple audio and subtitle streams and stream selection in general it is not an option for me…

    You haven’t said why, but if it’s just that managing lots of streams using command line tools is more hassle than you want to deal with, you might take a look at MKVToolNix. It’s pretty good at muxing, even if the source media is not a .mkv file.







  • But here’s where Debian gets tripped up by the ecosystem: the moment you hit a login prompt, you enter a session with user-locked audio. This isn’t Debian’s fault. It’s the fault of PulseAudio, PipeWire, and the entire philosophy of session-bound audio daemons that don’t care what the kernel is doing.

    It’s worth noting that PipeWire is being developed with support for a system-wide, multi-user instance, which should solve the problem that I think the author is describing above. When I last checked a couple years ago, it was enabled with this build option: -Dsystemd-system-service=enabled

    The name of that flag seems to imply that systemd is required, which would be disappointing for folks who use other init systems. I haven’t tried it, so I don’t know if it’s a true requirement or just a name that was convenient at the time it was created.



  • If I wanted to do this, I think I would start by getting to know the IT staff. This would:

    • Help me to understand the challenges they face in getting their work done: what’s problematic for them, what’s helpful, what skills they already have, etc. This would eventually guide me in how to approach suggesting changes with minimal friction.
    • Make me a familiar person to them, and allow opportunities to build trust in my skills, knowledge, and judgment. If this is established before I ever suggest a change, it could avoid some of the doubt and resistance that would surely come if a stranger walked up and pushed for changes. I want to be a friend, not a foe.
    • Potentially identify an ally within IT: Someone who might already want to make the switch (perhaps because they’re tired of Microsoft’s BS) or at least agree that it would make sense. An ally on the inside would not only make it easier to get others to seriously consider the change, but also potentially help gather information about how MS Office is currently being used so that I could prepare equivalent LibreOffice workflows for users who need them.

    I suggest taking your time, and saving Linux for later so that it doesn’t create more friction against moving to LibreOffice.


  • A package is “kept back” when it faces requirements that can’t be resolved while adhering to the given options.

    For example, this can happen when a dependency at a certain version is required, but that version is available only from a source (e.g. backports) whose priority is too low to be used by default*. You can resolve this particular situation by naming not only the main package, but also the dependency in question, on your apt install -t bookworm-backports command line. (The -t bookworm-backports option overrides the default source priorities.)

    Looking at the dependencies of pipewire-audio in backports, I see that one of them (wireplumber) has a version requirement that can be satisfied from backports, so this might work for you:

    sudo apt install -t bookworm-backports pipewire wireplumber
    

    BTW, I’m sure that pipewire from backports works on bookworm, because I use it myself. You don’t have to wait for Trixie.

    *You can get details about how the priority system works via man apt_preferences.