Issue is fixed, kmilo now receives fakekey-events and forwards to
guidance-power-manager by a dcop call. guidance uses dbus in order to
tell hald to actually change brightness.
changelog entry:
kdeutils (4:3.5.8-1ubuntu7) hardy; urgency=low
* debian/patches/kubuntu_14_kmilo_powermanager.diff:
Added Brightness Down & Up key actions (DCOP call to Guidance
Power-Manager). Fixed all DCOP calls to recent change of
application top level name (power-manager -> guidance).
-- Luka Renko < [EMAIL PROTECTED]> Sun, 10 Feb 2008 20:45:42 +0100
Workaround for gutsy:
edit scripts in /etc/acpi to use dcop-calls instead of acpi_fakekey.
the dcop-commands by luka renko sometimes don't work until acpid is manually
restarted (dcop can't attach to server).
the following calls work better as i see it:
dcop --all-sessions --all-users power-manager-`ps ax|grep -m 1 guidance|awk '{
print $1 }'` power-manager brightnessUp
dcop --all-sessions --all-users power-manager-`ps ax|grep -m 1 guidance|awk '{
print $1 }'` power-manager brightnessDown
I think this bug could now be closed.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
