Re: 16-CURRENT non root users unable to use sound/beep anymore after upgrade to a4ed783cee2a
- Reply: Sulev-Madis Silber : "Re:_16-CURRENT_non_root_users_unable_to_use_so und/beep_anymore_after_upgrade_to_a4ed783cee2a"
- In reply to: Mark Millard : "Re: 16-CURRENT non root users unable to use sound/beep anymore after upgrade to a4ed783cee2a"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 22 Jun 2026 18:03:40 UTC
Jun 22, 2026 19:48:04 Mark Millard <marklmi@yahoo.com>: > On 6/22/26 03:04, polyduekes@proton.me wrote: >> On Monday, June 22nd, 2026 at 2:54 PM, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote: >> >>> On Mon, 22 Jun 2026 06:23:36 +0000 >>> polyduekes@proton.me wrote: >>> >>>> has something been recently changed in regards to user permissions for /dev/dsp,i updated my 16-current system after some days and am noticing that now a non root user which was able to access /dev/dsp and play sound is now unable to do so and fails with Failed to open '/dev/dsp': Permission denied >>> >>> You'll need to add the user who need to access audio devices >>> to recently added audio group (gid=43) just like you'll be doing >>> for X11/Wayland screens for video (gid=44) group. >>> >>> IIRC, audio group is added to stable/15, too, but switches for >>> audio device to audio group is NOT merged not to violate POLA. >>> >>> This is described in /usr/src/UPDATING at the entry dated 20260521. >>> https://cgit.freebsd.org/src/tree/UPDATING#n42 >>> >>> Please habitally confirm UPDATING. I believe it should be >>> a good habit. >>> >>> Regards. >>> >>> >>> -- >>> Tomoaki AOKI <junchoon@dec.sakura.ne.jp> >>> >> sorry i forgot to clarify properly,i didn't anticipate a failed merge of /etc/group by pkg during upgrade, i had checked the available groups after upgrade but audio group wasn't available due to the failed merge(at that point i wasn't aware the merge failed) so i assumed it wasn't the problem >> >> thanks for the reminder about UPDATING entries,they slipped my mind >> >> > > I could imagine that, for now, it would be good if, at the very end of > its output, pkg upgrade or pkg install reported on how many *.pkgnew > files and/or *.pkgsave files had been had been generated, at least when > the number is positive. It would prompt to investigate. > +1 on the warning at the end of the pkg session!