[–] 37 points 1 month ago (6 children)

Most of the indicators you're talking about are, in my opinion, superficial markers of adulthood. Do you show up for the people you care about? Do you fulfill your commitments? Do you look for opportunities to grow and improve? Do you do the hard thing you need to do instead of the easy thing?

These are the traits that make you an adult, not how many kids you have or whether you own or rent housing. You can have 10 kids or none and still be an adult. You can own, rent, or live in your parents' basement and still be an adult. You can't be making promises you don't keep or always taking the easy way out and be an adult. Those other things are all vanity metrics.

  • source
  • [–] 9 points 1 month ago (2 children)

    I don't know what the reception was at the time, but people seem to hate Stuntman, at least in retrospect. I loved it though. It's a driving game in which you play the part of a movie stuntman, driving through a movie set as the director barks orders at you, telling you live how to drive the scene. It has a nice variety of movies, and the scenes are actually cool to drive and to watch.

    It tickles a part of my brain that loves repeating a task until I perfect it... and boy, you get to do a lot of repetition.

    The one thing I don't like is that you suffer a PS2 load time with each failed attempt. We're talking minutes between attempts. Loved it apart from that though.

  • source
  • [–] 2 points 2 months ago

    Seconding Quartz, but I also wanted to share how I self-host all the services required. I self-host Forgejo and use obsidian-git to make it easier to push my vault changes to my self-hosted repo. The repo has a workflow that runs the Quartz build on any new commit, building to a location my web server points to.

    It works pretty well. About 2 minutes after a change is pushed, the build with those changes is done and being served.

  • source
  • parent
  • context
  • [–] 1 point 4 months ago (1 child)

    Thanks for the clarification. By "persist across restarts," I'm referring to the fact that if I just install the agent in my container, it won't persist if I restart the container, unless I install it on a volume which seems clunky. Running the agent alongside in a separate container with network access is the solution I was looking for.

    On the Redis and Valkey restores, that makes sense. Disaster recovery is my use case anyway. Do you document the manual restore process for those? I didn't notice it in a brief review of the docs, but I may have overlooked it.

  • source
  • parent
  • context
  • [–] 3 points 4 months ago (3 children)

    This looks exciting! A couple of questions:

    1. How would I deploy an agent into an existing docker container in a way that makes it persist across restarts? Most of my databases are running in containers.
    2. Regarding redis and valkey: what good does backup do without restore? Not trying to denigrate; I just really want to understand how that is useful.

    Thanks for building this!

  • source
  • [–] 3 points 5 months ago

    This has been my experience with Matrix, and the message decryption problems are a dealbreaker. I hope the person who replied to you saying those have very recently been fixed is correct, but the fact that such a fundamental feature was broken for so long leaves me with little confidence in Matrix. I had this problem years ago on a Matrix community, then again maybe a year ago on a different community, and even more recently on my self-hosted instance. Don't understand how you can push a chat platform that effectively doesn't deliver ~1/12 messages to random users and let that issue hang around for years.

    XMPP looks really interesting as an alternative. Hope that development continued at a brisk pace.

  • source
  • parent
  • context
  • [–] 36 points 6 months ago (11 children)

    Couldn't the same be said for just about any self-hosted app? You can watch video files with a local video player, so no need for Jellyfin; you can save passwords in KeePass, so no need for Vaultwarden; etc.

    Seems to me like, if you'd like to have access to this app along with your data from any computer without having to overlay a separate data syncing solution and install a local app on each of those computers, that's justification enough. Or maybe I'm just not understanding your critique here...

  • source
  • parent
  • context
  • [–] 3 points 6 months ago (2 children)

    I found a review summary that said the background music in the game made it difficult to see enemies and that I should turn down the BGM track to fix it. 😆

  • source
  • submitted 1 year ago* (last edited 1 year ago) by to c/linux@lemmy.ml
     

    I'm on Bazzite Linux 42 and was having some trouble with my 2.4GHz wireless keyboard disconnecting, so I decided to replace it. The new one is having similar issues despite being a different brand (new: XVX, old: Royal Kludge), so I suspect the culprit may actually have been software all along. I have a 2.4GHz wireless mouse connected to the same system that is generally reliable, so I don't believe it's an issue of 2.4GHz interference. The keyboards work well when connected to my Mac, so I don't believe it's faulty hardware.

    This keyboard has one feature that may be helpful in troubleshooting: it flashes an LED when it’s trying to reconnect. (The previous one had no indicator.) I can clearly see that, after the keyboard has been idle for a bit, it starts trying to reconnect again. I suspected a power management issue, but I believe I’ve disabled that. I started with a rule in /etc/udev/rules.d/:

    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1038", ATTR{idProduct}=="1830", TEST=="power/control", ATTR{power/control}="on"
    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0c45", ATTR{idProduct}=="fefe", TEST=="power/control", ATTR{power/control}="on"
    

    (These rules disable power management for both keyboard and mouse, just in case.) I got the IDs with lsusb. I’m assuming the part of the ID before the colon is the vendor ID and the part after is the product ID.

    That didn’t seem to help at all, so I tried disabling USB power management with rpm-ostree kargs --append-if-missing="usbcore.autosuspend=-1". That made the problem better, but now it just seems to take longer (a couple of minutes) for the keyboard to lose connectivity. Also, now when it loses connectivity, it seems even disconnecting and reconnecting the dongle doesn't always fix it.

    Anyone have ideas what I might try from here?

     

    I'm in the process of setting up backups for my home server, and I feel like I'm swimming upstream. It makes me think I'm just taking the wrong approach.

    I'm on a shoestring budget at the moment, so I won't really be able to implement a 3-2-1 strategy just yet. I figure the most bang for my buck right now is to set up off-site backups to a cloud provider. I first decided to do a full-system backup in the hopes I could just restore it and immediately be up and running again. I've seen a lot of comments saying this is the wrong approach, although I haven't seen anyone outline exactly why.

    I then decided I would instead cherry-pick my backup locations instead. Then I started reading about backing up databases, and it seems you can't just back up the data directory (or file in the case of SQLite) and call it good. You need to dump them first and backup the dumps.

    So, now I'm configuring a docker-db-backup container to back each one of them up, finding database containers and SQLite databases and configuring a backup job for each one. Then, I hope to drop all of those dumps into a single location and back that up to the cloud. This means that, if I need to rebuild, I'll have to restore the containers' volumes, restore the backups, bring up new containers, and then restore each container's backup into the new database. It's pretty far from my initial hope of being able to restore all the files and start using the newly restored system.

    Am I going down the wrong path here, or is this just the best way to do it?

     

    I'm running a Docker-based homelab that I manage primarily via Portainer, and I'm struggling with how to handle container updates. At first, I had all containers pulling latest, but I thought maybe this was a bad idea as I could end up updating a container without intending to. So, I circled back and pinned every container image in my docker-compose files.

    Then I started looking into how to handle updates. I've heard of Watchtower, but I noticed the Linuxserver.io images all recommend not running Watchtower and instead using Diun. In looking into it, I learned it will notify you of updates based on the tag you're tracking for the container, meaning it will never do anything for my containers pinned to a specific version. This made me think maybe I've taken the wrong approach.

    What is the best practice here? I want to generally try to keep things up to date, but I don't want to accidentally break things. My biggest fear about tracking latest is that I make some other change in a docker-compose and update the stack which pulls latest for all the container in that stack and breaks some of them with unintended updates. Is this a valid concern, and if so, how can I overcome it?

     

    I am running Bazzite 40 on a system with an RTX 4080. Up until yesterday, I was connecting computer -> Samsung HW-Q900C soundbar -> Samsung Q90C TV. I learned that the soundbar doesn't have HDMI 2.1 ports which is why I hadn't been able to get 120Hz, so I changed my setup to computer -> TV + soundbar -> TV (eARC).

    Now, I do have 120Hz, but I lost a bunch of other options in my display settings, including HDR. The only options I can set there now are resolution, orientation, refresh rate, and scale. I suspect this is an issue with the TV communicating its capabilities in a way the OS doesn't understand, but I'm not sure how to fix or work around it. Can anyone suggest a fix? Is there a setting I can change on the TV or maybe an app I can run on the computer to manually set the TV's capabilities?

    Update: Just discovered kscreen-doctor. Here's the output:

    Output: 445 HDMI-0
    	enabled
    	connected
    	priority 1
    	HDMI
    	Modes:  446:3840x2160@60!  447:4096x2160@120  448:4096x2160@100  449:4096x2160@60  450:4096x2160@50  451:4096x2160@30  452:4096x2160@24  453:4096x2160@24  454:3840x2160@144  455:3840x2160@120*  456:3840x2160@100  457:3840x2160@60  458:3840x2160@50  459:3840x2160@30  460:3840x2160@25  461:3840x2160@24  462:3840x1600@144  463:3840x1600@120  464:3840x1600@60  465:3840x1080@144  466:3840x1080@120  467:3840x1080@60  468:2560x1440@120  469:2560x1080@144  470:2560x1080@120  471:2560x1080@60  472:1920x1080@144  473:1920x1080@120  474:1920x1080@100  475:1920x1080@60  476:1920x1080@60  477:1920x1080@50  478:1920x1080@30  479:1920x1080@25  480:1920x1080@24  481:1680x1050@60  482:1600x900@60  483:1440x900@60  484:1280x1024@75  485:1280x1024@60  486:1280x800@60  487:1280x720@60  488:1280x720@60  489:1280x720@50  490:1152x864@75  491:1024x768@75  492:1024x768@70  493:1024x768@60  494:800x600@75  495:800x600@72  496:800x600@60  497:720x576@50  498:720x480@60  499:640x480@75  500:640x480@73  501:640x480@60 
    	Geometry: 0,0 3840x2160
    	Scale: 1
    	Rotation: 1
    	Overscan: 0
    	Vrr: incapable
    	RgbRange: unknown
    	HDR: incapable
    	Wide Color Gamut: incapable
    	ICC profile: incapable
    	Color profile source: incapable
    

    SOLUTION: Turns out this was my goof. I was trying to set up auto-login on my user account. In doing so, I set it to automatically log in to Plasma (X11) instead of Plasma (Wayland). Odd that the default option in that dropdown is not the one you’re currently using, but 🤷‍♂️.

    What I’m now trying to figure out is why I can’t set auto-login for Plasma (Wayland). The Apply button is disabled. 🤔

    Thanks to everyone who shared ideas.

    view more: next ›