You are not logged in.
So, I have been using volumeicon to manage my volume
I use this in my I3 config to load it.
exec_always --no-startup-id volumeiconSo, when I first boot up, there is no icon in the i3bar, and to get the icon I need to restart the WM and then the icon comes. But when I restart the WM with the icon still there, I get two icons instead of only one.
Here is the screenshot
https://i.imgur.com/KDSpr5s.png
Last edited by NoodlesWeAte (2022-06-07 13:14:59)
Offline
Ain't ya supposed to fork it?
Offline
fork? Sorry, i didn't get it
Offline
Try without 'always' and adding a delay
exec --no-startup-id sleep 1 && volumeiconMaybe I'm not saying it right..
I mean
exec_always --no-startup-id volumeicon &The "&" forks it into the background.
Offline
It didn't work,
Offline
Try without 'always' and adding a delay
exec --no-startup-id sleep 1 && volumeicon
No it didn't work
Offline
Forking is irrelevant - i3 forks before calling the exec function internally. Adding a sleep is also irrelevant as the commands are not run until i3 is ready anyways. There should also be no need for --no-startup-id as volumeicon is a gtk3 program - though this is harmless.
But rather than randomly throwing other things at the command, collect some diagnostics. Go back to a simple / proper `exec volumeicon` and check for any error output from i3. Depending on how you start i3 this may be in your xorg log (i.e., if you use startx / xinit and don't redirect the logs). Post the logs here. Then you can also try logging the output of volumeicon itself with `exec volumeicon >~/volumeicon.log 2>&1` and sharing the created volumeicon.log after a restart of i3 that results in no volume icon being displayed.
Also please post the output of `env | grep -i dbus` and describe how you start X (and share any xinitrc or other relevant startup files).
Additionally posting your complete i3 config may be helpful.
EDIT: the post below is most likely the cause - this could be confirmed by checking error output as noted.
Last edited by Trilby (2022-06-07 17:13:00)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Maybe volumeicon doesn't start correctly when pulseaudio/pipewire is configured for socket activation.
To combat that you could first run "pactl info" first or simply enable the pulseaudio/pipewire user services.(systemctl --user enable ...)
Personally I use pa-applet-git. (AUR)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Volumeicon does not work wel with pipewire.... If you manual start volumeicon after i3 start, there is gonna be OK.... Only solution I found is to play "some startup sound" before starting volumeicon, than volumeicon works well...
In my startup script in Qtile was something like this:
espeak "random text"
volumeicon &You can play some sound like XP startup sound, hahahhaha... than start volumeicon.... Or just use pa-applet.
Last edited by Pyntux (2022-06-07 18:16:41)
I do not speak English, but I understand...
Offline
dogknowsnx wrote:Try without 'always' and adding a delay
exec --no-startup-id sleep 1 && volumeiconNo it didn't work
Try and increase the delay (5 seconds) in order for the audio server to be fully loaded before 'volumeicon' starts...
Considering that 'volumeicon' hasn't been updated in almost two years, looking for a replacement is probably the way to go...
Last edited by dogknowsnx (2022-06-08 10:08:20)
using simple exec volumeicon worked for me.
thnx
Offline
Please remember to mark solved topics by prepending [SOLVED] to the title...