[03:56] <valorie> some good books here:
[03:56] <valorie> one day sale 50% off 25 top titles, DRM Free PDF, EPUB, etc.. just in case someone's interested: http://shop.oreilly.com/category/deals/best-of-oreilly-dotd.do?code=DEAL&imm_mid=0a39d2&cmp=em-npa-books-videos-deal-day-best-of-dd-direct
[03:57] <valorie> [15:58] <ahiemstra> [14:15:01] pfft
[03:57] <valorie> sale is almost over though
[23:28] <bkerensa> valorie: viva la washington
[23:28] <bkerensa> :D
[23:29] <bkerensa> money approved and being sent to meh
[23:29] <bkerensa> :D
[23:29] <bkerensa> reserving car and hotel tonight
[23:31] <valorie> oh, have they finally got the code for the hotel?
[23:31] <valorie> last I checked it wasn't done
[23:31] <valorie> time to make sure my son wants to attend again
[23:35] <bkerensa> valorie: how big is bellingham?
[23:35] <bkerensa> :d
[23:35] <bkerensa> I get 540 miles free with zipcar
[23:35] <valorie> not big at all
[23:35] <bkerensa> but if I go over I have to pay 0.45 a mile
[23:36] <bkerensa> lol
[23:36] <bkerensa> its 530 miles for the trip round trip
[23:36] <bkerensa> but thats with no driving in town
[23:36] <bkerensa> :P
[23:36]  * bkerensa crosses fingers
[23:36] <valorie> you can check with google maps for the diff between the college and the hotel
[23:37] <valorie> usually the Sat. night party is at the hotel, so no driving
[23:37] <valorie> except for maybe college --> lunch or dinner
[23:38] <valorie> usually not much driving involved
[23:38] <valorie> except up and back, which is a bit of a haul
[23:38] <valorie> gorgeous drive, though
[23:52] <seattlegaucho> valorie: last time the party was at the museum downtown
[23:53] <seattlegaucho> bkerensa: it's a college town mostly
[23:53] <seattlegaucho> WWU
[23:53] <bkerensa> oh I love colleges
[23:53] <bkerensa> :D
[23:54] <seattlegaucho> there are a couple of points of interest, ie: breweries and the ice shop downtown (can't remember the name, but it's well known)
[23:54] <seattlegaucho> s/ice/ice cream/


[06:26] <bazhang> * [Robbie] (~Rob@93-44-60-19.ip95.fastwebnet.it): Rob
[06:27] <bazhang> anyone familiar with that IP?
[06:29] <rww> already checked, just came up with various instances of him
[06:29] <rww> one of which was a Comcast address, but I assume that was someone else
[06:29] <bazhang> ok thanks. I thought we had a factoid refuting what he was asking
[06:52] <bazhang> lordie
[06:53] <elky> any minute now
[06:54] <ikonia> ....I think not......
[06:54] <rww> elky: nah, he'll try to join #poobuntu-cops instead of here
[06:54] <elky> lol
[06:56] <bazhang> hahaha
[06:59] <bazhang> * [FamilyFriendlyHa] (~asshat@173-24-135-10.client.mchsi.com):
[07:00] <rww> yeah, they changed their nick from asshat at someone's request earlier
[07:00] <rww> asshat1, even
[07:01] <valorie> at least they were being honest, right?
[07:02] <rww> oh
[07:02] <rww> valorie
[07:02] <rww> <loco hat>is there a page somewhere with kubuntu promotional materials?
[07:02] <bazhang> haha
[07:03] <rww> like flyers and what not
[07:03] <valorie> um, I think so -- searching
[07:03] <Flannel> SU?
[07:03] <bazhang> get ikonia to ddos him with flyers
[07:04] <valorie> https://code.launchpad.net/~kubuntu-packagers/kubuntu-default-settings/kubuntu-promo
[07:07] <rww> Anything with newer branding and that doesn't mention 6.06 ;)?
[07:07] <valorie> oh my
[07:07] <Flannel> rww: have you checked SU?
[07:07] <rww> (also, the poster in that repo didn't compile for me)
[07:07] <rww> Flannel: no, because I only just managed to expand SU
[07:07] <Flannel> oh sorry
[07:08] <Flannel> Well, you should've asked :P
[07:08] <ikonia> whats SU ?
[07:08] <rww> ikonia: spreadubuntu
[07:08] <ikonia> oh
[07:08] <Flannel> (I don't know what's on there for Kubuntu, but it'd be a good place to check)
[07:08] <valorie> there is good KDE promo stuff
[07:08] <valorie> and some kubuntu stuff on Spreadubuntu
[07:08] <rww> that might be useful too, if you have a link
[07:09] <rww> looking on spreadubuntu now :)
[07:09] <valorie> I'll get the kde stuff
[07:09] <valorie> https://community.kde.org/Promo/Material
[07:11] <valorie> www.kde.org/stuff/clipart.php
[07:15] <rww> thanks
[07:15] <rww> might end up taking one of the SU flyers and updating it a bit
[07:15] <bazhang> jono has no nick protection? seriously?
[07:16] <rww> yes he does...
[07:16] <bazhang> * jono is now known as Guest96931
[07:16] <rww> which is a demonstration of how he does have nick protection...
[07:17] <bazhang> the /whois says jono bacon
[07:17] <rww> he has nick protection. he doesn't have a sane reliable authentication method configured.
[07:17] <bazhang> heh ok
[07:17] <Flannel> anyone could put "jono bacon" in their whois :P
[07:18] <bazhang> thats shocking to me
[07:18] <bazhang> like esr asking for help with something simple in #xubuntu
[07:18] <valorie> mmmm, bacon
[07:18] <Flannel> bazhang: Don't read RFC 3514
[07:18] <bazhang> Bake&
[07:18] <valorie> lol
[07:18] <bazhang> Flannel, ok
[07:19] <rww> bazhang: if i recall correctly, sabdfl has forgotten his NickServ password at least once
[07:19] <rww> Canonical employees are humans too :3
[07:19] <bazhang> hilarious!
[07:19] <rww> except for popey, he's a robot
[07:19] <bazhang> well ofc
[07:20] <valorie> I have it set up in konversation and again in the BNC
[07:20] <elky> he's an elvis droid
[07:20] <popey> \o/
[07:20] <elky> fuelled by marmite
[07:21] <valorie> !
[07:21] <valorie> what a terrible thing to say about a person!
[07:22] <Flannel> the marmite bit?
[07:22] <popey> It's all true
[07:22] <valorie> foul stuff
[07:23] <popey> lies
[07:24] <valorie> well, I haven't done a comparative test vegemite/marmite
[07:24] <valorie> yet
[07:24] <elky> oh no, you said the v word
[07:25] <valorie> but I've tasted black sausage, and haggis
[07:25] <valorie> and lived
[07:26] <bazhang> try snake's blood soup
[07:26] <valorie> oh, my god
[07:26] <popey> mmmm black pudding
[07:26] <popey> well, technically.. "food" mmmmm
[07:26] <valorie> elky: this is all your fault!
[07:26] <bazhang> or for lighter fare, congealed pigs blood on a stick
[07:27] <rww> if we wait long enough one of the northern europeans will mention lutefisk
[07:27] <valorie> that I've not tasted
[07:27] <bazhang> looks like a popsicle, tastes like blood!
[07:27] <valorie> pickled herring, yes
[07:28] <valorie> no Surströmming either
[07:32] <jussi> nor I, and don't intend to
[07:32] <valorie> which one, jussi?
[07:33] <jussi> potentially though, we should continue this conversation in some -offtopic channel
[07:33] <valorie> pickled herring was good
[07:33] <jussi> valorie: lutefisk
[07:33] <valorie> ah
[07:33] <valorie> sounds vile
[09:05] <ikonia> muted
[09:06] <k1l_> made trouble with his own 4 clients
[09:07] <ikonia> of course
[10:42] <ikonia> hello john3213
[13:47] <Pricey> @btlogin
[15:47] <popey> Pricey: Why do you use backward question marks⸮
[15:49] <Pricey> popey: Because I can't afford a license to the alternative.
[15:50] <popey> 12 Points. You are through to the next round.
 i got cancer from using nouvea drivers
[19:04] <IdleOne> wtf why u being such a d about the effin words
[19:05] <IdleOne> seems pretty clear that these acronyms, abbreviations and obfuscations should not be allowed in any ubuntu channels
[19:07] <IdleOne> enforcing it is left up to the ops of the individual channels. Common sense is what dictates to the ops how to enforce the language guidelines.
[19:07] <IdleOne> I really really hope that we never have an "official" list
[19:07] <h00k> I'd edit IdleOne to be on it :(
[19:07] <h00k> IdleOne
[19:07] <h00k> NO SWEARING h00k
[19:08] <IdleOne> :)
[19:08] <IdleOne> I luv u2
[19:08] <h00k> ;)
[19:12] <tsimpson> we've had the discussion over having a list of disallowed words, it's just not realistic to maintain such a document
[19:14] <IdleOne> Not only is it not realistic, I think it would be silly of us to even think of trying
[19:14] <phunyguy> ^
[19:15] <phunyguy> also, hi
[19:15] <IdleOne> There is no such list precisely because we want ops to use common sense and not follow the letter of the law.
[19:16] <IdleOne> s/not follow/not always follow/
[19:23] <Pricey> IdleOne: You seriously don't think words like "dictator" should be used anywhere, yet you just used the word "dictates".... I'm not sure that's consistent.
[19:23] <IdleOne> Pricey: my use of the "d" word was not to replace dictator
[19:23] <IdleOne> This is why we use common sense, intent is 99% of text
[19:23] <Pricey> IdleOne: I honestly can't tell if you're being serious or not.
[19:24] <Pricey> IdleOne: sabdfl is an acronym where the d stands for dictator.
[19:24] <Pricey> Is that allowed?
[19:24] <IdleOne> Pricey: My intent was to obfuscate "dick"
[19:24] <IdleOne> see how that d word is no longer a nice word
[19:25] <Pricey> Dick's a good friend.
[19:25] <Pricey> His parents call him Richard.
[19:25] <IdleOne> I have no issue with the word dictator itself, but I do have issue if it is used to insult someone.
[19:25] <IdleOne> clearly its use in sabdfl is meant as tongue and cheek
[19:26] <Pricey> Oh so it's alright when it's a joke, totally wrong otherwise.
[19:26] <IdleOne> yes, intent.
[19:26] <IdleOne> if you mean to call me a dictator because I enforce the guidelines of the community we are a part of, then yes it is not ok.
[19:27] <Pricey> Even if it is being used in a purely descriptive manner?
[19:27] <IdleOne> this is where common sense comes into play
[19:28] <Pricey> 19:26:55 <+IdleOne> if you mean to call me a dictator because I enforce the guidelines of the community we are a part of, then yes it is not ok.
[19:28] <IdleOne> this is why we should not have a list of banned words
[19:28] <IdleOne> Pricey: again it all depends on the intent
[19:28] <Pricey> IdleOne: So we can't say things like 19:26:55 <+IdleOne> if you mean to call me a dictator because I enforce the guidelines of the community we are a part of, then yes it is not ok.
[19:29] <IdleOne> Now I don't know if you're joking or not
[19:30] <Pricey> A few moments ago you suggested that it is not ok to call someone a dictator for enforcing the guidelines.
[19:30] <Pricey> Then you say that it is ok... depending on the intent.
[19:30] <Pricey> I'm asking you retract the first bit.
[19:31] <IdleOne> I won't
[19:31] <IdleOne> and I also won't continue this discussion
[19:31] <Pricey> Don't you feel like they are contradictory?
[19:32] <IdleOne> I feel you are being contradictory just for the sake of it now.
[19:32] <IdleOne> back to my game.
[19:32] <Pricey> I think there's a big issue here where bunches of guidelines, policies, edge cases etc. are enforced... and THEN common sense is used. I feel we're doing it the wrong way around.
[19:36] <Pricey> IdleOne: If you feel I've missquoted you over the last 15 minutes then please give me a smack.
[19:37] <IdleOne> You haven't misquoted me, but you are intentionally not reading between the lines and trying to understand what my intent is. This wouldn't bother me so much if you were not a native English speaker.
[19:38] <IdleOne> But clearly your mastery of the English language is sufficient enough to know what I mean.
[19:38] <phunyguy> dictator can be used to compare someone to the likes of Hitler, etc.  That is where the "mean" comes into play.
[19:40] <Pricey> Yes!
[19:41] <Pricey> So saying things like "if you mean to call me a dictator because I enforce the guidelines of the community we are a part of, then yes it is not ok" isn't going to get us anywhere. There's nothing wrong with calling you a dictator.
[19:41] <phunyguy> Pricey, also with sabdfl, the b stands for benevolent.
[19:41] <Pricey> phunyguy: Well aware.
[19:42] <phunyguy> "well meaning and kindly."
[19:42] <phunyguy> well we can't pick and choose sections of an acronym for the sake of argument...
[19:43] <CarlFK> I am not sure there is anything worth arguing about ;)
[19:44] <phunyguy> Also Pricey I do agree with what you said about the guidelines, policies, etc, being enforced, then common sense being used.
[19:44] <Pricey> phunyguy: How do you mean sorry?
[19:44] <CarlFK> people will say whatever they want.  if someone else has a problem with it, there is a process.  the process seems to work really well.
[19:44] <phunyguy> I umm...
[19:44] <phunyguy> what?
[19:45] <Pricey> phunyguy: I'd like to confirm what you're agreeing with by seeing it in your own words.
[19:46] <phunyguy> I would rather not jump into all of that right now, but basically blindly following and enforcing guidelines, when there wasn't any malicious intent,
[19:48] <phunyguy> there is obviously way more, but I would prefer not to discuss that at the moment.
[19:50] <Pricey> phunyguy: Cool, sounds good to me. Why would you rather not discuss things?
[19:51] <phunyguy> if I told you that, it would defeat the purpose.
[19:52] <phunyguy> :)
[19:53]  * phunyguy wanders off to finish the work day.
[19:56] <Pricey> Doesn't sound constructive :-/


[09:00] <jurgenKatz> excuse me, could you say if the latest version of xubuntu can be installed on my computer?
[17:42] <xubuntu14w> I need help please Whenever I shutdown or reboot my pc Xubuntu 18.04 64 bit the process wouldn't complete and I get stuck in a black, also suspending the screen it can't wake up again.
[17:43] <xubuntu14w> ??


[15:23] <douglasawh-work> spikeb I've learned not to trust what people tell you.  working with users will do that. :)
[16:49] <douglasawh-work> h00k: I will try to be there tonight but I'm guessing I won't be.  We shall see.
[20:12] <uberushaximus> Lolwut, thursday is on the 18th
[23:53] <nickmoeck> wait I'm confused, is the meeting tonight or tomorrow
[23:54] <spikeb> tomorrow
[23:54] <spikeb> or tonight
[23:54] <spikeb> since its both thursday and the 17th
[23:54] <spikeb> heh
[23:55] <spikeb> email says tonight.


[05:55] <mup> Bug #1482502 opened: API open error: EOF during bootstrap <ci> <intermittent-failure> <maas-provider> <test-failure> <juju-core:Triaged> <juju-core windows-public-clouds:Triaged> <https://launchpad.net/bugs/1482502>
[06:25] <mup> Bug #1430205 changed: lxc template needs refreshing every 24 hours <lxc> <sts> <juju-core:Fix Released> <https://launchpad.net/bugs/1430205>
[06:49] <mup> Bug #1482513 opened: checklist failed with "at least three machines that have more than one disk" <juju-core:New> <https://launchpad.net/bugs/1482513>
[07:03] <voidspace> dooferlad: are you around?
[07:54] <dooferlad> voidspace: here now
[07:54] <dooferlad> voidspace: had rubbish night, so later than wanted start
[08:42] <voidspace> dooferlad: thanks
[08:42] <voidspace> dooferlad: sorry about your night
[08:42] <voidspace> dooferlad: and thanks for the review
[08:42] <voidspace> fwereade_: you have internet back yet, or you just found somewhere with wifi to work?
[08:42] <dooferlad> voidspace: no problem - wan't a big hunk of code!
[08:42] <voidspace> dooferlad: hehe, not exactly...
[08:43] <voidspace> dooferlad: did your state subnets branch land?
[08:43] <voidspace> dooferlad: if so you could move the card from Landing to Merged
[08:44] <dooferlad> voidspace: done. Thanks for the reminder.
[09:23] <voidspace> dimitern: I may need help with adding reference counting to subnets
[09:23] <voidspace> dimitern: I'll look at how it's done in other places first
[09:23] <voidspace> dimitern: maybe you could suggest somewhere else to look, otherwise I'll go spelunking through code
[09:25] <voidspace> dimitern: dooferlad: FYI my api branch landed
[09:26] <dimitern> voidspace, certainly
[09:27] <dimitern> voidspace, a nice, isolated example would be service settings ref counts
[09:27] <voidspace> dimitern: thanks
[09:28] <dimitern> voidspace, look at and around settingsRefsDoc
[09:28] <voidspace> dimitern: so it requires a separate collection for the refs
[09:28] <TheMue> dimitern: can you also provide edit access to the spreadsheet?
[09:29] <dimitern> voidspace, essentially you need explicit txn-revno to assert the collection hasn't changed
[09:29] <dimitern> voidspace, it doesn't require a separate collection, but fwereade I know prefers this approach
[09:29] <voidspace> dimitern: yeah, it's more the general shape of the infrastructure (that we use a separate doc for example) and where the refs are updated
[09:30] <dimitern> TheMue, which one ? for the sprint?
[09:30] <voidspace> dimitern: if fwreade prefers it that sounds like a good reason to do it :-)
[09:30] <TheMue> dimitern: exactly, otherwise I do it the standard way via alexisb
[09:30] <dimitern> voidspace, yeah, and to make life easier add helpers inc and dec ops and assert unchanged ops
[09:31] <voidspace> ok
[09:31] <dimitern> TheMue, let me see if I can do it
[09:31] <TheMue> dimitern: thx
[09:32] <dimitern> TheMue, try now
[09:33] <TheMue> dimitern: it works, great, thx again
[09:34] <dimitern> TheMue, np
[09:34] <dimitern> voidspace, dooferlad, both of you should have edit access as well
[09:35] <voidspace> dimitern: settingsIncRefOp and settingsDecRefOps (inconsistent naming!) both seem straightforward
[09:36] <voidspace> although there decrementing ref count to zero deletes the settings
[09:36] <voidspace> we don't want that behaviour
[09:49] <dimitern> voidspace, the naming is inconsistent because one is returning txn.Op and the other []txn.Op, but fair point
[09:50] <rogpeppe> anyone know if juju CI is currently blocked on critical bugs?
[09:51] <rogpeppe> i remember there was a website you could check, but i can't remember the name
[09:51] <rogpeppe> dimitern: ^
[09:51] <dimitern> rogpeppe, http://juju.fail
[09:52] <dimitern> rogpeppe, and it seems it's blocked
[09:52] <rogpeppe> dimitern: ok, i won't bother trying to propose my one line change to provider/dummy :)
[09:52] <rogpeppe> dimitern: thanks
[09:52] <rogpeppe> dimitern: i'll bookmark that
[09:52] <dimitern> rogpeppe, it's great :)
[09:53] <rogpeppe> dimitern: it should have a favicon :)
[09:59] <dimitern> rogpeppe, marcoceppi accepts contributions for it - I've done it once :)
[10:00] <rogpeppe> dimitern: then i'd have to make one :)
[10:02] <perrito666> I fix committed that bugfix why is it still blocked?
[10:03] <perrito666> There is no ci failure to support it and the relevant test is passing I say just change the severity
[10:05] <perrito666> Dimitern rogpeppe ^
[10:05] <rogpeppe> perrito666: i've no idea
[10:05] <dimitern> perrito666, no idea - ping mgz, sinzui ?
[10:06]  * perrito666 goes back to breakfast, irc on the phone is very annoying
[10:06] <perrito666> Mgz?
[10:32] <dimitern> TheMue, I'm looking at your branch
[10:32] <TheMue> dimitern: the WIP one or the not yet PR branch with the cleaner approach?
[10:32] <dimitern> TheMue, about the tests we're talking about
[10:33] <dimitern> TheMue, the one I can see (ending with "-simplified-approach" or something)
[10:34] <TheMue> dimitern: ah, fine, just adding tests here
[10:34] <dimitern> TheMue, let's finish all the tests with mocking, but at the end add a separate suite embedding JujuConnSuite (with comment that it's an integration test) that tests the full stack end-to-end
[10:34] <TheMue> dimitern: yep, will do, sounds logical to me
[10:34] <tasdomas> dimitern, ping?
[10:35] <dimitern> TheMue, i.e. add some IPs, make some of them dead (not all), call Cleanup...() and ensure they are released and removed
[10:35] <TheMue> dimitern: so far integration has been on worker level only. a bit late.
[10:35] <dimitern> tasdomas, pong
[10:35] <tasdomas> dimitern, a quick testing question
[10:35] <dimitern> tasdomas, sure
[10:35] <TheMue> dimitern: yeah
[10:36] <tasdomas> dimitern, in https://github.com/juju/juju/pull/2927/files#diff-34326fed18c50f27a1b95570dc428e0aR573 I'm adding a call to state from runner.Context
[10:36] <tasdomas> dimitern, what would be the best way to path that call to state, making it return an error?
[10:37] <tasdomas> uniter.State is not an interface, so I can't just mock it out
[10:38] <dimitern> tasdomas, let me have a look
[12:20] <voidspace> ericsnow: what's a "WMP feature test"?
[12:20] <mgz> perrito666: I marked bug as released to unblock branches - as I understand it we don't have coverage at present without jes testing, also master failed for other reasons when running the rev.
[12:22] <voidspace> ericsnow: WPM even
[12:24] <perrito666> mgz: oh, why did it fail?
[12:26] <mup> Bug #1479289 changed: statushistory uses sequence, fails in multi-env state servers <blocker> <jes> <status> <juju-core:Fix Released by hduran-8> <juju-core 1.24:Fix Released by hduran-8> <https://launchpad.net/bugs/1479289>
[12:26] <mgz> perrito666: juju not coping with errors from ec2 when deploying a bunch of stuff with quickstart, and joyent networking not being sorted yet
[12:26] <mgz> so, known robustness issues
[12:27] <perrito666> meh
[12:47] <TheMue> dimitern: ping
[12:55] <dimitern> TheMue, pong
[12:56] <mup> Bug #1482634 opened: leadership manager lifetime tied to state <tech-debt> <juju-core:Triaged by fwereade> <https://launchpad.net/bugs/1482634>
[12:57] <TheMue> dimitern: do you have a good example for working with a mock in one suite and the dummy in another suite in the same package?
[12:59] <mup> Bug #1482634 changed: leadership manager lifetime tied to state <tech-debt> <juju-core:Triaged by fwereade> <https://launchpad.net/bugs/1482634>
[12:59] <TheMue> dimitern: the test itself is done, I only needed the coretesting.MgoTestPackage(t)
[13:00] <TheMue> dimitern: and then, because they are two suites, one panics
[13:01] <TheMue> dimitern: one simple solution could be to not mock and use dummy for all tests of the API, but hmm, we tried to have less mongo starts
[13:05] <TheMue> dimitern: running the one with our Mgo... and the other one with gc.TestingT(t) would be nice. *sigh*
[13:06] <dimitern> TheMue, you only need to call MgoTestPackage once, regardless of how many suites you have
[13:07] <dimitern> TheMue, I can't think of a good example off hand for a package where there are both mocked unit tests and dummy provider based integration tests
[13:07] <TheMue> dimitern: yes, but doing so in TestPackage leads to a "Panic: cannot share a state between two dummy environs; old "only"; new "dummyenv""
[13:08] <dimitern> TheMue, can I have a look at the code that causes the panic?
[13:09] <TheMue> dimitern: sure, I'll quickly commit and push the branch
[13:11] <TheMue> dimitern: here it is https://github.com/TheMue/juju/blob/addresser-simplified-approach/apiserver/addresser/addresser_test.go
[13:11] <mup> Bug #1482634 opened: leadership manager lifetime tied to state <tech-debt> <juju-core:Triaged by fwereade> <https://launchpad.net/bugs/1482634>
[13:12] <TheMue> dimitern: and package_test.go contains the former code commented plus the call of MgoTestPackage
[13:12] <marcoceppi> dimitern glad you still use it!
[13:12] <TheMue> dimitern: the DummyAddresserSuite is now the new 2nd one using the dummy provider while the AddresserSuite uses the mock
[13:14] <TheMue> dimitern: the ttest at the bottom still misses the final check, that the address has been removed. wanted to test so far and then had the trouble with Mgo...
[13:14] <dimitern> marcoceppi, absolutely - that's my go-to source to check for blockers :)
[13:15] <TheMue> marcoceppi: dimitern: juju.fail? yeah, a very good and helpful tool
[13:17] <perrito666> I love it, just learned a couple of days ago about it
[13:17] <dimitern> TheMue, so you're saying calling MgoTestPackage in a package which have some suites using JujuConnSuite and some not panics?
[13:17] <perrito666> fwereade: hehey, internet is back?
[13:18] <TheMue> dimitern: yep
[13:18] <dimitern> TheMue, if that's the case too bad :( we can move that integration test to the worker then
[13:18] <TheMue> dimitern: *sniff*
[13:19] <TheMue> dimitern: liked the idea of having pure functional tests as well as integration in a so compact way
[13:20] <TheMue> hmmm, "in such a compact way" sounds better and more correct
[13:20] <fwereade> perrito666, yeah
[13:21] <perrito666> fwereade: what was the culprit?
[13:21] <fwereade> perrito666, we're pretty sure we tracked it down to an a/c unit that hadn't actually been unplugged from everything
[13:21] <fwereade> perrito666, so we've got someone coming over to take a look at that
[13:21] <perrito666> fwereade: :) dont forget to ask for the neutral line check
[13:22] <fwereade> perrito666, on the a/c? or everywhere?
[13:22] <TheMue> dimitern: that's btw one reason why I like the standard go tests where I create the environment in helper functions as a first statement in TestFoo(t *testing.T)
[13:22] <perrito666> fwereade: everywhere, it is not normal to have the protection break on all 3 circuits if only 1 is faulty
[13:23] <natefinch> TheMue: +1 for standard go tests w/ a help if setup is needed.
[13:23] <fwereade> perrito666, yep. will do
[13:23] <TheMue> dimitern: so my tideland test typically load the assertion type/helper as a first statement, then create their environment(s) and then do the tests
[13:24] <TheMue> natefinch: thx
[13:24]  * perrito666 +1s natefinch
[13:25] <natefinch> TheMue: I think it's just a lot more clear w/o magical functions getting called that you don't even see.   Plus, I think mgo's test timing doesn't include setup or teardown, which means you miss a lot of important information about how long a test really takes
[13:26] <TheMue> natefinch: yep
[13:27] <natefinch> TheMue: er s/mgo/gocheck/
[13:27] <TheMue> natefinch: here at https://github.com/tideland/golib/blob/master/cells/cells_test.go#L168 is an example how I'm doing it, always trying to be as simple as possible
[13:28] <fwereade> I know I'm OCR, but cann I hit someone up for a review of http://reviews.vapour.ws/r/2315/ please? somewhat urgent
[13:28] <TheMue> natefinch: and if a larger setup is needed it's simply a privat function in the same test (extra or same file)
[13:29] <natefinch> TheMue: yep.
[13:29] <TheMue> natefinch: the task of gocheck for more simple test is done by https://godoc.org/github.com/tideland/golib/audit#Assertion
[13:29] <natefinch> TheMue: the nice thing about using the standard test's framework is better integration with third party tools, like goconvey's web UI.
[13:30] <TheMue> natefinch: yes, another big advantage
[13:30] <perrito666> fwereade: ship it
[13:31] <perrito666> I am satisfied by the amount of explanations around the dirty hack :)
[13:31] <fwereade> perrito666, tyvm
[13:34] <fwereade> ericsnow, ty for your review; and by the way, RB seems not to have picked up https://github.com/juju/juju/pull/2932
[13:35] <perrito666> rb is missing a lot of things lately
[13:59] <natefinch> oh for fsck's sake... the tests are wiping environment variables... now I understand why the tests keep telling me they can't find $HOME
[13:59] <perrito666> lol
[14:01] <katco> natefinch: standup
[14:03] <voidspace> perrito666: a few questions on your version checker PR
[14:03] <voidspace> perrito666: other than my questions looks good
[14:04] <perrito666> voidspace: hey thanks :)
[14:12] <ericsnow> fwereade: re: that review request, it barfed because of unicode (in Python 2)
[14:14] <mup> Bug #1482513 changed: checklist failed with "at least three machines that have more than one disk" <Landscape Server:Incomplete> <https://launchpad.net/bugs/1482513>
[14:23] <fwereade> ericsnow, eww, what did I do to it?
[14:23] <ericsnow> fwereade: not your fault :)
[14:24] <perrito666> heh, thank I didn't write my name properly on github nor in my git account
[14:24] <perrito666> that usually blows djangos with unicode errors
[14:26] <fwereade> ericsnow, what should I do to goose it into action when that happens?
[14:26] <ericsnow> fwereade: I thought I had fixed it but I guess not
[14:26] <ericsnow> fwereade: create a new pull request? (discard the old one)
[14:26] <perrito666> ericsnow: you never fix all unicode problems
[14:26] <fwereade> ericsnow, ok, cheers
[14:27] <ericsnow> perrito666: :)
[14:28]  * perrito666 used to be the "reminder there is a 'rest of the world'" to former co workers doing python web apps
[14:28] <perrito666> I wont say what was their nationality :p
[14:30] <dooferlad> voidspace / dimitern: I am being told by Juju that it is out of IP addresses when trying to perform a static allocation. Do you know how to reset the pool? This is with MAAS.
[14:30] <fwereade> ericsnow, does PR2939 have the same problem?
[14:30] <dooferlad> I have already reset the leases files it is using
[14:31] <voidspace> dooferlad: "reset the pool"? there is no way...
[14:31] <voidspace> dooferlad: juju attempts to allocate addresses from the static range
[14:32] <voidspace> dooferlad: if it fails (MAAS returns an error) it marks the address as unavailable
[14:32] <perrito666> fwereade: how do you even cause a unicode error? do you have special chars in your kb?
[14:32] <voidspace> dooferlad: if it succeeds it uses the address
[14:33] <fwereade> perrito666, I didn't think I was doing anything special -- no :hankey:s in the comments or anything
[14:33] <dooferlad> voidspace: so what I do when MAAS thinks it has run out?
[14:35] <voidspace> dooferlad: well if *MAAS* thinks you've run out it usually means you have
[14:35] <voidspace> dooferlad: increase the static range
[14:35] <voidspace> *statically allocated range*
[14:36] <voidspace> that should work
[14:36] <dooferlad> voidspace: I have two physical machines, one is on, there are three containers on it. I have 100 addresses in the static range.
[14:36] <voidspace> dooferlad: something has gone wrong then :-)
[14:36] <dooferlad> voidspace: yea.
[14:37] <voidspace> some error was causing address allocation to fail and addresses be marked as unavailable
[14:37] <voidspace> you could poke mongo directly and clear all addresses marked as unavailable
[14:37] <voidspace> we should have an issue (we've certainly talked about) retrying unavailable addresses
[14:38] <voidspace> *for retrying
[14:41] <perrito666> voidspace: why on earth are we not using more periodicworker
[14:42]  * perrito666 facepalms
[14:43] <voidspace> perrito666: I don't know... :-)
[14:43]  * perrito666 changes it a bit to use a custom clock
[14:47] <dooferlad> voidspace: https://gist.github.com/dooferlad/082996faeb2168a76ab4 does it
[14:47] <dooferlad> voidspace: provided your maas is called "maas"
[14:53] <voidspace> dooferlad: my maas usually is called maas
[14:53] <voidspace> dooferlad: ah, so they were allocated with maas
[14:53] <voidspace> I wonder how they got allocated
[14:53] <voidspace> we must have allocated them, then something *else* went wrong so we marked the address as unavailable and tried another one
[14:53] <voidspace> still worrying
[14:54] <voidspace> dooferlad: hmmm... maybe not
[14:54] <voidspace> I'm slightly confused but never mind, if it worked then great
[14:54] <dooferlad> voidspace: juju destroy-environment -y --force maas
[14:54] <dooferlad> voidspace: I bet repeatedly using that doesn't help
[14:54] <voidspace> dooferlad: hah, yes
[14:54] <voidspace> dooferlad: they just remained allocated from previous runs
[14:55] <voidspace> that makes sense
[14:55] <voidspace> if you use maas 1.8 and trunk it should no longer be an issue
[14:55] <voidspace> they'll now be freed correctly
[14:55] <dooferlad> I am
[14:55] <voidspace> using devices
[14:55] <voidspace> in theory...
[14:55] <dooferlad> though I ran out when using net-cli
[14:55] <voidspace> the devices are correctly cleared and we're assuming maas also releases their IP addresses
[14:55] <voidspace> that may not have the new devices stuff in it
[14:56] <voidspace> you can tell - when you create a container check if a corresponding device is created (visible in the MAAS UI)
[14:57] <dooferlad> Oh, that's new (to me):  ERROR juju.cmd supercommand.go:429 upgrade in progress - Juju functionality is limited
[15:05] <dooferlad> voidspace: ohh, now there are devices! Shiny!
[15:35] <voidspace> right EOW
[15:35] <voidspace> happy weekend everyone
[15:37] <dimitern> dooferlad, hey
[15:38] <dooferlad> Hi
[15:38] <dimitern> dooferlad, did you manage to fix your ip addresses issues?
[15:38] <dimitern> dooferlad, I have a tool for this btw
[15:38] <dooferlad> Yep. Pasted above
[15:39] <dooferlad> Well, mine is pasted above
[15:39] <dimitern> dooferlad, ah :) good - but here's mine as well - expectedIP
[15:39] <dimitern> ?!
[15:39] <dimitern> https://github.com/dimitern/go-tools
[15:43] <dooferlad> dimitern: cool, will try to remember that is there.
[15:43] <dooferlad> I think we should bubble up a warning to the CLI if we can't allocate a static address and we wanted to. It is the sort of thing that hunting through logs for just sucks.
[15:44] <dooferlad> but for the moment I am out of energy, so calling it a day.
[15:45] <dimitern> dooferlad, We will do that soon
[15:45] <dimitern> dooferlad, have a nice weekend :)
[16:00] <perrito666> bbl
[16:05] <bogdanteleaga> do we support instance type constraints on azure?
[16:14] <dimitern> bogdanteleaga, looking at provider/azure - selectInstanceTypeAndImage it seems we do
[16:15] <bogdanteleaga> dimitern: yup, I managed to get it working in the end
[16:16] <bogdanteleaga> sadly, I don't think it matters since I wanted an SSD for the main drive and D# instances provide it only for a secondary drive
[16:24] <rogpeppe> anyone know of an easy way of getting just the public address of a service from a juju status?
[16:25] <rogpeppe> i'm wondering if there's a command buried somewhere along the same kind of lines as juju api-endpoints
[16:35] <mgz> rogpeppe: a service doesn't have a public address
[16:35] <mgz> rogpeppe: units of the service do
[16:35] <rogpeppe> mgz: i mean a unit, sorry :)
[16:35] <bogdanteleaga> the closest I get is juju status --format=oneline
[16:36] <rogpeppe> bogdanteleaga: that + awk or sed will do the trick, thanks
[16:37] <mgz> I've just used --format=json and a jsonpath tool thing in the past
[16:37] <bogdanteleaga> juju status --format=oneline | cut -d ' ' -f 3
[16:37] <rogpeppe> bogdanteleaga: yeah.
[16:37] <bogdanteleaga> cut is a bit easier, at least for me :)
[16:37] <rogpeppe> bogdanteleaga: i haven't used cut in years :)
[16:37] <rogpeppe> bogdanteleaga: i can never remember whether field numbers start at 0 or 1
[16:38] <bogdanteleaga> heh, I always keep trying until I find it
[16:38] <bogdanteleaga> awk always seemed hard to use
[16:38] <rogpeppe> bogdanteleaga: i'll probably do: addresses=$(juju status --format oneline | awk '/^- myservicename/ {print $3}')
[16:38] <bogdanteleaga> but then, it does way more
[16:39] <rogpeppe> bogdanteleaga: awk is kinda awkward :)
[16:39] <bogdanteleaga> I didn't wanna use that one :D
[16:40] <rogpeppe> bodie_: i actually only realised the pun after i pressed return
[17:36] <alexisb> folks, do I have developers still around in US hours?
[17:36] <katco> alexisb: yep
[17:36] <alexisb> we have a hot issue I need someone to take
[17:37] <katco> alexisb: you should have natefinch, ericsnow, perrito666, and cherylj at your disposal
[17:40] <katco> cherylj: hey you around?
[18:06] <natefinch> alexisb: still need help?
[18:06] <alexisb> natefinch, nope
[18:07] <natefinch> alexisb: excellent
[22:21] <perrito666> ok, both branches pushed :) I am done


[00:15] <valorie> hmmm, I've never seen that
[00:16] <valorie> I guess I would tend to do in the commandline: `sudo apt update && sudo apt full-upgrade`
[00:17] <valorie> and if that didn't quiet it, `sudo apt install -f`, where f=fix
[01:54] <ponchale> hi
[01:54] <ponchale> how are you
[01:54] <ponchale> I'm back
[01:54] <ponchale> hehehe
[01:54] <ponchale> someone connected?
[04:57] <FlameReaper-PC> Is there a reason why sddm doesn't show up? Tried restarting it several times but I don't see anything. Logs seem to show it starts normally... but I see nothing
[05:04] <bobbySmurda> Is kubuntu active still being developed? Links from the kde community are dead and packages support versions up to like 13.10 since then nothing.
[05:34] <FlameReaper-PC> All right, sddm thinks it's running but it doesnt' seem to load to the login screen. It just leaves the screen it's supposed to start still with the kernel messages visible.
[05:34] <FlameReaper-PC> as a result I have to use startx.
[05:35] <FlameReaper-PC> Anyone has any idea why? I'll post the necessary logs if needed.
[06:18] <jiuser17> how is the state in "encrypting kubuntu with dmcrypt using the gui-installer" ? this bug exists for more than 4 years now. In my opinion a not-so-good-thing. if you also want to reach beginners
[06:28] <MacLeod> Why beginners are necessary? especially will only shout at new plasma
[06:33] <jiuser17> it was just a compare to ugly unity-ubuntu or other gtk-based *untus... in any of them you can select "full disk encryption".. set your pw and thats it.. only under kubuntu you always had to to luks/dmcrypt in konsole. I alway been kubuntu user. but I set-up many installations.
[06:34] <jiuser17> and in these times.. encryption is a must have imho
[06:34] <jiuser17> I always wished it would have been so easy to use dmcrypt with the kubuntu installer..
[06:39] <MacLeod> some communities talk a lot of Kubuntu's death :D
[06:41] <jiuser17> is there a good alternativ if it really would die?
[06:41] <jiuser17> i think no
[06:41] <valorie> well, you could help us improve the installer
[06:42] <valorie> we're not dying, but it's been a struggle lately
[06:42] <valorie> the entire team works well together, and we have fun
[06:42] <jiuser17> if I had the skills I would help. be sure.. but I am not a programmer/developer.. just a "linux-power-user" since a couple of years now :-(
[06:42] <valorie> but there are not enough of us right now
[06:43] <valorie> jiuser17: which is where most of us started, right?
[06:44] <jiuser17> valorie: you are right :-)  but let me ask.. do you personally know this bug I mean?  how could I do something against that
[06:44] <valorie> I'm not a coder either, so I don't
[06:45] <valorie> however, if you drop into #kubuntu-devel when people are awake, or write to kubuntu-devel list and offer, I'll bet you get some pointers on a good direction
[06:46] <valorie> for starters, if ubuntu's installer offers that, then what needs to be done is to compare, and fix ours
[06:47] <valorie>  because encryption has nothing to do with KDE software
[06:47] <jiuser17> valorie: so if you arent a coder either.. how do you participate?  what do you DO? :-)
[06:47] <valorie> I'm on the kubuntu council, I write, and answer people's questions
[06:47] <valorie> I'm a grandmother, and don't have the yen to learn to program
[06:47] <jiuser17> ok thats pretty cool
[06:48] <valorie> however, I'm a good writer, editor, and love people and tech
[06:48] <valorie> so that's how I pitched in
[06:49] <valorie> oh, I do testing as well
[06:49] <jiuser17> :-) :-)  at what age can I call myself to be a grandfather? very interesting :-)   perhaps I could apply as kubuntu-grandpa
[06:49] <valorie> it was my middle son and his wife having my grandson Oscar!
[06:50] <valorie> I blog as linuxgrandma btw
[06:50] <valorie> and I work in KDE as well
[06:51] <jiuser17> very cool. will have a look at your blog..
[06:51] <valorie> neat!
[06:52] <jiuser17> about the installer problem.. gonna ask perhaps in the dev channel.. I know there are bigger problems at this time.. but it is worth a question
[06:52] <jiuser17> bye
[06:52] <valorie> sometimes people say that they are beginners, and so can't contribute
[06:52] <valorie> but "beginner" status is a super-power
[06:53] <valorie> you pick up on glitches that the devels work around habitually, and forget to fix
[06:53] <jiuser17> always knew to be a super hero... :-)
[06:54] <valorie> especially for testing
[06:56] <valorie> oh, and finding and fixing documentation
[06:57] <MacLeod> i don't say that dies. i say that there is such talks, and in large quantities...
[06:58] <valorie> that's too bad, and not based in reality
[06:58] <MacLeod> it has moved me to begin to learn a situation and try to participate
[06:58] <MacLeod> i know
[06:58] <valorie> great!
[07:01] <MacLeod> installer has one more bug btw
[07:02] <MacLeod> on 16.04 daily
[07:02] <valorie> oh, have both of you filed these bugs in launchpad?
[07:03] <valorie> the easiest way is `ubuntu-bug ubiquity` in the commandline
[07:04] <valorie> that way the system gathers all necessary info from your computer
[07:08] <MacLeod> crashes on machines that has no UEFI, underfined field or smt
[07:08] <MacLeod> it's not mine, was caught by several people from community
[07:09] <valorie> right, I think there is no non-uefi version for recent releases
[07:09] <valorie> !uefi
[07:10] <valorie> maybe the mini-iso has no uefi
[07:10] <valorie> not sure
[07:14] <MacLeod> problem not in uefi directly. i think script does some init, but can't get field secure_boot or something like that, i forgot(
[07:15] <MacLeod> and crashes when in another part tries to read that field
[07:15] <valorie> please file a bug next time you test
[07:16] <valorie> also, are you reporting your test results in the qa site?
[07:16] <valorie> we *need* testing, for this LTS more than anything
[07:17] <valorie> http://iso.qa.ubuntu.com/
[07:17] <valorie> follow the links there to get to the ISOs for testing
[07:31] <MacLeod> I did not especially tested 16.04 cause there old version of plasma
[07:32] <MacLeod> i makes Qt / plasma from sources and practice deep diving to repos/code last week :P
[07:32] <valorie> right, we're having a bit of a problem getting the latest into the archive
[07:32] <valorie> hopefully that happens Very Soon
[07:32] <valorie> our paperwork (FFe) is nearly done
[07:33] <valorie> we just need testing
[07:36] <MacLeod> i know several people who work testing hard
[07:36] <valorie> that's good, IF the results are reported
[07:36] <MacLeod> but... have lost in translation problem (
[07:40] <MacLeod> they from our russian community http://kubuntu.ru
[07:40] <valorie> translation/internationalization problems are bugs which should be reported also, MacLeod
[07:40] <valorie> there probably needs to be someone who can report or at least comment in english though
[07:45] <MacLeod> only the few can conduct any activity on English speaking resources
[07:45] <MacLeod> I will try to help them...) many years community live separately mostly, it is unfair
[07:46] <valorie> yes, it's great to know that there is a thriving russian community
[07:47] <valorie> we have lots of active users in Romania as well; fortunately one of our devels is Romanian and speaks english well also
[07:47] <valorie> so it would be great if you got more involved
[07:48] <valorie> site looks great!
[07:49] <valorie> in fact, it would be cool if you wrote a little piece about the site for the main Kubuntu.org site
[07:49] <valorie> and send it to Kubuntu-devel ?
[07:49] <valorie> just a few sentences
[07:57] <MacLeod> I'll tell more - many people here loves KDE and kubuntu but happens cry about bugs and packaging delays)
[07:57] <MacLeod> well, I'll prepare the description
[07:58] <valorie> super, we'd love closer ties with our international users
[07:59] <valorie> so we can make the experience better for all of you
[08:03] <MacLeod> i think so
[08:03] <MacLeod> actually my English isn't really good, in perfection only Russian and pair of programming languages))
[08:04] <MacLeod> but it's better than nothing
[08:04] <valorie> your english is lovely
[08:04] <valorie> and if you hang out with us english-speakers, it can only get worse
[08:04] <valorie> lol
[08:05] <valorie> what sort of programming do you do?
[08:10] <MacLeod> I've just got used to speak, write paragraphs of the text freely. and now i experience some restrictions :)
[08:11] <valorie> I can help
[08:11] <MacLeod> c-like, c++ and c# mostly. and javascript/node.js
[08:11] <valorie> you could send it directly to me, I can edit, and send it back
[08:11] <valorie><EMAIL_ADDRESS>[08:11] <MacLeod> it would be great! thanks
[08:12] <valorie> I look forward to working with you on this
[08:15] <MacLeod> okay, nice
[08:25] <FlameReaper-PC> I have been rebooting a few times in attempts to fix my SDDM problems but so far I haven't resolved anything, was there anyone who responded to my query before?
[08:28] <valorie> FlameReaper-PC: no, but have you tried
[08:28] <valorie> systemctl enable sddm in a tty?
[08:29] <valorie> `systemctl enable sddm` in a tty?
[08:29] <valorie> within the tick marks
[08:30] <valorie> btw, is this in 15.04, or 15.10 ?
[08:31] <FlameReaper-PC> valorie: 15.10
[08:31] <valorie> hmmm
[08:31] <FlameReaper-PC> I have tried systemctl enable sddm and disabling it a few times
[08:31] <valorie> I haven't had problems with sddm for over a year
[08:31] <FlameReaper-PC> let's see in chronology
[08:31] <valorie> `systemctl start sddm`
[08:31] <FlameReaper-PC> I was following the instructions to remove Intel's drivers from 01.org
[08:32] <FlameReaper-PC> up to that point I have no problems, and also because I'm replacing my graphics card
[08:32] <valorie> hmmm, that isn't a site I'm familiar with
[08:32] <FlameReaper-PC> or wait
[08:32] <valorie> better to stick with official pages
[08:32] <valorie> !intell
[08:32] <valorie> oops
[08:32] <valorie> !intel
[08:32] <FlameReaper-PC> ah yes it was https://01.org/
[08:33] <valorie> this is for chromeOS
[08:33] <valorie> not ubuntu
[08:33] <FlameReaper-PC> https://01.org/linuxgraphics << here to be precise
[08:33] <FlameReaper-PC> and so I did the procedure to remove it
[08:34] <FlameReaper-PC> and rebooted
[08:34] <valorie> The driver enables desktop-like visuals for people that rely on mobile devices for gaming, entertainment, medicine, energy or design.
[08:34] <valorie> is this a mobile device?
[08:35] <FlameReaper-PC> No
[08:35] <FlameReaper-PC> it's a PC
[08:35] <FlameReaper-PC> http://pastebin.com/JdmEu0Ym SDDM's log
[08:35] <valorie> I think this is the problem
[08:35] <valorie> that is not the proper site for a driver download
[08:35] <FlameReaper-PC> Yeah, I already had the drivers there removed
[08:35] <FlameReaper-PC> nouveau is working as it should on my PC right now, but SDDM remains weird for me
[08:36] <FlameReaper-PC> from what I can understand from SDDM's logs was it behaved normally, but from what i can see it doesnt' show up the login UI
[08:36] <valorie> something is stopping it, but I don't know what
[08:36] <valorie> your paste shows it being stopped
[08:36] <FlameReaper-PC> At the end down there it's because I killed it by 'systemctl stop sddm'
[08:37] <valorie> ah
[08:37] <FlameReaper-PC> because at that point SDDM's UI isn't showing up
[08:37] <valorie> unfortunately, although we use SDDM, it is not our software, and the rest of Ubuntu doesn't use it either
[08:37] <FlameReaper-PC> if I try to do a normal boot the screen just stays there and then jumps back into showing the kernel logs visible on startup
[08:37] <FlameReaper-PC> do I need to ask KDE regarding this?
[08:38] <FlameReaper-PC> also I've tried installing LightDM as alternative but it's not working for me
[08:38] <valorie> well, I think you need new intel drivers
[08:38] <valorie> right, and we offer no help for lightdm
[08:38] <valorie> we've not used it for quite awhile
[08:38] <FlameReaper-PC> valorie: but I already rolled back to the drivers from the official repositories
[08:39] <valorie> ah, good
[08:39] <valorie> ok
[08:39] <valorie> !info sddm
[08:39] <FlameReaper-PC> right now a workaround I have is to boot via nodm
[08:39] <valorie> how about `sudo apt install --reinstall sddm`
[08:39] <FlameReaper-PC> valorie: already tried to no avail
[08:40] <valorie> ok, how about dpkg sddm --reconfigure
[08:40] <valorie> uh, not sure that's quite right
[08:40] <FlameReaper-PC> hold on, I just reinstalled sddm again
[08:41] <FlameReaper-PC> I'll try this one more time, it just made changes to the Xsession scripts
[08:41] <FlameReaper-PC> I can just kill the X server and try restarting via sddm, right?
[08:42] <valorie> if you know to startx
[08:42] <valorie> sounds like you do
[08:42] <FlameReaper-PC> I can do it, let's see if SDDM plays nicely now
[08:53] <FlameReaper-PC> Back, looks like that didn't do it either.
[08:53] <FlameReaper-PC> In the meantime I have some more logs, I'll put them up now.
[08:58] <valorie> well, I can't help much with them, but you could write to the kubuntu-user list perhaps
[08:59] <FlameReaper-PC> sddm.log: http://pastebin.com/8sN7pKN1, systemctl status sddm: http://pastebin.com/JDPZjiAB, syslog | grep -i sddm: http://pastebin.com/1embz9bZ, Xorg.0.log: http://pastebin.com/eEVAe5EY
[08:59] <FlameReaper-PC> valorie: I guess I'll do some more reading if I can find a solution then, thanks
[09:09] <lordievader> Good morning.
[09:12] <valorie> lordievader: are you any good with sddm?
[09:12] <lordievader> Err, not really. It works for me... still need to configure it some day.
[09:13] <valorie> heh, same here
[09:13] <valorie> FlameReaper-PC has had some problems and just posted very complete logs above
[09:14] <lordievader> This is one of those, login -> get thrown back to the login screen, things?
[09:15] <valorie> "sddm thinks it's running but it doesnt' seem to load to the login screen. It just leaves the screen it's supposed to start still with the kernel messages visible."
[09:15] <lordievader> Oeh, that is new.
[09:15] <valorie> yeah
[09:16] <lordievader> Why the recovery mode?
[09:16] <valorie> FlameReaper-PC: still here?
[09:17] <FlameReaper-PC> valorie: Yes
[09:18] <valorie> lordievader asks why the recovery mode?
[09:18] <FlameReaper-PC> because otherwise I can't seem to access the tty
[09:18] <FlameReaper-PC> right now a workaround I have is to start by using nodm
[09:19] <lordievader> FlameReaper-PC: Please reboot without it.
[09:19] <FlameReaper-PC> as it is my SDDM setting was to autologin
[09:19] <lordievader> Sddm has a few scripts which check for these kind of keywords.
[09:20] <FlameReaper-PC> lordievader: reboot without?
[09:20] <lordievader> Without the recovery parameter.
[09:20] <FlameReaper-PC> the recovery mode?
[09:21] <FlameReaper-PC> also if it helps should I set SDDM to require my password for login or does it not change anything
[09:21] <lordievader> For this problem it shouldn't matter.
[09:28] <FlameReaper-PC> back in normal mode, but sddm still doesnt' show itself
[09:29] <lordievader> FlameReaper-PC: Not in another tty, by any chance?
[09:33] <FlameReaper-PC> hmm
[09:33] <FlameReaper-PC> let's see
[09:33] <lordievader> ?
[09:34] <FlameReaper-PC> nope, that doesn't seem to be the case
[09:35] <FlameReaper-PC> normally SDDM will start on vt7, right?
[09:35] <FlameReaper-PC> either way I don't see it running on ttys 1~6
[09:41] <lordievader> That depends, I believe Kubuntu still starts it on vt7 yes.
[09:41] <lordievader> You could run the binary yourself (as root) and see if it crashes or something.
[09:43] <FlameReaper-PC> lordievader: as in 'sudo /usr/bin/sddm' or something?
[09:43] <lordievader> FlameReaper-PC: Yes, run that from a tty.
[09:48] <FlameReaper-PC> No result
[09:50] <lordievader> What happens when you start x in one tty (sudo /usr/bin/X :0) and in another tty run 'startkde' (or startplasma whatever it is nowadays)?
[09:53] <FlameReaper-PC> X returns a black screen, and the other tty returns "$DISPLAY is not set or cannot connect to X server."
[09:53] <lordievader> Ah right, sorry: DISPLAY=:0 startkde
[09:54] <FlameReaper-PC> right
[09:54] <FlameReaper-PC> hold on
[09:59] <FlameReaper-PC> Doing that made the display turn off for a bit, and then it turns back on to a black screen.
[09:59] <FlameReaper-PC> startkde returns no error, but nothing seems to load on the black screen.
[09:59] <FlameReaper-PC> Coincidentally there's this one line in syslog: [ 1989.168154] kactivitymanage[9926]: segfault at 7f7ff1d6dcd0 ip 00007f7fd8015291 sp 00007fff25ce7788 error 4 in libQt5Sql.so.5.5.1[7f7fd8001000+3f000]
[09:59] <lordievader> Hmm, seems like the graphics driver is being difficult.
[10:00] <lordievader> What nVidia do you have and is it a hybrid system?
[10:01] <FlameReaper-PC> Reverted to a GTS 250
[10:02] <lordievader> FlameReaper-PC: No hybrid setup?
[10:03] <FlameReaper-PC> It's a desktop system and I don't think the motherboard allows for a hybrid set-up
[10:04] <lordievader> Right, that makes it easier.
[10:04] <FlameReaper-PC> unless if I need to set my motherboard to only detect the discrete GPU
[10:04] <lordievader> Is it a possibility to install the closed source driver?
[10:04] <FlameReaper-PC> I had it before but I reverted to nouveau after
[10:33] <FlameReaper-PC> The proprietary driver works, however I'm starting to feel the issue boils down to SDDM for some reason.
[10:34] <FlameReaper-PC> "sudo /usr/bin/X :0" in one tty and "DISPLAY=:0 startkde" in another works, but SDDM still shows nothing
[10:44] <lordievader> Hmm, do you have backports installed?
[10:46] <FlameReaper-PC> yes.
[10:47] <lordievader> Hmm, your system is up to date?
[10:48] <FlameReaper-PC> yes.
[10:48] <lordievader> When did this problem start? Perhaps after an update of sddm? (Check /var/log/apt/history to see what was updated and when)
[11:18] <FlameReaper-PC> [Saturday, March 5, 2016] [6:48:58 PM MYT] <lordievader> When did this problem start? Perhaps after an update of sddm? (Check /var/log/apt/history to see what was updated and when)
[11:18] <FlameReaper-PC> Started when I installed my graphics card which was yesterday?
[11:19] <FlameReaper-PC> Before that I was running off the Intel drivers from the Intel driver installer
[11:19] <lordievader> Hmm, so not a regression bug... Well still worthy of a bug report ;)
[11:20] <lordievader> !bug | FlameReaper-PC
[11:59] <BluesKaj> 'Morning all
[12:08] <FlameReaper-PC> Testing the X display with sddm-greeter works, but sddm itself seems to refuse to work.
[12:08] <lordievader> Could you paste sddm's xorg log again?
[12:09] <FlameReaper-PC> lordievader: is it sddm.log?
[12:26] <FlameReaper-PC> It's mysteriously fixed somehow and I don't even know why...
[12:26] <FlameReaper-PC> Rebooted once and SDDM is back. I'm able to login and log out
[12:27] <FlameReaper-PC> just to be sure, I'll try this again
[12:27] <FlameReaper-PC> i mean, try relogging in as normal
[12:29] <FlameReaper-PC> All right, SDDM is now back. Now time for a minor issue: network manager doesn't seem to remember the passphrase for the network I've set for it
[12:32] <FlameReaper-PC> kwallet doesn't seem to be open and I can't seem to open it
[12:32] <soee> FlameReaper-PC: you are on 15.10 ?
[12:33] <lordievader> FlameReaper-PC: Good that the sddm issue fixed itself :)
[12:33] <FlameReaper-PC> soee: yes
[12:33] <FlameReaper-PC> lordievader: as puzzled as I am about it, I'm very glad. :)
[12:34] <soee> FlameReaper-PC: you have backports ppa enabled with latest updates /
[12:34] <FlameReaper-PC> yes
[12:35] <FlameReaper-PC> and the system is currently up-to-date.
[12:35] <soee> ok :)
[15:51] <AppAraat> hi, I was wondering, is there any way of making KDE windows feel a bit "smaller" in size? Right now it looks pretty huge on my 1366x768 display.
[15:52] <soee> well you can change boder size or remove them and make smaller window decoration by changing its utton sizes
[15:55] <AppAraat> ok I'll try that, thanks.
[16:33] <AppAraat> anyone knows why this happens in Konsole and not in Terminator - http://imgur.com/a/wZDvu
[16:33] <AppAraat> it's the last characters of the PS1
[16:33] <AppAraat> (especially)
[16:34] <AppAraat> both have terminus font running
[17:09] <Hydrogen> Hi Friends... I've got a dual monitor setup, but one of them is rotated 90 degrees.  I can tell it to rotate 90 degrees in the display config, but it still trys to set the resolution to 1920x1080 instead of 1080x1920, which makes the monitor very unhappy
[17:10] <Hydrogen> Is there a trick?
[17:12] <AppAraat> could this probably be related to video driver?
[17:21] <AppAraat> is there any way to change the entry in Dolphin Configurations -> Startup -> Home Folder to `$HOME` or `~` ?
[17:21] <AppAraat> primarily because I'm sometimes moving from one system to another, and users are named differently.
[17:26] <Hydrogen> AppAraat, my guess is it's related to xorg being huge and clunky and annoying, and I'm sure theres some command I probably should have memorized to make the display behave, but I didn't memorize it :/
[17:50] <Fritigern> valorie: Do you happen to be running 5.5.5 or later?
[17:50] <Fritigern> I am wondering if you ever get hit by the apt-check bug ( https://bugs.kde.org/358359 )
[17:53] <AppAraat> Hydrogen: I'm glad I have Intel Core i5 with HD4000 so I don't have to worry about graphic support of Wayland when it comes out. Hopefully it gets us much less headache
[18:21] <rogerduncan100> join
[18:23] <rogerduncan100> Internet wasn't working in Canada on 14.04 LTS but I guess somebody fixed it!
[18:24] <rogerduncan100> Must have sent a   pulse to my IP address...............
[18:24] <rogerduncan100> You people are so clever.
[18:25] <rogerduncan100> I was getting ready to reinstall and the whole shebang.
[18:26] <rogerduncan100> logout
[18:54] <AppAraat> http://i.imgur.com/rrke8Qj.jpg
[20:27] <bass> bizzare bug I think - i change the "file association" of mp4 files ... and something immediately changes it back! how to fix this??
[20:41] <doc2rue> hello word !
[20:55] <bayatoon> slm
[21:28] <hydrogen> Hi again... So now my kubuntu does not want to display two screens at once regardless of orientation
[21:29] <hydrogen> It works fine if I unify the outputs, but if I want two discrete monitors it displays one as black
[21:29] <hydrogen> (yes, they are both enabled, yes, the resolutions on both are appropriate for the monitor)
[22:26] <Asuran> is there a websearch where i can browse kubuntu 15.10 repo?
[22:26] <Asuran> except the repo url itself, i want to get some overview which versions kubuntu uses
[22:26] <soee_> it is Ubuntu repo basically
[22:27] <Asuran> ah okay thanks, i just asking because of calligra
[22:27] <Asuran> i would like have most recent version of it or not too far behind
[22:27] <Unit193> !info calligra
[22:28] <Asuran> ah okay and i can safely mix ubuntu packages into kubuntu?
[22:28] <Asuran> i ask because of ppa
[22:29] <Asuran> and third party stuff
[22:29] <soee_> as i said all packages Ubuntu has Kubuntu can have also as it is basedon ubuntu
[22:29] <Unit193> They are the same exact repos, so you already have.  Though you have to be careful with PPAs.
[22:31] <Asuran> Unit193: ah and why? because ubuntu packages rely on untiy and kubuntu doesnt provide it or like that
[22:31] <Unit193> Nothing to do with KDE vs Unity, just PPAs are from whatever random user you're picking it up from, soo.
[22:31] <Unit193> !ppa
[22:32] <Asuran> ah okay
[22:33] <Asuran> okay thanks so far
[23:51] <lyze> Heyho :) How can I change the panel so that whenever a program is in "fullscreen" mode (set via right clicking the frame -> fullscreen) and it's in focus that the panel hides but hwenever I alt tab out of it the panel gets visible?
[23:51] <lyze> Kinda like in xfce / windows


[07:34] <dholbach> good morning
[09:05] <dpm> dholbach, davidcalle, I followed the conversation on the community team channel, and this is something I actually wanted to discuss a while ago - could we document the way we use branches (and the deployment procedure) somewhere in a doc? Perhaps in a README.md file on the spec branch or on the d.u.c branches
[09:09] <davidcalle> dpm: the current - actually impossible to do - way is documented in deploy.md
[09:10] <davidcalle> dpm: so yeah, this will be replaced
[09:11] <dholbach> cool
[09:14] <dpm> awesome, thanks davidcalle
[13:18] <mhall119> davidcalle: what info do you need from me?
[13:38] <davidcalle> Hey mhall119 :) I've found the RT from january and it was revno 162 (hence the staging branch), so I guess we should keep it this way and request a deployment of the same branch, what do you think?
[13:39] <davidcalle> (which is actually what is deployed on staging: (lp:staging/164)
[13:41] <mhall119> davidcalle: we don't deploy to production from branches, only from the tarball in swift
[13:44] <davidcalle> mhall119: we don't pull anything at all?
[13:45] <mhall119> nope
[13:45] <mhall119> they just do a `juju set build_label=$version` and it pulls the tarball out of swift
[13:46] <davidcalle> mhall119: I was expecting something to be pulled when this config is changed :) Great
[13:47] <mhall119> so the production branch should be identical to what's in production, but it's not the source of production deployments itself
[13:50] <davidcalle> Ok then. /me starts to file the RT
[14:18] <davidcalle> mhall119: does the following steps seem clear to you for an RT?  (end of doc) http://pad.ubuntu.com/zdvmD4Ekb6
[14:19] <mhall119> starting at line 68?
[14:20] <davidcalle> mhall119: yes
[14:21] <mhall119> hmmm, does piping yes to a manage.py command work? Does it terminate when the manage.py command exits?
[14:23] <davidcalle> mhall119: it returns "yes: write error" but actually works
[14:23] <mhall119> ok
[14:24] <mhall119> otherwise it looks fine, just make sure they have a db backup of the last stuff before starting on this
[14:25] <davidcalle> mhall119: that's the first step ;) Maybe I should make step 2: MAKE SURE YOU HAVE BACKED UP THE DATABASE
[14:26] <davidcalle> Alright, let's explode prod ;)
[14:30] <mhall119> \o/
[14:31] <mhall119> burn it down!
[14:44]  * dholbach crosses fingers
[14:47] <davidcalle> dpm: mhall119: dholbach: you are CCed on the RT ;)
[14:47]  * davidcalle throws RT over the wall and runs
[14:47] <dholbach> yep, saw it :)
[14:47] <mhall119> just saw it
[14:47] <mhall119> now run!
[14:47] <mhall119> just kidding, it'll probably take a few days before anybody tries to run it
[14:48] <davidcalle> mhall119: too late I've wished a happy deployment day to Daniel this morning, they don't have a choice :)
[14:48] <dpm> great