FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Kubuntu Development

 
 
LinkBack Thread Tools
 
Old 12-02-2007, 07:45 AM
Luka Renko
 
Default Bightness laptop keys regression in gutsy (bug 145337)

Posting this to kubuntu-devel@, so that other people can participate.

On Thursday 29 November 2007 12:51:17 you wrote:
> I'm no KDE expert but if you can tell me which KDE files should be looked
> at I would be glad to help sort the Brightness keys problem of Bug 145337.
> This is a serious bug for many laptop users because we can't recover from
> suspend when using KDE. Everything works fine in Gnome though. So it could
> be just a matter of copying a few lines from Gnome into KDE.

Yes, the test packages I have prepared for thsi bug [1] did not work, which
was a suprise for me, as other keys (for example battery key on my HP
laptop), works by using more or less the same method. Test binaries for gutsy
are in my PPA [2] and source of the changes is here [3], but as already
confirmed by several people, they do NOT work. As I do not have appropriate
HW to test, it is a bit hard to debug this further.

Why regression in gutsy: because brightness keys were handled completely in
the kernel before, but with gutsy kernel this have changed. Proper fix was
done for gnome-power-manager (just before gutsy release), but not for
Kubuntu/KDE.


How do we handle laptop keys in Kubuntu:

1. Linux kernel ensures proper keycode assignment for all laptops

2. Kubuntu maps known keycodes to xkeysym
This is done by Xsession script [4], which uses mappings defined in xmodmap
file [5].

3. kmilo sets KGlobalAccel actions for xkeysym
Some actions are performed by kmilo (lock screen, eject CD...), while others
are communicated to other processes via dcop.

In the case of brightness keys, we have added the mappings and changed kmilo
to call appropriate dcop calls (as confirmed in bug [1]), but this does did
not work.


What can go wrong here:

1. Kernel does not generate the keycode
Not the case, as "xev" command shows keypress and keycode.

2. Mapping to xkeysym does not work
Not the case, as "xev" shows appropriate xkeysym after mapping

3. kmilo KGlobalAccel does not catch xkeysym action
Very hard to debug, but we could test different mappings just to check if
there are some limitations on which xkeysym work.

4. kmilo dcop call to guidance-power-manager does not get through
dcop calls work when tested, but it may be that they cannot be delivered for
some reason. Probability is low, as similar dcop work on my laptop for
battery key (just different xkeysym and dcop call).

In order to debug this furher, I would first focus on point 3. I will write
some debugging ideas on separate e-mail.

Regards,
Luka


[1] https://launchpad.net/bugs/145337
[2] https://edge.launchpad.net/~lure/+archive
[3] http://people.ubuntuwire.com/~lure/bug145337
[4] /etc/X11/Xsession.d/80ubuntu-xmodmap
[5] /usr/share/apps/kxkb/ubuntu.xmodmap

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 12-02-2007, 08:06 AM
Luka Renko
 
Default Bightness laptop keys regression in gutsy (bug 145337)

On Sunday 02 December 2007 09:45:20 Luka Renko wrote:
> 3. kmilo KGlobalAccel does not catch xkeysym action
> Very hard to debug, but we could test different mappings just to check if
> there are some limitations on which xkeysym work.
....
> In order to debug this furher, I would first focus on point 3. I will write
> some debugging ideas on separate e-mail.

How to manually test this with brightness keys on your laptop:

1. Manually assign keycode
In Konsole, execute the following commands:
xmodmap -e 'keycode 101 = XF86LaunchD'
xmodmap -e 'keycode 212 = XF86LaunchE'

2. Assign some KDE global shortcuts
- start System Settings
- go to "Keyboard & Mouse", select "Keyboard Shortcuts" section
- in "Shortcuts Schemes", check that you are in "Global Shortcuts" tabe
- find "Maximize Window" action (in "Windows" section)
- select it and in the bottom of screen select "Custom" or click on button
with "None" label
- dialog will open, now press appropriate brightness key (up or down)
- XF86LaunchD or XF86LaunchE should be entered
(if not, check step 1.)
- click "Apply" button

3. Test newly assigned key
- ensure that you have one window set as current
- press assigned key -> window should maximize

If the first key works, please repeat step 2. and 3. with the second
brightness key, to test both xkeysym assignments.
When I get some reports (positive or negative), we can debug this further.

You can also try to reach me on IRC in #kubuntu-devel - just ping Lure.

Regards,
Luka

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 

Thread Tools




All times are GMT. The time now is 07:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org