I was redirected here from bug #140652, that is duplicate of this bug. I
have macbook air 2012, and brighness, battery report etc. doesn't work
in KDE, but works in Unity.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in Ubuntu.
KMilo no longer exists in Intrepid/KDE4 - invalidating.
** Changed in: kdeutils (Ubuntu)
Status: In Progress = Invalid
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs,
Doesn't really affect kdebase either, more of a guidance-power-manager
bug, if the bug still exists at all. Does it?
** Changed in: kdebase (Ubuntu)
Status: In Progress = Invalid
** Also affects: guidance-power-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Oh, I see from the comments that this works with guidance-power-manager.
** Changed in: guidance-power-manager (Ubuntu)
Status: Incomplete = Fix Released
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification
Maybe this fix from Dov-El works for you as well? It worked for me, but
I am not on Kde:
The fix is found @ http://www.ubuntu1501.com/2008/04/overview-of-
ubuntu-804-hardy-heron-on.html . and was blogged by aaronmt
(http://www.blogger.com/profile/00032734089773880467).
quote
To fix brightness,
It worked for me (using Gnome) for some months, but now it is broken
again, see bug 105512.
--
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
Will the patch make it to Gutsy's repositories? Or some other solution?
It's weird to close a bug with a workaround of this sort... And it's a
shame that after half a year it's still present, I've spent too much
time figuring this out after a flawless fresh install on my HP 6510b.
--
Brightness
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:
** Tags added: qa-hardy-desktop
** Tags removed: qa-hardy-list
--
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 a bug contact for kdebase in ubuntu.
--
I upgraded from Xubuntu 7.04 to 7.10 and the Fn key combos on my Toshiba
Satellite L40-12K stopped working, including the brightness adjusting
ones. Also Xfce's Ctrl+Esc shortcut doesn't work now, it works maybe
once in 20 tries. This is also the case with a fresh install of Xubuntu
7.10.
--
No success on my HP2510p.
Downloaded Luka's updated packages. Logout/Login. Screen brightness
buttons still don't work.
Also tried Ryan's xmodmaps to XF86Launch1 and XF86Launch2. No change in
brightness.
Brightness buttons work in Gnome, nevertheless. xev keycodes correspond to:
keycode 101 =
Issue is fixed in Hardy 8.04 alpha with kernel 2.6.24-2-generic and
2.6.24-3-generic. At least on my Everex where I have been running Hardy.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member
Luka: I retested the dcop calls and they work fine.
--
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 a bug contact for kdebase in ubuntu.
--
kubuntu-bugs mailing
Luka,
You have a typo in your sources. It doesn't work because these lines:
{ BrightnessUp, KShortcut(XF86Launch1, SLOT(pmBrightnesUp())
},
{ BrightnessDown, KShortcut(XF86Launch2),
SLOT(pmBrightnesDown()) },
are supposed to be these linese:
{
Ryan, sure it helps. ;-) Thank you very much for catching this!
I have uploaded new kdeutils/kdebase packages to my PPA (gutsy) and they
should be built in couple of hours. When I get at least some
confirmation that it works for some reporters (do not forget to
logout/login!), I will prepare
Packages are now available in my PPA. Add this to your sources.list:
deb http://ppa.launchpad.net/lure/ubuntu gutsy main
After update/upgrade, do logout/login (or reboot) and test brightness
keys.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You
Just tried the rebuilt packages. Brightness down works but not
brightness up.
--
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 a bug contact for kdebase in ubuntu.
The only problem for me now is the brightness popup of guidance-power-
manager is ugly. I have kmilo-legacy installed so the asus plug-in shows
the kmilo osd. Wish we could disable the popup from guidance-power-
manager. Nothing is exposed via dcop so it has to be edit in guidance-
power-manager
I didn't download Luka's packages but changing those lines causes the
brightness keys to work on my machine. Check your
/usr/share/apps/kxkb/ubuntu.xmodmap.
Add the XF86Launch1 and XF86Launch2 lines if they don't exist. Something
like:
keycode 101 = XF86Launch2
keycode 212 = XF86Launch1
I
dragon76: does dcop calls works? Can you again test the stuff from
comment #37
Ryan: I have changed back mapping for Down to XF86LaunchD and Up to XF86LaunchE
We can work on better popup for Hardy.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You
** Tags added: qa-hardy-list
--
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 a bug contact for kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
** Bug watch removed: GNOME Bug Tracker #469748]has
http://bugzilla.gnome.org/show_bug.cgi?id=469748]has
** Bug watch added: GNOME Bug Tracker #469748
http://bugzilla.gnome.org/show_bug.cgi?id=469748
--
Brightness key stopped working after update [Gutsy]
I have started a thread in kubuntu-devel mailing list for further debugging. If
you want to participate, join the discussion there:
https://lists.ubuntu.com/archives/kubuntu-devel/2007-December/002058.html
I will also report any progress in the bug.
--
Brightness key stopped working after
In message at https://lists.ubuntu.com/archives/kubuntu-
devel/2007-December/002059.html you ask results of procedure below.
Don't work here.
How to manually test this with brightness keys on your laptop:
1. Manually assign keycode
In Konsole, execute the following commands:
xmodmap -e 'keycode
It *almost* works. I assign both keys to maximize explained. When I try to
maximize a window I can see it get bigger but then it instantly turns back to
the size it had before.
Same effect with both key combination.
--
Brightness key stopped working after update [Gutsy]
Maximize is toggle action - so it may be that two presses were
registered. You can check with if you run xev and check its output.
--
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
1. Exact HW
cat /var/lib/acpi-support/system-product-name
Answer:
HP Compaq 2510p Notebook PC
2. Do these two commands (if run from Konsole) change brightness
properly on your laptop?
dcop `dcop | grep power-manager` power-manager brightnessUp
dcop `dcop | grep power-manager` power-manager
Can each of reporters that have problem on Kubuntu Gutsy report back the
following info for their laptop:
1. Exact HW
cat /var/lib/acpi-support/system-product-name
(ThinkPad T60p) 2007FHG
2. Does these two command (if run from Konsole) change brightness properly on
your laptop?
dcop `dcop |
I use kubuntu from gutsy. The brightness keys used to work on feisty,
and stopped after an upgrade yesterday.
$ cat /var/lib/acpi-support/system-product-name
8743CTO
The dcop scripts don't work for me
$ lshal -m
Start monitoring devicelist:
-
Hi,
just to confirm for DELL Latitude D520 after upgrade Feisty - Gutsy:
Using Feisty setting brightness worked fine without any problem!
Using Gutsy setting brightness using power manager (also kpowersave) works
fine, but NOT using Fn-keys.
1. Exact HW
cat
Same problem here on a Toshiba Satellite a100-912 running Kubuntu Gutsy.
Fn brightness keys worked in Feisty.
1. Exact HW
SATELLITE A100
2. Does these two command (if run from Konsole) change brightness properly on
your laptop?
Yes. they step up and down of a 10% and they even show a
Just want to confirm the bug, T60.
It used to work flawlessly in Kubuntu Feisty, but not anymore since Gutsy.
The strange this is that everything looks normal (see below), it just doesnt
work.
No idea where to look for the problem.
Can each of reporters that have problem on Kubuntu Gutsy
Update:
I just tried to activate AIGLX and Compiz and now the dcop calls don't work
anymore either.
I still get an OSD-message that the brightness would change, but it doesn't.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug
1. Inspiron 1501
2. No and no. I do get a little notification thing next to the battery icon
in the system tray. It says Brightness: 0%.
3. Yes. Up is 212 and Down is 101.
lshal -m output:
09:41:07.799: platform_i8042_i8042_KBD_port_logicaldev_input condition
ButtonPressed = brightness-up
1. Exact HW
cat /var/lib/acpi-support/system-product-name
MM061
(it's a Dell Inspiron 6400)
2. Does these two command (if run from Konsole) change brightness
properly on your laptop?
DCOP commands do work perfectly.
3. Does your laptop return same keycodes from brightness up (212) and
Just to report that the binaries from lure's ppa didn't work, but Mike
Lopez's script works on my Inspiron 1501 without a problem (I am using the
script manually, like 'lcdbryt.sh up'.
--
//victor
http://www.perroscongatos.com/
--
Brightness key stopped working after update [Gutsy]
I've compiled a custom kernel ( 2.6.24rc1 with git12 patch). Oddly enough the
brightness keys are working now with lure's packages.
Maybe it is a kernel issue not kde.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug
KeyRelease event, serial 32, synthetic NO, window 0x1c1,
root 0x59, subw 0x0, time 77599873, (95,53), root:(99,76),
state 0x0, keycode 101 (keysym 0x1008ff42, XF86Launch2), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Unfortunately, it still
On Sat Nov 3 2007 07:29:37 Luka Renko wrote:
Interesting: for some strange reason, Launch[DE] does not work always.
Have uploaded changed binaries with assign Launnch[1-2] instead - hope
this helps.
Still nothing changed here either.
--
Brightness key stopped working after update [Gutsy]
I upgraded ny system using deb http://ppa.launchpad.net/lure/ubuntu gutsy main
but doesnt work yet.
My fn-brightness still doing nothing.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of
OK, I have test binaries for kdebase-bin and kmilo prepared in my PPA.
If you would like to test it, add this to your /etc/apt/sources.list :
deb http://ppa.launchpad.net/lure/ubuntu gutsy main
Then run apt-get update and upgrade.
Then you need to logout/login (or restart the system) to test.
It doesn't work here either (MacBook).
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
The fix isn't working for me either, but it seems that with the package
versions in http://ppa.launchpad.net/lure/ubuntu, keycodes 212 and 101
has been bound to keysyms XF86LaunchD and XF86LaunchE.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You
On Fri Nov 2 2007 09:15:20 Luka Renko wrote:
OK, I have test binaries for kdebase-bin and kmilo prepared in my PPA.
If you would like to test it, add this to your /etc/apt/sources.list :
deb http://ppa.launchpad.net/lure/ubuntu gutsy main
Then run apt-get update and upgrade.
Then you need
Interesting: for some strange reason, Launch[DE] does not work always.
Have uploaded changed binaries with assign Launnch[1-2] instead - hope
this helps.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you
Can each of reporters that have problem on Kubuntu Gutsy report back the
following info for their laptop:
1. Exact HW
cat /var/lib/acpi-support/system-product-name
2. Does these two command (if run from Konsole) change brightness
properly on your laptop?
dcop `dcop | grep power-manager`
* Model: Dell XPS m1210
1. system-product-name is MXC062
2. The dcop-commands work.
3. The keycodes returned are 212 and 101.
lshal -m reports
platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed =
brightness-up
platform_i8042_i8042_KBD_port_logicaldev_input condition
1. Exact HW
cat /var/lib/acpi-support/system-product-name
HP Pavilion dv6000 (GF651EA#ABD)
2. Does these two command (if run from Konsole) change brightness properly on
your laptop?
dcop `dcop | grep power-manager` power-manager brightnessUp
dcop `dcop | grep power-manager` power-manager
1. Everex StepNote ST5340T
2. The dcop commands work
3. brightness up = 212
brightness down = 101
Just in case it helps: lsmod -m
platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed =
brightness-up
platform_i8042_i8042_KBD_port_logicaldev_input condition
1. Exact HW
ThinkPad T60
cat /var/lib/acpi-support/system-product-name
2007C3U
2. Does these two command (if run from Konsole) change brightness
properly on your laptop?
Yes, they do. I get a tooltip over guidance-power-manager's kicker icon
about the brightness as well, instead of the
1. MM061
2. Works fine - same as Kyle S.
3. Don't see my laptop there. But here's the lshal -m output:
15:50:44.872: platform_i8042_i8042_KBD_port_logicaldev_input condition
ButtonPressed = brightness-up
15:50:44.901: platform_i8042_i8042_KBD_port_logicaldev_input condition
ButtonPressed =
Thank you all for fast response.
I have uploaded the fix to my PPA and will ask for testers (as I do not
have the HW to properly test the fix) later when packages get built.
Then we will see if we can request StableReleaseUpdate for gutsy.
** Also affects: kdeutils (Ubuntu)
Importance:
mikelopez: Thanks for the script. I got it working, but I had to change
/proc/acpi/video/VGA/LCD/brightness to
/proc/acpi/video/VID/LCD/brightness - changing VGA to VID made it
work on my Dell Inspiron E1505. Hope your fix can shed some light on the
bug.
--
Brightness key stopped working after
Hi I'm running Kubuntu Gutsy on a Gateway ML6720 laptop and it doesn't
work either. Based on the comments here, I decided to write a short
bash script as a temporary workaround. It looks like that acpi_fakekey
is not working properly. I did however notice that echoing a value to
I can confirm that the bug is also present in kpowersave in addition to
kpowermanager.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Kubuntu Gutsy 7.10 amd64 generic kernel.
Same problem in kde here. I have an Everex StepNote ST5340T, it is
identical to an Averatec 2370 and the Averatec's are experiencing the
same problem. Key presses register correctly as above posts indicate.
The turn backlight off key works, but is a
i have same problem here i use Xfce , Fn keys for bright does not work. i have
a dell vostro 1400.
it doesnt work since kernel 2.6.22-10, now im with 2.6.22-14.
When i boot old kernel fn keys work without problems.
--
Brightness key stopped working after update [Gutsy]
It would be nice if someone could tell me where to find an earlier kernel so I
could test this on my computer as well.
Then we could dig through the kernel changelog and see what made it stop
working.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
Loic Nageleisen wrote:
my conclusion:
- acpi stuff now only generates events and does not takes action anymore
- gnome power manager is the only app currently able to catch these key or
hal events and change brightness accordingly
- there's no app for KDE able to do that
- there's no
Okay, as the kde bug and the gnome bug seem to be different, I unmark
Bug #105512 as duplicate as it is upstream, but still present in Gutsy
as of today.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Invalid
--
Brightness key stopped working after update [Gutsy]
Same problem with a 1501. Gutsy with all the updates (it's updating some
stuff right now, but they're unrelated). The funny thing is, I used to
have this problem in Feisty, until Dell released a bios update. Then it
_sort of_ worked. If I hit the brightness keys a few times (no matter
which one),
I'm encountering this problem on my asus w7j too.
Basically:
- pressing keys gives acpi event (checked wich acpi_listen), which in turn
generates fake keypress events (checked with xev) and hal events (checked by
hal -m)
- pressing keys does change brightness in gnome. 'cat
Running KDE on Dell Inspiron here.
Using KDE power manager does work.
From the console, with KDE running, I can change the brightness settings
using:
% dcop power-manager-6385 power-manager brightnessUp
% dcop power-manager-6385 power-manager brightnessDown
(Use % dcop power-manager-6385
i'm having the same problem on a thinkpad t60.
just so you know, this bug
[url=http://bugzilla.gnome.org/show_bug.cgi?id=469748]has been reported
upstream[/url].
[url=http://bugzilla.gnome.org/show_bug.cgi?id=469748#c17]it
appears[/url] that the hal guys switched the type or the brightness
Still not working on Gnome for me, all updates until now (Oct. 13th)
installed... Dell Inspiron 1501.
--
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 a bug contact
Dont't work for me too, Dell Inspiron 1501.
--
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 a bug contact for kdebase in ubuntu.
--
kubuntu-bugs mailing list
Maybe that information helps: When I try to use the gnome-brightness-
applet, it refuses to work, telling me, that the brightness of my screen
couldn't be detected.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote:
As of today, brightness setting fully works for me on a T60. Anyone
confirming that?
Also on a T60 here, still not working for me (in KDE).
--
Brightness key stopped working after update [Gutsy]
On 10/7/07, Kyle S [EMAIL PROTECTED] wrote:
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote:
As of today, brightness setting fully works for me on a T60. Anyone
confirming that?
Also on a T60 here, still not working for me (in KDE).
I'm on a Dell Inspiron 6400.
The
Hm. Maybe it has to to something with the display drivers? Because there
is a tool called 'radeontool' which claims to be a 'utility to control
backlight on radeon based laptops'. I can turn the backlight completely
off with that tool, but cannot dim it. Dimming for me only works with
'echo -n 62
This is weird.
(Running Dell Inspiron 6400 with Intel 945GM graphics card)
When logging in with KDE (this is important) If I listen to
acpi_listen or lshal -m everything seems to be working... except for
the actual brightness which does NOT change. I have these processes
running:
~ % ps axf |
This reminds me of some curiosity I experienced in Feisty: Executing the
command 'echo -n 62 /proc/acpi/video/VGA/LCD/brightness' didn't instantly
change the brightness, only if I pressed 'Fn + down (or maybe up)' the
brightness was set to the given value. But still, using only the Fn-key
As of today, brightness setting fully works for me on a T60. Anyone
confirming that?
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Yeah, but the original reporter marked bug #105512 found on a gnome
setup as a duplicate of his kdebase-bug. I kind of doubt that it is
related to kde or gnome, but some different package, both have in
common. Which one, I don't know.
--
Brightness key stopped working after update [Gutsy]
On 10/5/07, der_vegi [EMAIL PROTECTED] wrote:
Yeah, but the original reporter marked bug #105512 found on a gnome
setup as a duplicate of his kdebase-bug. I kind of doubt that it is
related to kde or gnome, but some different package, both have in
common. Which one, I don't know.
I don't
Yes, you're right, the marking is counter-productive. It was done by too
many people: One marked a gnome bug as a duplicate of a kdebase-bug,
then I added gnome-power-manager, then it was marked as invalid for kde
and 'fix released' for gnome by someone else, then I reopened it for
If it's not a HAL bug, then IMHO it should be made a HAL bug, because I
want to be able to set the brightness of my laptop screen without having
to start KDE or Gnome in order to do so.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received
On Friday 05 October 2007 11:22:41 der_vegi wrote:
Yes, you're right, the marking is counter-productive.
[...]
It might be a HAL bug, but as I am not too much into that stuff, I'll
keep my fingers off marking now. ;)
Yeah it seems like we're having to speculate where the problem actually
** Changed in: kdebase (Ubuntu)
Status: New = Invalid
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Fix Released
I'd like to gently point out that the original reporter of this bug is a KDE
user. This makes no sense at all.
--
Brightness key stopped working after
Well, for me the brightness keys still don't work in daily-live 20071003
(amd64), newest updates installed, which means that I do have hal
0.5.9.1-6ubuntu1 gnome-power-manager 2.20.0-0ubuntu3 installed.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
Maybe an output of 'lspci -vvnn' helps?
** Attachment added: output of 'lspci -vvnn'
http://launchpadlibrarian.net/9712909/lspci_vvnn
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = Confirmed
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Some package have been updated.
Now the FN-brightness keys work again.
- hal (0.5.9.1-6ubuntu1)
- gnome-power-manager (2.20.0-0ubuntu3)
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of
** Changed in: kdebase (Ubuntu)
Status: New = Invalid
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Fix Released
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote:
Some package have been updated.
Now the FN-brightness keys work again.
Still not working for me in KDE land, upgraded a number of packages, last
upgrade was less than an hour ago. Browsing the code in
guidance-power-manager right now,
** Also affects: gnome-power-manager (Ubuntu)
Importance: Undecided
Status: New
--
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 a bug contact for kdebase
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running
Kubuntu. Brightness keys do not work even though lshal -m,
acpi_listen, and acpid all see them/do the right thing. No OSD from
kmilo anymore either, for anything, even volume or thinklight which work
(probably only because
Running Dell Inspiron 6400 here.
# dmidecode -s system-manufacturer
Dell Inc.
# dmidecode -s system-product-name
MM061
# dmidecode -s system-version
Not Specified
Just updated to Gutsy BETA, and brightness keys don't work anymore.
If I remove the power cable, brightness goes down, but if I
I don't think this bug is related to kdebase, as it also happens on my
ubuntu daily-live 20070929 (amd64). I'm using a Dell Inspiron 1501. But
changing display brightness with the Fn-keys hasn't worked for me since
feisty.
--
Brightness key stopped working after update [Gutsy]
Same problem here with Ubuntu Gutsy on a Dell Inspiron 640m/E1405.
Brightness-down works, Brightness-up does not.
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
*** This bug is a duplicate of bug 34802 ***
https://bugs.launchpad.net/bugs/34802
** This bug has been marked a duplicate of bug 34802
unable to increase brightness once it's been decreased to its minimum
--
Brightness key stopped working after update [Gutsy]
** This bug is no longer a duplicate of bug 34802
unable to increase brightness once it's been decreased to its minimum
** Changed in: kdebase (Ubuntu)
Sourcepackagename: acpi-support = kdebase
--
Brightness key stopped working after update [Gutsy]
https://bugs.launchpad.net/bugs/145337
You
92 matches
Mail list logo
