[+CC: dunz0r; tried to help me out on IRC with the same]
On Fri, Oct 21, 2011 at 6:46 PM, Julien Danjou jul...@danjou.info wrote:
I just hit a bad bug. awesome would not start!
Oh my! Truck load of thanks JD :). I had been a victim of the same
since the last 2-3 days. Tried to debug it, but was
Hi,
I just hit a bad bug. awesome would not start!
I discovered that this was caused by obvious. I use the volume_alsa
widget, which runs amixer. But I had pulseaudio installed. And doing a:
xtrace amixer -c 0 -- get Master
showed that the pulseaudio plugin of alsa was run and tried to
On Fri, Oct 21, 2011 at 03:16:40PM +0200, Julien Danjou wrote:
Removing pulseaudio resolved the problem for now, but I think we should
do something in obvious to avoid that, like unsetting the DISPLAY
environment variable.
Why not simply defer the first update of the widget to give awesome a
On Fri, Oct 21 2011, Daniel Silverstone wrote:
On Fri, Oct 21, 2011 at 03:16:40PM +0200, Julien Danjou wrote:
Removing pulseaudio resolved the problem for now, but I think we should
do something in obvious to avoid that, like unsetting the DISPLAY
environment variable.
Why not simply defer
On 21.10.2011 15:16, Julien Danjou wrote:
I just hit a bad bug. awesome would not start!
I discovered that this was caused by obvious. I use the volume_alsa
widget, which runs amixer. But I had pulseaudio installed. And doing a:
xtrace amixer -c 0 -- get Master
showed that the
On Fri, Oct 21 2011, Uli Schlachter wrote:
@jd: Are you on the 3.4 branch or is your git clone just too old? Did I break
your config badly enough to make you switch to 3.4? :-)
Yeah, I'm on 3.4 for a long time now. :)
--
Julien Danjou
pgpuD11oBLIWw.pgp
Description: PGP signature
On Fri, Oct 21, 2011 at 04:11:01PM +0200, Uli Schlachter wrote:
[...]
That problem is relatively common. I only ever saw it happening due to
pulseaudio.
In other news, you have a great timing. Let's look at the recent git history
for
the master branch:
[...]
[...]
To make this
