[09:33]  * ppisati -> reboot
[09:45] <apw> arges, you still got the electric blue notifications?  ppisati seems to have them too
[09:45] <arges> apw, they disappeared after another upgrade yesterday
[09:46] <arges> apw, now i see other things.... highlight text in a webpage then right click... unfortunately i can't take a screenshot of it 
[09:46] <apw> arges, ok that odd
[09:46] <apw> arges, try a delayed screen shot perhaps
[09:46] <arges> apw, good idea
[09:46] <arges> now i can't click again... 
[09:46] <arges> time for another cup of coffee
[09:51] <cking> smb, see the hud graphs in https://bugs.launchpad.net/ubuntu-power-consumption/+bug/938584/+attachment/2770166/+files/hud-cpu-maxed-out.ods
[09:51] <ubot2`> Launchpad bug 938584 in indicator-appmenu "hud-service consumes all the cycles on my CPU" [High,New]
[09:51] <arges> ouch
[10:08] <apw> cking, i wonder how manu menu idems hud really has to search when you think about it
[10:08] <apw> its got just the menus for the current application, and those in the indicators
[10:09] <apw> lets be, really, really, generous and say there are 1000 entries to search
[10:09] <apw> how long can it take to do a earch on those
[10:09] <cking> apw, i suppose the source will be enlightening
[10:10] <apw> or heavy
[10:10] <smb> I would assume a lot is because it restarts the search for every new key you type
[10:10] <apw> smb, in the test case i typed 7 characters, so it might have had to redo the search up to 7 times
[10:11] <apw> to lets say thats a search of 7k lines
[10:11] <smb> apw, And draw its current map thoughts
[10:11] <cking> where does it get the data from? dbus?
[10:12]  * smb would not be surprised to find it polls back whether the drawing operation has not been done yet ever millisecond
[10:12] <apw> cking, i suspect it does yeah
[10:12] <cking> so it should cache this, bet it doesnt
[10:12] <apw> yeah
[11:02] <apw> smb, my desktop just went pop
[11:02] <smb> apw, awsome
[11:03] <apw> cking_, you lost your graphics yesterday, no VT switches right ?
[11:03] <cking> yep and today, had to reboot at 10:20 ish today because it locked up
[11:04] <apw> cking, just happened to me, xorg sleeping on a futex
[11:04] <smb> apw, Does that means hangs/locksup or just that tendency to randomly turn of the display for a few secs that I sometimes see 
[11:04] <cking> more than just a few seconds
[11:34] <apw> mine was dead totally, had to be kicked in the eye
[11:46] <ogra_> well at least your fonts didnt turn into rainbows (like it is here) and i guess your notifications didnt turn green either
[11:49] <cos^> if someone says he has applied a patch on LKML, which kernel branch does it go?
[12:16]  * henrix will be back in ~20min
[12:53] <apw> cos^, to that maintainers tree, which in theory you can figure out from the MAINTAINERS file
[12:53] <apw> ogra_, heh, there is a lot of luminous blue OSDs being reported too
[12:57] <ogra_> fun
[13:04] <cos^> apw: ok.. it should be in jikos tree but it isn't. maybe he hasn't pushed the commit yet..
[14:34] <ppisati> HP to Make ARM Servers Available for Testing in Q2
[14:34] <ppisati> http://www.pcworld.com/article/249988/hp_to_make_arm_servers_available_for_testing_in_q2.html
[14:34] <ppisati> FYI
[14:35] <ogra_> assuming they exist until then :P
[14:35] <ppisati> :)
[14:35] <ppisati> well, they said they'll openm a lab for selected costumer
[14:35] <ppisati> in case the silicon is not ready yet, they can fake it via qemu :)
[14:36] <ogra_> haha
[15:16] <henrix> whois bjf
[15:16] <henrix> ugh
[15:27]  * ogasawara back in 20
[15:49]  * tgardner reboots tangerine
[16:00] <ogasawara> tgardner: be there in a bit
[16:01] <skaet> ogasawara, is the linux kernel we have in the archive now going to be the one for beta 1?   (or are there some more bug fixes you're trying to land)
[16:01] <tgardner> ogasawara, ack, interview call at 0900 if you wanna attend
[16:01] <ogasawara> skaet: the one in the archive is what I plan for beta-1
[16:01] <skaet> ogasawara, thanks. :)
[16:04] <jsalisbury_> Is anyone else having issues with tangerine?
[16:05] <ppisati> jsalisbury: it has been rebooted some minutes ago
[16:05] <tgardner> jsalisbury, I'm trying to get it to reboot
[16:05] <ppisati> jsalisbury: but otrher than that, it works here
[16:05] <tgardner> ppisati, I don't think it actually rebooted
[16:06] <jsalisbury> tgardner, ppisati, ahh, ok. thanks
[16:06] <tgardner> ppisati, 16:02:15 up 3 days,  1:17,  2 users,  load average: 0.00, 0.03, 0.08
[16:06] <ppisati> good point :)
[16:06] <jsalisbury> tgardner, my sessions all got kicked off and I can't seem to log back in.
[16:07]  * jsalisbury wonders if tgardner has a long enough arm to reach the power switch :-)
[16:07] <tgardner> jsalisbury, gonna have too pretty soon
[16:07] <tgardner> jsalisbury, looks like its back, 2 min uptime
[16:08] <jsalisbury> tgardner, hmm, I'm back in now
[16:08] <jsalisbury> tgardner, top looks really strange, a bunch of root RT processes
[16:08]  * cking orders a USB3 -> SATA dohicky
[16:09] <jsalisbury> tgardner, hmm, maybe that's normal.  Looks like watchdog, migration and kworker
[16:11] <jsalisbury> 64 threads for each ?
[16:24] <apw> jsalisbury, could be easily be one per cpu of many of those kernel threads
[16:24] <apw> jsalisbury, to ensure deadlock avoidance
[16:29] <jsalisbury> apw, that makes sense.  
[16:30] <cking> it's not like they are doing much most of the time
[16:30] <apw> if anything ever in many cases, just sitting there
[16:30] <cking> and doing the very occasional wakeup
[16:31] <cking> hrm, why has rhythmnbox lost all my mp3s?.  Bah
[16:37] <apw> cking, synced to the contents of your phone
[16:37] <cking> fortunately not
[16:38] <cking> if my music collection gets sync'd to /dev/null I won't be a happy bunny
[16:38] <ogra_> buy vinyl its more persistent anyway !
[16:39] <ogra_> (though admittedly hard to listen to on flights)
[16:40] <apw> ogra_, well as long as you don't play it with anything other than a laser
[16:40] <ogra_> lol
[16:40] <apw> they say you lose about 20% of the top end the first time you play it with a needle
[16:40] <ogra_> you think needles wouldnt pass security ?
[16:40] <apw> which is why the autophiles like it, it softens the top end right off
[16:40] <ogra_> nonsense
[16:41] <ogra_> digitalization swallows more 
[16:41] <apw> oh i am not saying an mp3 is worth shit at all
[16:41] <ogra_> unless you deal with hilarious big media to store flacs
[16:42] <apw> the thing about digitisation loss though is you can target it, vinal lost is exponentially worse at high frequencies
[16:42] <apw> either way i can't tell with my ears
[16:43] <ogra_> needles dont do harm to records if your player is proper ... sadly the used vinyl has usually been played on record grinders
[16:43] <ogra_> the hig feqs totally depends on the setup and on how much you invest
[16:44] <ogra_> it *is* on the media ... if your first playing scratches it off is a different thing and a matter of the equipment
[16:45] <apw> ogra_, indeed, though other than a non-contact reader, i am not convinces any needle based reader is able to not remove the high end, they are simply too heave to move out the way
[16:45] <ogra_> the area where the needle touches the vinyl doesnt have any sounds on it 
[16:46] <ogra_> vertically that is 
[16:46] <apw> the needle is vibrated up left and up right to induce the sound
[16:46] <apw> somethign is moving it
[16:46] <ogra_> yep
[16:46] <apw> ok, so that thing that moves, has to be moved, moved by the surface shape of the slot in the plastic
[16:46] <ogra_> and there it matters how your player, your system, your needle itself etc is designed and combined
[16:47] <ogra_> right
[16:47] <apw> and the relative weight of that defines how much energis is required for the plastic to mvoe it
[16:47] <apw> the higher the frequency the faster, and more the energy
[16:47] <ogra_> if it would grind off the surface you would have black plastic dust all around if you played a record 
[16:48] <apw> and at those higher frequency it is a thiner and thiner bit of plastic which does it
[16:48] <ogra_> thats where the design of the cardtridge comes into play 
[16:48] <apw> ogra_, nope, all it has to to is average the plastic into a flat line
[16:48]  * tgardner rebuilds gomeisa precise chroots yet again
[16:48] <apw> it doesn't need to remove any
[16:48] <apw> just move it about
[16:48] <ogra_> and the cut of the needle etc
[16:48] <apw> of course a good needle has to be infinitly better than a bad one
[16:49] <ogra_> i have 40year old records that still have all high freqs :)
[16:49]  * tgardner reboots gomeisa
[16:49] <apw> ogra_, and how can you tell that?
[16:50] <tgardner> smb, need to bounce gomeisa. holler when your job is done
[16:50] <apw> i can believe you have records that sound fine after 40 years
[16:50] <smb> tgardner, sure
[16:50] <apw> tgardner, subtle ...
[16:51] <apw> tgardner, i wondered why my build was struggling, the chroot is gone :)
[16:51] <apw> tgardner, what happened to em, will mine break if i update them?
[16:52] <ogra_> apw, indeed, its hard to tell since my ears got 40 years older too :)
[16:53] <smb> tgardner, I am gone
[16:54] <tgardner> apw, more of that resolvconf package nonsense. it keeps breaking things on a lucid host
[16:54] <tgardner> tangerine is working well
[16:55] <apw> tgardner, yeah just have to upload 100MB there to get my build going :)
[16:57] <tgardner> apw, whinger
[16:57] <apw> tgardner, to the very core, always
[16:58] <tgardner> apw, its rebuidling now...
[16:59]  * smb found the copy /etc/passwd from the host approach breaking chroot updates in subtle ways
[18:25] <jjohansen> apw: bug#925028 isn't entirely fixed by my apparmor patches.  It still requires profiles to have the attach disconnected flag, I am planning to look at it more today
[18:26] <apw> bug #925028
[18:26] <ubot2`> Launchpad bug 925028 in lxc "apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL)" [High,Confirmed] https://launchpad.net/bugs/925028
[18:26] <apw> ok cool
[18:40] <jsalisbury> ogasawara, this looks like it might be a quick fix by including the firmware in precise: bug 939231
[18:40] <ubot2`> Launchpad bug 939231 in linux-firmware "Dlink DWA-160 (Atheros AR9170 802.11n ) is broken" [Undecided,New] https://launchpad.net/bugs/939231
[21:37]  * cking -> EOD