I needed to share some pictures from PC to the TV and I remember setting up Rygel in the past to do it. It wasn't pretty because it only worked if I kept rygel running in the foreground. That was several distributions ago. Figured that things might have changed.
I forgot how people on this side of the fence think. The "don't fix it unless it's broken" and "You need to scratch your own itch" mentality is still very much in force. A quick check confirmed that things were pretty much the same, not working by default. I prepared myself for an afternoon of shell commands and config file editing. But this time, I had something going for me. I had AI, specifically Google Gemini AI.
Started simple enough. It advised me to check whether everything is ok. Which included using the verbose mode using the command rygel -v. I found that really just displayed the version. What this meant was that Gemini may not know about rygel specifically and was using similar programs as analogies to come up with answers (Lesson #1). So I did what most people in conversation would do, I told it that it was wrong. Chatting AI is a form of communication which means information has to flow both ways. Telling it was wrong made it think harder and gave me the correct parameter, rygel -g 5. This increased the log level but it still didn't show anything. Gemini told me to set the environment variable G_MESSAGES_DEBUG=all rygel, which forces output from the underlying libraries. That did the trick. I also had to change the user's rygel config file to point the URIs from a link to the actual full path. From there I was able to set it to run automatically at the user level using systemctl --user ...
No comments:
Post a Comment