/srv/irclogs.ubuntu.com/2016/10/12/#ubuntu-devel.txt

=== zigo is now known as Guest59427
cpaelzergood morning05:30
=== marcusto_ is now known as marcustomlinson
dokoMirv: looking at https://launchpadlibrarian.net/289272540/buildlog_ubuntu-yakkety-amd64.qliss3d_1.4-2_BUILDING.txt.gz05:48
dokothere's a X11 header check, but it looks like it's triggered by CHECK_QT4, so some qt4 dev package seems to be missing an x11 -dev dependency05:49
Mirvdoko: I haven't spent many minutes with Qt 4 since initial 2012 qtchooser work, but there is just two dev packages libqt4-dev and libqt4-opengl-dev. the former does recommend libqt4-opengl-dev that depends on Mesa dev than depends on X11 dev06:00
Mirvit does not seem there would be anything related changed in Debian after last Ubuntu merge06:01
dokoMirv: ok, adding libx11-dev gets me one step further: https://launchpadlibrarian.net/289273657/buildlog_ubuntu-yakkety-s390x.qliss3d_1.4-2ubuntu1_BUILDING.txt.gz06:02
dokonow complaining about missing shared qt libs06:02
dokoMirv: add the libqt4-opengl-dev b-d doesn't help06:08
Mirvso it has built in Debian six months ago, before qt4-x11 4.8.7+dfsg7. dfsg7 added -std=gnu++98 as a workaround for GCC6, maybe that could affect something negatively06:14
pittiGood morning06:15
Mirvor as it's using autotools for some reason, they'd need to be updated or qmake used instead (there is qliss3d.pro in addition to the autotools files)06:16
handsome_fengHi, gays, Good morning !Because of some issues found in test today, we have updated the theme package,  Could anyone help to upload this: package: ubuntukylin-theme, Code : https://code.launchpad.net/~zctgbhu/ubuntukylin-theme/16.10 Release: https://launchpad.net/ubuntukylin-theme/16.10/1.6.2 , Thank you !06:39
dokoMirv: ahh, that's failing because *no* libs can be found in /usr/lib anymore ;-P06:53
doko++ ls '/usr/lib/*.a'06:54
doko+ QT_IS_STATIC=06:54
doko+ test x = x06:54
doko+ QT_IS_STATIC=no06:54
doko+ test xno = xno06:54
doko++ ls '/usr/lib/*.so'06:54
doko+ QT_IS_DYNAMIC=06:54
doko+ test x = x06:54
doko+ as_fn_error 0 '*** Couldn'\''t find any Qt libraries' 4119 506:54
doko+ as_status=006:54
dokoso this qt config test is horribly broken :-/06:55
=== Guest59427 is now known as zigo
tmusI've disabled resolved completely, using dnsmasq instead. But if I connect to a VPN, the domain provided as "dns-search" from the VPN server, is the ONLY domain that's resolved by the DNS on the VPN connection, causing a lot of things to not work... Can I send ALL DNS queries the way of the VPN?09:02
tmusThis worked fine in 16.0409:02
=== zumbi_ is now known as zumbi
pittitmus: could be fallout from bug 159272109:11
ubottubug 1592721 in network-manager (Ubuntu Xenial) "Don't write search domains to resolv.conf in the case of split DNS" [Medium,Fix released] https://launchpad.net/bugs/159272109:11
pittitmus: NM uses dnsmasq by default again in 16.10, FTR09:11
tmuspitti, good to hear that resolved was pulled - i like the idea, but not ready yet imho...09:13
pittitmus: it's still being used on the server09:13
pittitmus: for NM we need a proper DNS plugin for split-horizon DNS, which didn't exist until two weeks ago09:14
pittiwe'll get that in Z09:14
tmuspitti, cool...09:14
pittitmus: but your issue sounds like an NM-internal change (the above bug)09:14
tmushaving read through the bug, this is clearly related, but not the same problem09:17
tmusFor my VPN (this particular VPN anyway), i'm not split-tunnelling. Still, only DNS requests to my VPN's primary search-domain goes to the VPN DNS09:18
tmus(we have a looot of internal domains - but only the primary resolves correctly)09:18
tmuslooking through syslog, it's clear that dnsmask is asked to use the VPN provided DNS servers *only* with the provided search-domain09:19
tmusactually it may be the same but now that i'm reading it the second time09:20
tmuspitti, can I msg you 10 lines of log to explain?09:26
pittitmus: you can, but I suggest to put them on the bug instead and discuss there (busy with release stuff)09:26
tmuspitti, fair enough :)09:28
pitticpaelzer: btw, you need https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=40cb56b9 as well if you have any tests that reboot09:57
cpaelzerthanks pitti10:03
cpaelzerpitti: I was broken on s390 due to other things then, but happy on amd64 with my tests that did not include reboots10:03
seb128mardy, hey, is https://errors.ubuntu.com/problem/cdb7a4fc6d47e3ba3ce18606745c27933f9a7f57 something you are aware of? it's the n°1 error on e.u.c for 16.1010:26
seb128could be a qt issue, webbrowser seems to have a similar report10:27
=== dosaboy_ is now known as dosaboy
seb128Mirv, ^ do you know about those reports?10:28
mardyseb128: I really wasn't, thanks10:28
seb128mardy, yw10:28
mardyMirv: it's QNetworkManager, and happens during destruction...10:31
mardyMirv: the first reports are from Oct 2nd and happen with older versions of signon too. So I guess it's due to some Qt landing...10:34
seb128mardy, Mirv, webbrowser has the same issue so it would suggest a qt bug rather than a signon one10:35
Mirvseb128: yes, bug #1630765 , happens after bug #1618590 got fixed. there's silo 2054 that is in QA's hands that includes a cherry-pick from Qt 5.8 which however upstream doesn't seem suitable for their 5.6 criteria, but we might accept that workaround10:49
ubottubug 1630765 in webbrowser-app (Ubuntu) "webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration()" [Medium,Confirmed] https://launchpad.net/bugs/163076510:50
ubottubug 1618590 in Canonical System Image "scoperunner crashed with SIGSEGV in QObject::disconnect()" [Critical,Fix committed] https://launchpad.net/bugs/161859010:50
Mirvlatest discussion about what the workaround would be hiding is at https://codereview.qt-project.org/#/c/172173/ , thanks to Michael from our side for providing valgrind trace to upstream10:50
seb128k10:51
seb128which I guess means it's not going to be fixed for release10:51
MirvI guess no. reverting to the previous version would bring the scoperunner crash-on-exit back.10:51
Mirvubuntu-qa: have you started looking at silo 2054 for desktop (and xenial+overlay phone)?10:52
davmor2Mirv: nope still in the queue10:52
MirvI was hoping there'd be a real fix by now, but it starts to look like we'd need to stop unloading those plugins10:52
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
morfhi12:34
morfis it possible to install ubuntu mobile to samsung galaxy s5 (klte)?12:34
=== _salem is now known as salem_
pragomer_1Getting error "/init line 7 can't open /dev/sr0 no medium found" when booting via pxe.. here's my menu-entry:http://pastebin.com/3EJ4cPdp    Whats wrong?13:11
ginggstseliot: the libcuda-8.0-1 provides seems to have fallen out of the nvidia driver somewere between 361 and 36714:27
bdmurrayjbicha: Why did you reopen the yakkety task for bug 1619188?14:32
ubottubug 1619188 in casper (Ubuntu Yakkety) "Unattended upgrades can break persistent live media" [Medium,Triaged] https://launchpad.net/bugs/161918814:32
jbichabdmurray: because I assumed it was broken on yakkety too, but I'll re-close it now14:33
bdmurrayjbicha: I just booted a yakkety live cd again and -security is commented out and the script is +x so its good.14:34
jbichabdmurray: good, I'm glad yakkety works at this point :)14:38
tseliotginggs: I don't recall removing it, or maybe I simply imagined adding that?14:45
tseliotginggs: BTW, is that only for yakkety?14:45
tseliotI actually said "I have just uploaded your changes", so it's just me losing that change somehow14:47
ginggstseliot: yes, it is only for yakkety (for now - maybe commit to git for xenial and include with next upload so we can put cuda in backports)14:50
tseliotginggs: ok, thanks14:50
ginggsi was definitely in 361 https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/361.45.11-0ubuntu414:51
ginggs*it14:51
tseliotginggs: yes, I probably used a slightly older branch as a base when creating the one for the 367 series14:54
tseliotginggs: uploaded. I managed to find the same commit from the 361 branch. Go figure...15:12
ginggstseliot: thanks!15:16
tseliotthanks for making me notice15:16
=== timrc_ is now known as timrc
=== salem_ is now known as _salem
=== imcleod is now known as imcleod-mtg
=== _salem is now known as salem_
nacccan anyone see clearly why osgearth and qgis haven't migrated from trusty-proposed to trusty? All other archs have, and update_excuses/update_output say they are 'successful' and in the 'final' list.16:17
naccsorry, specifically on armhf only16:18
chilukcyphermox.. debdiffs in lp 1631474 ... modified per your recomendation.... I also did a bit more testing..16:39
ubottuLaunchpad bug 1631474 in initramfs-tools (Ubuntu) "No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option" [High,In progress] https://launchpad.net/bugs/163147416:39
chiluknot exactly what you asked for, but I felt it flowed better this way.. I claim personal preference.. I also improved the comment in case the next guy doesn't think like I do.16:39
=== salem_ is now known as _salem
slangaseknacc: that sounds somewhat related to the changes pitti was just making to britney this week16:50
slangaseknacc: oh, also, I'm not sure if we actually do migration of binaries using proposed-migration for stable releases16:50
slangasekit might require a manual copy16:50
naccslangasek: ok, i was just surprised the other archs migrated but armhf hadn't16:53
naccslangasek: maybe it just needs a manual poke? should i be asking #ubuntu-release instead?16:53
slangaseknacc: no, #ubuntu-release is busy with releasing ;)  I'm having a look at these16:54
Laneynacc: I think they're just random builds that happened after the release16:54
slangaseknacc: "the other archs migrated" - except they didn't, because what Laney said16:54
naccslangasek: yeah, i was hesitant to interject there today :)16:54
naccLaney: ah16:54
LaneyWe deleted some similar ones in xenial earlier today16:54
LaneyNot sure how they got retried; didn't think that was available for released suites (but ICBW there)16:55
naccok, had a user in #ubuntu wonder why qgis wasn't installable on armhf in trusty16:55
naccLaney: except for osgearth, it's not a rebuild? or do you meant something else16:56
LaneyBuild failure that later succeeded16:56
naccah!16:56
naccslangasek: Laney: thanks for the explanation!16:57
slangaseknacc: ah yeah I can't work out how to actually copy these in to trusty-updates, because copy-package operates on source packages and there is no source in trusty-proposed.  Punting until a launchpad wizard can look at it (post-release)17:00
slangasek(my best idea so far is to copy the source /back/ from trusty release into trusty-proposed, so that there's then a source package that can be copied; but that sounds like a good way to make launchpad very angry about publication history)17:01
infinityslangasek: copy-package -e $ver --force-same-destination --from-suite=trusty-proposed -b foo17:03
naccslangasek: ack, i'll put it on my todo to follow-up on later17:03
slangasekinfinity: when the source was never previously in trusty-proposed?17:03
infinityslangasek: If it ever existed in trusty-proposed, LP will magically find it and put it back.17:03
slangasekah17:03
slangasekok17:03
slangasekyeah this is "random arch build caught up post-release"17:03
slangasekso it was never in -proposed17:03
slangasekerrr wait17:03
infinitySure it was.17:03
slangasekeverything builds in -proposed these days17:03
infinityEVerything starts out in proposed.17:03
slangasekhee17:03
slangasekthanks17:03
naccsmoser: heh, your cloud-utils import kind of forced me to rethink the solution we had. It's now a bit more abstracted in the code and handles your particular case better (it was a real bug in the old implementation). When we do a source patch, we need to do it anywhere we might encounter that published version, including when we are lookingat the parents of a new import17:05
slangasekCopy candidates:17:05
slangasek<hang>17:05
slangasekah there it is17:06
smosernacc, so uploaded ?17:06
naccsmoser: testing my fix now :)17:06
smoseryou have a feel / guess for how many packages might need "source patch" ?17:06
naccsmoser: and then need to actually clean up my changelog etc, but i think it's working17:06
naccsmoser: so far we've hit 317:07
smoser3/~5017:07
smoser:-(17:07
naccsmoser: yep17:07
naccsmoser: not great, not terrible (IMO)17:07
smoser$ proxy curl --silent http://archive.ubuntu.com/ubuntu/dists/xenial/main/source/Sources.xz | xzcat | grep ^Package: | wc -l17:13
smoser247017:13
smoser6% failure rate on 2400 packages is 14417:13
smoserwithout touching universe. so yeah, maybe its not bad, but if in fact we have to manually patch 144 things, that sucks.17:14
naccand i'm not sure it's on my roadmap to support importing all of main :)17:15
naccas of right now, i'm focused on server packages17:15
nacci'm not saying it's not a problem17:16
smoserwhat about just going on ?17:16
smoserwarn: could not import package at version X.17:17
naccthen we'd have an inaccurate history17:17
naccthere are algorithmic guarantees we are trying to assert :)17:17
naccwe do orphan packages in some cases17:17
smoser --allow-failed-imports17:17
smosergiven the archive seems to have started rejecting things like that, its probably mostly a historic problem.17:18
naccit's exclusively historic17:18
naccsmoser: feel free to file a bug :) as of right now, i'm not convinced it's a large enough issue to warrant adding a flag, or changing the algorithm again17:19
smosernacc, alternatively i could convince you otherwise by changing that pipe command above to just loop over usd-import <package>17:20
smoserand file individual bugs :)17:20
naccthat would also be fine17:21
=== _salem is now known as salem_
naccsmoser: it would be interesting to run that with --no-push, tbh, it'll probably take a few days to complete17:23
=== salem_ is now known as _salem
* smoser tries17:25
naccsmoser: ok, cloud-utils can import with my fix(es). Want me to push now, or are you ok with waiting while I clean up my changelog17:29
smosernacc, not really a hurry17:30
smoserjust if i'm going to look at code now, i first run usd-import17:31
naccsmoser: ok, i should be able to push in about 20 minutes, it's not that complicate of a change, i just want to verify it a bit17:31
jderosechiluk: something seems slightly wonky with latest initramfs-utils from your PPA (at least for my use case); i added a comment to the bug17:43
chilukthanks jderose17:44
chilukjderose: can you get me full console log output?...17:44
jderosechiluk: yeah, what's the best way to do this?17:45
chilukcheck to see if the errors are showing in /var/log/syslog or kern.log.. I suspect neither.17:46
jderosechiluk: or what's the place to dump this from if i don't have a serial console setup? after the boot i can mount a usb drive, copy it over to that17:46
jderosechiluk: okay, i'll just grab everything from /var/log17:46
chilukdumping serial console would be the best .. as I don't think the messages you are seeing get dumped into /var/log17:47
slangaseknacc: so these packages are uncopiable, even with infinity's hint, with an error about 'binaries conflicting with the existing ones'.17:47
jderosechiluk: i'll try to get serial console smart in the mean time, but no promises :)17:47
chilukthat would be awesome jderose...17:48
naccslangasek: hrm, that's odd, because rmadison says there are no binaries for armhf?17:49
slangaseknacc: certainly17:49
chilukjderose what is your /proc/cmdline as well?17:49
slangaseknacc: it's a strange error, and there certainly should never have been /different/ binaries with the same version number17:49
naccslangasek: agreed -- do you want me to file a bug?17:49
slangaseknacc: against launchpad, sure17:50
naccslangasek: ok, thanks!17:50
jderosechiluk: "initrd=initrd.img-4.4.0-36-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0"... so the only "weird" thing i'm doing is using net.ifnames=0, not sure if that's effecting anything or not17:50
chilukah jderose I think what's happening is htat you are now going through the full all_net_bootable device bringup loop.17:53
chilukwhich wasn't functioning correctly before.17:53
jderosechiluk: okay, so this is working as expected, despite making stuff take a bit longer?17:53
chilukyeah ... jderose ... give me one second.17:54
naccslangasek: LP: #163280017:54
ubottuLaunchpad bug 1632800 in Launchpad itself "qgis and osgearth stuck in trusty-proposed for armhf" [Undecided,New] https://launchpad.net/bugs/163280017:54
chilukjderose ... I'm going to give you a script to run on your machine ..  we may have to strip out some additional devices.17:54
chilukit also could just be possible that it's now trying all your devices for a dhcp server.17:54
chilukinstead of just the one you want.17:54
jderosechiluk: FYI, this was PXE booting a machine with one Ethernet and one WiFI nic17:57
chilukjderose can you run http://paste.ubuntu.com/23313997/  for me?17:57
chilukand tell me the output?17:58
jderosechiluk: is it okay to run it after the full boot completes, or does in need to be run early, like in the initramfs stage?17:58
chilukafter full boot should be good enough.17:58
jderoseokay, just a sec...17:59
chilukI just want to see if you have any odd devices..17:59
chilukand the order in which they come up.17:59
chilukcyphermox... hold off for a second... Looking at jderose's use case ..17:59
chilukyeah so looking into it jderose I suspect the initramfs may be attempting to bring up your wlan device as well.18:03
chilukthe solution to that would be using ip=:::::eth0:dhcp instead of simply ip=dhcp18:04
chilukwhich is actually more correct than it was previously.18:04
jderosechiluk: you're script is just outputting "eth0"18:04
chilukhmm. I expected you to have multiple devices..18:06
chilukand one failing.18:06
chilukjderose: do you get the same errors if you use ip=:::::eth0:dhcp ??18:09
chilukjderose.. for your use case nothing much has changed between 8.3+lp1631474 and 8.3+lp1631474b2 ..18:11
cyphermoxchiluk: too late.18:11
chilukyou should be following the same logic path with both commits.18:12
chilukit's ok cyphermox.. I think we have something else at play here with jderose.18:12
cyphermoxmy guess is there are timeouts -- the right way to figure this out is to get all the logs18:13
chilukcyphermox: does that mean you've made the upload?  I think we are still safe with the debdiffs as they are currently in the bug.18:14
cyphermoxyes, it's done, and yes, that part is correct18:14
jderosechiluk: okay, "ip=:::::eth0:dhcp" seems to work fine, no unexpected delay18:15
jderosebut "ip=dhcp" still works differently than it previously did18:15
chilukcyphermox ^^^ sounds to me like we're now correctly processing  all_netbootable_devices ..18:16
chilukbut running all_netbootable_devices for him only yeilds eth0.18:17
chilukwhich is odd.18:17
cyphermoxwhat other devices are there?18:17
chilukcyphermox: running all_netbootable_devices  only shows eth0..18:18
chilukwhich is why I'm confused..18:18
chilukjderose you said there was a wireless card in there as well right?18:19
cyphermoxyes, what other interfaces should there be?18:19
jderosecyphermox: just a wifi NIC, although `ifconfig -a` isn't actually showing the device for whatever reason18:19
chilukprobably lacks drivers18:19
cyphermoxwell, then that's the reason -- the driver is probably missing18:19
cyphermox"missing" == not loaded yet18:19
chilukbut that' doesn't explain why ip=dhcp causes errors where ip=:::::eth0:dhcp does not.18:20
chilukat least for him.18:20
jderosemaybe so. seems `wifi-tools` isn't install by default on ubuntu server, so that might be the problem too18:20
chilukjderose what do you see in /sys/class/net/*   ?18:21
jderosechiluk: just "eth0" and "lo"18:21
cyphermoxjderose: please open a bug and add all the output you have on screen as you try to boot18:22
jderosecyphermox: sure, but i might not have time till tomorrow18:22
chilukthat's fine.. jderose.. something else is going on in your boot case..18:24
jderosechiluk: gotcha, thanks. seems like i can just use "ip=:::::eth0:dhcp" and be fine18:24
chilukfeel free to ping me or cyphermox jderose when you have all thte logs grabbed.18:24
jderoseokay, will do18:25
=== imcleod-mtg is now known as imcleod
dmj_s76infinity: In doing upgrade testing xenial->yakkety, the updater complains that it can't authenticate.  Is that expected currently?18:42
=== buxy is now known as kalibot
=== kalibot is now known as buxy
slangasekdmj_s76: certainly not; can you be more specific?18:52
dmj_s76So running do-release-upgrade -d18:53
dmj_s76gpg: BAD signature from "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>"18:54
dmj_s76Authentication Failed18:54
dmj_s76Authenticating the upgrade failed.  There may be a problem with the network or with the server.18:55
dmj_s76Similar authentication failure message when using the graphical updater18:55
=== buxy is now known as kalibot
=== kalibot is now known as buxy
slangasekdmj_s76: ok, could that mean that you have (or did have) a captive portal in the way that is corrupting the download?  Do you see a similar failure from 'sudo apt update'?19:22
chilukslangasek can I get sru approval for https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474  initramfs-tools ?  you look to have approved the previous sru for initramfs-tools.19:41
ubottuLaunchpad bug 1631474 in initramfs-tools (Ubuntu Yakkety) "No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option" [High,In progress]19:41
slangasekchiluk: ENOTIME; grab the sru staffer du jour?19:41
chilukwill do.19:41
chilukI understand you guys are knee deep in release time.19:42
dmj_s76slangasek: Actually checking into that20:01
dmj_s76slangasek: apt update works fine20:03
=== ximion is now known as ximion-afk
tsimonq2Who is responsible for yaboot nowadays?20:41
dmj_s76slangasek: infinity: Sorry to worry you guys.  It was a caching issue on our network.21:17
slangasekdmj_s76: so I suspected, thanks for confirming :)21:17
dmj_s76Had to wait to confirm on our end but wanted to give you a heads up in case it was an issue blocking testing for others21:18
=== tedg_ is now known as tedg
=== mariogrip_ is now known as mariogrip
=== michagogo_ is now known as michagogo
=== zigo_ is now known as zigo
=== karstensrage_ is now known as karstensrage
=== NishanthMenon__ is now known as NishanthMenon
=== ginggs_ is now known as ginggs
=== _salem is now known as salem_
=== salem_ is now known as _salem
slavanapI'm Windows developer. I want to implement Ubuntu File Manager right click extension. Where should I start? Which docs should I read first?23:23
tsimonq2slavanap: I would join #ubuntu-desktop if I were you :)23:27
cjwatsonThis isn't my field, but I think "nautilus extensions" would probably be good search terms here23:28
tsimonq2that too ^23:28
cjwatson(and "apt search nautilus extension" shows several existing ones that you could perhaps use as example code - again, not my field so I don't know which ones are best)23:29
=== ximion is now known as ximion-afk
slavanaptsimonq2, thanks for advice! :)23:34
slavanapcjwatson, got it! Thanks!23:35
naccrbasak: took a while, but i think i've got the framework for upload/ tagging going now23:39
naccrbasak: although something i've got is provoking a pygit2 segfault :)23:44

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