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