Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 343963 - tint2 segfault on 2.6.36 kernel (patch included)
Summary: tint2 segfault on 2.6.36 kernel (patch included)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-03 11:48 UTC by Andrew Brouwers
Modified: 2011-04-01 19:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Brouwers 2010-11-03 11:48:26 UTC 
After updating to 2.6.36 last night, tint2 was segfaulting with an error about "current_now" relating to the batter.

http://code.google.com/p/tint2/issues/detail?id=299

...is a link to the upstream bug report, and the patch was already accepted in to their SVN repository.

Reproducible: Always
Comment 1 Christian Ruppert (idl0r) gentoo-dev 2010-11-03 17:14:23 UTC 
This problem has been fixed in our software repository. The fix will be available on the mirrors soon. Thank you for your bug report.
Comment 2 Alexey Mishustin 2011-04-01 18:03:14 UTC 
That's strange, but I met the same issue today.

ERROR: battery applet can't open energy_now
Segmentation fault

Laptop ASUS W7J, tint2-0.11.
Comment 3 Andrew Brouwers 2011-04-01 18:43:03 UTC 
(In reply to comment #2)
> That's strange, but I met the same issue today.
> 
> ERROR: battery applet can't open energy_now
> Segmentation fault
> 
> Laptop ASUS W7J, tint2-0.11.

*tint2-0.11-r1 (03 Nov 2010)

  03 Nov 2010; Christian Ruppert <idl0r@gentoo.org> -tint2-0.9.ebuild,
  -tint2-0.10.ebuild, +tint2-0.11-r1.ebuild, +files/battery_segfault.patch:
  Revision bump, fixes bug 343963, thanks to Andrew Brouwers
  <abrouwers@gmail.com>. Remove old ebuilds.


^^ be sure you are on -r1.
Comment 4 Alexey Mishustin 2011-04-01 19:35:22 UTC 
>^^ be sure you are on -r1.

Testing? OK. Thanks.