Hi,

What do you mean by "there hasn't been any activity in it recently"? Have
you checked the comments? One person actually found a workaround after
almost 2 years. There has been a ton of happy comments on that.

But for myself - I am not using the laptop nor Ubuntu anymore, so I cannot
confirm anything about it.

But if you check the comments then it is quite obvious that the problem is
still there and there is a small program that you can use for a workaround.


Regards,
Erik



On Sat, Feb 22, 2014 at 1:07 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> erikj, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux 971061
>
> If reproducible, could you also please test the latest upstream kernel
> available (not the daily folder) following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Once you've tested the upstream
> kernel, please comment on which kernel version specifically you tested. If
> this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-3.14-rc3
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Tags added: quantal
>
> ** Tags removed: acpi battery
> ** Tags added: needs-kernel-logs needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
>    Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
> ** Project changed: acpi => linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/971061
>
> Title:
>   acpi reports battery state incorrectly
>
> Status in The Linux Kernel:
>   Incomplete
> Status in "linux" package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have a new Samsung 9-series laptop (NP900X3B) and the battery state
>   is detected incorrectly. Basically the state what was at the time of
>   boot stays active all the time - regardless of the ac-adapter state.
>
>   Here is output from "acpitool -a -b" in various situations:
>
>   When booted with charger connected and charger is still connected:
>     Battery #1     : charging, 47.00%, 01:00:43
>     AC adapter     : on-line
>
>   When booted with charger connected and charger is now disconnected:
>     Battery #1     : charging, 47.00%, 01:36:59
>     AC adapter     : off-line
>   [The battery couldn't possibly be charging when the AC adapter is
> offline!]
>
>   When booted with charger disconnected and charger is still disconnected:
>     Battery #1     : discharging, 47.00%, 01:39:44
>     AC adapter     : off-line
>
>   When booted with charger disconnected and charger is now connected:
>     Battery #1     : discharging, 47.00%, 00:53:43
>     AC adapter     : on-line
>   [The battery is actually charging as the AC adapter is online]
>
>   The percentage and time are correctly updated when the battery is
>   actually charging or discharging - regardless of the reported state.
>   So the state is the only thing that is incorrect. However a number of
>   applications make their decisions based on this state (battery
>   monitor, jupiter, etc.) and therefore behave incorrectly.
>
>   "lshal -m" doesn't report anything when I plug the charger in or out.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.04
>   Package: acpi (not installed)
>   ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
>   Uname: Linux 3.2.0-21-generic x86_64
>   ApportVersion: 2.0-0ubuntu2
>   Architecture: amd64
>   Date: Sun Apr  1 22:50:35 2012
>   EcryptfsInUse: Yes
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64
> (20120328)
>   ProcEnviron:
>    LANG=en_US.UTF-8
>    SHELL=/bin/bash
>   SourcePackage: acpi
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/971061/+subscriptions
>