What software have you found particularly frustrating or difficult to configure on Linux?
Jellyseer in docker. It won’t accept my jellyfin login. It just spins and spins. But I plan to use it locally. And everyone says you have to sign in initially not local? I don’t know. I’m annoyed with it and gave up for now.
I think this means it can’t actually see your jellyfin instance, you need to use your computer’s local network ip instead of localhost if the two containers aren’t in the same pod via a docket compose file. I’ve had this issue before.
Nah. It’s on the same docker compose file through portainer. And I’ve been using the local ip. I never use local host for some reason lol
You probably need to use localhost lol or the name of container set in the docker compose file. Both might work, I forget
I’ll try name of container. I have tried localhost in my troubleshooting. It loads the login screen fine. But just spins for 3 minutes then errors out at some point just like the IP lol I’ll be working on it when I get home later after this flight and I’ll let you know if I solve my struggles lol
Wishing you luck, it’s so worth it once it works
I still don’t fully understand how to gracefully have multiple desktop environments and switch between them. When I want to try something new to me like lxqt, I usually spin up a VM.
Just add a new user
Normally, the process is:
- install the packages for the desktop environment
- log out (not just locking the screen)
- find a dropdown or cogwheel where you can select the other desktop environment
- log in
Having said that, I don’t know what you mean with “graceful”. Desktop environments may involve lots of packages, which may create configuration files in your home directory or get auto-started in your other DEs, so it can be messy.
Something minimal, like LXQt or the various window managers, isn’t going to cause much of a mess, though.I guess, creating a second user with a separate home-directory, like the other person suggested, would isolate that potential mess…
Recently? Email notifications for my crontab jobs. I learned that snapraid sync had been failing for 200 DAYS. I was thinking it’d be easy for some reason. It hasn’t been.
Overall though, Nextcloud was a nightmare and I just gave up.
In recent years I’ve found NextCloud to reasonable. A little delicate initially, but once you have it working, the upgrades are very easy.
I also realized that I just didn’t need all of the functionality and such. In reality I just need a file sharing system akin to Google drive.
Xserver… Somehow trying to find the magic string of letters and numbers that made your screen work.
Modeline ftw.
Shudder. I had this weird brand laptop… Sotec IIRC and there just wasn’t a modline that ever got it all right.
Just recently XDG Portals to get video sharing working. It just kept using the GTK fallbacks instead of KDE as I configured it, but it used the correct ones when starting from the terminal.
Eventually I figured out I had set an env override for
XDG_CURRENT_DESKTOP="sway"in my user systemd environment, because that’s what I used previously.Multiple versions, paths, and installs of Python. Using pip makes it worse.
I have limited Python experience, but I always thought that’s what virtualenvs and requirements.txt files are for? When I used those, I found it easy enough to use.
pyenv and pyenv-virtualenv together solves this for me. Virtualenv with specific python versions that work together well with other tools like pip or poetry.
It boils down to something like
$ pyenv install 3.12.7 $ pyenv virtualenv 3.12.7 myenv $ pyenv activate myenvand at that point you can do regular python stuff like pip installing etc.
If you’re having to type out version numbers in your commands, something is broken.
I ended up having to roll my own shell script wrapper to bring some sanity to Python.
You misunderstand, the first two commands are just one time setup to install a specific python version and then to create an env using that version. After that all you need is `pyenv activate myenv´ to drop you into that env, which will use the correct python version and make sure everything is isolated from other environments you might have.
You can also just create an env with the system python version, but the question was specifically about managing multiple versions of python side by side and this makes that super easy.
You could also combine it with
direnvto automatically drop you into the correct environment based on the folder you are in, so you don’t have to type anything after the initial setup.The issue is more general. When dealing with, say,
apt, my experience is that nothing ever breaks and any false move is immediately recoverable. When dealing with Python, even seemingly trivial tasks inevitably turn into a broken mess of cryptic error messages and missing dependencies which requires hours of research to resolve. It’s a general complaint. The architecture seems fragile in some way. Of course, it’s possible it’s just because I am dumb and ignorant.When you come across some Python code for something written 5 years ago and they used four contributed packages that the programmers have changed the API on three times since then, you want to set up a virtual environment that contains those specific versions so you can at least see how it worked at that time. A small part of this headache comes from Python itself mutating, but the bulk of the problem is the imported user-contributed packages that multiply the functionality of Python.
To be sure, it would be nice if those programmers were all dedicated to updating their code, but with hundreds of thousands of packages that could be imported written by volunteers, you can’t afford to expect all of them them to stop innovating or even to continue maintaining past projects for your benefit.
If you have the itch to fix something old so it works in the latest versions of everything, you have that option… but it is really hard to do that if you cannot see it working as it was designed to work when it was built.
You really don’t want to use pip. That’s how you download malicious code.
Especially during the transition from 2 to 3. Let’s hope that’s all behind us.
It used to be button 10 (also counting 4 scrollwheel directions and click) of my Elecom trackball. I had written a small C program reading the device node and writing the events just of that to stdout, then piping that to a tclsh script (so I could change it easily and it’s still super fast for gaming) which did something in X. Horrible. But then they added support for more buttons to everything (kernel, X) and now I can just map it in games, like any other.
Trying to configure Sway in NixOS. I gave up and just use KDE Plasma. I do miss using Sway from when I used Arch, though.
Wild. I used sway for the first time with Nix since I could rollback a misconfiguration.
I use i3 - Sway is supposed to be 100% compatible with i3 - and I find the configuration file very straightforward. What’s different in the version in NixOS?
Getting Keycloak and Headscale working together.
But I did it after three weeks.
I captured my efforts in a set of interdependent Ansible roles so I never have to do it again.
Fortunately I haven’t had to open it in a very long time.
Why did we have to learn what modelines were to get a picture on screen?
Similar here. I used to have 2 screens that if they turned off for powersaving only 1 of them would wake up. So I had a script on the desktop to do a reset and move them correctly.
#!/bin/bash xrandr --output HDMI2 --off xrandr --output HDMI2 --auto --same-as HDMI1 xrandr --output HDMI1 --right-of HDMI2 exit
Nvidia drivers on Arch, KDE Plasma 6.
Isn’t it always postfix? Not because of the software, but because of other clients and other servers.
hyprland but I’m a noob
Rootless podman, PostgreSQL, redis, nextcloud, nginx, iptables in one…
I’ve been on arch for years, but have recently started pc gaming. Lutris has been surprisingly easy to get working. I have a nintendo switch already and decided I want to try to use the joycons for the computer, don’t want to buy gamepads but it gives and alternative to keyboard and mouse. Getting them consistently recognized by bluetooth has been a massive pain, but after searching I’ve figured out a package that I can install that fixes the issues. In fact, I couldn’t find anyone who found a solution to this issue without installing this specific package.
That package is pulseaudio-bluetooth, even though the nintendo joycons do not have an audio jack or capability to receive audio. I’ve had my audio set up and configured with alsa, and alsa does everything (relating to audio) that I need it to, but pulseaudio-bluetooth requires me to install pulseaudio (duh) and will not work unless I enable the pulseaudio service, which fucks up my alsa config. I’ve spent a while trying to dick around trying to get pulseaudio to pretend it doesn’t exist except for connecting joycons, but there’s always some nuisance popping up. I also tried using a different usb bluetooth controller and plugging them into different usb ports. Given up for the moment and will probably just buy another gamepad and hope it works better without needing pulseaudio-bluetooth.
In all honesty I still don’t really know what the hell I’m doing on arch, I originally installed it to learn this stuff better but all I’ve really learned is how to read documentation well enough to get things working by trial-and-error. I’ve had a stable system for like ten years now though and I’m too comfortable with it to warrant switching to a friendlier distro, but this specific issue is a pain in the ass.
