Volumeicon not starting from within autostart

cloverskull · 2016-06-26 22:56:39

Hey guys,

I followed johnraff's guidance to replace volti with volumeicon. I have done this on multiple installations of BL on various hardware. Now, I have most recently done it on a MacBook Pro 11,5. Manually starting volumeicon works fine. Starting it in autostart, even as the final item with a 30 second delay, does not cause it to auto start. How should I go about troubleshooting this?

Thanks!

hhh · 2016-06-26 23:07:31

Post your autostart file and wrap it in code tags, please.

cloverskull · 2016-06-27 18:23:06

Disregard, it works if I set it to 30 seconds. I had it set to 20 seconds and it wasn't working. Still, 30 seconds to start volumeicon seems a bit much...

Head_on_a_Stick · 2016-06-27 18:43:47

cloverskull wrote:

it works if I set it to 30 seconds

Really?

I never put any `sleep`s in my autostart files and volumeicon always works as expected.

Could you post your complete file please?

I will see if I can reproduce this.

cloverskull · 2016-06-27 22:39:28

Yep will do. I'm at work so can't until later. It's on a MBP so it could be some goofy hardware issue. I also updated asound stuff, if memory serves, so I'll have to go through my bash history (fairly new installation) and see what all I've done.

That said, I seem to recall a few people having issues with volumeicon not working unless an absurdly long sleep period is prepended to launching it.

johnraff · 2016-06-28 07:12:54

I can confirm that volumeicon needs a good sleep before being got out of bed. On this machine (4x3.2GHz Intel i3) every so often it fails to start and I increase the sleep a little. At the moment it's at 12s and we'll see if that's enough...

cloverskull · 2016-06-28 17:49:26

Drat, forgot to update the thread with my configuration contents. All the same, I wonder if there is a bug in volumeicon somewhere.

@johnraff - any brainstorm ideas how to redirect the volumeicon launch into a log file, to see what's causing hiccups during autostart? I'll see if anyone is tracking bugs in volumeicon itself.

damo · 2016-06-28 18:08:03

cloverskull wrote:

....
@johnraff - any brainstorm ideas how to redirect the volumeicon launch into a log file, to see what's causing hiccups during autostart? I'll see if anyone is tracking bugs in volumeicon itself.

Anything in '~/.xsession-errors'?

Head_on_a_Stick · 2016-06-28 18:11:58

OK, this is interesting...

Just tried removing all the `sleep`s in the autostart file:
https://gist.github.com/Head-on-a-Stick … 8c410eaf4d

volumeicon fails to start with this error:

volumeicon: alsa_backend.c:86: asound_get_volume: Assertion `m_elem != ((void *)0)' failed.

Let me fiddle some more...

EDIT: https://forums.bunsenlabs.org/viewtopic … d=628#p628

EDIT2: `sleep 2s` works in my system, no errors now

https://gist.github.com/Head-on-a-Stick … 6f685f0653

Last edited by Head_on_a_Stick (2016-06-28 18:12:36)

cloverskull · 2016-06-28 18:24:05

Interesting. Old volumeicon bug listed as fixed here: https://github.com/Maato/volumeicon/issues/6

However the suggestion is to blacklist pcspeaker. I think that may be a red herring.

Perhaps the full alsa/pulse stack hasn't been completely instantiated by this point? Is there a way to test?

#1 2016-06-26 22:56:39

Volumeicon not starting from within autostart

#2 2016-06-26 23:07:31

Re: Volumeicon not starting from within autostart

#3 2016-06-27 18:23:06

Re: Volumeicon not starting from within autostart

#4 2016-06-27 18:43:47

Re: Volumeicon not starting from within autostart

#5 2016-06-27 22:39:28

Re: Volumeicon not starting from within autostart

#6 2016-06-28 07:12:54

Re: Volumeicon not starting from within autostart

#7 2016-06-28 17:49:26

Re: Volumeicon not starting from within autostart

#8 2016-06-28 18:08:03

Re: Volumeicon not starting from within autostart

#9 2016-06-28 18:11:58

Re: Volumeicon not starting from within autostart

#10 2016-06-28 18:24:05

Re: Volumeicon not starting from within autostart

Board footer