[04:17] <pitti> Good morning
[05:54] <pabloh> Can somebody recommend an lightweight display manager? (I've been using Qingy for a while but it's hard to get it working on some hardware)
[06:12] <RAOF> lightdm? :)
[06:22] <mvo> pitti: good morning! what do you reckon are the chances for https://launchpadlibrarian.net/180534575/gobject-introspection_1.40.0-2ubuntu1_1.40.0-2ubuntu2.diff.gz to go upstream into debian? it seems to work fine from my limited testing, the only issue is that the gir libs need adjusting now in their gir1.2-foo.install file (/usr/lib/girepository-1.0/* -> /usr/lib/*/girepositoriy-1.0/*)
[06:44] <pitti> mvo: for debian, no problem; the hardcoded /usr/lib/girepository-1.0/ is a bit ugly for upstreaming, though
[06:46] <pitti> mvo: I'll commit our changes to Debian
[06:46] <mvo> pitti: hold on a sec
[06:46] <pitti> mvo: err, wait
[06:46] <pitti> mvo: are the typelibs actually platform dependenct?
[06:46] <mvo> pitti: this will cause ftbfs for the packages that build with the new gojbect-introspection
[06:46] <mvo> pitti: the fix is trivial, just updating the install path
[06:46] <pitti> mvo: in any way, this requires a note to ...
[06:46] <pitti> yes
[06:47] <mvo> pitti: if you think thats ok, I'm all for it :)
[06:47] <pitti> ... d|u-devel-announce@ at least, and a transiiton
[06:47] <mvo> pitti: I don't know how platform dependent the typelibs really are, but they are different on the arches, not sure what plays a role here
[06:48] <mvo> pitti: I can prepare a ppa with this change and test build of the rdepends to ensure we don't run into nasty corner cases. or do you think the gir stuff is all well behaved?
[06:49] <didrocks> hey mvo, bonjour pitti!
[06:49] <mvo> hey didrocks, good morning
[06:50] <pitti> mvo: well, at this stage (RTM) testing can never hurt, although I'm not sure how much introspection we actually use on touch (probably very little)
[06:51] <mvo> pitti: very little indeed, just 2 gstreamer libs right now iirc
[06:53] <pitti> mvo: so, the announcement to the devs is the main thing to do then
[06:54] <mvo> pitti: all right, let me draft something this morning.
[07:09] <willcooke> morning all
[07:09] <willcooke> seb128, Chromium 35 is in.  I think ChrisCoulson took care of it
[07:09] <willcooke> 36 has issues
[07:11] <didrocks> morning willcooke
[07:12] <willcooke> hey didrocks
[07:12] <willcooke> didrocks, are you UTC +1 ?
[07:13] <didrocks> willcooke: yeah, just one hour in the future compared to you :)
[07:13] <willcooke> so is it 8:13 for you?
[07:13] <didrocks> no, it's 9:13, with dailight saving
[07:14] <didrocks> daylight*
[07:14] <willcooke> ahh, ok - so you're still an hour ahead of me then
[07:14] <didrocks> yep
[07:14] <willcooke> didrocks, the reason I ask is that I really need to catch up with you, but I don't think I'll be able to do it until say 3pm your time
[07:14] <willcooke> is that ok>
[07:14] <willcooke> ?
[07:15] <didrocks> willcooke: that's fine, no worry! I usually go for running at lunch time :)
[07:19] <willcooke> hrm, you know what didrocks - we should have continued our journey down to Oz & NZ and paid those guys a visit, since we're half way there anyway
[07:20] <RAOF> willcooke: Come down to Hobart, it's lovely!
[07:20] <didrocks> willcooke: ahah, that would have been a really neat idea. And you can even tell this is for team building to meet robert ancell :)
[07:21] <willcooke> RAOF, didrocks  - I'll see if rickspencer3 will pay :D
[07:21] <didrocks> heh
[07:22] <willcooke> right - bbiab, school run
[07:29] <didrocks> waow 600 on /lib, don't ask why I couldn't log in into that container
[07:29] <didrocks> the base image is right though
[07:29] <czajkowski> aloha
[07:30]  * didrocks purges and redownload to see if the container is corrupted
[07:30] <didrocks> hey czajkowski!
[07:33] <didrocks> waow, the container is really corrupted…
[07:33]  * didrocks tries back to build it himself
[07:34] <didrocks> and relaunch a remote build
[07:59] <czajkowski> didrocks: gooood morning you happy chappy!
[08:00] <didrocks> czajkowski: did you leave to your conference already?
[08:00] <czajkowski> didrocks: yup arrived last night in Munich so at todays hackathon and lots of Ubuntu machines being used over here
[08:01] <czajkowski> nice to see it being used out and about by random people
[08:01] <czajkowski> that table is currently hacking mongodb ubuntu and censors for the the day
[08:01] <didrocks> waow, excellent!
[08:02] <czajkowski> yup will try and get this page updated during the day https://www.hackerleague.org/hackathons/munich-iot-hackathon-planning/participations but then you cna see what is built
[08:02] <czajkowski> also a very useful site!
[08:04] <Laney> hey hey ho ho
[08:04] <willcooke> 'sup Laney
[08:04] <didrocks> czajkowski: great!
[08:04] <didrocks> morning Laney
[08:04] <willcooke> tkamppeter, I just pimped the Open Printing  summit via G+
[08:05] <willcooke> I'll see if someone who actually has some followers (popey) can re-share
[08:05] <seb128> good morning desktopers
[08:06] <Laney> alright
[08:07] <Laney> wie gehts?
[08:07] <seb128> hey didrocks Laney willcooke czajkowski
[08:07] <seb128> good!
[08:07] <seb128> Laney, you?
[08:07] <didrocks> re seb128!
[08:07] <seb128> willcooke, @chromium, ack, thanks
[08:07] <seb128> didrocks, re ;-)
[08:07] <willcooke> np
[08:07] <seb128> willcooke, did you see my comment yesterday about eventual travelling and when that would be likely to be?
[08:07]  * willcooke scrolls back
[08:08] <seb128> it was in query
[08:08] <seb128> just wondering if you could figure out if we had some travelling planned after the summer and when
[08:08] <willcooke> seb128, didnt get it - the wifi in Blue Fin is sometimes dodgy
[08:09] <willcooke> seb128, I understand there /might/ be something in October, but I will find out for certain
[08:09] <willcooke> do you guys use some kind of IRC proxy?
[08:10] <seb128> willcooke, thanks, would be handy if we want to e.g book holidays
[08:10] <willcooke> something which is a bit more "store and forward"
[08:10] <seb128> I don't
[08:10] <seb128> larsu, Laney and some other do
[08:10] <Laney> yeah, screen+irssi
[08:10] <Laney> some people like irccloud
[08:10] <larsu> screen+irssi for me as well
[08:10] <larsu> on a raspi
[08:11]  * willcooke checks it out
[08:11] <didrocks> willcooke: I did use irssi + bip. And after some years, realized that if people want to reach me when I'm not there, emails is better :)
[08:11] <didrocks> I have then only to backlog emails
[08:11] <didrocks> and not emails + irc + …
[08:11] <seb128> emails also include content usually
[08:12] <seb128> not just "ping" ;-)
[08:12] <didrocks> really true! :)
[08:12] <Laney> 'ping' is better
[08:12] <Laney> waaaaaay more ignorable :-)
[08:12] <didrocks> ahah
[08:12] <seb128> lol
[08:12] <willcooke> ha
[08:12] <didrocks> willcooke: so, I guess you're warned now, don't ping without adding context ;)
[08:12] <willcooke> hehe - yeah I saw that yesterday :)
[08:13] <willcooke> I have a habit of doing that :/
[08:17] <tkamppeter> willcooke, thanks for pimpimg.
[08:20] <willcooke> dpm, https://plus.google.com/108554416426692294217/posts/jKQh1NmjrPo
[08:20] <seb128> willcooke, do you know if the chromium update is going to go to other series than utopic as well?
[08:21] <willcooke> dpm, is that something that one of the Ubuntu official accounts could re-share/tweet about?
[08:21] <willcooke> seb128, hrm - good question, I don't know.  Jamie said Chris sponsored it in, so I assume that Coulson?
[08:21] <willcooke> I can ask him
[08:21] <willcooke> (if it is)
[08:21] <seb128> it's chrisccoulson yes
[08:21] <seb128> he doesn't seem to be online though
[08:22] <willcooke> I'll find him...
[08:22] <seb128> he might just not be up yet
[08:23] <seb128> https://launchpad.net/ubuntu/+source/chromium-browser btw, for the versions/by serie
[08:23] <seb128> Laney, are you reviewing the developer mode mr?
[08:27] <Laney> yes
[08:28] <dpm> hi willcooke, let me have a look
[08:28] <ogra_> whee, thanks !
[08:32] <dpm> willcooke, https://plus.google.com/100887841569748798697/posts/CRKD6jJEjyF
[08:33] <willcooke> dpm, woot - thanks dude
[08:33] <willcooke> there you go tkamppeter!  250k followers :)
[08:33] <willcooke> yayay chrisccoulson
[08:34] <willcooke> chrisccoulson, morning chap!  Sorry to pounce on you the second you log in
[08:34] <chrisccoulson> hi :)
[08:35] <willcooke> chrisccoulson, the sponsorship of Chromium 35 you kindly did yesterday - is that for all series or just U?
[08:35] <chrisccoulson> willcooke, just for U. chad says cr36 will be ready by thursday, which I'll upload to all releases
[08:35] <chrisccoulson> I didn't see the point in pushing cr35 to all releases, only to update it again a couple of days later
[08:39] <willcooke> chrisccoulson, word
[08:39] <Laney> bird
[08:39] <willcooke> Laney, bird = word?
[08:39] <Laney> so they say
[08:39] <willcooke> I didn't know
[08:40] <Laney> I thought everybody had heard
[08:40] <willcooke> about?
[08:40] <Laney> bird being the word
[08:40] <willcooke> \o/
[08:41] <chrisccoulson> lol
[08:43] <seb128> chrisccoulson, ready on thursday, waiting to see :p
[08:43] <seb128> cr35 was "ready" for like 3 weeks before it got uploaded
[08:43] <chrisccoulson> hi seb128 :)
[08:43] <seb128> I hope we don't keep doing the same to hit then "oh, next one is coming, let's do this one" and never upload anything
[08:44] <seb128> because it's always take ages and by the time things are tested there is a new one
[08:44] <seb128> chrisccoulson, hey ;-)
[08:44] <chrisccoulson> seb128, hmmm, cr35 was only ready last week. at least, that's when the builds ended up in https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage
[08:44] <seb128> k
[08:45] <seb128> well, it was "almost ready" for a while before that
[08:45] <seb128> but if cr36 is ready this week or next, it's fine I guess
[08:45] <seb128> let's see
[08:45] <chrisccoulson> Yeah, hopefully
[08:46] <tkamppeter> willcooke, great, still too much paper needed ...
[08:46] <didrocks> remember that cr34 is really buggy
[08:47] <didrocks> like the loosing tabs and so on
[08:47] <didrocks> not great for a LTS
[08:47] <seb128> yeah
[08:47] <didrocks> losing*
[08:49] <czajkowski> Trevinho: has the patience of a saint! we at least have a bug reported this time https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1347494  still working on the back trace
[08:49] <ubot5> Launchpad bug 1347494 in unity (Ubuntu) "Logging in doesn't load unity desktop on admin account" [Undecided,New]
[08:53]  * didrocks doesn't know why containers produced on docker hub are broken…
[08:53] <didrocks> (bad permissions on directories)
[08:53] <czajkowski> Trevinho: for some unknown ditty reason it seems to hate unity-dbgsyms E: Unable to locate package unity-dbgsyms
[08:53] <czajkowski> are they built for utopic could that be it?
[08:54] <didrocks> Sweetshark: did you get the same issue?
[08:54] <didrocks> seems to be https://github.com/dotcloud/docker/issues/5892
[08:54]  * didrocks reads
[08:57] <Sweetshark> didrocks: havent run into that yet, but will look out now ;)
[08:58]  * didrocks is trying -s=devicemapper as suggested
[09:02] <Laney> czajkowski: dbgsym not dbgsyms, and you have to have enabled that repository if you didn't already https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages
[09:04] <seb128> czajkowski, you need the ddeb source matching you normal apt sources
[09:09] <Laney> whoops!
[09:09] <Laney> I just reproduced the "gstreamer 1.4" leak
[09:09] <Laney> ..........only I was still on 1.2.4
[09:09] <didrocks> Sweetshark: yeah, so if you add users that are non root, don't use trusted builds for now, rather, build them yourself
[09:09] <didrocks> Sweetshark: there is no workaround/fix apparently yet
[09:09]  * didrocks followed up on the bug
[09:11] <seb128> Laney, lol
[09:11] <seb128> Laney, so blaming the gst update wrongly?
[09:11] <seb128> Laney, how do you reproduce it?
[09:11] <Laney> seb128: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1346821/comments/5 I did that
[09:11] <ubot5> Launchpad bug 1346821 in media-hub (Ubuntu) "media-hub-server uses all system's memory (sigkill send to init)" [Critical,New]
[09:12] <Laney> load an album, then click the second half of the slider to make it go to the next song
[09:15] <seb128> k
[09:15] <seb128> did you downgrade base as well?
[09:15] <seb128> or only gst?
[09:15] <Laney> I didn't downgrade
[09:16] <Laney> just on an old image
[09:29] <willcooke> tkamppeter, you're muted at your end I think
[09:30] <willcooke> tkamppeter, I heard you for a second there
[09:31] <seb128> tkamppeter, do you know if canon mg6350 printers are known to have issues/not work with trusty? the printer is correctly detected/added by system-config-printer, printing makes the printer receive the job (it says so on its small lcd screen) but nothing gets out of the printer then
[09:32] <seb128> it's like the job was invalid and dropped by the printer or something
[09:32] <seb128> not sure how to debug, some website recommends just installing the driver from the constructor website
=== Estilanda_ is now known as Estilanda
[10:33] <didrocks> ok, going for exercising!
[10:48] <czajkowski> Laney: any sweet chance you're in london this week ?
[10:48] <Laney> czajkowski: nope
[10:49] <Laney> come to GUADEC next week? :-)
[10:49] <czajkowski> I've had 3 weeks of no tracel I'm enjoying this :p
[10:50] <Laney> actually I will be changing trains @ stp to get there ...
[10:54] <tkamppeter> seb128, the Canon printers have USB problems. Try the command "lpadmin -p <queue> -o usb-unidir-default=true" for the print queue.
[10:54] <tkamppeter> seb128, See "USB printer does not print or prints garbage" on https://wiki.ubuntu.com/DebuggingPrintingProblems
[10:56] <seb128> tkamppeter, thanks, that one is a wifi one, and it works with the ppd from canon
[10:56] <tkamppeter> seb128, if this works out, report a bug on http://www.cups.org/str.php, post the "lsusb" output (USB product/vendor IDs) and make/model of the printer. Or edit /usr/share/cups/usb/org.cups.usb-quirks and attach the patch to your bug report.
[10:56] <seb128> tkamppeter, ok, thanks
[10:59] <tkamppeter> seb128, for WiFi/Network I do not have any known problems of Canons. For WiFi printing in general I had only problems with my FritzBox router, but the FritzBox support helped me and fixed the firmware bug. I am running development firmware now and the printer works. Printer is HP though.
[11:01] <tkamppeter> seb128, no I remember that there are users of LiveBox routers who had problems with printers connected via IPP (independent of wired or wireless), these users have to replace the ipp://... URI by ipp14://...
[11:01] <tkamppeter> s/no/now/
[11:02] <willcooke> Sweetshark, just set up a 1:1 weekly - let me know if you want to move it
[11:04] <willcooke> larsu, ditto
[11:05] <willcooke> Laney, ditto
[11:11] <Sweetshark> willcooke: should be fine if we really do this hard timeboxed as I have a weekly call (Engineering Steering Committee at LibreOffice on 16:00CEST on Thursday) right after that.
[11:13] <willcooke> Sweetshark, sure, no worries.  I think once we get in to the swing of things it won't take 30 mins
[11:25] <willcooke> who is at guadec next week? seb128, didrocks, Laney?  attente too?
[11:25] <Laney> yes, & larsu & desrt
[11:25] <willcooke> excellenrt
[11:25] <willcooke> excellent
[11:32] <willcooke> exercise time for me now.  bbiab
=== alan_g is now known as alan_g|afk
=== alan_g|afk is now known as alan_g
=== alan_g is now known as alan_g|lunch
=== greyback is now known as greyback|lunch
=== MacSlow is now known as MacSlow|lunch
[12:47] <larsu> willcooke: I'll be on a train this Friday for our 1:1 (going to GUADEC)
[12:51] <willcooke> larsu, no worries, we'll catch up soon
[12:51] <larsu> cool, thanks
=== jhernand1z is now known as jhernandez
=== alan_g|lunch is now known as alan_g
[13:07] <seb128> willcooke, oh, forgot to reply for the guadec list, but what Laney said ;-)
=== willcooke is now known as willcooke|meetin
=== MacSlow|lunch is now known as MacSlow
=== greyback|lunch is now known as greyback
=== Estilanda_ is now known as Estilanda
=== willcooke_ is now known as willcooke
[13:37] <seb128> kenvandine, hey, are you going to review the dual sim work from Jonas?
[13:38] <kenvandine> seb128, yup
[13:38] <seb128> kenvandine, great, thanks ;-)
[13:39] <seb128> kenvandine, what happened to the landing from yesterday btw?
[13:39] <kenvandine> merge problems then pep8 test failures
[13:39] <seb128> urg
[13:39] <kenvandine> i'm going to finish it up this morning
[13:39] <seb128> is anyone working on fixing those?
[13:39] <seb128> k
[13:39] <kenvandine> it was building when i left yesterday
[13:39] <kenvandine> they got fixed late
[13:39] <seb128> kenvandine, should https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/call_forwarding/+merge/227761 bet set as "work in progress"? CI run and I said that's all you wanted from it
[13:40] <kenvandine> it's ready now
[13:40] <seb128> k
[13:40] <kenvandine> a review would be great :)
[13:40] <seb128> is Jonas doing one?
[13:40] <seb128> I can have a look as well
[13:40] <kenvandine> i haven't asked
[13:40] <seb128> k
[13:40] <seb128> let me look first
[13:40] <kenvandine> thx
[13:40] <seb128> if I feel like another review is welcome I can ping him
[13:41] <seb128> kenvandine, when you said 'they got fixed", you are speaking about the pep8 error? where? I didn't see a new mr?
[13:41] <seb128> or is that a new commit on one of those listed?
[13:41] <kenvandine> new commit
[13:41] <seb128> k
[13:41] <kenvandine> it's all built in the silo now
[13:41] <seb128> nice
[13:41] <seb128> land it!
[13:41] <kenvandine> i just need to do a round of testing
[13:41] <kenvandine> after my next meeting though :)
[13:45] <Laney> glad that pep8 is working now
[13:47] <seb128> yeah
[13:50] <Laney> btw I saw some dual sim MP come in and I was suspicious that it seems to duplicate the qml for the single and dual case
[13:50] <Laney> I'd think it ought to be possible to handle both in the same file
[13:50] <Laney> just in case anyone reviews this
[13:53] <asac> seb128: whats our gstreamre source package?
[13:53] <asac> e.g. launchpad ubuntu link at best
[13:53] <seb128> asac, https://launchpad.net/distros/ubuntu/+source/gstreamer1.0
[13:53] <asac> https://launchpad.net/ubuntu/+source/gstreamer1.0
[13:53] <asac> ah good
[13:54] <seb128> why?
[13:54] <seb128> still discussing that sync?
[13:54] <seb128> btw Laney said it's also happening with the old version
[13:55] <asac> seb128: not sure ... just got asked how we can e better in coordinating such pieces with stakeholders before dropping them
[13:55] <seb128> k
[13:56] <asac> at best it causes confusion and distraction for folks that are knee deep in making gstreamer magic happening for phone
[13:56] <asac> if that happens without them knowing
[13:56] <seb128> yeah, that makes sense
[13:56] <asac> what are your thoughts?
[13:56] <seb128> I guess we could create a table of packages that need confirmation before being synced, with their owners
[13:56] <seb128> but then we need to owners to be responsive and look at the pending syncs
[13:56] <asac> right
[13:57] <seb128> rather than being busy and ignore those
[13:57] <asac> so proactive merge/sync work management
[13:57] <seb128> otherwise we stay on outdated unsupported versions
[13:57] <Laney> I bet £10,000 that list will be 'everything on the phone'
[13:57] <seb128> and we loose the benefit of being close from Debian
[13:57] <seb128> Laney, and I bet for quite a part of the list there are going to be no active owner
[13:57] <seb128> like if libpng has a an update
[13:57] <seb128> or libzlib
[13:58] <seb128> or libelf
[13:58] <asac> i think its an interesting topic for the distro to figure
[13:58] <seb128> what we currently have works fine most of the time
[13:58] <seb128> it's just a bug, we get bugs through silo landings as well
[13:58] <seb128> those happen
[13:59] <Laney> looks like it wasn't even a bug
[13:59] <seb128> we have britney also to protect the image
[13:59] <Laney> so we're actually discussing something that wasn't even a problem
[13:59] <seb128> if we have tests in place to catch issues...
[13:59] <Laney> which seems a bit mad
[13:59] <seb128> right
[13:59] <seb128> but potentially a such sync could create an issue/introduce a new bug
[13:59] <Laney> a problem is that this report blinded people who then didn't even look into the problem
[13:59] <seb128> but silo landing as well
[13:59] <seb128> our testing is not perfect
[14:00] <seb128> right
[14:00] <Laney> I better go have lunch or else I'll EOD without having eaten :P
[14:01] <Laney> been trying to merge -bad 1.4, speaking of gst ...
[14:01]  * Laney screams
[14:01] <Laney> I was in the wrong directory when building the source package so it didn't get rebuilt so the build failed again
[14:01]  * Laney force afks
[14:01] <seb128> urg
[14:01] <seb128> enjoy!
=== m_conley_away is now known as m_conley
[14:20] <willcooke> Come to the Ubuntu On Air engineering update - I'm totally live dudes
[14:25] <seb128> oh, indeed you are there!
[14:26] <willcooke> exposing my ignorance in public
[14:27] <seb128> willcooke, xdg-utils is a bunch of scripts to deal with things like "open that file", "inhibit screen locking", which tries to do do the right thing for the desktop env in use
[14:27] <willcooke> thx seb128
[14:27] <seb128> that was a weird question to ask
[14:27] <willcooke> kicks mhall119
[14:27] <seb128> indeed
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
[14:49] <Laney> willcooke: seems like a bit of a baptism of fire...
[14:50] <mvo> willcooke: ubuntu-on-air on day3? woah, what a ride for you :)
[14:52] <willcooke> \o/
[15:06] <seb128> Laney, nobody decided for settings on line length changes
[15:07] <seb128> the document Jussi pointed to seems to be a "unity" one
[15:07] <seb128> e.g trying to be standard accross our projects iirc
[15:08] <seb128> I'm still undecided with the 80 chars, that feels like a too high constrains for modern width screens, though I agree it can be handy in some cases
[15:09] <Laney> I guess people don't bother having code side by side any more
[15:09] <Laney> whatever
[15:09] <seb128> but even on my laptop screen with qtcreator and a sidebar I can easily go to 110 chars
[15:09] <seb128> side by side is useful for debugging when you do old/new version, but otherwise do you use it?
[15:09] <Laney> all the time
[15:09] <Laney> listen
[15:10] <Laney> if you want to get rid of it then just do it
[15:10] <Laney> I just resent being linked to some random document
[15:10] <ogra_> and your screen pnly allows 160 chars ?
[15:10] <ogra_> *only
[15:10] <Laney> actually it's 141
[15:11] <seb128> Laney, I've no strong opinion, I just find that the 80 chars is easy to hit and does make for some extra wrapping which is less comfortable to read sometimes
[15:11] <seb128> but it's not a big deal either
[15:12] <ogra_> Laney, time to drop that 14" VGA monitor ... its 2014 !!
[15:12] <seb128> but yeah, I'm not wanting to change unless those guideline are something documented as being our standards for all projets we work on
[15:12] <seb128> ogra_, it's called a laptop
[15:12] <ogra_> seb128, sure ... but 141 chars !
[15:13] <seb128> my laptop does 136 chars
[15:13] <seb128> we don't all have hidpi ;-)
[15:13] <ogra_> my laptop does a *lot* more ... do you guys only work on tty consoles ?
[15:13] <seb128> no, it's gedit or qtcreator
[15:13] <Laney> vim
[15:13] <seb128> but resolution is not 1900 here
[15:13] <seb128> it's 1300
[15:13] <ogra_> ah, old HW :)
[15:14] <Laney> don't even know what it is, possibly 1280x960
[15:14] <seb128> not so old, but those resolutions are better for my eyes
[15:14] <seb128> if I were on 1900 I would adapt the font and hit around the same number of chars
[15:15] <seb128> well, anyway, not an useful discussion
[15:15] <Laney> anyway I'm aware I'm the only one who cares
[15:15] <ogra_> heh, yeah
[15:15] <Laney> so, fine by me if it makes everyone else sad
[15:16] <didrocks> seb128: Laney: the recommendations are 120 at most actually, to have the content readable
[15:17] <didrocks> intellij set 120 by default, whereas they tweak that value to 100 in Android Studio
[15:17] <Laney> kay
[15:17] <Laney> I checked what GNOME say and they say up to 120 too
[15:17] <didrocks> yeah, seems the standard to have readable content (longer makes it hard to read)
[15:19] <Laney> I want a linter to enforce this now >:)
[15:19] <Laney> especially if it fails the build
[15:19]  * Laney gets excited
[15:20] <didrocks> Laney: it's called pep8 :p
[15:20] <didrocks> oh C++, meh ;)
[15:20] <Laney> pep8 says 79 btw
[15:21] <didrocks> yeah, that's their default
[15:21] <didrocks> you can tweak it though
[15:21] <Laney> up to 100
[15:21] <didrocks> (as in udtc)
[15:21] <didrocks> I'm using 120 for both, but 100 can be a good start :p
[15:22] <Laney> pep8 is quite clear
[15:22] <didrocks> Laney: https://github.com/didrocks/ubuntu-developer-tools-center/blob/master/.pep8
[15:22] <Laney> indeed you can override it
[15:22] <Laney> by pep8 I mean the document
[15:23] <didrocks> (I exclude the virtualenv directory, most of the standard python library fails miserably)
=== Estilanda_ is now known as Estilanda
[16:32] <seb128> ok, calling it a day
[16:32] <seb128> Laney, have a nice early w.e, see you in Strasbourg
[16:33] <seb128> good evening desktopers
[16:33] <Laney> seb128: cheers, see you there
[16:33] <Laney> have a good evening!
[16:33] <seb128> thanks
[16:49]  * didrocks goes as well
[16:49] <didrocks> see you in Strasbourg Laney!
[16:49] <Laney> bye!
[16:50] <Laney> have a good two days
[16:50] <didrocks> thanks ;)
=== alan_g is now known as alan_g|EOD
[17:07] <willcooke> EODing now too - toodle pip
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== rickspencer3_ is now known as rickspencer3
=== Ursinha-afk is now known as Ursinha
=== m_conley is now known as m_conley_away