There's a podman container for ollama on my system that keeps starting and stopping. I don't even ha
There's a podman container for ollama on my system that keeps starting and stopping. I don't even have ollama installed anymore
OIs there a way to address this?
Jdelete the container with podman rm?
OIt's immediately recreating itself and repeating the same problem?
Jdo you have the service installed?
Jsystemctl status --user ollama?OOh yeah I do, hm
Obut it's only loaded, not started?
Olisting it shows as Loaded but attempting to
systemctl stop ollama.service says the sevice isn't loadedJyou need the --user in there
Oah, i see
Jand then after you stop it do a disable and then container cleanup should be easy
OMhm, just did that, seems like it fixed the issue
Jor do a
podman system clean to just clean up in general after you do thatOgood call, actually
Osystem isn't a valid subcommand apparently but I can do through the cleanup manually through podman desktop
Othanks for the help
PIs it possible to prevent the screen from dimming or turning off while in desktop > fullscreen mode? Windows does this automatically if you're watching a maximized Netflix browser window for example. Of course we can turn off screen suspend/dim manually but I was wondering if there's a better way - maybe add browser set to Netflix in game mode?
OShould be dependent on the desktop you're using. Are you using Plasma?
Oif you are, you can go into the power applet and literally just flip a switch to disable screen locking
Ofor GNOME you might need the caffiene extension
Kpreinstalled
OAaah
Ogood call
VDoes anyone know if the steam deck gnome build has the frame/fps limited issue fixed yet?
KI have that build on 6 devices and cannot reproduce it
Kincluding an OLED deck, LCD deck, LGO, desktop, and two laptops
Kno promises
Kthere is no part of GNOME running when gamescope does and no difference in the session
VInteresting, when I use the built in frame limited in gamescope last I tested it it did nothing unless I specifically turned on vsync in game
Kso an issue like that also would not be GNOME specific
Kyeah, no such issue here
VBad install maybe? Could always try it again
VI highly doubt it but I did install via a ventoy USB, think that could be related in some capacity?
Kimmutable, we all have the same system
Kcan't be that
ZVentoy actually is the best way to install tbh
VI'll try reinstalling it then, if I get the same issue again I'll report back
Kthis too
Vshould rumble work for xbox-like controllers connected via bluetooth?
Kyes
KI am using an elite controller series 2 right now
Krumble works fine
VI have a Flydigi Vader 3 pro, looks like it works on cable, but not bt
Kgame running through steam?
Hhere is a log of the failure to go to desktop. I selected "Switch to Desktop" from Gamemode at 16:05. Interestingly, also, gamemode keeps telling me I have a steam update no matter how many times I apply it.
It looks like it's trying to start plasma? Isn't that the KDE variant?
Is gnome still supported or did I somehow clobber the start command?
It looks like it's trying to start plasma? Isn't that the KDE variant?
Is gnome still supported or did I somehow clobber the start command?
log.txt590.11KB
Vnope, heroic launcher, but proton. I'm checking it in steam settings, when I connect via cable, it shows up as a "xbox 360 controller", but on BT it is "flydigi vader 3p". Only the cable version has the "rumble" option during testing in the steam settings
Hdoes the flydigi have a way to change its mode, its in dinput over bt atm which usually does not expose rumble
Hyou need it to be in xinput mode
Kplasma is generic, it just means "desktop"
Vhmm, it has some windows-only software to tune it. Lemme fire up the VM to check it
