On Wed, Jan 11, 2012 at 01:05:06PM +0100, Matthijs Kooijman wrote:
This check might be a bit of a hack right now, but I guess the entire
is process X running, then don't handle the key is in a way. I guess
the perfect solution would be to connect to gnome-settings-daemon and
find out if the
Hi Michael,
Did you look into PowerDevilRunning() in the same file? This function gets the
module information from KDE. I guess the Gnome version could work similarly.
Hmm, I was going to look at that function and then got distracted or
something. Stupid I overlooked that.
Having said that,
On Wed, Jan 11, 2012 at 01:05:06PM +0100, Matthijs Kooijman wrote:
It seems something like this could happen through DBus, but
gnome-settings-daemon is only active on the session bus and I doubt it's
possible to implement this reliably (since you don't know where the dbus
session for the user
Hi Michael,
seems our messages (and patches) crossed paths. From a quick look, my
patch looks more sensible, since it check gnome-settings-daemon, not
UPower (AFAICS the latter only executes the suspend, not triggers it?).
Anyway, let me know what you think.
Gr.
Matthijs
signature.asc
Hi all,
I've applied the patch from Michael, it works well.
Regards,
Igor.
2012/1/11 Matthijs Kooijman matth...@stdin.nl
Hi Michael,
seems our messages (and patches) crossed paths. From a quick look, my
patch looks more sensible, since it check gnome-settings-daemon, not
UPower (AFAICS the
On Wed, Jan 11, 2012 at 05:18:20PM +0100, Matthijs Kooijman wrote:
seems our messages (and patches) crossed paths. From a quick look, my
patch looks more sensible, since it check gnome-settings-daemon, not
UPower (AFAICS the latter only executes the suspend, not triggers it?).
Anyway, let me
6 matches
Mail list logo
