Debian User Forums

This is definitely possible to make work - I'm using Allegro for such stuff myself, and there it's as easy as first drawing the OpenGL, then restoring your transforms and projection_transforms and render_state, and then you can simply draw using allegros primitives or whatever.

An example (minorly edited version of allegro example ex_opengl - https://github.com/liballeg/allegro5/blob/master/examples/ex_opengl.c ), I have a al_draw_rectangle close to the bottom of the main loop that is drawn ...

I take that back, it have not solved the problem for me.

I actually might have found a solution - See shamaks post here:

viewtopic.php?p=790227&sid=f507e4270719 ... 01#p790227

Remove your user from the audio group - might seem counter-intuitive, but it seems to work for me.

Thanks shamak!

See https://github.com/canonical/lightdm/issues/213 for the upstream issue.

I have no solution, but also run into this problem myself.

viewtopic.php?t=156287

or simply check so that gives
in the version field.

Do you use wifi or only cabled internet? This could be a regression in wifi drivers in the linux kernel, which is fixed in bookworm-updates - see

https://lists.debian.org/debian-stable- ... 00002.html

for what to add to sources.list to get the update and install this linux update.

I had done an upgrade to Debian 12.3 over the weekend and I only saw the post about not upgrading to 12.3 yesterday. I think the problem was related to some issue with the 12.3 update messing up the file system. I did another update today and now my system is 12.4. My question is does upgrading to 12.4 fix the problem for people who did the 12.3 update. In other words do I have anything to worry about?

The file system problems were present in the kernel update included in the Debian 12.3 ...

The thing is that this behaviour (of lowering the volume each reboot/user switch) is new for bookworm - it wasn't the case in bullseye, but came after the upgrade.

/var/lib/alsa/asound.state (or whatever file you specify with the -f flag)
is used to store current settings for your soundcards. The settings include
all the usual soundcard mixer settings. More importantly, alsactl is capa‐
ble of controlling other card-specific features that mixer apps usually
don't know about.

The configuration file is generated automatically by running alsactl store.
Editing the configuration file by hand may be necessary for some soundcard
features (e.g ...

You can directory accessed to both users and to save my_asound.conf in it. For example. /home/common.

sudo mkdir /home/common
sudo chown nobody:nogroup /home/common
sudo chmod 775 /home/common

and to add both users in nogroup.


It isn't the permissions of the file (or the folder containing) my_asound.conf that is the problem, but files that alsa needs to access to change the config - look at the error message I posted:

alsa-lib main.c:844:(execute_sequence) exec '/bin/rm -rf /var/lib ...

And it still doesn't work - it's not the permissions of my local "my_asound.state" that is the problem (that is fixable), but the alsa config. See the result:

peter_irich wrote: 2023-10-08 06:48 It is right use asound.state in own directory, for example,

Code: Select all

/usr/bin/alsactl store N -f ~/my_asound.state

Ah, alright, now I follow. Still, it needs to be writable by both users. (which of course is doable).

peter_irich wrote: 2023-10-07 19:25 In UbuntuI I not need sudo to run alsactl, for example,

Code: Select all

/usr/sbin/alsactl dump-cfg

works from user.

Well, you don't need root/sudo for that in Debian either (which is the topic for this forum), but writing/changing config is a different thing from reading the config.

Also - this wasn't necessary before the Bookworm upgrade (The part turning off the soundcard for the user switching from, and then turning it on for the user switching to was, but not setting the sound volume, this is new for Debian 12).

No, call it with full path: /usr/sbin/alsactl. And it is possible to create desktop-file in ~/.config/autostart by hands.


That won't work running without root/sudo:

alsa-lib main.c:844:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1)

Also - this (if working) would solve the problem on login, but not when switching between users already logged in (using the Ctrl+Alt+F7/F8 maneuver). I do loose the volume when switching between users too, but it is a ...

None1975 wrote: 2023-10-06 11:41

gusnan wrote: 2023-10-05 18:41 Thanks! - that is indeed a good workaround. Now I just need to find out a good way to do this automatically on login

Hello. Try using xfce auto starting mechanism.

Thanks - will that be able to handle running as root/using sudo? alsactl is unfortunately not runnable as a normal user.

And the diff on the configs for anybody interested:

--- my_asound_low.state 2023-10-05 20:51:59.394607647 +0200
+++ my_asound.state 2023-10-05 20:34:23.012178920 +0200
@@ -52,10 +52,10 @@
control.5 {
iface MIXER
name 'UMC204HD 192k Output Playback Volume'
- value.0 104
- value.1 104
- value.2 104
- value.3 104
+ value.0 127
+ value.1 127
+ value.2 127
+ value.3 127
comment {
access 'read write'
type INTEGER
@@ -63,10 +63,10 @@
range '0 - 127'
dbmin -12700
dbmax 0
- dbvalue.0 -2300 ...

Thanks! - that is indeed a good workaround. Now I just need to find out a good way to do this automatically on login

I have a USB Sound interface Behringer UMC204HD, and on every morning system startup I need to go to alsamixer, select the UMC204HD sound card and increase the volume. This sticks until reboot or user switch (logging in as another user on X), when it is down again (to 41 of 100, alsamixer also says -23dB gain) on Line A, Line B, "UMC204HD 192k Output Front" and "UMC204 192k Output Rear".

Does anybody else see this? And does anyone have a solution?

This is on Debian 12, standard kernel ...

I don't know about the specifics in this case, but also look on the git tags - You can see that 247.3-7+deb11u1 was tagged Aug 7 - and if I see correctly it looks like a 247.3-7+deb11u2 hasn't been tagged yet .

My personal workflow is update the changelog, do the commit, and then upload (which could be way later). But then wait until the upload actually was accepted into the Debian archive, and only tag the commit when the upload was accepted which could be even later again.