/srv/irclogs.ubuntu.com/2015/08/10/#ubuntu-devel.txt

pittiGood morning04:19
veebersMorning pitti :-)04:23
pitticjwatson, lamont, infinity: most of the virt builders are "cleaning", looks like they're stuck?05:26
pittiwgrant: ^ or maybe you know05:28
wgrantpitti: Let me see.05:29
wgrantThat is rather broken indeed.05:29
pittiI'm going to put another big chunk of work on the buildds soon /me sighs at g++05:30
wgrantpitti: Ah, no, it's fine.05:30
wgrantJust lots of small kubuntu-ci builds.05:30
pittiand they don't manifest as an actual build, but as "cleaning"?05:30
wgrant(ubuntu-archive-tools' "manage-builders -v" is informative here; it whines when things are stuck for more than a few minutes)05:31
wgrantkubuntu-ci has a lot of small builds starting at the same time.05:31
wgrantSo they all finish quickly, and leave a lot of builders cleaning at the same time, so they queue a bit.05:31
pittiwgrant: ah, ok; thanks for checking!05:31
pitticjwatson, lamont, infinity: unping then ^05:31
wgranthttps://lpstats.canonical.com/graphs/BuildersActiveVirtual/20150810/20150811/ <- suddenly a queue from nowhere.05:32
wgrantWe can possibly increase the reset concurrency a bit now, but it's very rarely a problem like this.05:32
wgrantAnd this'll resolve itself in maybe 10 minutes.05:32
=== ara_ is now known as ara
dholbachgood morning07:33
=== _ is now known as Guest58868
darkxstjdstrand, thoughts on https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1466290/comments/13? core GNOME is pretty blocked on this and feature freeze is fast approaching08:00
ubottuLaunchpad bug 1466290 in gnome-online-accounts (Ubuntu) "Update to 3.16" [Medium,New]08:00
dokopitti, do you care about http://autopkgtest.ubuntu.com/packages/a/apport/wily/amd64/08:04
pittidoko: yes, I do; I just fixed one regression, looking at the other right now08:04
pittidoko: related to the first one -- is it really intended to have /usr/bin/gcc-5 instead of /usr/bin/gcc-5.2 ?08:05
pittidoko: (it's one of the issues that hold up binutils and gcc-5)08:05
pittilintian also ought to be fixed now08:06
pitti(didn't run yet)08:06
dokopitti, yes, next major release will be 6.x08:07
highvoltagewin 2608:12
dokoLaney, pitti: could you work on more "binNMU's" today?09:03
pittidoko: I could; I'm currently working on finishing some transitions that we started in Ubuntu, resolving FTBFS etc.09:04
pittinot sure what is more urgent09:04
Laneygoing to look at the state soon09:04
dokogood as well09:04
LaneyI'm working on a deduplication script for the tracker atm09:05
dokolooks like slangasek wants to force gcc-5 and gcc-defaults to -release tonight to see what else migrates09:05
pittiah, my merged lintian passes again \o/, that should unblock another 4 packages09:07
pittidoko: doing a final test run of apport, then uploading this; should unblock binutils and gdb09:08
* pitti runs for some errands while this runs09:09
pittidoko: right, this should flush quite some things, e. g. gcc5 -> mozjs24 -> {gjs,cjs} (and presumably much more)09:12
pittifrom a quick look, all teh regressions in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gcc-5 also appear somewhere else (where they are better to track)09:12
dokopitti, I'm working with kubuntu to get the kde related things done. however there are four others: ruby-re2 libwx-scintilla-perl gprbuild freecad09:16
dokonow afk, going back home with the train09:16
ricotzpitti, hey :), some likely important packages which aren't on that list: scribus, vlc09:20
pittidoko: I'm already looking on freecad09:22
pittidoko: ruby-re2 needs transition of re2, I can NMU to Debian/sync/re-build in Ubuntu09:23
pittiplease use the pad -- tracking on IRC is too hard09:23
pittidoko: adding re2 for me09:25
pittiricotz: scribus and vlc don't have autopkgtests; doko's list was regressions from http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gcc-5 which aren't KDE-ish10:04
=== dholbach_ is now known as dholbach
Mirvseeing libcolumbus1v5 rename brigs me the memory that no-one has really combed the libraries that are actually deprecated and not in use anymore... there's cruft from earlier phone efforts in the archives10:40
pittiMirv: please do let us know which ones we can just remove10:40
Mirvyeah, worth doing so10:41
Mirvlet me think a bit and see if I come up with any that I can verify10:41
Mirvpitti: ok I've some 15 source packages now collected.. made a pad for it: http://pad.ubuntu.com/drop-obsolete-phone-packages11:04
Mirvsil2100: can you check the above too? ^ and say if something seems not to be removed from archives in wily11:04
Mirvpete-woods: are libcolumbus, unity-voice and libdbusmenu-qt to be continued to be used on 16.04 LTS unity 7 desktop?11:06
pete-woodsMirv: unity-voice technically isn't used any more11:06
pete-woodsbut the others are11:06
pittiMirv: thanks! will process once sil2100 signs off11:06
pete-woodsunity-voice has a dependency, though11:06
pete-woodsso would need to remove that from HUD first11:06
pete-woodsthen you will also get space savings from the voice definition files11:07
Mirvpete-woods: yes, I noticed I've unity-voice installed on my desktop11:07
pete-woodsMirv: it's not used, because there is no UI to invoke the voice recognition any more11:07
pete-woodsafter HUD was pulled from the phone11:08
Mirvpete-woods: thanks for the explanation! so some benefit could be had by at least dropping the dependency. I filed bug #1483210 now.11:09
ubottubug 1483210 in hud (Ubuntu) "drop unity-voice dependency from HUD, remove unity-voice from archives" [Undecided,New] https://launchpad.net/bugs/148321011:09
pete-woodsMirv: thanks11:09
* sil2100 looks11:11
Laneycan anyone see why https://launchpad.net/ubuntu/+source/open-vm-tools/2:9.10.2-2822639-1ubuntu2/+build/7763199 happens?11:21
pittiLaney: hm, seems to work in my amd64 -proposed chroot11:22
pitti"apt-get build-dep open-vm-tools", I mean11:22
Laneyright, I tried sbuilding it11:23
cjwatsonLaney: open-vm-tools is in main, the mentioned build-deps are in universe11:50
cjwatson... and with that, holiday11:50
Laneyhuh11:50
LaneyOh, there was a new upstream release waiting in proposed already11:51
LaneyI had subconsiously discounted that due to it only being a no-change rebuild11:51
Laneyutlemming: ^^^ any chance you could take a look at that?11:51
=== _salem is now known as salem_
apwxack12:06
pittiinfinity: why is fisher03 on manual?13:36
pitti(asking because we could really use some more ppc64el horsepower)13:36
pittiI just retried to revive denneed04, let's see how it goes13:36
pittiapw: cheers13:42
pittiapw: want to do another one?13:46
pittiMirv: does this happen to tell anything to you? http://paste.ubuntu.com/12048072/13:47
pittiMirv: I just added a change to add -fPIC to the CXXFLAGS, which apparently was respected (as it appears in the c++ line now), but I'm still getting that error13:47
apwpitti, damn, so much of this is pending for lack of build resources, gah13:58
pittiMirv: ah, it seems this error message is utterly confusing; it rather objects to being built with -fPIE it seems13:58
pitti    (!defined(__PIC__) || (defined(__PIE__) && defined(Q_CC_GNU) && Q_CC_GNU >= 500))13:58
pittiso Qt does not want to be built with -fPIE on gcc > 513:58
pittiapw: that too; it's annoying to see updates on the trackers and when waiting for retrying/uploading followup transitions, but so far there's still enough first-level stuff to do :/13:59
Mirvpitti: ..yes, so I think this is the last change that went into 5.4.2 we luckily had before the GCC5 transition began: http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3eca75de67b3fd2c890715b30c7899cebc096fe913:59
pittiMirv: hm, that commit description is equally wrong/confusing then13:59
pittior maybe it *is* the intention, then the code is wrong?14:00
pittiMirv: so should I drop -fPIE from gnuplot5?14:00
Mirvpitti: yes it seems they do want to ban the usage of -fPIE14:02
pittitoo bad, it's quite nice for ASLR14:02
Mirvon x86 only, to be exact, since reduce relocations (-Bsymbolic) is only used on x86 with Qt14:02
pittiMirv: oh right, it actually does build on any !x86 arch: https://launchpad.net/ubuntu/+source/gnuplot5/5.0.1+dfsg1-2build114:03
pittiMirv: but it's impractical to drop this by-arch, as a package like gnuplot can't know on which arches we enabled -Bsymbolic14:04
* pitti tries to drop it from all arches then14:04
Mirvpitti: yes, and the upstream might change to enable it for other archs too but there's a binutils bug on armhf that was thought to be fixed but isn't so it's currently as it is14:05
Mirvhttps://bugreports.qt.io/browse/QTBUG-4735014:05
Mirvwe did have -reduce-relocation explicitly set at one point but with Qt 5.4 upgrade it caused Unity 8 to show black screen on arm because of this buggy behavior, so now we accept what upstream defaults to14:06
pittiMirv: ack, thanks for the pointers!14:07
Mirvpitti: you're welcome! I'm happy I battled with Qt 5.4.2 in June without anyone specifically asking for it, since now this problem was largely resolved before GCC5 transition began. GCC5's painful enough as it currently stands.14:10
=== juliank0 is now known as juliank
pittiwah, wah, wah, still doesn't build14:10
pittiand why on earth is it so utterly hard to actually find the error message in a build log14:10
pittiMirv: hm, I patched out the addition of -fPIE in configure.in and configure, but it still creeps in; might that come from some pkg-config stuff from Qt itself?14:14
pitti"grep -r fPIE" is empty now14:15
pitti(and so is "fpie")14:15
Mirvpitti: hardening flags? see https://launchpad.net/ubuntu/+source/poppler/+changelog14:19
pittiMirv: ah!14:21
pittiMirv: ok, one step further, but it's *still* there14:23
pittiactually, it's not14:24
pittiMirv: oh! so I *do* need to use -fPIC, but must not use -fPIE14:24
Mirvpitti: yes!14:24
pittibut that is wrong14:25
pittiPIC isn't for executables14:25
pittithat's PIE14:25
MirvI thought PIC was superset of PIE, but I'm not really knowledgeable at that level14:27
pittiI thought PIC -> shlibs, PIE -> exes14:28
pittifinally!14:33
pittithanks Mirv, builds at last14:33
Mirvno problem14:35
davmor2pitti: ofcourse PIE is not for executable PIE is for eating hmmmmm PIE!!!!14:53
pittidavmor2: it's summer! "pie" is spelt "ice cream" now.14:56
tdaitxpitti, you might have seen these already, but I found a couple link that might help: http://code.qt.io/cgit/qt/qtbase.git/plain/dist/changes-5.4.2 https://bugreports.qt.io/browse/QTBUG-45755 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6588614:57
ubottugcc.gnu.org bug 65886 in target "[5/6 Regression] Copy reloc in PIE incompatible with DSO created by -Wl,-Bsymbolic" [Normal,New]14:57
davmor2pitti: Baked Alaska is still PIE14:57
pittitdaitx: thanks; the "changes" is quite useful (it's what the git commit Mirv pointed to did)14:58
tdaitxhmm... right, I missed that one15:00
tdaitxalthough the Changelog itself does add that "Applications using qmake or cmake >= 2.8.12 as their build system will adapt automatically. Applications using an older release of cmake in combination with GCC 5.x need to change their CMakeLists.txt to add Qt5Core_EXECUTABLE_COMPILE_FLAGS to CMAKE_CXX_FLAGS. In particular, applications using cmake >= 2.8.9 and < 2.8.11 will continue to build with the -fPIE option and invoke the special compatibility mode15:01
tdaitxif using GCC 4.x."15:01
infinitypitti: Because I forgot I was working on it.  D'oh.  Fixing.15:04
tdaitxpitti, btw, thanks for the fixing the Changelog of the 2 ftbfs fixes I made the other week... one question: what is the right procedure to add those links when creating the debdiff? at added the debdiff at the time I created the LP bug and used submittodebian to create the bug at debian... seems like I should first create the bugs and only then attach the patches, right?15:08
pittitdaitx: you can do that, but adding the bug refs as a sponsor isn't a big deal15:08
pittitdaitx: creating an LP bug is instant, so doing that, and re-doing the debdiff is simple15:08
pittitdaitx: the Debian BTS is a much worse beast and there are some delays involved15:09
tdaitxindeed15:09
infinityThe only real delay is greylisting.15:09
infinityUse the BTS often enough, and it's delay-free.15:09
infinitySo, obviously, file more bugs!15:09
tdaitxsweet15:09
tdaitx=)15:09
=== gshereme is now known as gshereme|away
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
=== tdaitx is now known as tdaitx|lunch
Riddellricotz: ping, you rebuild openconnect?16:25
RiddellI need it rebuilt for plasma-nm, do you know the status of that in the ubuntu archive?16:25
=== Malsasa_ is now known as Malsasa
ricotzRiddell, how do you mean? the -proposed pocket doesnt provide a rebuild yet, feel free push one16:42
=== Malsasa_ is now known as Malsasa
Odd_Blokearges: I mistakenly "fixed" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1381776 in trusty when it actually only appears in precise.17:07
ubottuLaunchpad bug 1381776 in cloud-init (Ubuntu) "cloud init depends on python-serial but does not declare it" [Medium,Confirmed]17:07
Odd_Blokearges: But there isn't actually an impact on the installed package, so can we let that through and fix the needlessly added dependency in the next SRU?17:08
Odd_Blokearges: (As in, the package is determined as a dependency by debhelper's Python stuff, so the requirements of the package haven't changed, just the Build-Depends)17:09
=== tdaitx|lunch is now known as tdaitx
argesOdd_Bloke: so if it isn't needed in trusty why not just fail the -proposed version and then when the next upload comes along we just overwrite it17:10
Odd_Blokearges: Would we be able to expedite getting that in to the archive and out of -proposed?  We've got another SRU that we want to do that is fairly time-critical.17:11
Odd_Blokearges: (But contains big enough changes that trying to verify everything all at once would have been painful)17:11
argesOdd_Bloke: we can overwrite the current version in proposed. Does it just contain that one fix?17:12
Odd_Blokearges: The version in -proposed fixes three bugs; the only change needed to that package would be to fix this problem.17:13
Odd_Bloke(Well, fixes 2 bugs and this non-bug)17:13
argesOdd_Bloke: ok in that case verifying #1464253 and then 'verifying' 1381776 would help (perhaps comment on how its a non-bug fix and what your plan is in the next upload)17:14
Odd_Blokearges: Ack, thanks.  Both of those bugs are now verified.17:17
argesOdd_Bloke: another helpful thing would be to ensure all development tasks are marked either 'invalid' or 'fix released'17:19
argesat least for bug 138177617:19
ubottubug 1381776 in cloud-init (Ubuntu) "cloud init depends on python-serial but does not declare it" [Medium,Confirmed] https://launchpad.net/bugs/138177617:19
Odd_Blokearges: So that should reflect the status in the development release (i.e. not a problem)?17:20
argesOdd_Bloke: yea so if its not a bug in development its probably 'invalid' or if its already fixed 'fix released'17:21
Odd_Blokearges: Ack, will make sure I do that in future.17:21
argesOdd_Bloke: np17:22
argesOdd_Bloke: ok so just to confirm cloud-init in precise/trusty/vivid can be released, then you'll upload a new one here soon for the next update17:23
Odd_Blokearges: Yep, they are all ready for release.17:24
argesok17:24
Odd_BlokeAnd I will start preparing the new SRU tomorrow morning.17:24
Odd_Bloke(As I'm about to EOD)17:24
argesok17:27
israeldahlHi, is there anyway to make PowerPC debs in a PPA?  I don't think I am allowed to manually upload them.17:46
tewardnot an expert but i don't think so...?17:49
maxbThat's more a question for #launchpad, but there are no virtualized PPC builders, so you'd need a PPA enabled to use non-virtual builders, which I *think* is only an option for people employed by Canonical for security reasons17:49
israeldahlthanks guys...17:50
israeldahlis the other option to create a repository then?17:50
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
infinitymterry: Hah, nice clash on the lxd MIR. :)18:44
infinitymterry: I guess now it's REALLY assigned to ubuntu-security.18:44
infinityTwice!18:44
mterryinfinity, hah  :)18:46
dokohmm, after today's updates, my mouse cursor on the wily-proposed desktop disappears after some time19:07
dokoLaney, seb128: ^^^ any idea?19:07
seb128not really no, sorry19:07
tjaaltondoko: try a VT switch and back, or suspend/resume cycle19:31
dokotjaalton, vt switch didn't help. will try suspend/resume next time19:32
dokojamespage, smoser: mongodb ping ... you last updated the package in 2014 ...20:01
smoserdoko, you're pinging because its ftbfs ?20:03
dokosmoser, yes20:04
dokosmoser, and we need it for the transition20:04
smoseri'll poke and see if we cant get someone to look at it.20:05
dokosmoser, ok, I'll upload a workaround to not build with -Werror20:06
smoserok. and then we'll try to drop taht in another upload.20:07
dokosmoser, juju-mongodb needs attention too20:10
smoserok. thanks.20:10
dokosmoser, open-vm-tools too20:10
dokosmoser, and ceph20:11
smoseryou have a comprehensive list ?20:12
dokosmoser, see slangasek's email to ubuntu-devel (and there are the various ruby packages in dep-wait status which need resolving)20:13
smoserk20:15
Logancould someone please help me figure out what's going wrong with this build? https://launchpad.net/ubuntu/+source/aqsis/1.8.2-1ubuntu1 I can't find a specific error message in the log...20:20
Loganthe same upload built perfectly fine in my PPA: https://launchpad.net/~logan/+archive/ubuntu/ubuntu-tweak/+build/777839120:20
Loganoh right, it's the parse error again20:22
dokosmoser, LP: #1482777 needs bug subscribers, and filed LP: #1483400 for mongodb. the ceph ftbfs is LP: #148340320:41
ubottuLaunchpad bug 1482777 in xml-security-c (Ubuntu) "[MIR] open-vm-tools 9.10.2 build dependencies: xml-security-c and xerces-c" [Critical,New] https://launchpad.net/bugs/148277720:41
ubottuLaunchpad bug 1483400 in mongodb (Ubuntu) "mongodb ftbfs with GCC 5 and boost 1.58" [Critical,Confirmed] https://launchpad.net/bugs/148340020:41
ubottuLaunchpad bug 1483403 in ceph (Ubuntu) "ceph FTBFS with boost1.58" [Critical,Confirmed] https://launchpad.net/bugs/148340320:41
smoserthank you20:45
smoseranyone want to guess what would do this ?21:12
smoserplease21:12
smoserhttp://paste.ubuntu.com/12051576/21:12
smoserfor some reason the while loop there just does not read the second line.21:13
slangaseksmoser: any chance that 'sudo cat /proc/net/route' gives different results? :)21:14
dokosmoser, configured open-vm-tools without xmlsecurity and xerces support, seems to build21:15
sarnoldsmoser: how repeatable is that? it looks fine, runs fine on my system..21:15
smoserslangasek, no different21:16
smoserhttp://paste.ubuntu.com/12051601/21:16
smoserwell, this system keeps repeating it.21:16
dokobarry, 3.5 related: https://bugs.launchpad.net/ubuntu/+source/checkbox-support/+bug/148341021:18
ubottuLaunchpad bug 1483410 in checkbox-support (Ubuntu) "checkbox-support FTBFS in wily" [High,Confirmed]21:18
barrydoko: ack21:18
smoserhttp://paste.ubuntu.com/12051630/21:19
smoserslangasek, take a look at that.. .very odd. they're the same contetns. but behave differnetly.21:20
slangaseksmoser: what are you meaning to show with that pastebin? you seem to be showing everything *except* the output of 'sudo cat /proc/net/route'21:21
smoserslangasek, ? cat /proc/net/route at the bottom21:39
smosereverything there is done as non-root21:39
smoserso it took the root suggestion out of the picture, but it didnt matter anyway.21:40
slangaseksmoser: oh, because you see the same misbehavior even when running as non-root, check21:40
slangaseksmoser: so it's gotta be either a kernel bug or a dash bug.  What does strace look like?21:44
barryslangasek: how terrible will it be to MIR libgeos-dev?  i'm more or less stuck between three not so great options for getting django buildable in wily.  libgeos-dev to main seems like the least painful option.  otherwise it's try to try to backport a huge diff from upstream (not sure it will apply and build to our version), or pull in django 1.8.3 from experimental, but i'm really not sure i want to start a django transition right now21:46
barrytoo :/  thoughts?21:46
slangasekbarry: it seems like a reasonably self-contained library dep, shouldn't be too horrible IMHO?  But you probably want the MIR team's input21:47
barrymaybe doko can weigh in?21:49
dokobarry, but it doesn't build python bindings?21:52
barrydoko: no, django's test suite uses it via ctypes21:52
barrythe problem is, test discovery works differently on py2 and py3, and the latter picks up gis tests that py2 doesn't pick up.  but you can't just add some test skips because its during discovery that modules get imported which hit libgeos-dev21:53
dokoChanges in 3.4.221:54
doko2013-08-2521:54
dokoseems to be dead upstream21:54
dokohttps://github.com/libgeos/libgeos21:56
barrylooks like they've got some recent-ish changes there21:56
dokobut some activity at https://github.com/libgeos/libgeos/commits/svn-trunk21:56
dokoyeah, no release. well, look at the other criteria for a MIR ...21:57
barrycross pocket b-ds bite again :/21:58
barrywell, if mir of libgeos-dev is unlikely, we might just be stuck with a broken django stack for now21:59
barryi guess another option is to just ignore test failures for django22:00
sarnoldjust how bad is pulling in 1.8.3? iirc django is important to maas, openstack, probably elsewhere, and breaking those doesn't sound fun22:12
infinitysmoser: Is that weird /proc behaviour in a namespace (ie: a container) by any chance?22:43
infinitysmoser: Oh, no.  I can reproduce it here in my base system on my laptop.22:44
infinityWTF.22:44
sarnoldI wondered if it might have anything to do with read block sizes, so I tried dd with different bs, but the 14 or 15 tests I ran all gave identical results on my computer22:46
sarnoldfor i in 1 2 4 8 16 32 64 128 256 512 1024 4096 8192 ; do dd if=/proc/net/route of=$i bs=$i ; done22:46
infinityI don't see any fishy non-printable chars in the file, which was my first guess.22:47
infinityWell, my second guess.  My first guess is the kernel just flat out not giving you that line in a pipe.  Which seems like the only plausible answer right now.22:48
infinitysarnold: You say it doesn't break for you?22:48
infinitysarnold: Do you have a default gateway on the machine you're trying on (that seems to be the line both smoser and I are missing)22:48
sarnoldinfinity: yeah, I do have a default gateway22:49
sarnoldinteresting...22:49
sarnold3.13.0-57-generic here22:49
infinity4.1.whatever here.22:49
infinity4.1.0-3-generic22:50
cyphermoxyou're missing a default gateway?!22:50
infinitycyphermox: No.22:50
infinitycyphermox: Only when reading proc with a pipe.22:50
cyphermoxok22:50
cyphermoxwell, obviously, since you're online :P22:50
infinitycyphermox: Compare:22:50
infinitysh -c 'while read line; do echo line: $line; done' < /proc/net/route22:50
infinitycat /proc/net/route22:50
infinityAnd witness the bizarre missing line.22:51
cyphermoxah, interesting22:51
sarnoldcyphermox: you too?22:51
cyphermoxyeah22:51
sarnoldo_O22:51
cyphermoxhttp://paste.ubuntu.com/12052232/22:52
cyphermox4.1.0-2-generic22:54
infinityYep, same missing line.22:54
infinityIt's always either the first route or the default.  Hard to say, since they're the first route on all the test systems.22:54
cyphermoxit's also the one you're most likely to care about :)22:55
infinitysmoser: Have you seen this on a stable kernel, or just on wily?22:55
* infinity tests 4.2.22:55
sarnoldhow about "cat < /proc/net/route" ?22:56
cyphermoxcorrect22:56
infinitysarnold: That's fine.22:56
sarnoldgah. that hurts my head.22:58
infinitySame issue on 4.2, *and* confirmation that it's the default route.23:03
infinityCause my machine came up with two defaults (on eth0 and wlan0), and both are removed from the piped list.23:04
infinityWeeeeeird.23:04
infinityhttp://paste.ubuntu.com/12052314/23:04
infinityapw: WTF is wrong with your kernel? :)23:05
dokotjaalton, no, suspend/restore doesn't help either23:07
infinityBah.  Literally identical set of packages installed, still no failure.  Not we're in the realm of the bizarre.23:23
infinityErr, wrong window.23:23
=== salem_ is now known as _salem
smoserinfinity, i have only ever seen that today23:48
smoserrunning on 4.1.0-2-generic23:49
smoserlinux-image-4.1.0-2-generic23:49
* smoser reboots taht system to -3 to see if it goes away23:49
infinitysmoser: It's still broken in 4.1-3 and 4.223:50
infinitysmoser: Was curious if it was alright under 3.19 and earlier.23:50
infinity(sarnold says it's fine on 3.13)23:50
infinityThough, he also has different userspace, which is less helpful.23:50
smoseryeah, mine is not user namespace23:50
infinityNo, neither was mine.  I got past that theory. :)23:51
* smoser files a bug23:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!