[06:52] <bluesabre> Unit193: ah... the meeting is a hangout?
[06:53] <flocculant> bluesabre: morning - and I would guess it is
[06:53] <flocculant> anything to do with that community team generally is
[06:53]  * bluesabre would prefer IRC at this hour
[06:54]  * flocculant would prefer IRC at any hour - some people are really hard to understand however awake you are :p
[06:57] <Unit193> bluesabre: Crap, it is?
[06:59] <flocculant> ask dpm - he's probably about in ubuntu-community-team now, if he's not then dholbach will be
[07:03] <bluesabre> Unit193: can go without video
[07:04] <Unit193> bluesabre: This is going to be fun...
[07:04] <flocculant> did a time get picked yet?
[07:08] <Unit193> Yep, now.
[07:08] <flocculant> oh good luck then :p
[07:09] <Unit193> Indeed, didn't have time to setup a mic.
[07:17] <Unit193> bluesabre: Did I miss anything about any dpkg/apt integration at all?  Even most basic levels?
[07:18] <bluesabre> it's different than apt, doesn't break apt, coexists with apt
[07:19] <Unit193> Right, like pip/gems..
[07:26] <bluesabre> Unit193: really good question
[07:29] <Unit193> bluesabre: Thanks, you had great ones.
[07:30] <bluesabre> the questions relevant to me :D
[07:30] <ochosi> hi folks
[07:30] <ochosi> can't be @hangout
[07:31] <ochosi> is it still ongoing?
[07:31] <flocculant> morning ochosi
[07:31] <flocculant> cya all later
[07:31] <bluesabre> hey ochosi, yes, will link you the youtube link when its done
[07:32] <bluesabre> (ubuntu snappy meeting, Unit193 and I are there)
[07:34] <bluesabre> This does seem better than My Apps, which had a horribly slow review queue and required a new upload for every ubuntu release
[07:35] <Unit193> I don't know anything of My Apps.
[07:35] <Unit193> Wonder how support will be. :3
[07:35] <Unit193> support == user support.
[07:40] <Unit193> bluesabre: Hah, just what I was going for.
[07:43] <bluesabre> :)
[07:47] <Unit193> bluesabre: You're awsome, thanks for staying up.  Get some good rest.
[07:48] <bluesabre> ha
[07:48] <bluesabre> I went to bed and set an alarm
[07:48] <bluesabre> and now I'll probably go back to bed :D
[07:48] <Unit193> ...I just got home in time for it.
[07:50] <bluesabre> ochosi: they'll probably publish a link to it a bit later
[07:50] <bluesabre> main takeaways...
[07:50] <bluesabre> coexists with apt
[07:51] <bluesabre> snappy apps are launched by ubuntu-snappy-cli
[07:51] <Unit193> Basically lives in chroots (squashfs filesystems), is for content providers to get content to end users.
[07:51] <bluesabre> libraries are contained within the snaps (and in the future may be in separate library snaps)
[07:52] <bluesabre> updates to the snappy system with be backported to 16.04 as they come along
[07:52] <bluesabre> *will
[07:53] <bluesabre> sounds like a pretty good system, and I can see a lot of use cases with it
[07:55] <bluesabre> Unit193: the old MyApps - https://developer.ubuntu.com/en/publish/ - biggest problem was things staying in "Awaiting moderation" for months at a time, making it faster to get things into Debian NEW and finding a MOTU to sync it back to Ubuntu :|
[07:56] <Unit193> Hah, wow.  Niiice.
[07:56] <bluesabre> and the general issue with having to republish for every ubuntu release you wanted your stuff to be on
[07:56] <bluesabre> menulibre was there at the beginning :D
[07:57] <Unit193> So, might be fun to poke with a stick, I'm not against them, but I don't really see me using them either.
[07:57] <Unit193> Yeah, was in extras.
[07:57] <bluesabre> yup
[07:58] <bluesabre> its pretty cool for their IOT and embedded devices, I think its something like "snappy deploy $something $ip" to punt an app to a device
[07:59] <bluesabre> anyway, back to bed for me
[07:59] <bluesabre> night/morning all
[07:59] <Unit193> Not as useful on the desktop, but informative and as I said, not against it.
[07:59] <Unit193> bluesabre: Sleep well.
[08:35] <Unit193> Suppose that should go on the agenda.
[11:35] <pavlushka> suspend resumes to black screen.
[11:35] <pavlushka> and hi Every one!
[11:39] <flocculant> Unit193 bluesabre - thanks for going there to see what the crack is with it :)
[11:40] <flocculant> Unit193: agenda - might be useful to do that - saves going over the same ground over and over :p
[11:40] <flocculant> hi pavlushka
[11:41] <pavlushka> Hi flocculant !!! :)
[11:42] <pavlushka> flocculant, what do I do? tested more than 3 times today.
[11:43] <flocculant> what do you mean by what do I do?
[11:44] <pavlushka> suspend resumes to black screen
[11:44] <flocculant> report it
[11:44] <flocculant> once
[11:44] <pavlushka> ok
[11:45] <pavlushka> using ubuntu manual test or LP bug?
[11:45] <flocculant> you don't report bugs with the tracker - it's not possible
[11:46] <flocculant> you list on the tracker the bug you've reported through launchpad via ubuntu-bug
[11:51] <flocculant> pavlushka: is this your system that's got the broken screen that you have to use an external monitor on?
[11:51] <flocculant> if that's the case you need to make it plain
[11:51] <pavlushka> yes
[11:52] <pavlushka> plain means removing the external monitor?
[11:54] <flocculant> no plain means making it obvious that you've got a broken laptop and external monitor in the report
[11:55] <pavlushka> definitely I will as I did for the previous.
[11:55] <pavlushka> but thanks for pointing.
[11:56] <pavlushka> the priority gets hi.
[11:56] <flocculant> then wait for responses - no need to keep adding things, changing affected packages
[11:56] <pavlushka> awee, you got that!
[11:57] <flocculant> got what?
[11:58] <pavlushka> what you said, I did it for a bug. I was just not sure.
[11:58] <flocculant> bbl
[12:03] <pavlushka> ok
[14:20] <knome_tracker> 'lo
[14:25] <krytarik> knome_tracker: LOL
[14:25] <knome_tracker> krytarik: what?
[14:25] <krytarik> Nothing. :X
[14:25] <knome_tracker> i don't have access to my ssh host as i don't have my private key on my mum's laptop
[14:25] <knome_tracker> ...for a reason
[14:26] <Elroy> Hi Xubuntu Dev-Team - The Compton Problem with nVidia Driver over 352.-- is permanent and at 16.04 on AMD ("iommu=soft") + nVidia 970GTX - Install FAILS !
[14:27] <knome_tracker> compton?
[14:27] <Elroy> Coming later back ...
[14:27] <knome_tracker> that's not in the default install
[14:27] <Elroy> but its only a tearfree xcomposiotr
[14:27] <knome_tracker> don't get me wrong; i'd like it to work, but is it compton the reason the install is failing?
[14:28] <Elroy> no
[14:28] <knome_tracker> what is then?
[14:28] <knome_tracker> have you filed a bug?
[14:28] <Elroy> the reason is a problem with usb ("iommu=soft") and AMD Mainboard with iommu hard
[14:29] <knome_tracker> so.. you are adding a kernel boot option and then the installation doesn't work?
[14:30] <knome_tracker> in any case... have you filed a bug?
[14:30] <Elroy> Xubuntu 15.10 works fine to Install, but 16.04 can`t start the Nouveau Driver for the Install and writes the message "Live CD working in Progress - working - but hold on"
[14:31] <Elroy> Ojn Ubuntu MATE 16.04 there are not this fail
[14:31] <Elroy> and Ubuntu 16.04 also have not this fail
[14:32] <knome_tracker> ...have you filed a bug?
[14:33] <Elroy> i read about the compton fail with nVidia Driver up to 364.-- (tthere is now another competition about OpenGL - xrender doesn`t work on my machine
[14:33] <Elroy> must do now - the prob is - i can`t get a screenshot
[14:34] <Elroy> only my hardware constellation i can send you
[14:34] <knome_tracker> that's a start
[14:34] <knome_tracker> but please do not intertwine the compton issue to this
[14:34] <knome_tracker> if it's related, then it's not high priority for us
[14:34] <Elroy> working for a long time with xubuntu - it`s the first time i have this failure
[14:34] <knome_tracker> if it's not, it's better not mention it in the bug
[14:35] <knome_tracker> it sounds weird to me that this bug only happens with xubuntu, and it might be hard to reproduce, but...
[14:36] <Elroy> understand that compton another point is - excuse for my english, i`m 60 years old and coming from austria - german
[14:36] <knome_tracker> that's ok
[14:37] <Elroy> Interessting - Ubuntu-Gnome fails not - but budgie-remix have the same problem
[14:37] <krytarik> Elroy: Extending on what knome_tracker just said, did you checksum the image?
[14:37] <Elroy> yess
[14:37] <Elroy> with gnash and thunar
[14:38] <Elroy> i downloaded three times another image - every time the same
[14:38] <krytarik> !md5sum | Elroy
[14:39] <Elroy> okm prob this ... no i`m waiting for a upgrade and driving with version 15.10 without any probs
[14:39] <Elroy> thxs for writng and tipps - see you
[14:40] <krytarik> Thanks as well.
[14:40] <knome_tracker> Elroy: and please file the bug... :P
[14:40] <Elroy> stay only in future with xubuntu - before i have testing for my linux-forum 35 distros, but for playing ist this the best
[14:40] <Elroy> make this
[14:41] <Elroy> bye
[17:37] <Nairwolf> hi guys ;) I've been away from computers recently. What's new ? We're after the kernel freeze. Do you need more tests ?
[17:40] <flocculant> Nairwolf: we always do - but if you want to hang on for a few days - next week will see the start of the release candidate testing fortnight
[17:42] <davmor2> flocculant: pfff next week I've been at it 3 days already ;)
[17:43] <Nairwolf> flocculant: okay, I should be able to be present.
[17:43] <Nairwolf> Maybe this week, I will try to help to improve french translations
[17:45] <flocculant> davmor2: :)
[17:45] <flocculant> davmor2: I just want to double check my triple check before I ask people to test upgrades ...
[17:46] <davmor2> flocculant: they work but keep it quiet because someone will break it if you tell them
[17:48] <flocculant> yea - that's what my triple check found out :p
[17:49] <flocculant> knome: perhaps you could explain some arcane wiki wobblyness - target wiki page does not exist - copy from existing to target - can't do that target exists ...
[17:50]  * flocculant just put it down to some strangeness that tends to accrue around ubuntu wiki(s)
[18:30] <ochosi> evening
[18:34] <ochosi> knome: including the back and forth it seems that the team is leaning towards option 2) (10 winners)
[18:44] <flocculant> ochosi: good evening :)
[19:28] <knome> i'm feeling down because no more wittgenstein quotes were exchanged in the thread
[19:30] <knome> ochosi, in any way time is tight, and now we need to contact more winners
[19:30] <knome> who's volunteering for that?
[19:31] <knome> i mean i can do it at latest tomorrow, but if somebody can do it before..
[19:43] <flocculant> knome: I can do that - have any gone out yet at all?
[19:43] <flocculant> and any pro-forma mail?
[19:44] <flocculant> hey dude - your submission will be in the package we seed with xenial - congrats for thats
[19:46] <flocculant> and it's 2 people ...
[19:57] <knome> flocculant, none gone out
[19:57] <knome> flocculant, we also need to check the attribution name
[19:57] <knome> flocculant, especially in cases it isn't clearly something they'd want to be called
[19:58] <knome> flocculant, maybe we can cowrite it in a pad
[19:58] <knome> unless you did it already :)
[19:58] <flocculant> nope - done nothing as I wasn't sure what had been done
[19:58] <knome> :D
[19:58] <knome> nothing was done
[19:59] <flocculant> :)
[19:59] <knome> i'll open a pad
[19:59] <knome> http://pad.ubuntu.com/xx-wallpaper-winners
[20:01] <flocculant> mmm
[20:01] <flocculant> having trouble opening the contest site
[20:01] <knome> mm
[20:02] <knome> actually i'm thinking we should "TO" these mails to the xubuntu contacts mailing list so we have a sensible archive of the replies
[20:03] <flocculant> xubuntu contacts?
[20:03] <knome> yeah
[20:03] <flocculant> no idea wth that is
[20:03] <knome> https://lists.ubuntu.com/mailman/listinfo/xubuntu-contacts
[20:03] <flocculant> oh one of those private jobs
[20:04] <knome> it says "only members of the xubuntu team are subscribed to this list" but it means "only xubuntu team members *can* subscribe to this list"
[20:04] <knome> yep
[20:04] <knome> (that said, if anybody wants access, feel free to poke me)
[20:05] <knome> it's not a very exciting list really though
[20:05] <flocculant> well
[20:05] <flocculant> I'm certainly not going to TO that list and get spammed by moderation messages
[20:05] <Unit193> flocculant: FWIW, I remember discussions about when it was created, and since then it has been mentioned several times. :3
[20:06] <knome> it mostly has communication with the officially endorsed vendors
[20:06] <flocculant> Unit193: possibly I have heard of it - but so infrequently I just *shrug*
[20:06] <flocculant> knome: right
[20:06] <Unit193> Right, I didn't know I could have access, but I never really checked either.  Then again, most of the time I follow via archives. >_>
[20:06] <knome> and a test email from lyz with the topic "Fruit"
[20:06] <flocculant> ha ha
[20:06] <Unit193> Hah!
[20:06] <knome> Unit193, archives are private ;)
[20:07] <Unit193> Yes, figured.
[20:07] <flocculant> knome: moderating needed
[20:07] <knome> flocculant, if you want to be subbed, i can do that, or if you rather not get more mail, i can add you to the auto-mod list
[20:07] <flocculant> I subbed
[20:07] <flocculant> ^^
[20:07] <knome> oh ;)
[20:08] <knome> let's see..
[20:08] <flocculant> didn't think about auto-modding
[20:08] <knome> approved
[20:08] <flocculant> I'll likely unsub later :p
[20:08] <knome> wfm too
[20:08] <flocculant> thanks
[20:08] <flocculant> ok - happy to TO that list now :p
[20:08] <flocculant> still not getting to the site
[20:08] <knome> i really don't mind who of the team is subbed, mostly i think most do not need to be subbed..
[20:08] <knome> pff :)
[20:09] <Unit193> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2016-April/001179.html that can be nice.
[20:09] <knome> flocculant, let me try something
[20:09] <flocculant> read that - mmm - over there in the wall above my head :p
[20:09] <flocculant> Unit193: ^^
[20:09] <Unit193> flocculant: Ah, well it's handy, means less delta to Debian. \o/
[20:09] <knome> actually i seem to be having trouble with the contest site too
[20:10] <knome> >__<
[20:10] <flocculant> ;)
[20:11] <flocculant> bluesabre: what is the latest date for packaging the wallpapers?
[20:11] <ochosi> knome: yeah, i'm feeling blue too, no more wittgenstein quotes plus flocculant broke his vow never to bring up the knickers again
[20:11] <flocculant> ochosi: well
[20:11] <knome> yeah, knickers should be left *down*
[20:11] <flocculant> mailing list was a new set of knickers :p
[20:11] <knome> flocculant, able to log in now
[20:12] <ochosi> flocculant: well a fresh pair is the least i'd expect!
[20:12] <flocculant> knome: nope
[20:12] <knome> bluesabre, i guess you'd like to push before final freeze? :P
[20:12] <knome> flocculant, i mean i am..
[20:12] <knome> i logged you out from all sessions
[20:12] <knome> so you can try again now
[20:13] <knome> ochosi, what kind of scrutiny do you think we should take with unsplash stuff?
[20:13] <knome> ochosi, does unsplash give any contact addresses for a friendly notification?
[20:14] <knome> apparently not necessarily
[20:14] <ochosi> knome: not that i know of
[20:14] <ochosi> i think it's up to the authors
[20:14] <knome> yep
[20:14] <knome> all the way up to the authors
[20:14] <knome> :X
[20:15] <flocculant> in there now - nipping out - back soon
[20:15] <knome> ochosi, plz join the pad and read the last line
[20:15] <knome> ochosi, and tell me: if no confirmation, will we just expect the details are ok, or boot?
[20:16] <ochosi> not sure why we need confirmation for something that is already on a website..?
[20:16] <ochosi> so anyway, i wouldn't boot those submissions
[20:16] <ochosi> even if unconfirmed
[20:17] <knome> okay, so just expect details are right
[20:17] <ochosi> cause the authors already "confirmed" the details initially on unsplash
[20:17] <knome> yeah, but some people didn't "get" what attribution means
[20:17] <knome> so they inserted name of work there
[20:18] <ochosi> yeah, but in unsplash it's clear
[20:18] <knome> yes, but we aren't even talking just about unsplash
[20:18] <knome> actually we are talking everything BUT unsplash
[20:19] <ochosi> :)
[20:19] <knome> hmmh
[20:23] <knome> so since we are doing something for archival, should we actually attach (a thumnail of) the submission to the mail so that gets archived too
[20:23] <knome> instead of relying on some arbitrary urls
[20:25] <knome> ochosi, you realize 16UTC on sat is less than 24 hours from now?
[20:26] <ochosi> i didn't set that time/date :)
[20:26] <knome> i wrote sunday
[20:26] <knome> you corrected it to saturday
[20:26] <knome> "corrected"
[20:26] <ochosi> oh, maybe i mistyped then
[20:26] <ochosi> hehe
[20:26] <knome> i mean that can be earlier on sunday
[20:26] <knome> it all depends when sean is around to upload
[20:27] <knome> i'm fine with a 24-hour window too
[20:27] <knome> so likely 21UTC on sat
[20:27] <knome> but the more time we can give, the better
[20:27] <ochosi> yeah, up to bluesabre (or whoever uploads finally)
[20:28] <knome> maybe greenknife picks up the upload this time
[20:29] <Unit193> bluesabre: Get anywhere on thunar?
[20:35] <pavlushka> Hi every one!
[20:35] <pavlushka> the dist-upgrade is not supposed to behave like this I think, http://paste.ubuntu.com/15698126/
[20:36] <Unit193> It can.
[20:37] <pavlushka> then where's the different between "sudo apt-get upgrade & sudo apt-get dist-upgrade" ?
[20:37] <pavlushka> *diffenerce
[20:37] <Unit193> dist-upgrade will install new stuff, basically.  That can mean something conflicts that you have installed though.
[20:39] <pavlushka> is code-block conflicting with gcc then?
[20:39] <flocculant> ok back again
[20:40] <knome> flocculant, i'm pretty happy with the mail
[20:40] <knome> flocculant, needs a bit of tweaking for some bits
[20:40] <flocculant> yea just looking for Inglish :p
[20:40] <knome> flocculant, would probably make sense to rename the files to something other than their original names
[20:40] <ochosi> bbabl
[20:41] <knome> flocculant, and the thumbnail (600x in width, shown in the result overview) should be fine
[20:41] <knome> actually, that reminds me of something meh
[20:43] <flocculant> knome: where are you getting thumbnails from then?
[20:43] <knome> we need to crop some of the images
[20:43] <knome> flocculant, right-click the image on the results page, click view image
[20:43] <knome> gives you for example -> http://contest.xubuntu.org/wp-content/uploads/2016/03/squirreledit-600x375.jpg
[20:43] <flocculant> aah right
[20:44] <pavlushka> Unit193, what should I do then? can I fix it with a command or I have to uninstall the held back packages?
[20:44] <knome> the images that needs cropping are sent by me and ochosi
[20:44] <knome> so no need to mention that in the mail specifically
[20:45] <flocculant> will the contest url for the thumbnail remain? eg use that to grab the image in the mail I send
[20:45] <flocculant> or grab it to local and use that
[20:45] <knome> grab to local and attach to the mail
[20:46] <knome> the urls will not remain and i don't want to think what url would be static enough
[20:46] <flocculant> okey doke
[20:46] <knome> attaching to mail makes them stick with the info, so it's the best
[20:46] <knome> might be that moderating is required anyway then though :P
[20:46] <knome> because file size
[20:47] <knome> by all you mean including me and ochosi?
[20:47] <flocculant> yep
[20:47] <knome> sure, totally
[20:47] <flocculant> wasn't going to originally :)
[20:47] <knome> what i meant about not needing to mention resolution issues
[20:47] <knome> is that we know that already and i can do the cropping tomorrow
[20:47] <flocculant> yup
[20:53] <pavlushka> Unit193, a request, if it is possible to suggest anything before I go to sleep.
[20:54] <flocculant> knome: happy with that pad?
[20:54] <Unit193> Eh?
[20:54] <knome> flocculant, yeah
[20:55] <flocculant> ok - biab then ...
[20:55] <pavlushka> its 3 am here, I was gonna go sleep but the problem happened.
[20:55] <knome> flocculant, give me a ping when you've sent them out and i'll make sure they get approved
[20:55] <knome> flocculant, and for sanity, please send multiple files with the same mail when same submitter :P
[20:55] <flocculant> knome: I'll do a real draft of one on the pad first
[20:55] <knome> just duplicate the appropriate lines
[20:55] <knome> ack
[20:56] <flocculant> knome: yea - I had fully intended to only send one mail when I could :)
[20:56] <Unit193> pavlushka: It's not really a big deal, sleep, it'll still be there tomorrow.
[20:56] <knome> i'm watching a series, but i'm responsive (i can pause easily)
[20:56] <flocculant> okey doke
[20:56] <pavlushka> feeling sleepy, Good night guys!
[21:02] <flocculant> knome: this link? https://creativecommons.org/licenses/by/3.0/
[21:02] <knome> mhm
[21:02] <knome> sorry, could have dug it up
[21:04] <flocculant> np
[21:04] <flocculant> knome: check the pad please
[21:05] <knome> flocculant, let's not use the url at all
[21:05] <flocculant> submission one
[21:05] <knome> see pad
[21:05] <flocculant> I am :)
[21:05] <knome> because the url is gone in a few weeks
[21:06] <knome> flocculant, ah, you're right
[21:07] <knome> let me see the naming convention
[21:07] <knome> i mean
[21:07] <flocculant> http://contest.xubuntu.org/wp-content/uploads/2016/03/squirreledit-600x375.jpg
[21:07] <knome> let's use a name that will be the final name *in the package*
[21:07] <knome> well
[21:07] <knome> right
[21:07] <knome> maybe you are right indeed
[21:07] <flocculant> actually that's not the case  rename
[21:07] <flocculant> re name
[21:07] <flocculant> it's called
[21:08] <knome> this is indeed best
[21:08] <knome> (in pad)
[21:08] <flocculant> home/wolf/blah :p
[21:08] <knome> so basically you want to remove -xxx-xxx from the filename
[21:08] <flocculant> yup
[21:08] <flocculant> ok - cool - thanks
[21:08] <knome> yeah, you're absolutely right, it makes most sense this way
[21:08] <knome> my bad :P
[21:09] <knome> also
[21:09] <flocculant> ok - I'll go with that now
[21:09] <knome> no!
[21:09] <knome> :P
[21:09] <knome> the () stuff in attribution and name of work
[21:09] <knome> are intended to be sent to recipients
[21:10] <flocculant> what?
[21:10] <knome> see pad again
[21:11] <knome> maybe we can group the lines better
[21:11] <flocculant> yea - the submission bit makes sense
[21:11] <knome> it makes for attribution too
[21:11] <knome> if you look at the winning submissiond
[21:11] <flocculant> the attribution one is just what they said in the first place
[21:11] <knome> for one of them, the author clearly misunderstood the attribution field
[21:12] <flocculant> yellowjacket
[21:12] <knome> yeah
[21:12] <flocculant> you mean :)
[21:12] <knome> and since many are "Untitled", we want the author(s) to be able to name their work now
[21:12] <knome> if they want
[21:13] <flocculant> yea that makes more sense now
[21:14] <knome> is your nick "ochosi" on the pad?
[21:14] <knome> :P
[21:14] <flocculant> mine?
[21:14] <knome> oh no
[21:14] <knome> i only saw me and him on the nick list before i refreshed :D
[21:14] <flocculant> :)
[21:15] <knome> yep, i'm fine with that now
[21:15] <flocculant> ok - biab then :)
[21:15] <knome> as long as all the content that is there goes through, the formatting is more or less minutiae
[21:15] <flocculant> yea
[21:16] <flocculant> I'll bold the 'incorrect' line in the one I send out
[21:17] <knome> :D
[21:22] <knome> hahah, in the queue
[21:22] <knome> ;)
[21:29] <knome> flocculant, oops
[21:30] <knome> (nvm)
[21:30] <flocculant> sorry pleia2 - didn't see knome's random line in the middle of the drag and drop ...
[21:30] <knome> that
[21:30] <knome> nvm...
[21:33] <flocculant> ochosi: really the elfenbeint address?
[21:33] <flocculant> knome: ^^ cos he's off doing dad stuff :) - xfce.org address?
[21:34] <knome> flocculant, PM :)
[21:38] <flocculant> knome: mmm so for ones that are sourced from unsplash or something and obviously not photo's on a local drive should we put the source url in the mail?
[21:38] <flocculant> I guess given it's 2 specific people doesn't hurt
[21:39] <knome> i would still attach them the same way as others
[21:39] <knome> we can't depend on unsplash either
[21:39] <flocculant> I will attach thumbnails ofc
[21:39] <knome> right, yeah
[21:39] <knome> you can add the source URL too
[21:39] <knome> indeed
[21:39] <flocculant> Original source of the photo:
[21:40] <flocculant> I'm putting
[21:40] <knome> yup
[21:43] <flocculant> specifically this one - I'll ping ochosi and tell him that perhaps spell it Mountainous
[21:43] <knome> or hilly
[21:44] <knome> :P
[21:44] <flocculant> no really - spillong errir there :)
[21:44] <knome> :)
[21:57] <flocculant> knome: ok - all sent now
[21:57] <knome> and all approved
[21:57] <flocculant> cool
[21:57] <flocculant> ochosi: so really - spelling :)
[21:57] <knome> thanks for taking care
[21:57] <flocculant> welcome
[21:58] <flocculant> I care generally :)
[21:58] <knome> carebears :P
[21:58] <flocculant> next time
[21:58] <flocculant> sooner
[21:58] <flocculant> community voting
[21:58] <flocculant> or I will be cross
[21:58] <knome> i'd like to tweak some terms at least
[21:59] <flocculant> so basically now wait for some to come up with titles at least :p
[21:59] <knome> would be fun to do a winter contest
[21:59] <flocculant> perhaps we could do a mid-cycle one
[21:59] <flocculant> complete with voting ...
[21:59] <knome> would have to be .10..
[21:59] <flocculant> like 17.10
[21:59] <flocculant> yea
[21:59] <knome> yep
[21:59] <knome> or 16.10 ;)
[22:00] <flocculant> yea
[22:00] <knome> 2016 is the 10th anniversary for xubuntu anyway
[22:00] <flocculant> oh well
[22:00] <knome> and lots of other activity
[22:00] <flocculant> then we should for sure do that
[22:00] <knome> yeah
[22:00] <knome> just let's pump up the stuff for june first ;)
[22:01] <flocculant> we have the tool now - no reason why we can't pick it up after that - and get voting end September ish
[22:01] <flocculant> loads of winter Australia pics :D
[22:01] <knome> hahah
[22:01] <knome> indeed
[22:01] <knome> i also have an improved version of the tool
[22:01] <knome> :P
[22:02] <Unit193> knome: I don't like the dev. link in the topic, not a handydandy link to meetings anymore. :(
[22:02] <knome> boo
[22:02] <knome> :)
[22:02] <knome> set up your own channel for meeting topics! (:
[22:03] <Unit193> Pah, riight.  I just won't look at the agenda.  :P
[22:04] <knome> Unit193, just edit and save a blank field
[22:04] <flocculant> knome: seen the mail yet?
[22:04] <knome> flocculant, which one?
[22:04] <Unit193> knome: Eh, can't actually nuke though it seems.
[22:04] <flocculant> Unit193: aah right
[22:04] <Unit193> OK, will do.\
[22:04] <knome> oh
[22:04] <flocculant> knome: the I screwed up attribution one :p
[22:04] <knome> yep
[22:04] <knome> i see it now
[22:04] <knome> good good
[22:04] <knome> i thought so
[22:04] <flocculant> yea :)
[22:04] <flocculant> I'll reply now
[22:05] <knome> approved
[22:05] <Unit193> That's amusing: Last modified: 1970/01/01 00:00 by
[22:05] <knome> Unit193, fun, isn't it!
[22:05] <Unit193> knome: I don't suppose you'd actually put it in the header there?
[22:06] <knome> i guess i did
[22:06] <knome> :)
[22:06] <Unit193> knome: Oh, and looked at the dokuwiki output stuff yet?  And, dokuwiki doesn't do template pages like we used to?
[22:06] <knome> no, haven't
[22:06] <knome> and don't know about template pages
[22:06] <knome> do we need such?
[22:07] <Unit193> Having it on the old wiki was pretty handy, some of us really did stink with meetings more than others.  Still do.
[22:07] <knome> heh
[22:07] <Unit193> Look, not trying to be a pain.
[22:07] <knome> no no, i'm not thinking you are
[22:07] <knome> but isn't the template for the meeting in the output?
[22:08] <flocculant> yes
[22:08] <knome> just copy-paste everything except the full log
[22:08] <knome> and that's it
[22:08] <knome> ...except now that the markup is different and we need to update the output
[22:08] <flocculant> was just about to say that
[22:08] <flocculant> and
[22:08] <flocculant> are we moving meetings *now*
[22:08] <knome> nope
[22:08] <Unit193> > https://wiki.ubuntu.com/Xubuntu/Meetings/Archive/Minutes/ that.
[22:08] <flocculant> oh good
[22:09] <knome> but rather sooner than later, once the output stuff is fixed
[22:09] <flocculant> knome: I thought we were moving the archive meeting stuff too?
[22:09] <flocculant> Unit193: doesn't that just get the name right?
[22:09] <knome> Unit193, right, that's just the "pick a page name" stuff :P
[22:09] <knome> haha, it's echoing
[22:09] <flocculant> ing
[22:09] <flocculant> ing
[22:10] <flocculant> in
[22:10] <flocculant> g
[22:10] <knome> flocculant, i'm not completely sure
[22:10] <knome> flocculant, it's possible too
[22:10] <knome> but not worth it before the new meeting minutes are in the wiki
[22:10] <flocculant> knome: just seems a bit pants to not
[22:10] <flocculant> or don't move them
[22:10] <flocculant> like release notes
[22:10] <knome> yep
[22:11] <flocculant> which might be changing post xenial ...
[22:11] <knome> yep
[22:11] <knome> ep
[22:11] <knome> eo
[22:11] <flocculant> well
[22:11] <knome> ep
[22:11] <knome> p
[22:11] <knome> p
[22:11] <knome> p
[22:11] <knome> *
[22:11] <knome> .
[22:11] <knome> .
[22:11] <flocculant> s/might/will
[22:11] <flocculant> :)
[22:11] <knome>
[22:12] <flocculant> then might change back post post xenial
[22:13] <Unit193> https://www.dokuwiki.org/plugin:commentsyntax that's not default? :(
[22:13] <knome> actually # comments should work automatically
[22:13] <flocculant> knome: oh yea - wiki - so when I asked you earlier about copying and it said page existed - perhaps it should say "possibly the page exists if a draft gets used' cos I must have almost done it previously
[22:14] <knome> hmm
[22:14] <flocculant> and then not actually saved the page
[22:14] <flocculant> but that's ubuntu wiki not our one ofc
[22:14] <knome> oh right
[22:14] <knome> the ubuntu wiki might say a page exists if it's deleted before
[22:14] <knome> and then you can't copy to that spot anyway
[22:14] <flocculant> I scratched my head - then just *meh* copy paste it
[22:14] <knome> because essentially it exists in the database
[22:15] <knome> just not for the user
[22:15] <flocculant> yep
[22:15] <knome> until you go see the history
[22:15] <knome> it's a bit weird indeed..
[22:15] <flocculant> :)
[22:20] <flocculant> studio have a really comprehensive iso testing wiki page - https://wiki.ubuntu.com/UbuntuStudio/Testing/ISOTesting
[22:20] <flocculant> might do similar at our wiki for us - with the ubuntu one - no real control over content
[22:20] <flocculant> nice to link for testers when they start
[22:21] <knome> flocculant, or contributor docs?
[22:21] <flocculant> would be a ballsache on there I thought
[22:21] <knome> hahah
[22:21] <flocculant> that was in fact my first thought
[22:22] <flocculant> would be better on wiki
[22:23] <flocculant> could really be a couple of pages
[22:23] <flocculant> and wiki changes are ofc immediate
[22:23] <knome> wfm
[22:26] <flocculant> might try and dragoon akxwi :)
[22:30] <Unit193> Since I think people should put their names when adding something to the agenda, I don't like adding things if I won't be there to talk about it (I find that quite annoying when running meetings.)
[22:31] <knome> Unit193, agree
[22:32] <Unit193> However, Sean is running it and knows more than I do about Snappy.
[22:32] <flocculant> I agree too
[22:33] <flocculant> I do try and remove things when I have added them
[22:33] <flocculant> and will miss meeting
[22:33] <knome> leaving them if they need to be discussed is imo ok even if you miss the meeting as long as your nick is there
[22:34] <knome> because then it can be skipped quickly if you aren't around and nobody else knows what it's about
[22:34] <flocculant> add it to 'Discussion' (nick/topic)
[22:34] <flocculant> I can't imagine anyone saying it's a bad idea
[22:34] <knome> nope
[22:35] <flocculant> Unit193: you could for instance do Snappy ( bluesabre/ Unit193)
[22:35] <flocculant> and then ask bluesabre if he's going to be there :D
[22:35] <knome> so bluesabre is the nick and Unit193 is the topic?
[22:36] <knome> :P
[22:36] <flocculant> oh my
[22:36] <knome> AHAHAHA
[22:36]  * knome laughs uncontrollably
[22:36]  * flocculant adds krytarik to all topics
[22:36] <Unit193> flocculant: He's running it, and I'm certain I won't be there. :P
[22:36] <flocculant> Unit193: I knew that :)
[22:36] <Unit193> knome: Nah, he doesn't want to talk about me.  And I mean he specifically doesn't! :D
[22:36] <knome> if we do some nick/topic stuff, then we could also put it in a table
[22:37] <knome> easier to read and prettier
[22:37] <flocculant> knome: works - worked for FC agenda
[22:37] <knome> and not so much worse in the markup that it would mean anything
[22:37] <flocculant> sometimes simple is best
[22:37] <Unit193> Except, I'm not logged in...
[22:37] <flocculant> oh right
[22:38] <knome> Unit193, ha :P
[22:38] <flocculant> Unit193: we'll see you in an hour ish then :p
[22:38] <flocculant> though - it has been pretty responsive lately
[22:39] <knome> must have been the xubuntu stuff that was slowing it down then
[22:39] <flocculant> ha ha
[22:39] <knome> now if only one more flavor leaves, it's ok for the rest of the teams
[22:39] <Unit193> Nope, I'm still waiting.
[22:40] <Unit193> Oh right, and tadaaa.  New core.
[22:40] <flocculant> \o/
[22:40] <flocculant> Unit193: real one?
[22:40] <flocculant> like for the tracker?
[22:41] <Unit193> flocculant: No, only the one that hardly matters. :/
[22:42] <flocculant> now now old chap
[22:42] <flocculant> it matters :)
[22:42] <flocculant> we just can't get it sorted out
[22:45] <Unit193> Well, it is unofficial, so really.  It'll be nice when I don't have to do that too. :P
[22:46] <flocculant> yea ofc
[22:46] <flocculant> it'll be a good day
[22:46] <Unit193> Also the official stamp would go great on it. :3
[22:47] <flocculant> I guess we should let release have a few days off - then really try and get it done for .1
[22:47] <Unit193> Point releases are harder anyway.
[22:48] <Unit193> Oh, remembered the wiki, and: Reason: Error reading from remote server
[22:48] <Unit193> Can someone else add it?
[22:48] <flocculant> Unit193: sanppy?
[22:49] <knome> sanppy indeed
[22:49] <knome> and croe
[22:49] <flocculant> cron?
[22:49] <Unit193> flocculant: That or 'Seeding Snappy'
[22:49] <Unit193> But, that one covers more just in case.
[22:51] <flocculant> anything else while I'm managing to edit?
[22:51] <Unit193> Can't think of anything, so hope not.  Oooh!  Nuke that core one. >_>
[22:51] <Unit193> :P
[22:53] <flocculant> done
[22:53] <Unit193> flocculant: BTW, they said they've done a lot of internal QA, and it'd mainly just be adding ubuntu-snappy-cli (26MB on Xubuntu) so that when a user installs a snap from gnome-software, it's actually able to run.  That's the base platform for running them.
[22:54] <flocculant> good job we let gs in then
[22:54] <Unit193> Also, the "rebranding" thing, that's just "Hey, 'Software' isn't very descriptive, maybe we should call it 'Ubuntu Software' or something slightly better."  Heh, well yes, presuming we want to support snaps OOTB.
[22:55] <flocculant> at least it won't be leaving dependencies around either :p
[22:55] <Unit193> Right, snaps are self-contained, literally.  They're in a squashfs. :P
[22:55] <flocculant> assuming I understand these snaps properly
[22:55] <flocculant> aah cool - so I did \o/
[22:55] <Unit193> I wondered how large each one was, then.
[22:55] <Unit193> flocculant: Yep, bundled libs and all in one file, basically. :P
[22:55] <flocculant> love to see an amarok snap ...
[22:56] <flocculant> if nothing else I wouldn't need to copy the list of stuff I installed for it :)
[22:57] <Unit193> I don't really care all *that* much either way, but I'm leaning towards "Eh, lets not seed it."
[22:57] <flocculant> well I am in the awesome position
[22:57] <flocculant> do I need to qa this? no - *shrug*
[22:58] <Unit193> But if we did, a recommend only in desktop. :P
[22:59] <knome> pleia2, social media time!
[22:59] <knome> pleia2, i see you're not idle, no hiding!
[22:59] <pleia2> I haz working
[22:59] <pleia2> but can publish now
[22:59] <knome> yup
[23:00] <flocculant> pleia2: evening
[23:00] <knome> so color schemes
[23:00] <knome> what
[23:00] <knome> wp says word count 0
[23:00] <pleia2> sometimes computers are less good at counting
[23:00] <knome> :|
[23:00] <knome> it doesn't show any content either
[23:01] <knome> there it is
[23:01] <knome> just being very wonky apparently
[23:01] <knome> well now it isn't there...
[23:01] <knome> sigh
[23:02] <knome> loading without js works
[23:02] <knome> ok, https://xubuntu.org/news/small-details-text-editor-terminal-color-schemes/ is out
[23:02] <knome> tweeting next
[23:02] <flocculant> thanks knome :)
[23:03] <flocculant> 2 nice series of posts these imo
[23:03] <knome> yep
[23:03] <knome> now we only need to write the two last articles for the other :D
[23:04] <knome> flocculant, did the mugshot situation clear up?
[23:04] <flocculant> lost track
[23:04] <flocculant> ummm
[23:04] <flocculant> situation ?
[23:04] <knome> i mean, the personal info integration article is schedule for monday
[23:04] <flocculant> oh right
[23:04] <knome> you wanted to postpone it because something something something
[23:05] <pleia2> g+ and fb done
[23:05] <pleia2> back2work
[23:05] <knome> pleia2, thanks, hf!
[23:05]  * pleia2 picks up crowbar
[23:05] <flocculant> afaik - a 'user' with no admin rights can only do a small section of mugshot changes
[23:05] <Unit193> She's going to give someone a headache..
[23:05] <knome> right
[23:05] <knome> Unit193, or maybe the ballache flocculant mentioned earlier
[23:06] <flocculant> Unit193: ot leg or arm
[23:06] <flocculant> knome: oooh :(
[23:06]  * knome giggles
[23:06] <knome> IT'S SO FLUFFY!
[23:06] <flocculant> bluesabre: are we stopped now with the mugshot for 'user' changes?
[23:10] <knome> so of the planned articles, we still need to write one about wallpaper stuffz
[23:10] <flocculant> mmm
[23:10] <knome> and then we have whole release week empty if we want to prod one in on monday for example
[23:11] <flocculant> glad you have release week open ...
[23:11] <knome> on release week tuesday we will publish the last article about media managers though
[23:11] <flocculant> there is a release announcement to do
[23:11] <flocculant> there is release testing to do
[23:11] <knome> yep..
[23:11] <knome> ack
[23:11] <flocculant> there is release panics to do
[23:11] <flocculant> :)
[23:11] <knome> all panic is slightly better if there's more of it
[23:12] <knome> gives a nice feeling of accomplishment too
[23:12] <flocculant> I think that the wallpaper stuff should show *just* before release week
[23:12] <knome> actually,
[23:12] <knome> here's an idea
[23:12] <flocculant> liek Monday or something
[23:12] <knome> let's bundle it with the contest results
[23:13] <knome> (well, testers can see it in dailies, but who cares)
[23:13] <knome> so it could be release week monday for that
[23:13] <knome> and something else for next weeks friday
[23:13] <knome> two ideas not yet used are
[23:13] <flocculant> works for me
[23:13] <knome> - presentation mode (which is useful btw)
[23:13] <flocculant> might be
[23:13] <knome> - workspace stuff (no specific idea)
[23:13] <flocculant> I'm kind of going to go a bit quiet in a week or so
[23:14] <flocculant> about non-qa stuff that is ;)
[23:14] <knome> heh
[23:14] <knome> i'd hope the articles for next weeks publishing would be ready at latest early next week
[23:14] <knome> (except monday, which should be ready before.. monday9
[23:14] <flocculant> I'd really like us to be a bit quiet on 'things' by next Friday
[23:15] <knome> what "things"? :)
[23:15] <flocculant> we can big it up on Thursday in 2 weeks
[23:15] <flocculant> anything
[23:15] <knome> err, are you saying you don't want any articles next week?
[23:15] <flocculant> I'd like the social stuff to be testing loud once we hit *next* weekend
[23:15] <flocculant> no no no
[23:15] <knome> :D
[23:16] <flocculant> by the Friday latest
[23:16] <knome> right, yeah
[23:16] <knome> so let's recap
[23:16] <knome> next week:
[23:16] <flocculant> let's put a date on it :)
[23:16] <knome> monday: small details article
[23:16] <knome> tuesday: media manager article
[23:16] <knome> wed: small details
[23:16] <knome> thu:
[23:16] <knome> fri: small details
[23:16] <knome> weekend off
[23:16] <knome> then the week after:
[23:17] <knome> mon: small details/wallpaper contest
[23:17] <knome> tue: media manager
[23:17] <flocculant> after the 15th nothing unless I ack it
[23:17] <knome> and after that, everything is open
[23:17] <knome> or we can just announce the wallpaper stuff on friday
[23:17] <knome> and leave the release week open except the media manager article
[23:17] <flocculant> not too worried about the days - JUST that date :)
[23:18] <knome> mhm
[23:18] <knome> the original schedule for the media manager articles was one week earlier, but that didn't work out
[23:18] <knome> the idea was to keep release week quiet indeed
[23:19] <flocculant> I'm going to be really pissed if we are warbling about some *thing* when I am desperately trying to drum up testers
[23:19] <knome> yep
[23:19] <knome> do you have a schedule planned?
[23:19] <flocculant> yea I realise the article schedule slipped
[23:19] <knome> only for media manager stuff
[23:20] <knome> lots of wiggle room for the details since we decided to publish as many as three articles out per week
[23:20] <flocculant> knome: I need to try and sit down this week and sort out upgrades/install testing and some sort of order
[23:20] <knome> ack
[23:20] <flocculant> and ofc - respins will be an unknown quantity
[23:20] <knome> when you know better, poke me and we'll see what kind of publicity stunts we do and when
[23:21] <knome> then intertwine everything
[23:21] <flocculant> so planning is a bit of a misnomer :)
[23:21] <flocculant> yea
[23:21] <knome> (ultimately (and unfortunately) i think the target audiences for the testing stuff and the article series are a bit different though)
[23:21] <flocculant> yea ofc they are
[23:21] <flocculant> totally understand that
[23:21] <flocculant> but
[23:22] <flocculant> not something we can sensibly share stage on
[23:22] <knome> indeed
[23:22] <flocculant> release has to take precedence here
[23:22] <knome> the article series are nice, and probably have more audience, but i agree that testing stuff should have more publicity
[23:22] <flocculant> let me look up at backlog a bit
[23:22] <knome> we can even coordinate something like twice a day
[23:22] <knome> for testing, that is
[23:22] <knome> to try to target EU and US people
[23:23] <flocculant> yup
[23:24] <flocculant> so there are panels/mugshot not published?
[23:25] <flocculant> knome: ^^ unwritten ones?
[23:26] <flocculant> cos I'm confused with what's not published and your list above ...
[23:26] <flocculant> wallpaper is missing is all
[23:30] <knome> yes
[23:31] <knome> the wiki isn't up-to-date
[23:31] <knome> sorry for that :P
[23:32] <flocculant> was lookign on wordpress actually :)
[23:32] <knome> oh
[23:32] <knome> anyway, yeah, wallpaper is only one missing
[23:51] <flocculant> so actually 2 and that to get in
[23:51] <bluesabre> evening all
[23:52] <knome> flocculant, ack, UNLESS we want more
[23:52] <flocculant> knome: can we do the 2 next week - then nothing till release day?
[23:52] <bluesabre> flocculant: re: wallpapers, Sunday latest I'd say
[23:52] <flocculant> wallpaper on release day sounds to me
[23:52] <bluesabre> Unit193: no progress on Thunar, maybe this weekend
[23:53] <flocculant> bluesabre: right that's what we said in the end - you'll see the mail :p
[23:53] <bluesabre> flocculant: changes to mugshot are done
[23:53] <knome> flocculant, everything else is already next week except that one media manager article
[23:53] <flocculant> knome: cloud?
[23:53] <flocculant> leave it there :p
[23:53] <bluesabre> flocculant: might have a change to menulibre over the weekend
[23:53] <bluesabre> just a fix ofc
[23:53] <flocculant> bluesabre: ok
[23:54] <knome> cloud is next week, "other options" is last week
[23:54] <knome> or we can flip
[23:54] <knome> but cloud is closer to being ready :P
[23:55] <flocculant> bluesabre: I'm going to aim to get release notes up to date by weekend end - would be awesome if you can find time to look, then I can just update that as things fall in
[23:55] <bluesabre> flocculant: will do, just ping again as my memory will be reset when i go to sleep tonight :D
[23:55] <flocculant> knome: mmm - I really want testing to take precedence in the final 7 days
[23:55] <knome> flocculant, i understand
[23:56] <flocculant> bluesabre: oh crap - so who'll remind me to do it :p
[23:56] <bluesabre> :D
[23:56] <knome> flocculant, so you'd want to move the wallpaper stuff to release day?
[23:56] <flocculant> well
[23:56] <flocculant> I'd like that
[23:57] <knome> oki
[23:57] <knome> fortunately we have time to think about that:)
[23:57] <flocculant> unless the previous weekend at very latest
[23:57] <bluesabre> anything else needed from me currently? Friday nights are my chill nights :D
[23:57] <knome> this next/last/previous thing is getting confusing
[23:57] <flocculant> I think I can get bluesabre to back me up on not filling social media up with pretty stuff when we really want to get as much testing done as possible :p
[23:58] <bluesabre> pretty stuff and get us more testers at the same time
[23:58] <flocculant> knome: hang on - let's get bluesabre to agree with me and I'll give you dates :p
[23:58] <knome> lol
[23:58] <bluesabre> lol
[23:58] <flocculant> bluesabre: ha
[23:58] <knome> actually i'm really close to going to bed :P
[23:58] <knome> but maybe if you're quick..
[23:59] <flocculant> knome: up to the 15th/16th I don't care :)
[23:59] <bluesabre> I'm flexible, just let me know what to do
[23:59] <knome> yep, i got that
[23:59] <flocculant> after that ask perhaps :)
[23:59] <knome> bluesabre, sit!
[23:59] <knome> bluesabre, beg!
[23:59] <flocculant> ha
[23:59] <bluesabre> fix thunar for meeeee!
[23:59] <knome> bluesabre, paw!
[23:59]  * bluesabre begs
[23:59] <flocculant> ha ha ha
[23:59] <flocculant> I wish I could


[01:56] <mhall119> mfisch: with the new powed, my nexus 7 has a tendency to auto-suspend and then never wake up again
[01:57] <mhall119> :(
[01:57] <mhall119> quite inconvenient
[02:08] <goddard> is there any support for ubuntu touch on a galaxy nexus CDMA?
[02:16] <mhall119> !devices > goddard
[02:17] <mhall119> darn, I always do the wrong one
[02:17] <mhall119> !devices | goddard
[02:20] <mhall119> I don't think anybody has it working on the CDMA version
[02:21] <dank101> hopkinskong, Why hello
[02:21] <mhall119> goddard: http://forum.xda-developers.com/forumdisplay.php?f=1455 might be of interest to you though
[02:22] <mhall119> sorry, http://forum.xda-developers.com/showthread.php?t=2159515 is more specific
[02:26] <slangasek> asac, ogra_: "archive size and mirror complaints" --> "not justifiable in terms of the download usage actually seen, vs. the hit the mirror network would take by the size increase reducing the pool of available mirrors"
[02:27] <dank101> is hopkinskong afk?
[02:27] <dank101> i was going to help him with the HD2
[02:44] <dank101> help
[02:45] <dank101> when i try to build to ubuntu-platform-api package it fails to build
[02:45] <RehpotsirhC> Anyone know how I can get past the error You must specify VARIANT_DEFCONFIG !?
[02:46] <dank101> http://pastebin.ubuntu.com/5708800/
[03:01] <dank101> anyone
[03:13] <goddard> mhall119: thanks
[03:26] <dank101> anyone
[03:50] <dank101> Anyone?
[04:00] <RehpotsirhC> Is it possible to only build the ubuntu portion of touch and use the latest dev version of CM?
[04:25] <rem> hi
[04:26] <remrem> hi
[06:52] <mardy> mhall119: this is the bug blocking dconf-qt: https://bugreports.qt-project.org/browse/QTBUG-31226
[07:22] <dholbach> good morning
[07:59] <jussi> anyone about?
[08:04] <tsdgeos> jussi: i'm around, if that makes you feel un-lonely :-)
[08:04] <seb128> jussi, hey
[08:04] <jussi> wow, people :)
[08:04] <jussi> so
[08:05] <jussi> I have an issue.
[08:05] <jussi> http://paste.ubuntu.com/5709349/
[08:05] <jussi> any help is really appreciated :=)
[08:06] <jussi> Its on a nexus 4, I had ubuntu touch, went back to android, then now trying to get ubuntu again
[08:06] <tsdgeos> adbd cannot run as root in production builds
[08:06] <tsdgeos> yes
[08:06] <tsdgeos> i had that
[08:07] <tsdgeos> jussi: did you do the -b in phablet-flash?
[08:07] <jussi> no, let me try that again
[08:07] <tsdgeos> actually it's Mirv's answer in askubuntu.com/questions/264726/adbd-cannot-run-as-root-in-production-builds :D
[08:09] <jussi> tsdgeos: ahh, my googling didnt turn up much, probably bad technique.
[08:09]  * jussi waits for the download to happen
[08:14] <Mirv> if it helps, please vote my answer up in askubuntu :) I also didn't manage to google a simple answer, so when I eventually re-read the instructions and understood what I was doing wrong, I added the answer
[08:14] <Mirv> the error message alone isn't helping much
[08:32] <jussi> Mirv: it did help :) thanks to you and tsdgeos.
[08:33] <jussi> Mirv: however, do you know if sim unlocking is supported? and if so, how do I enter my pin ?
[08:48] <Mirv> jussi: no, I don't know if it pin code asking should be disabled or not
[08:48] <kengyu> anyone knows how to build the Ubuntu Touch rootfs (ubuntu-touch-raring-armhf.tar.gz) ?
[08:48] <jussi> Mirv: doesnt seem to work here. Where should I report bugs?
[08:49] <Mirv> jussi: possibly https://bugs.launchpad.net/phone-app ... it would be lower level as well, but maybe the phone-app would be the one to have the UI to enter the code
[08:49] <Mirv> someone else might know better
[08:51] <jussi> right, Ill report there and hope that the triager knows better than me.
[08:54] <johba> i'm trying manual installation of ubuntu on nexus 10 like here: https://wiki.ubuntu.com/Touch/Install?action=show&redirect=TouchInstallProcess#Step_4_-_Deploying_Image_to_Device
[08:55] <johba> after copying and rebooting with adb reboot recovery, the tablet is back into android
[08:55] <johba> what am i doing wrong?
[09:14] <Mirv> johba: I'm not that familiar with the manual installation method, but what about just the more automated 'phablet-flash -b'?
[09:14] <Mirv> after having used that so that I had the default image up and running, I was able to use the manual installation method to push a image of my own selection
[09:17] <mindhormone> hi
[09:18] <mindhormone> can i install ubuntu touch on Samsung galaxy S-7562?
[09:24] <nerochiaro> tmoenicke: can you please join #ubuntu-app-devel and set autojoin ?
[10:07] <brendand> it looks to me like touchpad's used to have a 'Touch mode' attribute in xinput --list, but now they don't?
[10:07] <brendand> but touchscreens still do
[10:20] <mqxy> is 2g and 3g working on galaxy s2 in ubuntu touch
[10:22] <mqxy> ???
[10:27] <Aditi> Hi
[10:27] <Aditi> Does anyone know the boot time for Ubuntu?
[10:33] <sergiusens> jussi: Mirv sim unlocking is not supported
[10:34] <jussi> sergiusens: ok, thanks. can it be done from the commandline or do i need to go find someone with a phone that takes micro sims..
[10:34] <sergiusens> jussi: it's in the release notes btw https://wiki.ubuntu.com/Touch/ReleaseNotes#Telephony
[10:36] <sergiusens> jussi: the rilmodem/ofono part is not yet implemented, so it falls into using a different phone or reflashing android and unlocking it
[10:50] <ybon> Any one knows if Ubuntu Touch will be ready for http://www.fairphone.com/ ?
[10:55]  * ogra_ noticers that rsalveti's last merge has a completely wrong number in the mail LP sent
[10:57] <ogra_> ah, it is two times the same MP in succession
[11:40] <hopkinskong_w8> ah
[12:16] <dholbach> sergiusens, rsalveti: hey! how are you doing? when in the cycle do you think we're moving touch to saucy?
[12:18] <ogra_> dholbach, once we have https://blueprints.launchpad.net/ubuntu/+spec/client-1303-containers-host-client-ubuntu-android mostly implemented
[12:18] <ogra_> (hopefully by end of the week we have images with flipped container ... then we still need to weed out the bugs caused by the model flip)
[12:19] <dholbach> great
[12:20] <pmcgowan> dholbach, there are builds now for saucy if anyone wants to testthem
[12:21] <ogra_> pmcgowan, you really dont want to use them the next two-three days
[12:21] <ogra_> i'm actively shuffling bits around
[12:22] <ogra_> (you would end up with a container in a container in a container in a ...
[12:22] <ogra_> )
[12:22] <ogra_> (if you would use them with the current install)
[12:22] <pmcgowan> ogra_, ack
[12:28] <dholbach> cool - just wanted to hear back how things are going as it was mentioned in another conversation somewhere - no worries :)
[12:37] <ogra_> sergiusens, do you know what ships the udev.override file in the touch images ? is that in mountall as well ?
[12:38] <ogra_> ah, ubuntu-session apparently
[12:42]  * ogra_ drops the hacked mountalll from saucy  images
[13:18] <harrisr> is ubuntu available on galaxy tab 2 10.1
[13:19] <timp> harrisr: seems like it https://wiki.ubuntu.com/Touch/Devices
[13:20] <harrisr> is it easy to install and will it void my warrenty
[13:22] <timp> harrisr: sorry, I don't know much about that. Install instructions are included on the wifi, but I  have no idea about the warranty
[13:23] <harrisr> when will ubuntu touch be fully out
[13:24] <harrisr> to the public
[13:24] <ogra_> in october
[13:24] <bfiller> sergiusens: any way to make the user backup script save the current timezone?
[13:24] <ogra_> you should be able to start dogfooding by end of this month though
[13:25] <diwic> ogra_, good job on the container switch stuff, sounds complex :-) Do you know if it has reached the daily images yet?
[13:26] <harrisr> ok ty
[13:26] <ogra_> diwic, it wont go into raring, and saucy is in flux (i should have them ready by end of the week with some luck)
[13:26] <ogra_> diwic, i wouldnt recommend using the saucy image while i do the switch though
[13:27] <diwic> ogra_, okay, so the "dogfooding project", will that be done on raring or saucy?
[13:27] <ogra_> both hopefully ... but we wont switch to saucy until the container flip is done
[13:28] <ogra_> and then there will still be bugs in userspace caused by the flip
[13:28] <diwic> ogra_, thanks for the update. The audio stuff is partially blocked by the container flip, so just curious.
[13:29] <ogra_> we have all pieces ready just not all of them implemented yet, by friday i should be able to point you to some install instructions
[13:30] <diwic> ogra_, yeah, no worries. I have other stuff to do too :-)
[13:30] <ogra_> good :)
[13:36] <sergiusens> bfiller: yes, I was adding that to the build
[13:36] <sergiusens> ogra_: overrides are in lp:session-manager
[13:36] <ogra_> yeah, found them
[13:36] <sergiusens> ack
[13:36] <ogra_> we need to drop that for saucy
[13:37] <bfiller> sergiusens: there was a good post on the mailing list about doing that
[13:37] <bfiller> would be helpful
[13:37] <ogra_> i removed mountall already
[13:38] <rsalveti> hopefully after the flip we can remove all overrides
[13:38] <ogra_> well, we should remove them now :)
[13:38] <ogra_> i'm in the middle of the flip with the saucy images already
[13:39] <ogra_> (if livecd-rootfs shows ever up in the archive i can move on)
[13:39] <ogra_> mountall is already gone
[13:39] <ogra_> udev needs to be next
[13:40]  * ogra_ adds android-tools-adbd to the seeds
[13:46] <Saviq> dpm, question: are we supposed to update the .po files ourselves or just the .pot file and LP will take care of the rest?
[13:48] <dpm> Saviq, you should only worry about updating the .pot file and committing it to the branch whenever there are new strings or before a release. Launchpad will then take care of all the rest
[13:49] <Saviq> dpm, yup, great, thanks
[13:49] <dpm> no ;)
[13:49] <dpm> argh, *np
[13:51] <timp> dpm: can launchpad automatically create the .pot from the source files?
[13:53] <dpm> timp, it can, but only for autotools + intltool based projects. It can do it for them because the rules for gettext are pretty standard there, but it cannot do the setup detection for cmake or qmake projects because the gettext support there is more...
[13:53] <dpm> freestyle :)
[13:55] <timp> ok
[14:00] <kalikiana> dpm, technically speaking that sounds unconvincing. transifex can create pot files for non-autotools projects as well
[14:00] <mfisch> mhall119: file a bug and attach /var/log/upstart/powerd.log
[14:02] <dpm> kalikiana, right, Launchpad has other considerations than Transifex. I don't know how they do it, but that's rather for the LP developers and architects to discuss, not me :)
[14:03] <mhall119> mfisch: I've re-flashed it, I will if it happens again
[14:03] <kalikiana> dpm, sure, just saying that it sounds more like a digestible phrase than a technical reasoning
[14:04] <kalikiana> dpm, and I have an inner itch against doing things manual on a "dont forget" basis ;-)
[14:07] <dpm> kalikiana, right, I'm pretty certain the LP devs did their homework, assessed what they could do and also had to match the resources they had to what they could achieve. Also the focus was to provide this feature for Ubuntu and message sharing with upstream projects in LP, and the biggest external upstream we had was GNOME, and with adding autotools + intltool POT support nearly all of it was covered
[14:09] <dpm> for other build systems there wasn't the predictability on the rules to use to build POT files. In any case, that's my recollection of the little involmement I had in it, not related to the actual development
[14:10] <dpm> kalikiana, I fully agree with you on not doing things manually, though
[14:12] <kalikiana> dpm, I didn't mean to get into an argument or criticize anyone. just noticed the wording is vague and imho not something to "accept" given today's QA standards
[14:12] <dpm> I'm sure the LP guys would take patches :)
[14:14] <stgraber> ogra_: not sure if you noticed that lxc fails at install time on at least some of the phones, that's because of missing bridge support in the kernel. I'm going to upload a fix to saucy's lxc upstart job to make this non-fatal
[14:15] <ogra_> stgraber, ah, no, i only tested on maguro ...
[14:15] <kalikiana> dpm, a quick stab at the ubuntu wiki suggests it's most likely just a missing command in the debian packaging
[14:15] <ogra_> stgraber, shouldnt we ask the kernel team to set the right options instead ?
[14:15] <kalikiana> dpm, is there a bug open against the ui toolkit?
[14:16] <stgraber> ogra_: well, we don't really need the bridge on the phone as we're using shared networking between the container and the "host"
[14:16] <ogra_> ah, network bridge, ok
[14:16] <dpm> kalikiana, a bug for what?
[14:17] <kalikiana> dpm, missing pot for the ui toolkit, which timp was looking at
[14:17] <kalikiana> I guess it wasn't filed then :-)
[14:18] <dpm> kalikiana, gotcha. Yep, we've been talking about bug 1175724
[14:43] <nerochiaro> om26er: can you explain ckpringle what happens with the camera unit tests when you push the zoom button ? does the launcher come up ? why are they unreliable ?
[14:49] <om26er> nerochiaro, ckpringle if the screen is rotated it pulls out the notification area. while interacting with the slider,
[14:49] <ckpringle> om26er: right but the shell should orientate too
[14:49] <ckpringle> (I know it doesn't yet)
[14:50] <om26er> ckpringle, also in the portrait mode if I try to interact with the slider at times the launcher is pulled out, so have to carefully target the slider
[14:52] <mhall119> in general, the launcher and window switcher could be made smarter, so that it would ignore to-the-edge-and-back movemenet
[14:52] <mhall119> and only respond to swipes that originate from outside
[15:02] <nerochiaro> om26er: is that only if you do it manually or also with autopilot tests ?
[15:03] <salem_> tmoenicke, ping
[15:03] <om26er> nerochiaro, autopilot tests have a different problem, that I think is slider handle being is too small for autopilot, or we are doing something wrong in our tests that the slider handle is not grabbed with autopilot
[15:10] <mhall119> mardy: hey, can you update me on the Trojita work you started on?
[15:13] <mterry> How does an app or Unity know that they are switching from phone to tablet to desktop modes?  Is that signal/API done yet?
[15:13]  * ogra_ doubts that
[15:14] <mterry> ogra_, bummer
[15:14] <ogra_> convergence is 14.04 stuff ... 13.10 is just "make sure to not shoot ourselves in the foot once we'll get there"
[15:14] <nerochiaro> om26er: the slider handle can't be too small, autopilot will position the cursor even on a single pixel
[15:15] <oSoMoN> bfiller: if you wanna give a try to tabs, check out lp:~osomon/webbrowser-app/tabsmodel (disclaimer: it’s ugly and not fully functional yet)
[15:15] <t1mp> mterry: no
[15:15] <t1mp> mterry: that signal/API is not there yet
[15:15] <om26er> nerochiaro, do you have a device?
[15:16] <bfiller> oSoMoN: thanks
[15:16] <nerochiaro> om26er: yes
[15:16] <om26er> nerochiaro, can you try this test there: camera_app.tests.test_zoom.TestCameraZoom.test_slider ?
[15:17] <nerochiaro> om26er: never ran tests on the device
[15:17] <om26er> nerochiaro, right, I reported bug 1179592 if you have a few spare cycles can you please look into that
[15:18] <om26er> nerochiaro, I think that could be a root cause for all the slider related tests failures
[15:18] <oSoMoN> bfiller: note that I haven’t tested on the phone yet, the UI probably looks even uglier there
[15:18] <om26er> that's actually a regression from the time when autopilot tests were disabled in jenkins
[15:21] <bfiller> mfisch: ping
[15:21] <mfisch> bfiller: pong
[15:21] <bfiller> mfisch: build 138 (today's), power button never turning screen back on. you seeing this?
[15:21] <bfiller> on galaxy nexus
[15:22] <mfisch> bfiller: I am not seeing it because I had to reflash back to ufa, let me ping sforshee
[15:22] <sforshee> bfiller, I'll check it out
[15:23] <nerochiaro> om26er: on yesterday's image the +/- buttons appear just fine for me on my device
[15:24] <mfisch> bfiller: mhall119 reported some issues as well
[15:25] <om26er> nerochiaro, that's problematic on desktop, as in the bug report, though you will see mis alignment of the camera view area on devices
[15:28] <mhall119> mfisch: after a phablet-flash and rm -r ~/.local/share, I haven't had the issue again
[15:28] <mhall119> though resuming from suspend is still noticably slower than it was pre-powerd
[15:28] <sforshee> mhall119, there are some changes landing today that should help with the speed
[15:28] <sforshee> at least speed of screen on
[15:29] <mhall119> cool
[15:29] <ogra_> mfisch, are you guys uploading to saucy and copy the binary to raring btw ?
[15:29] <ogra_> i cant get any of the new features to work in saucy apparently
[15:31] <ogra_> (in fact powerd doesnt even start automatically here)
[15:32] <nerochiaro> om26er: let me try on desktop then
[15:32] <om26er> nerochiaro, also see the screenshot on the device, note the right border: http://imagebin.org/index.php?mode=image&id=259334
[15:32] <om26er> that's a regression
[15:32] <mfisch> ogra_: jenkins is uploading for raring, not sure what's going on with saucy, but I'm back on UfA as of today
[15:33] <ogra_> hmm
[15:33] <om26er> nerochiaro, oh and see in my screenshot there is no +/- on the Nexus 4 as well
[15:39] <mfisch> ogra_: Its probable that saucy isn't being updated by jenkins
[15:39] <ogra_> yeah, that should be fixed
[15:42] <kalikiana> mfisch, jenkins is not doing anything at the moment :-)
[15:42] <mfisch> so I hear
[15:42] <ogra_> heh
[15:42] <ogra_> good point
[15:53] <sergiusens> ogra_: powerd releases to whatever is in the changelog
[15:54] <sergiusens> mhall119: ubuntu touch has used powerd since the begining ;-) Just not the auto suspend :-)
[15:54] <ogra_> well, would be good to have all packages in saucy for regressiion testing
[15:54] <sergiusens> mfisch: did you see asac 's MRs? If you are not taking care of it... I might just jump in and work on it
[15:54] <ogra_> i bet we'll have a lot of fun with our stuff and the removal of consolekit in saucy
[15:55] <mhall119> sergiusens: ah,I should be more specific then
[15:55] <ogra_> everything using dbus should be tested against that
[15:55] <sergiusens> ogra_: I can work on an auto copy (already have code for it, jsut need to create a package list)
[15:55] <mfisch> sergiusens: sforshee is on it already
[15:55] <ogra_> ok
[15:55] <sergiusens> mhall119: sorry for being pedantic :-P
[15:55] <sergiusens> mhall119: speaking of which, are we good to add the terminal app?
[15:56] <ajalkane> Terminal app yeeaaaaah! :)
[15:56] <mhall119> sergiusens: as soon as someone reviews the code and gives it a +1
[15:57] <mhall119> as far as I'm concerned we're goot to add it, it's the first thing I do after a phablet-flash
[15:57] <sergiusens> mhall119: ahhh... mzanetti ^^ :-)
[15:57] <mzanetti> huh?
[15:57] <mzanetti> terminal app?
[15:57]  * mzanetti wants now!
[15:57] <mzanetti> awesome :)
[15:57] <sforshee> bfiller, I just flashed today's image to a galaxy nexus and the power button seems to be working
[15:58] <mhall119> mzanetti: it's in the core apps PPA
[15:58] <mhall119> together with a plugin for the terminal widget
[15:58] <mzanetti> mhall119: cool stuff. will it be included in the default image?
[15:59] <mfisch> sergiusens: sforshee has a pending mp that addresses most of asacks changes
[15:59] <mhall119> mzanetti: once it's reviewed by someone on the phablet team
[15:59] <mhall119> mzanetti: sergiusens: https://code.launchpad.net/~mhall119/touch-preview-images/more-coreapps/+merge/164802
[15:59] <pmcgowan> mzanetti, you could review it and approve ;)
[15:59] <mzanetti> mhall119: btw. I've ported yet another app :) one where I don't depend on unreleased Qt modules or unfinished app lifecycles so there are chances I can actually really finish it soon
[15:59] <mzanetti> I'll review, yes
[16:00] <mzanetti> mhall119: fahrplan2. Lets you find trains/busses on the go. supporting DE, DK, FI, AU, AT and some more
[16:00] <mhall119> mzanetti: nice, is it on the collections wiki?
[16:00] <mzanetti> mhall119: not yet
[16:00] <mhall119> https://wiki.ubuntu.com/Touch/Collection
[16:00] <mhall119> if you can add it to the list please
[16:05] <asac> mfisch: will he put it into the mainloop with proper wakelocking to ensure we dont fall asleep?
[16:06] <sforshee> asac, I haven't made changes to move some of the stuff to the mainloop like you did. We could look at that, it just wasn't in the code I had already written.
[16:06] <asac> please look at that unless everything will get thrown away
[16:07] <sforshee> asac, a lot of the display-related code is temporary
[16:08] <ogra_> yeah, surfaceflinger will hopefully be gone soon
[16:08] <asac> sure, so move it into single threading please first
[16:08] <asac> this mutexing is just scary
[16:08] <asac> the looper can be wrapped in a GSource :)
[16:09] <asac> the on_new_event entry point in code is stil the same
[16:09] <asac> so the patch is still very close ... just need to add the wakelocking on top
[16:10] <asac> anyway ... will not look at this code again unless my phone on/off is again not working well :)
[16:10] <asac> which means: snappy and robust :)
[16:11] <sforshee> asac, my changes are approved and just waiting on jenkins to be merged, they make display on/off much better
[16:12] <asac> ok tell me when i will test
[16:12] <asac> but please do the event loop fix
[16:12] <asac> the amount of mutexes you land is really scary :)
[16:12] <asac> solve it in one place will make the thing just more fantastic
[16:12]  * asac shuts up :)
[16:13] <fginther> mhall119, ping
[16:14] <mhall119> fginther: pong
[16:15] <fginther> mhall119, any progress with launchpad ops on armhf builds?
[16:16] <mhall119> let me check in on them
[16:17] <fginther> mhall119, thx
[16:17] <mardy> mhall119: hi! About trojita: http://news.gmane.org/gmane.mail.trojita.general
[16:18] <mardy> mhall119: I just got it started, now Matt Richardson is on it
[16:21] <mhall119> mardy: do you think it's suited for building an email client for Ubuntu Touch?
[16:21] <mardy> mhall119: I think so, or at least it's worth a good try
[16:22] <mardy> mhall119: the code is clean and structured to run on many different UIs
[16:22] <mhall119> cool, thanks mardy
[16:24] <bfiller> sforshee: seems to be timing related, was working mostly now it's not. Any info I can get now that it's in the state to help debug?
[16:25] <sforshee> bfiller, I could take a look at /var/log/upstart/powerd.log
[16:27] <bfiller> sforshee: https://pastebin.canonical.com/91715/
[16:29] <bfiller> sforshee: might be happening when you try to wake it right away after screen goes black, need to try some more
[16:29] <bfiller> sforshee: it's definitely still running but not responding to power button event
[16:29] <sforshee> bfiller, from the log it looks like powerd is still trying to turn the screen on
[16:30] <mfisch> bfiller: if you need a work around, sudo initctl restart powerd, from ssh
[16:31] <bfiller> sforshee: yup, when I press the power button I see this in the log: https://pastebin.canonical.com/91716/
[16:32] <sforshee> bfiller, maybe the backlight is off. What does 'cat /sys/class/backlight/s6e8aa0/brightness' output?
[16:32] <sforshee> try that a few times after pressing the power button and see if it changes
[16:33] <bfiller> sforshee: 0 each time
[16:33] <bfiller> never changes
[16:33] <sforshee> bfiller, that's probably the problem
[16:33] <sforshee> try poking in 255: 'echo 255 > /sys/class/backlight/s6e8aa0/brightness'
[16:33] <bfiller> sforshee: I'm on galayx nexus
[16:33] <sforshee> then see if things are better
[16:34] <bfiller> trying
[16:35] <bfiller> sforshee: yeah that made it work
[16:36] <bfiller> sforshee: arg, but just got it back into the hosed state after playing with it for a while
[16:37] <sforshee> bfiller, be sure you give it 5 seconds after pressing the power button for the screen to come on. There's a problem with that in today's image, which I have a fix for.
[16:38] <bfiller> sforshee: ok
[16:38] <sforshee> bfiller, I was able to reproduce
[16:38] <sforshee> I have a guess as to what's causing this
[16:38] <bfiller> sforshee: shouldn't powerd always set the correct state of backlight? maybe it's already doing this..
[16:39] <sforshee> bfiller, I think it's a race where it may read the "current" backlight value while it's 0, then it will never set it to any other value
[16:39] <sforshee> lp:~sforshee/powerd/display-improvements might fix it if you want to give that a try
[16:40] <sforshee> oh, those changes are on trunk now as well
[16:41] <mhall119> mardy: is there a bzr branch with the trojita stuff in it, or only git?
[16:44] <mardy> mhall119: only git
[16:44] <mhall119> ok
[16:53] <sforshee> asac, bfiller: here's a build with the display changes if you want to test: http://people.canonical.com/~sforshee/powerd_0.10_armhf.deb
[16:56] <bfiller> sforshee: thanks, I'll try
[16:56] <asac> sforshee: is it snappy?
[16:56] <sforshee> asac, yep :-)
[16:56] <asac> good ... if not i will let you know
[16:56] <asac> dont have wget yet :)
[16:58] <ogra_> wget it !
[16:58] <asac> sforshee: screen is flashing more than before for whatever reason
[16:58] <asac> you also should add the cancel event feature i landed on the snappy branch
[16:58] <asac> i think
[16:59] <asac> oh
[16:59] <asac> its again dead :)
[16:59] <asac> not robust !!!
[16:59] <asac> screen stays black :)
[16:59] <ogra_> see above
[16:59] <asac> take the saved_brightness hu nk i guess
[16:59] <asac> from my patch
[17:00] <sforshee> asac, I haven't gotten a chance to go back to your patch and pick out the changes yet
[17:00] <asac> ok
[17:00] <asac> one sec
[17:00] <asac> i till point you directly :)
[17:00] <sforshee> asac, I can't reproduce the black screen anymore, how did you get it?
[17:01] <asac> just rapidly click on and of
[17:01] <asac> f
[17:01] <asac> sometimes change the rhythm
[17:01] <asac> then you get it
[17:01] <asac> it happens if you activate
[17:01] <asac> wait
[17:01] <asac> it happens if you suspend while you activated
[17:01] <asac> but activation didnt happen
[17:01] <asac> then you remember saved_brightness forevetr as 0 :)
[17:02] <asac> sforshee: http://bazaar.launchpad.net/~asac/powerd/fix-racy-screen-on-and-no-mutex-refactor/revision/23
[17:02] <asac> and i think you want  most from here: https://code.launchpad.net/~asac/powerd/snappy-on-off-with-delayed-suspend-cancellation
[17:02] <asac> starting at rev 27
[17:02] <asac> atm the events pile up and get discarded, while they should just get fast pathed if there is a pending event that is in "delayed"
[17:03] <RehpotsirhC> Is there a ubuntu components only repository list so I can build stock CM and integrate the ubuntu components accordingly?
[17:03] <sergiusens> RehpotsirhC: stock CM wouldn't work
[17:03] <ogra_> have you read the porting guide
[17:03] <sforshee> asac, the problem with that is that before long we'll have external clients processing and acknowledging the state changes, and when we can't simply throw it away
[17:03] <ogra_> it's more about removing bits than adding any :)
[17:04] <sergiusens> RehpotsirhC: go over all the commits in phablet.ubuntu.com and you will why
[17:04] <ogra_> (there are only three ubuntu trees in the build)
[17:04] <RehpotsirhC> ogra_, I have. Unfortunately the Phablet-10.1 repositories don't support the new device configurations (mainly jfltecan) and how it separates the def configurations.
[17:04] <sergiusens> ogra_: well, me modified most of the git repos as well (kernel, service manager ring a bell among others)
[17:05] <RehpotsirhC> During compilation it complains about not specifying the variant configuration.
[17:05] <RehpotsirhC> brb
[17:05] <ogra_> oh, right, but even there it is rather removal than addition
[17:05] <sforshee> asac, the backlight fix is sane enough given that long-term the code will be thrown away
[17:10] <asac> right
[17:15] <doanac> asac: looks like you've been patching some code I have a question about :)
[17:15] <asac> doanac: yeah ask me ... i am the only one who knows only half truth here :)
[17:15] <doanac> is there a relatively easy way (shell or python) to request the screen be turned on and left on?
[17:15] <asac> doanac: by whom?
[17:15] <asac> ah by shell or python
[17:15] <doanac> ideally, one of those
[17:16] <asac> we definitely dont want to provide such feature to apps directly, but not sure if that means we could have that in the dbus api
[17:16] <asac> sforshee: ?
[17:16] <doanac> i have a test where I need to drain the battery rapidly. turning the screen on helps accelerate that
[17:17] <sforshee> doanac, powerd-cli active
[17:17] <sforshee> doanac, oh, but that won't keep the screen on
[17:17] <sforshee> no, we don't have that capability currently
[17:17] <doanac> sforshee: yeah, that's what I was seeing last night
[17:18] <doanac> i tried going through sysfs with blank/unblank and brightness stuff, but it just seemed to get things out of whack
[17:18] <sforshee> doanac, the only way would be if mfisch's changes to make the screen timeout configurable has an always-on value, but iirc it does not
[17:19] <doanac> sforshee: so what do you see my most efficient avenue for getting this done is?
[17:19] <mfisch> I think we add a new value and not overload this one
[17:19] <doanac> i can help contribute a patch if needed
[17:20] <sforshee> doanac, feel free to contribute a patch, otherwise I'll add it to my todo list
[17:20] <MadShiva> Hello
[17:20] <doanac> has mfisch's branch landed? or do i need to work off something not merged?
[17:21] <sforshee> it's in powerd trunk
[17:21] <mfisch> yes, in trunk for the setting
[17:21] <doanac> okay.
[17:21] <mfisch> doanac: you need to leave the screen on, or turn it on over and over?
[17:21] <doanac> mfisch: i need to leave the screen on for a while. and then probably let it go back to its default behavior
[17:22] <doanac> mfisch: any tips/pitfalls for testing powerd?
[17:22] <mfisch> doanac: sudo dbus-launch gsettings set com.canonical.powerd activity-timeout 3600
[17:22] <mfisch> doanac: that will keep the screen on for 1 hour
[17:22] <doanac> mfisch: that should work for me
[17:23] <doanac> w/o having to get my hands dirty
[17:23] <mfisch> doanac: you have to reboot the phone or restart powerd after changing that
[17:23] <mfisch> doanac: we're not listening for setting changes currently
[17:23] <MadShiva> I have a small question. I would like to follow the instruction that's on the webpage but it's there some chance that I brick my tablet ?
[17:24] <doanac> thanks guys!
[17:25] <sergiusens> mhall119: just tried the latest terminal app, everything I type is hidden (color wise) until I press enter
[17:25] <mhall119> sergiusens: go to the settings tab and increase the font to 14
[17:25] <mhall119> I'm not sure why, but the font size seems to affect that
[17:25] <mhall119> too big or too small and it won't display it all the time
[17:25] <mhall119> 14 works for me on my nexus 7
[17:27] <dobey> mhall119: hey. do you know if the SDK will be getting shipped into precise-backports or precise-updates at all? or will it only be available as the thing that installs in /opt?
[17:27] <sergiusens> mhall119: 14 onwards works for me on maguro... can we make 14 the default?
[17:28] <mhall119> dobey: it should be available via the PPA, and install to /usr/share/
[17:28] <mhall119> for precise
[17:28] <netcurli> bug #1182503
[17:28] <mhall119> sergiusens: probably, I'll ask zdmitry when he's online
[17:28] <sforshee> asac, bfiller: I updated the package at http://people.canonical.com/~sforshee/powerd_0.10_armhf.deb with the black screen workaround
[17:29] <netcurli> font size 14 does not work for me on my galaxy nexus
[17:29] <dobey> mhall119: are there any plans to ship it in -backports or -updates, rather than just a PPA then?
[17:30] <awe_> sergiusens, approved your MR.  rsalveti, do you want to chime in before I happrove?
[17:30] <rsalveti> awe_: I'm about to test it, I can happrove if you want
[17:31] <rsalveti> awe_: just approve, but not happrove
[17:31] <awe_> that's what I did
[17:31] <sergiusens> thanks guys
[17:31] <rsalveti> awesome
[17:31] <asac> ok let me check
[17:31] <mhall119> dobey: I don't think so, bzoltan1 would know for sure
[17:31] <sergiusens> mhall119: regarding the file manager. It can just list stuff today, right?
[17:31] <bzoltan1> What Should I Know For Sure? :)
[17:31] <mhall119> sergiusens: it can do file operations, copy/rename/delete, etc
[17:32] <asac> sforshee: with your patch i see a flickering regularly still
[17:32] <dobey> bzoltan1: if the sdk packages will ever get shipped in precise-updates or precise-backports
[17:32] <mhall119> opening files may work in theory, but needs platform-level support for making the file open the right external application
[17:32] <sforshee> asac, flickering when?
[17:32] <asac> sforshee: when turning on. i believe i was able to identify that it shows the desktop unlocked for a very brief moment
[17:32] <asac> and then goes to the lock screen
[17:33] <asac> sforshee: when turning on the screen again
[17:33] <bzoltan1> dobey:  We have precise packports of the SDK right now available
[17:33] <asac> sforshee: i just click rapidly on and off
[17:33] <sforshee> asac, which device?
[17:33] <asac> GN
[17:33] <asac> oh ... i was able to see the Videos panel indeed
[17:33] <asac> for a bit longer time now
[17:33] <dobey> bzoltan1: in the PPA yes. i was just wondering if there are plans to get them shipped in the precise archives proper, so people don't have to add a PPA to get it. or if it will only ever be in a PPA for precise
[17:34] <sforshee> asac, I'm not seeing it
[17:34] <asac> oddd... i am sure that for the quick flickers its the Notes
[17:34] <bzoltan1> dobey:  I do not think we will push the SDK packages to Precise
[17:34] <dobey> bzoltan1: ah ok. :-/ thanks.
[17:35] <bzoltan1> dobey: in my opinion Precise users should have the same features from the PPAs... Does the PPA delivery represent any impediment for you?
[17:35] <sforshee> huh, apparently the touchscreen is being left on and is still operating when the screen is off
[17:35] <sforshee> asac, ^ ... could that be causing it?
[17:36] <sergiusens> mhall119: how do you paste after a cut/copy?
[17:36] <bzoltan1> dobey:  supporting Precise is the right thing, since that is the LTS release right now... but to be honest I think developers should use Raring
[17:36] <sergiusens> bzoltan1: devs should use saucy ;-)
[17:36] <mhall119> sergiusens: I think that's not working atm
[17:36] <asac> sforshee: not sure why that would reveal whats behind the lock screen
[17:36] <sergiusens> mhall119: ack
[17:36] <asac> anyway ... my code has the same problem
[17:37] <bzoltan1> sergiusens:  :) you are right
[17:37] <sforshee> asac, because you're accidentally touching something on the left side that's dismissing the lock screen while the screen is off
[17:37] <mhall119> sergiusens: ajalkane may be able to give more detail on what's working and what isn't
[17:37] <asac> sforshee: i doubt it
[17:37] <asac> i am just rapidly clicking on/off
[17:38] <sforshee> that's the only way I've been able to get anything remotely similar to what you describe
[17:38] <asac> yeah .. definitely happens even if fingers are far wayt from screen
[17:38] <sergiusens> awe_: rsalveti https://code.launchpad.net/~sergiusens/touch-preview-images/ubuntu-build-phablet/+merge/166114
[17:38] <dobey> bzoltan1: it means more work in terms of maintenance for the ubuntu one team, since we won't be able to reduce our overhead there by shipping new stuff that depends on qt5, and it means we have to keep some amount of the new stuff working without it, in places where it would be possible to just wholly switch to the new qt5 bits for everything. (iow, we end up with multiple projects which do the same things)
[17:38] <asac> sforshee: maybe its because i run it with messages on ... that might slow stuff down minimally :/
[17:38] <asac> G_MESSAGES_DEBUG=all powerd
[17:38] <asac> try that
[17:38] <sforshee> we always run it that way currently
[17:38] <asac> its not much output... but who knows
[17:38] <sforshee> in the upstart job
[17:39] <ajalkane> sergiusens: after copy/cut you should have in toolbar "Paste" button
[17:39] <dobey> bzoltan1: ie, it would be nice to develop apps on raring, and be able to ship them to precise users without requiring the user to add PPAs to use it (for example, if i develop an app, and want to sell it in software-center)
[17:39] <asac> well, maybe its slower to send it over USB :)
[17:39] <asac> who knows
[17:39] <asac> i run it in ADB in foreground to test
[17:39] <bzoltan1> dobey: why would we ship anything new to Precise what depends on Qt5?
[17:39] <rsalveti> sergiusens: happroved
[17:39] <dobey> bzoltan1: so our users get new features and we don't have to maintain code that's already 1.5 years old, for the next 3.5 years? :)
[17:40] <asac> dunno ... i clearly see it :)
[17:40] <bzoltan1> dobey: backporting qt5 to Precise would sound like we turned Precise to be a rolling release :)
[17:40] <asac> "Notes" ...
[17:40] <asac> interestingly enough the first thing if i slide to the right is the Videos
[17:40] <asac> and the notes app has been closed a while back :)
[17:41] <bzoltan1> dobey:  I am far from being a distro guru... but I consider Precise as a frozen release what receives only serious bug fixes and security updates...
[17:41] <sergiusens> bzoltan1: there were some talks about backporting unity, so Qt5 may not be out of the option
[17:41] <MadShiva> sorry to ask again but what's the risk of brick I really want to port ubuntu touch to my tablet P7300
[17:41] <bzoltan1> dobey:  but please educate me ... I really do not know much about this distro thingy
[17:41] <dobey> bzoltan1: i don't think so. it doesn't break old apps. unlike shipping a new kernel often does :)
[17:42] <mistersprinkles> Does the lastest source still come with preloaded data?
[17:42] <ogra_> it was dropped
[17:42] <bzoltan1> dobey:  do not be so sure :) Qt5 comes with the qtchooser and qt5default duality nightmare ... backpporting qt5 means touching qt5 ... and  for example QtCreator is known to have funny behavior with this duality.
[17:42] <ogra_> (not sure if in todays or tomorrows image though)
[17:43] <bzoltan1> sergiusens: I would not recommend to backport the Unity Next to Precise, but that is not my decision.
[17:43] <sforshee> asac, I do get a white flash when the video app is active
[17:43] <asac> right
[17:43] <asac> guess even after you closed it
[17:43] <asac> you will still see it :)
[17:44] <asac> maybe something to do with framebuffer?
[17:44] <asac> buffering?
[17:44] <sforshee> I don't know that "close" currently means close
[17:44] <sforshee> it may still be running
[17:44] <asac> probably
[17:44] <dobey> bzoltan1: ah true. but were lots of qt4-based things break in raring when we pushed qt5 to it?
[17:44] <asac> :)
[17:44] <asac> well let me check
[17:45] <sforshee> but it goes away for me after closing the app
[17:45] <bzoltan1> dobey:  We did not test all Qt apps, but I remember that it was not a straight forward victory march
[17:45] <asac> sforshee: it killed the process properly here
[17:45] <asac> if i click on the launcher icon and wait till the X appears
[17:45] <asac> so yeah
[17:45] <asac> well.
[17:45] <asac> not for me
[17:45] <asac> the Notes app wasnth running but i was seein git :)
[17:46] <bzoltan1> dobey, sergiusens:  All in all... from the point of Qt5 and Unity Next I would live Precise alone... that is the cheapest and less risky way. But if for some strategical reason we need Qt5 on Precise we can do it ... not impossible and not even too hard. But it comes with risks and does not happen by casting with a magic wand :)
[17:46] <sergiusens> bzoltan1: not unity-next, just unity 7 ;-)
[17:47] <sergiusens> bzoltan1: also, I'm not pushing for it :-)
[17:47]  * sergiusens just mentions the virtual hallway talk he eavesdrops
[17:47] <bzoltan1> sergiusens:  Sorry I was on holiday for few days :) I am not aware of the latest naming trends :)
[17:48] <sergiusens> bzoltan1: unity 7 is the unity in raring, unity 8 is unity-next
[17:48] <dobey> i don't really care about unity 8 (unity next) going on precise :)
[17:48] <bzoltan1> sergiusens: Once an old mentor of my told that everything is possible, you can heat your hous with Stradivarius violins... but it might be a bit expensive :)
[17:49] <dobey> and i wasn't asking for qt5 to be done with a amgic wand. was just asking if there were plans for it to go there (and subsequently quantal if yes), because it makes lots of things much easier for some of us :)
[17:50] <sergiusens> dobey: I would say no, there are no plans
[17:51] <dobey> or, if the qt5 cmake magic integration stuff can work with qt4, i could probably fix this code to be buildable on qt4, and that would work for me too.
[17:52] <sergiusens> Mirv: I did an install of qmlrunner manually on my phone on Friday and it ort of broke (uninstalled most things), it left me with a broken link
[17:55] <bzoltan1> dobey:  I will talk to my people and see how much work it would take to backport the Qt5 and exactly how much risk it would represent ... now that you explained the whole story to me, actually I am getting convinced :D
[17:57] <dobey> bzoltan1: it would be nice for app developers to be able to write apps with the new sdk stuff, and have people running the current LTS to be able to use them, without having to wait another year for an upgrade to the next LTS, yeah :)
[17:58] <dobey> bzoltan1: thanks. :)
[17:58] <bzoltan1> dobey:  With that one I fully agree... but it would mean constant support of the SDK for 4 releases... I try to convice the right people to give me more QA engineers :)
[18:02] <dobey> bzoltan1: well, if it was going to happen, but didn't happen until the sdk was a "1.0" thing, that made some compat guarantee going forward, i'd think that'd be fine.
[18:04] <asac> sforshee: any idea why the battery is charging so slow on GN? do we need to poke something on the battery driver side?
[18:09] <pmcgowan> asac, are you plugged into an outlet? should be fast then, slower on usb
[18:10] <asac> usb
[18:10] <asac> slower than with android before for sure
[18:11] <ogra_> mine is charged after ~2h when connected to the PC
[18:11] <ogra_> surely faster on an outlet
[18:11] <asac> mine is charging 5 hours now
[18:11] <asac> from 5%
[18:11] <asac> to 60%
[18:11] <ogra_> wow
[18:11] <asac> connected to thinkpad in a dock
[18:11] <asac> doc
[18:11] <asac> king
[18:12] <ogra_> stat
[18:12] <ogra_> ion
[18:12] <ogra_> ?
[18:13] <asac> rihgt
[18:13] <asac> argh :)
[18:14] <sergiusens> bzoltan1: how do I prevent qtcreator from creating ssh keys? I'm passed 5 now again and need to add special rules to all my ssh logins or get the too many authentication failures
[18:14] <sergiusens> bzoltan1: can't you do like we do in phablet-network-setup where if there's a id_rsa.pub to just copy it in?
[18:15] <bzoltan1> sergiusens: You are the second person after me who met this issue... I do not like it eaither
[18:16] <bzoltan1> sergiusens:  You are right, that adb pushing the .pub would be a better alternative
[18:16] <bzoltan1> sergiusens:  I am about to EOD, but would you file a bug about it please?
[18:16] <sergiusens> bzoltan1: and if not found, create it :-)
[18:16] <sergiusens> sure
[18:17] <bzoltan1> sergiusens:  thanks...
[18:28] <om26er> mhall119, Do we have plans to rename the core apps or atleast remove 'ubuntu' from the app name ?
[18:32] <mhall119> om26er: yes we do
[18:33] <mhall119> popey and I have a list of things that need to be done to rename them
[18:33] <mhall119> om26er: is there any specific timeframe that we need to get that done by?
[18:33] <mhall119> otherwise it's just been waiting until there wasn't something more important
[18:33] <om26er> mhall119, no, that's not a requirement, just asking
[18:34] <om26er> mhall119, so we remove ubuntu from the name? then ubuntu-calculator-app becomes calculator-app ?
[18:36] <mhall119> yes
[18:37] <mhall119> we'll start with the package name, .desktop and .qml file names
[18:37] <mhall119> then later rename the launchpad team and project
[20:22] <mistersprinkles> The image to flash is only 24MB?
[21:02] <user82> awe_, how are you coming along with the data?
[22:08] <WebbyIT> pmcgowan: hi :) What is tag dogfood? https://bugs.launchpad.net/phone-app/+bugs?field.tag=dogfood
[22:09] <pmcgowan> WebbyIT, it refers to usability issues uncovered as people are using the phone as their primary device
[22:09] <WebbyIT> pmcgowan: ok, thanks :D
[22:09] <pmcgowan> refers to "eating your own dogfood" may not translate
[22:10] <ajalkane> Dogfood is slightly more tasty than fishfood
[22:10] <pmcgowan> now how would you know that
[22:11] <WebbyIT> pmcgowan: yah, in italian we haven't a translation for this
[22:11] <pmcgowan> I need to think more globally
[22:11] <pmcgowan> you think I would by now
[22:12] <ajalkane> I once was a child. And I had fish. I don't want to delve on it more :)
[22:14] <WebbyIT> i think we haven't any idiomatic expression for this, only "use everyday" or something like this...
[22:14] <WebbyIT> ajalkane: i'm sorry for you
[22:14] <WebbyIT> :P
[22:15] <ajalkane> Thank you... I'm sorry for me too, but probably for different reasons