[05:41] <dobey> anyone have any ideas as to why intel driver might cause X BadMatch/BadPixmap crashes, but only in Nautilus?
[06:25] <larsu> good morning!
[06:46] <pitti> Good morning
[06:51] <larsu> morgen pitti!
[06:52] <pitti> hey larsu, how are you?
[06:52] <seb128> good morning desktopers
[06:52] <seb128> hey larsu pitti
[06:52] <pitti> bonjour seb128 !
[06:52] <larsu> pitti: good thanks! How are you?
[06:58] <pitti> larsu: gut, danke!
[07:03] <didrocks> good morning
[07:04] <seb128> hey didrocks ;-)
[07:04] <larsu> hi didrocks!
[07:04] <didrocks> hey larsu!
[07:04] <didrocks> re seb128
[08:33] <seb128> dobey, thanks for transitioning software-center to CI landing and merges the ubuntu changes back to the upstream vcs
[08:35] <dobey> seb128: sure. was glad to finally get that done yesterday :)
[08:37] <seb128> :-)
[08:45]  * seb128 starts wondering if upgrading nautilus was good idea
[08:46] <didrocks> seb128: for the icon size or something else?
[08:47] <didrocks> I still find the move action to be confusing btw (especially if you move files to a network share)
[08:47] <seb128> quite some of the changes feel like regressions
[08:47] <seb128> upstream is reverting some of those in 3.20 so they seem to agree
[08:47] <seb128> like they dropped the context menu to delete and are restoring it
[08:47] <seb128> same for the one to create symlinks
[08:48] <seb128> the "in toolbar" copy dialog is less obvious
[08:48] <seb128> the icons are too big
[08:48] <seb128> the menubar patch is way more work that I was expecting
[08:48] <didrocks> the copy icon is clearly not obvious
[08:48] <seb128> like larsu has been on it for almost a month, I think we could have worked on more useful things
[08:48] <seb128> they change in trunk to open the popup copy dialog automatically
[08:48] <didrocks> even after knowing where it is, I do the action and always have this 0.5s "did I really start copying/moving?"
[08:49] <seb128> to workaround a bit the fact that it's not obvious
[08:49] <seb128> I'm going to backport that and see how it feels
[08:49] <didrocks> yeah, that one (and icon size) are the most obvious issues to me
[08:49] <seb128> but yeah, the icons size and the copy UI are the ones that concerns me most atm
[08:49] <didrocks> I even didn't notice about the delete removal
[08:50] <didrocks> but I either use del or command line
[08:50] <seb128> same here
[08:50] <didrocks> so not a good example :)
[08:50] <seb128> same for symlinks
[08:50] <seb128> I never use those
[08:50] <seb128> or at least not in nautilus
[08:50] <didrocks> yeah, I wonder if people use this
[08:50] <seb128> they are more "tech" work to me
[08:50] <didrocks> yep
[08:50] <seb128> and I use nautilus to manage my datas a bit
[08:50] <seb128> like move photos around
[08:51] <seb128> or clean up my downloads folder
[08:51] <didrocks> yeah, I wonder about the delete in context menu
[08:51] <didrocks> I never see "regular users" using the context menu
[08:51] <dobey> i just want my nautilus to not crash arbitrarily
[08:51] <seb128> dobey, does it do that in xenial for you?
[08:52] <dobey> seb128: haven't tried xenial. it does in trusty, i think because of intel drivers. i sometimes get BadPixmap crashes in it :(
[08:54] <seb128> :-(
[08:54] <seb128> I'm not aware of that one
[09:00] <willcooke> morning desktoppers
[09:00] <willcooke> seb128, how did the CC catch up go?  All ok?
[09:01] <dobey>          buf = "BadDrawable (invalid Pixmap or Window parameter)", '\000' <repeats 15 times>
[09:01] <dobey> :(
[09:02] <seb128> dobey, :-/
[09:02] <didrocks> good morning willcooke
[09:02] <seb128> willcooke, hey, it went very well, thanks
[09:02] <seb128> willcooke, didrocks and Laney joined
[09:02] <seb128> didrocks gave some updates on the online dash status and the code in
[09:02] <seb128> and Laney discussed a bit gnome-software
[09:02] <willcooke> super, thanks seb128, didrocks Laney
[09:03] <willcooke> I will go find the logs actually...
[09:03] <seb128> otherwise they seemed happy to know that we have active contributors on GNOME and other things and not much frictions
[09:03] <seb128> k
[09:03] <didrocks> yw
[09:03] <dobey> i don't know where the crash reports are going though :(
[09:03] <Laney> yo
[09:03] <didrocks> hey Laney
[09:03] <Laney> happy first friday!
[09:04] <dobey> hmm, nautilus package has 1800 open bugs :(
[09:06] <larsu> Laney: happy end of first week!
[09:06] <dobey> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1071155 is similar anyway
[09:07] <seb128> hey Laney, happy friday!
[09:07] <dobey> hrmm, 9 open bugs in nautilus for sig 5 in _XReply()
[09:07] <dobey> and 5 of them have bug heat > 160
[09:07] <dobey> other 4 are at 10
[09:08] <seb128> I think the issue is that not many people know how to deal with those bugs
[09:08] <seb128> they don't feel like gtk/gnome issues
[09:08] <dobey> they are a bit of a pain to debug, yeah
[09:09] <dobey> really needs someone who knows X well enough, to poke at them
[09:10] <dobey> not sure who's working on X for us any more though
[09:11] <seb128> not many people, that's part of the issue
[09:11] <seb128> tjaalton is but I don't think he has enough free slots to look at those
[09:11] <willcooke> what seb128 said
[09:13] <dobey> :(
[09:14] <tjaalton> dobey: happens only on intel? install the xenial driver, works fine in wily
[09:15] <davmor2> willcooke: the phone has a phone icon now when you connect it oh pretty :D
[09:16] <dobey> tjaalton: i'm running the wily kernel already. also it works fine on my intel laptop. it only crashes on my workstation
[09:16] <tjaalton> dobey: no, intel X driver
[09:16] <tjaalton> or try forcing uxa in xorg.conf
[09:17] <tjaalton> what generations are those?
[09:17] <hikiko> hi
[09:17] <dobey> when's the wily xorg going to end up in trusty for HWE?
[09:17] <tjaalton> once libdrm is past NEW
[09:17] <dobey> workstation is haswell
[09:17] <tjaalton> is when the rest is getting pushed
[09:18] <dobey> not sure on the laptop, i think also haswell
[09:18] <dobey> maybe ivybridbge
[09:18] <tjaalton> ok
[09:18] <tjaalton> my desktop is ivybridge, no issues there
[09:18] <tjaalton> on wily
[09:19] <dobey> i don't recall if it was crashing for me when i had ivybridge in my workstation
[09:19] <willcooke> davmor2, nice!!
[09:19] <tjaalton> what's the resolution on workstation?
[09:19] <dobey> 4k
[09:20] <tjaalton> that could be it
[09:20] <dobey> i had an nvidia card in for a week, and nautilus didn't crash on it
[09:20] <dobey> but had enough other problems with that, that i just returned it
[09:21] <tjaalton> so try forcing uxa, or pull the X driver from xenial
[09:22] <seb128> Laney, is there anything keeping gnome-calendar in main? it doesn't seem to be on the current iso yet?
[09:22] <seb128> I guess it's on your todolist?
[09:24] <Laney> I seeded it
[09:24] <Laney> so the Task presumably
[09:25] <seb128> k
[09:26]  * Laney runs ./update
[09:27] <Laney> you can't do that until after the promotion
[09:27] <Laney> so easy to lose it if there is a gap
[09:27] <seb128> that's a bit backward
[09:27] <seb128> because usually we do the promotion once something tries to pull the binary in
[09:27] <Laney> seed -> component mismatch -> promote -> ./update
[09:28] <seb128> but oh well, it's minor
[09:28] <seb128> k
[10:02] <seb128> mitya57, hey, thanks for updating nautilus in decembre, you didn't use the packaging vcs though? (there was commit/not released work that you seem to not have included and your version is not in there) or did you just forgot to push?
[10:06] <seb128> larsu, I'm working on a nautilus update, how is the menubar change coming? can I give it a test build even if it's not ready it to be proposed? just to see how it's working
[10:10] <larsu> seb128: I'm done with the action rewiring and am writing xml right now
[10:10] <seb128> k
[10:10] <larsu> you'll need a gtk patch too
[10:10] <larsu> let me open a bug for that one first
[10:10] <seb128> danke
[10:10] <seb128> is that something upstream is likely to agree on?
[10:10] <seb128> or an ubuntu hack?
[10:10] <larsu> upstream
[10:11] <larsu> well, depends on desrt ;)
[10:11] <seb128> k
[10:13] <desrt> hi
[10:13] <Laney> hi desrt!!!
[10:13] <willcooke> morning desrt
[10:14] <desrt> Laney!
[10:14] <larsu> morning desrt :)
[10:14] <desrt> willcooke: g'morn
[10:14] <desrt> hihi larsu
[10:14] <desrt> and hello didrocks and seb128 :)
[10:14] <seb128> hey desrt
[10:15] <didrocks> good morning desrt
[10:15] <larsu> desrt: since you're here - care to look at https://bugzilla.gnome.org/show_bug.cgi?id=760312 ?
[10:16] <seb128> bah
[10:16] <larsu> seb128: that's the patch I was talking about ^
[10:16] <seb128> bzr bd-do doesn't like lp:~ubuntu-desktop/nautilus/ubuntu it seems
[10:16] <seb128> UnicodeEncodeError
[10:16] <seb128> grrrr at python
[10:16] <seb128> larsu, thanks
[10:16] <didrocks> the usual :)
[10:17] <desrt> larsu: 'hi' was a subtle way of saying "i hope i get a bug link" :)
[10:17] <larsu> desrt: oh. I read it as "hi"
[10:17] <pitti> hey desrt, how are you? (and where?)
[10:19] <desrt> larsu: and yet i got my bug link =)
[10:19] <larsu> desrt: totally unrelated :P
[10:19] <desrt> pitti: good morning :D
[10:19] <desrt> pitti: i am before coffee, so i have difficulty answering "how are you" :)
[10:20] <desrt> and i am in toronto, where it is still very dark indeed
[10:20] <Laney> isn't it 05:20?
[10:21] <desrt> that is correct.
[10:21]  * Laney screams
[10:21] <desrt> larsu: are you sure this patch correctly handles the remoteactiongroup/platform_data stuff?
[10:22] <larsu> desrt: why would that have anything to do with it?
[10:22] <desrt> because GtkApplicationWindow doesn't wire that through, iirc
[10:22] <desrt> i'll do the review in the bug...
[10:22] <larsu> ugh, are you sure?
[10:23] <desrt> fairly sure, yes.
[10:25]  * desrt hopes that 5am pre-coffee reviewing doesn't come back to bite her
[10:26] <larsu> desrt: UNITY!
[10:26] <larsu> (thanks for the review)
[10:26] <desrt> "needs word" is certainly less dangerous than "accepted-commit_now"
[10:29] <larsu> heh
[10:29] <larsu> desrt: the gist: I want to export additional actions from inside a subclass of GtkApplicationWindow
[10:30] <desrt> amusing story of the day: (due to various online posts drawing equivalences between them) google translate is now confusing "russian federation" with "mordor", "russians" with "occupiers" and "sergey lavrov" with "sad little horse"
[10:30] <desrt> larsu: why can't the subclass simply add the actions like everyone else does?
[10:32] <larsu> desrt: that sounds horribly inefficient...
[10:32] <desrt> what kind of actions are we talking here, and how many?
[10:32] <larsu> but I'd rather do that than deal with the platform data mess
[10:32] <larsu> desrt: normal amount, nothing fancy
[10:33] <desrt> use action entries?
[10:33] <desrt> reimplementing the actiongroup infra is annoying and awkward and you're probably going to get it wrong
[10:33] <desrt> (for reasons like platform_data...)
[10:39] <larsu> desrt: hm? The actions already exist
[10:39] <larsu> in some widget deeper down
[10:39] <larsu> I don't like that reimplementing the interface doesn't work
[10:40] <larsu> seems like something that totally should work
[10:41] <desrt> we could possibly detect if you also reimplement RemoteActionGroup for yourself...
[10:41] <desrt> or we could implement it directly on the window itself, as well
[10:41] <desrt> that almost makes sense, in fact
[10:41] <larsu> yeah.... clearly
[10:42]  * larsu shall not shave this yak now though to not make seb128 more impatient ;)
[10:42] <larsu> desrt: thanks for catching this anyway
[10:42] <desrt> if you want to do the remoteactiongroup impl on the window itself and do a patch for that, i'd be happy to look at it... provided you give a better answer on the "why can't you just use actions" question
[10:43] <desrt> because i agree that it would be theoretically nicer
[10:43] <desrt> same argument could be made for GApplication itself
[10:43] <larsu> why didn't you do it this way in the first place i wonder?
[10:44] <desrt> it used to be possible to provide your own action group
[10:44] <desrt> maybe still is, although very much deprecated, and for a long time
[10:44] <desrt> it was the early days before we figured out what was really a good pattern here
[10:44] <larsu> ah, right
[10:44] <desrt> and before GActionMap existed
[11:02] <andyrock> morning all
[11:05] <willcooke> hey andyrock
[11:19] <hikiko> Trevinho|OFF,
[11:19] <hikiko> andyrock,
[11:19] <hikiko> I have a question
[11:20] <andyrock> yup
[11:20] <hikiko> without any of my code
[11:20] <hikiko> the old shadows update all the time
[11:20] <hikiko> it's like a busy loop
[11:21] <hikiko> do you know that it was intentional or there's something that marks regions as dirty etc?
[11:21] <hikiko> i mean
[11:21] <hikiko> that shouldn't happen anyway
[11:21] <andyrock> i don't think it's intentional
[11:21] <hikiko> but do you know why it happens?
[11:21] <andyrock> maybe it's a workaround for something
[11:22] <andyrock> to be honest nope
[11:22] <hikiko> mmm then I have to fix this first, otherwise unity will calculate the shape (and perform convolution) at almost every frame with the new shadows...
[12:05] <hikiko> andyrock, Trevinho|OFF ignore :) it was a program I left open that was causing the frequent updates!
[12:19] <didrocks> pitti: probably a very stupid question, but how can I trigger an autopkgtests using the test request format?
[12:21] <pitti> didrocks: ah, ATM you can't, I'm afraid; firewall limits that to snakefruit (or do you have access there?)
[12:21] <didrocks> pitti: I do have access here, ~ubuntu-archive
[12:21] <pitti> didrocks: ah
[12:21] <didrocks> but I don't see anything handy in run-autopkgtest --help
[12:21] <pitti> didrocks: now, I didn't yet expose those in run-autopkgtest
[12:21] <didrocks> ah, I'm not that crazy :)
[12:22] <pitti> amqp-publish -u<EMAIL_ADDRESS>-r  debci-trusty-amd64 -b 'ubuntu-make-master {"test-git": "https://github.com/ubuntu/ubuntu-make.git", "ppas": ["ubuntu-desktop/ubuntu-make-builddeps", "ubuntu-desktop/ubuntu-make"]}'
[12:22] <pitti> didrocks: that's what I used for testing back then
[12:22] <pitti> didrocks: shoudl be straightforward to add it to run-autopkgtest, similar to --ppa
[12:23] <didrocks> SECRET will be replaced by the right thing in amqp-publish?
[12:23] <pitti> didrocks: if you want to have a go at it, please do; otherwise I'll try to do that on Monday
[12:23] <pitti> didrocks: no, I just edited it out for pasting into public IRC :)
[12:23] <didrocks> pitti: well, I can have a look, but let me ensure it can runs properly first :)
[12:23] <didrocks> ok ;)
[12:23] <didrocks> run*
[12:23] <didrocks> pitti: also, that I can play with the env variables and such, let's see
[12:24] <didrocks> between that and https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Test_request_format, should be workable :)
[12:24] <pitti> didrocks: for experiments it would be good if you could skip armhf for now, as that's horribly swamped
[12:24] <pitti> didrocks: go nuts on x86, they have plenty of capacity
[12:24] <pitti> . o O { me is *sooo* happy to be able to say that now, since Tuesday ☺ }
[12:25] <didrocks> haha! ok :) I just need one arch anyway for testing this
[12:29]  * didrocks looks fot amqp-publish
[12:29] <didrocks> for*
[12:31] <didrocks> pitti: amqp-tools isn't installed on snakefruit, though?
[13:18] <pitti> didrocks: no, it's not; I ran that from my adt control instance
[13:18] <pitti> didrocks: I can run stuff for you if you wwant
[13:18] <didrocks> pitti: well, it was easier for me to implement the options, I did this :p
[13:19] <didrocks> I saw the job running in the web ui, but then, it seems to fail
[13:19] <pitti> didrocks: ah, just got a worker failure mail
[13:19] <didrocks> the issue is that I can't find the logs back
[13:19] <pitti> W: Failed to fetch http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make-builddeps/ubuntu/dists/xenial/main/source/Sources  404  Not
[13:19] <pitti> +Found
[13:19] <pitti> didrocks: right, sorry; this counts as a "tmpfail", i. e. it thinks that this is a temporary glitch
[13:19] <didrocks> yeah, I think if test-git or test-bzr are provided, we shouldn't force a ppa or trigger
[13:19] <pitti> didrocks: so it retries instead of posting the log
[13:20] <pitti> didrocks: you don't need a trigger, but you need a PPA
[13:20] <didrocks> no, it's a real failure, I don't have anything in the ppa for the current devel serie
[13:20] <pitti> let's please not clutter the ubuntu result container for these
[13:20] <didrocks> so the archive doesn't exit
[13:20] <didrocks> exist*
[13:20] <pitti> ah, makes sense
[13:20] <didrocks> hum, should I do a dummy upload in the ppa then?
[13:21] <pitti> didrocks: usual workaround is to copy (or upload) a package into it and delete it again
[13:21] <didrocks> yeah
[13:21] <pitti> didrocks: upload, or copy-package with binaries
[13:21] <didrocks> can do this
[13:21] <didrocks> anyway, I tried on trusty then
[13:21] <didrocks> with the ppas
[13:21] <didrocks> and same, seems to have failed quite quickly
[13:21] <didrocks> (the 2 archives exists here)
[13:21] <didrocks> but I don't see anything in the ui
[13:21] <pitti> adt-run [13:19:34]: @@@@@@@@@@@@@@@@@@@@ apt-source ubuntu-make-master
[13:21] <pitti> E: Unable to find a source package for ubuntu-make-master
[13:22] <didrocks> making sense :)
[13:22] <pitti> this looks like this didn't get the git argument
[13:22] <didrocks> but the doc says it won't try to use the "pkg" as a "pkg"
[13:22] <didrocks> ah
[13:22]  * didrocks check for typos
[13:22]  * pitti looks at the full log
[13:24] <pitti> Received request for package ubuntu-make-master on trusty/amd64; params: {u'ppas': [u'ubuntu-d
[13:24] <pitti> esktop/ubuntu-make-builddeps', u'ubuntu-desktop/ubuntu-make'], u'test_git': u'https://github.com/ubuntu/ubuntu-make.git'}
[13:24] <pitti> didrocks: s/test_git/test-git/
[13:24] <pitti> did I typo that on the wiki?
[13:24] <didrocks> I guess you did
[13:25] <pitti> no, it's ok there
[13:25] <didrocks> waow
[13:25] <didrocks> I can't read
[13:25] <didrocks> indeed, I reopened the page and it's there
[13:25] <pitti> well, to be fair these pretty well look the same :)
[13:25]  * pitti hugs didrocks
[13:26]  * didrocks hugs pitti back
[13:26] <didrocks> ok, so running on trusty
[13:26] <didrocks> let's see
[13:27] <pitti> didrocks: I killed all adt-runs for u-make for now, to break the infinite retry loop
[13:27] <pitti> seems for this kind of operation this needs to become more clever
[13:30] <didrocks> urgh, sorry for the retry loop on this then :)
[13:30] <didrocks> did you kill last one?
[13:30]  * didrocks looks
[13:30] <didrocks> no, so looking at http://autopkgtest.ubuntu.com/running.shtml#pkg-ubuntu-make-master :)
[13:31] <pitti> didrocks: no need to be sorry; it's  my ongoing quest for minimizing human activity in a system where everything can (and does) fail all the time
[13:31] <pitti> didrocks: killed that too
[13:31] <didrocks> pitti: oh?
[13:31] <didrocks> that one wasn't with the correct parameters?
[13:31] <didrocks> (my last retry after the fix)
[13:32] <pitti> didrocks: oh sorry, I thought you said "this one is also old"
[13:32] <pitti> didrocks: as it already ran for 11 mins
[13:32] <didrocks> pitti: well, it's installing ubuntu-desktop! :p
[13:32]  * didrocks reruns
[13:32] <pitti> ok, running again
[13:33] <didrocks> pitti: so, then, I should see it stored in http://autopkgtest.ubuntu.com/packages/, right?
[13:33] <didrocks> (after the first run)
[13:33] <pitti> http://paste.ubuntu.com/14437805/ .. totally trivial command line, eh!
[13:33] <pitti> didrocks: no, there's no web UI frontend for PPAs right now
[13:34] <didrocks> pitti: ahah, and that's without the --env parameter still! :p
[13:34] <pitti> didrocks: if you run it against the ubuntu archive, it'll appear there, but not for PPAs; so far we haven't needed one,  but we could set up something
[13:34] <didrocks> ok
[13:34] <pitti> didrocks: no problem -- just start another one with env and let them run in parallel
[13:34] <didrocks> pitti: oh right, the *cloud*
[13:34]  * didrocks tries
[13:35] <didrocks> (done)
[13:35] <didrocks> this one should only run a pep8 test
[13:35] <pitti> didrocks: it's fine if you run 10 in parallel occasionally; if you need much more, and it starts blocking things, we need to ask for moar powah
[13:36] <didrocks> indeed, it will still takes time though until we have real ubuntu-desktop images
[13:36] <didrocks> pitti: I don't remember, the ppas artefacts archive in swift will be per ppa per release, right?
[13:37] <didrocks> (so we can remove the vivid one at some point, right?)
[13:37] <pitti> didrocks: correct
[13:37] <didrocks> sounds good :)
[13:37] <pitti> didrocks: oh, you don't have "ubuntu-desktop" in d/t/control Depends:, but call apt-get yourself?
[13:37] <pitti> didrocks: do you call it with $(which eatmydata 2>/dev/null) apt-get ?
[13:38] <pitti> didrocks: if not, it'll be awfully slow (test Depends: do that automatically)
[13:38] <didrocks> pitti: ah, I don't, I guess I should. There was a reason I minimize the deps in d/t/control (that was before the holidays…)
[13:38] <didrocks> pitti: ok, adding eatmydata
[13:38] <didrocks> ah yeah, the lines with test deps was getting really long
[13:38] <didrocks> and I have this "setup" tests
[13:38] <pitti> didrocks: testbeds have that magic dpkg force-unsafe-io flag in the config, but it doesn't seem to be nearly as fast as eatmydata
[13:39] <didrocks> and I need to have all them listing the same deps, to reuse the same test bed
[13:39] <didrocks> that's why I put the dep setup logic in setup (in addition to the other setup parts)
[13:39] <pitti> WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.
[13:39] <pitti> 0 upgraded, 1254 newly installed, 0 to remove and 0 not upgraded.
[13:39] <pitti> Need to get 534 MB of archives.
[13:39] <didrocks> yeah, I'm using simple apt, which is fine in trusty and xenial
[13:39] <pitti> After this operation, 2015 MB of additional disk space will be used.
[13:39] <pitti> pas mal :)
[13:39] <didrocks> ahah :)
[13:40] <didrocks> if you want to kill those 2 runs because they will be slow due to no eatmydata, please feel free
[13:40] <pitti> didrocks: I don't care
[13:40] <didrocks> I'm adding that to master meanwhile
[13:40] <didrocks> ok :)
[13:40] <pitti> let's just let it finish
[13:40] <pitti> didrocks: queues are empty right now anyway (except arm)
[13:40] <didrocks> yeah
[13:40] <didrocks> pitti: btw, if you are interested in the structure: https://github.com/ubuntu/ubuntu-make/tree/master/debian/tests
[13:41] <didrocks> you basically have: pep8/small/medium/large
[13:41] <didrocks> which are the real tests
[13:41] <didrocks> (you can pass TESTS="small large" for instance)
[13:41] <didrocks> no parameter is what we used to have "pep8 small"
[13:41] <didrocks> collect-coverage is for collecting and archiving global coverage report
[13:42] <didrocks> custom is used when you set one or more specific tests
[13:42] <didrocks> like TESTS="tests/small/test_foo.py:Bar.baz tests/…"
[13:42] <didrocks> and TESTS=all runs everything but custom ofc
[13:43] <didrocks> (well, it runs custom which is skipped)
[13:43] <pitti> didrocks: ah, https://github.com/ubuntu/ubuntu-make/blob/master/debian/tests/control is clever -- so you have a separate "setup" job and re-use the testbed for everything
[13:44] <pitti> didrocks: btw, there's no need to repeat all the stanzas
[13:44] <pitti> didrocks: as long as the depends:, restrictions: etc. are identical, you can just do
[13:44] <pitti> Tests: foo bar baz
[13:44] <didrocks> oh, even better then!
[13:44]  * didrocks modifies
[13:45] <pitti> didrocks: wouldn't it be easier to run https://github.com/ubuntu/ubuntu-make/blob/master/debian/tests/setup-testbed#L17 with "needs-root"?
[13:46] <pitti> didrocks: calling sudo in tests is a bit meh (if you do it, please call "sudo -n", to avoid eternal hangs because of password questions)
[13:46] <pitti> didrocks: you can do su -c "commands here" $ADT_NORMAL_USER
[13:46] <didrocks> ah, there is a variable for this :)
[13:46] <didrocks> I was going to ask how to not hardcode "ubuntu" for user name
[13:47] <didrocks> (I still have some commands I don't want as root)
[13:47] <pitti> meh, apt-get install has some trouble in the test
[13:47] <didrocks> argh?
[13:47]  * didrocks looks
[13:48] <pitti> didrocks: you can't :) (I just looked at the tail -f of the log)
[13:48] <pitti> http://paste.ubuntu.com/14437883/
[13:48] <didrocks> ah ok, so it's not the one running I see (I only see one btw? I maybe typoed the env variable…)
[13:49] <pitti> didrocks: that's the old one without --env, yes (no "env" in the command line)
[13:49] <didrocks> hum, I didn't get this kind of no tty issue on my xenial vm at least
[13:49] <pitti> DEBIAN_FRONTEND=noninteractive ?
[13:49] <didrocks> so, debconf doesn't really like it
[13:49] <didrocks> yeah, I didn't setup anything for this though here
[13:50] <didrocks> I wonder if a default changed
[13:50] <pitti> although wait, this is already set in tests
[13:50] <pitti> but this doesn't make it through  sudo
[13:50] <pitti> didrocks: that test run finished now (due to apt-get error), should be in swift now
[13:51] <pitti> didrocks: which PPA was that against?
[13:51] <didrocks> pitti: ubuntu-desktop/ubuntu-make
[13:51] <didrocks> (as I takes last ppa from the list IIRC to match against)
[13:51] <pitti> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ubuntu-desktop-ubuntu-make?format=plain
[13:52] <pitti> sorry, not xenial, trusty
[13:53] <pitti> didrocks: ah, this one looks happier, but that didn't install -desktop<EMAIL_ADDRESS>[13:54] <didrocks> ah, they are not stored
[13:54]  * didrocks was stupidely looking at the first one
[13:55] <didrocks> so, I can ofc now change the Depends: line
[13:55] <didrocks> as I have everything in one line
[13:56] <pitti> didrocks: you can line-break test control just the same way as debian/control, FYI
[13:56] <didrocks> but that would mean that I don't add needs_root for setup (but I can add -n to sudo)
[13:56] <didrocks> ah nice :)
[13:56] <pitti> didrocks: you still need it to configure autologin and stuff though?
[13:56] <didrocks> yeah, and also the setup does some extra stuff
[13:59] <didrocks> oh, actually, I didn't really try to setup the testbed that way
[13:59] <pitti> hah, didrocks is serial-killing workers again :)
[13:59] <didrocks> as I already had an ubuntu-desktop VM
[13:59] <didrocks> (the adt one)
[13:59] <didrocks> and reused that one
[13:59] <didrocks> so sudo apt install ubuntu-desktop was a noop (only updating the metapacakge)
[14:00] <didrocks> pitti: I guess I'm going to start now from a cloud image as in the infra
[14:00] <didrocks> and see what's going on when installing ubuntu-desktop without any tty
[14:00] <didrocks> (or ssh)
[14:00] <pitti> didrocks: potential gotcha: test Depends: don't install recommends by default; if you do need them, Restrictions: needs-recommends
[14:02] <didrocks> pitti: ok, shouldn't be a problem. If I want to install ubuntu-make itself, even from a git repo, it will only try to match the package name, right? not the real version (like, if git changed debian/changelog but it's not released yet?)
[14:02] <pitti> didrocks: right, test-git is *only* for the test (debian/tests/control); it doesn't get built
[14:03] <pitti> --env=T --env=E --env=S --env=T --env=S --env== --env=p --env=e --env=p --env=8
[14:03] <pitti> didrocks: I don't think that was intended
[14:03] <pitti> didrocks: array vs. string confusion somewhere?
[14:03] <pitti> didrocks: "env" parameter is a list, not a string
[14:04] <didrocks> hum, not with adt-run, though?
[14:04] <didrocks> I had to sue --env="TESTS=medium large"
[14:04] <didrocks> for instance
[14:04] <pitti> didrocks: no, but that's what is on the command line
[14:04] <didrocks> yeah
[14:04] <didrocks> I checked the wrapper
[14:04] <didrocks> it's using a string parameter
[14:05] <pitti> didrocks: i. e. I suppose your run-adutopkgtest change submits it as a string, not a list
[14:05] <didrocks> so somewhere else in the chain?
[14:05] <didrocks> ah, it's not passed as such to adt-run?
[14:05] <pitti> didrocks: it needs to be {"env": ["foo=bar", ...]}
[14:05] <pitti> not {"env": "foo=bar"}
[14:06] <pitti> didrocks: so every entry in "env" is passed as --env=value, yes
[14:06] <pitti> but "every entry" in a string is a character onnly
[14:06] <pitti> {"test-git": "https://github.com/ubuntu/ubuntu-make.git", "ppas": ["ubuntu-desktop/ubuntu-make-builddeps", "ubuntu-desktop/ubuntu-make"], "env": "TESTS=pep8"}
[14:06] <didrocks> ok, I was still puzzled by the adt-run --env="TESTS=medium large" <…> format :)
[14:06] <pitti> didrocks: ^ that's what was in the queue
[14:06] <didrocks> but ok, making sense
[14:07] <didrocks> I would have had --env="TESTS='medium large'" <…> for instance
[14:07] <pitti> but it needs to be ... "env": ["TESTS=pep8"]}
[14:07] <pitti> didrocks: run-autopkgtest shoudl accept multiple --env options, then it'll automatically be a list
[14:09] <didrocks> pitti: ok, modified as such
[14:09] <attente> good morning all
[14:09] <didrocks> good morning attente
[14:09] <seb128> hey attente
[14:09] <attente> hi didrocks, hi seb128
[14:10] <pitti> didrocks: so that, eatmydata (if available), and DEBIAN_FRONTEND=noninteractive or moving the installation to d/t/control?
[14:10] <didrocks> pitti: moving the installation, one sec, finish up formatting and pushing
[14:10] <attente> seb128: thanks for approving that u-s-d merge. do you know who i should ping about maliit-inputcontext-gtk?
[14:10] <didrocks> and adding -n to remaining sudo calls
[14:10] <pitti> didrocks: btw, adt-run has a --testname option which sounds like what your $TESTS does; it sounds useful to expose that as test param too?
[14:10] <seb128> attente, no idea, try asking kenvandine or bfiller maybe?
[14:11] <seb128> they probably can redirect you
[14:11] <attente> seb128: sure, thanks
[14:11] <seb128> yw
[14:11] <pitti> didrocks: then it will only run that given test from d/t/control, not all of them
[14:11] <didrocks> pitti: mine is a little bit more complex than this, I always need setup and collect to run
[14:12] <didrocks> + the testname can be more specific
[14:12] <pitti> ah, ok
[14:12] <didrocks> like "tests/small/test_foo.py:Bar/baz tests/large/test_games:Unity3DTests"
[14:12] <didrocks> for instance
[14:12] <didrocks> to only run those 2
[14:12] <didrocks> (help debugging as some tests can take some very long time
[14:12] <didrocks> )
[14:13] <didrocks> and that results in the end to "setup/custom/collect" to be run
[14:13] <didrocks> (pep8/small/medium/large are all "passing", doing nothing)
[14:13] <didrocks> and custom do the right thing
[14:13] <didrocks> pitti: making more sense? ^
[14:13] <pitti> didrocks: yes, it does
[14:14] <kenvandine> attente, try Elleo
[14:14] <pitti> just looking for potential simplifications, but cf. "as simple as possible, but no simpler" :)
[14:14] <attente> kenvandine: thanks
[14:16] <kenvandine> np
[14:18] <didrocks> pitti: ah, but I remove ubuntu-make in some condition
[14:18] <didrocks> conditions
[14:18] <didrocks> pitti: so, I will need to keep that one installed in setup-testbed, right?
[14:18] <didrocks> pitti: or is adt-run a little bit dummy and just parsing d/t/c and see if things match?
[14:19] <didrocks> (even if tests can remove some packages)
[14:19] <didrocks> (I remove ubuntu-make in case of branch testing to ensure there is no confusion on what is running)
[14:19] <pitti> didrocks: yes, it only parses Depends:, it doesn't check what's actually installed on the testbed after a test
[14:19] <didrocks> ok ;)
[14:20] <didrocks> as I remove umake/ dir when running system setup to ensure I don't have an import which is magically resolved by the local folder (also, coverage report is then confused)
[14:24] <didrocks> pitti: looking good to you? https://github.com/ubuntu/ubuntu-make/blob/master/debian/tests/control
[14:25] <didrocks> hope you support trailing commas :)
[14:25] <pitti> didrocks: needs-recommends is really necessary with this?
[14:25] <pitti> didrocks: I think it does, test it locally with your desktop image? (just the smallest test you have, pep8?)
[14:26] <didrocks> pitti: well, I use needs-recommends to have a desktop image as close as possible to reality
[14:26] <didrocks> let's see with my dekstop image how that goes
[14:26] <pitti> didrocks: I haven't tested multi-line Tests: and Restrictions:, thanks for being guinea pig :)
[14:26] <pitti> didrocks: right, but reality changes quite often :)
[14:27]  * didrocks *guineas*
[14:27] <didrocks> :p
[14:27] <pitti> didrocks: and libreoffice, orca, thunderbird etc. will hardly matter?
[14:27] <didrocks> that's true, I'm still worried about things we miss that can interfere though (even if I mostly need lightdm and unity TBH)
[14:27] <pitti> didrocks: I'd actually argue the other way around: If u-make depends on something which isn't a depends: of u-desktop, then that dependency is missing
[14:28] <pitti> didrocks: well, leave it in for now, and then we can just try a run without
[14:28] <didrocks> pitti: well, it's more for frameworks we install on, TBH, than umake itself
[14:28] <didrocks> but yeah, agreed
[14:29] <pitti> no recommends: should make the install a looot faster
[14:29] <didrocks> yeah, if we don't start from a desktop image.
[14:29] <didrocks> let's get the thing running and then, we can give a try
[14:30] <didrocks> it*
[14:30] <pitti> agreed
[14:31] <didrocks> ok, multi-line worked!
[14:31] <pitti> cool
[14:31] <didrocks> so, let's try a run (running small tests, which are less than a minute)
[14:31]  * pitti puts an "officially didrocks approved" stamp onto autopkgtest
[14:31] <didrocks> that will test the env variable again :)
[14:31] <didrocks> don't go toooo fast :)
[14:34] <didrocks> http://autopkgtest.ubuntu.com/running.shtml#pkg-ubuntu-make-master
[14:34] <didrocks> let's see…
[14:35] <didrocks> at least env make sense :)
[14:35] <pitti> --env=TESTS=pep8
[14:36] <pitti> yep
[14:36] <pitti> and it's running
[14:37] <didrocks> I'm trying a second one in parallel which should give: --env="TESTS=pep8 small"
[14:38] <pitti> didrocks: I see three running tests, all have --env=TESTS=pep8 only
[14:39] <didrocks> 3? I made 2 requests…
[14:39] <didrocks> weird
[14:39] <seb128> bah, laptop not booting anymore
[14:39] <seb128> took me a bit to figure out that it boots with the previous kernel
[14:39] <didrocks> and I only see one in the web ui
[14:39] <seb128> also grrrr at systemd for not being able to reboot a machine
[14:40] <seb128> it's stucked for ever on the dots animate and never reboot, need to sit on the power key
[14:40] <pitti> didrocks: yeah, web UI bug -- it can't tell apart multiple tests with exactly the same params
[14:41] <didrocks> pitti: my 2 requests were: ubuntu-make-master
[14:41] <didrocks> hum
[14:41] <didrocks> grrr @middle-click bug
[14:41] <didrocks> http://paste.ubuntu.com/14438198/
[14:41] <didrocks> better
[14:42] <pitti> didrocks: hm, that got eaten somewhere then
[14:43] <didrocks> pitti: yeah, let's see first at least if one requests goes successfully to the end :)
[14:43] <didrocks> btw, run-autopkgtest isn't versioned?
[14:43] <pitti> didrocks: versioned how?
[14:43] <didrocks> (I just modified it on snakefruit, didn't seem to have been bzr add on the vcs)
[14:44] <pitti> didrocks: oh, britney2-ubuntu is in bzr
[14:44] <pitti> didrocks: you should see a bzr diff on snakefruit if you modified it there
[14:44] <pitti> didrocks: and it's there
[14:44] <didrocks> $ bzr diff run-autopkgtest@
[14:44] <didrocks> bzr: ERROR: Path(s) are not versioned: "run-autopkgtest@"
[14:45] <pitti> didrocks: ah, bin/run-autopkgtest is a symlink to ~/proposed-migration/code/b2
[14:45] <didrocks> it's under "unknown"
[14:45] <didrocks> ah
[14:45] <didrocks> hum
[14:45] <didrocks> a lot of other uncommited modif in this repo
[14:45] <pitti> didrocks: just the config (setting the password)
[14:45] <didrocks> where is my git add? ;)
[14:46] <pitti> didrocks:  you can't push on snakefruit anyway
[14:47] <pitti> didrocks: ah, TESTS=pep8 still installs ubuntu-desktop; I guess that's a consequence of moving to Depends:?
[14:47] <didrocks> pitti: yeah, that's wanted
[14:48] <didrocks> (until we have base images for this)
[14:48] <pitti> my hope is actually that without recommends and with eatmydata that thing is fast enough so that we stop caring as long as you aren't actually watching it :)
[14:49] <didrocks> pitti: I'm not in ~ubuntu-release, so I can't push from here (France, Lyon, @home) :)
[14:49] <didrocks> pitti: yeah, let's see :)
[14:49] <pitti> didrocks: send me a patch, bundle, or MP?
[14:50]  * didrocks will sms you the diff
[14:50]  * pitti does adb | git am -
[14:50] <didrocks> heh
[14:50] <pitti> didrocks: the fun thing is, my mobile just rang with a notification :)
[14:51] <pitti> (but it's just the reminder for the 16:00 UES update confcall)
[14:53] <pitti> didrocks: voilà<EMAIL_ADDRESS>[14:53] <didrocks> pitti: https://code.launchpad.net/~didrocks/britney/additional-parameters/+merge/282007
[14:53] <didrocks> pitti: heh, on @mobile ringing :)
[14:54] <pitti> didrocks: that took 15 minutes, not tooo bad
[14:54] <didrocks> yeah, it's not as bad as it could have been :)
[14:54] <didrocks> ok, I need to check the artefacts
[14:55] <pitti> didrocks: so without recommends that's maybe just 7
[14:55] <didrocks> looks perfect!
[14:55] <didrocks> I still have the per-tests artefacts and the global coverage collect
[14:55] <pitti> didrocks: code coverage is a bit poor :)
[14:55] <pitti> didrocks: I see lots of coverage files etc. in artifacts.tar.gz, so looks ok?
[14:56] <didrocks> pitti: rohhhhhhhh, why pep8 doesn't test more, right! ;)
[14:56] <didrocks> pitti: yeah :p
[14:56] <didrocks> basically you have subfolders
[14:56] <pitti> didrocks: so, go and hit it with the full thing!
[14:56] <didrocks> like artifacts/{pep8, small, …}
[14:56] <pitti> didrocks: perhaps once with recommends, once without, then we can compare
[14:56] <didrocks> and the global one at root
[14:57] <didrocks> pitti: hum, I think I need to look at why --env="TESTS=pep8 small" didn't work first
[14:58] <pitti> ah, right
[14:58] <pitti> didrocks: do you need that for the full test suite?
[14:58] <didrocks> yeah
[14:58] <didrocks> I only run pep8 and small without arguments
[14:58] <didrocks> (as large depends on 3rd party services, unfair to block packages if some $networks are starting to fail and they can)
[14:59] <didrocks> medium were a little bit flacky, but I made them way better, I want to see how they run first
[14:59] <didrocks> (on the cloud)
[15:05] <didrocks> pitti: seems the target focus isn't the right branch, I've done another MP at https://code.launchpad.net/~didrocks/britney/additional-parameters/+merge/282015
[15:09] <pitti> didrocks: pulled, thanks!
[15:09] <didrocks> sweet :)
[15:10] <Laney> cyphermox / xnox: Can you remind me how to start ubiquity from a bzr checkout please? :)
[15:10]  * Laney has asked this loads of times before but always forgets
[15:11] <pitti> time for adding that to README?
[15:11] <pitti> or better ./run-from-checkout
[15:11] <xnox> Laney, .... are you in the vm?
[15:12] <xnox> (don't start ubiquity on the installed machine...)
[15:12] <Laney> xnox: I hacked main
[15:12] <Laney> it's not going to do anything bad now
[15:13] <xnox> don't go past partitioning step, is all that i can suggest ;-)
[15:13] <didrocks> "oupsss, pressed enter"
[15:13] <didrocks> :)
[15:13] <Laney> I want to make the slideshow step use wk2, no need to go beyond that
[15:13] <Laney> but I don't know how to launch the darned thing properly!
[15:27] <Laney> bleh
[15:29] <pitti> Laney: last time I hacked ubiquity, I gave up and just changed the code inline on a live session
[15:29] <pitti> Laney: i. e. scp the changed files, then run it from live
[15:29]  * Laney is going to just install it probably
[15:29] <Laney> I hacked it to just launch to the slideshow anyway
[15:35] <Laney> eww, those deps
[15:35]  * Laney goes for a vm after all
[16:02] <didrocks> pitti: oh, I know why you got 3 instances running before
[16:02] <didrocks> so run-autopkgtest -s trusty -a amd64 --ppa=ubuntu-desktop/ubuntu-make-builddeps --ppa=ubuntu-desktop/ubuntu-make --test-git https://github.com/ubuntu/ubuntu-make.git --env "TESTS=pep8 small" ubuntu-make-master
[16:02] <didrocks> (using the ssh redirection line) ends ups in running "small" (see the swift container) and ubuntu-make-master :p
[16:02] <pitti> ah!
[16:02] <pitti> yay quoting
[16:03] <pitti> didrocks: so if you'd run that directly on snakefruit it would work
[16:03] <didrocks> yeah, I guess so
[16:04] <pitti> didrocks: or use double quoting
[16:04] <didrocks> it's a little bit counter intuitive, I wonder if we can make that better
[16:04] <pitti> didrocks: use commas for separating test names :)
[16:04] <didrocks> yeah, sounds like an option
[16:04] <pitti> (actually I'm quite serious -- on CLIs it's mostly just not worth the trouble dealing with spaces correctly)
[16:04] <didrocks> I liked having a nosetests3 compatible format
[16:05] <didrocks> does nosetests3 support commas? it's just a list of args
[16:05] <pitti> didrocks: ah, maybe not, I don't know nose
[16:07] <didrocks> I guess commas is the best option, quite annoyed to change the format compared to runtests for local run, but I guess it's okish
[16:07] <pitti> didrocks: or double-quote
[16:07] <pitti> didrocks: you wouldn't trigger them manually that often, so it's not such a biggie
[16:08] <didrocks> pitti: yeah, it's more an issue of remembering when trying some PR branch
[16:15] <Laney> still mostly light at 16:15
[16:15] <Laney> spring is coming
[16:15] <seb128> :-)
[16:18] <didrocks> "some" yeah
[16:19] <Laney> xnox: how do I get ubiquity to show me tracebacks?
[16:19] <Laney> seems the wrapper is doing something with stderr
[16:20] <xnox> it's in ubiquity logs in like /var/log/ubiquity/ no?
[16:20] <Laney> nein
[16:20] <xnox> and/or in the popout window
[16:20]  * pitti waves good night
[16:20] <xnox> =(
[16:20] <Laney> no window
[16:20] <Laney> that log directory doesn't even exist
[16:20] <Laney> maybe it's erroring too early?
[16:20] <Laney> I put a syntax error in gtk_ui.py on purpose to test
[16:21] <didrocks> good night pitti!
[16:21] <seb128> pitti, have a good w.e!
[16:23]  * Laney tries to port directly sans-tracebacks :-)
[16:27]  * didrocks waves good evening, have a nice week-end everyone! :)
[16:28] <seb128> didrocks, thanks, you too
[16:29] <willcooke> cya didrocks
[16:30] <Laney> bye didrocks!
[16:30] <didrocks> see you willcooke, Laney, seb128!
[16:30]  * Laney appeciates that didrocks stays around for a minute now ;-)
[16:31] <didrocks> Laney: thinking of you! :)
[16:31] <Laney> you BEAST!
[16:33] <willcooke> darn window focus
[16:34] <seb128> ctrl-w?
[16:34] <willcooke> ha, yeah
[16:34] <seb128> :-)
[16:34] <seb128> I do that often when I use dual screen
[16:34] <seb128> look at one screen and closing thing on the other
[16:37] <willcooke> exactly
[17:50] <Laney> weeeeeeeeeee
[17:50] <seb128> Laney, enjoy!
[17:50] <Laney> woah
[17:50] <Laney> no NO!
[17:50] <Laney> I was weeing at something working
[17:50] <seb128> ah ok :-)
[17:51] <Laney> Note that due to historical reasons, GtkNotebook refuses to switch to a page unless the child widget is visible. Therefore, it is recommended to show child widgets before adding them to a notebook.
[17:51] <Laney> that was a very helpful piece of documentation
[17:51] <Laney> thanks whoever wrote it
[18:05] <Laney> ok
[18:05] <Laney> now I am going
[18:05] <Laney> laters! happy weekend
[18:06] <seb128> bah
[18:07] <seb128> gnome-icon-theme upload rejected because the vcs was outdated
[18:07] <seb128> going to resolve that on monday
[18:07] <seb128> Laney, have a good w.e!
[18:07] <Laney> MY BAD
[18:07] <Laney> SORRY!!!!
[18:07] <seb128> & same to desktopers
[18:07] <willcooke> see ya
[18:07] <seb128> Laney, no worry, and I pushed my revision
[18:07] <seb128> let's sort that next week
[18:07] <seb128> no hurry
[18:08] <seb128> willcooke, have a good w.e!
[18:10] <willcooke> I'm off too - ta ta
[18:12]  * Laney pushed a fix up for seb128
[18:12] <Laney> didn't upload it though, too scary
[18:12] <Laney> byeee
[22:47] <attente> have a good w.e. everyone
[22:52] <flocculant> attente: have a good one too :)
[22:52] <flocculant> I thought I would say that - you're late, they've all gone already ;)
[22:53] <attente> flocculant: haha, thanks :)
[22:53] <flocculant> :)
[22:54] <flocculant> always someone waiting for Laney to throw sand at them it seems :D


[05:32] <cpaelzer> good morning
[05:44] <cpaelzer> rbasak: the revised edition of the squid tests will be added to squid4 by Amos
[05:45] <cpaelzer> rbasak:for squid3 we have to device on next merge if we want to use them as they are now or if you want to move in the same shrinked version that will be in squid4 then
[05:46] <cpaelzer> rbasak: we can talk later today about that
[08:45] <lordievader> Good morning
[10:43] <zioproto> hey there
[10:43] <zioproto> we upgraded trusty to xenial and mitaka to newton
[10:44] <zioproto> we are hitting a few 'ulimit' issues
[10:44] <zioproto> is there any limit in /proc for the routing of the packets in the namespaces on the network nodes
[10:44] <zioproto> ?
[11:48] <help-im-stuck> hello
[11:49] <help-im-stuck> i wrote lxc launch ubuntu:16.04 and it downloaded 2 things.. adapted-kangaroo and cunning-gelding.. what are these for? Can't find much on google about this..
[11:50] <TafThorne> I think...
[11:50] <TafThorne> Those are the randomy generated named the scripts generate for your two new containers.
[11:51] <TafThorne> If you chose to name your container it would use that name instead.  If you do not specify a name it makes one up.  That is based on the whole 30 minutes of lxc related stuff I have typed in on one afternoon.
[11:51] <help-im-stuck> :)
[11:52] <help-im-stuck> Thanks for the info
[11:52] <TafThorne> You are welcome.  I hope it is at least vaguely correct.
[11:52] <help-im-stuck> but who does it download 2 containers when i asked for one?
[11:52] <TafThorne> The US should start waking up soon.
[11:52] <help-im-stuck> why*
[11:52] <help-im-stuck> what timezone are you in?
[11:52] <TafThorne> UK so currently BST which is... GMT+1 or UTC+1
[11:54] <TafThorne> I am meant to be doing some testing using lxc for a bug that is probably fixed.  I downloaded a something, connected to the container, logged in and then something.
[11:54] <help-im-stuck> so it's only one hour difference from where i am
[12:00] <TafThorne> Dunno.  It is 13:0019
[12:00] <TafThorne> for me
[12:02] <help-im-stuck> it's 14:02 for me
[12:06] <help-im-stuck> do i really need multicast on ubuntu server?
[12:06] <help-im-stuck> ufw is blocking it anyway
[12:07] <hateball> depends if you are serving stuff that you announce with multicast I guess
[12:07] <hateball> like cups services or whatever
[12:10] <help-im-stuck> my modem/router sends multicast requests to my ubuntu.. even tho upnp is disabled on the router xD
[12:11] <hateball> did you reboot the router after doing so
[12:11] <hateball> some routers only re-read configs on reboot, like crappy ISP ones :p
[12:12] <help-im-stuck> yes, i rebooted it
[12:12] <hateball> and you havent any smb shares going?
[12:12] <help-im-stuck> the ufw log says src=modem ip dest = <IP_ADDRESS>
[12:14] <help-im-stuck> so it's my modem.. maybe i should give my isp a call
[12:16] <maswan> well, upnp is not the only multicast out there, is there?
[12:16] <maswan> I'm thinking of mdns etc
[12:17] <hateball> yes, is why I asked if there were any smb shares or something in the router
[12:17] <hateball> or if it shares a printer perhaps
[12:17] <hateball> or maybe even media sharing
[12:18] <help-im-stuck> no, it's a pretty simple config.. it just acts dhcp for my internal lan
[12:41] <help-im-stuck> what is session c1 ?
[13:04] <aaronr> cpaelzer: thanks for your help on that Nagios issue. added an SRU to the launchpad bug, if there's anything else I can do to help out with resolving that issue please let me know.
[13:05] <cpaelzer> aaronr: thank you for your support
[13:06] <cpaelzer> aaronr: the next thing to do is really create the updated packages
[13:06] <cpaelzer> aaronr: the USBSD even we now de regularly is for people to learn doing so, otherwise this is down to waiting until priority made it happen by someone who already knows how
[13:07] <cpaelzer> aaronr: that is the event I linked on the bug
[13:07] <cpaelzer> whenever I see issue which would perfectly qualify for that even I kind of "offer" it more explcitly
[13:07] <cpaelzer> after all we are a community, so I like teaching how things are done
[13:07] <aaronr> i'm totally up for learning about that. :) I've done some packaging for PPAs before so I have a little experience, but I've not worked on any official packages, so not sure what differences there would be
[13:07] <cpaelzer> not only for the sake of not doing them on my own :-)
[13:08] <help-im-stuck> lxc exec <container> bash .. and I don't have to enter a root password.. not even when typing it as a regular user.. why?
[13:08] <cpaelzer> aaronr: there are a few things which "shold be done" like on the versioning, on a proper changelog and so on
[13:08] <cpaelzer> aaronr: but in general all of that is out there documented, yet as ducumentation is - it is useless if not guided through a bit
[13:09] <ahasenack> help-im-stuck: because you are in the lxd group
[13:09] <help-im-stuck> i see :o
[13:09] <aaronr> yeah i remember that from reading docs before, although it's been a while. am i best off waiting until the next event and then tackling this during that?
[13:09] <aaronr> happy to do so if that's best
[13:10] <cpaelzer> aaronr: yeah if nobody else picked it until then that would be great
[13:10] <cpaelzer> aaronr: but if you happen to prefer other timing than every other week on wednesdays let me know
[13:10] <cpaelzer> aaronr: I do not insist on the timing, we jsut happen to try to keep these days free for it
[13:11] <cpaelzer> aaronr: if no one shows up there is always plenty to fill the days, but vice versa if one is active and willing we could do on another day
[13:11] <cpaelzer> aaronr: next event is on 10th May, and if you want to do on another day catch me here and give me a bit headroom to clean up other tasks
[13:11] <aaronr> ah okay, in that case when I get some free time am I okay to just pop in here and ask for a little help? if so, I should be able to tackle it this week, or i can just book some time in for may 10th
[13:13] <cpaelzer> aaronr: ok both work, you will find me here
[13:13] <cpaelzer> aaronr: and if I'm not around nacc and rbasak are the others to catch for this
[13:14] <aaronr> cpaelzer: okay great. i'll try and tackle it this week at some point then. I'll give one of you a shout once I get a bit of time to look at it
[13:14] <aaronr> thanks again for all your help on this
[13:15] <cpaelzer> nacc: I think I found a nice new importer case :-)
[13:15] <cpaelzer> nacc: well I'm talking too early let me check the detauls first and then I'll file something for you
[13:17] <rbasak> cpaelzer: well I want to know too :-)
[13:17] <cpaelzer> just found the reasons I think
[13:17] <cpaelzer> rbasak: nacc: https://packages.debian.org/search?suite=sid&searchon=names&keywords=exim4
[13:18] <cpaelzer> The last version never migrated for Debian on "hurd-i386" it seems
[13:18] <cpaelzer> that makes unstable/sid have 4.89-1 AND 4.89-2 for tools like rmadison and such
[13:19] <cpaelzer> nacc: rbasak: it seems usd merge picks the first version for the tagging of new/debian
[13:19] <cpaelzer> I'd think it should pick the last in that case
[13:19] <cpaelzer> although it might differ case by case dependign what the reason is
[13:20] <rbasak> The importer should be blind to build issues - it sees source only.
[13:20] <cpaelzer> rbasak: nacc: oh I see it is not only the tagging, there isn't even a lpusip/import/4.89-2
[13:20] <rbasak> And 4.89-2 is published in sid, so that's all it should care about.
[13:20] <rbasak> Right
[13:20] <rbasak> So either it hasn't imported 4.89-2 yet or there's some different issue with it.
[13:20] <rbasak> Perhaps the empty directory bug?
[13:20] <rbasak> Those should block imports now.
[13:20] <rbasak> (until we've fixed it)
[13:21] <rbasak> nacc will need to check the importer log to see why 4.89-2 isn't imported. Or we could try importing manually to see.
[13:21] <cpaelzer> rbasak: he imported it a few days ago for me manually
[13:22] <cpaelzer> rbasak: I'm checking what the dates of that upload are, but I think it was in his manual run
[13:23] <rbasak> usd.source_information.SourceExtractionException: Empty directory/ies found in source package, which are not representable in git. Please report a bug at https://bugs.launchpad.net/usd-importer.
[13:23] <rbasak> So that's the reason. The import would be buggy.
[13:23] <cpaelzer> -2 is form 20th April and his re-upload was on 27th, so it should be there
[13:23] <cpaelzer> oh I see
[13:24] <cpaelzer> rbasak: you said that is "The empty dir bug" it didn't introduce himself to me :-)
[13:24] <cpaelzer> that is bug 1687057 I assume?
[13:24] <rbasak> Yes. I just updated the bug.
[13:25] <cpaelzer> rbasak: lets talk about that later when we sync anyway
[13:25] <rbasak> ack
[13:25] <cpaelzer> rbasak: I can pick another package for now
[13:58] <rcj> C-Otto: Just a follow-up on cloud-images.u.c.  lost+found has been removed
[14:21] <jbicha> hi, does Ubuntu Server want to be the bug subscriber for LP: #1200296 ?
[14:23] <cpaelzer> nacc: for the first time used the "warp up all" usd merge finish, but I get missing debian/control.in
[14:23] <cpaelzer> nacc: is that a known issue or should I file something so you can look deeper?
[14:28] <rbasak> jbicha: I don't think ~ubuntu-server wants to be touching the spice stuff at all, but perhaps we have to because qemu :-/
[14:28] <cpaelzer> I still don't "want" to touch it
[14:28] <cpaelzer> :-)
[14:29] <rbasak> I think it'll be between cpaelzer and dpb1 to decide :)
[14:30] <cpaelzer> need to read on the history of those decisions first
[14:30] <cpaelzer> and dpb1 likely is a bit busy atm
[14:30] <cpaelzer> I'll keep the bug open to look at it
[14:31] <cpaelzer> there are also more MIRs on accelerated 3d on virt, but that was new and then full of CVEs at first
[14:31] <cpaelzer> so that didn't pass yet either
[14:31] <cpaelzer> even Debian dropped it again after a few weeks
[15:43] <ndee> hi there, when I do a df, I see following: /dev/md2        1.8T  1.7T     0 100% /
[15:44] <ndee> df -i gives me /dev/md2       121561088 27353493 94207595   23% /
[15:45] <ndee> how come the harddisk as 100GB free but I can't write any more data to it?
[15:47] <nacc> ndee: what message do you get when you try to write?
[15:47] <ndee> nacc: I deleted now some files and I can write again
[15:50] <ndee> nacc: but how can the display in "df" be off for about 100GB?
[15:50] <nacc> ndee: you haven't said any error messages or what you were trying to write
[15:50] <nacc> ndee: so i don't know
[15:53] <ndee> nacc: the message was: No space left on device
[15:54] <ahasenack> ndee: does that filesystem has reserved space for the root user? By default, unless you changed that during mkfs, it will
[16:01] <tomreyn> ndee: if it's an ext* file system: sudo dumpe2fs -h /dev/md0 | grep ^Reserved
[16:01] <tomreyn> md1 rather in your case
[16:01] <tomreyn> i mean md2
[16:04] <ndee> tomreyn: umpe2fs 1.42.9 (4-Feb-2014)
[16:04] <ndee> Reserved block count:     24311012
[16:04] <ndee> Reserved GDT blocks:      908
[16:04] <ndee> Reserved blocks uid:      0 (user root)
[16:04] <ndee> Reserved blocks gid:      0 (group root)
[16:04] <ahasenack> 24311012 * ${block_size}
[16:04] <ahasenack> block_size is further down, remove the grep and use |less
[16:05] <ndee> the block_size is 1kb
[16:05] <ndee> ah no, 4096
[16:05] <ndee> jup, that matches it around
[16:05] <ndee> thanks!
[16:06] <ahasenack> you can change that setting with tune2fs
[16:06] <ahasenack> -m (percentage) or -r (actual count)
[16:26] <teward> ahasenack: if you ahve any questions on the nginx triage guidelines up there, let me know - I know powersj, rbasak, and others had asked me how to handle certain triage cases so I put the special cases up :p
[16:27] <teward> (since some of them are "Not Going To Happen" and we didn't want to step on any workflows I have in place heh)
[16:27] <teward> (in case that wasn't clear during the meeting, I didn't want to steal the entire stage for too long :P)
[16:27] <nacc> teward: you are quite the diva :)
[16:28] <teward> nacc: i'm semi-attention-whorey if that's what you mean :P
[16:28] <nacc> teward: lol
[16:28] <teward> just glad I resolved the FTBFSes with the assist from Debian heh
[17:21] <dougquaid> I have an ubuntu server without a gui, but I want to install a minimal version of the xubuntu desktop on it. What packages do I need for that?
[17:28] <ahasenack> teward: oh, it's ok, I just wanted to know what the "template" for the mysql triage page would look like, that's all
[17:28] <teward> ahasenack: i think the 'template' is slightly different
[17:28] <teward> in that there's no real template.
[17:28] <teward> but if the MySQL page uses the nginx page i wrote as a start point, that's cool :)
[17:29] <ahasenack> I think that's the intention :)
[17:32] <powersj> https://wiki.ubuntu.com/ServerTeam/mysql is our start
[17:32] <teward> somehow my quick attempt with the NGINX page happened to make the template for mysql heh
[17:38] <mason> dougquaid: apt install xubuntu-core or xubuntu-desktop at a guess
[17:47] <__Yiota> ok, is anyone experiencing issues with services on 16.04?
[17:50] <teward> __Yiota: 'services'?
[17:50] <__Yiota> yes
[17:50] <__Yiota> pgpool2, nginx, haproxy
[17:50] <__Yiota> they fail to start sometimes
[17:50] <teward> being more specific next time might help.
[17:50] <nacc> __Yiota: and what 'issues'
[17:50] <nacc> __Yiota: your statement is so vague as to be contentless
[17:50] <teward> I haven't had issues with 'nginx', and 'fail to start' suggests you should be looking at error logs lol
[17:51] <__Yiota> that's the thing, the error logs don't show anything
[17:51] <__Yiota> pgpool2 logs, haproxy logs, all clean
[17:51] <__Yiota> sudo service haproxy status shows it has started without errors
[17:51] <__Yiota> I guess the issue is we built our cookbooks on 14.04
[17:52] <teward> __Yiota: don't rely on that
[17:52] <__Yiota> we upgraded without testing, pinning these issues down is hard
[17:52] <teward> `sudo systemctl -l status [SERVICE]`
[17:52] <__Yiota> is there a system.d log?
[17:52] <__Yiota> thank you teward
[17:52] <teward> get the actual useful data from there lol, stop relying on upstart stuff.
[17:52] <teward> or dedicated service error log files (for example, /var/log/nginx/error.log heh)
[17:52] <__Yiota> I see
[18:25] <__Yiota> hi
[18:25] <__Yiota> I created an ssh tunnel to my node's ip
[18:25] <__Yiota> I pointed chrome to the SOCKS proxy on localhost
[18:25] <__Yiota> everytime I create the SSH tunnel, no other computer except mine can access it
[18:26] <__Yiota> I've closed the SSH tunnel and I can still access the node via DNS via load balancer
[18:26] <__Yiota> and im also able to access it via the node's ip
[18:26] <__Yiota> any ideas?
[18:30] <RoyK> __Yiota: autossh?
[18:31] <__Yiota> ssh -D 8080 -C -N me@node_ip
[18:31] <RoyK> try autossh
[18:53] <help-im-stuck> so.. i'm trying to create a lxc vpn and i've done so.. it's working but i don't know how to check for dns-leaks and such from the commandline.. any ideas?
[18:55] <sarnold> help-im-stuck: there's a website listed in https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1685391 that may be helpful; I've never tried it but someone else recentlypointed it out..
[18:56] <help-im-stuck> so it's broken?
[18:56] <sarnold> no idea
[18:56] <help-im-stuck> i block my isp:s dns servers with ufw
[18:57] <sarnold> be sure to block tcp too
[18:57] <help-im-stuck> yes, both
[18:58] <help-im-stuck> but in tcpdump, when i boot my lxc and it connects.. i can see that it talks to isp dns:es..
[19:00] <help-im-stuck> but after that it's all ok
[19:00] <help-im-stuck> maybe it should be like that..
[19:12] <help-im-stuck> I would like to have a vpn+dnscrypt in one lxc.. that acts like a nat router and give other lxc:s ip:s..
[19:29] <help-im-stuck> how about the -new- lxd and lxc.. no more config files to edit and everything should be done by lxc command ?
[19:30] <help-im-stuck> lxc start .. etc
[19:31] <help-im-stuck> are there any additional info about this new config system?
[19:40] <ahasenack> help-im-stuck: https://linuxcontainers.org/lxd/introduction/ should be a starting point for everything lxd related
[19:44]  * mason bookmarks that.
[19:48] <help-im-stuck> been reading there all day :)
[20:02] <powersj> This is also reading through if you are new to lxd 2.0 https://stgraber.org/2016/03/11/lxd-2-0-blog-post-series-012/
[20:02] <powersj> worth reading*
[20:10] <help-im-stuck> powersj, thanks
[20:11] <ahasenack> help-im-stuck: lots of good blog posts there indeed
[20:14] <Skittishtrigger> I am using ubuntu 16.04-server and am having issues with a vsftpd(secure) connection. Would it be ok to ask questions pertaining to that here or is there a btter spot?
[20:14] <Skittishtrigger> ufw is NOT the issue btw.
[20:18] <Skittishtrigger> Anyways https://gist.github.com/skittishtrigger/889dd213e7ab6eba93b573ca06760f7b is my current setup. Initial tests before securing went fine but after adding the chroot list connections started timing out (connected but timeout after 20sec)
[20:20] <Skittishtrigger> nevermind. I apologize. I found a better channel for that. thank you thoguh.
[21:06] <Dynamiiic>  hi, ive got 2 ubuntu servers (1 14.04 and 1 on 16.04) when i SSH into them the 14.04 serv has tab-autocompletion whilst 16.06 doenst, any experience with it?
[21:09] <tarpman> Dynamiiic: apt install bash-completion
[21:10] <Dynamiiic> apt list | grep auto-complete
[21:10] <Dynamiiic> WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
[21:10] <Dynamiiic> auto-complete-el/xenial,now 1.3.1-2 all [installed]
[21:11] <Dynamiiic> yet it wouldnt auto-complete parameters like apt-get (install) like 14.04 would
[21:11] <Dynamiiic> it would only complete apt-get
[21:12] <tarpman> Dynamiiic: auto-complete-el is completion for emacs. not for your shell.
[21:12] <Dynamiiic>  apt-get install bash-completion
[21:12] <Dynamiiic> bash-completion is already the newest version (1:2.1-4.2ubuntu1.1).
[21:13] <tarpman> is your shell bash?
[21:14] <Dynamiiic> oh wow.
[21:14] <Dynamiiic> i simply connect thru ssh, the 14.04 server seems to start in bash whilst 16.06 doenst
[21:14] <Dynamiiic> excuse me for the troubles
[21:14] <tarpman> if you want to change your login shell to bash: chsh -s /bin/bash
[21:15] <Dynamiiic> dont recall doing that on the 14.04 one tho, was that default back then?
[21:15] <tarpman> it should be default on 16.04 as well. I can't say why your 16.04 server would be different
[21:16] <tarpman> maybe some difference in how your user was created/configured. idk
[21:16] <Dynamiiic> hmm, etc/passwd shows:
[21:16] <Dynamiiic> $uname:x:1000:1000:,,,:/home/$uname:/bin/bash
[21:16] <tarpman> ok. if you ssh in and do echo $SHELL - does that say /bin/bash?
[21:17] <sarnold> or ls -l /proc/$$/exe ?
[21:17] <tarpman> check your ~/.bashrc, the lines for enabling completion may be commented out
[21:17] <tarpman> I've been porting my own .bashrc for so long I have no idea what the default looks like any more :)
[21:18] <Dynamiiic> $uname@hostname:~$ echo $SHELL
[21:18] <Dynamiiic> $uname@hostname:~$ ls -l /proc/$$/exe
[21:18] <Dynamiiic> lrwxrwxrwx 1 $uname $uname 0 May  2 23:17 /proc/8581/exe -> /bin/bash
[21:18] <Dynamiiic> $uname@hostname:~$
[21:18] <Dynamiiic> oh, echo $SHELL returns /bin/bash
[21:18] <Dynamiiic> well, on the 14.04 install its commented out but still works
[21:19] <Dynamiiic> tried ucommenting on 16.06 but that didnt do the trick
[21:19] <Dynamiiic> un*
[21:19] <tarpman> takes effect after you either source ~/.bashrc or log out and in again
[21:19] <tarpman> not sure whether the default /etc/bash.bashrc has completion uncommented or not
[21:20] <Dynamiiic> default its uncommented i believe
[21:30] <Dynamiiic> guess i didnt remember to source ~/.bashrc after editting
[21:30] <Dynamiiic> fixed, thanks alot
[21:30] <Dynamiiic> strange it wasnt on by default tho
[21:31] <Dynamiiic> also, if running a small wordpress site on a low-memory server would you guys recommend nginx or apache?
[21:34] <sarnold> whichever you understand better
[21:34] <sarnold> I prefer nginx because it feels simpler in all respects
[21:34] <Dynamiiic> i can setup both but looking for performance
[21:34] <sarnold> then make it a high-memory server? :)
[21:35] <sarnold> I suspect wordpress caching / database performance may matter more than which front end you're running
[21:35] <Dynamiiic> haha, running it for a small company that belongs to a friend, he doenst want too much hosting costs/year so i suggested i´d setup a server for him
[21:35] <Dynamiiic> a 256MB serv should be sufficient for his traffic, but think nginx is better optimized
[21:36] <sarnold> that would be my expectation too but I can't promise that it's based on anything scientific :)
[21:36] <ppetraki> it's hard to go wrong with nginx
[21:57] <vagvaf> hello people. I think have completely broken my php installation and need help. this is the error that i'm getting: https://pastebin.com/Y0w10T1s
[21:59] <sarnold> vagvaf: eww. I think I'd aim for apt-get purge for all those php things and try to return to a clean slate quickly. Be sure to backup whatever -is- configured first if you've got anything configured..
[22:00] <vagvaf> sarnold, i don't. let me try it
[22:00] <patdk-lp> hmm, missing things
[22:01] <patdk-lp> just phpmoddisable or whatever all the stuff
[22:01] <patdk-lp> that should fix it up
[22:01] <patdk-lp> well, fix fpm so it runs
[22:01] <sarnold> oh? I figured it was unhappy at the apt level too
[22:01] <patdk-lp> probably what is hanging it all up
[22:01] <patdk-lp> it is, cause the install package for fpm isn't sucessful cause the restart of fpm fails
[22:02] <patdk-lp> so making it start clean, will fix it up and it will fix up the other stuff
[22:02] <patdk-lp> and likely have only one thing to fix afterwards
[22:02] <patdk-lp> the big question I have, is why have mod-php and fpm installed at the same time
[22:02] <patdk-lp> they are redundant
[22:02] <patdk-lp> or maybe, disable fpm from systemd so it doesn't attempt to start it
[22:03] <patdk-lp> but that doesn't always work out during package update time
[22:03] <vagvaf> so, i purged php.* and reinstalled it. i get no errors anymore but my localhost/info.php returns a blank page
[22:04] <patdk-lp> well, could do that too :)
[22:04] <patdk-lp> now what did you install?
[22:04] <patdk-lp> mod-php or php-fpm?
[22:04] <patdk-lp> you can only use one or the other, or even php-cgi
[22:04] <patdk-lp> you can have them all installed, but useless to attempt to use more than one
[22:05] <vagvaf> php php-common php7.0 php7.0-cli php7.0-common php7.0-fpm php7.0-json php7.0-opcache php7.0-readline
[22:05] <patdk-lp> ok, did you configure apache to use php-fpm?
[22:06] <vagvaf> patdk-lp no..i will look for it
[22:06] <patdk-lp> see if a php file is in /etc/apache2/mods-enabled too
[22:06] <patdk-lp> one of those might have pulled in mod-php
[22:06] <patdk-lp> not sure if php does or not
[22:07] <patdk-lp> if you wouldn't have specified all those, but let it pull in dependencies itself, yo uwouldn't get into this whole mess so badly :)
[22:07] <patdk-lp> but it being blank is odd
[22:07] <vagvaf> i just installed php it drew everything else by itself ;)
[22:07] <patdk-lp> unless php is working
[22:08] <patdk-lp> what do you mean just installed?
[22:08] <patdk-lp> apt-get install php7.0-fpm
[22:08] <patdk-lp> that wouldn't pull in cli
[22:08] <patdk-lp> you might need cli, but not websites
[22:08] <vagvaf> apt-get install php
[22:08] <patdk-lp> ya, that is too generic
[22:09] <patdk-lp> you didn't tell it what php yo uwanted so it made a guess
[22:09] <patdk-lp> cli/cgi/fpm/mod
[22:09] <vagvaf> i don't see a php file in /etc/apache2/mods-enabled
[22:10] <patdk-lp> ok
[22:10] <patdk-lp> restart apache
[22:10] <patdk-lp> then tell is what happens
[22:10] <patdk-lp> looks like, apt-get install php, picks fpm/mod/cgi
[22:10] <patdk-lp> likely fpm first
[22:10] <patdk-lp> to help your sanity, if you just want it simple
[22:11] <patdk-lp> apt-get remove php7.0-fpm; apt-get install libapache2-mod-php7.0
[22:11] <vagvaf> aaah thanks :D
[22:11] <patdk-lp> mod-php is much easier, but ends up using more memory normally
[22:11] <patdk-lp> and you have to be careful what apache threading model you use
[22:11] <patdk-lp> but it's *simple*
[22:11] <patdk-lp> if you just want to leave most htings at default settings
[22:12] <patdk-lp> fpm is great, but does require a lot of manual work, but is highly flexable :)
[22:13] <vagvaf> still blank page
[22:13] <patdk-lp> what does apache log say?
[22:14] <patdk-lp> in /var/log/apache2/, likely access/other/error
[22:14] <patdk-lp> or is this server public and I can test?
[22:15] <vagvaf> no it's not public
[22:15] <vagvaf> hold on
[22:16] <vagvaf> this is the message: https://pastebin.com/1AW8y41H
[22:16] <patdk-lp> nothing in the other files?
[22:16] <vagvaf> hold on
[22:18] <vagvaf> it worked!
[22:18] <patdk-lp> could have been browser caching issue
[22:20] <vagvaf> thanks a lot!!
[23:50] <teward> since when do Xenial LXD images come with SSH password auth disabled by default