[11:27] <ali1234> when i plug in my webcam the output volume on my soundcard changes. how can i debug this?
[11:28] <ali1234> /lib/udev/rules.d/90-alsa-restore.rules looks like a good place to start
[12:14] <ali1234> found it. the udev rule is actually broken
[12:15] <ali1234> RUN+="/usr/sbin/alsactl nrestore $attr{number}" - but $attr{number} is unset here, so it restores the volume on all cards instead
[13:38] <ali1234> bug 1268301
[13:38] <ubot2> Launchpad bug 1268301 in alsa-utils (Ubuntu) "udev alsa restore restore rules are broken" [Undecided,New] https://launchpad.net/bugs/1268301
[21:41] <YOURBESTFRIEND> hello?
[21:42] <YOURBESTFRIEND> I'm trying to fix some bug
[21:43] <YOURBESTFRIEND> I need help
[21:59] <YOURBESTFRIEND> this is the channel for One Hundred Papercuts, right?
[23:02] <ochosi> robert_ancell: ping
[23:03] <robert_ancell> ochosi, hello
[23:03] <ochosi> hey!
[23:03] <ochosi> i quickly wanted to ask you something about lightdm, greeters and powermanagement
[23:04] <ochosi> i would like to set the timeout for the monitor to shut off (dpms off) to a lower value if lock_hint=true
[23:04] <ochosi> is there a sensible way to implement that on the greeter-level, or is it something that would have to go in lightdm?
[23:04] <robert_ancell> it would have to be in the greeter level
[23:05] <ochosi> ok
[23:05] <ochosi> i haven't really looked into setting these kind of settings yet, so far i've only managed to force it to blank
[23:05] <robert_ancell> there's no code in liblightdm-gobject for this at the moment. If there's an appropriate X api (xrandr?) to wrap we could put some there
[23:05] <ochosi> yeah, haven't really investigated properly
[23:05] <ochosi> i was just wondering whether the greeter *can* even change these kind of X settings
[23:06] <ochosi> (cause this would go through the X11 screensaver extension i guess)
[23:06] <robert_ancell> ochosi, I think you have to use the X idle timer, which means you need some sort of service monitoring it
[23:07] <robert_ancell> service = greeter in this case or gnome-settings-daemon (which is what we do for unity-greeter)
[23:08] <ochosi> the problem i see is: if i change the timeout for X in the greeter (which doesn't seem problematic as long as the greeter is a lockscreen), if someone uses VT8 to log in (while the session in VT7 is locked), they would "inherit" that X setting, no?
[23:08] <ochosi> so their monitor would go into dpms off after 1 minute e.g.
[23:09] <ochosi> or is that assumption mislead because the login/session would reset these values?
[23:12] <robert_ancell> ochosi, each X server would have independent settings
[23:12] <ochosi> yeah
[23:13] <ochosi> but since lightdm opens another X server upon locking, the user logging in there would inherit those settings
[23:15] <robert_ancell> not sure what you mean by inherit, but the session would handle the idle timer for :1 and the greeter for :0 so the behaviour would be set by the greeter and session
[23:17] <ochosi> ok, what i meant is this. active session in vt7 -> lock (i.e. dpms timeout of 1min in greeter on vt8) -> other_user logs in on greeter on vt8 -> session on vt8 still has that timeout of 1min dpms
[23:17] <ochosi> i guess in your case things are really different cause you have the omnipresent gnome-settings-daemon
[23:18] <ochosi> we have xfce-session, which doesn't touch those X idle timer values
[23:18] <ochosi> (and which isn't present in gtk-greeter)
[23:19] <ochosi> robert_ancell: anyway, it's not your problem as i said myself now :) so thanks for the heads-up, i'll try to implement it in gtk-greeter somehow
[23:19] <robert_ancell> cool
[23:19] <robert_ancell> ah, I see what you mean
[23:19] <ochosi> just implemented fake transparency, so i think we can almost emulate the look of unity-greeter ;)