[05:49] <didrocks> good morning
[05:54] <darkxst> hey didrocks
[05:55] <didrocks> good evening darkxst, how was your week-end?
[05:56] <darkxst> didrocks, crap still can barely walk and today they found a blood clot in my leg ;(
[05:56] <didrocks> argh :/
[05:56] <didrocks> yeah, typical issues when you can't really move… :/
[05:57] <didrocks> going to the hospital to get it extracted?
[05:57] <darkxst> no, just been put on medication, and lost lots of blood for some tests
[05:58] <didrocks> ah, I can something to make your blood liquid
[05:59] <darkxst> didrocks, trying to finish up my gdm3 merge, but migrating settings is a mess, can't use dpkg-maintscripts-helper scripts, since the conffiles cross packages
[06:00] <didrocks> darkxst: most of the time, you can force with pre-depends the orders
[06:01] <didrocks> (not really indicated for general case, but for some special case like that)
[06:01] <darkxst> didrocks, but the paths and packages change
[06:01] <darkxst> /etc/gdm -> /etc/gdm3
[06:01] <didrocks> ah, not as easy then, indeed…
[06:01] <darkxst> gdm -> gdm3
[06:01] <didrocks> or in that case, don't care about the conffiles in the older package
[06:01] <didrocks> just handle the removal in the new binary
[06:01] <didrocks> (after transitioning)
[06:03] <darkxst> well I don't suppose many people modify gdm configs, so just going to get annoyed corner cases
[06:05] <darkxst> rm_conffile may work, since the old conffiles seem to get owned by the transitional package
[06:05] <didrocks> better to handle the transition still
[06:05]  * didrocks dislikes when we drop the ball on config transition
[06:06] <didrocks> but you don't really care about the "owning" part for moving to one package to another one
[06:06] <didrocks> you just don't install it in the "new" version of the old package
[06:06] <didrocks> and then, you handle the conffile in the new package, extracting data, rming the old conffile, and filing data in the new one
[06:06] <darkxst> didrocks, dpkg-maintscript-helper is was cares about owership
[06:07] <didrocks> oh, interesting, in that case, you should do it the old way :)
[06:07] <didrocks> you still have the scripts we used some moons ago at https://wiki.debian.org/DpkgConffileHandling
[06:10] <darkxst> yeh guess I will have to
[06:11] <darkxst> is there anyway to actaully test the scripts without a full package rebuild?
[06:12] <didrocks> just drop the file in /var/lib/dpkg/info and run it manually AFAIK
[06:12] <didrocks> (as root, of course)
[06:12] <didrocks> you can as well opened your previous ar .deb package, and change the file
[06:13] <didrocks> and run dpkg -i directly
[06:14] <darkxst> didrocks, I did try that, and the helper scripts bailed out with "invalid package", but thats less of a problem is I don't use it
[06:15] <darkxst> also debconf is dumb, suppose I have to tell it directly the new display manager is gdm3, right now it asks to choose between gdm and gdm3 (can only guess the configure script runs while both versions are unpacked?)
[06:18] <didrocks> yeah, that's what happen I guess
[06:18] <didrocks> as those triggers are executed on configure
[06:18] <didrocks> and so, you have the unpack step first (and removal)
[06:21] <darkxst> that shouldnt be a problem though, and the diff against debian is actually sane now!
[06:22] <didrocks> yeah, this gdm/gdm3 has been a nightmare for too many years
[06:22] <didrocks> thanks for fixing it! :)
[06:22] <darkxst> yeh, there hasnt been a proper merge in maybe 10 years
[06:24] <darkxst> didrocks, don't thank me yet, you will probably have to NEW it ;) and someone is going to have to sponsor the upload
[06:26] <didrocks> darkxst: I prefer NEWing that reviewing MIRs TBH :p
[06:27] <darkxst> yeh and I guess the NEWing bit is actually pretty simple in this case, same upstream code
[06:29] <darkxst> no one is going to review the merge though, would take them all day !
[06:30] <didrocks> yeah, I bet!
[06:30] <didrocks> This will be more a case of "I try to install -> works -> upload"
[06:30] <didrocks> like libreoffice uploads :)
[06:34] <darkxst> didrocks, has only taken me a year to finish it up
[06:35] <darkxst> s/to get around to finishing it up/
[06:37] <didrocks> heh ;)
[06:40] <darkxst> didrocks, mainly because its like impossible to get a sane diff, between the two
[06:41] <didrocks> yeah, I guess anyway it's a case where testing (and early drop in the distro) is the best that we can get
[06:42] <darkxst> yep, lots of time left in this cycle!
[06:42] <darkxst> and 3.18 is almost done
[06:43] <didrocks> nice!
[06:44] <darkxst> just waiting on MIR stuff for gtk, then there are the few long standing outdated packages
[06:47] <darkxst> didrocks, or should that be Mir?
[06:48] <darkxst> why name a display server after a process!
[06:52] <didrocks> darkxst: yeah, I know :/
[06:52] <didrocks> Mir is the project
[06:52] <didrocks> MIR is the process
[07:18] <darkxst> didrocks, I well know that, but its still confusing!
[07:58] <Sweet5hark> moin all
[07:59] <didrocks> good morning Sweet5hark!
[08:03] <willcooke> morning
[08:04] <didrocks> hey early willcooke
[08:05] <Sweet5hark> didrocks, willcooke: hey guys.
[08:14] <larsu> good morning!
[08:14] <darkxst> hey willcooke larsu
[08:14] <didrocks> morning larsu
[08:15] <larsu> morning didrocks & darkxst. How are you?
[08:15] <didrocks> good, thanks! yourself?
[08:16] <darkxst> larsu, broken... apparently have a blood clot in my leg, but battling with gdm3 merge was just as painful ;)
[08:16] <larsu> darkxst: oh sorry to hear. Hope you get better soon!
[08:16] <larsu> didrocks: good thanks :)
[08:18] <darkxst> larsu, not sure I will ever recover from merging gdm3!
[08:18] <darkxst> my leg however should recover soon
[08:20] <larsu> haha :)
[08:21] <seb128> good morning desktopers
[08:21] <seb128> hey larsu
[08:21] <didrocks> re seb128
[08:21] <seb128> I just missed something funny?!
[08:21] <darkxst> larsu, took my entire friday evening to just get a sane enough diff, with some rename, sed foo
[08:21] <larsu> seb128: morning! how are you?
[08:22] <darkxst> seb128, probably <darkxst> larsu, broken... apparently have a blood clot in my leg, but battling with gdm3 merge was just as painful ;)
[08:22] <seb128> larsu, good! how are you?
[08:22] <seb128> gdm fun, I see
 larsu, not sure I will ever recover from merging gdm3!
 my leg however should recover soon
[08:22] <darkxst> seb128, merge is done, just battling with migrations now
[08:23] <darkxst> I can't use the helper scripts ;(
[08:23] <seb128> why not?
[08:23] <darkxst> cause paths and packages changes
[08:24] <darkxst> dpkg-maintscript-helper checks to see if package owns the files, but we are crossing packages and changing paths
[08:25] <seb128> k
[08:26] <darkxst> seb128, really migration is just a mess, but the resulting diff is so much more saner, atleast
[08:27] <seb128> that's something ;-)
[08:30] <larsu> seb128: great thanks!
[08:32] <darkxst> seb128, atleast it only needs to be done once!
[08:42] <darkxst> seb128, or twice, though my git branch from the first attempt last year proved incredibly helpful ;)
[08:42] <seb128> larsu, did you see my ping on friday btw?
[08:42] <larsu> seb128: notify osd icons? Working on it
[08:42] <seb128> larsu, yes
[08:42] <larsu> sorry, conference was more fun than I thought
[08:42] <seb128> thanks, should we hold the current silo?
[08:42] <larsu> and got the log spam issue fixed :)
[08:42] <larsu> talking to maintainers in person helps ;)
[08:42] <seb128> no problem :-)
[08:42] <seb128> great!
[08:43] <seb128> was it fixed in glib?
[08:43] <seb128> or in dbus?
[08:43] <larsu> my (amended) patch is in dbus (just the spec)
[08:43] <larsu> I'll take care of pushing the glib fix today
[08:43] <seb128> great
[08:43] <seb128> danke
[08:43] <larsu> yw!
[08:44] <larsu> seb128: ya hold it if you don't mind watining the day
[08:45] <seb128> k, doing that, no worry
[08:49]  * willcooke -> opticians - bbiab
[09:03] <Laney> hullo
[09:05] <darkxst> hey laney
[09:05] <Laney> sup darkxst
[09:05] <Laney> I read scrollback, no need to repeat ;-)
[09:06] <darkxst> Laney, too much crap
[09:07] <larsu> morning Laney!
[09:10] <didrocks> hey Laney!
[09:10] <seb128> hey Laney, how are you?
[09:11] <Laney> hey larsu & didrocks & seb128!
[09:11] <Laney> what a treat!
[09:11] <ricotz> hey desktopers
[09:11] <Laney> doing good thanks, nice relaxing weekend
[09:11] <Laney> good weekends all?
[09:11] <Laney> hi ricotz
[09:11] <ricotz> seb128, hi, afaics bamf doesnt like those two gedit desktop-files and seems to randomly pick one as default
[09:12] <ricotz> hey Laney
[09:12] <ricotz> Trevinho, hi ^, regarding bamf <-> new gedit
[09:14] <didrocks> morning ricotz
[09:15] <ricotz> hi didrocks
[09:20] <seb128> ricotz, no idea about that, it's not different from what we did with e.g totem or nautilus
[09:20] <seb128> but we can revert the GNOME renames if needed
[09:22] <seb128> Laney, seems like doko fixed binutils and a good part of what was stacked migrated on saturday ;-)
[09:22] <Laney> yeah I saw
[09:22] <Laney> good old doko
[09:24] <seb128> I'm glad it did migrate
[09:25] <seb128> I misread what you said on friday and though we were stucked to get x265 and other things through
[09:26] <Laney> no that's gstreamer and other things
[09:27] <seb128> k
[09:27] <seb128> I though we ended up with everything have to go together
[09:27] <seb128> anyway it's mostly good now ;-)
[09:29] <ricotz> seb128, I think I see this with nautilus too, not sure about totem
[09:30] <seb128> ricotz, is that a bamf bug?
[09:30] <ricotz> seb128, I would not revert the GNOME renames, this would break the DBusActivatable feature?
[09:30] <seb128> is that used anywhere?
[09:31] <ricotz> seb128, it might be a bamf issue, maybe NotShownIn OnlyShowIn would be better to differenciate
[09:32] <ricotz> not sure, but it is there for a reason and avoiding to follow the rename might just lead to problems later
[09:33] <ricotz> keeping those old-named files arround is just to preserver user-settings regarding pinned application in unity?
[09:35] <seb128> not only unity or pinned applications
[09:35] <seb128> but yeah user settings
[09:35] <seb128> it's also e.g mimetype associations
[09:36] <seb128> you pick something else as your favorite text editor and then back gedit
[09:36] <seb128> and you have gedit.desktop in your config
[09:39] <larsu> oh we're talking about *this* again
[09:39]  * larsu sighs
[09:47] <seb128> larsu, yeah, we alternate between that and headerbar as favorite topics :p
[09:50] <larsu> haha
[09:52] <seb128> but yeah, it's another issue that we never really resolved and that GNOME completely ignored :-/
[09:52] <seb128> unsure what to do about it
[09:53] <larsu> write a migration tool that converts desktop file names in all the user settings
[09:53] <ricotz> seb128, I see
[09:53] <larsu> or put a translation thing into gli
[09:53] <larsu> *glib
[09:53] <seb128> the migration thing is not possible
[09:53] <seb128> you can't know every user config and they storage format
[09:54] <seb128> some apps could have a custom sql database with the .desktop names in it
[09:55] <seb128> unsure what was the outcome of the translation thing into glib previous time we discussed it
[09:55] <larsu> which apps deal with desktop files?
[09:56] <seb128> good questions, I've no idea
[09:56] <seb128> every sort of "launcher" we have in the archive?
[09:56] <seb128> gnome-panel, cairo-dock, unity, xfce-panel, lxde-panel, kde*
[09:56] <seb128> and every sort of dock I don't know about
[09:57]  * larsu wonders why he even got into that debate again :)
[09:57] <seb128> haha
[09:57] <larsu> solution: put up a big bug, add all the things
[09:57] <larsu> and fix it for unity only
[09:57] <larsu> others will quickly follow if we provide an easy way to integrate
[09:57] <seb128> yeah, let's stop there, I feel like we are going to go circle and just create frustration
[09:57] <larsu> indeed
[09:57]  * larsu makes another tea
[09:57] <seb128> :-)
[09:58] <larsu> much better use of these 5 minutes
[09:58] <Laney> someone help me find the actual failure in ffmpeg?
[09:58] <Laney> 's build log
[09:58] <seb128> Laney, url?
[09:59] <Laney> :(
[09:59] <Laney> it's on → machine
[09:59] <Laney> https://launchpadlibrarian.net/225504108/buildlog_ubuntu-xenial-armhf.ffmpeg_7:2.8.1-1build2_BUILDING.txt.gz
[10:00] <Laney> slangasek tried to fix it but it didn't work
[10:00] <Laney> wondering if there is some easy enough way but can't find the error
[10:00] <larsu> FT_FREETYPE_H is not defined?!
[10:01] <larsu> #include MACRO is ... weird
[10:01] <seb128> Laney,
[10:01] <seb128> gcc -I. -I./ -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC -DZLIB_CONST -MM ffplay.c | sed -e "/^#.*/d" -e "s,^[[:space:]]*ffplay\\.o,./ffplay.o," > ffplay.d
[10:01] <seb128> ffplay.c:3217:46: error: missing binary operator before token "("
[10:01] <seb128>  #if defined(__APPLE__) && SDL_VERSION_ATLEAST(1, 2, 14)
[10:01] <Laney> is that breaking it?
[10:01] <seb128> ?
[10:02] <Laney> Test idct8x8 failed. Look at tests/data/fate/idct8x8.err for details. make[2]: *** [fate-idct8x8] Error 1 tests/Makefile:203: recipe for target 'fate-idct8x8' failed
[10:02] <Laney> that one I think
[10:02] <Laney> doesn't show that file though
[10:02] <Laney> THANKS FFMPEG
[10:03] <larsu> seb128: that one and the ones about freetype macros being empty
[10:03] <Laney> no
[10:04] <Laney> https://launchpadlibrarian.net/225502974/buildlog_ubuntu-xenial-amd64.ffmpeg_7:2.8.1-1build2_BUILDING.txt.gz
[10:04] <Laney> because it's in there too and still builds
[10:04] <seb128> Laney, https://sourceware.org/bugzilla/show_bug.cgi?id=19217
[10:04] <seb128> ?
[10:04] <davidcalle> willcooke, hey, sorry I'm not done with scopes patches yet, will update you on it asap
[10:05] <Laney> seb128: yeah I think it was trying to work aroudn this one
[10:05] <seb128> just disable that one test on armhf?
[10:05] <Laney> so should be disabled in this case I guess
[10:05]  * Laney looks at it
[10:06] <willcooke> back
[10:08] <seb128> wb willcooke
[10:08] <Laney> hi willcooke
[10:09] <Laney> good bonfire?
[10:09] <larsu> hey willcooke
[10:10] <Laney> or was the opticians related...
[10:10] <Laney> don't stand too close to the fire...
[10:10] <willcooke> :)
[10:11] <willcooke> I have to wear galsses now
[10:11] <willcooke> *glasses
[10:11] <Laney> it begins
[10:11] <willcooke> heh
[10:12] <willcooke> Being able to see things close up again will be lovely though
[10:12]  * Laney is practicing staring out of the window for a bit every now and then
[10:12] <Laney> oh hi HMP Nottingham
[10:12] <willcooke> :D
[10:13] <willcooke> chrisccoulson, do you have a few mins today to catch up re: my email?
[10:24] <willcooke> larsu, I want to fix this:  https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/762349
[10:24] <willcooke> larsu, can you tell me which are the best files to edit and I'll try and scrape an MP together
[10:25] <willcooke> I think it'll be something in /usr/share/themes/Ambiance/gtk-3.0/
[10:25] <willcooke> and then Radiance as well
[10:25] <larsu> willcooke: yep, gtkwidgets.css
[10:26] <willcooke> thanks
[10:26] <larsu> how do you want to color them?
[10:26] <willcooke> gonna make active the same colour as it is and inactive darker I think
[10:26] <larsu> ah cool stuff
[10:26] <willcooke> I'll get JohnLea to check it
[10:26] <larsu> please use the shade()/darker() stuff instead of hard coding a value
[10:26] <willcooke> got it
[10:27] <larsu> (that's also a bit hard coding, but not as bad)
[10:27] <larsu> imo
[10:27] <willcooke> yeah, makes sense
[10:28] <Laney> willcooke: firefox looks good imho
[10:29] <larsu> Laney: I agree, but that only works when the tab bar is attached to another dark widget
[10:29] <larsu> like the title bar or a header bar
[10:29] <larsu> looks bad otherwis
[10:29] <larsu> *e
[10:29] <willcooke> I'll try with darker and I think I'll be able to get close
[10:30]  * larsu is looking forward to seeingthat
[10:30] <Laney> such as where?
[10:30] <willcooke> larsu, will I need a separate entry for the tabs in gedit too - or is there a clever way to do both terminal tabs and gedit tabs?
[10:31] <larsu> willcooke: it's the same widget. If you need to do something app specific, please put it in apps/<appname>.css
[10:31] <larsu> like if you want to select by GeditWindow or similar
[10:31] <larsu> but I'd prefer to keep that small
[10:31] <larsu> Laney: old gedit has tabs below the toolbar
[10:31] <willcooke> ah cool, I think they should be the same, so a single widget is good news
[10:31] <larsu> Laney: I'm sure there are more apps that do this
[10:32] <Laney> I'm not doubting you...
[10:32] <larsu> willcooke: there should already be quite some rules about tabs in gtkwidgets.css
[10:32] <Laney> just asking for an example
[10:32] <larsu> gtkwidgetfactory!
[10:35] <Laney> ok, can't visualise the problem, looking forward to seeing it in action then :)
[10:42] <willcooke> I've tried it with @dark_bg_color but it clashes badly with the main background of the gedit window for example
[10:42] <willcooke> so that's similar to ffox
[10:42] <willcooke> dont like it
[10:42] <willcooke> gonna try again just making it slightly darker
[10:42] <willcooke> larsu, is using shade acceptable?
[10:42] <willcooke> if Ihave to
[10:42] <Laney> I don't get why it's okay for FF
[10:42] <Laney> eyes are hard
[10:43] <willcooke> I'll do a screenshot, one sec...
[10:43] <Laney> nah, I believe you :P
[10:44] <larsu> willcooke: yeah, of course
[10:45] <seb128> willcooke, want to look at bug #1479054 as well? ;-)
[10:45] <didrocks> seb128: quick, assign! :)
[10:45] <seb128> hehe
[10:46] <didrocks> welcome to our new theme maintainer, larsu is off the hook \o/
[10:46] <seb128> we have a new theme maintainer \o/
[10:46] <Laney> muhahaha
[10:46] <seb128> :-)
[10:46] <larsu> didrocks: pssst - don't let him know yet
[10:46] <larsu> it has to look natural
[10:46] <didrocks> ahah
[10:46] <willcooke> Sure!  CSS is about my level
[10:47] <seb128> he's not maintaining it, just looking at some issues
[10:47] <seb128> that's fine
[10:47] <willcooke> actually, I'm quote happy to do this
[10:47] <willcooke> quite
[10:47] <seb128> :-)
[10:47] <willcooke> ok, gedit fixed
[10:47] <Laney> oh cool, you can fix the big info icon in hidpi too
[10:47] <Laney> THANKS!
[10:47] <willcooke> daker(@bg_color) is the right one imo
[10:47] <Laney> css theme comes with icon theme
[10:47] <BigWhale> Hello everyone... :)
[10:47] <willcooke> and since I'm not the maintainer then let's ship it
[10:47] <willcooke> now
[10:47] <willcooke> damnit
[10:48] <seb128> hey BigWhale
[10:48] <larsu> willcooke: if you're the maintainer you can even review your own patches!!!
[10:48] <willcooke> \o/
[10:49] <willcooke> ok, that was easy! :D
[10:49] <willcooke> Now I have to work out bzr
[10:49] <seb128> screenshot? ;-)
[10:49] <willcooke> YOU QUESTION ME?!?!?!?
[10:49] <seb128> NEVER SIR
[10:50] <willcooke> haha
[10:50] <seb128> :-)
[10:50] <seb128> just wanted to see the beautiful outcome, going to wait for the package to land ;-)
[10:50] <willcooke> actually, it's not awesome.  e.g. the close icons on the inactive tabs could do with a tweak as well I think
[10:51] <Laney> teach this man about the inspector
[10:51] <seb128> didrocks, see how he starts caring about detail, going to make a good theme maintainer, i'm telling you ;-)
[10:51] <willcooke> http://imgur.com/4wB3zIi
[10:51] <willcooke> screen shot
[10:52] <willcooke> "golf facts" were for my sons homework
[10:52] <willcooke> honest
[10:52] <didrocks> seb128: heh, I'm actually waiting for the first theme regressions though :p
[10:52] <didrocks> then, he will get the stamp
[10:52] <larsu> willcooke: was about to mention those :P
[10:52] <willcooke> :)
[10:53] <willcooke> oh, that's odd.  The close icon in gedit has no circle around in on active or inactive, but terminal does
[10:54] <willcooke> ok, yeah I need to get the inspector working
[10:55] <willcooke> oh, but only when the window isn't focused do the circles appear
[10:55]  * willcooke decides thats a bug
[10:56] <seb128> willcooke, install libgtk-3-dev and do ctrl-shift-I
[10:56] <didrocks> (you probably need to restart the app after installing the -dev package)
[10:57] <willcooke> thx
[10:58] <willcooke> humm, that circles issues doesn't exist on 14.04
[10:59] <davmor2> willcooke: yeah, yeah, blame your son for looking at golf stuff, sure we believe you ;)
[11:00] <willcooke> :D
[11:02] <davmor2> willcooke: oh good news at the weekend I found a non-apple compatible mini display port to hdmi so I can now play multimonitor with xps, will be looking at setting it up this afternoon.  One big question though, on the auto detect of monitors should it not ask for the dpi of the monitor?
[11:03] <larsu> davmor2: should it not find it out for itself?
[11:03] <willcooke> davmor2, erm, not sure I follow you, but I would expect it to do it automatically
[11:03] <davmor2> willcooke: from the quick test at the weekend it looks like it was correctly getting 1080p for the resolution, but the dpi was still set to the xps 4k
[11:04] <davmor2> willcooke: so the screen app on the laptop was fine, but on the monitor filled the screen and then some
[11:05] <willcooke> hrm, dunno.  Question for Trevinho I think ^^
[11:08] <davmor2> Trevinho: just for the record, Xps 13 4k display, scaling factor 2 set through the Screen Display section of the settings app, plugged into an acer 26" monitor at 1920x1080
[11:09] <davmor2> Trevinho: I'll take screenshot/photo's later when I set it up properly
[11:12] <willcooke> seb128, could you have a look at that mailing list proposed email today?
[11:13] <seb128> willcooke, oh, right, sorry I started on that friday and got sidetracked with other thing, doing that after lunch
[11:14] <willcooke> thx seb128
[11:15] <seb128> np, sorry for not doing it on friday
[11:22] <willcooke> nw
[11:23] <Laney> is that the one about the seed changes?
[11:24] <willcooke> Laney, more just "here are some app changes..."  brasero, empathy, g cal
[11:24] <willcooke> I think we should still communicate the seed changes properly
[11:24] <willcooke> this is just a heads up
[11:24] <willcooke> mhall119 asked for it
[11:24] <willcooke> but if you're nearly ready with the seed changes email, that will be better
[11:27] <Laney> No not yet
[11:28] <willcooke> oki, I will carry on with this then
[11:29] <Laney> I'll do the changes this week though
[11:29] <Laney> Hope we don't get some terrid discussion
[11:30] <didrocks> "braserooooooooooooooooooooooooo"
[11:30] <didrocks> :)
[11:32]  * davmor2 pictures didrocks doing his best Darth Vader Noooooooooooooooooooooooooooooooo! impression with that "braserooooooooooooooooooooooooo"
[11:32] <happyaron> I guess I'll stuck with GNOME translations for half of the week, to get all the submissions processed...
[11:50] <Laney> http://162.213.34.169/html/
[11:52] <didrocks> Laney: nice! you are running it?
[11:52] <Laney> ya
[11:52] <Trevinho> davmor2: unfortunately you can only define a global scale value for apps, while unity can be scaled per-screen..
[11:52] <Laney> just hooked it up in the stack, nothing fancy now
[11:53] <davmor2> Trevinho: right so it is the scaling at fault then :(  meh
[11:54] <Trevinho> davmor2: yeah... unfortunately it's not nice, but no toolkit has the concept of scaling per monitor currently
[12:01] <Sweet5hark> seb128: I dont plan to SRU bug 1514195 as a backport, but with 5.0.4: sure.
[12:20] <seb128> Sweet5hark, wfm
[13:09] <Laney> https://launchpad.net/~laney/+archive/ubuntu/arm/+build/8279451
[13:10] <seb128> Laney, well done!
[13:11] <Laney> not sure skipping a test is that smart :P
[13:11] <Laney> but thanks
[13:29] <willcooke> argh!
[13:29] <willcooke> Themes are hard
[13:29] <willcooke> well, css selectors are hard
[13:29] <willcooke> Seems the close buttons on Gedit tabs are specific to Gedit
[13:32] <seb128> yeah, the nautilus ones seem differen
[13:32] <seb128> t
[13:32] <willcooke> Using the inspector and looking at the selector says it's a GeditCloseButton
[13:33] <willcooke> so I will put the changes in the gedit css file
[13:33] <seb128> that makes sense
[13:33] <willcooke> cool
[14:08] <attente> good morning!
[14:08] <willcooke> hey attente
[14:08] <seb128> hey attente
[14:08] <attente> hi guys
[14:08] <didrocks> hey attente
[14:08] <attente> hi didrocks
[14:28] <Laney> what up attente
[14:29] <larsu> hi attente!
[14:29] <attente> hey Laney, hey larsu
[14:33] <desrt> good morning peeps
[14:33] <desrt> attente: any reason not to use a socketpair for your dbus connection?
[14:34] <larsu> hey desrt
[14:34] <desrt> morning :)
[14:36] <attente> desrt: i thought using pipes would be simpler
[14:36] <attente> desrt: good morning
[14:37] <desrt> pipes can't do everything you can with sockets
[14:37] <desrt> like sending fds
[14:37] <attente> oh
[14:38] <attente> before i switch over to sockets, do you think it's because the object doesn't implement org.freedesktop.Properties, etcx
[14:38] <attente> ?
[14:40] <attente> like who is responsible for implementing that interface?
[14:40] <attente> gdbus-codegen doesn't generate it
[14:40] <seb128> hey desrt
[14:41] <larsu> attente: it should when you have properties in the dbus xml
[14:42] <attente> larsu: oh, so what about org.freedesktop.DBus.Introspectable?
[14:43] <qengho> FJKong: zaoshanghao. That is not in hanzi because my input method isn't doing anything after switching from en to zh-pinyin. fcitx is running. Can you help me debug?
[14:43] <larsu> attente: same (but I think register_object() does this, even)
[14:47] <attente> larsu: ok, thanks
[14:52] <willcooke> gtk inspector has black corners as well, that's related to the tooltips thing right?
[14:52] <seb128> that's an exemple of application using the client side decoration
[14:53] <seb128> you know that topic that comes back every cycle :p
[14:53]  * willcooke shuts up now
[14:53] <seb128> so not exactly like the tooltip (which we fixed with a gtk workaround)
[14:53] <seb128> but hikiko/trevinho are working on that
[14:54] <willcooke> ahhh, ok, yes
[14:54] <willcooke> thx
[14:55] <willcooke> larsu, css selectors make me sad.  In our 1:1 on Friday can you give me a hand with this?  The basic patch for making unselected tabs darker is very simple, but trying to get rid of the light grey circle from around the close icon on an unfocused window has me beaten
[14:57] <larsu> willcooke: sure! css is a bit tricky (order matters, but more so specificity of the rules)
[14:57] <larsu> and specificity is hard to grok
[14:57] <Trevinho> seb128: yeah, I did a first version, but hikiko one would cover more cases
[14:58] <larsu> this is the year of fixed client side decorations!
[14:58] <larsu> oh I guess I should say "cycle"
[14:58] <willcooke> larsu,  I /think/ I need to make the selector match the Geditclosebutton but for an unfocused window, the logic is sound, but yeah, not working ;)  I'll keep playing with it in the meantime.  It's a fun learning exercise
[15:01] <larsu> willcooke: I don't think you can select for unfocussed things...
[15:01] <larsu> buttons are very tricky
[15:01] <larsu> all the same classes, but look different in a million places
[15:02] <willcooke> I'll press on :)
[15:02] <attente> desrt: why is passing around fds not possible with pipes in my case? the pipes are internal to my process
[15:03] <desrt> why are you speaking dbus to yourself via pipes?
[15:04] <attente> it's a test case
[15:07] <seb128> Laney, can you push your nautilus upload (the bg scaling fix) to the vcs?
[15:08] <Laney> done
[15:08] <seb128> thanks
[15:08] <Laney> yw
[15:08] <seb128> I'm starting looking at the 3.18 update
[15:09] <willcooke> larsu, do things like Ambiance and Radiance inherit from other themes?  e.g. Should I be looking for the general button theme outside of the Ambiance directory?
[15:09] <Laney> seb128: keeping the headerbar yes?
[15:10] <larsu> willcooke: no, they don't
[15:10] <larsu> only the icon themes inherit
[15:10] <willcooke> cool, that makes it easier, thanks larsu
[15:10] <larsu> but there's some stuff in -borders.css
[15:10] <seb128> Laney, for now yes, same as gedit, let's see how those go
[15:10] <larsu> if I haven't removed all of that yet...
[15:10] <Laney> just checking
[15:10] <seb128> Laney, going to need to redo the menubar patch though
[15:10] <Laney> because the menu bar patch was the reason we blocked it before
[15:10] <seb128> yeah
[15:11] <seb128> that needs to be redone
[15:11] <seb128> I would usually ask larsu but he's busy with geoloc work so I'm going to have a try
[15:11]  * larsu can help out!
[15:12] <seb128> larsu, want to have a look at doing the menubar patch for nautilus?
[15:12] <larsu> sure
[15:12] <seb128> hopefully it's easy enough, they ported their code to the modern ways
[15:12] <seb128> larsu, danke
[15:12] <Laney> HAHA
[15:12] <Laney> that went from "I'm going to have a try" to "larsu is doing it" in about 45 seconds
[15:13] <Laney> ♥
[15:13] <seb128> larsu, just do that based on git, I'm going to look at the package update and refreshing the other patches, etc (based on the work robert did for 3.16 and the gnome3 ppa, though they often comment patches instead of refreshing them)
[15:13] <seb128> Laney, :-)
[15:13] <seb128> there is still quite a load of patches and diff for the Debian rebase
[15:13] <seb128> so it's not like I was avoiding doing any work :p
[15:13] <larsu> seb128: master, even?
[15:13] <Laney> drop all the patches!
[15:14] <Laney> ...ubuntu14
[15:14] <larsu> just drop a random one every week
[15:14] <larsu> I'm sure didrocks could write a script for that
[15:14] <seb128> haha
[15:14] <Laney> oh yeah it's still doing the wallpaper
[15:14] <Laney> :( :( :( :(
[15:15] <seb128> larsu, yes, I don't think 3.18.1 and master are too far
[15:15] <Laney> ): ): ): ):
[15:15] <Laney> backwards smileys are weirdly hard to type
[15:15] <mterry> kenvandine, did you see my poke about deja-dup's no-python2 branch?
[15:15] <larsu> Laney: also, read
[15:15] <kenvandine> mterry, yeah, sorry i didn't respond
[15:15]  * Laney reads things all the time
[15:15]  * Laney is good at reading
[15:15] <Laney> my mum told me so
[15:16] <kenvandine> i was busy and glanced at the branch and saw i couldn't review it quickly
[15:16] <desrt> attente: transfering fds with dbus is only possible on unix sockets because it is done using a control message that is specific to unix sockets
[15:16] <desrt> for your testcase, though, what are you doing?
[15:16] <kenvandine> mterry, i can look at it today or tomorrow, ok?
[15:16] <desrt> are you creating the proxy sync or async?
[15:16] <desrt> and is the 'service side' in the same thread?
[15:17] <larsu> Laney: also how to read backwards smileys? d:
[15:18] <Laney> C:
[15:18] <mterry> kenvandine, no rush at all.  Just wanted to make sure it was on your radar
[15:19] <kenvandine> yeah, that's a huge merge proposal :)
[15:19] <kenvandine> i might need help setting up my desktop for running the tests, it's been ages
[15:20] <kenvandine> but not this morning, meetings
[15:26] <Laney> so
[15:26] <Laney> gtk 3.18?
[15:26] <Laney> ok, no objections, thanks guys!
[15:26]  * Laney slides it in
[15:27] <attente> smooth
[15:27] <seb128> Laney, no real blocker for me, I hope the bg issue is not going to hit too many users/going to be hard to resolve
[15:28] <Laney> ya let's file gtk318 + rls-x-incoming bugs
[15:30] <attente> desrt: it's a test case for a library (maliit-glib) that talks to a stub server over dbus to make sure the library talks to it properly
[15:31] <attente> i'm creating the proxy sync
[15:34] <attente> service side is created with g_dbus_interface_skeleton_export on the same thread, don't know if the signal handlers are being called on the same thread or a different one though
[15:34] <desrt> attente: that's the problem
[15:34] <desrt> attente: proxy creation needs to talk to the service
[15:34] <desrt> attente: you create the proxy sync, so the client-side waits until the service responds
[15:35] <desrt> meanwhile, the service can't respond until the mainloop runs, which it can't do because you're doing a sync wait
[15:35] <desrt> put the service in a thread
[15:38] <larsu> or don't do sync operations..
[15:38] <desrt> in a testcase?
[15:39] <larsu> sure, why not?
[15:39] <desrt> because sync is easier and it's just a testcase
[15:39] <larsu> putting it in a thread sounds like it will bring more problems later ;)
[15:40] <desrt> imho if you want to have a service in the same process as a client, for testing purposes, it only makes sense that it would be in a separate thread
[15:40] <desrt> rather than the two things constantly having to dance around each other in the same maincontext
[15:41] <larsu> should work fine though, shouldn't it?
[15:42] <desrt> as long as you constantly sprinkle your code with (run the mainloop for a while) sections complete with termination conditions
[15:42] <desrt> the way people write tests isn't normally event driven
[15:43] <desrt> it's "do this, then this, then this"
[15:43] <desrt> it's not particularly well suited to async, unless you're writing in vala or something like that
[15:43] <desrt> also: i'm not even sure if this is really the problem.  it just sounds like it.
[15:44] <larsu> well sure, it won't work if you do everything sync
[15:44] <larsu> in that case threads do make more sense
[15:44] <larsu> and probably you're right - in a test case this is easier
[15:48]  * desrt cleans up the glib inline mess once and for all
[15:57] <didrocks> larsu: what this script being in nodejs, dart, go?
[16:02] <larsu> didrocks: your choice ;)
[16:03] <didrocks> \o/
[16:03]  * didrocks does it in perl then
[16:03] <didrocks> (j/k)
[16:03] <didrocks> well… https://metacpan.org/release/Git-Raw
[16:04] <larsu> didrocks: you've been pulled off this project. Effective immediately
[16:04] <larsu> don't even joke about doing stuff in perl
[16:04] <didrocks> :)
[16:04] <didrocks> I'll know next time I don't want to work on something
[16:04] <didrocks> just threat doing it in perl!
[16:05] <larsu> !
[16:10] <attente> how do i ensure the signal handlers are called in my new thread and not the main one?
[16:10] <larsu> attente: from gdbusproxy? They're called in the thread you create the proxy in
[16:12] <attente> larsu: so i have to create the proxy in a separate thread? it's not enough to create the server in a separate thread?
[16:12]  * attente doesn't know this stuff...
[16:17] <larsu> attente: wait. what?
[16:18] <larsu> you create the server in a thread, and create the proxy (which points to the server?) in the main thread?
[16:22] <larsu> brb
[16:24] <attente> oh i need two non-main threads?
[16:38] <larsu> attente: don't know what you talked about with desrt, but I'd assume you only need the one for the service and do the rest from the main thread
[16:45] <attente> :(
[16:56]  * Laney 's fingers slipped
[16:57]  * Laney is off to catch a train - ttyl!
[17:02] <didrocks> see you Laney!
[17:03] <didrocks> and see you guys, time to go off!
[17:39] <willcooke> Trevinho, andyrock, hikiko-lpt  -  I'd like to have our first Agile sprint planning and kick off this week.  andyrock is there a morning which works better for you this week?
[17:40] <willcooke> Wednesday morning is pretty good for me
[17:41] <Trevinho> willcooke: that's fine as well, not sure about andyrock (who maybe prefers afternoon)
[17:46] <hikiko-lpt> hello I just arrived home
[17:47] <hikiko-lpt> fosscomm :d
[17:47] <hikiko-lpt> wednesday is fine for me as well :)
[17:51] <seb128> hum
[17:51] <seb128> what cursor themes are using other distributions?
[17:52] <seb128> gedit throws warnings because we don't have "progress" and "text" in our default one, but it seems the other installed ones on Ubuntu also don't have those
[18:09] <willcooke> ok, I think I've just made my first ever MP
[18:10] <willcooke> larsu, it's trivial I know, and I should wait until I've got all my fixes in
[18:10] <willcooke> but I wanted to see if I could work out how to do it
[18:11] <willcooke> so feel free to reject or whatever
[18:21] <willcooke> oh, so I have to link to a bug at commit time
[18:23] <seb128> you can do that with --fixes lp:<nnn>
[18:24] <willcooke> but only at commit time?
[18:25] <seb128> you can do it on launchpad then
[18:25] <seb128> like add a branch to the bug
[18:25] <seb128> the commit in bzr log isn't going to have the bug reference if you do that
[18:25] <seb128> but it's good enough for the CI to have the reference in the changelog etc
[18:27] <willcooke> oki, I'll delete it and do it properly
[18:28] <seb128> you can "bzr uncommit" and then commit again
[18:28] <seb128> and then push --overwrite
[18:33] <willcooke> cool, thanks seb
[18:36] <seb128> yw!
[18:49] <larsu> willcooke: congrats! Off to a pub in a bit - will have a look in the morning
[20:12] <willcooke> Trevinho, https://bugs.launchpad.net/ubuntu-themes/+bug/1493607  <-- fixed right?
[20:12] <willcooke> I can close it if yes
[20:13] <Trevinho> willcooke: yep
[20:13] <willcooke> thx Trevinho
[20:13] <willcooke> done
[21:12] <willcooke> oh
[21:12] <willcooke> Hrm
[21:13] <willcooke> I thought that once I'd put up a branch for review then I would be free to continue working in that branch on other things and commit further changes to other bugs
[21:14] <willcooke> but it rather looks like the branch I put up for review earlier now includes a fix to the Gtk2 theme
[21:14] <willcooke> larsu, I've asked John Lea to ack the changes so please hold off for his OK before accepting.  Or if you want to reject, then you don't need to wait :)
[21:18] <willcooke> robert_ancell, when PS Jenkins Bot said "Needs Fixing" - how do I find out why it thinks that?
[21:18] <robert_ancell> willcooke, it should say in a comment
[21:19] <robert_ancell> what is the MP?
[21:19] <willcooke> ahhh
[21:19] <willcooke> I see
[21:19] <willcooke> thanks
[21:19] <willcooke> https://code.launchpad.net/~willcooke/ubuntu-themes/ubuntu-themes/+merge/277043
[21:21] <robert_ancell> willcooke, yeah, the commit message missing - I thought so. That one is a bit confusing.
[21:21] <willcooke> Yeah, because I certainly had a message
[21:23]  * Sweet5hark fixed 10 crashing race conditions today.
[21:23] <willcooke> \o/
[21:24]  * Sweet5hark now comfortably feels yoda speaking.
[21:27] <willcooke> right ho, quittin' time.  G'night all