Sound is generally working, but not in the Phoniebox #2267

mag-1sm · 2024-02-18T18:49:59Z

mag-1sm
Feb 18, 2024

Hello and thanks a lot for this great application,

this is my first contribution in the forum, so hopefully I do everything correct ...
I know there were (and are) several threads about this topic, but nothing helped in my case.

I work with a Raspberry 3B without a sound card. My install is without spotify.
This is the third time I build a phoniebox. The first time in 2019 (still working), the second time in 2021 (working until recently, now SD-Card defect)

I downloaded the legacy release mentioned on the page and the imager and installed it on the Micro-SD.
After sudo apt-get update and sudo apt-get upgrade I installed the Phoniebox via the current one-line-install command

cd; rm install-jukebox.sh; wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/master/scripts/installscripts/install-jukebox.sh; chmod +x install-jukebox.sh; ./install-jukebox.sh

After a reboot I didn't hear the startup sound, which I was used to from my previous installs. Neither did I hear a second beep from the Phoniebox.
I started the desktop and turned up every volume-button. I had to manually activate the RFID-function, although I thought I chose the correct RFID-Reader. After that I connected functions like stop or shutdown to chips and they work. The player does start with a RFID-chip, but I can hear no sound.

If I play the same file outside the phoniebox I can hear it.

Mainly two things were different this time:

Installation via Imager, not Noobs. But that shouldn't make any difference.
This time the Phoniebox prompted iFace "Headphone". Last time it was PCM.

The problem is similar to Issue 561, but the solution mentioned there didn't work for me.
It is also similar to Issue 1220, which was solved via issue 1202, but I couldn't find the file asound.conf on my system.
The Audio-FAQ couldn't help me as well.
aplay -l shows

By now I tried it several times with various settings and on two different Raspis, I cannot solve the problem. Could you possibly help me out?

Answered by AlvinSchiller

Feb 22, 2024

I took a closer look into this:

It seems that since bookworm the audio device order has changed for the "desktop" version (maybe caused by "Pipewire"?). This causes the error for the playback (before "bcm*" was id 0, now its id 1).
To fix this the default audio device can be changed using the "/etc/asound.conf" file, like described here.

sudo nano /etc/asound.conf

pcm.!default {
    type hw
    card 1
}
ctl.!default {
    type hw
    card 1
}

Also there is a bug in the interface selection during the setup. For the "desktop" version the result differs for amixer scontrols and sudo amixer scontrols. As the mpd service is run as root the output of sudo amixer scontrols has to be used to fun…

View full answer

mag-1sm · 2024-02-18T20:15:51Z

mag-1sm
Feb 18, 2024
Author

The first text was incomplete. I forgot aplay -l

**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: vc4hdmi [vc4-hdmi], Gerät 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 1: Headphones [bcm2835 Headphones], Gerät 0: bcm2835 Headphones [bcm2835 Headphones]
  Sub-Geräte: 8/8
  Sub-Gerät #0: subdevice #0
  Sub-Gerät #1: subdevice #1
  Sub-Gerät #2: subdevice #2
  Sub-Gerät #3: subdevice #3
  Sub-Gerät #4: subdevice #4
  Sub-Gerät #5: subdevice #5
  Sub-Gerät #6: subdevice #6
  Sub-Gerät #7: subdevice #7

0 replies

s-martin · 2024-02-18T20:49:03Z

s-martin
Feb 18, 2024
Collaborator

Please check, if the name is „Headphones“ (attention to the plural S!) in /etc/mpd.conf, settings/global.conf and settings/Audio_iFace_Name.

4 replies

olbasoil Feb 18, 2024

I have a the same issue. _ have changed Headphone to Headphones in /etc/mpd.conf but I can't find a settings directory?

s-martin Feb 18, 2024
Collaborator

Should be in the Phoniebox directory /home/pi/RPi-Jukebox-RFID

olbasoil Feb 18, 2024

Thanks for the instant reply. I found them and have changed Headphone to Headphones in all 3 files, rebooted but still have the same issue (no sound, not playing).
This is my first exposure to the interface, so I may be reading it all wrong, but I do get the message ' is playing', the counter shows the track length, but the first number, which I assume is position, is stuck on zero.
I'm also not sure how to verify that sound is working on the Pi without a desktop?
#mag-1sm I hope you don't mind me joining in, but the issues seem to be the same.

mag-1sm Feb 18, 2024
Author

Don't worry, I'm happy not to be alone with this problem.
I test it with my headphones in the headphone jack. Alternatively I tried loudspeakers with USB-Power supply and headphone jack connection, but this time nothing works.

mag-1sm · 2024-02-18T21:24:11Z

mag-1sm
Feb 18, 2024
Author

I read about this plural earlier and changed it in mpd.conf, but only in one file. Now I changed all three - but nothing changed.

2 replies

s-martin Feb 18, 2024
Collaborator

Did you restart?

mag-1sm Feb 18, 2024
Author

A reboot didn't help.

AlvinSchiller · 2024-02-18T22:10:18Z

AlvinSchiller
Feb 18, 2024
Collaborator

Can you post the output of amixer scontrols?

0 replies

olbasoil · 2024-02-18T22:17:44Z

olbasoil
Feb 18, 2024

This is mine:

Simple mixer control 'Master',0
Simple mixer control 'Capture',0
pi@pimusic:~ $ amixer scontrols
Simple mixer control 'Master',0
Simple mixer control 'Capture',0

4 replies

mag-1sm Feb 18, 2024
Author

same ...
pi@raspberrypi:~ $ amixer scontrols
Simple mixer control 'Master',0
Simple mixer control 'Capture',0

AlvinSchiller Feb 19, 2024
Collaborator

Can you try and replace "Headphones" with "Master" in all three files, described above?

olbasoil Feb 19, 2024

I have replaced Headphones with Master in the three config files, but still no sound.
Where I can see '00 : 00 / 15 : 09' in the interface, the '00:00' never increases.
I can confirm that vlc is able to play the files.

AlvinSchiller Feb 19, 2024
Collaborator

hmm ok strange.
Can you supply the output of tail -n 200 /var/log/syslog to get some more information for research?

olbasoil · 2024-02-19T11:53:56Z

olbasoil
Feb 19, 2024

I just got this:

tail: cannot open '/var/log/syslog' for reading: No such file or directory

0 replies

olbasoil · 2024-02-19T11:57:59Z

olbasoil
Feb 19, 2024

these are the files I have in /var/log

alternatives.log cups lastlog samba
apt dpkg.log lightdm vncserver-x11.log
boot.log exim4 lighttpd vncserver-x11.log.bak
boot.log.1 faillog mpd wtmp
boot.log.2 fontconfig.log private Xorg.0.log
bootstrap.log hp README Xorg.0.log.old
btmp journal runit

5 replies

AlvinSchiller Feb 19, 2024
Collaborator

Ah you are on bookworm, right?
Please please then use journalctl -n 200 after you started playback.

olbasoil Feb 19, 2024

This is the journalctl after a reboot and attempting to play a track
Feb 19 15:09:14 pimusic systemd-timesyncd[418]: Contacted time server 90.155.73.34:123 (2.debian.pool.ntp.org).
Feb 19 15:09:14 pimusic systemd-timesyncd[418]: Initial clock synchronization to Mon 2024-02-19 15:09:14.155412 GMT.
Feb 19 15:09:14 pimusic systemd[1]: Starting phpsessionclean.service - Clean php session files...
Feb 19 15:09:14 pimusic systemd[1]: phpsessionclean.service: Deactivated successfully.
Feb 19 15:09:14 pimusic systemd[1]: Finished phpsessionclean.service - Clean php session files.
Feb 19 15:09:17 pimusic systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Feb 19 15:09:28 pimusic sudo[1364]: www-data : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/echo playlistinfo#012close
Feb 19 15:09:28 pimusic sudo[1364]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=33)
Feb 19 15:09:28 pimusic sudo[1364]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:31 pimusic sudo[1368]: www-data : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/home/pi/RPi-Jukebox-RFID/scripts/playout_controls.sh -c=playerplay
Feb 19 15:09:31 pimusic sudo[1368]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=33)
Feb 19 15:09:31 pimusic mpd[661]: exception: Failed to open "My ALSA Device" (alsa); Failed to open ALSA device "default": Unknown error 524
Feb 19 15:09:31 pimusic mpd[661]: exception: Failed to open "My ALSA Device" (alsa); Failed to open ALSA device "default": Unknown error 524
Feb 19 15:09:31 pimusic sudo[1368]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:37 pimusic sudo[1411]: www-data : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/home/pi/RPi-Jukebox-RFID/scripts/rfid_trigger_play.sh -d=tallis
Feb 19 15:09:37 pimusic sudo[1411]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=33)
Feb 19 15:09:37 pimusic mpd[661]: player: played "tallis/beepbeep.mp3"
Feb 19 15:09:38 pimusic mpd[661]: exception: Failed to open "My ALSA Device" (alsa); Failed to open ALSA device "default": Unknown error 524
Feb 19 15:09:38 pimusic mpd[661]: exception: Failed to open "My ALSA Device" (alsa); Failed to open ALSA device "default": Unknown error 524
Feb 19 15:09:38 pimusic mpd[661]: player: problems opening audio device while playing "tallis/beepbeep.mp3"
Feb 19 15:09:39 pimusic sudo[1524]: root : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/echo tallis
Feb 19 15:09:39 pimusic sudo[1524]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:09:39 pimusic sudo[1524]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1526]: root : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/chown pi:www-data /home/pi/RPi-Jukebox-RFID/scripts/../set>
Feb 19 15:09:39 pimusic sudo[1526]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:09:39 pimusic sudo[1526]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1528]: root : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/chmod 777 /home/pi/RPi-Jukebox-RFID/scripts/../settings/La>
Feb 19 15:09:39 pimusic sudo[1528]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:09:39 pimusic sudo[1528]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1530]: root : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/echo tallis
Feb 19 15:09:39 pimusic sudo[1530]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:09:39 pimusic sudo[1530]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1532]: root : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/chown pi:www-data /home/pi/RPi-Jukebox-RFID/scripts/../set>
Feb 19 15:09:39 pimusic sudo[1532]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:09:39 pimusic sudo[1532]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1534]: root : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/chmod 777 /home/pi/RPi-Jukebox-RFID/scripts/../settings/La>
Feb 19 15:09:39 pimusic sudo[1534]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:09:39 pimusic sudo[1534]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1411]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:39 pimusic sudo[1537]: www-data : PWD=/home/pi/RPi-Jukebox-RFID/htdocs/api ; USER=root ; COMMAND=/usr/bin/echo playlistinfo#012close
Feb 19 15:09:39 pimusic sudo[1537]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=33)
Feb 19 15:09:39 pimusic sudo[1537]: pam_unix(sudo:session): session closed for user root
Feb 19 15:09:46 pimusic systemd[1]: phoniebox-idle-watchdog.service: Deactivated successfully.
Feb 19 15:10:09 pimusic CRON[1543]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 19 15:10:09 pimusic CRON[1544]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Feb 19 15:10:09 pimusic CRON[1543]: pam_unix(cron:session): session closed for user root

AlvinSchiller Feb 19, 2024
Collaborator

Looks Like Mpd is using the device name "default". Can you post the "audio_output" entries of your mpd.conf?

mag-1sm Feb 19, 2024
Author

Assuming all the #-lines are comments I found this (let's see if olbasoil writes the same):

# An example of an ALSA output:
#
audio_output {
	type		"alsa"
	name		"My ALSA Device"
#	device		"hw:0,0"	# optional
#	mixer_type      "hardware"      # optional
#	mixer_device	"default"	# optional
	mixer_control	"Headphones"		# optional
#	mixer_index	"0"		# optional
}

Everything else regarding audio_output also seems to be on comment. You can still see "headphones", because I just got back to the computer and didn't try the change to "master", which doesn't seem to have worked. As far as I know I am on bookworm too.

AlvinSchiller Feb 19, 2024
Collaborator

Please try "Master" nevertheless and also supply the log output, to have some references.

olbasoil · 2024-02-19T17:15:17Z

olbasoil
Feb 19, 2024

Yes, mine is identical. Everything is commented out except

audio_output {
type "alsa"
name "My ALSA Device"

1 reply

olbasoil Feb 19, 2024

sorry, I also have

#	device		"hw:0,0"	# optional
#	mixer_type      "hardware"      # optional
#	mixer_device	"default"	# optional
	mixer_control	"Master"		# optional
#	mixer_index	"0"		# optional

AlvinSchiller · 2024-02-19T19:45:35Z

AlvinSchiller
Feb 19, 2024
Collaborator

I'm I right that you are using the "desktop" version of Raspberry Pi OS?

4 replies

mag-1sm Feb 19, 2024
Author

Yes, I am using the desktop version. I never tried or worked with the lite version, but if it runs there correctly it is worth a try ...
I changed everything to master and restarted ... still no sound. Log follows.

In the beginning there is something from the zzz-folder, which I created via the scripts for testing. The file I played for this log is in the standard shared-Folder.

Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster/bbb-AudioF>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster/bbb-AudioF>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster/bbb-AudioF>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster/fff-threeS>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster/fff-threeS>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster/fff-threeS>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi autohotspot[1570]: Wifi already connected to a netw>
Feb 19 20:44:25 raspberrypi systemd[1]: Finished autohotspot.service - Automati>
Feb 19 20:44:25 raspberrypi systemd[1]: Startup finished in 6.202s (kernel) + 2>
Feb 19 20:44:25 raspberrypi mpd[695]: ffmpeg/ac3: Estimating duration from bitr>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/AudioFormatsTest/aud>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/MP3 Whitespace Start>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number00.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number01.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number06.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number07.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number02.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number09.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number05.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number0..mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number08.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number04.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number10.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/Counting/number03.mp3
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/MP3-StartUpSound/sta>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: ffmpeg/ac3: Estimating duration from bitr>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi mpd[695]: update: updating ZZZ/SubMaster Whitespace>
Feb 19 20:44:25 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:44:25 raspberrypi systemd[1381]: Starting gvfs-udisks2-volume-monitor>
Feb 19 20:44:25 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:44:25 raspberrypi systemd[1381]: Started gvfs-udisks2-volume-monitor.>
Feb 19 20:44:25 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:44:26 raspberrypi systemd[1381]: Starting gvfs-gphoto2-volume-monitor>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:44:26 raspberrypi systemd[1381]: Started gvfs-gphoto2-volume-monitor.>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:44:26 raspberrypi systemd[1381]: Starting gvfs-goa-volume-monitor.ser>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:44:26 raspberrypi systemd[1381]: Started gvfs-goa-volume-monitor.serv>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:44:26 raspberrypi systemd[1381]: Starting gvfs-afc-volume-monitor.ser>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:44:26 raspberrypi systemd[1381]: Started gvfs-afc-volume-monitor.serv>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:44:26 raspberrypi systemd[1381]: Starting gvfs-mtp-volume-monitor.ser>
Feb 19 20:44:26 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:44:26 raspberrypi systemd[1381]: Started gvfs-mtp-volume-monitor.serv>
Feb 19 20:44:28 raspberrypi NetworkManager[620]: [1708371868.0593] agen>
Feb 19 20:44:29 raspberrypi dbus-daemon[494]: [system] Activating via systemd: >
Feb 19 20:44:29 raspberrypi systemd[1]: Starting packagekit.service - PackageKi>
Feb 19 20:44:29 raspberrypi PackageKit[1848]: daemon start
Feb 19 20:44:29 raspberrypi dbus-daemon[494]: [system] Successfully activated s>
Feb 19 20:44:29 raspberrypi systemd[1]: Started packagekit.service - PackageKit>
Feb 19 20:44:29 raspberrypi PackageKit[1848]: uid 1000 is trying to obtain org.>
Feb 19 20:44:29 raspberrypi PackageKit[1848]: uid 1000 obtained auth for org.fr>
Feb 19 20:44:33 raspberrypi systemd[1]: systemd-fsckd.service: Deactivated succ>
Feb 19 20:44:37 raspberrypi PackageKit[1848]: refresh-cache transaction /15_bee>
Feb 19 20:44:40 raspberrypi systemd[1]: systemd-hostnamed.service: Deactivated >
Feb 19 20:44:45 raspberrypi systemd-timesyncd[368]: Timed out waiting for reply>
Feb 19 20:45:01 raspberrypi systemd-timesyncd[368]: Contacted time server 94.16>
Feb 19 20:45:01 raspberrypi systemd-timesyncd[368]: Initial clock synchronizati>
Feb 19 20:45:12 raspberrypi PackageKit[1848]: get-updates transaction /16_bcbab>
Feb 19 20:45:17 raspberrypi CRON[2300]: pam_unix(cron:session): session opened >
Feb 19 20:45:17 raspberrypi CRON[2301]: (pi) CMD (sudo /usr/bin/autohotspot >/d>
Feb 19 20:45:17 raspberrypi sudo[2302]: pi : PWD=/home/pi ; USER=root ; C>
Feb 19 20:45:17 raspberrypi sudo[2302]: pam_unix(sudo:session): session opened >
Feb 19 20:45:18 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:45:18 raspberrypi systemd[1381]: Starting xdg-desktop-portal.service >
Feb 19 20:45:19 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:45:19 raspberrypi systemd[1381]: Starting xdg-document-portal.service>
Feb 19 20:45:19 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:45:19 raspberrypi systemd[1381]: Starting xdg-permission-store.servic>
Feb 19 20:45:19 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:45:19 raspberrypi systemd[1381]: Started xdg-permission-store.service>
Feb 19 20:45:19 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:45:19 raspberrypi systemd[1381]: Started xdg-document-portal.service >
Feb 19 20:45:19 raspberrypi sudo[2302]: pam_unix(sudo:session): session closed >
Feb 19 20:45:19 raspberrypi CRON[2300]: pam_unix(cron:session): session closed >
Feb 19 20:45:19 raspberrypi xdg-document-portal[2382]: Ignoring invalid max thr>
Feb 19 20:45:19 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:45:19 raspberrypi systemd[1381]: Starting xdg-desktop-portal-gtk.serv>
Feb 19 20:45:20 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:45:20 raspberrypi systemd[1381]: Started xdg-desktop-portal-gtk.servi>
Feb 19 20:45:20 raspberrypi rtkit-daemon[1415]: Supervising 6 threads of 3 proc>
Feb 19 20:45:20 raspberrypi rtkit-daemon[1415]: Supervising 6 threads of 3 proc>
Feb 19 20:45:20 raspberrypi rtkit-daemon[1415]: Supervising 6 threads of 3 proc>
Feb 19 20:45:20 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:45:20 raspberrypi systemd[1381]: xdg-desktop-portal-wlr.service - Por>
Feb 19 20:45:29 raspberrypi systemd[1]: phoniebox-idle-watchdog.service: Deacti>
Feb 19 20:45:45 raspberrypi xdg-desktop-por[2364]: Failed to create screenshot >
Feb 19 20:45:45 raspberrypi xdg-desktop-por[2364]: No skeleton to export
Feb 19 20:45:46 raspberrypi sudo[2525]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:45:46 raspberrypi sudo[2525]: pam_unix(sudo:session): session opened >
Feb 19 20:45:46 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Acti>
Feb 19 20:45:47 raspberrypi sudo[2525]: pam_unix(sudo:session): session closed >
Feb 19 20:45:47 raspberrypi systemd[1381]: Started gnome-keyring-daemon.service>
Feb 19 20:45:47 raspberrypi sudo[2561]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:45:47 raspberrypi sudo[2561]: pam_unix(sudo:session): session opened >
Feb 19 20:45:47 raspberrypi sudo[2561]: pam_unix(sudo:session): session closed >
Feb 19 20:45:47 raspberrypi gnome-keyring-daemon[2559]: GNOME_KEYRING_CONTROL=/>
Feb 19 20:45:47 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:45:47 raspberrypi gnome-keyring-daemon[2559]: The Secret Service was >
Feb 19 20:45:47 raspberrypi gnome-keyring-daemon[2529]: discover_other_daemon: 1
Feb 19 20:45:47 raspberrypi org.freedesktop.secrets[2529]: GNOME_KEYRING_CONTRO>
Feb 19 20:45:47 raspberrypi gnome-keyring-d[2559]: The Secret Service was alrea>
Feb 19 20:45:52 raspberrypi sudo[2571]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:45:52 raspberrypi sudo[2571]: pam_unix(sudo:session): session opened >
Feb 19 20:45:52 raspberrypi sudo[2571]: pam_unix(sudo:session): session closed >
Feb 19 20:45:57 raspberrypi sudo[2603]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:45:57 raspberrypi sudo[2603]: pam_unix(sudo:session): session opened >
Feb 19 20:45:57 raspberrypi sudo[2603]: pam_unix(sudo:session): session closed >
Feb 19 20:46:02 raspberrypi sudo[2635]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:02 raspberrypi sudo[2635]: pam_unix(sudo:session): session opened >
Feb 19 20:46:02 raspberrypi sudo[2635]: pam_unix(sudo:session): session closed >
Feb 19 20:46:07 raspberrypi sudo[2667]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:07 raspberrypi sudo[2667]: pam_unix(sudo:session): session opened >
Feb 19 20:46:08 raspberrypi sudo[2667]: pam_unix(sudo:session): session closed >
Feb 19 20:46:12 raspberrypi xdg-desktop-por[2364]: Failed to create screen cast>
Feb 19 20:46:12 raspberrypi xdg-desktop-por[2364]: No skeleton to export
Feb 19 20:46:12 raspberrypi dbus-daemon[1403]: [session uid=1000 pid=1403] Succ>
Feb 19 20:46:12 raspberrypi systemd[1381]: Started xdg-desktop-portal.service ->
Feb 19 20:46:13 raspberrypi sudo[2701]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:13 raspberrypi sudo[2701]: pam_unix(sudo:session): session opened >
Feb 19 20:46:13 raspberrypi sudo[2701]: pam_unix(sudo:session): session closed >
Feb 19 20:46:18 raspberrypi sudo[2733]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:18 raspberrypi sudo[2733]: pam_unix(sudo:session): session opened >
Feb 19 20:46:18 raspberrypi sudo[2733]: pam_unix(sudo:session): session closed >
Feb 19 20:46:23 raspberrypi sudo[2770]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:23 raspberrypi sudo[2770]: pam_unix(sudo:session): session opened >
Feb 19 20:46:23 raspberrypi sudo[2770]: pam_unix(sudo:session): session closed >
Feb 19 20:46:28 raspberrypi sudo[2802]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:28 raspberrypi sudo[2802]: pam_unix(sudo:session): session opened >
Feb 19 20:46:28 raspberrypi sudo[2802]: pam_unix(sudo:session): session closed >
Feb 19 20:46:33 raspberrypi sudo[2834]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:33 raspberrypi sudo[2834]: pam_unix(sudo:session): session opened >
Feb 19 20:46:34 raspberrypi sudo[2834]: pam_unix(sudo:session): session closed >
Feb 19 20:46:39 raspberrypi sudo[2866]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:39 raspberrypi sudo[2866]: pam_unix(sudo:session): session opened >
Feb 19 20:46:39 raspberrypi sudo[2866]: pam_unix(sudo:session): session closed >
Feb 19 20:46:39 raspberrypi sudo[2898]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:39 raspberrypi sudo[2898]: pam_unix(sudo:session): session opened >
Feb 19 20:46:39 raspberrypi mpd[695]: mixer: Failed to set mixer for 'My ALSA D>
Feb 19 20:46:39 raspberrypi mpd[695]: exception: Failed to set mixer for 'My AL>
Feb 19 20:46:39 raspberrypi sudo[2898]: pam_unix(sudo:session): session closed >
Feb 19 20:46:41 raspberrypi sudo[2909]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:41 raspberrypi sudo[2909]: pam_unix(sudo:session): session opened >
Feb 19 20:46:44 raspberrypi mpd[695]: output: Failed to open mixer for 'My ALSA>
Feb 19 20:46:44 raspberrypi sudo[3026]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:44 raspberrypi sudo[3026]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3026]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3058]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3058]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3058]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3060]: root : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3060]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3060]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3063]: root : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3063]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3063]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3065]: root : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3065]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3065]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3067]: root : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3067]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3067]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3069]: root : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3069]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3069]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3071]: root : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3071]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3071]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[2909]: pam_unix(sudo:session): session closed >
Feb 19 20:46:45 raspberrypi sudo[3074]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:45 raspberrypi sudo[3074]: pam_unix(sudo:session): session opened >
Feb 19 20:46:45 raspberrypi sudo[3074]: pam_unix(sudo:session): session closed >
Feb 19 20:46:50 raspberrypi sudo[3106]: www-data : PWD=/home/pi/RPi-Jukebox-RFI>
Feb 19 20:46:50 raspberrypi sudo[3106]: pam_unix(sudo:session): session opened >
Feb 19 20:46:50 raspberrypi sudo[3106]: pam_unix(sudo:session): session closed

AlvinSchiller Feb 19, 2024
Collaborator

I installed the desktop version and facing the same issue. Using the lite version is behaving the correct way.

I will take a closer look on this later, but if you are not needing the desktop, that would be a fix.

AlvinSchiller Feb 22, 2024
Collaborator

I took a closer look into this:

It seems that since bookworm the audio device order has changed for the "desktop" version (maybe caused by "Pipewire"?). This causes the error for the playback (before "bcm*" was id 0, now its id 1).
To fix this the default audio device can be changed using the "/etc/asound.conf" file, like described here.

sudo nano /etc/asound.conf

pcm.!default {
    type hw
    card 1
}
ctl.!default {
    type hw
    card 1
}

Also there is a bug in the interface selection during the setup. For the "desktop" version the result differs for amixer scontrols and sudo amixer scontrols. As the mpd service is run as root the output of sudo amixer scontrols has to be used to function properly (e.g. volume control).
So most likly PCM has to be used instead of Master or Headphone.
Please change this in all three files described earlier or here.

Answer selected by AlvinSchiller

s-martin Feb 22, 2024
Collaborator

I wonder when the RaspberryPi team will finally stop changing the audio stuff. 🫣

Was also breaking things for buster....

olbasoil · 2024-02-19T20:39:07Z

olbasoil
Feb 19, 2024

I've just done a fresh install on bullseye lite 32, and it is working perfectly. Many thanks for your help in this.
#mag-1sm I hope this is also working for you.

0 replies

mag-1sm · 2024-02-19T21:56:06Z

mag-1sm
Feb 19, 2024
Author

Uh. After an install of the lite version I finally get the startup sound, so it seems to be working. But apart from that everything else seems to become way more complicated. Apart from the fact that I must have done something wrong during the installation process, because I can't connect via VNC or Filezilla, the registering of the rfid-cards sounds wild.

I hope I can learn it within the next few days, but a working desktop install would be highly appreciated. I admit I'm rather a desktop person. :-)

But anyway, thanks a lot so far for figuring out what the problem is. ;-) What a great and helpful community.

1 reply

mag-1sm Feb 23, 2024
Author

Just a final remark from me:
As mentioned before I installed Lite and was very happy to discover, that the access via a remote device still opens the phoniebox page I was used to. And when I finally read that the Hotspot only activates itself if it can't find the fitting wifi (that's why I couldn't see anything at home) I managed to assign the RFIDs - which in my case are outdoors.
Now everything is working just like before and as it should. :-)

Thanks again for immediately providing such useful information and help to find the bug.

olbasoil · 2024-02-19T22:17:07Z

olbasoil
Feb 19, 2024

I've also been struggling without vnc because there's nothing on the Pi to connect to, but I found winscp is a good sftp client.

…

On Mon, 19 Feb 2024, 21:56 mag-1sm, ***@***.***> wrote: Uh. After an install of the lite version I finally get the startup sound, so it seems to be working. But apart from that everything else seems to become way more complicated. Apart from the fact that I must have done something wrong during the installation process, because I can't connect via VNC or Filezilla, the registering of the rfid-cards sounds wild. I hope I can learn it within the next few days, but a working desktop install would be highly appreciated. I admit I'm rather a desktop person. :-) But anyway, thanks a lot so far for figuring out what the problem is. ;-) What a great and helpful community. — Reply to this email directly, view it on GitHub <#2267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKVCV3ZQPYTQNGHKUGHEL5DYUPDAFAVCNFSM6AAAAABDOLTDOGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKMRSGQ3TG> . You are receiving this because you commented.Message ID: ***@***.*** com>

3 replies

AlvinSchiller Feb 19, 2024
Collaborator

Yes, VNC can't work without a UI.
I use winscp too, with putty extension. So you can access the filesystem and also have a ssh terminal access.
That should be sufficient to manage the phoniebox ^^

Filezilla should also work with the right settings i suppose, but don't have any experience.

PS: The installation also creates a samba share, so the shared folder can be accessed via network too (like Windows Explorer, ...)

edednedy Feb 22, 2024

I've been fighting this exact same problem. I have installed and reinstalled multiple times. I'll be completely lost without a desktop. But on one of my desktop installs the player did work, so it must be a setting that you choose during installation, probably something to do with the headphone.

AlvinSchiller Feb 22, 2024
Collaborator

I've been fighting this exact same problem. I have installed and reinstalled multiple times. I'll be completely lost without a desktop. But on one of my desktop installs the player did work, so it must be a setting that you choose during installation, probably something to do with the headphone.

Can you have a look at #2267 (reply in thread) and test this, if the "desktop" version is mandatory for you?

edednedy · 2024-02-22T21:10:26Z

edednedy
Feb 22, 2024

I'm not at all familiar with using a terminal window, so I tried the simplest thing first.

$ sudo nano /usr/share/alsa/alsa.conf
Now replace the lines near the end of the file:

defaults.ctl.card 0
defaults.pcm.card 0

with:

defaults.ctl.card 1
defaults.pcm.card 1

And much to my surprise, that's all it took. Working with sound now and still have desktop environment.
Much thanks AlvinSchiller

0 replies

Sound is generally working, but not in the Phoniebox #2267

Replies: 13 comments · 24 replies

mag-1sm Feb 18, 2024 Author

s-martin Feb 18, 2024 Collaborator

s-martin Feb 18, 2024 Collaborator

mag-1sm Feb 18, 2024 Author

mag-1sm Feb 18, 2024 Author

s-martin Feb 18, 2024 Collaborator

mag-1sm Feb 18, 2024 Author

AlvinSchiller Feb 18, 2024 Collaborator

mag-1sm Feb 18, 2024 Author

AlvinSchiller Feb 19, 2024 Collaborator

AlvinSchiller Feb 19, 2024 Collaborator

AlvinSchiller Feb 19, 2024 Collaborator

AlvinSchiller Feb 19, 2024 Collaborator

mag-1sm Feb 19, 2024 Author

AlvinSchiller Feb 19, 2024 Collaborator

AlvinSchiller Feb 19, 2024 Collaborator

mag-1sm Feb 19, 2024 Author

AlvinSchiller Feb 19, 2024 Collaborator

AlvinSchiller Feb 22, 2024 Collaborator

s-martin Feb 22, 2024 Collaborator

mag-1sm Feb 19, 2024 Author

mag-1sm Feb 23, 2024 Author

AlvinSchiller Feb 19, 2024 Collaborator

AlvinSchiller Feb 22, 2024 Collaborator

Replies: 13 comments 24 replies

mag-1sm
Feb 18, 2024
Author

s-martin
Feb 18, 2024
Collaborator

s-martin Feb 18, 2024
Collaborator

mag-1sm Feb 18, 2024
Author

mag-1sm
Feb 18, 2024
Author

s-martin Feb 18, 2024
Collaborator

mag-1sm Feb 18, 2024
Author

AlvinSchiller
Feb 18, 2024
Collaborator

mag-1sm Feb 18, 2024
Author

AlvinSchiller Feb 19, 2024
Collaborator

AlvinSchiller Feb 19, 2024
Collaborator

AlvinSchiller Feb 19, 2024
Collaborator

AlvinSchiller Feb 19, 2024
Collaborator

mag-1sm Feb 19, 2024
Author

AlvinSchiller Feb 19, 2024
Collaborator

AlvinSchiller
Feb 19, 2024
Collaborator

mag-1sm Feb 19, 2024
Author

AlvinSchiller Feb 19, 2024
Collaborator

AlvinSchiller Feb 22, 2024
Collaborator

s-martin Feb 22, 2024
Collaborator

mag-1sm
Feb 19, 2024
Author

mag-1sm Feb 23, 2024
Author

AlvinSchiller Feb 19, 2024
Collaborator

AlvinSchiller Feb 22, 2024
Collaborator