[09:57] <amitk> zul: Do you want me to pull both commits since 0a7ecab0094bf5b59586eb8e2a2071c1740eba9a?
[10:09] <arooni__> zomg so many updates today for gutsy..... what changeD?
[03:16] <zul> oooh..
[03:16] <zul> you might want to change that
[03:16] <BenC> oops
[03:16] <amitk> :-D
[03:16] <zul> need more coffee BenC?
[03:17] <BenC> wonder where the extra 'e' after /m came from
[03:18] <BenC> glad I only use that password here :)
[03:18] <zul> hehe
[05:10] <evand> Can someone take a look at bug 139453?  mjg59 suspects it's a kernel issue, rather than usplash.
[05:10] <ubotu> Launchpad bug 139453 in usplash "colors are left on the screen after blanking with usplash enabled" [High,Triaged]  https://launchpad.net/bugs/139453
[10:20] <manchicken> Is power-management (e.g. battery levels and monitoring) a kernel issue or a user-land issue?
[10:21] <johanbr> Depends on exactly what the problem is.
[10:23] <manchicken> Problem is that both under KDE and GNOME I get the power management programs telling me that I'm switching onto or off of AC power incorrectly.
[10:23] <manchicken> Also, much of the time on battery power the program is either reporting no power on the battery incorrectly.
[10:24] <manchicken> Also, my machine doesn't seem to want to come back from suspend to RAM, so that's another problem.
[10:27] <manchicken> I'm guessing that since I'm running Gutsy that System76 isn't going to be all that interested in helping, so I'm trying to find someone who might be able to sort the problem out.  I'm guessing that the power-management problems may be in HAL or maybe dbus (not sure how the power-management programs fetch their data), but I'm pretty sure that the suspension issue is ACPI/kernel related.
[10:27] <manchicken> allee: What's going on?
[10:31] <allee> manchicken: hey! dadchecken. 
[10:32] <manchicken> Howdy :)
[10:33] <manchicken> brb, gotta call the fire dept
[10:34] <allee> manchicken: oh :)
[10:34] <JanC> manchicken: I guess you can ask/inform the system76 guys, as I guess they _will_ be interested to have working equipment to sell, even after the gutsy release  :)
[10:34] <manchicken> Yeah
[10:36] <bdmurray> manchicken: so many questions. ;) You could look at /proc/acpi/battery/BAT0/[state|info]  to see what the kernel says about your battery
[10:37] <manchicken> True.  I'll get into more of that once I'm done dealing with this real-life fire.
[10:37] <manchicken> brb.
[11:02] <johanbr> manchicken: Try looking at the files in the /proc/acpi directory. If the information there is incorrect, it's a kernel issue.
[11:16] <manchicken> So that sucked.  Anyway, I'll take a look at /proc/acpi
[11:18] <manchicken> I am getting some weirdness.
[11:19] <manchicken> Sometimes it says charged but has "unknown" for present rate or remaining capacity.
[11:19] <manchicken> Now it says I'm charging, but the cord is most certainly disconnected.
[11:19] <manchicken> So that sounds like a kernel issue then?
[11:20] <manchicken> The temperature seems a bit off, too.  It's switching back and forth between 5 C and 48 C
[11:31] <JanC> 5 & 48 C you mean  ;)
[11:31] <JanC> but that sounds quite wrong indeed
[11:32] <JanC> I have seen some weird things underfeisty a couple of times, but couldn't reproduce it
[11:34] <manchicken> Yea
[11:34] <manchicken> I'm just putting what the file had in it :)
[11:35] <manchicken> The power management and suspension stuff is really impacting me negatively though.
[11:35] <manchicken> Right now it's telling me that it's going to take 27 hours to charge my battery, which I'm pretty sure is wrong.
[11:36] <manchicken> I'm guessing System76 doesn't have any IRC channels though.
[11:36] <bdmurray> manchicken: you'll want to submit a bug report regarding the kern then
[11:37] <bdmurray> kernel even
[11:37] <manchicken> Okie dokie.
[11:37] <bdmurray> and attach a tarball of /proc/acpi
[11:37] <bdmurray> in addition to the the kernel teams minimum bug requirements
[11:38] <manchicken> Where might I find those?
[11:38] <manchicken> (the minimum requirements that is)
[11:39] <bdmurray> http://wiki.ubuntu.com/KernelTeamBugPolicies or something close to that
[11:39] <manchicken> Much thanks.
[11:40] <manchicken> I'll try to either post to an existing report or post a new one.
[11:40] <bdmurray> No problem
[11:52] <manchicken> This is interesting.
[11:53] <manchicken> In syslog I get very unusual keycode error messages reported whenever I unplug or plug in the AC adapter.
[11:54] <bdmurray> I imagine your BIOS is up to date
[11:54] <manchicken> bdmurray: I'm unaware of how to change or check such a thing.  I'm guessing System76 would give me such an update over their repository.
[11:56] <manchicken> If my situation only somewhat resembles that of another bug, should I just add my addition to that bug report, or should I post a new bug report and cite that it is similar to another?
[11:58] <bdmurray> manchicken: Your bug sounds very hard specific and so the best idea is to submit a separate bug report
[11:58] <bdmurray> and mention that it is similar
[11:58] <bdmurray> s/hard/hardware/
[11:59] <manchicken> Righto.
[11:59] <manchicken> I'm also emailing System76 support.
[12:09] <manchicken> Bug #139701 reported.
[12:09] <ubotu> Launchpad bug 139701 in linux-source-2.6.22 "Under Gutsy on System76 Darter, battery state information is often incorrect." [Undecided,New]  https://launchpad.net/bugs/139701
[12:17] <bdmurray> manchicken: that bug report looks great - thanks
[12:19] <manchicken> Not a problem.  I hope it helps someone fix a problem :)