*** This bug is a duplicate of bug 438763 ***
https://bugs.launchpad.net/bugs/438763
** This bug is no longer a duplicate of bug 311436
Backlight can't be set, although possible using "xbacklight"
** This bug has been marked a duplicate of bug 438763
Can not set backlight brightness on m
*** This bug is a duplicate of bug 438763 ***
https://bugs.launchpad.net/bugs/438763
I found a duplicate of this issue actually here on LP, and it was
reported upstream as well. Then I think I just found another duplicate
that is assigned and confirmed to the ACPI package.
** This bug is no l
*** This bug is a duplicate of bug 438763 ***
https://bugs.launchpad.net/bugs/438763
Technically bug 438763 is a newer report, but it has a bit more info.
Turns out you need a special kernel module not included with the
standard kernel for this to work.
** This bug has been marked a duplicate
I am so glad you found out that the issue is also in UNR, well not
really, but I am happy that it doesn't just happen with Kubuntu, but
hate that it is happening at all for you. I will try and figure out
where this should get filed. I really appreciate your quick responses
and excellent help in tri
Okey-dokey... I know what to do now :) Thanks!
Anyhooo... as of a complete update at 9:32pm BST, the UNR applet isnt
working, nor are the brightness function keys. Ho-hum
Guess this shouldn't be under "KDE workspace" anymore... feel free to
move this somewhere more appropriate if you wish.
I
OK, I reopened the bug. In the future all you have to do is go to
https://bugs.launchpad.net/bugs/. Bugs that are marked Fixed
Release won't show up in the bug lists unless you specify it.
Did you by chance do a reboot after the upgrade to see if that fixed the
issue? I just did the same update an
Sorry to email directly but the bug has disappeared off launhpad.
Just done (another) update (mainly python stuff I think) and now its
not working again :'(
Care to reinstate?
Thanks
Rachael
www.rlb.tel
On 3 Oct 2009, at 19:10, Richard Johnson wrote:
> That was quick. I read my email where
That was quick. I read my email where you said it doesn't work in UNR,
opened up the page and was going to comment that we need to find out
where the problem lies, and look, it is fixed \o/ woohoo! That was easy
:)
--
Battery monitor applet no longer controls brightness on Samsung NC10
https://bu
W-Ho!!!
It works again :)
And for the first time so do the NC10's brightness function keys :-D
** Changed in: kdebase-workspace (Ubuntu)
Status: Incomplete => Fix Released
--
Battery monitor applet no longer controls brightness on Samsung NC10
https://bugs.launchpad.net/bugs/4176
Hi
It turns out this isn't a specific KDE problem... the brightness applet in UNR
doesn't work any more either :(
So I guess it must be something to do with the sub-system?
This is a fairly major issue tho for all NC10 owners since the
brightness function keys don't map under *buntu without a re
Is this still reproducible with a newer release of KDE, preferably
Karmic and KDE 4.3.1? I don't have the NC10, but all of my machines work
correctly using the battery monitory for screen brightness. Thanks!
** Changed in: kdebase-workspace (Ubuntu)
Status: New => Incomplete
--
Battery mo
** Package changed: kubuntu-meta (Ubuntu) => kdebase-workspace (Ubuntu)
--
Battery monitor applet no longer controls brightness on Samsung NC10
https://bugs.launchpad.net/bugs/417651
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-worksp
12 matches
Mail list logo
