[12:25] <cmaloney> BTW MUG Meeting tonight (http://mug.org)
[12:26] <cmaloney> We're going to be remote for the forseeable future so if you've wanted to come to a meeting this is as good a time as any. ;)
[14:13] <cmaloney> http://n-gate.com/hackernews/2020/09/07/0/
[14:32] <Scary_Guy> lol, I've read all of that.  Funny site though and I like how they put hacker in quotes.
[14:33] <Scary_Guy> My favorite client is still materialistic for android.
[14:33] <Scary_Guy> Though it could use some updating
[14:35] <Scary_Guy> I didn't see this mentioned though.  I thought it was big news https://linuxreviews.org/%22Linusgate%22_Leaked:_Over_250_Messages_About_Code_of_Conduct_Complaints_Against_Linus_Torvalds
[14:49] <cmaloney> I'm sure there's a point in there but damned if I can find it
[17:32] <brian__> Does anyone know what might prevent a program run as a user cron job from playing sound to the ALSA driver?
[17:32] <brian__> The program in question works just fine when run from the terminal.
[17:32] <jrwren> env vars
[17:33] <brian__> Ok, thanks. I need to go spelunking through my env to see what might be missing, then. *sigh*
[17:35] <brian__> The odd thing is that it used to work, meaning something changed in my setup since then.
[17:37] <cmaloney> brian__: Also could be that ALSA is locked by another process
[17:41] <brian__> It's looking like env vars. Running bash with an empty env gets me "Connection refused" and "Inappropriate ioctl for device" messages.
[17:42] <cmaloney> Does it work from cron when you're logged in?
[17:43] <brian__> No.
[17:43] <jrwren> what app?
[17:43] <cmaloney> how are you opening the sound device / executing th is? :)
[17:43] <jrwren> mpg123 or something?
[17:44] <brian__> paplay from the pulseaudio-utils package.
[17:45] <cmaloney> paplay to the alsa device?
[17:47] <brian__> The actual program is grandfatherclock. I initially thought it was going straight to ALSA when I glanced at the config file, but it's actually calling paplay which then tries to play a .au sound file to Pulse audio.
[17:48] <cmaloney> ah, OK
[17:48] <cmaloney> So it's not alsa, but more likely pulseaudio
[17:48] <brian__> Yes.
[17:49] <cmaloney> is it a system-wide pulseaudio or pulseaudio that's started by your user?
[17:49] <cmaloney> If it's Ubuntu then you likely have two pulseaudio daemons running
[17:49] <cmaloney> one for lightdm and one for your user
[17:50] <brian__> My user.
[17:50] <brian__> I just see the one.
[17:50] <brian__> Ok, that makes sense, then.
[17:50] <cmaloney> you might have some luck adding "--verbose" to see what it's trying to run
[17:51] <cmaloney> because pulseaudio tries to smooth over a lot of crap happening at the soundcard level
[17:52] <cmaloney> The "connection refused" is likely that the daemon isn't running
[17:52] <cmaloney> the inappropriate ioctl makes me wonder what device it's trying to run against, and if it's actually trying some odd fallback or something
[17:52] <cmaloney> but --verbose should give you more details on what its doing.
[17:52] <cmaloney> Good luck!
[17:52] <brian__> You're right, I don't think it is. top tells me that pulseaudiop is being run with the --daemonize=no options.
[17:53] <cmaloney> That's likely the gdm version
[17:53] <brian__> I'm running KDE.
[17:53] <cmaloney> erm, whatever KDE does then. ;)
[17:54] <cmaloney> check the user that its running against
[17:55] <brian__> It's running as my user.
[17:57] <jrwren> what about PULSE_SERVER envvar?
[17:57] <brian__> Not defined.
[18:00] <jrwren> what does pax11publish or xprop -root PULSE_SERVER say?
[18:00] <brian__> not found
[18:01] <jrwren> no pax11publish command? hrmf.
[18:01] <brian__> I have it. It just doesn't print anything.
[18:02] <brian__> And now I've messed everything up. My KDE volume control widget is no longer recognizing the ouput device (Pulse Audio).
[18:04] <brian__> I'm going to log out and log back in to try getting KDE's Pulse Audio config to work again.
[18:45] <brian__> Finally got it. I needed to configure pulseaudio to set up a unix socket that clients can use.
[18:46] <cmaloney> Ah, cool
[18:46] <cmaloney> Glad it got sorted
[22:41] <cmaloney> https://octodon.social/@craigmaloney/104831655861756082