-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{pipewire,alsa-ucm-conf}: UCM profiles don't get loaded nor detected #390939
Comments
What does |
Nonworking:
Working:
I don't see anything correlating to the device here. But I can confirm it is working. (in the second example) |
Run it with |
Ok! Non-Working:
Working:
|
That smells like a kernel bug to me, but I'll run it by upstream. |
Can you try staging-next? It has Pipewire 1.4.1, which may fix this. |
@K900 |
Try staging-next first. |
I already did a patch yesterday to Pipewire 1.4.1 (tried yesterday with same results unfortunately) |
So is your first log from 1.4.0 or 1.4.1? |
1.4.0, but they are pretty much the same |
They are not, 1.4.1 contains fixes that may be relevant to your issue. Can you please try staging-next? |
Build will take quite some while |
This is the output now:
And the device seems to work. So the current workaround is just going back to the working commit and wait for nixpkgs-next to merge into unstable? Or is there any way to get pipewire merged earlier to resolve this bug? |
You can run your system off staging-next for now, and then switch back to unstable when it's merged. There are no known major regressions on staging-next currently. |
Ok, will do that then. Is there a timeline for merge? |
Whenever Hydra is done rebuilding things. |
Perfect! Thank you for the help! |
Nixpkgs version
Describe the bug
When updating to #7b73ac5f5a08743fb72c0f474fe13c7acdc4e632 the UCM recognition and application is not working anymore. When rolling back to #8ed2c5f96192addbf8e83dff1080df7ba2c15ca9 the System works as expected.
Steps to reproduce
Expected behaviour
Device is getting acknowledged and registered with the UCM rule.
Screenshots
I uploaded one log of the working edition and one of the nonworking to compare. Logs are too long to insert into the log output further down.
Relevant log output
Additional context
nonworking-log.txt
working-log.txt
System metadata
"x86_64-linux"
Linux 6.12.18, NixOS, 25.05 (Warbler), 25.05.20250310.7b73ac5
yes
yes
nix-env (Nix) 2.24.12
/nix/store/q2vsi5rvgnk8127l3ir706g29gninj7n-source
Notify maintainers
@Kranzes @K900 @roastiek
Note for maintainers: Please tag this issue in your pull request description. (i.e.
Resolves #ISSUE
.)I assert that this issue is relevant for Nixpkgs
Is this issue important to you?
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: