/srv/irclogs.ubuntu.com/2018/03/30/#snappy.txt

zyga_kyrofa: ack, I will try tomorrow00:07
zyga_jdstrand: ack00:08
=== cwayne_ is now known as cwayne
=== rob-oi-ma_ is now known as rob-oi-ma
=== zyga_ is now known as zyga
=== davidcalle_ is now known as davidcalle
=== sdrobertw_ is now known as sdrobertw
=== stokachu_ is now known as stokachu
=== andyrock_ is now known as andyrock
zygapedronis: ack00:13
=== caveat-_ is now known as caveat
mupBug #1684014 changed: LibreOffice in snap won't print <libreoffice (Ubuntu):New> <https://launchpad.net/bugs/1684014>05:06
zygaGood morning07:05
pstolowskimorning zyga!07:15
zygaHey hey07:15
zygaIt is Friday and everything looks terrible :-)07:15
pstolowskizyga: no kidding07:18
zygapstolowski: fedora builds are broken07:20
zygapstolowski: travis slots last night were all gone07:20
zygapstolowski: and I didn't manage to release snapd07:20
pstolowskigosh07:21
pstolowskizyga: what's going on with fedora this time?07:22
pedronispstolowski: afaict go build itself (wich is mostly a wrapper process) dies with exit 2 just before doing the steps of building snapd main itself (after having built all other packages)07:25
pedroniswithout printing any useful info07:26
pedronisfun :/07:26
* pedronis -> afk07:26
pedronispstolowski: zyga:   I tried to strace it,   it was late so maybe I missed something, but afaict no smoking gun there, just after it writes sig.o to signal.a  (the internal pack, internal meaning I discovered is code inside go build not an external exec) it just starts unlinking stuff from the work dir and then you get the exit 207:30
pedronisso it's a sorf of unexplained semi orderly death07:30
* pedronis really afk07:30
pstolowskiwere there any updates to fedora?07:31
pedronisI don't know,   golang claims to be from Mar 5  (so we should have been using it already?  but I don't know how updates percolates there)07:32
zygahmm07:32
pedronisrpmbuild seems the same07:32
pedronisbut maybe some lib changed07:33
zygahey pedronis, thank you for the analysis07:33
pedroniszyga: for details, what I did sofar   is set the few GO env vars and rerun  the "go build" line   in a -debug spread session,   with -n  (to see how far we go, as I said very far)  and then with strace -f07:34
pedronisit's also very consistent07:36
pedronisdies the same way each time07:36
zygapedronis:  do you remember what you set?07:37
pedronisI also double checked the content of the work dir ,  as I said signal.a  looks right  but   ... /cmd/snapd/_obj is not yet created07:37
pedroniszyga: it's in the log07:37
pedronisjust GOPATH  and GOFLAGS07:38
pedronisI think07:38
zygaok07:38
pedronisafter of course cd-ing into /root/rpmbuild/....07:38
* zyga goes to reproduce this with fresh head07:39
zygaso, the list of updates is on https://bodhi.fedoraproject.org/updates/?releases=F2707:43
zygaI'll see if there's something recently that could explain it07:43
pstolowskizyga: looking into this too07:49
zygaif we don't find anything quickly let's split focus and not all try to solve this07:50
zygaI went back 10 days and there's nothing that would indicate any relationship07:51
zygathe closest I saw was a clang update to ship a versioned compiler-version binary07:51
zygaI noticed that on 18.04 high-dpi regressed as compared to 17.10 (for snaps)08:05
pstolowskizyga: fwiw I got that error when building signal.a; then I executed /var/tmp/rpm-tmp.5TbNku manually and it succeeded08:23
pstolowskizyga: (fedora on linode)08:23
zygainteresting, I wonder what that tells us08:23
pstolowskiexactly08:24
pstolowskizyga: i've rebuilt manually like that 3 times, worked08:34
zygapstolowski: I'm doing a mock build to see how that works08:35
pstolowskizyga: do you know what creates and calls /var/tmp/rpm-tmp.5TbNku ?08:35
zygaI think it's part of some RPM macro but I don't know which08:36
zygait could also be a recovery mechanism08:36
zygawhen rpm fails, it writes "reproduce me" shell08:36
pstolowskizyga: yeah, ok, it's assembled from snapd.spec08:37
zygaBreakfast break08:38
zygaAfter that I will mock build08:39
zygaAnd try koji next08:39
pedronispstolowski: that is interesting because if  I run the go build part alone again and again is still fails08:41
pstolowskipedronis: wow, interesting08:46
pstolowskipedronis, zyga and i'v just run the build via rpmbuild --with testkeys -bs and it failed08:47
zygayes, I got that too08:47
pedronisso repeating rpmbuild  fails (different state each time),     repeating go build   fails (afaict)08:48
pedronisbut repeating the tmp script works?08:48
pedronisfascinating08:48
pstolowskipedronis: i'm just going to try tmp script again08:48
pedronisis it succedding in the sense of exit 008:49
pedronisor in the sense it build a snapd binary?08:49
zygaI tried to remove the spread + linode|google magic out of the equation08:51
zygaI built an source tarball and srpm08:51
zyganow building it in mock08:51
zygathis is essentially how all of fedora is normally built08:51
zygaiff this fails08:51
zygawe can give this srpm to people and ask for help08:52
pstolowskipedronis: yes, exit 0, no error around signal.a, the execution ends with https://pastebin.ubuntu.com/p/gtHJGPbPmV/08:52
zyga+ mock is nicer than rpmbuild directly08:52
pstolowskipedronis: so, tmp script just succeeded again08:52
zygaso09:02
zygaah, I didn't use test keys so maybe that's why09:02
zygathe source rpm + mock fail on pack but in a different spot09:02
zygaBUILDSTDERR: /usr/lib/golang/pkg/tool/linux_amd64/compile -o $WORK/golang.org/x/net/context/ctxhttp.a -trimpath $WORK -shared -goversion go1.9.4 -p golang.org/x/net/context/ctxhttp -complete -installsuffix shared -buildid ab9e3e1669ce2ef40183ac44ed64b157e02355b9 -D _/usr/share/gocode/src/golang.org/x/net/context/ctxhttp -I $WORK -I /usr/share/gocode/pkg/linux_amd64_shared -pack ./ctxhttp.go09:02
pedronispstolowski: how are you running it again,  I get  failed to create symbolic link because the link alreday exists09:03
zygaPharaoh_Atem: hey09:05
zygaPharaoh_Atem: so I have a srpm I can reproducibly fail to build in mock09:05
pedronispstolowski: are you rm -rf something before running it again?09:06
pstolowskipedronis: I get that symink error too but that doesn't interrupt the build09:06
pedronisheh09:07
pedronisit definitely does here09:07
pedronispstolowski: ah, are you running without -e ?09:07
pedronisthat's why it finishes09:07
pedronisit ignores errors09:07
pedronisnothing magic09:07
pstolowskiah09:07
pstolowskidammit09:08
pedronisindeed09:08
pedronistoo bad09:08
pedroniszyga: I have no clue what dimension changed (our code,  fedora bit) though ... it stopped working quite randomly yesterday afaict09:09
zygayes, I'm totally puzzled09:09
zygaI will try with -testkeys now09:09
zygaas my failure looks the same but in different spot09:09
pedronisit seems a go build bug09:10
pedronisbut unclear why it appears now09:10
pedroniswhat it triggers it09:10
pedroniss/what it/what709:10
* pedronis -> off09:10
pedroniszyga: one thing to try would also be  to copy over the BUILD directory to bionic and see if that go build command fails there too with 1.9,  fwiw it failed for me also when I didn't pass some of the ldflags stuff09:12
pedronisanyway as said, from the strace it seems to fail in the boring bits of driving the build09:13
zygaon my host it consistently fails elsewhere09:29
zygamaybe it depends number of CPUs?09:30
zygaoh, I'll try koi first09:31
zygakoji09:31
pstolowskifwiw it fails also with go1.9.5 and 1.10.1 on fedora09:48
Caelumzyga: my btrfs died, I submitted that request from the console on a half-broken system, just reinstalled now and picking up the pieces, on ext4 this time10:01
pedroniseven just this fails:   cd /root/rpmbuild/BUILD/snapd-1337.2.31.1  ;  cd cmd/snapd;  go build -v -x .   with or without -a10:02
pedronisit just exit 2 before building main10:02
zygaCaelum: ouch10:02
zygasorry to hear that10:02
zygaCaelum: I made some changes since your patches10:02
Caelumexcellent10:02
zygapedronis: I submitted a koji build https://koji.fedoraproject.org/koji/taskinfo?taskID=2605735610:03
Caelumso .32 is out10:03
pedronispstolowski: would be interesting to copy over the BUILD to an ubuntu system and see if it fails too,   as I show there it seems to fail even without fancy options or anything10:03
pstolowskipedronis: yes, i'm going to try that next10:04
pedronisit just refuses to build cmd/snapd(/maing.go) on fedora10:04
zygathe log is a little bit more useful10:04
zygahttps://koji.fedoraproject.org/koji/getfile?taskID=26057357&volume=DEFAULT&name=build.log&offset=-400010:04
zyga(tail of the build log)10:04
zygatail feature == good thing to copy10:04
zygadoes this cp $WORK/b150/_pkg_.a /builddir/.cache/go-build/92/92ebdb22b8c38b43994a36a864adc877e4e85517bc1f1a7c1b22ee610a1af86d-d # internal10:05
zygaerror: Bad exit status from /var/tmp/rpm-tmp.MIqip3 (%build)10:05
zygasay it is actually cp that failed?10:05
pedronisthat's a completely different kind of failure10:05
pedronisthough10:05
pedroniswe don't know10:05
pedronisusually the last thing printed might have work or not10:05
pedronisas I said in the other failure10:06
pedronisthe pack works10:06
pedronisis the next step that is not taken10:06
zygathis is in koji, the fedora build service10:06
pedronisI understand10:06
pedronisjust saying that looks like a failure10:06
zygaif this is kernel related they are (perhaps) on a different version of that10:06
pedronisbut a different failure10:06
pedronisit's also an exit 1 vs exit 210:07
zyganote that the same SRPM was failing on pack on my host10:07
pedronisI note that on linode the failure mode is very deterministic10:07
pedronisas I said it seems to refuse to go to the last bit10:08
pedronisand build cmd/snapd itself10:08
pedronis(the pack itself works)10:08
pedronisindeed it fails like that, exit 2 refusing to build main even in builds that don't have a pack bit10:08
pedronislate10:09
pedroniszyga: as I said the failure in that  log, looks very different, it seems to be failing building one the prereq packages10:10
pedronison snapd itself10:10
pedroniss/on snapd/not snapd/10:10
pedroniswhat   golang is that btw?10:11
pedronis1.10?10:11
zygaI switched from F28 to F27 and now it's the same error I saw on my host10:11
zygalet me check10:11
zygahttps://koji.fedoraproject.org/koji/getfile?taskID=26057448&volume=DEFAULT&name=build.log&offset=-4000 (the F27 build tail)10:11
zygaDEBUG util.py:439:   golang                              x86_64 1.9.4-2.fc27            build 622 k10:12
zyga1.9.410:12
pedronison F27 ?10:12
pedronison F28 ?10:12
zygathis is on F27 now10:13
zygathe prior build was on F28 and this is why it was different, it was also on using more recent golang10:13
pedronisit just feels like they brok all go building10:14
pedronisit's very strange10:14
pedronisalso the errors are all different10:14
zygaI'll ask around10:14
zygaI asked on fedora-devel10:18
zyganot sure what to do now10:19
zygaI feel we should disable fedora for the time being10:19
zygathis would unblock the release10:19
pedroniszyga: interesting, not sure if related but  I see,    /usr/share/gocode/src/%{go_import_path}  like that in the filesystem10:22
pedronislike some package is really broken10:22
zygaoh10:22
zygathat looks like RPM macro that didn't expand10:22
zygathat's very interesting, let me look10:22
zygapedronis: I'll disable fedora now10:23
zygalet's see if that passes10:25
mupPR snapd#4962 opened: spread.yaml: switch Fedora 27 tests to manual <Created by zyga> <https://github.com/snapcore/snapd/pull/4962>10:26
zygaI’m debugging this in fedora-devel10:45
pedroniszyga: pstolowski: so if I copy over to ubuntu the  gocode dir and the rpmbuild dir and set GOPATH to those, even old go 1.6 fails to build cmd/snapd with exit 210:52
zygacool find10:53
zygabut does that tree include effectively golang 1.9 source?10:53
pedronisno10:53
pedronisgocode has only our deps10:54
pedronisgoroot is the 1.6 one10:54
pstolowskipedronis: and that gocode dir contains that suspicious unexpanded macro?10:54
pedronisyes10:54
pedronisbut yes, it would be better to try this with ubuntu go 1.910:54
pedronisless moving parts10:54
pedronisbut is interesting nevertheless10:55
pedronisit really seems is some issue with src code  (ours or the one brought in by dep packages)10:55
pedronisand to be clear, this is just a plain:   go build -a -v -x .10:56
pedronisnothing fancy10:56
pedronisfrom cmd/snapd10:56
zygalet's try building older tree10:56
pedronisanyway  the %{}  thing for sure cannot bring any good10:56
zyga# cd /home/zyga/go/.cache/govendor/gopkg.in/yaml.v2; git reset --hard 86f5ed62f8a0ee96bd888d2efdfd6d4fb100a4eb10:57
zygafatal: Could not parse object '86f5ed62f8a0ee96bd888d2efdfd6d4fb100a4eb'.10:57
zygammmm10:57
zyga./get-deps.sh failed10:57
zygaworked after I removed ~/go/.cache10:57
zygapedronis: "go build ./cmd/snapd" works10:58
pedronis?10:58
pedroniswhere, in which sense?10:58
pedronisyou mean with our usual vendor dir?10:58
zygayes10:58
zygain a checkout on F2710:58
zyganot in the whole build machinery10:58
pedronisso it seems some packages  are broken10:59
pedronisand render this %{} nonsense10:59
zygaI ran "go build -a -v -x" next and it printed a wall of text and exited with 13010:59
threshgood morning10:59
pedronisand that breaks things10:59
pedronis(strangely in a very non visible way)10:59
zygahey thresh10:59
zygapedronis: go build -a -v -x in cmd/snapd also works10:59
zygafrom our checkout10:59
zygals10:59
zygapedronis: https://github.com/snapcore/snapd/pull/496211:02
mupPR #4962: spread.yaml: switch Fedora 27 tests to manual <Created by zyga> <https://github.com/snapcore/snapd/pull/4962>11:02
zygalet's land this11:02
pstolowski+111:03
pedroniszyga: pstolowski:  yes definitely switching the share/gocode stuff with out usual deps makes thing work again11:11
pedroniseven using them not through vendor to be clear, but just in the GOPATH11:13
pedroniszyga: pstolowski:  so  yesterday one of the deps packages was updated?   or something changed in the rpm go stuff that affects one happens when they are installed?11:14
pedronisI mean in fedora11:14
zygapedronis: I looked at the list of changes published in bodhi and I dind't notice anything golang at all11:15
zygapedronis: let's merge my PR and unblock master11:16
pstolowskiand i've just removed that bogus /usr/share/gocode/%{go_import* path from fs but that didn't make a difference, must be something else in gocode dif11:18
pstolowski*dir11:18
pstolowskilunch break11:20
pedronispstolowski: yea, I tried the same,  I don't get a missing package error, but even without the %{} nonsese, it still exit 211:23
pedroniseven go 1.611:23
zygapedronis: I think it may be yaml related11:28
zygahttps://zero.crans.org/?3e5975e22418a02e#Xv5Juf3UYkZ0FgzYq9Uu2h9AFG4FKFMWqbITXDLVZno=11:28
pedronisI was thinking the same11:28
pedronisa bit unclear exactly what11:28
zygathis is something fedora developer was helping me with11:28
zygaI'll revert the yaml version bump and build11:29
pedronisbut the run that bumped it was green ??11:32
zygareverted, no change11:33
zygaso back to where we started :/11:33
vidal72[m]zyga: I fixed trailing " and there is no more backend_test.go failure in https://github.com/snapcore/snapd/pull/494411:34
zygapedronis: shall we merge 4962 or do you want to resolve this before master can move11:34
mupPR #4944: interfaces: add /var/lib/snapd/snap to @{INSTALL_DIR} <Created by Erick555> <https://github.com/snapcore/snapd/pull/4944>11:34
pedroniszyga: I should be off, I'm not taking decisions11:34
zygaok11:34
pedroniszyga: anyway it's not a bug in our code afaict11:35
zygayes, that is clear, I thin11:35
zyga*think11:35
mupPR snapd#4962 closed: spread.yaml: switch Fedora 27 tests to manual <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4962>11:53
threshwoah, my forum post is flagged as spam12:11
threshverynice12:11
thresh> Multiple community members flagged this post before it was hidden12:11
threshwhat12:11
threshseriously?12:12
* zyga -> walk12:12
threshhow is https://forum.snapcraft.io/t/snapcraft-stage-packages-inconsistent-behaviour/4746 a spam ?!12:15
threshand/or advertisement12:15
threshis there a saner platform to collaborate with devs?12:15
jdstrandniemeyer: hi! quick 'snap switch' question. I have canonical-livepatch on a system. it was tracking stable, r26. yesterady I did 'sudo snap refresh --edge canonical-livepatch'. this refreshed to r38 and marked the snap as starting to track edge (based on snap info). this is all fine12:23
jdstrandniemeyer: then I did 'sudo snap switch --channel=stable canonical-livepatch'. this did not refresh the snap (good) and marked the snap as tracking stable (as seen with snap info. also good)12:24
jdstrandniemeyer: so at this point, I thought that everything was all set for the snap to only refresh the next time stable refreshed, however, at some point later in the day, the snap refreshed automatically in the background and downgraded to stable. is this expected behavior?12:25
jdstrands/stable refreshed/stable's revision changed/12:25
vidal72[m]thresh_: someone doesn't like you :)12:27
vidal72[m]thresh:  ^12:27
jdstrandniemeyer: here is a little more detail:12:28
jdstrand$ sudo snap changes canonical-livepatch12:28
jdstrandID   Status  Spawn                 Ready                 Summary12:28
jdstrand551  Done    2018-03-29T13:17:24Z  2018-03-29T13:17:31Z  Refresh "canonical-livepatch" snap from "edge" channel12:28
jdstrand552  Done    2018-03-29T13:18:04Z  2018-03-29T13:18:04Z  Switch "canonical-livepatch" snap to stable12:28
jdstrand553  Done    2018-03-29T20:49:59Z  2018-03-29T20:50:02Z  Auto-refresh snap "canonical-livepatch"12:28
jdstrand554  Done    2018-03-30T12:20:37Z  2018-03-30T12:20:40Z  Refresh "canonical-livepatch" snap from "candidate" channel12:28
jdstrandniemeyer: it is '553' that did the downgrade back to stable12:28
jdstrandniemeyer: if it is operating as designed, that's fine (though, I wonder about the utility of 'switch' then), I just want to make sure it is working correctly12:29
pedronisjdstrand: no, that's the correct behavior, it will refresh to whatever is on stable12:31
pedroniss/correct/expected/12:31
pedronisremember there's no order in revisions12:31
pedronisjdstrand: switch is more useful if say candidate and revision have the same revision, but I also think we changed refresh to work more like switch in that case12:34
pedronisso it might not be as useful as it was12:34
threshvidal72[m], but I'm amazing and nice12:35
vidal72[m]:)12:36
zygaWhich post is that12:39
threshI linked it half and hour ago here12:45
threshafraid to post it twice now lol12:45
jdstrandniemeyer: nm, pedronis answered12:46
jdstrandpedronis: sure, I realize there is no order with revisions, but if I was on r26/stable then refreshed to r38/edge, then snap switched to stable, I didn't expect to go to r26/stable. I expected to go to !26/stable12:47
jdstrandpedronis: I'm not sure of the utility of snap switch then tbh. it ends up being a delayed refresh12:48
jdstrandpedronis: where I want a delayed refresh to a new thing in the switched to channel12:49
* zyga is back from his walk12:51
zygapopey: what blocks sublime-text from release?12:53
zygathresh: I didn't see the link, can you please re-post?12:54
mupPR snapd#4955 closed: cmd/snap-confine: make /run/media an alias of /media <Critical> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4955>13:00
popeyzyga: actually realised that we should store rename s-t3 to s-t, otherwise the hundreds of people with st3 won't get updates13:00
zygacan we even do this?13:01
zygaI don't think we can13:01
popeyI believe the store people can rename a snap yes13:01
popeyit keeps the id13:01
zygaah, in that case, all for it13:01
zygacan I help somehow13:01
zygaI'd love to just use s-t from snaps already13:01
popeyare store people working today?13:01
popeyyeah, sorry, been on vacation the last few days so it's been back burner13:02
pstolowskizyga: standup, or skip?13:03
zygaoh13:08
zygasorry13:09
popeythresh: dunno why the forum is marking your posts as spam. I have unflagged them as such. Maybe niemeyer knows13:09
zygapstolowski: let's skip maybe13:09
zygapstolowski: google signed me out13:09
zygapstolowski: is it just you and me?13:09
zygaok, found my token13:10
zygathank you popey13:14
popeywtf. i just installed a snap and as soon as the apparmor connections were made the session exploded13:18
popeyi didnt even launch the snap, it ended immediately after install finished13:18
jdstrandpopey: eom?13:18
popeyeom?13:18
zygapopey: probably udev13:18
zygaor oom13:19
zyga(out of memory)13:19
popeyunlikely13:19
popeyit has 64GB13:19
zygabut I saw people reporting bugs about touchpad issues when installing a snap13:19
zygawoah, nice machine!13:19
popeyjust logged back in and I get a "xorg crashed" bug reporter13:19
zygaand it feels like udevadm trigger is not good13:19
zygapopey: can you ssh in13:19
zygaand run journalctl -f13:19
zygaand reproduce?13:19
popeyi logged back in, on a desktop13:19
popeyI'm on core beta13:20
zygapopey: is that a wayland session13:20
zygawhen wayland crashes it takes the session with it13:20
popeyhah, not on your life13:20
zygawell, review your log13:21
zygathere's gotta be a backtrace somewhere :)13:21
popeyjuat waiting for whoopsie to do its thing13:21
popeyhttps://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1760104  whoospie says it's an nvidia driver bug, so who knows13:28
zygapopey: *bam*13:29
zygamaybe it's our bug13:30
zygaI got 404, it's marked as security13:30
popeyI wlll try and reproduce it13:30
zygapopey: look at your journal first13:30
popeygiven I am building a new rev of the snap13:30
zygathere is likely a backtrace there already13:30
popeywill that be already attached to the bug?13:31
zygaI cannot see the bug13:31
* zyga is super happy today13:31
popeyhttps://www.irccloud.com/pastebin/Ic5TwB7Y/13:31
popeythat's all i see in journal13:31
zyga
no no, that's -f13:31
zygathat's "follow"13:32
zygarun journalctl13:32
zygaand page it13:32
zygauntil you see something that's clearly a backtrace13:32
zygait should be from this boot only13:32
zygaso not _too_ long perhaps13:32
* zyga is super happy because his T470 has a working modem now :)13:32
zygait's internal, antennas work and I have 100GB of data plan to use13:32
popeywow13:33
zygaso I can now do what I love doing13:33
zygawork outside :)13:33
popeywork anywhere13:33
zygathe modem I got before was not on the whitelist (curse you lenovo)13:33
zygabut this one is flawless :)13:33
zygaI'm slowly getting used to the T series, X was way smaller13:34
zygabut this is not huge either, it's the okay size for work13:34
zygaand it's not heavy which is what I was worried about13:34
popeyhttps://paste.ubuntu.com/p/3FbykZXbx2/13:39
popeynot a lot interesting in there?13:39
threshmany thanks popey13:41
* thresh wanders off to friday evening endeavours13:41
popey\o/13:42
zygaMar 30 14:15:58 hal compiz[23168]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"13:42
zygabut this is after X died13:42
zygaMar 30 14:15:34 hal audit[1042]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.dosbox-x.dosbox-x" pid=1042 comm="apparmor_parser"13:42
zygaMar 30 14:15:35 hal systemd[22791]: Starting Notification regarding a crash report...13:42
zygaMar 30 14:15:36 hal update-notifier-crash[1108]: Xorg13:42
zygawe have the same mouse :)13:42
popeyhah13:42
jdstrandpopey: haha 'eom'. I meant oom, yes :)13:43
popey"End of memory" :D13:43
zygahmmm13:43
jdstrandEnd Of Memory. hehe13:43
zygaMar 30 14:15:33 hal systemd-udevd[689]: Process '/usr/lib/snapd/snap-device-helper change snap_vidcutter_vidcutter /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:0' failed with exit code 2.13:43
zygaMar 30 14:15:33 hal systemd-udevd[689]: Process '/usr/lib/snapd/snap-device-helper change snap_vlc_vlc /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:0' failed with exit code 2.13:43
zygaMar 30 14:15:33 hal systemd-udevd[689]: Process '/usr/lib/snapd/snap-device-helper change snap_writefull_writefull /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:0' failed with exit code 2.13:43
zygaMar 30 14:15:33 hal systemd-udevd[689]: Process '/usr/lib/snapd/snap-device-helper change snap_zzt_zzt /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:0' failed with exit code 2.13:43
zygajdstrand: ^ does this ring a bell13:43
zygaremember the nvidia udev bug?13:43
zygais this back in some way?13:43
zygathen X crashes on udev13:44
jdstrandzyga: what size is it?13:44
zygasize?13:44
zygathe mouse?13:45
jdstrandzyga: your system. I was reading backscroll13:45
jdstrandzyga: but, yes, it does ring a bell. let me look13:46
zygajdstrand: it's popey's system, we just share the same mouse :)13:46
zygaI bought my yesterday, wanted something that had a working wheel for games13:46
popeyI get it on weekends13:46
zygapstolowski: there is a broken gopkg.in/yaml.v2 upload 10 days ago13:47
zygait broke us13:47
zygapstolowski: people in fedora-devel are fixing it13:47
pstolowski\o/13:47
pstolowskizyga: thanks for info13:47
* zyga painfully goes through secure code and makes all the functions into methods13:48
jdstrandzyga: this is what I was thinking of: https://github.com/snapcore/snapd/pull/4022/files13:52
mupPR #4022:  interfaces/opengl: don't udev tag nvidia devices and use snap-confine instead (2.28) <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4022>13:52
zygayeah13:52
jdstrandactually this: https://github.com/snapcore/snapd/pull/393813:52
mupPR #3938: interfaces/opengl: don't udev tag nvidia devices and use snap-confine instead <Created by jdstrand> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3938>13:52
zygapopey: ls /dev/nvidia* /dev/nv*13:53
zygamaybe with -l13:53
zygabut it appears we are tagging something13:53
zygaand then failing13:53
popeyhttp://paste.ubuntu.com/p/PRpFNNqc29/13:53
jdstrandno new devices there13:55
jdstrandpopey: ls -lR /dev/dr[im]13:56
popeyhttp://paste.ubuntu.com/p/PBx2T3XCTh/13:56
zygajdstrand: are you sure?13:57
zygaah13:57
zyganvme13:57
* zyga is a moron13:57
jdstrandpopey: udevadm info /dev/dri/card013:57
popeyhttp://paste.ubuntu.com/p/C875ZW9MPB/13:57
zygawell, it's tagged for sure13:59
zygapopey: is this a dual-gpu machine?13:59
popeynope13:59
jdstrandand it's not the same bug since there is udev information on it13:59
zygayes14:00
zygathat's a very good point14:00
zygajdstrand: I kind of feel we should hash the udev tag, it's a leak of all the snaps on popeys's system14:00
jdstrandthere are other leaks of that14:01
zygaI also wonder if there's something we could do to make the list of tags shorter14:02
zygaespecially for udev14:02
zygawe could tag "capability" more than "snap"14:02
zygabut that's unrelated to the bug14:02
jdstrandI think we should consider hashes when we have fine-grained network mediation and/or inode labelling since we'll need to hash for both14:02
zygajdstrand: can we run the device helper14:02
zygato see the error?14:02
jdstrandzyga: sure, go ahead14:03
zygaI mean, I cannot :)14:04
zygalet me come up with the command to run14:05
jdstrandit's in the logs14:05
jdstrand/usr/lib/snapd/snap-device-helper change snap_zzt_zzt14:05
jdstrand              /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:014:05
jdstrandpopey: do you have zzt installed?14:06
zygayeah, I see now14:06
zygausr/lib/snapd/snap-device-helper change snap_writefull_writefull /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:014:06
popeyof course I do :D14:06
zygapopey: can you please run: /usr/lib/snapd/snap-device-helper change snap_writefull_writefull /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 226:014:06
zygaas root14:06
jdstrandpopey: snap list shows it?14:06
popeyjdstrand: yes14:06
jdstrandok14:06
popey /usr/lib/snapd/snap-device-helper: 31: /usr/lib/snapd/snap-device-helper: cannot create /sys/fs/cgroup/devices/snap.writefull.writefull/devices.allow: Directory nonexistent14:07
jdstrandinteresting14:07
jdstrandI have issues like this here without nvidia14:07
jdstrandMar 30 06:33:32 localhost systemd-udevd[23812]: Process '/usr/lib/snapd/snap-device-helper change snap_test-policy-app-consumer_opengl /devices/pci0000:00/0000:00:02.0/drm/card0 226:0' failed with exit code 2.14:07
jdstrand/usr/lib/snapd/snap-device-helper: 31: /usr/lib/snapd/snap-device-helper: cannot create /sys/fs/cgroup/devices/snap.test-policy-app-consumer.opengl/devices.allow: Directory nonexistent14:08
jdstrandoh right14:08
jdstrandso, the cgroup isn't created unless the snap is started14:09
jdstrandso the 'change' operation fails14:09
zygaoh14:09
zygainteresting14:09
zygaI doubt this crashes x14:09
zygabut we should fix it14:09
jdstrandwe should probably just check that and exit 014:09
zygawe should bail14:09
jdstrandthat would not crash x14:09
zygaif there's no group at all14:09
jdstrandit is a spurious log entry14:10
jdstrandit's harmless14:10
zygaI agree14:11
jdstrandpopey: you naming your system 'hal' when looking at udev events feels really weird14:12
popeyhah :)14:12
zygapopey: the private bug you reported, does it contain a backtrace?14:12
popeyzyga: added you as a subscriber, can you see it now? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/176010414:13
jdstrandthis has nothing to do with snappy afaics:14:16
jdstrandSegvAnalysis:14:16
jdstrand Segfault happened at: 0x7f6b00000008: Cannot access memory at address 0x7f6b0000000814:16
jdstrand PC (0x7f6b00000008) not located in a known VMA region (needed executable region)!14:16
jdstrand Stack memory exhausted (SP below stack segment)14:16
jdstrandSegvReason: executing unknown VMA14:16
jdstrandSignal: 1114:16
zygapopey: I can14:17
zygaI agree with jdstrand14:17
mborzeckihellos14:17
mborzeckizyga: 2.32.2 coming later today?14:17
zygahey hey14:17
jdstrandseems like a 'normal' crasher14:17
zygayes, slowly14:18
zygawell, let me check PRs14:18
jdstrandpopey: depending on how adventurous your are feeling, you could revert to the previous core, remove the current core, then refresh core and see if it triggers it14:18
mupPR snapd#4949 closed: tests: fix quoting issues in econnreset test <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4949>14:19
popeyIt wasnt core that triggered it14:19
jdstrandpopey: you could remove/install then. the core idea is that it wuld stress test all the security systems14:20
popeyhm, can't reproduce it with the same snap again14:20
jdstrandI suspect it is poor timing14:20
jdstrandright14:20
jdstrandI would see random stuff like that with intel until the drivers settled down14:21
jdstrandit seemed to be triggerable by clicking on a tab in chromium14:21
zygamborzecki: hey14:22
jdstrandbut most of the time I could click on tabs fine. it is probably memory that is usually set right but occasionaly gets overwritten with garbage14:22
zygamborzecki: I have a small request if you can spare a moment14:22
jdstrandpopey: good luck! (I wish I could be of more help)14:22
popey:)14:23
popeyThanks for the time chaps :)14:23
zygamborzecki: 4963 CC pedronis14:23
zygathis is the nicer variant of the guardian14:23
zygaI'm just wondering if I should prefer the short "sec" or the longer "secure" for variable name :)14:24
mupPR snapd#4963 opened: cmd/snap-update-ns: convert Secure* family of functions into methods <Created by zyga> <https://github.com/snapcore/snapd/pull/4963>14:24
zygajdstrand: ^ nothing to worry about, just small code tweak to avoid a global in an upcoming fix14:24
zygahttps://src.fedoraproject.org/rpms/golang-gopkg-yaml/pull-request/1#request_diff fixes snapd in fedora :)14:35
mupPR snapcraft#1995 closed: options: introduce Project and ProjectInfo <enhancement> <Created by kalikiana> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/1995>14:43
zygajdstrand: how do you feel about https://github.com/snapcore/snapd/pull/439914:47
mupPR #4399: rewrite snappy-app-dev <Created by jdstrand> <https://github.com/snapcore/snapd/pull/4399>14:47
jdstrandzyga: it's in backlog to pickup. I will not get to it for a while yet14:48
zygaok14:48
jdstrandI have to some Ubuntu stuff (apparmor, ufw), finish some policy updates PRs (snapd) and move to snap/usn notifications14:48
jdstrandI'll try to get to it after those things14:49
zygathat's all right, I'm not pushing for it, I'm just going through PRs to see where we are in general14:50
* jdstrand nods14:50
zygaeh14:57
zyga+ MATCH 'Machine is not enabled'14:57
zyga+ canonical-livepatch status14:57
zyga2018/03/30 14:42:51 cannot use livepatch: your kernel "4.13.0-1011-gcp" is not eligible for livepatch updates14:57
zygaerror: pattern not found, got:14:57
zygathat sucks for sure14:57
zyganow I have to disable that test to unbreak master14:57
zygawhy does everything break14:57
zygaand how did this ever pass?14:57
zyga(on GCE)14:57
mupPR snapd#4964 opened: tests: adjust canonical-livepatch test on GCE <Created by zyga> <https://github.com/snapcore/snapd/pull/4964>15:05
* zyga wonders how this even landed15:05
zygapstolowski, jdstrand: ^ (because you're the only pair of reviewers today)15:06
cmarszyga: might be that gce changed their kernel since that test was written?15:06
zygaI strongly doubt that15:06
cmarsjust an idea, dk15:07
zygaI'll check with cachio next week15:07
pstolowskizyga: kk15:07
zygathe livepatch test failed all master PRs15:10
zyganot a great release day either15:10
pstolowski+115:13
cmarsoh, we did just release a new version of the lp client to stable.. it might be doing a better job of checking compatibility than the older version.15:13
zygaahhh15:14
zygathank you for explaining that! that's useful15:14
jdstrandzyga: you're keeping me busy today. +115:18
zygasorry :)15:19
* zyga -> dinner15:27
mupPR snapd#4965 opened: ifacestate: injectTasks helper <Blocked> <Created by stolowski> <https://github.com/snapcore/snapd/pull/4965>15:35
Pharaoh_Atemzyga: ???15:36
popeyis nvidia on 18.04 still busted?15:38
popey(yes)15:38
popeyi am on core from beta, and can't launch ohmygiraffe15:38
zygapopey: ish, we have a fix if stars align I will release it to beta today15:46
zygaPharaoh_Atem: all good now15:46
popeyok, thanks15:46
zygaPharaoh_Atem: golang package in fedora was busted but fantastic people from #fedora-devel figured it out15:47
zygaand now travis slots are not ready15:48
zygapopey: can you try edge?15:48
zygapopey: it should be fine on edge now15:48
popeynow?15:48
zygayes15:48
popeyok15:48
zygathough15:48
zygawell, let's see15:48
popeydoing now15:48
zygathank you15:49
zygabtw, sublime-text?15:49
zygait's in edge now15:49
popeydidnt we discuss this like 3 hours ago?15:49
zygayeah but I want to understand what's the next step15:49
zygasorry, I didn't mean to be nagging15:49
popeyask store people if they can rename st3 to st15:49
zygajust impatient15:49
popeynp15:49
popeyedge works with my nvidia application15:50
zygagreat news15:50
zygaso that's coming in beta15:50
zygasoon (tm15:50
zygawell, I can take an hourly nap now, it looks like travis is starving us after the series of failed builds15:51
=== pstolowski is now known as pstolowski|afk
* zyga EOWs16:25
zygaI'll do the release tomorrow16:25
zygahappy easter everyone :)16:25
kozazyga, happy easter and which version you release?16:28
zygakoza: 2.32.216:36
zygapopey: sublime-text from edge doesn't start on 18.0416:36
zygaI'll check why and get bakc to you16:36
popeypretty sure it worked here when i tried it16:36
zygathe rpath16:37
zyga 0x000000000000000f (RPATH)              Library rpath: [/snap/core/current/lib/x86_64-linux-gnu:/snap/core/current/usr/lib/x86_64-linux-gnu]16:37
zygait doesn't mention sublime-text the snap?16:37
zygaah, there's nothing inside16:38
zygano GTK anything16:38
zygasubl after removing the deb and using snap from edge on bionic https://www.irccloud.com/pastebin/oveW053Y/16:39
zygapopey: since neither the snap nore core ships them16:41
zygapopey: and since the snap has rpath set to just core16:41
zygapopey: those are expected to fail16:41
zygabut I don't know why it works for you16:41
zygacan you run it16:41
zygaand run my magic classic bug finding shell line?16:41
popeyhuh, not on this machine, maybe I tested on 16.04 laptop16:42
zygaI should make that a snap itself16:42
* zyga does so16:52
zygajdstrand: can system-observe grant r on /proc/pid/environ17:03
zygajdstrand: in addition /proc/pid/maps would be nice17:04
zygathere's nothing that provides that onw17:04
zyga*now17:04
jdstrandzyga: I'm uneasy about environ, but added it to my todo to think about17:46
jdstrandwell, I added both things17:46
zygajdstrand: thanks17:46
zygajdstrand: I'm seeing something odd on bionci17:46
zygaI'm editing the profile by hand17:47
zygaand I see a lot of this17:47
zyga^[[AMar 30 19:44:17 t470 kernel: [25362.426443] audit: type=1400 audit(1522431857.647:15305): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.classic-snap-analyzer.classic-snap-analyzer" pid=11067 comm="apparmor_parser"17:47
zygaafter clearly making some changes17:47
zygaand I get a denial17:47
zygaI added "/proc/*/environ r,"17:47
zygarecompiled and got this message and a denial17:47
zygaI will try on artful next17:47
jdstrandzyga: please file a bug against apparmor with a reproducer and jj can take a look next week (he is off this week)17:48
zygaack, thanks17:49
zygait is obviously broken on the -13 kernel ;-)17:59
* zyga found a bug with system key18:39
zyga:-(18:39
zygabuild-id mismatch in system-key https://www.irccloud.com/pastebin/YbDY7GB9/18:44
zygaah, this is "okay"18:45
zygahmm hmm hmm18:45
Caelumzyga: getting an error trying to add our project as a repo: [snappy|http://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed/] Valid metadata not found at specified URL19:25
zygaoh19:25
* zyga looks19:25
zygathose are the docs we have: https://docs.snapcraft.io/core/install-opensuse19:26
zygasudo zypper addrepo http://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed/ snappy19:26
zygathough we should really update that to enable auto refresh19:26
Caelumthat's what I was looking at and it gives me that error19:27
Caelumonce I do a zypper in -y snapd19:28
zygahmm hmm19:28
zygano idea, I'm AFK from my suse box now19:28
CaelumI'll ask on #opensuse-factory19:29
mupPR snapcraft#2043 opened: cli: support exporting login to stdout <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2043>20:15
zygaCaelum: checking now20:19
Caelumthe addrepo command works fine, it's once you try to install snapd20:20
zygaaha20:20
zygabooting now20:20
zyga487 updates from tumbleweed :)20:24
mupIssue snapcraft#1675 closed: Base logic for metadata setters set- <Created by sergiusens> <Closed by kyrofa> <https://github.com/snapcore/snapcraft/issue/1675>20:24
mupPR snapcraft#2002 closed: many: add snapcraftctl command for scriptlets <Created by kyrofa> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/2002>20:24
zygaCaelum: I cannot reproduce your issue20:28
zygaI used "zypper update" to refresh the database20:29
zygaI trusted the key for the system:snappy repo20:29
zygathen I zypper installed snapd20:29
zygainstalling Spotify20:29
mupIssue snapcraft#1671 closed: Rename prepare/build/install to pre-build/build/post-build, and deprecate prepare/build/install <Created by sergiusens> <Closed by kyrofa> <https://github.com/snapcore/snapcraft/issue/1671>20:30
zygaCaelum: and spotify starts and works correctly20:40
=== Lin-Buo-Ren-alt2 is now known as Lin-Buo-Ren
mupPR snapd#4960 closed:  interfaces/serial: change pattern not to exclude /dev/ttymxc (2.32) <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4960>23:20
mupPR snapd#4964 closed: tests: adjust canonical-livepatch test on GCE <Critical> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4964>23:20

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