Created attachment 35798 [details] upowerd --verbose output when unplugging the laptop Hi, This is a follow-up for gpm bug #610600 [0] which needs to be re-assigned to upower. When I unplug my laptop, upower doesn't detect the change immediately. It does only happen after 30 seconds, as shown in the output of upowerd --verbose (see attached file): No updates on supply /org/freedesktop/UPower/devices/battery_BAT1 for 30 seconds; forcing update Also see the discussion on the gpm mailing list about this issue [1]. I would be happy to make further tests or test any proposed patches which could solve this issue. Also note this issue still happens with upower 0.9.4. This is on Debian unstable, with an Acer Aspire 1810TZ laptop. Cheers, Julien [0] https://bugzilla.gnome.org/show_bug.cgi?id=610600 [1] http://mail.gnome.org/archives/gnome-power-manager-list/2010-March/msg00000.html
Can you get the --verbose log when using upower 0.9.4 please. Thanks.
Created attachment 35887 [details] upower 0.9.4 verbose output Hi Richard, Here is the requested log. Same as before: - No updates on supply /org/freedesktop/UPower/devices/battery_BAT1 for 30 seconds; forcing update Cheers, Julien
Could you try upower from git master please -- I think it might help. Thanks.
hi, I cannot compile git master. I have a first error in configure: ./configure: line 3062: syntax error near unexpected token `0.6.7' ./configure: line 3062: `GOBJECT_INTROSPECTION_CHECK(0.6.7)' If I remove this line by hand, it seems to work fine, but, then, no Makefile.in are created: config.status: error: cannot find input file: `Makefile.in' $ find . -name Makefile.* ./Makefile.am ./rules/Makefile.am ./etc/Makefile.am ./doc/Makefile.am ./doc/dbus/Makefile.am ./doc/man/Makefile.am ./libupower-glib/Makefile.am ./src/Makefile.am ./src/dummy/Makefile.am ./src/freebsd/Makefile.am ./src/linux/Makefile.am ./policy/Makefile.am ./tools/Makefile.am ./devkit-power-gobject/Makefile.am Any hint? Cheers, Julien
Hi, 0.9.5 is now in Debian, and I see no change compared to the previous release as for my issue. Cheers, Julien
Hi, I have just noticed I'm not hit by this issue any more. The fix is very recent, and the only possibly related update I can think of is that I am testing linux 3.0.0 rc2 I must admit that I haven't been able to test that much, hence I leave this report open for now, will close it later if my tests show it is actually fixed. Cheers, Julien
Closing as per comment 6.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.