=== freeflying_away is now known as freeflying === freeflying is now known as freeflying_away [04:43] Good morning [05:50] pitti, ping [05:50] hey tvoss_ === smb` is now known as smb [07:00] good morning [08:55] slangasek, you are patch piloting today? [08:58] I doubt [08:58] he'll be around for several hours yet [08:59] Laney, oh right, I still cant work out all the timezones ;) [08:59] I just type "Time in XXX" into google :P [09:01] I have a few locations in my datetime indicator: a couple across usa, utc, a couple in europe and beijing. =) and steve is west coast. [09:05] What is the standard location: http://ports.ubuntu.com/ubuntu-ports/ or http://ports.ubuntu.com/ ? they seemed to be the same...? [09:06] d-i prefers the former [09:07] ok, thanks. === liam_ is now known as Guest751 === dholbach_ is now known as dholbach [12:23] pitti: hid-generic 0005:045E:0762.0019: input,hidraw3: BLUETOOTH HID v0.13 Keyboard [Microsoft Bluetooth Mobile Keyboard 6000 <-- this keyboard has nothing in /sys/class/power_supply/ and nothing in upower --dump [12:24] hyperair: ah, too bad; thanks anyway! I got three responses for the sysfs dump now, should be enough to construct a test case [12:25] :) [12:25] okay good === jhenke_ is now known as jhenke === Sweetsha1k is now known as Sweetshark [13:12] kees, hardening defaults ping [13:18] FourDollars: hey, still here? [13:24] FourDollars: I'm afraid I need some more data for bug 1153488, I followed up there with a question [13:24] bug 1153488 in upower (Ubuntu) "Treats bluetooth input device batteries as system power supply" [Low,Triaged] https://launchpad.net/bugs/1153488 === kentb-out is now known as kentb [14:00] pitti: ack [14:01] FourDollars: I only became aware that you determine mouse vs. keyboard from the "bluetooth" parent device, and the dumps didn't include those [14:02] pitti: Yes. [14:02] I will collect the data for you. Wait a minute. [14:03] FourDollars: no hurry; thanks! [14:05] Hmm: "internal compiler error: Segmentation fault" on armhf and powerpc in the same source file. But not on amd64/i386. Who to contact to get this investigated? [14:06] Ampelbein: usually you should have pre-processed source file available and together with it you can file a bug against e.g. gcc-4.8 [14:06] Ampelbein: without pre-processed source file there is little to get investigated. Do you have it? [14:06] xnox: But I have neither armhf and powerpc. [14:07] Ampelbein: so where did you get the failure? [14:07] xnox: This happens on the build-servers (https://launchpad.net/ubuntu/+source/mrpt/1:1.0.2-1/) [14:08] So I would need someone (from canonical?) to copy the preprocessed source out of the build-chroot? [14:08] Ampelbein: it's gone and destroyed. [14:10] Hmm, ok. [14:10] Ampelbein: same is happening in debian https://buildd.debian.org/status/package.php?p=mrpt thus a FTBFS bug can be filed there as well. And on debian there are porters / porter boxes that a few people have access to to re-run builds. [14:11] pitti: There is no output from `grep -r . /sys/class/power_supply /sys/class/bluetooth`. Change it to `grep -r . /sys/class/power_supply/*hci* /sys/class/bluetooth/*hci*`? [14:12] xnox: Ok, will file a bug in Debian, thank you. [14:15] Cimi: ping [14:20] FourDollars: hm, should be necessary [14:20] FourDollars: are you running saucy? [14:20] FourDollars: in that case, it might be easiest and best to install umockdev and do "umockdev-record --all > /tmp/out.txt" and attach that [14:21] pitti: no. I run Ubuntu 12.04. [14:21] FourDollars: this will provide a complete dump of all devices [14:21] FourDollars: ah, ok [14:22] FourDollars: ah, perhaps this: [14:22] grep -r . /sys/class/power_supply/* /sys/class/bluetooth/* [14:24] ok [14:28] pitti: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/comments/23 [14:28] Launchpad bug 1153488 in upower (Ubuntu) "Treats bluetooth input device batteries as system power supply" [Low,Triaged] [14:30] FourDollars: splendid, thank you! [14:30] pitti: no problem. :) [14:47] darkxst_: yes, what's up? === psivaa is now known as psivaa-bbl [14:53] fwd from #ubuntu-quality: Would this be the right place to go if I wanted to propose a particular application be removed from USC? [14:57] ev, Reading your mail about high CPU usage services. [14:57] ev, Seems to me that we could make it opt-in. Then "bringing it to the desktop" would be a service by service thing. [14:57] ev, Perhaps by adding a stanza to the upstart job config? [14:58] ev, Something similar to the respawn limits [14:58] tedg: so the whitelist approach was discussed but the worry was that we wouldn't catch things like the ueventd bug [14:58] because we couldn't anticipate them going proper mental [14:59] ev, The whitelist would be "everything on phone" where the set is smaller, no? I mean we could grep for it and generate bugs. [15:01] tedg: hm? I mean in the general sense, going with a whitelist approach on the desktop means that we'll miss whatever we don't anticipate spinning out of control [15:01] unless I misunderstand what you're suggesting? [15:02] ev, Sure, on the desktop. But I think that it's an unbounded problem to watch everything. You don't want to kill my SETI@Home. [15:02] or totem or the flash plugin, etc. (this has already been discussed via mail) [15:02] * tedg has a prime refactorting botnet. No reason. [15:03] tedg: hah, recovered your lost secret GPG key yet? :-) [15:03] true, so whitelist rather than blacklist might be best [15:03] tedg: would you mind following up to the ML post with this? :) [15:03] ev, Heh, sure. [15:03] would "everything that provides a D-BUS service" be a good first bite into teh whitelist? [15:04] pitti, No, but I have kees' so we're good, mine isn't as useful. [15:04] pitti, +1 [15:05] Perhaps we could detect the case and generate a recoverable error for folks not in the whitelist. [15:18] jamespage: hey, are you around still? [15:18] hallyn_, yes [15:18] jamespage: was wondernig if you'd had any thoughts on the likewise-open bug situation === freeflying is now known as freeflying_away [15:20] hallyn_, I've not look at it hard yet [15:20] but I reckons there are a load of bugs that can be duped up [15:20] I'm assuming that ubuntu-server was not a bug subscriber until recently right? [15:20] jamespage: ok. I will probably take an overly broad brush and do that, and beg the reporters' forgiveness if I err. [15:20] that's my assumption too :) [15:21] all the old bug will drown out new, valid ones, so i'd like to just mark them invalid actually [15:21] and ask the reporters to respond and re-set to new if they still have the problem [15:21] hallyn_: you could set them to "incomplete" with "does this still happen in saucy?" and let them time out [15:22] pitti, alot of them look like dist-upgrades to lucid [15:22] so I'd rather not do that [15:22] not for those where this quetsion obviously doesn't make sense, of course :) [15:23] jamespage: so if a dist-upgrade to lucid failed on likewise-open, is it fair to assume that the reporter must've gotten past it by now? [15:23] i.e. mark invalid and ask to re-open? [15:23] any which were not dis-tupgrades, set to incomplete? [15:23] sounds reasonable [15:24] * jamespage worries about the state of likewise-open in distro [15:24] it does not get much love anymore [15:24] pitti: thanks for the suggestion, will do that for a bunch [15:24] jamespage: yeah i've considered spending a day to try it out so i can be better able to look over it [15:24] wasn't kirkland at one point our resident expert? :) [15:24] maybe - I'm not sure [15:25] I'm not 100% clear why its in the supported seed [15:25] i just .. have *never* used it. [15:25] yeah [15:25] Daviey: ^ do you know how that showed up? [15:25] hallyn_: jamespage: likewise? I think that was dendrobates' doing [15:26] hallyn_: jamespage: I think dendrobates, soren, or ttx might remember [15:27] * jamespage is slightly embarresed he had to lookup who dendrobates whas [15:27] (sorry) [15:27] jamespage: heh :-) [15:27] kirkland: i meant it showing up in server supported seed [15:27] jamespage: hallyn_: yeah, looking at likewise-open's debian/changelog, it was dendrobates (Rick Clark) that packaged it originally; I think he pushed the MIR as well [15:28] no seb128 today? [15:28] hallyn_: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/201537 [15:28] Launchpad bug 201537 in likewise-open (Ubuntu) "MIR for likewise-open" [High,Fix released] [15:28] hallyn_: oh, that one is zul's :-) [15:28] oh zul... deary me [15:28] kirkland: at those times, integration with AD was seen as a key feature [15:29] what did i do now? [15:29] and likewise-open was basically the component that was supposed to allow us doing it [15:29] so it was more of a product management thing [15:29] ttx: :-) [15:29] ttx: so let's blame nijaba, then :-) [15:29] I can see the context - thanks for clearing that up ttx [15:29] always blame nijaba [15:29] ttx: howdy, btw! [15:29] howdy! [15:42] jamespage: lol [15:42] dendrobates, sorry :-) [15:43] no worries === psivaa-bbl is now known as psivaa === masACC is now known as maswan [17:39] * kees looks forward to tedg's impersonation of him === slomo_ is now known as slomo [18:17] * tedg does his best kees: "Oh, look, I've got a goatee and all my IP traffic is coming from Siberia" ;-) [18:17] * tedg probably shouldn't quit his day-job === slomo_ is now known as slomo [18:42] tedg: hehe, A++ would be impersonated again === wedgwood is now known as Guest57531 === freeflying_away is now known as freeflying === freeflying is now known as freeflying_away