[14:37] <leonardus> I haven't been paying attention, is there a release date for 18.10 yet?
=== not_phunyguy is now known as phunyguy
[20:39] <Rounin> TJ-: Seems that my other user, Mr. Guest Guest, also has the same issue
[20:39] <TJ-> Rounin: ok, that helps a lot
[20:40] <TJ-> so as pacmd also doesn't list it it seems to be a problem with PA finding the ALSA devices. I think the next thing to do is test the ALSA output to prove there is sound
[20:40] <TJ-> Rounin: can you show me "pastebinit <( aplay -L )"
[20:41] <Rounin> Outright moving .config/pulse and killall -9 pulse had no effect either
[20:42] <Rounin> TJ-: What a clever tool! http://paste.ubuntu.com/p/ShfRg6Ggyw/
[20:42] <Rounin> (Now all we need to do is build a network stack on top of it, and we can finally have functional bidirectional TCP again)
[20:46] <TJ-> Rounin: now try "speaker-test -Dfront:CARD=PCH -t wav"
[20:48] <Rounin> TJ-:  Hmmm... "Playback open error: -16,Device or resource busy"
[20:48] <Rounin> TJ-: And aplay with -D sysdefault led to: ALSA lib pcm_dmix.c:1063:(snd_pcm_dmix_open) unable to create IPC semaphore aplay: main:828: audio open error: Permission denied
[20:52] <Rounin> front:CARD=PCH seems to lead to "Device or resource busy" whereas sysdefault:CARD=PCH gets permission denied when creating the semaphore
[20:52] <Rounin> I was so sure we could blame Poettering for this one
[20:53] <TJ-> Rounin: I think I had the syntax slightly wrong; but I can't make it work here either - I suspected in my case PA had thw ALSA device open exclusively. The syntax should be "-Dfront:PCH -t wav"
[20:53] <Rounin> Ah wait wait
[20:54] <Rounin> Now I tried it as root
[20:54] <Rounin> Let me just move my cable over to the analogue port
[20:55] <Rounin> "left front left front..."
[20:55] <Rounin> Yeah, seems like it's just a permission issue
[20:55] <Rounin> If only I knew what to change the permissions of... Do you know where these devices are?
[20:57] <TJ-> Right, so maybe your user isn't in the plugdev and/or audio groups?
[20:57] <Rounin> There are some "pulse" and "audio" gr... Yup
[20:58] <Rounin> Perhaps I did something weird to make it work before, and it stopped working due to the upgrade?
[20:58] <Rounin> Can't imagine why it worked in the previous version
[20:59] <TJ-> Rounin: have you reviewed the syslog/auth.log for clues ?
[21:00] <Rounin> TJ-: Oh wow! A lot of "Oct  6 17:53:30 lightning dbus-daemon[846]: [system] Rejected send message, 1 matched rules; type="error", sender=":1.42" (uid=1000 pid=2144 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.299" (uid=0 pid=8035 comm="/usr/lib/bluetooth/bluetoothd " 
[21:00] <Rounin> label="unconfi"
[21:00] <Rounin> Etc. etc.
[21:01] <Rounin> I've added myself to the groups, so I'll try logging out entirely and then back in
[21:01] <Rounin> Brb
[21:15] <Rounin> Hello again! I had to go in with a bootable USB and change my root password... Apparently I misspelled it when I set it, and the next 5-6 times I typed it
[21:15] <Rounin> Anyway, TJ-, I just wanted to say it's working now, and it was indeed the pulseaudio/audio/etc. group issue. Thanks so much for your help!
[21:16] <TJ-> Rounin: yay! I wonder if that needs reporting since it seems it should have been handled in the upgrade
[21:17] <Rounin> TJ-: Yeah, hard to tell... After all, who knows how and why it was working before?