[02:12] <balloons> anyone ever have there ppa build fail? I see the log, but I don't understand why it failed to build. https://launchpadlibrarian.net/98350420/buildlog_ubuntu-precise-i386.checkbox_0.13.5ubuntu1_FAILEDTOBUILD.txt.gz
[02:12] <balloons> bah.. I see it, sorry for false alarm :-)
[02:13] <imbrandon> copying checkbox/reports/xml_report.py -> build/lib.linux-i686-2.7/checkbox/reports
[02:13] <imbrandon> error: package directory 'checkbox_cli' does not exist
[02:13] <imbrandon> dh_auto_build: python setup.py build --force returned exit code 1
[02:13] <imbrandon> make[1]: *** [override_dh_auto_build] Error 1
[02:15] <balloons> yep. I missed that the first time, I just saw the error build 2.. I know how to fix. thanks imbrandon
[02:21] <barry> lifeless: mailman 3 supports sqlite and postgres currently (hopefully someone will donate mysql support)
[02:22] <lifeless> barry: so, just so you know, using timezones in the DB layer is pretty crackful
[02:22] <barry> lifeless: also, martin von loewis is working on a python 3 port of storm.  it would be awesome to eventually land that
[02:22] <barry> lifeless: i only care about utc
[02:22] <lifeless> barry: so storm supports utc already
[02:22] <barry> lifeless: not so much
[02:22] <lifeless> barry: thats what timestamp without timezone columns are
[02:22] <jamesh> lifeless: it is probably okay to use time zones in the database layer if every subscriber to every list on the system is in the same time zone
[02:22] <lifeless> barry: AIUI
[02:23] <barry> the problem is it chokes parsing +00:00 suffixes
[02:23] <lifeless> jamesh: a pretty narrow case :)
[02:24] <jamesh> yep, I'd recommend using "timestamp without time zone" columns with PostgreSQL -- a connection level time zone is not particularly useful for any task where you're doing work on behalf of multiple users with a single connection
[02:25] <jamesh> so best to ignore the feature
[02:25] <lifeless> its also dangerous
[02:25] <lifeless> if you do any manual sql it *won't* do what you might expect
[02:25] <barry> i'd be happy if it parsed the tz string and threw an exception on anything that wasn't +00:00
[02:25] <lifeless> barry: if what parsed the tz string?
[02:26] <barry> _parse_time() in storm/variables.py
[02:26] <lifeless> jamesh: barry: -> #storm I guess
[02:27] <ScottK> Don't distract barry.  He's got stuff to fix in his packages in Debian.
[02:27] <barry> ScottK: ouch ;)
[02:27] <ScottK> (you got the PM, I assume)
[02:28] <ScottK> It will get extremely more painful to get the package renames fixed up if we don't get them into precise.
[02:29] <mwhudson> jamesh: i bet you like django then
[02:29] <jamesh> mwhudson: Django is awesome.
[02:30] <mwhudson> jamesh: did i ever show you this bug? https://code.djangoproject.com/ticket/17062
[02:30] <mwhudson> jamesh: it's pretty awe-ful
[02:32] <jamesh> mwhudson: that'll teach you for relying on connection level time zones :)
[02:33] <mwhudson> jamesh: yep, or relying on people who etc
[02:34] <jamesh> you seem to be getting more developer attention than my django bug (admittedly mine was closer to a new feature request than a bug)
[02:35] <mwhudson> yeah, the bug was fixed quite quickly
[02:35] <mwhudson> (and without me noticing, yay trac!)
[02:35]  * jamesh is still waiting on https://code.djangoproject.com/ticket/16674
[05:38] <pitti> Good morning
[07:09] <dholbach> good morning
[07:11] <diwic> good morning dholbach
[07:11] <dholbach> hi diwic
[07:12] <diwic> question to anyone, I've heard good things about xbmc so I was considering installing it, but it seems to be not in the official repositories but in a PPA. Why?
[07:13] <micahg> diwic: debian 469397
[07:13] <pitti> Daviey: I assume I should move bug 844995 to final now? Or do you think you guys can fix kombu for b2 still?
[07:14] <diwic> micahg, thanks *reading*
[07:27] <pitti> infinity: do you still plan to work on bug 759545?
[07:30] <pitti> Daviey: do you consider bug 959683 urgent enough to keep it at b2? I think it's fine to move to final, WDYT?
[08:39] <infinity> pitti: I've already promised Daviey I'd find a fix before final (I intend to work on it this week).
[08:40] <infinity> pitti: But unless I fix it Monday, I think we're better off moving the milestone, yeah.
[08:49] <ritz> weird, bzr branch of gtk+3 fails
[08:49] <ritz> $ bzr clone  lp:ubuntu/oneiric/gtk+3.0
[08:49] <ritz> The command 'bzr clone' has been deprecated in bzr 2.4. Please use 'bzr branch' instead.
[08:49] <ritz> bzr: ERROR: Revision {james.westby@ubuntu.com-20110720104429-q7mz8vnm20mly8y4} not present in "Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))".
[08:50] <ritz> nm, https://bugs.launchpad.net/bzr/+bug/888841
[09:02] <ev> cyphermox: is there anything blocking us from setting up a server for the network manager connectivity check? We could potentially throw something on start.ubuntu.com, like the already-existent http://start.ubuntu.com/connectivity-check.html
[09:10] <pitti> infinity: ack, thanks
[10:32] <hrw> http://marcin.juszkiewicz.com.pl/2012/03/26/ubuntu-12-04-precise-and-cross-compilation-of-arm-kernels/ - refreshed instructions for precise. Thanks for everyone who helped to make it so easy
[11:33] <zyga> hi
[11:34] <zyga> on current precise I get very often double-event for every mouse button press
[11:34] <zyga> I never had this before the upgrade
[11:34] <zyga> running xev it seems that almost every button press is registered as two consecutive press and release events
[11:35] <zyga> http://pastebin.ubuntu.com/900292/
[11:36] <zyga> is there anyone that experiences similar issue?
[11:36] <zyga> it's turning anything that requires double-click into a single-click operation
[11:46] <jdstrand> @pilot in
[11:59] <cjwatson> mvo: bug 839986 looks like http://paste.ubuntu.com/900317/, but would you prefer to also change python-apt to return None from .uri in such cases?  (That wouldn't fix the whole problem; _guess_third_party_changelogs_uri_by_source would still need a change anyway.)  I don't know what you think is most correct here
[12:04] <cjwatson> @pilot in
[12:04] <cjwatson> I should probably do some of this
[12:05] <mvo> cjwatson: I think None makes sense
[12:07] <cjwatson> mvo: want a python-apt task then?
[12:07] <cjwatson> and I'll just apply the 'if not deb_uri:' part of that
[12:07] <cjwatson> (to update-manager)
[12:08] <mvo> cjwatson: a python-apt task for this would be nice, yes
[12:08] <mvo> cjwatson: thanks, that sounds like a good approach
[12:12] <mvo> cjwatson: I guess http://paste.ubuntu.com/900332/ is all we need in p-apt?
[12:12] <rbasak> If I'm preparing an upload for a bugfix by taking someone else's patch to a debian/patches/... file and only adding a changelog entry, and the only change is the bugfix, should I be using his name or my name to sign the changelog entry?
[12:14] <cjwatson> rbasak: his
[12:14] <rbasak> cjwatson: ok, thanks!
[12:15] <cjwatson> rbasak: it's acceptable to use yours and say "thanks, Person's Name", but using their name is more polite because it shows up in their +uploadedpackages or whatever it is in LP and is easier to find in applications for upload rights
[12:59] <cjwatson> jamespage: https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355 - I kind of feel uncomfortable overruling you on the bug, but it really isn't good form to change the packaging around in an Ubuntu patch, and I don't think we should be advising patch submitters to do it
[12:59] <cjwatson> if the package is laid out in 1.0 style such that patches are applied directly, it's OK for Ubuntu modifications to follow that
[13:00] <cjwatson> and much easier to merge later
[13:03] <jamespage> cjwatson, looking (can't remember the bug)
[13:09] <jamespage> cjwatson, ack - thats a fair point - please continue to feel free to overrule me when I'm going off on one....
[13:10] <cjwatson> jamespage: perhaps you could sort out the bug and do something that seems sensible, when you get a minute?  I also don't want to confuse the reporter overly
[13:11] <jamespage> cjwatson, leave it with me - he actually did alot more that I expect him todo
[13:12]  * cjwatson nods
[13:12] <cjwatson> thanks
[13:13] <jamespage> cjwatson, np - thanks for pointing out my sometimes over zealous nature!
[13:18] <stgraber> seb128: I added a comment to bug 331369 but didn't change it back to Triaged as I didn't have time to read through the whole history to see if someone decided that the current (in my view broken) behaviour is the "right" one
[13:20] <seb128> stgraber, talking to the wrong guy, you want to talk to MacSlow or design, I've nothing to do with notify-osd
[13:22] <stgraber> seb128: ok :) just poked you as you are commented-last on the LP bug
[13:22] <stgraber> MacSlow: ^
[13:25] <MacSlow> stgraber, talking about 331369?!
[13:27] <MacSlow> stgraber, well this decision is from Design... you have to talk to them... or you could try setting to com.canonical.notify-osd:multihead-mode "focus-follow"
[13:27] <MacSlow> stgraber, which would notification bubbles appear on the monitor with the currently focused window
[13:29] <stgraber> MacSlow: oh, I didn't know of multihead-mode, I guess I'll just set that then
[13:29] <MacSlow> stgraber, you know how to use gsettings for that?
[13:30] <stgraber> MacSlow: yep
[13:30] <MacSlow> stgraber, as values for that key use either "focus-follow" or "dont-focus-follow"
[13:37] <jdstrand> pitti: hi! these two merges against lp:ubuntu are in proposed now. can you set the status on them?
[13:37] <jdstrand> https://code.launchpad.net/~utlemming/cloud-init/cloud-init-lp948461_sru_oneiric/+merge/98014
[13:37] <jdstrand> https://code.launchpad.net/~utlemming/cloud-init/cloud-init-lp942061_sru_natty/+merge/97997
[13:38]  * soren contemplates whether we're approaching a record breaking short amount of time before the release to reveal what the next release is going to be named
[13:41] <soren> Hm.. "Precise" was announced 8 days before Oneiric's release. I guess there's still a bit of a way to go before we're in record breaking territory.
[13:41] <soren> *shrug*
[13:42] <cyphermox> ev: not much is stopping us really, and http://start.ubuntu.com/connectivity-check.html is pretty much sufficient
[13:43] <ev> cyphermox: we'd have to patch n-m though, surely? As it expects either a http header or "NetworkManager is online"
[13:43] <ev> or perhaps I've read the code wrong or missed an optional argument
[13:43] <ev> but that's excellent news
[13:43] <cyphermox> ev: that is, if you forget about the fact that enabling connectivity checking like this in ubiquity is going to be subject to FF; and adding a check is always scary to some
[13:44] <cyphermox> ev: no, I thought you could specify what to check for
[13:44] <ev> well, ubiquity already has a connectivity check built around this. I'm happy to move that in precise+1
[13:44] <ev> I'm more concerned about bug 964508
[13:44] <ev> err and it doesn't directly relate to this
[13:45] <ev> bug if I'm putting code in to check NM for the connection type
[13:45] <ev> then we get this for free
[13:46] <cyphermox> ev: don't bother, it's already supposed to be available :)
[13:46] <ev> what do you mean?
[13:47] <ev> oh, I see
[13:47] <ev> indeed, but that's what I mean by it being only loosely related
[13:47] <ev> it would be nice if whoopsie didn't throw several megs of core dump at a captive portal page
[13:47] <cyphermox> well, just like any other application probably shouldn't try to load up and talk to a portal page...
[13:48] <cyphermox> ev: for device type checking, getActiveDevice via DBus will give you the active device; you can then ask it its type
[13:49] <ev> right, and that's what I'm doing (GetActiveDevices) - but it would still be nice to have the captive portal stuff so we don't think we're online and sending successful crashes when we are not.
[13:49] <ev> err ActiveConnections
[13:50] <ev> then iterating over that to find the types
[13:50] <ev> and bailing out if we find any that are 3g/modem
[13:50] <cyphermox> aye
[13:50] <cyphermox> oh... but then don't you risk bailing out if a 3g modem is connected but not the default route?
[13:50] <ev> indeed
[13:50] <ev> I was just going to say :)....
[13:51] <ev> suggestions welcome for how I pick the right interface to feed libcurl when there are both 3g and non-3g connections present
[13:53] <cyphermox> ev: I think you don't need to pass an interface in this case, it should magically work.
[13:54] <ev> ah, wonderful
[13:54] <cyphermox> (because whatever you're trying to access should be behind the default gateway)
[13:54] <cyphermox> so, for connectivity checking, feel free to experiment with it, I think I still have the excerpt for testing
[13:55] <cyphermox> or maybe not
[13:56] <cyphermox> essentially it's something like [connectivity]\nuri=http://start.ubuntu.com/connectivity-check.html\nresponse=Lorem ipsum
[13:56] <ev> yay
[13:59] <cyphermox> ev: from there if you look at the NM logs it will write an error in syslog if it fails, but IIRC continue silently if everything is fine
[13:59] <ev> cyphermox: cool, cheers
[13:59] <cyphermox> I don't see how you can connect that to just whoopsie though; seems like more of a system-wide thing
[14:00] <cyphermox> .... which I'm not sure I want to see exploding in precise :)
[14:01] <smw> Hey guys, can anyone answer a couple questions about version policy of packages? There is a programming language called go that is currently in RC2 and about to reach 1.0 status. Right now ubuntu has the "r60" version that is extremely old. Would ubuntu not update to 1.0 until the next release?
[14:02] <smw> Would there be any way to include the RC2 and then upgrade to the 1.0?
[14:03] <smw> r60 is practically a different language and will be useless when 1.0 comes out.
[14:04] <smw> (I am asking if there is a way to get it into the LTS or if it would need to wait for 12.10)
[14:04] <cyphermox> smw: afaik just needs somebody to do the work of updating the package
[14:05] <geser> and probably a FFe too
[14:05] <cyphermox> and of course have the feature freeze bug to go with the features added into your rc2 or 1.0
[14:05] <cyphermox> yeah
[14:05] <smw> cyphermox, what?
[14:06] <geser> smw: when is 1.0 planed to get released?
[14:06] <ev> cyphermox: I wont have to connect it to just whoopsie. But without it, whoopsie will interpret CONNECTED_GLOBAL to mean it can see out to the Internet, when the system might actually be behind a captive portal.
[14:06] <smw> geser, they refuse to give a time. The last two weeks were officially RC1 and RC2
[14:06] <smw> geser, I would say 1.0 is very soon.
[14:06] <cyphermox> ev: yeah, but that's not unlike it's been for the last forever :)
[14:06] <ev> :)
[14:07] <cyphermox> ev: so to me it feels very late to change this kind of default
[14:07] <smw> geser, you will not find that mentioned on the site, but I can show you release announcements on google groups from the google DevRel saying it is RC2 ;-)
[14:08] <cyphermox> especially without knowing how it might run with people over 3g in different setups, of the russians who need to connect to a vpn to get online, or those who have a firewall blocking the start.ubuntu.com page or some other thing :)
[14:08] <cjwatson> smw: it would help to get it updated in Debian, as we currently sync that package verbatim from there
[14:08] <geser> smw: 12.04 is about to release end of April, so there is not much time to release it, package it and get it into the archive for 12.04 (if an exception is granted to update the package that late)
[14:08] <cjwatson> it's not *essential* but it smooths the wheels a lot
[14:08] <smw> cjwatson, hm...
[14:08] <ev> cyphermox: sure, we can push that to +1 with the understanding that our crash reports statistics will be potentially missing data from systems behind captive portals
[14:09] <cjwatson> nobody seems to have even filed a Debian bug about any newer golang releases yet
[14:09] <smw> cjwatson, right now RC2 is debian's golang-weekly
[14:09] <smw> cjwatson, that is because RC2 was another weekly.
[14:09] <cjwatson> right, but there's a golang package which is supposed to be something you might actually use rather than a rolling snapshot
[14:09] <cyphermox> ev: I feel that's safer; but I'm open to having the decision taken above my head by foundations; if you think the benefit outweights the risks and relative newness of that feature.
[14:09] <smw> cjwatson, but no one would actually use r60 anymore
[14:10] <cjwatson> sure, but in principle that's what the non-weekly package is for
[14:10] <cjwatson> it should be upgraded if there's a newer actual release
[14:10] <smw> cjwatson, one sec
[14:10] <ev> cyphermox: nope - I think you're right. :)
[14:10] <smw> cjwatson, http://groups.google.com/group/golang-nuts/browse_thread/thread/b3dae81308fe654d/0b3b9e48efad3d17?show_docid=0b3b9e48efad3d17
[14:11] <cjwatson> um, I should clarify, I have no personal involvement with golang
[14:11] <cjwatson> just giving general advice
[14:11] <smw> cjwatson, they are right now in API/feature freeze for go1 .0.
[14:11] <vibhav> Is there any limit to the number of FFe's that can be requested after Feature Freeze?
[14:11] <smw> vibhav, FFe?
[14:11] <cjwatson> I don't really need to see the release announcement :)
[14:11] <cyphermox> ev: I don't have enough experience with how it might fly with some of the hairier internet connection methods; I think this particular thing would have benefited a lot from being introduced early in the release, and have a nice formal call of testing for each milestone, just in case.
[14:11] <vibhav> smw: Feature Freeze Exception
[14:11] <cjwatson> since I'm not the Debian maintainer here
[14:11] <smw> vibhav, ah
[14:12] <ev> cyphermox: understood
[14:12] <cyphermox> ev: we can definitely look into that for precise+1 though :)
[14:12] <ev> :)
[14:12] <ev> definitely
[14:12] <cjwatson> vibhav: not as such, although if you started flooding us with hundreds of them we might start taking a different attitude ...
[14:12] <geser> vibhav: no limit, but I guess you will become not very liked if you flood them with requests
[14:14] <smw> cjwatson, so I should submit a bug following the feature freeze exception page that says why I think golang-weekly instead of golang r60 should be included?
[14:14] <smw> cjwatson, can you give any tips on what type of information I should provide/use to convince them?
[14:15] <cjwatson> smw: what I suggested was filing a Debian bug asking for the new upstream release to be packaged there
[14:15] <cjwatson> that is the most straightforward way to get this done
[14:15] <smw> cjwatson, it is packaged, but not as "golang"
[14:15] <cjwatson> as "goland"
[14:15] <cjwatson> er, "golang"
[14:15] <smw> cjwatson, I doubt they would do that. They have no reason not to wait.
[14:16] <cjwatson> I can but offer advice
[14:16] <smw> cjwatson, of course.
[14:16] <cjwatson> there is also no reason not to ask :-)
[14:16] <smw> cjwatson, true :-)
[14:17] <cjwatson> (if nothing else, Debian has an "experimental" distribution ...)
[14:17] <smw> cjwatson, but I believe the answer I am going to get is a no. I would not try and push this on debian unstable because there would be no reason. However, ubuntu is about to release an lts so it matters ;-)
[14:17] <smw> cjwatson, yeah, but debian sid has no reason not to wait
[14:18] <cjwatson> we can sync from experimental; that's still easier than doing it locally
[14:19] <vibhav> cjwatson: But What if the exceptions are really good and not simply flood?
[14:19] <smw> cjwatson, yeah, I just have no good reason to convince sid to update ;-)
[14:20] <cjwatson> vibhav: you should just file them then
[14:20] <cjwatson> just bear in mind that the release team is composed of humans
[14:21] <vibhav> thanks cjwatson
[14:22] <cjwatson> vibhav: ... how many are we talking about?  I'm a bit disconcerted by the fact that you feel you need to ask ...
[14:23] <vibhav> cjwatson: I had filed a sync request eariler yesterday for syncing some package, Today I saw a list of bugs which were fixed in Debian and decided to file one more bug too, So I was a bit worried that I might annoy the release team
[14:23] <cjwatson> if you're working in units of one, I don't think you will
[14:23] <vibhav> ah ok
[14:24] <smw> cjwatson, how can I measure the impact of a package? Like get a list of all packages which require it to build or install.
[14:24] <cjwatson> smw: grep-dctrl over files in /var/lib/apt/lists/
[14:24] <smw> thanks cjwatson
[14:24] <cjwatson> neither golang nor golang-weekly has any reverse-dependencies in the distribution right now
[14:25] <cjwatson> or reverse-build-dependencies
[14:25] <smw> cjwatson, you checked?
[14:25] <cjwatson> yes
[14:25] <smw> thanks :-)
[14:25] <smw> cjwatson, damn, even golang weekly is not up to date :-\
[14:25] <pitti> jdstrand: done
[14:26] <jdstrand> pitti: thanks! :)
[14:26] <smw> cjwatson, when go1 is released, would they consider doing the major upgrade after the fact?
[14:26] <smw> cjwatson, since it is a low impact package
[14:27] <cjwatson> smw: maybe; http://wiki.ubuntu.com/StableReleaseUpdates
[14:27] <smw> cjwatson, thanks
[14:27] <cjwatson> the closer precise as released is to 1.0, the easier, though
[14:29] <smw> cjwatson, yeah, r60 is practically another language
[14:30] <smw> cjwatson, r60 was released ages ago. But once go1 comes out... it becomes useless
[14:30] <smw> cjwatson, then again, it is useless now ;-)
[14:40] <smw> cjwatson, yes! the debian packager for golang is an ubuntu person too! This will help :-)
[14:47] <smoser> jdstrand, is bug 964008 ok? we have 3 packages on that MIR. would you like separate ones?
[14:48] <jdstrand> smoser: that works fine. it might be nice to be more explicit than 'All MIR requirements apply to it' for shunit
[14:53] <smoser> jdstrand, i didn't really follow that.
[14:55] <jdstrand> smoser: bdrung tacked on shunit in comment #2 with that comment. that's fine, but it would be better if the mir request info was explicit in the bug for shunit
[14:55] <smoser> i'll update desscription. he added it to summary.
[14:56] <jdstrand> smoser: well, I see that, but I mean things like Maintenance, QA, etc. it is a different package after all :)
[14:56] <smoser> right. i'll update.
[15:17] <cjwatson> @pilot out
[15:43] <Whoopie> cjwatson: thanks a lot for uploading the sflphone package!!!
[15:43] <jhojho> so will precise ship linux 3.3?
[15:44] <cjwatson> Whoopie: you're welcome
[15:45] <jhojho> cjwatson: btw thanks for getting openssl updated...
[15:50] <jdstrand> @pilot out
[16:03] <Whoopie> cjwatson: Can I ignore this build error for sflphone? -> https://launchpadlibrarian.net/98415372/buildlog_ubuntu-precise-armel.sflphone_1.0.2-1ubuntu1_CHROOTWAIT.txt.gz
[16:05] <Laney> LP ops tried to fix that, evidently without success
[16:05] <cjwatson> Whoopie: not your problem, certainly, though it's somebody's problem
[16:06] <cjwatson> Laney: I've re-reported it
[16:06] <Whoopie> cjwatson: ok.
[16:06] <Laney> righto
[16:08] <dholbach> Sweetshark, adam_g, good luck later on! :)
[16:10] <Sweetshark> dholbach: what exactly do I have to expect? will I be grilled with questions or will it just be a quick nod off?
[16:10] <dholbach> Sweetshark, some questions will surely be asked - I don't know if anyone got just waved through
[16:10] <dholbach> :)
[16:45] <cjwatson> Whoopie,Laney: should be fixed now and with any luck won't recur again
[16:45] <cjwatson> (this was the first recurrence, after the first *oc*currence earlier today ...)
[17:03] <cjwatson> Whoopie: https://launchpad.net/ubuntu/+source/sflphone/1.0.2-1ubuntu1/+build/3319843/+files/buildlog_ubuntu-precise-armhf.sflphone_1.0.2-1ubuntu1_FAILEDTOBUILD.txt.gz is a package problem, however ...
[17:06] <cjwatson> Whoopie: new failure, too, the last version built on armhf
[17:08] <Daviey> @pilot in
[17:51] <alexbligh> If I have an old fashioned rc2.d/S99foo init script, what, if anything, stops that running before network interfaces are configured and up; i.e. is upstart interpretting the LSB stuff at the top or are they comments?
[18:06] <jodh> alexbligh: If you look at upstart-events(7) and /etc/init/rc-sysinit.conf, you'll see that the SysV compat services run after all static network interfaces are "up".
[19:03]  * lamont_ ponders how to get unity-greeter to actually show him his username, or a box to type same in, so that he can login to his machine as other than guest
[19:03] <slangasek> using uid < 1000, eh?
[19:03] <seb128> lamont_, get an uid in the normal range?
[19:03] <lamont_> uid=2501
[19:04] <slangasek> oh, really?
[19:04] <lamont_> and it's even in /etc/passwd
[19:04] <lamont_> rather than just relying on libnss-db to actually integrate
[19:04] <seb128> lamont_, do you have accountsservice installed?
[19:04] <lamont_> [SeatDefaults]
[19:04] <lamont_> greeter-session=unity-greeter
[19:04] <lamont_> user-session=ubuntu
[19:04] <lamont_> #greeter-hide-users=true
[19:04] <lamont_> seb128, yes
[19:05] <seb128> lamont_, if you uncomment the hide users you should get a box to type your username,password
[19:05] <lamont_> (I have not smacked things around since adding the # to the front of that last line of lightdm)
[19:05] <lamont_> did not
[19:05] <seb128> did not what?
[19:05] <lamont_> I get a pretty box with "Guest Session" and  "Log in" boxes
[19:05] <lamont_> no where to type a user name
[19:06] <seb128> if you uncomment it you should get a box "other..."
[19:06] <lamont_> let me smack X and all around one more time and see if changing it back helps.
[19:11] <lamont_> seb128, forwarded you the picture of my login screen
[19:12] <seb128> lamont_, can you share your /var/log/lightdm/lightdm.log?
[19:12] <lamont_> minimum-uid=20000
[19:12] <lamont_> I wonder if that's related.
[19:12] <seb128> where do you have that?
[19:12] <lamont_> guest-oaARA0@rover3:/etc/lightdm$ cat users.conf
[19:12] <seb128> urg
[19:13] <lamont_> that was my previous hack to get the user list to not show up on the login screen
[19:13] <seb128> lol
[19:13] <lamont_> since I REALLY DO NOT WANT IT THERE
[19:13] <seb128> yeah, that might be it :p
[19:13] <seb128> set it back to 500?
[19:13]  * lamont_ gives that a stab
[19:13] <seb128> though
[19:13] <seb128> # NOTE: If you have AccountsService installed on your system, then LightDM will
[19:13] <seb128> # use this instead and these settings will be ignored
[19:17] <lamont_> seb128, no change, even with a reboot (since I killed lightdm hard enough that it didn't come back...)(
[19:17] <lamont_> let me get you that log
[19:19] <lamont_> seb128, chinstrap, ~lamont has lightdm.log, x-0*log
[19:19] <seb128> lamont_, lightdm.log: Permission denied
[19:21] <lamont_> bother
[19:21] <lamont_> fixed
[19:21]  * lamont_ tries show-manual-login=true, based on x-0-greeter.log
[19:22] <lamont_> I wonder if that requires restarting lightdm
[19:22] <seb128> lamont_, the greeter is reloaded every time so no
[19:23] <lamont_> seb128, and of course, no scrollback as I bounce thru guest sessions
[19:23] <seb128> lamont_, the greeter is reloaded every time you log in so no need to restart lightdm
[19:24] <lamont_> that's good
[19:24] <lamont_> OTOH, I do have to log out of my guest session to get back there
[19:24] <lamont_> since they seem to get thrown away each time, too
[19:24] <seb128> right
[19:24] <seb128> mterry, there?
[19:26] <lamont_> seb128, see also chinstrap:~lamont/lightdm (copy of /etc/lightdm)
[19:28]  * lamont checks on what accountsservice has to say
[19:28] <lamont> because that may be related
[19:29] <seb128> lamont: you might want to use d-feet and look at org.freedesktop.Accounts on the system bus, but that would be for users to list
[19:29] <seb128> not for the others box to show
[19:30] <seb128> lamont: but you got over my lightdm knownledge, try pinging mterry or robert_ancell when he gets online
[19:30] <lamont_> seb128, ok
[19:30] <lamont_> though another possibility occurs to me... ubuntu-desktop decided to uninstall for a recent update, for the crying
[19:30] <lamont_> brb
[19:31] <lamont> nope.  still hates me
[19:31] <lamont> I'm guessing that neither one of them is here atm
[19:32] <smoser> cjwatson, around ? hallyn says you were looking at some crypto performance stuff recently.
[19:34] <lamont> seb128: do you happen to have a commandline for d-feet?
[19:34] <lamont> and somehow I fear that debugging this is going to require root and GTK
[19:34] <lamont> also, d-feet segvs when run from a vt
[19:35] <seb128> lamont, dbus-send but I'm not enough into dbus to know the syntax for it, I usually just use d-feet :p
[19:36] <cjwatson> smoser: just bug 958430
[19:36] <smoser> i'm seeing some performance regression during https download in precise compared to lucid (bug 963420).
[19:36] <cjwatson> you probably need, like, an actual expert :)
[19:36] <smoser> i'd much rather you not imply that there is an end to your expertise, cjwatson.
[19:37] <cjwatson> try 'openssl speed' comparisons like those in the bug above, if you can identify the right algorithm
[19:37] <lamont> smoser: I agree
[19:37] <smoser> crossing my fingers, i hope that my bug is a dupe of yours.
[19:37] <lamont> seb128: d-feet (run as guest) prompts me for a bus address, which is where I run into ENOCLUE
[19:37] <cjwatson> nope, you already have 1.0.1
[19:37] <smoser> as i had ruled out wget itself.
[19:38] <cjwatson> at various points I have been a performance journeyman and a crypto apprentice, but never a crypto performance expert
[19:38] <seb128> lamont, you can use the menus and connect to the system bus
[19:38] <cjwatson> smoser: might be more like 940230
[19:38] <cjwatson> bug 940230
[19:38] <dr3mro> unity scope cities stopped working is there a fix?
[19:39] <cjwatson> I'm still sort of sceptical as it seems that some of this was deliberate; I'd like to talk with the Debian maintainer before making any precipitate changes there, but haven't got round to it yet
[19:39] <lamont> seb128: User{1000,1001,2501}
[19:39] <hallyn> that sounds similar :)
[19:39] <seb128> lamont, yeah, I'm not sure why the greeter is not listed them then...
[19:39] <lamont> hrm
[19:44] <lamont> seb128: I'm tempted to remove and reinstall lightdm and unity, just to get back to the defaults and see if that makes a difference
[19:47] <mterry> lamont, you had a question?
[19:48] <lamont> mterry: yeah.  "why doesn't unity-greeter let me login as anyone other than guest?"
[19:48] <mterry> lamont, you mean you want a login box where you can type the user?
[19:49] <lamont> or even showing me the user name
[19:49] <lamont> I literally have the option of logging in as guest, or on a VT
[19:49] <lamont> would kind of like to have a gui again
[19:50] <lamont> my preference would be to have the box to type it in
[19:51] <mterry> lamont, well...  you're saying it used to show your name and now it doesn't?
[19:52] <mterry> lamont, you can set "greeter-show-manual-login = True" if you want to force a manual login box where you can type your username in
[19:52] <mterry> lamont, but if it used to show your username and now it doesn't, that might be a separate bug
[19:52] <lamont> mterry: so before, it was showing the username and I killed that evilness by setting the minimum uid to 20000 instead of 500.  Now, after the reboot this morning (probably a week or so worth of updates, sadly), I get told that Guest is all I get
[19:52] <lamont> where do I set greeter-show-manual-login=true?
[19:53] <mterry> lamont, /etc/lightdm/lightdm.conf
[19:53] <mterry> lamont, should be a commented out line setting it to False
[19:54] <lamont> no commented lines in the file at all
[19:55] <lamont> neither show-manual-login=true, nor greeter-show-manual-login=true seems to have any effect.  (when I login to the guest session, and then logout immediately - that should restart the greeter, yes?)
[19:56] <mterry> lamont, add that line (with a capital True) under a [SeatDefaults] section
[19:56] <mterry> lamont, oh, not a capital true.  Or maybe it doesn't matter, but other lines I have don't have the capital
[19:57] <lamont> changing case did nothing
[19:57] <mterry> lamont, you have it under SeatDefaults?
[19:57] <mterry> lamont, oh, logging out like that will restart the greeter, but not lightdm which is giving the greeter the hints
[19:57] <mterry> lamont, so try "sudo restart lightdm"
[19:57] <lamont> yeah - just noticed that
[19:58] <lamont> showing users now, but not the manual box
[19:58] <mterry> lamont, hah, so now we're ignoring your previous setting of minimum ui?
[19:58] <mterry> uid that is
[19:59] <lamont> I reverted that, so we're showing users > 500 again
[19:59] <lamont> but no "Other" or whatever box
[19:59] <lamont> let me try lowercase
[20:00] <lamont> mterry: apperantly, case matters
[20:00] <vanhoof> ogra_: about?
[20:01] <mterry> lamont, ok, sorry for leading you down the wrong path there with True then
[20:01] <lamont> mterry: which makes this update be "greeter-show-manual-login was introduced without correctly detecting the default should be true"
[20:01] <mterry> :)
[20:01] <lamont> for the case where there are no users > minuid
[20:01] <mterry> lamont, default is intentionally false, per design
[20:01] <mterry> lamont, ah, well if no guest login is shown, we would've shown the manual login box
[20:01] <lamont> mterry: correct.  and that default has only taken me a bit over an hour to track down and correct
[20:03] <lamont> so now I'm just back to the small issue that something I did "back when" has effectively made it so that unity 3d works just fine, as long as I don't need a launcher. :(
[20:03] <mterry> lamont, :-/
[20:03] <lamont> mterry: thanks much for the help with this
[20:04] <mterry> lamont, ym, sorry it caused problems
[21:32] <ogra_> vanhoof, yes, for a moment
[21:41] <jdstrand> SpamapS: hi! so, I install aws-status and have python-appindicator, but I don't see anything. where would I expect to see this? does it only show up if I have instances running?
[21:42] <jdstrand> SpamapS: this is in unity-2d if it makes a difference (vm)
[21:50] <SpamapS> jdstrand: it only shows up if you have instances running
[21:50] <SpamapS> jdstrand: now that you ask.. it does seem like we could show it with 0 instances. :)
[21:53] <Sweetshark> micahg: so what was your point about SONAME? I hope it wasnt 'needs a rebuild', thats so obvious I didnt bother with it at all.
[22:18] <hallyn> is there a standard response when a bug is reported and the system is having badcrc messages in syslog?
[22:19] <hallyn> i.e. some tool they could use to further investigate...
[22:19] <hallyn> sorry, lemme move
[22:31] <Whoopie> cjwatson: strange bug, "/usr/bin/ld: cannot find -lpjnath-armv7l-unknown-linux-gnueabi" and more of these.
[22:33] <cjwatson> presumably substitution of the arch name somewhere
[22:35] <Sweetshark> Laney: As micahg seems to be off right now, could you clarify your reservations about transitions?
[22:38] <Sweetshark> (because I think you guys are mistaken there when we talk about LibreOffice)
[22:40] <Whoopie> cjwatson: looking at the amd64 and i386 buildlog, you're right. It's a substitution. But the buildlog looks the same. I don't see why it fails. :-(
[23:11] <Daviey> Is it possible to get upstart potential runlevel status, like chkconfig does?
[23:12] <Daviey> ie, http://pastebin.com/d5L97JJM ..
[23:13] <Daviey> service --status-all , is current status, not potential status.
[23:16] <slangasek> Daviey: by and large no, because runlevels are just one kind of event in upstart and not necessarily the most important one
[23:24] <Daviey> slangasek: thanks