-
Notifications
You must be signed in to change notification settings - Fork 25
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
[BUG] Volume issues #24
Comments
Do you have pactl (pulseaudio) installed? |
Yes |
does |
|
It seems like your audio controller doesn't report a node.name. This is really weird and I wonder if it also happens to headphones? Can you post what |
Just spits out "No valid command specified." |
I think your pactl is broken or something? For me it reports the current sink. |
No, it works fine. Probably just different versions. Server String: /run/user/1000/pulse/native |
Yeah just checked, the get-default-sink command is part of pulseaudio v15+ and I'm on v13.99.1 |
Does it work once you update? |
13.99.1 is the latest PPA for pulse audio on ubuntu. I don't want to go and mess around with trying to upgrade it myself. |
I guess pulseaudio-utils or pipewire-pulse uses a higher version then because I'm running my stock repos from 22.04 Pop!_OS |
Can you use this snippet instead or add in a check for the get-default command failing and use this if so?
|
Yes I will add it |
Did that fix the problems you had? |
No unfortunately not volume_controller line 58 attempt to concatenate a nil value (upvalue 'node') |
Hi, I also encounter the same problem, My laptop is rather new(ASUS UM3402YA), the audio is currently unavailable. I am using the arch disro to install the theme. And my speaker work at native Debian with KDE installed. (Decide to change cuz I want latest kernel). I followed existing discuss to print out the info:
When I click the audio widget, it also say |
Update: It might my driver issue, I found that some one else encounter speaker issue from stackExchange. |
The problem is that neither of you got a |
I switched hdmi to speaker using gnome, and then login awesomewm, it was okay. |
Pinging. Did this bug ever get resolved ? I was thinking of trying this theme Desktop but just looking over everything first! |
Well yeah in the dev branch, I planned on adding a shit ton of stuff and rewriting most things but never got to finish it and I'm not using awesome anymore. If anyone wants to merge something feel free to open a PR but I probably won't make anything in the near future |
What window manager do you use these days ? i'm curious! |
KDE, mostly because of wallpaper engine and It's easy to theme, it just works and gnome breaks too often. I'm looking forward to CosmicDE from pop os |
I just stopped using awesome today and went back to i3 I'm going to learn it and not just copy stuff lol |
Trying to change my volume via the keyboard resulted in 'ERROR attempt to compare number with nil'. I soon noticed from the top bar's volume button that I don't have an output device selected which is likely the problem. However trying to select the only output device in the list resulted in 'ERROR .config/awesome/src/modules/volume_controller.lua:58: attempt to concatenate a nil value (upvalue 'node')
The text was updated successfully, but these errors were encountered: