[01:11] <xnox> @pilot out
[02:01] <Bluefoxicy> httperf --hog --num-conn 25000 --rate 10000 192.168.1.144 --timeout 5
[02:01] <Bluefoxicy> ^^^^ this hangs.
[02:01] <Bluefoxicy> httperf --hog --num-conn 15000 --rate 10000 192.168.1.144 --timeout 5
[02:01] <Bluefoxicy> ^^^ this does not.
[02:02] <Bluefoxicy> echo 1 | sudo tee /proc/sys/net/ipv4/tcp_tw_reuse ; echo 1 | sudo tee /proc/sys/net/ipv4/tcp_tw_recycle
[02:02] <Bluefoxicy> ^^^ Now neither hangs.
[02:02] <Bluefoxicy> Ubuntu 12.10
[04:59] <pitti> good morning
[05:33] <pitti> stgraber, infinity: can you please remove the pygobject block? all relevant autopkgtests succeeded, except software-center which failed before (and I tested that manually)
[05:40] <infinity> pitti: Sure.
[05:50] <pitti> infinity: thanks
[07:50] <pitti> hey mvo, guten Morgen
[08:21] <tuxinator> hi all
[08:21] <tuxinator> i cant figure out if mysql on ubuntu is compiled with openssl support or not
[08:22] <tuxinator> it looks like have_openssl is only a pointer to have_ssl in mysql?
[09:09] <coalwater> ls
[09:09] <coalwater> lol
[09:09] <coalwater> how do i install package 'quickly' on debian
[09:09] <coalwater> can't find the ppa
[09:17] <xnox> @pilot in
[10:06] <cjwatson> bdrung: Thanks (libibmad)
[10:56] <ev> mpt: why is silent error types just restricted to errors that occur during logout/shutdown? Shouldn't all internal errors be hidden behind the "report previous internal errors" checkbox too? (https://wiki.ubuntu.com/ErrorTracker#error)
[11:18] <mpt> ev, it isn't, that's just the kind we'd been definitive about so far. That's why it's a bulleted list. :-)
[11:18] <ev> ah, right
[11:19] <ev> so can I add non-desktop applications to that list?
[11:19] <mpt> Which ones?
[11:19] <mpt> If pulseaudio crashes, for example, that's an internal error that's going to be obvious to the user.
[11:19] <mpt> Or network-manager.
[11:20] <mpt> (Assuming that they were using sound or networking at the time.)
[11:20] <ev> hm, yeah
[11:21] <ev> if we were getting so precise as to separate out those cases, would it not also make sense to give them special wording?
[11:21] <ev> so, "sorry but your ability to hear sound may be hindered" rather than "an internal application crashed"
[11:21] <ev> something to that effect
[11:22] <ev> I guess I'm just worried that sometimes they'll see "an internal error occurred" and sometimes they wont, and it wont be clear why that's the case
[11:26] <mpt> ev, maybe. It depends how many we whitelist or blacklist, or whether there's a non-whitelist/-blacklist way of distinguishing them.
[11:26] <ev> sure
[11:30] <mpt> ev, perhaps we could go through the leaderboard and sort the non-application packages into those two categories
[11:31] <mpt> as a way of deciding whitelist vs. blacklist
[11:31] <ev> sure
[11:32] <ev> whenever you'd like
[11:35] <mpt> Thursday?
[11:40] <ev> mpt: sure
[13:10] <blami> hi, do I understand correctly that the output of complete multilib transition is that under /lib will be platform directory containing all libraries and current state is mixture of past and future, or am I missing whole thing?
[13:26] <didrocks> hey cjwatson, infinity: jibel told me that libbamf3-1 was in universe? I don't really understand what happened: I promoted it to main (from proposed) Friday, just after the copy happened for the daily release.
[13:27] <didrocks> cjwatson: infinity: I think that's why britney migrated it (once we rebuilt the rdepends because of the soname change) to the main pocket
[13:27] <didrocks> but then, in main, it was back in universe?
[13:27] <didrocks> s/in main/ in the release pocket/
[13:29] <xnox> didrocks: there is a bug where packages fall back into universe, after they are copied from -proposed to -release pocket.
[13:30] <xnox> =/ so most things need to be promoted twice.
[13:30] <didrocks> xnox: ah, so not related to the daily release at all. For future, it's the case everytime? So we need to repromote after the copy?
[13:30] <didrocks> ok, got it, good to know :)
[13:30] <didrocks> thanks xnox
[13:31] <xnox> didrocks: yes. daily release was all good.
[13:31] <xnox> np.
[14:42] <roaksoax> howdy! I was wondering if anyone know if it is possible to determine is package A is to be installed (or has been installed) in package B postinst script?
[14:42] <pitti> roaksoax: you cannot install packages from postinst scripts, as apt/dpkg are not recursive
[14:42] <pitti> (the first will lock the dpkg db)
[14:43] <roaksoax> pitti: yeah I don't want to install a package I just want to determine whether another package has been installed or is to be installed (and if that's even possible)
[14:43] <pitti> roaksoax: oh sorry, you mean if it already is installed? dpkg -s pkgname >/dev/null 2>&1
[14:43] <pitti> "about to be installed" would be looking into the future
[14:44] <pitti> you can check whether it's unpacked, but not configured yet by looking at the "Status:" line
[14:44] <roaksoax> pitti: right let's say I do: sudo apt-get install meta-package which installs package A and B. Package B gets installed first but I want to know whether A is to be installed or not
[14:44] <pitti> but apt doesn't unpack everything before it starts configuring, it does that stuff in batches
[14:44] <pitti> roaksoax: not sure what you want to do, but that's usually the kind of stuff triggers are for
[14:45] <pitti> so that an already installed package can do stuff when another package gets installed later on
[14:45] <roaksoax> pitti: alright cool! I;ll look into triggers. Thanks for the info :)
[14:45] <pitti> roaksoax: "man deb-triggers" FYI
[14:45] <roaksoax> thanks :)
[14:48] <tumbleweed> checking whether it's unpacked (instead of using triggers) just sounds like a recipe for non-deterministic behavior
[15:10] <arges> tyhicks: hey. I can't seem to find bug 1052038 on the pending SRU queue. I think last time we spoke this was ready to go right?
[15:18] <sconklin> @pilot in
[15:25] <cjwatson> blami: Basically yes
[15:26] <cjwatson> blami: (Though you mean multiarch, not multilib - multilib is something different)
[15:46] <hrw> sconklin: bug 1085392 maybe?
[15:46] <arges> zul: hello! I'm looking at the cinder FTBFS failure. Looks like a patch that skips the failed tests wasn't enabled. Does it make sense to enable this patch 'skip_failed_tests' and fix the ftbfs?
[15:49] <sconklin> hrw: Sorry to say, I'm a kernel guy, and only tend to look at kernel bugs
[15:50] <hrw> sconklin: ok, was worth trying ;D
[15:55] <zul> arges: yes penable it
[15:56] <arges> zul: okey dokey
[15:59] <GuidoPallemans> I'm making a Reddit reader for the phone! Anyone care to join? https://github.com/brambram/UbuntuPhoneRedditApp
[16:46] <xnox> hrw: now you can bug members of ~ubuntu-sru team to accept alsa packages from bug #1085392 E.g. infinity =)
[16:50] <tyhicks> arges: Yes, it has been ready to go for quite a while now. It just isn't getting any attention from ~ubuntu-sru, IIUC.
[16:51] <arges> tyhicks: well I don't see it on the list: http://people.canonical.com/~ubuntu-archive/pending-sru.html , so wasn't sure why that was
[16:52] <tyhicks> arges: Lets bug a member of the ~ubuntu-sru team to find out
[16:53] <tyhicks> infinity: Since you were pinged above for another SRU, can you take a look at bug 1052038 ? It has been sitting for a while now.
[19:52] <dkessel> hello guys. i have a question: under which circumstances does the bluetooth indicator icon get added to the indicator bar?
[19:52] <dkessel> i am asking because i seem to have a false positive...
[19:55] <roadmr> cyphermox probably knows :)
[20:02] <cyphermox> dkessel: if there is a bluetooth type device
[20:02] <cyphermox> dkessel: it kind of surprises me; maybe you have a device somewhere that says it does bluetooth even if it doesn't
[20:02] <cyphermox> or if you're using some of those logitech dongles for mice and keyboards
[20:03] <dkessel> cyphermox, i have a dell netbook. they sell the bluetooth module as an addon. but i don't have it. but i guess that explains it somehow...
[20:03] <sarnold> does it work anyway? :)
[20:03] <cyphermox> no, you should actually have a bluetooth device for the indicator to show up ;)
[20:04] <dkessel> tbh i tried to use it :)
[20:04] <dkessel> but as i don't have the module.... nothing
[20:04] <cyphermox> dkessel: what does hciconfig return?
[20:04] <dkessel> cyphermox, nothing
[20:04] <cyphermox> O.o?
[20:05] <dkessel> do i need some parameters?
[20:05] <cyphermox> going to have to look at the code
[20:05] <cyphermox> no
[20:05] <dkessel> :)
[20:05] <cyphermox> if there is a device it should be listed there
[20:05] <dkessel> funny
[20:06] <sarnold> I have to click the indicator and "turn on bluetooth" to get output from hciconfig on my machine..
[20:06] <infinity> Ditto.
[20:06] <infinity> Something's smart enough to know I have bluetooth, despite it being currently disabled/disconnected/whatever.
[20:07] <infinity> In fact, I can't even enable it from the indicator, cause it's hard-disabled by the machine.
[20:07] <dkessel> even if i do that, there's no output from hciconfig
[20:07] <roadmr> infinity: maybe something's dumb enough to assume you do; the smarts to know the device has to be enabled are yours :P
[20:07] <infinity> (But I still have the greyed-out indicator, until I undo my hardware rfkill)
[20:07] <slangasek> dkessel: what does 'rfkill list bluetooth' show?
[20:07] <roadmr> dkessel: udevadm info --export-db  |grep -i blue, does that say anything? (this is how checkbox looks for bluetooth so I'm guessing no, but may be interesting)
[20:09] <dkessel> slangasek, http://paste.ubuntu.com/1535302
[20:10] <stgraber> dkessel: can you paste the output of "dmesg"?
[20:11] <dkessel> roadmr, http://paste.ubuntu.com/1535311
[20:12] <roadmr> dkessel: thanks! so it looks like rfkill may be used to decide whether to display the indicator?
[20:13] <dkessel> stgraber, dmesg: http://paste.ubuntu.com/1535314
[20:14] <slangasek> roadmr: well, I think the indicator is displayed based on the presence of the underlying features that rfkill is also exposing
[20:14] <stgraber> thanks. So yeah, it looks like the applet is showing up when either you have a bluetooth device or the rfkill driver reports that you have one that can be turned on
[20:14] <roadmr> slangasek: well put, thanks :)
[20:15] <stgraber> not sure exactly how rfkill works, but I suspect it's getting the information from the firmware somehow (ACPI?) and that something's wrong somewhere in there
[20:15] <slangasek> dkessel: what's the output of 'ls -ld /sys/class/rfkill/rfkill3/device'?
[20:16] <dkessel> that takes a bit longer to type :) sec
[20:17] <dkessel> lrwxrwxrwx 1 root root 0 Jan 15 21:16 /sys/class/rfkill/rfkill3/device -> ../../../compal-laptop
[20:17] <slangasek> mmk
[20:18] <slangasek> so either the hardware claims to have a bluetooth interface, or the compal-laptop module has a bug
[20:19] <stgraber> dkessel: sorry, those are long paths. "cat /sys/class/rfkill/rfkill3/device/device/vendor" and "/sys/class/rfkill/rfkill3/device/device/device"
[20:19] <dkessel> :D
[20:20] <dkessel> i just found a new use case for ubuntu one... :)
[20:20] <stgraber> the first one should give you the hardware vendor id, the second one should give you the hardware product id
[20:20]  * dkessel pastes command lines
[20:20] <stgraber> oh, and I forgot cat in front of the second one, but you probably notice that ;)
[20:21] <dkessel> stgraber, file not found on first "vendor"
[20:22] <dkessel> stgraber, ...and another file not found on "device"
[20:23] <dkessel> shall i paste the contents of /sys/class/rfkill?
[20:23] <stgraber> ok, so based on what I'm seeing here, that'd mean that the driver isn't tied to a physical device (as /device/device should have pointed to the PCI or USB device)
[20:25] <stgraber> looks like a kernel bug to me... the compal-laptop driver always reports two rfkill entries even if the hardware isn't there
[20:26] <stgraber> I just tried it on my laptop with "modprobe compal-laptop force" (the force keyword is to bypass the DMI check) and I got two extra rfkill entries
[20:27] <dkessel> i would probably need help on how to properly file that bug
[20:27] <stgraber> http://paste.ubuntu.com/1535349/
[20:28] <stgraber> dkessel: do "ubuntu-bug linux" on your machine, once you have the bug filed on Launchpad give me the bug number and I'll see if there's something that should be added
[20:29] <dkessel> stgraber, will do
[20:31] <dkessel> hmm... "it appears you are currently running a mainline kernel".... meh - apport won't let me report... i'm running raring
[20:31] <stgraber> dkessel: fun... then go directly to https://launchpad.net/ubuntu/+source/linux/+filebug
[20:32] <stgraber> dkessel: and once the bug is filed, do "apport-collect <bug number>", that one should work without complaining too much
[20:35] <dkessel> launchpadlib would be part of ubuntu-dev-tools, i guess....
[20:39] <hrw> xnox: thanks man!
[20:45] <dkessel> stgraber: bug 1100004 . apport really didn't put much info in it...
[20:52] <stgraber> dkessel: posted a comment asking for a bunch more things that should help the kernel team get a fix matching your hardware
[21:07] <dkessel> stgraber: that sure spammed some people's mail folders :) well - thanks for the help!
[21:08] <stgraber> dkessel: oh, they're used to it ;)
[21:09] <dkessel> :D well I gotta go, see you :)
[22:09] <romaxa> which channel is hosted for ubuntu-phone people?
[22:09] <sarnold> romaxa: I think #ubuntu-phone
[22:10] <romaxa> ;_)
[22:17] <GuidoPallemans> where can I file QtQuick Ubuntu.components bugs?
[23:17] <sconklin> @pilot out
[23:30] <xnox> @pilot out
[23:30]  * xnox is back from volleyball ;-)
[23:30] <xnox> hrw: no problem. I accept payments in cider, monkey nuts and bird seeds =)
[23:55] <tkamppeter_> Does someone know how one makes the Pandaboard boot from a USB stick?