Hi dotancohen:
I'm really not sure on the KDE packages, I don't use KDE personally. I
would mark it against the kubuntu project and let the triagers handle it if
you're not sure either.
On Wed, Nov 5, 2008 at 12:07, dotancohen <[EMAIL PROTECTED]> wrote:
> Thanks, Mario, what are the appropriate
Here is the KDE bug:
https://bugs.kde.org/show_bug.cgi?id=174359
--
[regression] Hardware buttons no longer work in 8.10
https://bugs.launchpad.net/bugs/281981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks, Mario, what are the appropriate KDE packages? Here is my output,
for reference:
Outer window is 0x2a1, inner window is 0x2a2
PropertyNotify event, serial 8, synthetic NO, window 0x2a1,
atom 0x27 (WM_NAME), time 5284535, state PropertyNewValue
PropertyNotify event, serial
Please re-open a bug against the appropriate KDE 4.1 packages and in
there add that information about the keypresses showing the right
keysyms.
--
[regression] Hardware buttons no longer work in 8.10
https://bugs.launchpad.net/bugs/281981
You received this bug notification because you are a membe
So this shows that the keys are properly putting out the right keycodes.
It's a KDE specific problem then.
On Wed, Nov 5, 2008 at 09:22, mickru <[EMAIL PROTECTED]> wrote:
> Here is the data from my Dell XPS M1210:
>
> KeyPress event, serial 31, synthetic NO, window 0x501,
> root 0x1a6, su
Here is the data from my Dell XPS M1210:
KeyPress event, serial 31, synthetic NO, window 0x501,
root 0x1a6, subw 0x0, time 21635300, (-16,592), root:(1068,741),
state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen
YES,
XLookupString gives 0 bytes:
XmbLoo
mickru and dotcohen:
If your buttons aren't working properly, can you please run "xev" in a
terminal, press them and paste the output here? It's possible (and
likely) the buttons are properly mapped, just KDE4 doesn't know what it
should be doing with them.
--
[regression] Hardware buttons no l
For me the buttons do not work either ... They used to work under KDE
3.5.xx
Kubuntu 8.10
KDE 4.1.2
Date: 2008-11-5
Hardware: Dell XPS M1210
--
[regression] Hardware buttons no longer work in 8.10
https://bugs.launchpad.net/bugs/281981
You received this bug notification because you are a member
Not on my system, with KDE 4.1 on Kubuntu 8.10. Dell Inspiron E1505 /
6400. Reopening.
** Changed in: hal-info (Ubuntu)
Status: Fix Released => Confirmed
--
[regression] Hardware buttons no longer work in 8.10
https://bugs.launchpad.net/bugs/281981
You received this bug notification becau
The buttons work today...
--
[regression] Hardware buttons no longer work in 8.10
https://bugs.launchpad.net/bugs/281981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
This bug was fixed in the package hal-info - 20081013-0ubuntu2
---
hal-info (20081013-0ubuntu2) intrepid; urgency=low
* Add 02_dell_stop_key.patch
- Fixes the "Media" stop key to map properly to media
stops rather than cancel. (LP: #281981)
-- Mario Limonciello <[EMAIL P
There is a bug regarding the stop button that i'll fix. If you have
problems after this hal-info upload and have everything else up to date,
open this bug back up.
** Changed in: hal-info (Ubuntu)
Sourcepackagename: linux => hal-info
--
[regression] Hardware buttons no longer work in 8.10
https
I have more or les identical harware, and just discovered the same issue
(Dell XPS M1710 laptop, same soundcard and same media buttons).
I'd like to add that it worked only a few days ago. The issue is likely
with a relatively new kernel. Assigning to kernel.
** Changed in: linux (Ubuntu)
Sourcep
[EMAIL PROTECTED]:~$ aplay --list-devices
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0
14 matches
Mail list logo
