15:32 <willcooke> #startmeeting Desktop Weekly Meeting 2015-02-10
15:32 <meetingology> Meeting started Tue Feb 10 15:32:54 2015 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
15:32 <meetingology> 
15:32 <meetingology> Available commands: action commands idea info link nick
15:32 * larsu hugs back
15:33 <willcooke> Roll call: mlankhorst, attente_, desrt, dgadomski, didrocks, FJKong_, happyaron, Laney, larsu, qengho, seb128, Sweet5hark, tkamppeter
15:33 <seb128> _o/
15:33 <mlankhorst> o/
15:33 <dgadomski> o/
15:33 <willcooke> hrm - that list doesnt look long enough - if I missed you, shout
15:33 * desrt drops a pencil on the floor, bends over to pick it up
15:33 <desrt> oh hai!
15:33 <didrocks> hey
15:33 <Sweet5hark> ohai
15:33 <FJKong_> hi
15:34 * FJKong_ feel sleepy
15:34 <willcooke> So slight change of order today, mlankhorst up first
15:34 <happyaron> hi
15:34 <willcooke> #topic mlankhorst
15:34 <larsu> willcooke: I'll be off in a bit. Status: hackfests.
15:34 <mlankhorst> preparing mesa 10.5~git snapshot, making mouse events work in XMir under unity8, reworking mouse support in xmir, and a bit sick last week :(
15:34 <willcooke> fosflu
15:34 <mlankhorst> in next upload rotation/2x mode should work correctly with mouse events
15:34 <mlankhorst> indeed!
15:35 <willcooke> thanks mlankhorst.
15:35 <willcooke> larsu, you want to go next or are you done?
15:35 <willcooke> #topic larsu
15:35 <larsu> oh sure
15:35 * larsu is caught on the spot
15:36 <larsu> lots of discussion at the hackfest
15:36 <larsu> still didn't get a gedit headerbars conclusion
15:36 <larsu> might get a theme refresh soon
15:36 <desrt> larsu: see rule #1
15:37 <larsu> what's that?
15:37 <desrt> "make seb happy"
15:37 <desrt> we have to add a toolbar :p
15:37 <seb128> :-)
15:37 <desrt> see?
15:37 <desrt> he's happy already
15:37 <larsu> or keep the old version...
15:37 <willcooke> (Oh, before you go mlankhorst, larsu - Reviews.  Check your email and backlog at the end of this meeting for (slightly) more info.)
15:37 <seb128> let's discuss that later
15:37 <mlankhorst> oke :-)
15:37 <larsu> I also hacked a bit on gnome-terminal, making it's --app-id support more sane (thanks Laney for providing a transition script)
15:38 <desrt> larsu: what's the deal on that?  do you need me to look at those patches soon or is it back to a 'nice to have at some point in the future' type bug now?
15:38 <larsu> pondered using gtk 3.16 for V - looking pretty good safe for some smaller issues
15:38 <desrt> looks like chpe wanted another approach
15:39 <larsu> desrt: soon. The way they do things now is stupid
15:39 <larsu> desrt: this way the stupidity is in gtk at least - which we might fix with a private gdk api
15:39 <larsu> but please review
15:39 * desrt appears supicious
15:39 <desrt> talk to me more about this later
15:40 <larsu> why?
15:40 <larsu> ok
15:40 <desrt> i think i've lost scope of what exactly you're trying to do :)
15:40 <larsu> did some bug fixes as well
15:40 <larsu> I probably forgot stuff again: but </lars>
15:41 <Laney> pink killers
15:41 <desrt> you guys missed a sweet last night
15:41 <willcooke> #topic attente_
15:41 <desrt> they serve pink killers in pint glasses, you know
15:41 <willcooke> oops - thanks larsu
15:42 <attente_> helped debug https://bugs.launchpad.net/ubuntukylin/+bug/1408212
15:42 <attente_> wip/mir2 merged into master upstream
15:42 <attente_> not sure what to do about https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1245925, prevents ibus and fcitx from working while maliit-framework is installed, and it's pulled in by ubuntu-desktop-next
15:42 <ubot5> Launchpad bug 1408212 in Unity "Turn on/off the Large Text in Universal Access, it doesn't work immediately" [High,In progress]
15:42 <ubot5> Launchpad bug 1245925 in maliit-framework (Ubuntu) "Troublesome export in /etc/profile.d/maliit-framework.sh" [Undecided,Confirmed]
15:42 <attente_> investigation about getting fcitx working under Mir. kind of works with the gtk backend in the mir demo shell with exception of the candidate window
15:44 <willcooke> attente_, any ideas who can assist with 1245925?  Do you want me to try and find someone?
15:45 <seb128> willcooke, attente_, I can help getting that moving
15:45 <Laney> it should at least check for maliit-keyboard being installed before setting the thing
15:45 <seb128> right
15:46 <attente_> i'm not sure, the problem seems to be that you can't really have both maliit and ibus/fcitx running simultaneously
15:46 <seb128> ideally it should set the env from an upstart job or something
15:46 <attente_> at least for qt apps
15:46 <seb128> or im-config need to learn to unset it
15:46 <seb128> ?
15:47 <attente_> maybe the right thing to do is to treat maliit on the same level as ibus/fcitx
15:47 <seb128> I think so
15:47 <happyaron> forcing maliit will get in the way of 3rd party keyboards as well, on iOS/Android people write their own
15:47 <happyaron> yep
15:48 <seb128> attente_, don't forget in your week summary that you bisected kernels to find a mir/intel regression
15:48 <happyaron> IIRC there was even ibus backend for maliit
15:48 <Laney> he bisected gtk too
15:48 <attente_> but it gets weird when you start switching between u7 and u8
15:48 <Laney> king of bisects
15:48 <seb128> Laney, that was his "helped debug ...." line
15:48 <Laney> by BISECTING
15:48 <seb128> rrrright
15:48 <seb128> got you ;-)
15:49 <willcooke> oki, sounds like between us we can work something out then
15:49 <willcooke> thanks attente_
15:49 <seb128> attente_, well, even on unity8, you might want to switch between osk and ibus/fcitx
15:49 <seb128> even in the same session
15:49 <seb128> like one screen being your docked phone and one being your docking stating external monitor
15:49 <attente_> seb128: yeah, this is bad for us
15:49 <seb128> so we need something more dynamic that the env at some point
15:50 <attente_> happyaron: we can kind of resolve it for not-qt apps by making im-config override empty GTK_IM_MODULE for example, but i'm not sure what else can be done for qt apps
15:50 <attente_> right
15:51 <seb128> let's discuss that after meeting
15:51 <happyaron> ok
15:51 <seb128> maybe the devel list would be better for that
15:51 <seb128> more people/potential ideas
15:51 <willcooke> great, thanks chaps
15:51 <willcooke> #topic desrt
15:51 <desrt> hi!
15:52 <desrt> was in hackfest mode last week as well
15:52 <desrt> got a lot of useful engineering work done on stuff like mir, content hub, etc.
15:52 <Laney> - git wwpd
15:52 <desrt> wrote a neat thing called git wwpd :)
15:52 <desrt> people seem to like that...
15:52 <desrt> uh... mostly recovering from sickness and had a swap day yesterday so not a lot to report since the sprint
15:53 <Sweet5hark> .oO(what would the pope do?)
15:53 <desrt> Sweet5hark: what would 'push' do
15:53 <willcooke> thanks desrt
15:53 <desrt> displays a list of commits that would be sent to the server as a result of a particular 'git push' command
15:54 <willcooke> #topic dgadomski
15:54 <Laney> next step is to wrap git push and add a confirmation step
15:54 <dgadomski> hello everyone
15:54 <dgadomski> - got a fix for bug #1337873, will ask for more feedback after initial tests show no regression (it used to happen every 1-2k reboots, testing takes a while)
15:54 <ubot5> bug 1337873 in ifupdown (Ubuntu) "Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition" [Undecided,In progress] https://launchpad.net/bugs/1337873
15:54 <dgadomski> - back to analyzing bug #1104230 fix regression since kernel ~3.16.0-27
15:54 <ubot5> bug 1104230 in xserver-xorg-video-intel (Ubuntu) "DisplayPort 1.2 MST support is missing in the Intel driver" [Undecided,Confirmed] https://launchpad.net/bugs/1104230
15:54 <dgadomski> - analyzing a Network Manager issue - will prepare a lp bug for that, does anyone specialize in the network manager area to check if this is a known problem?
15:55 <Laney> c_yphermox does
15:55 <seb128> dgadomski, you can describe the bug on the channel after the meeting
15:55 <seb128> or check launchpad/bugzilla
15:56 <dgadomski> I will surely search first, just need to understand what is going on there exactly
15:56 <dgadomski> thanks
15:56 <dgadomski> EOF from me
15:56 <willcooke> thanks dgadomski
15:57 <willcooke> #topic didrocks
15:57 <didrocks> hey
15:57 <didrocks> Developer desktop:
15:57 <didrocks> - Added android NDK support to ubuntu make (not released yet). mhall119 should be happy about it.
15:57 <didrocks> - Workaround the "add a new unity launcher item  bug". Users should be happy this.
15:57 <didrocks> - patched pip install to do the right thing by default (not trying to install system-wide and get a traceback on pip install). aquarius should be happy about that.
15:57 <didrocks> - checked that others developer packaging systems are doing sane local install by default (rubygem, npm, bower…).
15:57 <didrocks> - Note that this put pressure on upstream to get this issue finally fixed (the topic was stalled for quite a while), and I proposed our help and backport an upstream fix this cycle (mostly same behavior). Barry should be happy with the final solution.
15:57 <didrocks> systemd:
15:57 <didrocks> - wrote and rewrote fsck<->plymouth integration patch first using epoll and then using systemd mainloop. Proposed upstream and waiting for a review now. pitti should be happy once it's merged.
15:57 <didrocks> - dropped libplymouth dependency, investigate and talk directly the raw protocol. Lennart should be happy with the replacement.
15:57 <didrocks> misc:
15:57 <didrocks> - MIR and AA duties. No-one can ever be happy about doing those.
15:57 <didrocks> - planned ahead to get sick a week before the sprint to NOT get fosflu. Success so far… I'm happy \o/
15:57 <didrocks> this whole week was about to make people happy :)
15:57 <didrocks> EOW
15:58 <willcooke> thanks didrocks
15:58 <pitti> haha
15:58 <pitti> hahahappy!
15:58 <didrocks> :p
15:58 <Laney> you should have seen him writing the plymouth code
15:58 <Laney> not happy!
15:58 <desrt> ya... particularly the 3rd time he was doing it
15:58 <willcooke> :D
15:58 <pitti> {blood,sweat,tears}²
15:59 * pitti hugs didrocks
15:59 * Laney hugs didrocks
15:59 <didrocks> Laney: yeah, other were happy, not I! :)
15:59 * desrt hugs didrocks
15:59 * didrocks hugs you back
15:59 <willcooke> #topic FJKong_
15:59 <FJKong_> * do some research on gif skin display for sogou IM, not easy to load gif skin from memory, needs more time fix it
15:59 <FJKong_> * bug 1413865 No default setting for "When power is critically low" in Power settings, still in progress
15:59 <ubot5> bug 1413865 in Ubuntu Kylin "No default setting for "When power is critically low" in Power settings" [Medium,Confirmed] https://launchpad.net/bugs/1413865
15:59 <FJKong_> * upload pinyin search code to github
15:59 <FJKong_> * take two day off
15:59 <FJKong_> not much to update
16:00 <willcooke> FJKong_, you are off next week right?
16:00 <FJKong_> willcooke: not all
16:01 <FJKong_> willcooke: next next maybe
16:01 <willcooke> kk, well if we don't speak before Thursday, have a great new year :)
16:01 <FJKong_> willcooke: thanks all
16:01 <willcooke> #topic happyaron
16:01 <happyaron> 1. Update most of the packages related to fcitx, prepare for the MIR again (sorry…)
16:01 <happyaron> 2. Fix symbols craziness of libgooglepinyin and fcitx-qt5
16:01 <willcooke> And a happy new year for next week happyaron as well :)
16:01 <happyaron> 3. Fix 6 bugs assigned from Ubuntu Kylin
16:02 <happyaron> thanks
16:02 <happyaron> over
16:02 <willcooke> thanks for the update happyaron
16:02 <willcooke> bed time now :)
16:02 <willcooke> #topic Laney
16:02 <Laney> • Sprinting last week, working on a few things such as
16:02 <Laney> ∘ A wrapper script for gnome-terminal to provide compatibility with old launchers
16:02 <Laney> ∘ Packaging snapshot of gtk, glib, overlay-scrollbars with GTK3 stuff disabled for evaluation of a possible switch in 15.04
16:02 <Laney> ∘ Fix some FTBFS in vivid test rebuild
16:02 <seb128> happyaron, FJKong_: happy new year :-)
16:02 <Laney> • Upload gtk 3.14 latest release with patches to fix setting the text scaling factor
16:03 <Laney> • Cherry pick the upstream patch to fix nautilus' glib signal connection order for background switching
16:03 <Laney> • Look at totem 3.14, should be fine after another round of bug fixes, working with darkxst on this
16:03 <Laney> • Poke a bit at gnome-screenshot 'flash' breaking on new gtk (involved bisecting gtk!), think larsu is looking at this now
16:03 <Laney> ❂
16:03 <willcooke> thanks Laney
16:03 <desrt> best part of the meeting is looking forward to Laney's choice of unicode
16:03 <willcooke> :D
16:03 <willcooke> #topic qengho
16:03 <willcooke> qengho is off today, but:
16:04 <willcooke> Released Chromium 40.0.2214.94. Prepared 40.0.2214.111, which should be out today. I'm back at work Thursday.
16:04 <willcooke> New Chromium \o/  thanks qengho
16:04 <willcooke> #topic seb128
16:04 <seb128> indeed \o/
16:04 <seb128> • looked at the vivid archive test rebuild, fixed some build issues
16:04 <seb128> • investigate libpwquality not being translated
16:04 <seb128> • fixed incorrect label wrapping in u-s-d free disk space dialog
16:04 <seb128> • backported g-c-c change to fix u-c-c build with new n-m, cleaned out some deprecation warnings as well
16:04 <seb128> • helped testing fixes for bluetooth/n-m segfaults
16:04 <seb128> • some sponsoring (new chromium)
16:04 <seb128> • looked at undefined symbol issue in gnome-bluetooth, hit libtool issues trying to fix the issue, opted rather to disable the plugin which is not useful/buggy (upstream dropped it in 3.10 as well)
16:04 <seb128> • ubuntu-system-settings
16:04 <seb128> ∘ implemented bluetooth ssp profile pairing
16:04 <seb128> ∘ disabled bluetooth pairing action for unsupported device types
16:04 <seb128> • usual share of desktop related bugs triages and discussions
16:04 <seb128> </week>
16:05 <willcooke> thanks a lot seb128
16:05 <willcooke> seb128, new kdb should be on its way to you
16:05 <FJKong_> seb128: thanks new year holiday start at 18th Feb to 24th :)
16:05 <seb128> willcooke, great
16:05 <seb128> FJKong_, noted!
16:05 <willcooke> FJKong_, happyaron - Beijing office is closed next week, so I expect most folk will be afk
16:06 <willcooke> #topic Sweet5hark
16:06 <Sweet5hark> - FOSDEM
16:06 <Sweet5hark> - TDF Board of Directors meeting
16:06 <Sweet5hark> - some employee meeting and Hackfest (but already on the way to sickness then :/)
16:06 <Sweet5hark> - flight home and three days (plus weekend) under fosdem flu: sneeze, sob, sneeze
16:06 <Sweet5hark> - prepared 4.4.0.3 for vivid
16:06 <Sweet5hark> - checked for horror regressions by mergedlibs, didnt find any so far
16:06 <Sweet5hark> - bug 1419836 seems interesting: doesnt happen upstream, but isnt mergedlibs related (checked rc2 vs. rc3)
16:06 <Sweet5hark> - bug 1419521 same, could use help from tkamppeter to figure out whats going on ...
16:06 <Sweet5hark> - /me heard about perf reviews, distributes free virtual lollypops
16:06 <FJKong_> willcooke: yes most of them will travel back to home ahead of days
16:06 <Sweet5hark> EOF
16:06 <ubot5> bug 1419836 in libreoffice (Ubuntu) "LibreOffice 4.4 (PPA): Extension can't be installed: Message: com.sun.star.uno.RuntimeException) "unknown error!"" [Undecided,Incomplete] https://launchpad.net/bugs/1419836
16:06 <ubot5> bug 1419521 in LibreOffice Productivity Suite "LibreOffice 4.4.0.3 broke printing" [Medium,Incomplete] https://launchpad.net/bugs/1419521
16:06 <willcooke> thanks Sweet5hark
16:06 <willcooke> #topic tkamppeter
16:07 <tkamppeter> - system-config-printer: Trusty SRU completed
16:07 <tkamppeter> - CUPS: Update to CUPS 2.0.2 in Ubuntu (Debian is in freeze, therefor they are currently not working on updates like this.
16:07 <tkamppeter> - cups-filters: Working on a PPD generator for auto-discovered network printers
16:07 <tkamppeter> - Bugs.
16:07 <willcooke> thanks tkamppeter
16:07 <willcooke> #topic robert_ancell
16:07 <willcooke> Worked on:
16:07 <willcooke> - TPM support - can finally log into my test machine using a binary
16:07 <willcooke> passphrase stored in TPM
16:07 <willcooke> - Fix seahorse FTBFS
16:07 <willcooke> Currently working on:
16:07 <willcooke> - TPM support (tidy up tools and start work on installer support)
16:07 <willcooke> - Updating Indic font packages (blocked on archive admin team removing
16:07 <willcooke> package block)
16:08 <willcooke> #topic willcooke
16:08 <willcooke> So, yeah, you know how I said we had ages to do the reviews? Well, I was lying.
16:08 <willcooke> Due Friday people
16:08 <willcooke> sorry
16:09 <willcooke> If you have have your personal review done by then, and have emailed me your 360 people, that'll be grand
16:09 <willcooke> The other thing I wanted to follow up on was https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1418295
16:09 <ubot5> Launchpad bug 1418295 in xserver-xorg-video-intel (Ubuntu) "Black screen after resuming from suspend" [Critical,Confirmed]
16:09 <willcooke> Just because it's a critical one
16:10 <willcooke> From the comments I think it's now almost agreed that it's a U7 issue
16:10 <willcooke> so I will follow up with those guys.
16:10 <willcooke> I'm going to London tomorrow - so if anyone needs anything from there let me know
16:10 <willcooke> the office I mean,
16:10 <seb128> willcooke, is that new that we need to go through you to ask for peer reviews?
16:10 <willcooke> not the ships
16:10 <willcooke> shops
16:10 <seb128> usually we could ask those directly
16:11 <willcooke> seb128, wellll. the docs say you email me and then I add it to the HR system.  I don't know if that's new or not, so let's just say it is
16:11 <seb128> k
16:11 <willcooke> That is
16:11 <willcooke> I just add that person as a reviewer
16:11 <Laney> we got this new system since then
16:11 <seb128> yeah, we didn't use the new website for that yet
16:11 <willcooke> and then the system emails them
16:11 <seb128> seems a step backward compared to the old system
16:11 <willcooke> right kk
16:11 <seb128> but let's see
16:11 <willcooke> yes
16:11 <Laney> so you're saying this part is not optional?
16:12 <willcooke> that's my (new) understanding yes
16:12 <willcooke> msg me if you want to talk about it
16:12 <Laney> interesting, ok
16:13 <willcooke> #topic any other business
16:13 <willcooke> going once
16:13 <Laney> stoppppppp
16:13 <didrocks> :p
16:13 <seb128> thanks :-)
16:13 <willcooke> Yes - the gentleman in the top hat
16:13 <Laney> GTK 3.15
16:13 <seb128> oh, that!
16:13 <Laney> I think there a few more issues than I expected
16:13 <Laney> so I'm becoming a bit more wary
16:14 <Laney> what do others think?
16:14 <seb128> it makes me a bit nervous, especially because of the new toolbars that we didn't really test yet (nor try to make look like we want)
16:14 <seb128> but we still have some time in the cycle
16:15 <willcooke> I'm a bit wary also, seems late in the cycle and a few too many unknowns and bugs for my liking.
16:15 <willcooke> seb128, do we have time?  Is this not a feature?
16:15 <didrocks> there is going to be a period when landing it will break things… depends if we agree about regressing our desktop or not
16:15 <seb128> didrocks, what sort of regressions are we talking about?
16:15 <Laney> and gnome's
16:16 <didrocks> seb128: the new toolbars "unknowness" for instance?
16:16 <seb128> willcooke, we, it's a feature to land it, it's not a feature to tweak more i.e the look of the scrollbars after ff
16:16 <willcooke> seb128, ack
16:16 <seb128> didrocks, well, that's something we need to resolve before landing
16:16 <Laney> not all applications will use the new scrollbars currently either
16:17 <Laney> e.g. webkitwebviews or vte widgets
16:17 <seb128> what would happen to e.g software-center then?
16:17 <Laney> normal scrollbar
16:18 <seb128> what was the reason we wanted to update gtk this cycle again?
16:18 <Laney> scrollbars :)
16:18 <seb128> I see
16:18 <Laney> there's still some black background cases
16:18 <seb128> g-s-m being the only known one we had to disable scrollbars for, right?
16:18 <Laney> ya
16:19 <seb128> I fear a bit that the new scrollbars are going to feel like a regression
16:19 <Laney> I think so
16:19 * FJKong_ say --. -.
16:19 <seb128> but we need to deal with that at some point, not sure if delaying but a cycle buy us much
16:19 <seb128> at the same time there is no strong need to update
16:20 <seb128> so we could play safe
16:20 <Laney> and there's other issues like black notifications on the greeter and whatever else I mentioned
16:20 <seb128> especially that we still have the systemd and bluez transitions to come this cycle
16:20 <Laney> 6 (8) months to work on it instead of 2
16:20 <Laney> people can work on it out of the ppa so it's better at the start of next cycle, if they have time
16:20 <Laney> the time-based release thing
16:20 <seb128> +1 for delaying
16:21 <willcooke> +1
16:21 <seb128> it feels like we are going to get some unexpected side effect
16:21 <seb128> and history tells it's better to do that when cycle open than at ff
16:21 <Laney> larsu was for it though, will be sorry to disappoint him
16:21 <willcooke> we can land it nice and early next release, plus there might be a theme change needed too - so we could combine that in?
16:21 <willcooke> you snooze you lose
16:21 <willcooke> ;p
16:22 * seb128 hugs larsu
16:22 <seb128> well, we can decide on that
16:22 <seb128> larsu can still try to convince us in the next days, nothing blocks us to revisit next week
16:22 <seb128> in case there is a status quo change
16:22 <willcooke> good point
16:22 <Laney> well
16:22 <Laney> it means that the gnome guys have to do some different work
16:23 <seb128> well, status is that we stay on what we have
16:23 <seb128> we can still see if people can sync on something else in the next week
16:23 <seb128> even if that's not likely
16:23 <Laney> works for me
16:23 <Laney> I think it was good to try
16:24 <seb128> I would like to at least let a chance to larsu to convince us when he's back, if he really thinks we should go with the new version
16:24 <Laney> because now we know issues to work on in an idle handler
16:24 <seb128> right
16:24 <Laney> style scrollbars, fix notifications, get them working on more apps, find out the nvidia problem, ...
16:24 <seb128> right
16:25 <Laney> cool
16:25 <Laney> moving on then
16:25 <seb128> + the gnome decoration issues
16:25 <seb128> + probably some extra bugs
16:25 <seb128> thanks Laney
16:25 <seb128> willcooke, seems like that's a wrap then :-)
16:25 <Laney> i'm assuming that one is fixed in 3.16 of mutter & gsd, but yes
16:25 <Laney> s/gsd/gs/
16:26 <willcooke> oki
16:27 <willcooke> One last thing then.. willcooke and Mrs willcooke are expecting the delivery of twin boys in May.  \o/
16:27 <willcooke> Hence no China trip for me
16:27 <Laney> yay!
16:27 <willcooke> #topic endmeeting
16:27 <Laney> congrats :-)
16:28 <willcooke> thanks Laney
16:30 <seb128> willcooke, congrats!
16:31 <desrt> willcooke: congrats :)
16:32 <attente_> +1
16:32 <attente_> or +2
16:32 <willcooke> :D thanks chaps
16:33 <Laney> oh that reminds me that I got some new pics of you-know-who ;-)
16:34 * desrt readys telegram
16:34 <desrt> piano lessons already!
16:34 <Laney> better than me tbh
16:35 <willcooke> :D
16:48 <Laney> hmm
16:49 <Laney> I'm getting notifications with actions from nm-applet
16:53 <seb128> Laney, so fallback dialogs?
16:53 <Laney> yes
16:53 <seb128> seems like a bug worth pointing to cyphermox
16:53 <Laney> could be me somehow
16:53 <seb128> when doing what/when?
16:53 <cyphermox> uh oh
16:53 <Laney> well for one I'm on xmonad ;-)
16:54 <Laney> but there's notify-osd and no notification-daemon
16:56 <Laney> yeah I restarted nm-applet and it's okay now
16:57 <Laney> cyphermox: stand down
16:57 <Laney> :)
16:57 <cyphermox> ok
16:57 <cyphermox> ;)
16:57 <cyphermox> glad I can still focus on plymouth, I think I'm getting somewhere finally
16:58 <Laney> you and didrocks can have a mutual counselling session
16:59 <Laney> apparently the codebase is fun to work with
16:59 <cyphermox> hahaha
17:04 <mhall119> didrocks: \o/
17:07 <Sweet5hark> seb128: suggesting for upload: http://people.canonical.com/~bjoern/vivid/4.4.0/libreoffice_4.4.0-1ubuntu1_source.changes and http://people.canonical.com/~bjoern/vivid/4.4.0/libreoffice-l10n_4.4.0-1ubuntu1_source.changes
17:08 <seb128> Sweet5hark, need sponsoring or just review?
17:09 <Sweet5hark> seb128: sponsoring. is: upstream rc2->rc3, completes mwaw MIR, reenables mergelibs
17:16 <happyaron> didrocks: mind have a look at fcitx MIR again? everything in your last message have been dealt with
17:25 <willcooke> seb128, can you try something on your U8 machine - from lightdm enter the wrong password - do you get the password box increasing in size?
17:25 <willcooke> and do you get the session icon just turning black?
17:26 <seb128> willcooke, neither of those, didn't update since friday though
17:26 <willcooke> seb128, mine is even older I think
17:26 * willcooke upgrades
17:28 <Laney> what's GDK_KEY_OpenURL?
17:41 <didrocks> happyaron: I'll have a round tomorrow or thursday
17:42 <didrocks> happyaron: but please first change the component status for everything you fixed (as told last time)
17:43 <didrocks> happyaron: that's easier for us to track then :)
17:44 <didrocks> Laney: I see now why when walking to the doctor I receive some unexpected telegram photos :)
17:44 <didrocks> willcooke: congrats!
17:44 <Laney> \o/
17:48 <willcooke> thx didrocks
17:52 <willcooke> seb128, update has fixed most things, but I might have found a bug...  could you try this tomorrow:
17:54 <willcooke> 1.  Log in to U8.  2.  With the mouse/touchpad click on the wifi indicator some times (I did it three or four I think). Dont drag down, just click so that it expands a little way, then release.   3.  Without moving the pointer touch the wifi indicator.  4.  CPU @ 100% U8 unresponsive.  5.  sad face.
17:59 <seb128> willcooke, sure can try
17:59 <seb128> willcooke, but for me trying to open the power indicator is enough to screw things
17:59 <willcooke> heheh
17:59 <willcooke> let me try that
18:00 <willcooke> yup
18:00 <willcooke> my elaborate dance was for nought
18:04 <seb128> hehehe
18:17 * didrocks waves good evening and good night
18:17 <willcooke> cya
18:17 <desrt> didrocks: ciao
18:17 <desrt> good evening
18:17 <didrocks> see you guys :)
18:40 <willcooke> oh, 360 reviews are super simple and quick
18:40 * willcooke -> dinner
18:42 * Laney the de-dialog-headerbarerer
18:42 <Laney> goodnight!
18:58 <larsu> night Laney
19:28 <robert_ancell> larsu, do you want bug 1396700 assigned to you?
19:28 <ubot5> bug 1396700 in indicator-bluetooth (Ubuntu) "Needs to be updated to bluez5" [High,In progress] https://launchpad.net/bugs/1396700
19:31 <larsu> robert_ancell: sure :)
19:31 <larsu> also, hi! How are you?
19:31 <robert_ancell> larsu, good, yourself?
19:31 <robert_ancell> mterry, any idea why my (Nexus 4) phone greeter always shows "No data sources available"?
19:31 <larsu> robert_ancell: good good, thanks. Just came back home after conferences and sprints
19:32 <robert_ancell> larsu, yeah, sounded like fun!
19:32 <mterry> robert_ancell, no :-/
19:32 <mterry> robert_ancell, sounds like a bug with libusermetrics?
19:33 <larsu> robert_ancell: it was! And exhausting. Caught Fosdemflu
19:33 <robert_ancell> mterry, is there a greeter log or anything I can check?
19:33 <robert_ancell> larsu, :(
19:33 <robert_ancell> mterry, or does the greeter just use a widget
19:37 <mterry> robert_ancell, we have our own widget
19:37 <mterry> robert_ancell, so it *could* be that failing
19:38 <mterry> robert_ancell, you could check ~/.cache/upstart/unity8.log to see if there's anything that looks like an infographics error
19:38 <mterry> robert_ancell, there will be lots of noise though
19:38 <mterry> robert_ancell, I'm not sure where libusermetrics outputs to
19:38 <mterry> robert_ancell, poke pete-woods for help with that
19:39 <mterry> robert_ancell, actually, looking at my own daily driver phone, I'm seeing that too
19:39 <mterry> robert_ancell, I think I forgot that was a feature
19:39 <mterry> robert_ancell, let's move to #ubuntu-touch and pull pete-woods in
19:39 <robert_ancell> mterry, yeah, it's always been broken on my Nexus 4. I wondered if it was just a feature for production phones
19:43 <attente_> bschaefer: hey, you were right, i managed to get fcitx input working under the demo server
19:43 <bschaefer> attente_, woooooooots!
19:43 <bschaefer> attente_, what was the issue?
19:43 <attente_> it's just missing the candidate window popup
19:43 <bschaefer> yeah that expected
19:43 <willcooke> nice attente_
19:43 <bschaefer> attente_, does it pop up behind the main window?
19:44 <willcooke> morning robert_ancell
19:44 <robert_ancell> willcooke, hello
19:44 <bschaefer> attente_, as.... IIRC its pretty much just a menu?
19:45 <attente_> bschaefer: it doesn't pop up at all, because that's being done in a separate process
19:45 <bschaefer> ooo yeah, thats done after the dbus call to the actual server
19:45 <attente_> but the committing of the test actually works
19:45 <bschaefer> sweet!
19:45 <attente_> if you need to get it working, you just need to update the local version of immodules.cache that it's looking up
19:45 <bschaefer> i guess the fun part now is ... how to get an out of process window to render on an app? (I dont think mir wants that?)
19:46 <bschaefer> attente_, naw, knowing it works was the main test :)
19:46 <attente_> and add a reference to the system location of the im-fcitx.so
19:46 <attente_> :)
19:46 <bschaefer> cool, ill have to give that a test at some point
19:46 <bschaefer> attente_, soo that means, gtk and qt
19:46 <attente_> yeah, the next part is to figure out how to get fcitx-qimpanel working under the demo server environment
19:47 <bschaefer> should have IM support already.... the only other issue do we want mir to support IMs if a toolkit talks directly to mir
19:47 <bschaefer> ie. SDL2/SDL1.2
19:47 <attente_> yeah... i guess we need that still
19:47 <bschaefer> though i know SDL2 has ibus support meaning it will do the talking to ibus
19:48 <bschaefer> attente_, the only issue with that is... mir would have to expose some fun parts ... i would think?
19:48 <bschaefer> then we would then have to write backends in ibus/fcitx ... a lot of work for little gain
19:48 <bschaefer> kgunn, ^
19:49 <bschaefer> attente_, but i suppose thats something we can discuss later haha, the main part is to get it working for 80-90% of the cases :)
19:49 <willcooke> sounds like a very sensible plan to me :)
19:49 <attente_> i'd be happy if we could just get the candidate window working :)
19:50 <bschaefer> very! though thats going to be interesting...now that we know its an out of process window
19:51 <bschaefer> attente_, im not sure how mir will want to handle that... as i think that would mean we need some sort of trusted session?
19:52 <bschaefer> attente_, do you know of any other programs that use out of process windowing like input methods?
19:52 <attente_> i guess osk? but it seems like it gets treated the same
19:53 <bschaefer> soo then how does an osk work ... like mallite? (i cant spell it)
19:53 <attente_> maybe there's some a11y stuff that we don't know about
19:53 <bschaefer> i know its through some trusted session though im not sure how that would work
19:53 <bschaefer> attente_, yup, possibly questions in #ubuntu-mir
19:53 <attente_> maliit works as a qt im-module afaict
19:54 <bschaefer> im not sure what that is :) ... but it seems to get a window rendering on top of the running process
19:54 <bschaefer> that then accepts input
19:55 <bschaefer> sooo thats pretty much what we would need for the input method preedit window
19:55 <attente_> i think the window has little to do with the actual input because fcitx still can detect the keystrokes despite not having a surface in the demo server
19:56 <bschaefer> attente_, yeah fcitx will get the events through filter key press
19:56 <bschaefer> soo it doesn't *need* input it self it just needs to render above everything at the correct location
19:57 <bschaefer> its quite nice actually (the way it takes events) but pretty much the preedit window is only good for rendering
19:57 <bschaefer> i dont think... it normally takes events?
19:57 <attente_> makes sense. i guess that window still needs to respond to pointer events though
19:57 <bschaefer> yeah it seems to respond on X11 to a pointer
19:59 <bschaefer> hmm i wonder why the window doesn't pop up somewhere... even if its out of process....maybe mir rejects it?
19:59 <bschaefer> you would think, even if something out of process requests a window... the window would still appear?
20:00 <attente_> it's probably popping up on vt 7
20:01 <bschaefer> o interesting, yeah...i wonder if you get something working on a unity8 desktop?
20:01 <bschaefer> if it would pop up somewhere...
20:01 <bschaefer> though i could be behind the surface (though i think it would just be rejected)
20:01 <bschaefer> attente_, also, how did you figure out the issue? (Some what curious haha)
20:02 <bschaefer> as what does immoudules do?
20:03 <attente_> bschaefer: yep. it's popping up on vt 7
20:03 <bschaefer> nice, soo now ... why does it think vt7 should own it?
20:03 <bschaefer> possibly it just assumes DISPLAY=:0?
20:03 <bschaefer> attente_, where did you run the server on? the umm fcitx server?
20:04 <bschaefer> ie. what happens if you run the fcitx server from tty1 or tty2 and aim it at gtk for mir?
20:04 <attente_> the fcitx-qimpanel process is just started from my X session
20:04 <attente_> when the session started
20:04 <attente_> which i guess explains why it's on vt 7
20:04 <bschaefer> i see, what happens if you attempt to run that on the demo?
20:04 <bschaefer> yeah
20:05 * bschaefer assumes its something like python/gtk or something?
20:05 <attente_> fcitx-qimpanel expects an X server it seems
20:05 <attente_> fcitx-qimpanel: cannot connect to X server
20:05 <bschaefer> sweet, now we know what to hack to get to work now :)
20:06 <bschaefer> though ... i wonder why it expects x11...
20:08 <bschaefer> where does qimpanel even come from?
20:08 <bschaefer> fcitx-ui-qimpanel
20:08 <bschaefer> haha nm...
20:08 <attente_> yep :)
20:08 <bschaefer> weird i didn't even have that installed?
20:08 <bschaefer> is that the only way to render the panel?
20:09 <bschaefer> fcitx-module-kimpanel
20:09 <attente_> fcitx comes with its own, but not many seem to be using it
20:09 <bschaefer> that makes sense
20:09 <bschaefer> attente_, for all we know it could just hard code a check for the DISPLAY
20:09 * bschaefer hopes its not a hard depends
20:10 <attente_> bschaefer: i'll have to look into it more, but i guess it depends on qt, and is using an x11 backend
20:10 <bschaefer> attente_, that makes sense, i wonder if you can force the mir backend?
20:10 * bschaefer doesn't know much about the qt port it self
20:10 <bschaefer> attente_, but awesome :)
20:11 <bschaefer> at lease you've something to track down haha
20:11 <attente_> yeah. i've never tried running a qt app under the demo server :)
20:11 <bschaefer> once that works...i hope the window renders over the mir app :)
20:11 <bschaefer> attente_, good luck!
20:11 <attente_> bschaefer: thanks :)
20:11 <bschaefer> also feel free to poke me if you need something tested or anything!
20:12 <attente_> will do
21:05 * willcooke -> EOD
21:05 <willcooke> g'night
23:40 <koding123> so what is the point of using Ubuntu Make( https://wiki.ubuntu.com/ubuntu-make ) instead of a package specific PPA?
00:39 <koding123> so what is the point of using Ubuntu Make( https://wiki.ubuntu.com/ubuntu-make ) instead of a package specific PPA?
05:40 <pitti> Good morning
06:24 * Mirv would like to file a bug "Abiword started launching on each login in vivid"...
06:43 <darkxst> hey pitti
06:43 <darkxst> did you get a chance to look at my systemd mount bug?
06:44 <pitti> darkxst: not yet, sorry; but still high on my list (probably today)
07:21 <darkxst> pitti, no problem, its just annoying me while constantly rebooting trying to fix gdm XRandr errors ;(
07:22 <didrocks> morning
07:22 <pitti> darkxst: you could try adding "mount -a" to /etc/rc.local
07:22 <pitti> darkxst: as a workaround
07:22 <pitti> hey didrocks, ça va ?
07:24 <didrocks> pitti: ça va, et toi ?
07:25 <pitti> didrocks: je vais bien aussi; trop de systemd bugs :)
07:27 <didrocks> argh :) j'ai lu hier le problème avec les symlinks
07:28 <didrocks> pitti: I guess I'm going to upload the protocol support in plymouth for fsckd, it does only add a new stenza for fsckd: and keys:
07:28 <didrocks> doesn't impact existing behavior
07:29 <didrocks> for the rest, we'll see once Lennart would review the patches
07:30 <pitti> didrocks: sure, that sounds fine
07:30 <darkxst> pitti, ok will try that
07:31 <pitti> didrocks: it seems Lennart is back from Brno and catching up with the ML, I hope we can get this in soon; otherwise I'll pull them into the ubuntu packages if you want
07:32 <didrocks> pitti: yeah, let's give another couple of days
07:33 <didrocks> pitti: I'm catching up on developer stuff before feature freeze during this systemd-less time :)
07:34 <seb128> good morning desktopers
07:34 <seb128> hey didrocks pitti
07:34 <didrocks> salut seb128
07:34 <pitti> bonjour seb128, ça va ?
07:35 <seb128> pitti, oui, et toi ?
07:35 <darkxst> hey seb128 didrocks
07:35 <seb128> hey darkxst
07:37 <darkxst> speaking of FF, anything blocking baobab, gnome-contacts etc other than titlebar patches?
07:37 <pitti> seb128: ça va bien aussi
07:38 <seb128> darkxst, didn't look at those, but probably not
07:38 <darkxst> and gedit, but I have no plans to implement the OSX ui, just de-headerbar ot?
07:38 <darkxst> ok
07:40 <darkxst> vino I suppose is blocked on bug 1271358
07:40 <ubot5> bug 1271358 in vino (Ubuntu) "Update to 3.12" [Wishlist,In progress] https://launchpad.net/bugs/1271358
07:41 <seb128> yes
07:41 <seb128> gedit, larsu and Laney were looking at it
07:41 <seb128> larsu added back the traditionnal menubar and decoration
07:41 <seb128> but it looks weird without a toolbar
07:41 <seb128> it also means the standard actions are not easily available
07:41 <seb128> (save, open, print, etc)
07:42 <seb128> so it's under discussion
07:42 <seb128> we might want to not update or to add a toolbar back
07:44 <darkxst> seb128, well the toolbar is there in the code, kinda
08:37 <seb128> didrocks, pitti, seems like http://launchpadlibrarian.net/196013611/casper_1.349_1.350.diff.gz is not working, do you have any idea why that could be the case?
08:39 <pitti> seb128: s/./:/ ?
08:39 * didrocks looks
08:39 <seb128> pitti, shrug, could be indeed ... do we have logs somewhere that could should the error?
08:39 <didrocks> yeah, should be $USER:$GROUP
08:40 <pitti> hm no, . works as well
08:40 <didrocks> oh, really?
08:40 <seb128> didrocks, ^
08:40 * didrocks learnt something today
08:40 <pitti> it's not documented, but I just tried it here
08:40 <seb128> I think I copied the line from somewhere else in casper
08:40 <pitti> didrocks: better don't :)
08:40 <didrocks> seb128: logs, you can see it at boot normally, but that's it
08:40 <didrocks> pitti: yeah, agreed, I lived quite happily without it :p
08:40 <didrocks> no obvious typo at least…
08:41 <seb128> ubiquity-hooks/30accessibility:		chroot /target chown -R $TARGET_USERNAME.$TARGET_USERNAME /home/$TARGET_USERNAME/.local
08:41 <didrocks> seb128: first boot, non persistent system I guess?
08:41 <seb128> didrocks, are those run at boot?
08:41 * seb128 tries
08:41 <seb128> do you know that log to look at?
08:41 <didrocks> seb128: yeah, really early at boot, and rerun at every boot
08:42 <didrocks> seb128: you won't find logs I guess, it's written on the console before the kernel loads AFAIK, but if you remove "quiet", you should see them
08:42 <didrocks> seb128: you can launch them by hand though
08:42 <pitti> seb128: you could boot with break=casper-bottom, there you might see some error messages and can also run stuff manually
08:42 <pitti> no, kernel loads before, that's the initramfs
08:44 <pitti> yeah, I see some "failed to change ... 1000 .. blabla" error messgae
08:44 <pitti> (without quiet)
08:44 <pitti> but why 1000, I thought it was 999
08:44 <pitti> ah no, that was another error message, I still see it on vt1 now
08:44 <larsu> good morning!
08:44 <seb128> hey larsu
08:45 <pitti> chown: unknown user/group ubuntu:ubuntu
08:45 <pitti> seb128: ^
08:45 <seb128> pitti, danke
08:45 <pitti> seb128: boot without quiet and check VT1
08:45 <didrocks> did you run that before the user is created?
08:45 <seb128> didrocks, I guess so? where is the user added?
08:46 <pitti> ./scripts/casper-bottom/25adduser
08:46 <seb128> so 51... should be after?
08:47 <pitti> seb128: no, the problem is that teh initramfs doesn't know this user
08:47 <pitti> try this: chroot /root "chown -R $USERNAME.$USERNAME /home/$USERNAME/.config"
08:47 <seb128> pitti, danke
08:47 <pitti> seb128: the user is only created in the /root file system
08:47 <seb128> right
08:48 <didrocks> making sense
08:48 <pitti> seb128: actually, I think without the quotes
08:48 <seb128> what's the easiest way to try those changes?
08:49 <pitti> seb128: the initramfs has vi, so break=casper-bottom, vi the file, and continue to boot (just ctrl+d or exit theh initramfs shell)
08:49 <seb128> pitti, danku
08:50 <pitti> seb128: F6 other options -> press esc twice to close the pop up menu, then you can edit the boot command line
08:50 <pitti> (I didn't know before that our live initramfs has vi, but I guess we weren't the first ones to hack casper fixes on the live system :)
08:52 <didrocks> it didn't 5 years ago
08:52 <didrocks> I'm jaleous now :p
08:52 * didrocks had to cat, awk and redirect :/
08:52 <pitti> sed FTW :)
08:54 <FJKong_> seb128: didrocks about this bug : https://bugs.launchpad.net/ubuntukylin/+bug/1413865
08:54 <ubot5> Launchpad bug 1413865 in Ubuntu Kylin "No default setting for "When power is critically low" in Power settings" [Medium,Confirmed]
08:55 <FJKong_> seb128: didrocks the right way is patch unity-control-center and add option 'suspend' ?
08:56 <seb128> FJKong_, does it make sense to suspend on those case? knowing that suspend uses power and your laptop is going to run flat anyway
08:57 <FJKong_> seb128: so maybe just shutdown ?
08:57 <seb128> yes, likely better
08:58 <didrocks> firefox developer edition support in ubuntu make done -> writing tests now :)
08:58 <FJKong_> seb128: so just patch ubuntu-settings and change default value to shutdown
09:00 <seb128> FJKong_, I guess so, though I wonder if we should rather patch the code to default to hibernate and fallback to shutdown if hibernate is disabled
09:01 <seb128> though since we disable hibernate by default we could decide it's up to the user to change the config if they enable it
09:01 <seb128> didrocks, pitti, thanks for the help, I tested it and confirmed it works this time :-)
09:03 <didrocks> nice!
09:04 <FJKong_> seb128: I think hibernate will be better
09:04 * pitti ^5s seb128
09:04 <Laney> yo
09:04 <didrocks> FJKong_: hibernate isn't supported on all machines though
09:04 <seb128> FJKong_, we don't enable hibernate by default though
09:04 <pitti> hey Laney
09:04 <seb128> hey Laney, wie gehts?
09:04 <didrocks> hey Laney
09:04 <larsu> morning Laney!
09:04 <FJKong_> oh
09:04 <FJKong_> I see
09:05 <FJKong_> it seems we have no other choice then
09:05 <seb128> FJKong_, well, as said we could still default to hibernate and fallback in the code to shutdown if hibernate is not available
09:05 <seb128> but I'm unsure it's worth the effort
09:06 <seb128> if users enable hibernate they can go and change the config
09:07 <FJKong_> seb128: how to enable hibernate then
09:13 <Laney> hey pitti seb128 didrocks larsu!
09:16 <seb128> FJKong_, http://askubuntu.com/questions/94754/how-to-enable-hibernation
09:16 <didrocks> and done, large and medium tests \o/
09:16 <didrocks> (with fake mozilla certificates and fake server for medium ones)
09:18 <seb128> dpm, pitti, so ubunut-system-settings has langpack support enabled, but we should strip the .desktop (since some code on touch isn't smart enough to use gettext and try to read the Name .ini style), what's the easiest way to do that? use --exclude on the file in dh_translations?
09:19 <dpm> morning seb128, I think I'll have to defer that one to pitti
09:20 <pitti> seb128: you mean should *not* strip the desktop?
09:20 <Laney> which code is that?
09:20 <Laney> wouldn't you want to do this for every application then?
09:20 <pitti> seb128: dh_translations does look at -X, so that ought to work
09:21 <pitti> seb128: that will still add X-Ubuntu-Gettext-Domain:, but keep the inline translations
09:21 <seb128> pitti, yeah, sorry :-/ *shouldn't*
09:21 <FJKong_> seb128: well, if we have a quick fix this version and put more time on it later, it that okay? I don't think most of user will enable hibernate after installing
09:21 <pitti> seb128: ah no, it will *not* add the domain
09:21 <pitti> seb128: so yes, -X
09:22 <seb128> pitti, no domain is fine, it means thing just use the inline translations
09:22 <seb128> FJKong_, yeah
09:22 <seb128> Laney, wdym for every application?
09:22 <seb128> Laney, most applications on touch are click and that doesn't use langpack
09:22 <seb128> other debs seem to not strip their .desktop already
09:22 <FJKong_> seb128: cool
09:22 <Laney> maybe now they are, haven't looked at that
09:23 <Laney> but one day you will be able to install deb packages
09:23 <seb128> Laney, the code is notifications/notification_manager.cpp
09:24 <seb128> Laney, that code is not ready to support debs, it's calling "click list" to get the entries
09:27 <Laney> then what are you fixing in a deb package?
09:27 <seb128> I probably don't understand the code
09:27 <seb128> let me look at it more
09:27 <seb128> but settings is listed unstranslated in that panel
09:27 <seb128> and added a Name[fr]= to the .desktop fixes it
09:28 <seb128> adding
10:44 <willcooke> trains.  :(
10:44 <willcooke> morning all
10:45 <didrocks> argh, another gnome-terminal segfault while doing a sbuild :/
10:47 <didrocks> let's see once whoopsie would retrace it for me
10:47 <larsu> willcooke: in brussels again?
10:47 * didrocks restarts the build and ubuntu make tests meanwhile…
10:48 <didrocks> larsu: seeing "trains…", definitively brussels and not London for sure :)
10:48 <willcooke> larsu, I think it would have been quicker to go to Brussels
10:49 <willcooke> They said the trains were delayed by 16 mins.
10:49 <willcooke> lies
10:49 <willcooke> damn lies
10:49 <didrocks> ahah, it's starting to be a trend it seems (train starting earlier than what they announce)
11:06 <mlankhorst> in holland I don't have to worry about that :P
11:06 <ogra_> because you can walk across the country in 1h :)
11:06 <mlankhorst> hah you wish
11:07 <mlankhorst> we do have a database of all windmills though :P
11:07 <ogra_> lol
11:10 <willcooke> And when global warming kicks off in a big way Holland will be nice and cool, because of all the windmills
11:10 <larsu> will also be under water...
11:10 <willcooke> (favourite Futurama spot ever)
11:11 <willcooke> http://www.quickmeme.com/img/e8/e8612be4060eee520cad620292dfc484f2a2f64568a3942ec0bcddb767023e9d.jpg
11:11 <mlankhorst> it will be nice and cool because the gulf stream will have collapsed and we will get the climate of new york :p
11:11 <chrisccoulson> didrocks, re your gnome-terminal crash - don't you use tmux so that you don't have to restart the build?
11:12 <mlankhorst> I've rebased Xmir on top of xorg-server 1.17.1
11:13 <didrocks> chrisccoulson: yeah, I'll soon start doing this I guess :)
11:15 <mlankhorst> and I've uploaded to my ppa the qtmir version that broke autorepeat but fixed mouse events in unity8
11:48 <willcooke> I assume phablet-shell is part of the sdk ppa
11:48 <popey> willcooke: phablet-tools package
11:49 <willcooke> hrm
11:49 <willcooke> I have that install but no phablet-shell
11:49 <popey> apt-cache policy phablet-tools
11:49 <popey> Installed: 1.1+15.04.20141107.1-0ubuntu1
11:49 <popey> ?
11:49 <popey> I am on vivid
11:49 <popey> you may need one of the sdk PPAs
11:50 <willcooke> ack, thanks popey
11:50 <pitti> seb128: btw, you have the shutdown hang, don't you?
11:50 <pitti> seb128: I noticed that unattended-upgrades delays shutdown a lot
11:50 <pitti> seb128: that might be another candidate for you?
11:51 <willcooke> ahh, I remember - I had to purge it to get Snappy to play nice
11:52 <pitti> didrocks: ^ you also reported some shutdown hangs; so modemmanager and unattended-upgrades might be things to try and disable
11:54 <didrocks> pitti: nice hint, will give it a try later
11:54 <willcooke> team - remember to get your self assessment done by Friday EOD
11:54 <willcooke> and let me know your 360 peers asap
11:54 <willcooke> this message will repeat
11:55 <darkxst> willcooke, has turned into a bot ?
11:56 <Laney> darkxst: think I've fixed those totem problems ("fixed" in one case :|)
11:56 <Laney> did you fwd your headerbar patch?
11:56 <willcooke> darkxst, I was always pretty close tbh :)
11:57 <darkxst> Laney, bookmarks problem?
11:57 <Laney> ya
11:57 <Laney> bug in the grilo plugin itself I think
11:58 <darkxst> Laney, not forwarded upstream yet, but will once I fix full screen issue
11:58 <Laney> did that
11:58 <darkxst> Laney, yeh I saw that commit after you mentioned it (way after I was sleep last night)
11:59 <Laney> http://paste.ubuntu.com/10172243/
12:00 <darkxst> Laney, Ack
12:01 <darkxst> and I really need to go to sleep
12:02 <darkxst> can you upload fix to gnome3 ppa or somewhere
12:03 <Laney> ya
12:03 <Laney> I'm going to fwd the dialogs-use-header stuff
12:03 <darkxst> Laney, we will eventually get packaging branches setup on alioth, but that hasnt quite happend just yet
12:05 <Laney> for what?
12:05 <darkxst> Laney, stuff in the gnome3 ppa's
12:05 <Laney> oh right
12:05 <darkxst> and perhaps some of the main branches in ubuntu GNOME packageset
12:06 <Laney> thought you'd branch off the ubuntu-desktop packages
12:07 <darkxst> Laney, we do where applicable
12:07 <darkxst> but i still don't like bzr
12:07 <darkxst> and pkg-gnome may one day move to git
12:07 <Laney> just you wait for git in launchpad
12:08 * larsu waits
12:08 <Laney> i'll figure out a cool merged-with-upstreams-history workflow
12:08 <darkxst> but in the meantime we are ok to host UG git repos on alioth
12:09 <Laney> doesn't really matter where they are i suppose
12:09 <darkxst> Laney, nope, majority of ubuntu sponsors would probably have commit access there I suppose
12:11 <Laney> there's an 'ubuntu-dev' group there already
12:11 <Laney> manually managed tho
12:21 * darkxst sleeps now
12:22 <Laney> night!
12:24 <darkxst> night
12:25 <didrocks> seb128: FYI, g-c-c for bluez5 now built in ppa. That should unblock you if you want to update (didn't retest yet with latest g-c-c)
12:25 <didrocks> larsu: that can interest you as well ^
12:25 <darkxst> didrocks, gnome-shell also has patches that need to be dropped for bluez5
12:26 <darkxst> (reverts)
12:26 <darkxst> but I am really sleep now
12:26 <nessita> hello! quick question, I updated my vivid install yesterday to latest, and since then some fonts are not properly rendered (yesterday Firefox was having the issue, today is evince), and I no longer can open a terminal with ctrl + alt + t. Any idea how to fix or where to ask?
12:26 <larsu> didrocks: which ppa?
12:26 <larsu> didrocks: and thanks :)
12:26 <didrocks> darkxst: if the gnome ubuntu team can provide a debdiff, we can send that to the same ppa and do the same copy on the D day (you have time still)
12:27 <didrocks> larsu: the transition one (see email): https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions
12:27 <larsu> didrocks: cool,thanks
12:27 <didrocks> yw!
12:27 * larsu wanted to start hacking on that today, but too much to do
12:27 <darkxst> didrocks, ok, tomorrow then
12:27 <larsu> DS-McGuire: got some time to talk in ~15 mins?
12:28 <DS-McGuire> larsu, I do :)
12:28 <didrocks> darkxst: core-devs have access to dput directly to the ppa FYI
12:29 <darkxst> didrocks, me no core-dev
12:32 <didrocks> just propose a debdiff when you have time (the best would be this week)
12:33 <darkxst> didrocks, ok, will take a look tomorrow
12:34 <darkxst> probably gnome-shell, g-s-d and g-c-c all have reverts currently to work with bluez4
12:35 * darkxst really sleeps now!
12:36 <willcooke> mlankhorst, should Xmir work with the devel channel?
12:36 <didrocks> darkxst: g-c-c is done, g-s-d has nothing to be done, g-s left to you, good night man :)
12:36 <darkxst> didrocks, ok, night
12:37 <mlankhorst> willcooke: ought to :P
12:37 <mlankhorst> I've just uploaded a rebuild against 1.17.1, haven't tested it yet
12:38 <willcooke> thanks mlankhorst
12:38 <willcooke> Just reflashing
12:40 <mlankhorst> oke
12:41 <nessita> willcooke, hi! which one would be the best channel to ask about issues with a vivid installation in a laptop?
12:41 <willcooke> nessita, #ubuntu will sort you out
12:41 <nessita> I see broken fotns such as https://drive.google.com/a/canonical.com/file/d/0B-cmfDncRJmYRnJ0SUhWWGsyVjQ/view?usp=sharing
12:41 <nessita> willcooke, thanks, going there
12:42 <willcooke> nessita, ahhh
12:42 <willcooke> seb128, didn't you see that as well (see link ^^)
12:42 <nessita> willcooke, ctrl + alt + t will not open a terminal either, since yesterday's updates
12:43 <mlankhorst> hm /me upgrades his phone too
12:43 <willcooke> Hrm.  Video drivers, or perhaps Gtk
12:45 <seb128> didrocks, thanks
12:46 <seb128> nessita, willcooke, yeah, I see similar fonts corruption sometime, I blame xorg but I'm unsure
12:46 <nessita> hola seb128 !
12:46 <seb128> mlankhorst, any idea what could lead to corruption like the one nessita has in the url she just shared
12:46 <seb128> nessita, yeah, nice to see you still around! how are you?
12:47 <nessita> seb128, super good. How about you?
12:47 <nessita> seb128, mlankhorst font corruption was isolated to firefox yesterday, today seems to happen with evince. I installed all vivid updates yesterday
12:47 <seb128> pitti, unattended-upgrade is enabled & inactive, I can try to disable it
12:47 <seb128> nessita, does it persist after xorg restart?
12:47 <mlankhorst> no idea..
12:47 <seb128> nessita, I'm great, thanks :-)
12:48 <mlankhorst> never seen that tbh
12:48 <nessita> seb128, it persistes yesterday for FF after computer restart, haven't tried today, let me do that
12:49 <seb128> nessita, k, the issue I sometime have doesn't persist after xorg restart
12:49 <seb128> so likely different
12:50 <nessita> seb128, restarted, pdf still looks corrupted
12:50 <nessita> trying another pdf
12:50 <seb128> nessita, yeah, could be that it's picking a wrong font as well
12:50 <seb128> nessita, did you install new fonts recently?
12:51 <nessita> seb128, seems the case (not picking the right font). No, I don't recall ever installing new fonts explicitely.
12:51 <seb128> nessita, can you grep for font in /var/log/dpkg.log ?
12:51 <nessita> yes
12:53 <nessita> seb128, http://pastebin.ubuntu.com/10172824/
12:53 <nessita> more results than I expected!
12:56 <seb128> nessita, hum, I'm unsure
12:57 <seb128> in evince, can you go to files->properties-> fonts tab
12:57 <seb128> what fonts does it list there?
12:57 <seb128> then maybe email me a pdf which shows the issue so we can compare what is used?
12:57 <nessita> ack, on it
13:02 <nessita> seb128, sent
13:03 <seb128> nessita, that pdf renders buggy for me as well, it's specific to this file right?
13:04 <nessita> yeah
13:04 <nessita> so the pdf itself is not important
13:04 <nessita> but yesterday firefox (and the terminal for a bit) we broken as well
13:04 <nessita> we can leave this as is, and I can let you guys know if something else breaks font-wise
13:05 <seb128> nessita, do you still have the other issues after a restart?
13:05 <nessita> seb128, nopes
13:05 <seb128> nessita, btw firefox has the same problem rendering that pdf, wonder if the file is buggy
13:05 <nessita> can be, is an old pdf
13:05 <seb128> nessita, k, so the firefox&co issue was probably the corruption I see sometime
13:05 <seb128> the pdf issue is different
13:06 <nessita> makes sense
13:11 <seb128> nessita, I tried different viewers on my android phone, they have the same issue on the pdf, so I think we can say it's an issue with the file in that case
13:12 <nessita> seb128, sounds good!
13:12 <nessita> the pdf is not important
13:16 <willcooke> willcooke, test
13:16 <willcooke> wifi. sigh
13:20 <seb128> willcooke, you are at the office?
13:20 <willcooke> yeah
13:22 <seb128> nessita, your issue could be https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1330385 ... you can maybe look in your log if there are such GPU error mentioned
13:22 <ubot5> Launchpad bug 1330385 in xserver-xorg-video-intel (Ubuntu) "Intel GPU crash corrupts fonts" [Undecided,Confirmed]
13:29 <nessita> seb128, checking!
13:29 <nessita> I certainly have an intel video card
13:35 <willcooke> attente_, can you remind me who you are syncing with on input methods from the Mir team?
13:36 <nessita> seb128, I can find the crash in my syslogs, but I will be paying more attention for future freezes/font corruptions
13:36 <attente_> willcooke: no one on the mir team
13:36 <willcooke> attente_, U8?
13:36 <seb128> nessita, can or can't?
13:36 <seb128> nessita, ok
13:36 <nessita> seb128, sorry, can't :-D
13:36 <seb128> nessita, k
13:36 <nessita> still morning to me!
13:36 <attente_> willcooke: just bschaefer so far
13:36 <willcooke> attente_, thanks!
13:36 <willcooke> attente_, good morning btw :)
13:37 <attente_> thanks!
13:40 <FJKong_> attente_: morning Hua
13:44 <attente_> FJKong_: good evening :)
13:51 * mlankhorst reflashes phone
14:11 <larsu> attente_, desrt: does gtk-mir ever draw decorations on behalf of the app?
14:11 <larsu> greyback is seeing that apparently
14:12 <desrt> yes.  it does.
14:12 <greyback> desrt: any easy way I could disable that temporarily?
14:12 <desrt> GTK_CSD=0 or something?
14:12 * larsu was totally unawware
14:12 <larsu> greyback: sorry :/
14:13 <greyback> larsu: no worries
14:13 <desrt> actually, i think that won't help
14:13 <greyback> no good
14:13 <desrt> GTK_CSD=1 is only useful for forcing it to be enabled
14:13 <desrt> GTK_CSD=0 is equivalent to being unset
14:13 <greyback> eee, 0 != undefined
14:13 <desrt> greyback: for mir it's hardwired to on
14:13 <larsu> what is this, javascript?!
14:13 <desrt> if (GDK_IS_MIR_DISPLAY (gtk_widget_get_display (GTK_WIDGET (window))))
14:13 <desrt> return TRUE;
14:13 <desrt> #endif
14:14 <desrt> gtk_window_should_use_csd (GtkWindow *window)
14:14 <greyback> desrt: thanks, gives me place to hack at
14:18 <desrt> i'm disconnecting from IRC for now.  too many pings and i need to sort through a bunch of reviews and other stuff.  bbl.
14:20 <willcooke_> desrt, ping
14:20 <willcooke_> I crack myself up - I really do.
14:20 <willcooke_> and it's not even Friday
14:40 <mlankhorst> https://www.youtube.com/watch?v=kfVsfOSbJY0
14:43 <Laney> bah
14:44 <Laney> suspend failure, burny laptop
14:45 * Laney stares at systemd
14:54 <Laney> how can I view the journal from the previous boot?
14:54 <Laney> --list-boots only shows this one
14:56 <seb128> Laney, see the README.Debian, you need to create the dir to enable persistent
14:56 <seb128> not sure why that's not done by default
14:56 <seb128> but maybe pitti or didrocks know
14:56 <Laney> hmm
14:57 <pitti> seb128: because we install rsyslog by default, and I don't think we want to write everything to disk twice
14:57 <Laney> oh so it's in the syslog maybe
14:59 <seb128> pitti, ok, makes sense
14:59 <Laney> Feb 11 12:46:43 iota systemd-sleep[31629]: System resumed.
15:00 <Laney> looks like it does some suspend things then does some resume things straight away
15:01 <pitti> Laney: is that with upstart or systemd? with upstart you might have a /var/log/pm-suspend.log
15:01 <Laney> pitti: systemd, I did the perma-switch last week
15:01 <pitti> hm, any kernel error message to go with that?
15:01 <Laney> sec, let me just pastebin the whole area
15:01 <sneezewort> Hello all. I left my system locked last night. When I came in this morning my system appeared as if it had rebooted, but when I run "who -b" it says last boot time was several days ago.
15:02 <sneezewort> How do I troubleshoot my lost session?
15:03 <sneezewort> In other words how can I figure out what happened, and how to keep it from happening again.
15:06 <Laney> pitti: http://paste.ubuntu.com/10174186/
15:06 <Laney> I wonder what the 2 minute gap is
15:06 <Laney> ah hang on, I did resume it
15:07 <pitti> Laney: I don't see a gap there
15:08 <pitti> just that there is pretty much zero time after suspend before resume
15:08 <pitti> Laney: is that reproducible, or only happened once?
15:08 <pitti> I don't think there's an inhibitor, otherwise you wouldn't have gotten that ar
15:08 <Laney> I did suspend, resume, <read a couple of emails>, suspend
15:08 <pitti> far
15:09 <Laney> yesterday I had to reboot because of a resume failure but it could have been the same thing
15:09 <Laney> lemme just try suspend/resuming a few times now
15:09 <pitti> oh, there I see the gap, sorry
15:09 <pitti> I figure you cut away the resume part from that?
15:15 <mzanetti> seb128: hey, did you push the workaround for bluez4 somewhere?
15:18 <seb128> mzanetti, hey, no, but you can edit /usr/share/ubuntu/settings/system/qml-plugins/bluetooth/DisplayPasskeyDialog.qml l39
15:18 <seb128> mzanetti, remove the .slice(entered)
15:18 <mzanetti> seb128: ack
15:18 <seb128> mzanetti, I can push that somewhere if you want, didn't do the fix I mentioned the other day yet but I can try to do that today or tomorrow
15:18 <seb128> (the "if "entered" > 6, then ignore it)
15:19 <mlankhorst> meh no luck now..
15:19 <mlankhorst> [   17.215852] init: apport-noui (/var/crash/_usr_bin_unity-system-compositor-spinner.0.crash) main process (2001) terminated with status 1
15:19 <willcooke_> sneezewort, you'll likely have better luck in the #ubuntu channel
15:19 <mzanetti> seb128: no worries, I'm just currently checking status on silo0 to see what's missing, and that one popped up.
15:19 <sneezewort> willcooke_, OK thanks.
15:22 <Laney> took 6 or 7 goes but I got a failure
15:25 <pitti> Laney: i. e. it immediately resumed again? either way, that sounds like a "fun" kernel bug to track down :(
15:25 <pitti> Laney: if you never had this before, I suggest trying some earlier kernels, perhaps utopic's?
15:25 <Laney> pitti: you get a black screen
15:25 <Laney> yeah, good plan
15:26 <pitti> Laney: another thing to try would be to run pm-suspend and see if you can reproduce it with that
15:26 <pitti> Laney: on any graphics card that supports KMS and reasonably modern nvidia cards (with the proprietary driver) the pm-utils quirks shouldn't be necessary any more, but maybe some are still applied on your system which help
15:31 <Laney> pitti: I'll try tomorrow, need to patch pilot now
15:31 <pitti> Laney: ah, safe flying!
15:31 <pitti> Laney: ack, we can then check which quirks pm-utils actually applies, etc.
15:37 <Laney> bah
15:37 <Laney> some network related lock up too
15:37 <Laney> bad day for laney
16:09 <Laney> mlankhorst: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1420294 for you
16:09 <ubot5> Launchpad bug 1420294 in mesa (Ubuntu) "Update Mesa Mir EGL platform for Mir 0.11" [Undecided,New]
16:20 <seb128> cyphermox, hey, do you where in the code you toggle on/off discoverability of bt?
16:20 <cyphermox> yes, that's in plugins/bluetooth/devicemodel.cpp
16:21 <didrocks> happyaron: fcitx MIR approved now, thanks!
16:21 <cyphermox> in the init functions as soon as you know there is an adapter to do this on
16:21 <didrocks> happyaron: see my comment on how we are going to promote things in main, are you going to seed it directly or having a dep/recommends?
16:21 <seb128> cyphermox, thanks
16:36 <willcooke_> didrocks, happyaron - great work guys, thanks
16:37 <didrocks> seems that vivid will get fcitx in main :)
16:41 <attente_> willcooke_, didrocks: should i start merging those old branches for u-c-c, u-s-d, indicator-keyboard for fcitx support?
16:43 <didrocks> attente_: did you try against latest fctix (it doesn't seem to have changed much)? is the support complete? Meaning we have the ibus vs fcitx switch? (I didn't follow the end of that discussion, probably seb128 is more up to date on this)
16:43 <attente_> didrocks: i'll try it again, but last i remember they were just waiting on the MIR
16:44 <didrocks> better to triple check, but if so, all good, then we can push them and promote things as needed :)
16:45 <attente_> ok, thanks, really hope they're still ok...
16:53 <willcooke_> does anyone else find setting the input focus in gnome-calculator to be a bit tricky?
16:54 <willcooke_> I get the caret when I move the mouse over the numbers field
16:55 <willcooke_> but when I click it doesnt get the focus unless the mouse is, seemingly above half way
16:56 <willcooke_> I think that line underneath where you put the numbers, where it might say, for example, "Division by zero is undefined"
16:56 <willcooke_> is what I'm actually clicking on
16:56 <willcooke_> but it might be nice if clicking there focused the numbers input area instead?
16:57 <willcooke_> or not show the caret until I'm over the numbers
16:57 <larsu> willcooke_: how do you get that field to lose focus?
16:57 <larsu> seems to always have focus for me
16:57 <didrocks> larsu: I'm desperatly trying to have it losing focus as well :)
16:58 <willcooke_> larsu, I can use the drop downs for converting between things
16:58 <larsu> ah
16:58 <larsu> yeah this is weird
16:58 <willcooke_> in advanced mode that is
16:58 <larsu> it's because you can select the "error" text
16:58 <willcooke_> I can see that selecting the text in there might be useful
16:58 <willcooke_> but not very often
16:58 <larsu> hence you also get a caret cursor
16:58 <willcooke_> yeah, makes sense
16:58 <willcooke_> it just rubs me up the wrong way for some reason
16:58 <willcooke_> :)
16:59 <larsu> mpt is a big proponent of that, because you want to allow users to copy/paste error messages for questions
16:59 <willcooke_> sure
16:59 <larsu> it looks like the same widget though
16:59 <larsu> maybe we can trick it to focus the right thing on click
16:59 <larsu> but keep the same behavior when selecting...
17:00 * didrocks can't use gnome-calculator anyway, it's not a RPN calc and so, breaks my mind… :)
17:00 <larsu> oh really?
17:00 <larsu> kewl
17:00 * larsu uses python3
17:01 <didrocks> larsu: years of using HP48, there is no going back in your mental model :)
17:01 <larsu> never did use that
17:02 <willcooke_> I would argue that when it loses focus and regains it the input field should be selected by default
17:02 <larsu> but I can imagine
17:02 <didrocks> willcooke_: agreed, maybe something to discuss with robert as he's upstream?
17:02 <willcooke_> sure, just venting my very minor annoyances
17:02 <willcooke_> :)
17:02 <willcooke_> I feel better now
17:03 <didrocks> ahah
17:03 <willcooke_> ah
17:03 <willcooke_> in basic mode
17:03 <didrocks> larsu: it was always fun to lend the calc to someone else and see them being very puzzled :)
17:39 * didrocks waves good evening and good night
19:36 <Noskcaj> Laney, Is there anything i can do to speed up the gtk3.16 work? I noticed the PPA versions are lightly behind gnome upstream
19:38 <Noskcaj> Also, should we try and fit clutter-gst-3.0 in before FF?
19:41 <mterry> seb128, hello!  Is there a wiki page about running the u8 preview image?
19:43 <mterry> https://wiki.ubuntu.com/Unity8Desktop
19:54 <mlankhorst> Laney: already done :P
19:54 <mlankhorst> Laney: but it FTBFS
19:55 <mlankhorst> forgot to re-upload the build fix with -v, so it didn't close the bugs
22:11 <robert_ancell> infinity, I'm trying to remove an archive block (bug 958345) by following the procedure suggested when I try to upload. Is that on the radar for ~ubuntu-archive?
22:11 <ubot5> bug 958345 in ttf-indic-fonts (Ubuntu) "ttf-indic-fonts packages are outdated" [Wishlist,Confirmed] https://launchpad.net/bugs/958345
22:23 <desrt> reminder: new launch attempt in ~40 mins
22:53 <robert_ancell> desrt, watcha launching?
22:54 <larsu> robert_ancell: a rocket
22:54 <robert_ancell> larsu, at new zealand?
22:54 * robert_ancell ducks
22:55 <ochosi> larsu: oh wow, you're around at this hour...
22:57 <desrt> robert_ancell: http://www.nasa.gov/multimedia/nasatv/
22:57 <desrt> an interesting launch for two reasons
22:57 <desrt> one: it's the first time we send something to orbit L1
22:58 <desrt> two: it's another attempt for space X to play xlander
22:58 <robert_ancell> oh, fun
22:58 <sarnold> I thought I heard they cancelled the landing due to weather concerns
22:58 <desrt> that was yesterday
22:58 <desrt> today is their retry
22:58 <desrt> and the winds are nice and calm....
22:58 <sarnold> I think it's the ten-meter waves at the landing location that caused them to scrub the landing
22:59 <desrt> i understood it was the 100km/h+ winds in the upper atmosphere
22:59 <sarnold> https://twitter.com/elonmusk/status/565636516551352321
23:00 <desrt> oh!
23:00 <desrt> :(
23:00 <desrt> no xlander today, i guess
23:02 <desrt> i thought you were talking about yesterday's scrub
23:03 <desrt> which was also due to weather...
23:04 <robert_ancell> flash crashed one second before launch
23:04 <desrt> perfect
23:04 <desrt> fortunately the rocket did not do the same
23:05 <larsu> ochosi: hacker schedule
23:05 <ochosi> :)
23:05 <larsu> robert_ancell: hopefully not :D
23:06 <ochosi> larsu: hmm, so what are your thoughts on a possible gtk3.16 transition? i thought you just finished fixing up gtk3.14..?
23:06 <larsu> ochosi: I was in the room when we had the idea...
23:06 <larsu> 3.16 was pretty calm
23:07 <ochosi> what, no theme breakage?
23:07 <desrt> stage1 just got cut loose
23:07 <larsu> only notify-osd so far
23:07 * ochosi is semi-disappointed
23:07 <larsu> and a few other issues (resizing problems in terminal for example)
23:07 <ochosi> but the 3.16 cycle is not done yet
23:07 * larsu has been running it for a week and it works great
23:07 <larsu> better inspector, too
23:08 <ochosi> hmm
23:08 <larsu> ochosi: I know, but I also know that probably not many more changes are coming
23:08 <ochosi> i guess i need to look into it
23:08 <larsu> it's in the desktop team ppa
23:08 <ochosi> well, i'm always a bit hesitative about gtk3 upgrades tbh :)
23:08 <larsu> <gnome-hat>we're getting better!</gnome-hat>
23:08 <ochosi> hehe
23:09 <ochosi> well, that is good to hear
23:09 <ochosi> both, that you're getting better and that you're wearing a gnome hat now
23:09 <larsu> usually I don't wear it in this channel
23:14 <ochosi> well, good though if there are upstream connections
23:16 <ochosi> less surprises
01:23 <infinity> robert_ancell: Have you sorted a sane way forward for the indic font mess?  If so, enlighten me and then, sure, we can remove the sync block if that's the right thing to do.
01:36 <darkxst> robert_ancell, can you copy https://launchpad.net/~darkxst/+archive/ubuntu/bluez5/+packages to the bluez transition ppa?
01:41 <robert_ancell> infinity, I haven't been able to work out why the block is there. So my current assumption is "we should just match Debian".
01:42 <robert_ancell> infinity, any more background info very welcome
01:49 <infinity> # cjwatson, 2012-06-01
01:49 <infinity> # Temporary blacklist entries for quantal, requiring manual resolution due
01:49 <infinity> # to conflicts with existing Ubuntu-versioned binaries.
01:49 <infinity> robert_ancell: ^-- So, this is probably no longer true, or likely not, but I can't investigate right this instant either.
01:50 <robert_ancell> infinity, that's fine. I just wanted to check that you guys are aware of the bug and/or find alternative means to find the right person to lift it
01:51 <robert_ancell> darkxst, I'm trying to find the PPA link - do you have it?
01:51 <darkxst> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions
01:52 <robert_ancell> darkxst, ta
01:57 <robert_ancell> darkxst, do they need rebuilding?
01:57 <darkxst> robert_ancell, no, binary copy should be fine
01:58 <robert_ancell> darkxst, done
01:58 <darkxst> thanks
06:45 <pitti> Good morning
06:50 <seb128> good morning desktopers
06:50 <seb128> hey pitti
06:51 <pitti> bonjour seb128 !
06:51 <pitti> I'm finally making some progress on finding out why people's fstab mounts get unmounted during boot
06:54 <happyaron> pitti, seb128, morning, :)
06:54 <seb128> hey happyaron
06:54 <pitti> hey happyaron, good day!
06:55 <seb128> pitti, oh, why is that?
06:55 <pitti> seb128: do you get that as well?
06:55 <pitti> bug 1419623
06:55 <seb128> no
06:55 <ubot5> bug 1419623 in systemd (Ubuntu) "systemd unmounts partitions from fstab" [Critical,Confirmed] https://launchpad.net/bugs/1419623
06:56 <seb128> but I don't have partitions mounted at boot
06:56 <seb128> only a /
06:56 <pitti> ah, I have /home and /srv in fstab
06:56 <pitti> and /boot/efi/
06:58 <pitti> seb128: it could still be a red herring, but so far my theory is that cgmanager does some mounts/unmounts/remounts which cause that; it remounts MS_SLAVE, not MS_RSLAVE
06:58 <pitti> (testing that now)
07:00 <pitti> but that doesn't yet explain the full story
07:01 <darkxst> pitti, still planing on switching to systemd init this cycle?
07:02 <pitti> darkxst: I was quite hopeful, but NFS, maas, and juju drag on.. :/
07:04 <darkxst> why is nfs a problem? surely upstream have that also?
07:05 <pitti> darkxst: upstream does have systemd units, yes; but our package only has an upstart job, so it doesn't work under systemd
07:05 <pitti> darkxst: slangasek wanted to look into that this week though
07:06 <darkxst> pitti, ok, I was thinking of switch Ubuntu GNOME, but then two critical bugs in a week ;(
07:06 <pitti> darkxst: oh, what's the other one?
07:07 <darkxst> pitti, ifup service hang,
07:08 <darkxst> guess that is fixed now?
07:08 <pitti> darkxst: ah, yes
07:09 <pitti> darkxst: see bug 1417010, both sysvinit and systemd are in vivid
07:09 <ubot5> bug 1417010 in sysvinit (Debian) "Reloading services can result in a deadlock under systemd" [Unknown,New] https://launchpad.net/bugs/1417010
07:11 <darkxst> pitti, I have missed that janitor comments, but certainly saw the fix-commited's
07:24 <seb128> hum
07:24 <seb128> https://lists.ubuntu.com/archives/ubuntu-desktop/2015-February/004636.html
07:24 <seb128> why is the sync bug #1420948 reaching the list?
07:24 <ubot5> bug 1420948 in appstream-glib (Ubuntu) "Sync appstream-glib 0.3.4-1 (universe) from Debian experimental (main)" [Wishlist,New] https://launchpad.net/bugs/1420948
07:24 <seb128> "You received this bug notification because you are a member of GNOME3
07:24 <seb128> Team, which is subscribed to appstream-glib in Ubuntu."
07:25 <seb128> darkxst: did you guys add the desktop list as contact info for your team or what?
07:25 <darkxst> seb128, we use gnome3-team for that
07:25 <seb128> or is that because there is no list associated to the team?
07:26 <seb128> darkxst, https://launchpad.net/~gnome3-team/+mailinglist
07:26 <seb128> hum, I don't understand
07:27 <darkxst> seb128, I don't know why that would go to desktop list
07:27 <seb128> let me ask on #launchpad
07:28 <darkxst> seb128, I also don't know why Noskcaj even filed that bug ;(
07:28 <darkxst> it needs fixes for MIR, that should be forwarded to debian before sync
07:39 <Noskcaj> darkxst, But it helps to get the newer version, doesn't it?
07:39 <didrocks> morning
07:40 <larsu> hi didrocks!
07:40 * didrocks spent 20 minutes in rebooting and being puzzled
07:40 <didrocks> hey larsu!
07:40 <darkxst> Noskcaj, it doesnt help the MIR
07:40 <darkxst> Noskcaj, fix those, forward to debian and propose an ubuntu package in the mean time?
07:41 <Noskcaj> no, of course not. ximion hasn't been online in the last 2 days, but he's normally pretty active
07:41 <darkxst> Noskcaj, I really don't see any reason they wouldnt take the changes
07:42 <darkxst> debian is normally more pedantic about copyright than us
07:42 <darkxst> useless build-deps and disabled but working tests seem to be a no brainer
07:44 <darkxst> Noskcaj, that said, may need https://github.com/hughsie/appstream-glib/commit/8fea9d934fbfffbead04a1a6ec9e4344725af188
07:44 <darkxst> for tests
07:51 <seb128> darkxst, Noskcaj, can you put the gnome3 list as contact address on https://launchpad.net/~gnome3-team/+contactaddress ?
07:52 <seb128> without that each member get emailed on any bug subscription
07:52 <seb128> which includes the desktop list through ubuntu-desktop being a member
07:52 <darkxst> seb128, sure no problem
07:52 <seb128> thanks
07:52 <darkxst> never even realised it worked (or didn't) like that
07:53 <happyaron> didrocks: I'm preparing patch for seeding fcitx, but in doubt whether I should remove ibus at the same time
07:53 <happyaron> some follow up patches are needed to switch the default
07:54 <didrocks> happyaron: I didn't follow the discussions about what would be done in the end (switch or supporting both), I suggest you discuss it with attente_ and seb128?
07:54 <happyaron> sure
08:03 <didrocks> pitti: seems Lennart stopped just before my fsck patch if my email history is right :p
08:08 <darkxst> Noskcaj, seems you have to subscribe yourself for new gnome3-team ML
08:08 <Noskcaj> ok, will do
08:08 <darkxst> thanks
08:19 <pitti> didrocks: heh, yes; talked to him yesterday, and at the moment patches come in faster than he can keep up with; I'll ping him today to ask who would be appropriate to review/commit them (given that it already went through several rounds)
08:20 <pitti> didrocks: now that I found out what breaks our mounts at boot (see #u-devel), I can think about other problems again :)
08:20 <didrocks> pitti: sounds good, thanks!
08:20 <didrocks> pitti: oh, nice! backloging :)
08:20 * didrocks answers to slangasek on CI Train and rewrite some wiki pages meanwhile
08:20 <didrocks> digging into my old code :p
08:50 <willcooke> morning
08:50 <willcooke> hrm - no clock
08:51 * willcooke restarts panel service
08:51 <willcooke> haz clock
08:51 <didrocks> hey willcooke
08:51 <willcooke> morning didrocks
08:51 <willcooke> ohhh
08:56 <seb128> good morning willcooke
08:56 <willcooke> hi seb128
09:06 <Laney> hey
09:07 <Laney> had to restart network-manager to get my network to work just now
09:07 <Laney> :(
09:07 <Laney> could be ofono still I guess, didn't kill that
09:10 <seb128> hey Laney
09:10 <seb128> what was it doing?
09:10 <seb128> connected by no data going through?
09:10 <Laney> 16 packets transmitted, 0 received, 100% packet loss, time 15000ms
09:11 <Laney> I ctrl-ced it after exactly 15000ms, how cool is that
09:14 <Noskcaj> darkxst, Excluding copyright fixes, lp:~noskcaj/ubuntu/vivid/appstream-glib/mir-fixes should be ready
09:14 <Noskcaj> I'm signing off for the night, if it's all good, please propose the merge
09:14 <darkxst> Noskcaj, needs copyrights also
09:15 <Laney> you should get ximion to fix this
09:15 <Laney> or upload your fixes then sync :)
09:16 <Laney> also something in main could require it, I reverted back to appdata-tools for ... cheese I think
09:17 * xnox Yaaaawh
09:20 <seb128> Laney, attente_, don't look at it, but https://appstore.bhdouglass.com/app/uu.mzanetti :-)
09:21 <darkxst> Laney, been through that entire conversation with Jackson already
09:21 <seb128> the "don't look at it" is for productivity reasons of course ;-)
09:21 <Laney> haha
09:22 <Laney> I thought someone would do this when they started talking about how easy it would be when we were playing it
09:22 <seb128> :-)
09:23 <seb128> it's working quite nice, need a few tweaks to be great
09:23 <Laney> someone just needs to do space team
09:23 <seb128> lol
09:23 <seb128> I've the feeling that one wouldn't be as trivial
09:24 * Laney updates to the latest image
09:24 <Laney> got to test ... something ...
09:29 <seb128> lol
09:32 <mzanetti> :D
09:39 <Laney> darkxst: do you have a branch for your totem pkg?
09:40 <darkxst> Laney, no just whats on gnome3 ppa
09:40 <darkxst> but you can upload there right?
09:41 <Laney> sure
09:41 <Laney> but good history is better if it exists
09:41 <darkxst> given ubuntu-desktop is a member of that team
09:42 <darkxst> Laney, they guy who was setiing up out packaging branches resigned ;(
09:43 <Laney> bzr branch lp:~ubuntu-desktop/totem/ubuntu; hack hack hack; bzr commit; bzr push lp:~gnome3-team/totem/gnome3-staging
09:43 <Laney> sorry you lost a volunteer :(
09:44 <darkxst> Laney, or just stage it in ubuntu-desktop if you want
09:45 <Laney> might do
09:45 <Laney> any news on the grilo-plugins split?
09:45 <Laney> + mir + whatever
09:46 <larsu> Laney: morning. re gnome-screenshot... we can't use libcheese's cheese-flash, because that requires a parent window now (which gnome-screenshot doesn't have in non-interactive mode) and it doesn't support flashing individual windows
09:46 <Laney> ah ok
09:46 <larsu> however, the only noteworthy changes are getting rid of the set_visual() call
09:46 <larsu> and fixing the opacity mess
09:47 <darkxst> Laney, didrock was happy with the MIR pending split, seb128 may not be so happy ?
09:47 <larsu> by having a priv opacity var and not reading back the opacity from the widget
09:47 <larsu> kind of like I did
09:47 <larsu> only thing that remains is that weird double flash, which I only see on compiz :/
09:47 <darkxst> but I am proposing first group in https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/comments/2
09:47 <ubot5> Launchpad bug 1394731 in grilo-plugins (Ubuntu) "[MIR] grilo-plugins" [Undecided,Incomplete]
09:47 <darkxst> and probably youtube
09:48 <seb128> darkxst, I'm fine with whatever others decide, I just would like to have a summary of what it's going to bring on the CD and the installed size impact
09:48 <larsu> Laney: and I can't seem to get rid of it unless I don't destroy the flash window, which of course makes it leak
09:48 * larsu is unsure what to do
09:48 <darkxst> I think Noskcaj will do the actual packaging
09:48 <Laney> darkxst: ok then
09:48 <Laney> are the build deps all okay?
09:49 <darkxst> Laney, everything is in main except dleyna-server which is a suggests in ubuntu packaging
09:49 <Laney> larsu: I think we're probably sticking with 3.14 anyway (per the meeting), so not super important to fix right now
09:50 <Laney> but will be needed next cycle
09:50 <Laney> darkxst: cool
09:50 <darkxst> Laney, 3.14 gtk?
09:50 <Laney> ya
09:50 <Laney> I'm going to mail the list in a minute
09:50 <Laney> after making a totem package ;-)
09:52 <larsu> Laney: ok, I'll file an upstream bug for the opacity part and start pestering Trevinho about compiz
09:52 <darkxst> Laney, ok
09:53 <darkxst> probably easier than fixing all the issues
09:53 <Laney> at least we know about them *now* instead of in 2 months
09:54 <darkxst> Laney, very much so, I Would be happy with gtk update landing early next cycle
09:54 <darkxst> aka faster than this cycle
09:54 <Laney> nod
09:56 <Laney> how do you unstage something in bzr?
09:57 <darkxst> Laney, idk, but suspect you can't once you have push to a public branch
09:57 <darkxst> uncommit does work before that though
09:58 <Laney> haven't push
09:58 <Laney> I just want to undo a bzr add
09:58 <darkxst> uncommit then
09:58 <Laney> not committed
09:59 <darkxst> Laney, I'm no bzr expert, do most things in git
09:59 <Laney> bzr rm --keep looks likely
10:00 <Laney> (Y)
10:01 <happyaron> attente_, seb128: wonders how do we proceed with the input methods..?
10:01 <seb128> happyaron, wdym?
10:01 <happyaron> seb128: I'm making a mp to seed fcitx, shall I remove ibus at the same time, or have both of them?
10:02 <happyaron> ...and, what's your opinion about switch or not (and what time)?
10:02 <seb128> happyaron, don't see fcitx
10:02 <seb128> seed
10:02 <seb128> we don't want to install it by default
10:02 <happyaron> why?
10:02 <seb128> because we need the support for fcitx to be merged in the indicator and unity-control-center first
10:03 <seb128> which didn't happen yet because we needed to build-depends on fcitx to build those
10:03 <seb128> which required fcitx MIR to be acked first
10:03 <seb128> so next step is to merge those in
10:03 <happyaron> ic
10:03 <seb128> the new build-depends can be added and are going to led to promotion
10:03 <seb128> then we can give a round of testing and see how things work
10:03 <seb128> then decide to make fcitx default or not
10:04 <seb128> but we probably want it default only for chinese in a first time
10:04 <happyaron> ok, great
10:04 <happyaron> that would make both ibus and fcitx included in the image
10:05 <happyaron> now the only input method in image is ibus-pinyin, which is for Chinese, to replace it we'll pull in fcitx
10:06 <darkxst> night all
10:06 <seb128> night darkxst
10:08 <seb128> ok, I give up on debugging that issue for now
10:08 <seb128> Laney, so, the u-s-s notifications, I was wrong, that code uses the gappinfo api to get the name
10:09 <Laney> I thought so
10:09 <seb128> Laney, that works and displays translated under unity7 and not unity8, on the same machine
10:09 <Laney> that works with langpacks already
10:09 <Laney> O_O
10:09 <seb128> I did go trough /proc/pid/environ
10:09 <seb128> no difference I can see
10:09 <seb128> I set the same LANG LANGUAGE LC_*
10:09 <Laney> do we call setlocale(LC_ALL, "") in u-s-s?
10:09 <Laney> surely so because other translations work
10:09 <seb128> no, but I tried to add that
10:09 <seb128> no difference
10:09 <seb128> and the code works under unity7
10:10 <Laney> ...
10:10 <seb128> why would it be required only under it?
10:10 <seb128> in src/i18n.cpp
10:10 <seb128> void initTr(const char *domain, const char *localeDir)
10:10 <seb128> {
10:10 <seb128> setlocale (LC_ALL, "");
10:10 <seb128> bindtextdomain(domain, localeDir);
10:10 <seb128> textdomain(domain);
10:10 <seb128> I added the setlocale line
10:10 <seb128> but that doesn't fix it
10:10 <seb128> I'm puzzled
10:10 <Laney> one second
10:11 <seb128> my current guess is that something in e.g qt5's x11 backend does system or locale init in a different way than the mir backend
10:11 <seb128> but that's random guess
10:13 <Laney> I guess you can gdb and break inside glib to see if these functions are being called
10:14 <seb128> yeah, that's what I was planning to do next
10:14 <seb128> "these" being?
10:14 <Laney> in GKeyFile I think (or GDesktopAppInfo) there's some fallback to use gettext
10:15 <seb128> I was going to try to stop on g_app_info_get_display_name() and see what is the locale/domain/etc
10:15 <Laney> g_key_file_get_locale_string
10:17 <seb128> ok, called on my desktop
10:17 <seb128> let's see on unity8
10:24 <ochosi> Laney: i just read in the log that there seems to be a tendency against gtk3.16, i presume this is not definitive yet? also, a bit surprised, since the call for testing only went out yesterday
10:25 <Laney> ochosi: I sent it last Friday no?
10:25 <ochosi> oh
10:25 <Laney> The call for testing was just that though
10:25 <Laney> it showed more issues up ...
10:26 <ochosi> tbh it only reached me indirectly, guess there are more MLs i have to subscribe to
10:26 <Laney> so it did its job as far as I'm concerned
10:26 <ochosi> ok
10:26 <Laney> ah yes, this kind of stuff I usually send to ubuntu-desktop@lists.ubuntu.com
10:26 <ochosi> yeah, i was away over the weekend until yesterday, so i only heard about it yesterday
10:26 <ochosi> that might explain the lag
10:27 <ochosi> will the definitive decision be announced on that ML too?
10:27 <Laney> yeah I'll follow up soon
10:28 <ochosi> ok, ty!
10:29 * larsu hopes for the best
10:29 <ochosi> same here
10:37 <willcooke> bah.  Upgraded phone to latest devel - wont boot.
11:06 <Laney> woah
11:07 <Laney> started sbuild, lightdm died
11:17 <Laney> what is going on :(
11:17 <Laney> "Waiting for network configuration..."
11:26 <Laney> kernel
11:26 <Laney> didrocks: was using -13 (moving from other channel)
11:26 <Laney> is there a 14 now?
11:26 <didrocks> Laney: ok, so -12 was working for me, I didn't try yet -14 (upgraded today, but didn't reboot)
11:26 <Laney> 12 is okay, that's what I went back to
11:27 * Laney tries dist-upgrade
11:41 <Laney> didrocks: ah, -13.14 seems to work
11:44 <didrocks> Laney: nice, I'll reboot later today and confirm
11:45 <nessita> seb128, hello! me again. Would you know why meld (http://meldmerge.org/), since the upgrade to vivid, shows its background in black instead of white? see https://drive.google.com/a/canonical.com/file/d/0B-cmfDncRJmYRFZSdDJuMjRoZVE/view?usp=sharing
11:45 <nessita> shall I file a bug?
11:54 <Laney> nessita: yes, (meld + ubuntu-themes)
11:54 <Laney> larsu usually fixes those, I guess he's subscribed to ubuntu-themes so will see it
11:55 <nessita> on it
11:56 <larsu> nessita: I might not be, please add me as subscriber
11:56 <nessita> larsu, kk, thanks
11:56 <Laney> nessita: I can't reproduce it myself though so please include steps
11:58 <nessita> Laney, tricky, I just opened meld and the background was black. I have a vivid system upgraded from utopic.
11:58 <Laney> me too
11:58 <Laney> but it looks normal here
11:59 <didrocks> willcooke: told you aquarius would be happy: https://plus.google.com/+StuartLangridge/posts/9fe7W2ijNhJ
12:00 <larsu> Laney, nessita: overlay-scrollbars?
12:00 <nessita> Laney, is ubuntu-themes a package I should have installed?
12:00 <larsu> yes
12:00 <Laney> light-themes
12:01 <larsu> oops, I always confuse the package and launchpad name
12:01 <nessita> light-themes: Installed: 14.04+15.04.20150128-0ubuntu2
12:01 <Laney> ya, I have o-s
12:01 <nessita> ok, filling the bug
12:01 <nessita> Laney, what is o-s?
12:01 <Laney> overlay-scrollbar-gtk3
12:01 <Laney> i.e. if you do GTK_MODULES= meld ... is it right?
12:03 <nessita> let me check
12:03 <nessita> Laney, GTK_MODULES= meld still shows a black background
12:04 <Laney> hmm
12:05 <nessita> https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1421180
12:05 <ubot5> Launchpad bug 1421180 in meld (Ubuntu) "Meld shows background in black instead of white" [Undecided,New]
12:05 <nessita> Laney, shall I mark it as also affecting ubuntu-themes then?
12:06 <Laney> yes please
12:06 <nessita> done
12:06 * larsu is having trouble reproducing
12:06 <willcooke> didrocks,  yay!
12:29 <Laney> ah
12:29 <Laney> we need to theme the "osd" class for totem's new controls
12:29 <Laney> looks nice under adwaita, ambiance not so atm ...
12:29 <larsu> we're not doing that yet?
12:30 * larsu thought he saw some .osd in there
12:30 <Laney> I don't think so, certainly doesn't look like it
12:30 <Laney> (transparent)
12:39 <Laney> larsu: seb128: darkxst: others: I uploaded a totem 3.14 to ppa:ubuntu-desktop/ppa, please try when it's built
12:39 <Laney> (should be able to see the osd issue then)
12:40 <larsu> will do, thanks
12:42 <nessita> larsu, so about the black meld issue, I tried purging it from the system and re-installing, and I still get the same issue. Is there other package that I should have installed that could help workarounding/fixing the issue?
12:43 <larsu> nessita: I don't think so. Does it happen with other themes as well?
12:43 <seb128> Laney, k
12:43 <nessita> larsu, let me check if I have other themes
12:44 <nessita> larsu, tried radiance and high contrast, same issue in bpth
12:44 <nessita> both*
12:45 <nessita> also, I may add to the bug, every time I hit "alt + tab" there is a glitch in the meld window because the files being merged are somehow set (super quickly) to None and then to the original file again. May record a video to be more explicit
12:47 <larsu> nessita: I've noticed this. probably a bug in meld
12:47 <larsu> nessita: and you're still seeing this even with overlay-scrollbars off?
12:48 <seb128> nessita, I can't confirm that one either
12:49 <seb128> seems a duplicate of https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1404720
12:49 <ubot5> Launchpad bug 1404720 in meld (Ubuntu) "comparison view has unreadably dark background" [Undecided,New]
12:50 <Laney> yeah he doesn't have o-s in that screenshot
12:51 <nessita> larsu, how can I set overlay-scrollbars off?
12:51 <larsu> nessita: start meld with `GTK_MODULES= meld`
12:52 <nessita> ah, yeah, I tried that, same black background
12:52 <seb128> nessita, what desktop env do you use?
12:52 <nessita> seb128, unity
12:53 <seb128> nessita, dpkg -l | grep libgtk-3-0
12:53 <nessita> all default settings except the task switcher, which I use the one that does not group windows
12:53 <nessita> ii  libgtk-3-0:amd64                                     3.14.8-0ubuntu1                            amd64        GTK+ graphical user interface library
12:53 <seb128> hum, k
12:53 <nessita> happy to keep debugging, jut throw commands at me :-D
12:53 <nessita> I use meld a lot, so this is important to me
12:54 <nessita> (and the black background makes it very hard to read)
12:54 <larsu> nessita: ok, let's get out the good stuff. Install libgtk-3-dev, restart meld, put the cursor over one of the panes and hit Ctrl+Shift+I
12:54 <larsu> gtk inspector should pop up
12:55 <nessita> larsu, on it
12:55 <larsu> and on the left side, a "MeldSourceView" should be selected
12:56 <seb128> nessita, when did the issue start?
12:57 <seb128> nessita, can you try to apply https://git.gnome.org/browse/meld/commit/?h=meld-3-12&id=281583a05117b9d05acb010c98adfebfeb27f70c
12:58 <nessita> seb128, I know I said I use meld a lot, and I do, but because some specific work assignment I did not work on code for several days, and I just restarted (fun) work today, so I noticed it today
12:58 <seb128> you use(d) KDE so could be ^
12:58 <nessita> seb128, but I haven't opened meld since I moved to vivid, so any time after that
12:58 <seb128> larsu, ^
12:59 <larsu> seb128: I'm using it constantly as well, never saw this issue
12:59 <seb128> larsu, KDE?
12:59 <larsu> meld :)
12:59 <nessita> larsu, so on the left side, in the Objects tab, I see GtkSettings, meld+meldapp+MeldApp, GtkAboutDialog, GtkApplicationWIndows, and 3 GtkFileChooserDialog
12:59 <nessita> larsu, not sure where to fing MeldSourceView
13:00 <tjaalton> ooh, that meld bug.. yes it's black for me too
13:00 <larsu> nessita: you need to select the MeldSourceView, either by drilling down or by clicking on the selector button in the toolbar
13:00 <larsu> nessita: and then clicking on the widget
13:00 <seb128> nessita, can you share your .config/gtk-3.0/Settings.ini if you have one?
13:00 <seb128> tjaalton, ^
13:00 <tjaalton> not found
13:01 <nessita> nessita@miro:~$ cat .config/gtk-3.0/Settings.ini
13:01 <nessita> cat: .config/gtk-3.0/Settings.ini: No such file or directory
13:01 <nessita> seb128, I only have .config/gtk-3.0/bookmarks
13:02 <nessita> larsu, entering a call, will be back with this as soon as I finish
13:02 <seb128> nessita, tjaalton, any chance you can try https://git.gnome.org/browse/meld/commit/?h=meld-3-12&id=281583a05117b9d05acb010c98adfebfeb27f70c
13:02 <seb128> you can probably edit the system files, python, it's easy
13:02 <Laney> mitya57 spoilered my email!
13:03 <Laney> while I was in the middle of writing it too
13:03 <nessita> seb128, will try, sure
13:03 <larsu> wubbly!
13:04 <seb128> whinoceros!
13:04 <larsu> :)
13:06 <Laney> yeah I spoilered the release name too
13:08 <Laney> annoying that emoji don't work in g-t for me >:(
13:08 <tjaalton> seb128: yep, fixed
13:08 <seb128> :-)
13:08 <seb128> larsu, ^
13:08 <seb128> tjaalton, thanks for testing, I'm going to update meld to the current stable version which includes that fix
13:08 <seb128> nessita, ^
13:09 <tjaalton> cool
13:09 <nessita> larsu, so sorry if I'm not seeing something obvious, but I can not find MeldSourceView in
13:09 <nessita> https://drive.google.com/a/canonical.com/file/d/0B-cmfDncRJmYMEVkMDBkVkdNblU/view?usp=sharing
13:09 <nessita> seb128, ack, trying now (was tryingt to get larsu 's info)
13:10 <larsu> nessita: not necessary anymore. The problem seems to be that meld changes css and doesn't repaint
13:12 <nessita> seb128, YES
13:12 <nessita> larsu, ack. So, what seb128 pointed out worked
13:12 <tjaalton> now I still have this weird problem since utopic where some fonts don't display.. guest account is broken as well, so apparently some packages don't mix too well
13:15 <nessita> seb128, larsu thanks a lot for your help! will comment on the bug
13:16 <tjaalton> hm, my font issue seems to be mostly/only with firefox/tb
13:17 <seb128> tjaalton, when it happens here xchat-gnome is impacted as well
13:18 <tjaalton> so gtk2 related?
13:18 <tjaalton> hmm no
13:18 <seb128> I was about to say that, but xchat-gnome is gkt3 since vivid
13:18 <tjaalton> right
13:18 <seb128> but I'm unsure I saw the issue recently, so maybe it was still old gtk by then
13:18 <seb128> but I doubt firefox uses gtk for font rendering
13:19 <tjaalton> a vanilla installation works just fine
13:20 <seb128> you mean? there issue is happening all the time on your installation?
13:21 <tjaalton> yes
13:21 <tjaalton> one way to reproduce is to read phoronix (yuck) forums
13:21 <tjaalton> the commented posts are blank
13:22 <tjaalton> also the page numbers
13:37 <ogra_> seb128, tjaalton i see that too from time to time in FF
13:37 <ogra_> (missing fonts or CSS)
13:39 <Laney> hmm
13:39 <Laney> looks like gtalk xmpp is going away on monday
13:39 <tjaalton> ogra_: oh, so I'm not seeing things
13:39 <Laney> guess we need to do some updates
13:39 <tjaalton> err, imagining things..
13:40 <larsu> Laney: does that mean it's not usable from telepathy anymore?
13:40 <Laney> i guess
13:48 <seb128> xmpp used to be a thing
13:48 <desrt> :(
13:48 <seb128> now no msn, no gtalk
13:48 <seb128> that's a shame :/
13:48 <desrt> seb128: it's okay.  we'll always have telegram
13:50 <desrt> seb128: can't really blame them, though, to be honest
13:50 <desrt> look at us and freedesktop.org
13:50 <desrt> we can either go through the specs process, or we can JFDI
13:50 <desrt> interop definitely slows you down
13:51 <seb128> right :-/
13:51 <desrt> i think that's what makes telegram so good
13:51 <desrt> they were super-pragmatic
13:52 <desrt> they have the same 'nice to have' list as everybody
13:52 <desrt> but at the top they put 'it has to work well, today'
13:52 <didrocks> focusing on one experience and getting it supported is clearly the key
13:52 <desrt> so the other 'nice things' have to be pushed aside
13:52 <willcooke> Sweet5hark, hey!  Getting "terminate called after throwing an instance of 'com::sun::star::uno::DeploymentException" when trying to run LO under Xmir - any suggestions?
13:53 <willcooke> this is on U8 / Mir / Xmir btw
13:53 * desrt is vaguely entertained by the string 'sun::star'
13:56 <Sweet5hark> willcooke: yeah, something is wrong with extension deployment on 4.4.x. Do you have any python extensions somewhere?
13:57 <willcooke> Sweet5hark, erm, I didnt change anything in the extensions, so probably not
13:57 <willcooke> erm
13:57 <willcooke> unless I pulled in some strange python version
13:58 <Sweet5hark> willcooke:  sounds very much related to bug 1419836, which I am currently looking into ...
13:58 <ubot5> bug 1419836 in libreoffice (Ubuntu) "LibreOffice 4.4 (PPA): Extension can't be installed: Message: com.sun.star.uno.RuntimeException) "unknown error!"" [Undecided,New] https://launchpad.net/bugs/1419836
13:58 <Sweet5hark> willcooke: this is with LibreOffice 4.4.0 on vivid?
13:59 <willcooke> Sweet5hark, yeah
13:59 <willcooke> Sweet5hark, sounds like very thing is in hand though - thanks :)
13:59 <willcooke> oh, it';s 1:1 time anyway
13:59 <willcooke> Sweet5hark, give me 2 mins to get tea?
14:00 <Sweet5hark> willcooke: sure, sure
14:00 <willcooke> Sweet5hark, thx
14:21 <willcooke> hey larsu - I think pretty much everybody has requested a 360 from you
14:22 <seb128> willcooke, did they?
14:22 <larsu> uh oh
14:22 * larsu should get busy?!
14:23 <seb128> larsu, I'm changing my request to Laney instead, don't worry ;-)
14:23 <desrt> ya.  me too.
14:23 <willcooke> too late desrt
14:23 <desrt> oh wait.  already picked laney :/
14:23 <larsu> ts, would have loved to review you guys
14:24 <seb128> larsu, sorry, next time :-)
14:24 <larsu> seb128: I'll put you down anyway :P
14:24 <seb128> larsu, yeah, please do, I'm happy to review you, and I didn't have so many people asking me
14:25 <larsu> :)
14:31 <seb128> willcooke, Sweet5hark, libreoffice doesn't start anymore for me either today on vivid
14:32 <willcooke> seb128, all under control :)
14:34 <Sweet5hark> seb128: as a hotfix: do a "mv ~/.config/libreoffice ~/.config/libreoffice_".
14:35 <Sweet5hark> seb128: Havent had that "cant start at all" here yet, so would be interested if the above does help as a workaround ...
14:35 <Sweet5hark> seb128: (and yes, I am working on figuring out what is going wrong there properly)
14:35 <seb128> Sweet5hark, willcooke, ok, mine works again without that
14:36 <seb128> Sweet5hark, willcooke, update-manager updated only part of the packages, a set was blocked on libmwaw-0.3-3 to be installed
14:36 <seb128> seems like the depends don't enforce the update to not be partial
14:36 <seb128> but it doesn't handle the out of sync between binaries
14:36 <seb128> works again after upgrading the remaining ones
14:50 * willcooke backlogging
14:51 * willcooke tries an update again
14:51 <willcooke> Sweet5hark, oh, I tried deleting all of ~/.config/libreoffice before, didnt help me - but might be unrelated
15:02 <willcooke> Sweet5hark, I see another LO update when dist-upgrading
15:03 <jcastro> didrocks, http://askubuntu.com/a/584704/235
15:03 <jcastro> how would an upgrade look like?
15:11 <Saviq> willcooke, FYI: window geometry memory just landed in archive
15:12 <willcooke> Saviq, woo!  Thanks!
15:12 <willcooke> This is awesome news.  Now when you switch between windowed and staged mode the windows will remember where they were.
15:12 <willcooke> seb128, ^^
15:13 <willcooke> Saviq, presumably that's held in memory rather than, say a config file?
15:13 <Saviq> willcooke, sql db
15:13 <willcooke> ooooh
15:13 <willcooke> nice
15:13 <willcooke> sqlite?
15:13 <Saviq> yup
15:13 <willcooke> cool
15:14 <willcooke> is that part of the u1db stuff?
15:14 <Saviq> willcooke, no actually, you need a postgres install ;P
15:14 <willcooke> hah
15:14 <Saviq> willcooke, not right now
15:14 * willcooke has evil thoughts about syncing window positions across devices
15:14 <Saviq> willcooke, it's not the target architecture for this most probably
15:14 <Saviq> willcooke, yeah, no
15:14 <seb128> Saviq, great, saw the changelog ... what's the id? like does it work between mode, or also between sessions?
15:14 <willcooke> :D
15:15 <Saviq> seb128, both
15:15 <seb128> excellent!
15:15 <willcooke> would this work for qt and gtk native apps as well?
15:15 <seb128> Saviq, how does it reconize the surface?
15:16 <willcooke> Laney, noticed any oddities with the UK archive servers today?
15:16 <willcooke> my updates keep crapping out
15:18 <Saviq> seb128, by app id right now, IIUC
15:18 <Saviq> mzanetti has details
15:18 <seb128> k
15:18 <seb128> which is fine as long as apps have one surface I guess :-)
15:19 * mzanetti reads scrollback
15:20 <mzanetti> yes, appId so far.
15:20 <mzanetti> we need to change that to windowId once we have such a thing
15:20 <mzanetti> but it'll do for MWC
15:22 <seb128> right
15:27 <willcooke> Sweet5hark, re-upgraded and everything is back to normal
15:30 <willcooke> seb128, mlankhorst - Typing in to a LO doc under Xmir \o/
15:30 <mlankhorst> goodie
15:31 <seb128> great
15:31 <willcooke> AND pointing at things :D
15:31 <willcooke> and clicking
15:31 <mlankhorst> haha good
15:31 <willcooke> when this broken track pad allows me
15:31 <willcooke> power menu still crashes things
15:31 <willcooke> bah
15:31 <willcooke> My life is not perfect.
15:32 <willcooke> ;)
15:32 <Laney> willcooke: with what message?
15:33 <willcooke> erm
15:33 <willcooke> I turned it off
15:33 <willcooke> I'll try again
15:34 <Laney> if it's something aboutu a mismatch on Translations-en then yes
15:34 <willcooke> Laney, the logs would be in cachce upstart right?
15:35 <Laney> I don't think that update-manager logs
15:35 <willcooke> ohh
15:36 <willcooke> sorry - I'm talking cross purposes
15:36 <willcooke> erm, so the upgrade works now
15:36 <willcooke> meh
15:36 <Laney> ya, that happens
15:36 <Laney> you hit some inconsistency and then it gets fixed
15:52 <didrocks> jcastro: we let the upstream upgrade mechanism instead of messing with it
15:52 <jcastro> ack
16:32 <larsu> Trevinho: why did you change blacklisting in that indicator-appmenu branch as well?
16:32 <larsu> and again, I'm not really happy with exporting all menus at all times
16:32 <larsu> listening I mean
16:33 <larsu> it seems to work though
16:33 <Trevinho> larsu: well, it was just wrong to look only to these hardcoded paths
16:33 <Trevinho> larsu: as for exporting all the menus, I agree, but there's just not another way to do this
16:33 <Trevinho> without rewriting everything
16:33 * larsu hates unrelated changes in the same branch
16:33 <Trevinho> :P
16:33 <larsu> Trevinho: yes there is. Get rid of this LIM madness
16:33 <larsu> (sorry)
16:34 <Trevinho> larsu: that's not the designed stuff
16:34 <Trevinho> solution
16:36 <larsu> Trevinho: I know :)  Anyhow, sorry for taking so long to take your branch for a spin. It seems good, approving
16:36 <larsu> Trevinho: I hope our deal's still on? :P
16:36 <Trevinho> larsu: anyway, considering that the indicator was generating all the menu data always and in any case, this won't change much things... a part from the fact that there will be more exported labels on dbus... but they will be updated less frrequently
16:37 <larsu> Trevinho: did the indicator cache data for all menus?
16:37 <Trevinho> larsu: yes, my hands are just bloody as they're inside the compiz core...
16:37 <larsu> hahaha
16:37 <Trevinho> larsu: it was and it will
16:37 <larsu> ok
16:38 <Trevinho> it was just loading them as soon as they were needed, so... once you focused a window. compared to now, where we do that always
16:38 <larsu> so the change is really just making the indicator exporting all the things to unity
16:38 <Trevinho> larsu: yes, and adding the relative parent xid
16:38 <Trevinho> so that we can then filter them out
16:39 <Trevinho> larsu: unity side of things was https://code.launchpad.net/~3v1n0/unity/lim-everywhere
16:39 <Trevinho> err is at
17:46 <seb128> Laney, ok, getting closer from the settings/translations/unity8 issue
17:47 <Laney> oh really!
17:47 <Laney> uitk/uss?
17:48 <seb128> Laney, I still don't know, but g_dgettext() fails to return a translation under unity8
17:48 <seb128> dgettext() works
17:48 <seb128> I'm reading glib source ;-)
17:48 <seb128> " For this
17:48 <seb128> * feature to work, the call to textdomain() and setlocale() should
17:48 <seb128> * precede any g_dgettext() invocations.  For GTK+, it means calling
17:48 <seb128> * textdomain() before gtk_init or its variants."
17:49 <seb128> i18n.cpp does call     textdomain(domain); though
17:49 <seb128> and I've added a setlocale() call to it as well
17:57 <seb128> doesn't make sense :-/
17:58 <Laney> does g_dgettext do anything?
17:58 <seb128> I wonder if qt's x11 backend does some locales init that the mir backend doesn't
17:58 <seb128> anything?
17:58 <seb128> well, it returns me the english string instead of the french one under unity8
17:58 <Laney> other than just call dgettext ...
17:59 <seb128> Laney, it calls that http://paste.ubuntu.com/10191432/
17:59 <seb128> and use dgettext() if that is true
17:59 <seb128> so that must be false
18:00 <seb128> our domain is not the default one but it has translations
18:04 <seb128> k, so something under unity8 must call that function before us and have it return false
18:04 <seb128> right?
18:05 <Laney> I guess
18:05 <Laney> can you break there?
18:05 <seb128> no
18:05 <Laney> get a bt
18:05 <seb128> but I can rebuid glib and do that
18:05 <seb128> I don't think you can "b" on a static symbol
18:05 <Laney> g_gettext?
18:05 <seb128> but I can remove the static and rebuild and do it
18:05 <Laney> d
18:05 <seb128> then step from it?
18:06 <Laney> should be enough to just see where this is called
18:06 <seb128> I guess yeah
18:06 <Laney> it's going to call the other one
18:06 <Laney> and you know it returns false anyway
18:07 <seb128> shrug, hate that
18:07 <seb128> using gdb on the phone to start the app doesn't work
18:07 <seb128> it hits sigbus errors for some reasons
18:13 <Laney> :/
18:14 * willcooke -> EOD
18:14 * willcooke -> EOD
18:14 <willcooke> hrm
18:17 <seb128> Oh yeah
18:17 <seb128> got ja
18:18 <Laney> O_O
18:18 <seb128> http://paste.ubuntu.com/10191675/
18:19 <seb128> hum, guess not
18:19 <seb128> grrr
18:26 <Laney> i'm off too
18:26 <Laney> swapping tomorrow but may be on a bit in the morning
18:27 <Laney> can help look at this bug on monday if you want
18:35 <seb128> Laney, I'm going to have it resolved by then I hope ;-)
18:35 <seb128> Laney, enjoy the swap day!
20:56 <robert_ancell> kenvandine, what device are you running cut the rope on?
20:57 <kenvandine> robert_ancell, krillin
20:57 <kenvandine> and mako too
20:57 <kenvandine> but only briefly on the mako
20:58 <robert_ancell> kenvandine, it's really low frame rate for me on mako
20:59 <robert_ancell> just wondering if that's the same on krillin / expected
21:00 <kenvandine> it's perfectly smooth on my krillin
21:00 <kenvandine> i played 2 levels on the mako
21:00 <kenvandine> and it was smooth
21:00 <robert_ancell> weird
21:01 <kenvandine> i've been playing the free version for a while on krillin
21:01 <kenvandine> it's always been slick and smooth on that
21:02 <kenvandine> robert_ancell, Elleo said it was choppy on his mako too
21:09 <kenvandine> bregma, you have the yoga 2 pro right?
21:09 <bregma> THE Yoga 2 Pro, yeah
21:09 <kenvandine> and love it?
21:09 <bregma> hate the keyboard, love the screen
21:09 <kenvandine> i'm thinking about buying one
21:10 <bregma> the case also feels very nice
21:10 <bregma> all sexy-like
21:10 <kenvandine> hard to find something with a display like that :)
21:10 <kenvandine> touch screen works fine?
21:11 <bregma> the touch screen works great
21:11 <kenvandine> i'm thinking it'll be a good candidate to play with convergence features :)
21:11 <bregma> it also has a gyro, accel, and magnetometer, if I could figure out how to use them
21:13 <kenvandine> does the accel work in ubuntu too?
21:13 <kenvandine> i assume we don't actually handle the rotation
21:13 <kenvandine> yet
21:13 <bregma> sensor support in general in Linux is in its early days
21:14 <bregma> these sensors are IIO, I have others that are I2C, and there's no goof userspace support for any of these
21:14 <bregma> it's like PC ausio was in the 1990s
21:14 <bregma> *audio
21:14 <kenvandine> :)
21:14 * kenvandine hasn't heard of IIO  :)
21:14 <bregma> or even video -- Hercules or Trident?
21:16 <bregma> I just want to be able to turn a tablet upside down and shake it to clear the screen, why does it have to be so hard?
21:16 <kenvandine> haha
21:16 <bregma> the feature for the Yoga 2 Pro I need to to detect when the keyboard is folded underneath (tablet mode) and disable the keyboard
21:17 <kenvandine> and enable the osk
21:17 <kenvandine> i'm kind of interested in the yoga 3 11"
21:17 <bregma> there's a hack out there to do that using the position sensor, I tested it but not installed it
21:17 <kenvandine> fanless :)
21:17 <kenvandine> but not the qhd display
21:18 <kenvandine> and not sure what to think of the processor
21:18 <bregma> there is a fan, but it rarely comes on and it's whisper quiet
21:18 <kenvandine> the yoga 3 is fanless
21:18 <kenvandine> has the intel M processor
21:18 <kenvandine> 800Mhz
21:18 <kenvandine> up to 1.7G i think
21:18 <bregma> it's good enough for what I do (building software, etc)
21:19 <kenvandine> i think the yoga 2 pro is a safer bet
21:19 <kenvandine> faster processor, and qhd screen :)
21:19 <robert_ancell> bregma, does the yoga have a sensor for that? I have a new Toshiba that does the screen flip but it doesn't seem to have a sensor
21:20 <bregma> robert_ancell, yes, it has a "position sensor" to indicate various keyboard positions (it does effectively 360 rotation of the keyboard)
21:20 <robert_ancell> bregma, how do you access that?
21:21 <bregma> through the /sys/bus/IIO interface
21:21 <bregma> it's pretty wretched
21:21 <robert_ancell> any tools to make that more accessible?
21:22 <bregma> there was a kernel patch floating around to redirect IIO through evdev, but it seems to be stillborn
21:22 <robert_ancell> hmm, I have a bunch of devices in there. I guess one of them might be related to screen position
21:24 <bregma> poke around, they give up their names and a description of their data if you squeeze hard enough
21:24 <robert_ancell> I've got the names but not sure what is what
21:25 <robert_ancell> accel_3d, gyro_3d, magn_3d, incli_3d, dev_rotation, als
21:26 <bregma> incli_3d is a 3D inclinometer
21:26 <bregma> als is ambient lighting
21:26 <bregma> https://github.com/pfps/yoga-laptop.git has some tools you might be able to take advantage of
21:27 * robert_ancell just tried to bring up the ubuntu switcher on his Android phone
21:27 <bregma> is that the new Unity 8 switcher?
21:27 <robert_ancell> yeah, the Ubuntu phone one
21:27 <bregma> there's a bug asking for it to be ported to Android
21:28 <bregma> I think it was triages as 'wishlist'
21:28 <robert_ancell> haha
21:29 <darkxst> Laney http://pastebin.com/scrYiXvE
21:34 <ochosi> larsu: i presume you know about this already, but progressbars are quite tiny in some apps with gtk3.14 (e.g. software center or update-manager)
21:34 <larsu> ochosi: ah right, I remember. Thanks
21:34 <ochosi> i guess that's a toolkit/app issue, not theming related
21:36 <larsu> not sure - it worked before, no?
21:37 <ochosi> before what?
21:38 <larsu> 3.14
21:44 <ochosi> larsu: yeah, i'm pretty sure they weren't *that* tiny
22:14 <Laney> darkxst: ok, I have a ppa1 anyway but I think I forgot to upload it
22:22 <darkxst> Laney, ok, gave it a quick test under GNOME seems fine
22:22 <Laney> neat
22:23 <Laney> just need the split then, hopefully before FF
22:23 <darkxst> we are still trying to confirm package naming with the DM
22:23 <Laney> ack
22:24 <Laney> berto's usually quite responsive, sure you'll be fine
22:34 <darkxst> ok
00:53 <tmpRAOF> Dear libtool: WTF.
06:38 <pitti> Good morning
06:39 <darkxst> hey pitti
06:39 <darkxst> storms are hitting! http://www.bom.gov.au/products/IDR021.loop.shtml
06:45 <TheMuso> darkxst: Where are you?
06:45 <darkxst> TheMuso, A little north of Melbourne
06:45 <TheMuso> darkxst: Ah yeah, nasty.
06:45 <TheMuso> darkxst: We are supposed to get storms here in Sydney too I think at some point.
06:46 <TheMuso> And hey there pitti.
06:46 <darkxst> TheMuso, we haven't had any rain at all in about a month, its probably useful!
06:46 <pitti> hey TheMuso, how are you?
06:46 <pitti> morning darkxst
06:46 <TheMuso> Oh yeah, as long as its not too heavy.
06:46 <TheMuso> pitti: Well thanks, yourself?
06:46 <pitti> TheMuso: quite well, thanks
06:47 <TheMuso> pitti: I've actually got something interesting to discuss re systemd, and its pkg-config file. For various reasons, I've been working to build pulseaudio with different prefixes/install locations, which gave me errors. This lead me to trying distcheck with puseaudio. I found that systemd's pkg-config file has the prefix hard-coded in the various service/unit directory variables. I see no bugs upstream/anywhere about this. Is this known?
06:48 <TheMuso> pitti: i.e systemduserunitdir=/usr/lib/systemd/user -- I would expect that variable to use ${prefix} rather than hard-code /usr...
06:49 <TheMuso> pitti: I was actually trying to come up with a patch to fix it, but my autofoo is lacking it seems...
06:49 <darkxst> TheMuso, maybe Lennarty did it on purpuse so you don't change the prefix ;)
06:50 <TheMuso> darkxst: But that makes no sense. If you look at other .pc files, when referring to the include dir etc, they all refer to prefix with a variable.
06:50 <TheMuso> darkxst: And it is likely to break the distcheck of packages that use systemd in some way, i.e pulseaudio.
06:50 <TheMuso> darkxst: Actually, it does break distcheck.
06:50 <TheMuso> There is no unlikelyness about it. :)
06:51 <darkxst> TheMuso, I wasn't actually being serious there!
06:51 <TheMuso> darkxst: Yeah saw the smily, but words on teh screen alone are not enough to convey such things, so yeah makes sense in context. :)
06:52 <darkxst> TheMuso, hardcoded paths are in the pc.in file?
06:53 <TheMuso> darkxst: No, it uses substitution to fill them in.
06:53 <TheMuso> But that has me wondering actually...
06:53 * TheMuso checks something.
06:54 <TheMuso> Hrm ok, as I expected. Never mind, thought the prefix variable was part of the .pc.in files I checked that look sane.
07:01 <darkxst> TheMuso, why are you building pulseaudio with different prefixes? if you just want to isolate from your system? jhbuild can do that
07:04 <TheMuso> darkxst: Reasons, I cannot really say.
07:06 <TheMuso> darkxst: But even so, distcheck is designed to make sure a package is buildable with custom prefixes as well as using a different DESTDIR.
07:06 <darkxst> just saying, jhbuild has quite some hacks, to make things work with messed up mixed prefixes ;)
07:06 <TheMuso> darkxst: Nice to know, but jhbuild is overcomplicated for what I am doing.
07:06 <darkxst> TheMuso, some things take vars from the actual installed .pc files
07:08 <TheMuso> darkxst: I'm sure jhbuild is wonderful and all, but more than what I need, and, still we come back to pulseaudio distcheck failing.
07:13 <darkxst> TheMuso, maybe a bug in pulseaudo configure.ac
07:14 <TheMuso> darkxst: It could certainly be worked around in pusleaudio's configure.ac, but IMO that is rather hacky, and not the correct solution.
07:14 <didrocks> good morning
07:15 <TheMuso> Morning didrocks.
07:15 <didrocks> hey TheMuso
07:15 <darkxst> TheMuso, this is a fruitless conversation since you can't say what you are doing ;) sure you can work it out!
07:15 <darkxst> hey didrocks
07:16 <didrocks> good evening darkxst ;)
07:16 <darkxst> didrocks, stormy evening! first rain in over a month!
07:17 <didrocks> darkxst: waow, is it planned to stay over the week-end or just doing the night?
07:17 <didrocks> during*
07:17 <TheMuso> darkxst: Sure I can, but I am still of the thought that working things out *properly* means fixing systemd's pkg-config.
07:17 <TheMuso> Anyway, EOD for me.
07:17 <darkxst> Tonight and sat
07:18 <darkxst> TheMuso, pkg-config does what it is told
07:18 <TheMuso> We had a lovely late storm that roled into my area of Sydney last night, just as I went to sleep, was lovely.
07:18 <TheMuso> darkxst: Yeah I know that. Anyway, I can work around it for now.
07:21 <darkxst> didrocks, https://code.launchpad.net/~noskcaj/ubuntu/vivid/appstream-glib/mir-fixes/+merge/249562 should clean up the appstream-glib MIR
07:22 <didrocks> darkxst: oh DSO link errors… insane we still have this nowdays, put my mind back more than 5 years ago :)
07:22 <darkxst> didrocks, I don't think Fedora builds with as-needed
07:22 <darkxst> even still
07:23 <darkxst> s/builds/links/
07:23 <darkxst> I hit them all the time in jhbuild
07:23 <didrocks> darkxst: oh really? I thought they turned on the gold linker… but probably not when seeing that :)
07:23 <didrocks> darkxst: need sponsoring?
07:23 <didrocks> looking good to me
07:23 <darkxst> didrocks, yes, I don't have powers for appstream-glib
07:24 <didrocks> darkxst: running a sbuild pass first to ensure the tests are working and then, sponsoring
07:28 <Noskcaj> thanks didrocks
07:28 <didrocks> yw Noskcaj :)
07:36 <didrocks> Noskcaj: darkxst: built successfully, sponsored and MIR approved
07:36 * didrocks closes tabs
07:49 <Noskcaj> didrocks, Since you approved the MIR, would you have time to s/appdata-tools/appstream-util in all the r-deps? The same binary is in both
07:49 <Noskcaj> It seems to be too trivial of a patch for it to be worth my time as someone without upload rights
07:50 <didrocks> Noskcaj: quite busy today, (and off Monday). If it can wait Tuesday (and you remind me about it), sure can do
07:50 <Noskcaj> cool
07:50 <darkxst_> Noskcaj, some naughty people can do copies from ppa's into archive
07:50 <didrocks> yeah, that works as well :)
07:51 * didrocks likes darkxst_'s idea
07:51 <Noskcaj> ok, i'll look at making a ppa tomorrow if no one steps up to do the work
07:51 <didrocks> Noskcaj: keep me posted on Tuesday, I'll do the package copy if nobody did it before then
07:51 <Noskcaj> ty
07:51 <didrocks> yw
08:50 <willcooke> morning
08:50 <seb128> hey willcooke
08:57 <didrocks> hey willcooke
08:59 <popey> anyone else having multi-monitor pain on vivid on Intel today? http://imgur.com/80LcmgV
09:00 <willcooke> popey, on you x220?  So Intel gfx?
09:00 <didrocks> popey: urgh no :/ x220, intel gfx here
09:00 <didrocks> popey: -14 kernel?
09:01 <didrocks> 3.18.0-13.14 here
09:03 <popey> yes
09:03 <popey> bug 1421575
09:03 <ubot5> bug 1421575 in xserver-xorg-video-intel (Ubuntu) "Desktop corruption when changing monitor config" [Undecided,New] https://launchpad.net/bugs/1421575
09:03 <popey> oh hang on, I'm on some dodgy 3.19 kernel
09:03 * popey reboots to sanity
09:04 <didrocks> popey: what are you installing on your poor system? :)
09:04 <popey> installed 3.19 upstream to diagnose some other issue (gpu lockup)
09:04 <popey> but this is way worse
09:04 <didrocks> willcooke: postponed the arduino stuff
09:04 <didrocks> as discussed yesterday
09:04 <willcooke> thanks didrocks
09:04 <didrocks> yw
09:05 <willcooke> I didnt get time to explore Eclipse yesterday
09:05 <willcooke> maybe over the weekend
09:05 <didrocks> willcooke: no worry, we'll backport that to the ppa at worst :)
09:05 <didrocks> popey: trying to compete with attente_ on kernel bisecting?
09:06 <popey> bah, still busted on 3.18
09:06 <popey> but busted differently
09:07 <didrocks> popey: -13.14? -13.13 did have some issues…
09:08 <popey> dunno, i can't ssh into it now, disk light solid, it's not happy
09:08 <didrocks> waow
09:08 <didrocks> just dist-upgraded (quite a lot since yesterday)
09:08 <didrocks> rebooting
09:08 <didrocks> and see if I blame you *personally*
09:08 <willcooke> *brrring* *brrrring*   Hello, IT
09:09 <popey> networking is also busted
09:09 <popey> seems to want to have wifi and wired on at once and is getting upset with this situation
09:10 <willcooke> I had that yesterday on my U8 box, I think it's a different NetMan issue
09:10 <didrocks> popey: sorry, everything's working well here
09:13 <popey> 3.18.0-13-generic is what I am on
09:13 <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1420404/comments/3 btw, summary of the u-s-s translations issue
09:13 <ubot5> Launchpad bug 1420404 in ubuntu-system-settings (Ubuntu) "Name entry in desktop file not localized" [High,In progress]
09:13 <willcooke> seb128, Laney is on swap today
09:14 <seb128> willcooke, I know, but he reads backlog when back usually, that can be monday
09:14 <willcooke> kk
09:14 <willcooke> just making sure
09:15 <seb128> willcooke, it's just a fyi on a bug I spent my day on yesterday
09:15 <willcooke> Hello Laney from the past
09:15 <seb128> he helped me a bit
09:15 <seb128> :-)
09:17 <popey> didrocks: https://www.youtube.com/watch?v=W3ZQ9xW0PhQ :(
09:18 <didrocks> popey: private video
09:18 <popey> fixed, ta
09:19 <didrocks> popey: waow, if we wanted to do it on purpose, we wouldn't be able I guess :)
09:19 <didrocks> I guess it's a question for mlankhorst
09:21 <darkxst> didrocks, just like I hit 5 screws today screwing down architraves ;( certainly can't do that if you try!
09:21 <ogra_> just put some duct tape over it
09:22 <darkxst> ogra_, duct tape will fix it ;)
09:22 <didrocks> darkxst: it's really "Friday 13th" it seems for some of you :)
09:23 <willcooke> :)
09:23 <willcooke> popey, mlankhorst is off today.
09:23 <darkxst> didrocks, doubt that is related to my achitrave problems!
09:24 <popey> balls, it is fine in a guest session
09:24 <popey> so something is knackered in my session
09:24 <popey> do we have a "reset compiz back to defaults" button anymore?
09:25 <didrocks> popey: you think it's compiz? do you have gnome-shell or any other DE?
09:25 <popey> no
09:25 <popey> I'm pure as the driven snow.
09:26 <didrocks> :)
09:26 <ogra_> popey, try removing the monitors.xml file
09:26 <popey> done that
09:26 <ogra_> ah
09:26 * popey copies monitors.xml from a good guest session in
09:26 <popey> \o/
09:26 <ogra_> heh
09:26 <darkxst> popey, just delete it, u-s-d will recreate a good one then
09:26 <popey> Not touching that again today.
09:26 <popey> nope, it didn
09:27 <popey> it created a _worse_ one
09:27 <didrocks> that's weird… maybe it's the gsd config
09:27 <didrocks> let me find it
09:27 <popey> http://paste.ubuntu.com/10201762/ is my good one
09:27 <didrocks> popey: do yo uhave the "bad" one?
09:28 <popey> no, but I can probably make a bad one by breathing near the display applet
09:28 <popey> lemme try
09:28 <didrocks> yeah, would be interesting
09:28 <darkxst> popey, if its creating broken configs, probably xrandr bug
09:28 <popey> k
09:28 <didrocks> darkxst: well, it does create a "good one" in his guest session
09:28 <didrocks> so puzzling…
09:29 <popey> didrocks: http://paste.ubuntu.com/10201816/ is the bad one
09:30 <popey> identical!
09:30 <didrocks> of course
09:30 <popey> but as my user if I touch the monitor config, even if I let it revert back, it still makes the display all messed up and flickery
09:31 <didrocks> popey: yeah, let's see with mlankhorst I guess, he will probably ask you to dump your xrandr configs
09:32 <popey> kk
09:33 <darkxst> popey, that looks like a driver bug
09:33 <popey> it must be something in my session
09:33 <darkxst> (unless xrandr is stuffing up the timings on your modes)
09:51 <willcooke> seb128, do you think I should be able to use gsettings set com.canonical.Unity8 usage-mode Staged to get U8 desktop in to tablet mode?
09:53 <seb128> willcooke, that should work yes
09:53 <willcooke> in which case....
09:53 <willcooke> sad face
09:53 <willcooke> should I be able to do it from an SSH session?
09:53 <willcooke> like,
09:54 <willcooke> do I need to be in the same session or something?
09:55 <didrocks> willcooke: did you get any error? (I think you are not in the same session bus)
09:55 <willcooke> no errir
09:55 <willcooke> when I tried from ssh
09:55 <willcooke> when I try from U8 terminal
09:55 <willcooke> I get a seg fault
09:56 <mlankhorst> ?
09:56 <didrocks> willcooke: if you then gsettings get com.canonical.Unity8 usage-mode, did you get the same value in return?
09:56 <willcooke> $ echo $?
09:56 <willcooke> 0
09:57 <didrocks> willcooke: it should print the value of usage-mode key (so "Staged")
09:57 <willcooke> nada
09:57 <willcooke> hey mlankhorst
09:58 <willcooke> mlankhorst, I know its your day off and all, but there's some weirdness for you to take a look at on Monday from popey up there ^^
09:58 <mlankhorst> define weirdness :P
09:58 <willcooke> mlankhorst, http://imgur.com/80LcmgV
09:59 <willcooke> mlankhorst, https://www.youtube.com/watch?v=W3ZQ9xW0PhQ
09:59 <willcooke> (not Rick Astley)3
10:00 <mlankhorst> looks more like a compiz bug :P
10:00 <mlankhorst> seen the same before
10:00 <popey> yeah, that was my feeling too
10:01 <seb128> willcooke, ssh, you might need to define the dbus env
10:02 <willcooke> seb128, if I get env from U8 terminal, grep for bus, and then copy that in to my SSH session, that might work?
10:02 <didrocks> willcooke: you need DBUS_SESSION_BUS_ADDRESS at least :)
10:02 <seb128> willcooke, just look to /proc/`pidof unity8`/environ
10:03 <seb128> easier to cat that, so you can select/paste
10:03 <seb128> rather than having to type it over
10:03 <willcooke> seb128, coolio, thanks
10:03 <seb128> yw
10:16 <willcooke> seb128, worked \o/
10:16 <seb128> willcooke, great!
10:18 <didrocks> weird that it wasn't working in your session though
10:18 <didrocks> (from the U8 terminal)
10:22 <Laney> seb128: nice fix!
10:23 <seb128> Laney, hey, thanks! it was "interesting" to debug
10:26 <seb128> Laney, btw did you go anywhere with the about panel/storage/qt5.4? Mirv wants to land qt5.4 early next week, we need to fix the panel to at least load, even if the disk computation is a bit off in a first time
10:27 <Laney> seb128: no sorry not yet, but could make it just use '/' or something
10:27 <seb128> Laney, right
10:28 <seb128> Laney, well, Mirv said he would have a look today, since they want to land qt and you are off work, just wanted to make sure he doesn't dup work
10:29 <Laney> oh well let me push the small bit I did
10:30 <Laney> Mirv: lp:~laney/ubuntu-system-settings/storageinfo-5.4
10:34 <seb128> Laney, thanks
10:35 <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1420404 btw for easy review karma if you want to ack it ;-)
10:35 <ubot5> Launchpad bug 1420404 in ubuntu-system-settings (Ubuntu RTM) "Name entry in desktop file not localized" [High,In progress]
10:35 <seb128> shrug
10:35 <seb128> why is CI grumpy on settings?
10:36 <seb128> seems like it fails to start or something
10:36 <didrocks> seb128: there are been a new CI Train rollout, maybe linked?
10:36 <seb128> didrocks, not sure
10:38 <Laney> seb128: I wonder if the uitk shouldn't have a fix here too
10:38 <seb128> Laney, yeah, I plan to open at least 2 bugs
10:39 <seb128> Laney, one to have the documentation mention that it sets the textdomain to that value
10:39 <seb128> Laney, and maybe one to say that is should set the domain only if it hasn't been set manually before
10:39 <seb128> (thanks didrocks for suggesting that one)
10:39 <seb128> Laney, is that what you were thinking about?
10:40 <Laney> indeed
10:40 <didrocks> yeah, you will clearly not be the only ones to be trapped by this, even if documented…
10:40 <seb128> well, to  be fair it's rather a special case
10:41 <seb128> but yeah, likely going to bite others
10:41 <seb128> you can do i18n.domain = ... from your qml
10:41 <seb128> and it's fine for the UI
10:41 <didrocks> I'm unsure that enthousiast would be happy to spend a day on something similar :)
10:42 <seb128> the fact that g_dgettext() decide on its strategy on the first call and that this calls happen between the init and the domain change is a bit special
10:42 <seb128> but yeah, we are probably not going to be the only one to use glib
10:42 <didrocks> yeah ;)
10:42 <willcooke> any quick workarounds for these wierd network manager issues?  I've already stopped ofono
10:43 <didrocks> willcooke: I didn't get it again since Brussels here btw…
10:43 <willcooke> ohh
10:43 <didrocks> last time I did restart the network manager service
10:43 <Laney> ah crap, I had a nm bug just now
10:43 <Laney> C+Ped some nmcli output to file one but I forgot and lost it :(
10:43 <willcooke> I have wired networking and wifi - and I can't get to the internet most of the time
10:43 <Laney> vivid?
10:44 <willcooke> if I unplug the ethernet it works again#
10:44 <willcooke> yeah, on my u8 vivid machine
10:44 <didrocks> ah, not the same, only wifi here
10:44 <Laney> ya, try sudo restart network-manager
10:44 <willcooke> tried that, no different
10:44 <willcooke> I'm running a ping to 8.8.8.8
10:44 <willcooke> and it'll suddenly just work for about 10 seconds, and then stops again
10:45 <willcooke> disabled wifi - looks better now
10:45 <willcooke> could be some loop on my internal network
10:46 <willcooke> but I doubt it, since everything else works
10:49 <Mirv> Laney: seb128: ah, excellent! I did http://pastebin.ubuntu.com/10202733/ as the bandaid solution to the rest of the about page if there wouldn't be a real fix
10:50 <Mirv> (in the ppa)
10:53 <Mirv> so if that branch helps it a bit further of not disabling the storage portion (even if wrong numbers), that would be better
11:41 <willcooke> mlankhorst, could we, if we wanted, interpret touch events as left-clicks in Xmir?
13:03 <willcooke> seb128, Trying to pair that kbd... "Please enter the following pin...." but no pin is shown
13:04 <seb128> willcooke, what device?
13:04 <willcooke> seb128, N7 running devel prop
13:05 <seb128> willcooke, yeah, bluez is buggy on that device
13:05 <seb128> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421598
13:05 <ubot5> Launchpad bug 1421598 in bluez (Ubuntu) "DisplayPasskey() "entered" number wrong on some devices" [Undecided,New]
13:05 <seb128> willcooke, https://code.launchpad.net/~seb128/ubuntu-system-settings/bluetooth-key-hint-workaround/+merge/249622 as a workaround
13:06 <willcooke> seb128, nice one!
13:06 <willcooke> seb128, will that land in devel proposed at some point, or do I need to *shudder* compile code
13:06 <willcooke> oh
13:06 <seb128> Mirv, k, would be better to not disable storage indeed, are you looking at a better fix?
13:06 <willcooke> it's qml
13:06 <willcooke> I can just copy it?
13:06 <seb128> right
13:06 <seb128> it's one line to change
13:07 <seb128> so yeah, you can even vi edit it
13:07 <seb128> need to set your device to rw first though
13:11 <Mirv> seb128: I'm EOD after this hangout, but maybe Laney knows what's the next step that should be done to his MP now that the button + free space reporting is possible to get back. I guess implementing/copying QML class that used to be StorageInfo? FYI, here's the current diff I have http://pastebin.ubuntu.com/10204250/
13:11 <seb128> Mirv, thanks, I guess we can look at doing better on monday
13:16 <willcooke> seb128, can you give me the path to DisplayPasskeyDialog.qml?
13:16 <willcooke> seb128, ignore
13:16 <seb128> willcooke, dpkg -S DisplayPasskeyDialog.qml
13:17 <willcooke> oh, neat trick, thanks
13:17 <seb128> yw!
13:19 <willcooke> yay! works
13:19 <willcooke> thanks seb128
13:19 <seb128> willcooke, great ;-)
13:44 <Mirv> seb128: yes, this solution at least fulfills the minimum level, and the main problem is probably thinking what's wise to do, the missing functionality itself is probably easy enough to replicate
13:44 <seb128> Mirv, right
13:46 <flexiondotorg_> I'd like some advice please.
13:46 <flexiondotorg_> I'm the Ubuntu MATE lead.
13:47 <flexiondotorg_> I've got a couple of files ubuntu-mate-settings that get installed to /etc/skel, just as other flavours have done. Such as Xubuntu.
13:47 <flexiondotorg_> Just want to get some feedback on that practice?
13:47 <desrt> flexiondotorg_: skel is evil.  stop doing that :)
13:47 <flexiondotorg_> Because I'm being asked by my sponsor to check with the desktop team.
13:48 <flexiondotorg_> desrt, Well, for I am using it for there is not other option.
13:48 <desrt> flexiondotorg_: is there not a way that you could make changes to the affected software to have the correct settings by default?
13:48 <desrt> flexiondotorg_: what are you doing with it?
13:49 <flexiondotorg_> desrt, Provide a default configuration for Tilda and qt4-config.
13:49 <flexiondotorg_> Much as Xubuntu currently do.
13:49 <desrt> because, almost certainly, it's not impacting all of the people that it ought to be, and is improperly impacting some of the people who it shouldn't be
13:49 <flexiondotorg_> Well, it is only relevant for system installs or new user additions.
13:50 <desrt> what can't qt by configured via more normal means?
13:50 <flexiondotorg_> Normal means?
13:50 <desrt> like xsettings, or so?
13:50 <desrt> ie: why are the needs of mate different here than the needs of gnome or unity?
13:53 <flexiondotorg_> Well, I guess my needs are the same as Xubuntu.
13:54 <desrt> sure... but that's not the question... in what way are they different than gnome/unity?
13:54 <flexiondotorg_> The default Qt4 look and feel doesn't fit and therefore requires a little tweak.
13:54 <desrt> it could be that xubuntu is also doing it wrong
13:54 <flexiondotorg_> desrt, Possibly. But I have tried to use the existing flavours as a guide.
13:54 <desrt> what's the tweak?  is it a new theme, basically?
13:55 <flexiondotorg_> desrt, Basicaly use GTk+ theme and Ubuntu font.
13:55 <desrt> and this isn't already the default under unity or gnome?
13:55 <desrt> maybe the fix to your problem is to get the defaults properly changed...
13:56 <desrt> anything else that you do really needs to be determined at runtime
13:56 <desrt> or at the absolute worst permissible case, via something like update-alternatives
13:56 <flexiondotorg_> So, how does Ubuntu (or rather Unity) set the Qt4 look?
13:56 <desrt> determined-by-packages-that-happened-to-be-installed-when-the-user's-homedir-was-created is just bonkers
13:57 <desrt> flexiondotorg_: i'd guess xsettings
13:57 <flexiondotorg_> desrt, Which package?
13:57 <desrt> {gnome,unity}-settings-daemon
13:57 <flexiondotorg_> If I have a reference I can follow.
13:57 <desrt> so probably mate-settings-daemon to you?
13:57 <flexiondotorg_> I'll take a peek.
13:57 <flexiondotorg_> desrt, Indeed.
13:57 <desrt> i'm not sure if this is true or not...
13:58 <desrt> i'm wildly guessing at this point
13:58 * desrt is not a qt guy
13:58 <desrt> i just know that it's surely possible to do a better approach than your skel thing, and the person who flagged it as suspicious was absolutely right to have done so
13:59 <desrt> even a dpkg-diversion on the relevant system config file would be a better option... (but still a bad one)
14:01 <flexiondotorg_> desrt, There is not system level configuration AKAIK.
14:02 <desrt> there always is :)
14:02 <desrt> sometimes they just put it inside the .c files....
14:02 <flexiondotorg_> desrt, Which I can't influence.
14:03 <desrt> but i'd be surprised to hear about something that could be changed via a dotfile and not by a similar file in /etc
14:03 <desrt> flexiondotorg_: why not?
14:03 <desrt> this is #ubuntu-desktop
14:03 <desrt> this is where changes like this happen all the time...
14:04 <flexiondotorg_> I'm trying to see if Ubuntu have already changed the Qt4 config.
14:30 <flexiondotorg_> desrt, While I continue looking for if/how Qt4 is being tweak by Unity/Gnome could you take a peek at the following please?
14:30 <flexiondotorg_> https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1351890
14:30 <ubot5> Launchpad bug 1351890 in mate-control-center (Ubuntu) "Changing external screen resolution with dual monitors" [Medium,Confirmed]
14:30 <flexiondotorg_> See the patch we've prepare in #9
14:30 <flexiondotorg_> How can we get this merged and released?
14:32 <desrt> flexiondotorg_: you're talking to the wrong guy, unfortunately
14:32 <flexiondotorg_> desrt, Do you know who I should approach?
14:33 <desrt> oh.  this is a gtk patch?
14:33 <desrt> i'd talk to Laney about that
14:33 <seb128> desrt, gtk patch yes, from 2010, which apparently didn't get applied to gtk2
14:33 <seb128> desrt, would be nice to have applied upstream as well?
14:33 * desrt thought it was a mate issue
14:33 <desrt> seb128: i doubt anyone would get very much objection from the gtk maintainers about that
14:34 <seb128> desrt, https://bugzilla.gnome.org/show_bug.cgi?id=635380 to apply to gtk2 apparently
14:34 <ubot5> Gnome bug 635380 in Backend: X11 "gdk_event_apply_filters is unsafe against changes in filter list" [Normal,Resolved: fixed]
14:34 <seb128> flexiondotorg_, I guess you can ask on the upstream bug if they can apply to gtk2, or maybe open a new bug about it on  bugzilla
14:34 <desrt> er... https://git.gnome.org/browse/gtk%2B/commit/?id=323df2b2800383832ed3c2e43626f2c6821c33ec ?
14:35 <desrt> oh.  you mean it didn't get backported
14:35 <flexiondotorg_> desrt, Correct.
14:37 <desrt> non-trivial backport there...
14:37 <flexiondotorg_> The patch is the TK2 backport.
14:37 <desrt> considering it modifies a file that doesn't even exist in gtk2
14:39 <desrt> you want to ping in #gtk+ on irc.gnome.org
14:39 <desrt> they'll almost certainly be very happy to accept that patch
14:40 <desrt> not really sure who monsta-mint is ... :)
14:40 <flexiondotorg_> desrt, monsta is a MATE dev.
14:40 <flexiondotorg_> desrt, Like myself.
14:45 <mlankhorst> willcooke: maybe
14:45 <mlankhorst> why? :P
14:50 <pitti> didrocks: lovely!
14:50 <pitti> didrocks: I get nice fsck progress (with the dummy) now *hug*
14:50 <pitti> didrocks: but neither in qemu nor on my real laptop Control-C works -- does that part need a plymouth fix?
14:52 <pitti> well, something for the next upload
15:03 <seb128> didrocks, congrats on getting some of that landing ;-)
15:31 <willcooke> mlankhorst, just playing with it on my touch screen laptop - I think it'd be a nice tweak if it's something that's easy to do
15:39 <didrocks> pitti: excellent! Control-C on the real laptop should work, the thing is that you have to press for ~1s
15:39 <didrocks> pitti: that was less noticeable with raw C
15:39 <didrocks> seb128: *finally*, phew! :)
15:39 <pitti> didrocks: ah! I suppose I didn't do that
15:39 <seb128> didrocks, :-)
15:39 * didrocks back from cycling
15:40 <seb128> didrocks, ready for the tour de france? ;-)
15:40 <didrocks> seb128: ahah, seeing how many cramps I have the day after cycling for 30kms… I would say… no :p
15:40 <didrocks> and 15kms/h is like 4 times less than tour de france ;)
15:40 <seb128> didrocks, Laney, btw I opened https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421672 and https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421661
15:40 <ubot5> Launchpad bug 1421672 in ubuntu-ui-toolkit (Ubuntu) "Overwrite the gettext to MainView.applicationName if already set" [Undecided,New]
15:40 <ubot5> Launchpad bug 1421661 in ubuntu-ui-toolkit (Ubuntu) "The applicationName documentation doesn't state that it define the gettext domain" [Undecided,New]
15:41 <didrocks> seb128: excellent! let's see how it goes (keep us posted, I'm interested ;))
15:41 <seb128> just as a fyi
15:41 <seb128> didrocks, sure
16:15 <koko_> beurk beurk
16:22 <attente_> switching VTs seems to kill the audio for me
16:25 <ogra_> attente_, i thought thats expected since you lose your polkit seat
16:36 <attente_> ogra_: has it always been like that? i seem to remember it being able to recover as soon as i log into the vt
16:36 <ogra_> i was complainin aboout it years ago ... that was pitti's explanation i got :)
16:37 <ogra_> not sure if that behavior had changed later and is now broken again
16:37 <ogra_> it could well be
16:37 <willcooke> attente_, desrt trying to run gedit on a device:  http://paste.ubuntu.com/10206929/
16:38 <willcooke> it seems to just crashg
16:38 <willcooke> anything I can do, is it that just how it is atm
16:39 <attente_> willcooke: checking
16:46 <seb128> willcooke, what is the issue exactly? gedit is sort of a special case, it doesn't run on my inspiron, it tries to open another surface and mir allows one surface by app only at the moment
16:46 <seb128> could be the same issue
16:46 <seb128> you can try eog instead, that should work
16:46 <willcooke> seb128, heh - works fine on my Inspiron :)  This is on N7
16:47 <attente_> i'm not sure. it's running on my thinkpad, but i don't have a device to test it on
16:48 <pitti> ogra_, attente_: as soon as you log into the VT, you should get your audio back, no?
16:48 <attente_> pitti: that's what i thought, but it doesn't seem to do that for me now
16:49 <attente_> seb128: the log output seems to only create one window
16:49 <seb128> k
16:50 <attente_> "Could not load Gedit repository ...", i don't have this line in my output
16:51 <willcooke> eog seems same
16:52 <willcooke> http://paste.ubuntu.com/10207102/
16:52 <willcooke> meh - dont worry about it for now
16:59 <seb128> ok, need to go, going to a spectacle tonight, have a nice w.e everyone
16:59 <willcooke> cya seb128
17:00 * didrocks goes as well, see you guys!
17:00 <didrocks> have a nice week-end :)
17:20 <attente_> willcooke: is it possibly because it's loading both the android and mesa drivers?
17:20 <willcooke> attente_, ah, ok - I'll pick this up with mlankhorst on Monday and see where we get
17:20 <willcooke> thanks attente_
17:21 <willcooke> oh
17:21 <willcooke> wait
17:21 <willcooke> no, it's not an Xmir thing - duur
17:21 <attente_> willcooke: can you try removing the mir-client-platform-mesa package and see what happens?
17:25 <willcooke> attente_, sure - trying now
17:28 <willcooke> attente_, sabdfl
17:28 <willcooke> oops sorry sabdfl - ignore
17:28 <willcooke> attente_, same - you want a pastebin of the log?
17:28 <attente_> willcooke: it's ok, should be the same without that line i think
17:29 <sabdfl> willcooke, ack :)
18:12 * willcooke -> EOW
23:42 <Noskcaj> Is anyone working on the evolution 1.12.11 update?
01:07 <Noskcaj> Does anyone have time to review/sponsor a merge of gnome-menus?
06:12 <pitti> Good morning
06:14 <larsu> morning pitti! Wie geht's?
06:15 <pitti> larsu: prima, danke! und Dir?
06:15 <larsu> auch. Nur müde
06:15 <pitti> larsu: war zur Abwechslung mal ein Wochenende zuhause, sehr entspannt
06:15 <larsu> ha schön!
06:15 <pitti> larsu: nicht jeder Hacker steht um 7 auf...
06:16 <larsu> pitti: stimmt, aber manche anscheinend schon ;)
07:45 <seb128> good morning desktopers
08:02 <mlankhorst> morning
08:07 <seb128> hey mlankhorst
08:09 <mlankhorst> what's up?
08:12 <seb128> it's monday!
08:13 <mlankhorst> indeed it is!
08:36 <seb128> xnox, pitti, hey, what's the status of https://code.launchpad.net/~xnox/system-service/python3/+merge/192805 , seems like it was mostly approved and the review comment got addressed since? should that land? (and what about https://code.launchpad.net/~xnox/system-service/pac-support/+merge/243904 then?)
08:36 <pitti> bonjour seb128, hey mlankhorst
08:37 <seb128> pitti, hey, wie gehts? had a good w.e?
08:38 <pitti> seb128: yeah, at home for a change -- very relaxing! :-) and your's? enjoyed valentine's day?
08:39 <pitti> seb128: py3 merge> ah, I didn't see the followup comment
08:39 <seb128> pitti, indeed I did! we had a nice w.e, went to saw a choir on friday, to the theatre on saturday and relaxed/enjoyed the sunny weather yesterday
08:40 <seb128> to see*
08:41 <Noskcaj> thanks for the sponsoring seb128
08:41 <seb128> Noskcaj, hey, yw!
08:42 <Noskcaj> Is there any reason we don't have yelp 3.14 yet? Did it break something?
08:43 <happyaron> can someone sponsor this? https://code.launchpad.net/~nobuto/ubuntu/vivid/unzip/fallback-encoding/+merge/249644
08:43 <happyaron> or should I subscribe sponsors team?
08:48 <seb128> happyaron, it's already in the sponsoring queue
08:49 <seb128> happyaron, I'm unsure about the change, why isn't that done upstream and/or in Debian?
08:50 <happyaron> seb128: upstream want's universe solution instead of locale hack, for Debian I'd like to wait until freeze is over
08:50 <seb128> why?
08:51 <happyaron> for which?
08:51 <seb128> things can be forwarded to the BTS/discussed during the freeze
08:51 <seb128> Debian
08:51 <happyaron> yes, but not done yet
08:51 <seb128> right, it should ;-)
08:51 <seb128> comment on the mp saying we at least need a bug report explaining the issue
08:51 <seb128> so we have references on why we carry the change
08:52 <happyaron> ok
09:03 <willcooke> o/
09:05 <Laney> morning!
09:06 <happyaron> seb128: bug 1422290
09:06 <ubot5> bug 1422290 in unzip (Ubuntu) "Default charsets handling for Windows archives in CJKV+th locale" [Medium,Triaged] https://launchpad.net/bugs/1422290
09:06 <happyaron> morning, :)
09:07 <seb128> happyaron, thanks
09:07 <seb128> hey willcooke, Laney, how is u.k this morning?
09:07 <Laney> very wet
09:07 <seb128> of course ;-)
09:09 <Laney> seb128: good weekend?
09:13 <seb128> excellent, thanks!
09:13 <willcooke> :)
09:13 <seb128> went to see a choir and to the theatre, enjoyed a sunny sunday as well
09:17 <seb128> Laney, what about you? good w.e?
09:20 <Laney> yep, had friends over for dinner on saturday & went climbing / played games yesterday
09:20 <Laney> relaxing!
09:27 <seb128> nice
09:27 <seb128> Laney, pitti, can one of you sponsor http://paste.ubuntu.com/10253033/ for me?
09:28 <seb128> I never receive an update on the Debian rt to replace my key, I wonder if they did it without getting back to me or if that's still waiting?
09:29 <pitti> seb128: can do, yes
09:29 <seb128> pitti, danke
09:29 <Laney> ah, faster than me
09:29 <pitti> seb128: hm, when I got my key replaced I did get a notification
09:30 <Laney> I'm being killed by fstrim atm
09:31 <pitti> seb128: ah, svn head has another change, I'll merge
09:31 <seb128> ups
09:31 <seb128> pitti, sorry about that
09:31 <pitti> no worries
09:31 <seb128> pitti, my most recent email on the rt to change key was gunnar asking if you could send again your email but inlined, did you do that?
09:32 <seb128> inline-signed rather
09:32 <pitti> yes, I thought I did
09:32 <seb128> hum, k
09:32 <pitti> seb128: I take the liberty to drop the wrong commas from the manpage
09:32 <seb128> pitti, wfm :-)
09:33 <pitti> seb128: given Debian's freeze, is that something you want to see in unstable now, i. e. do you want to send an unblock request?
09:33 <pitti> seb128: or sohuld I upload it to exp, or only an svn snapshot to vivid?
09:35 <seb128> pitti, no need to be in unstable no, it's just in the ubuntu sponsoring queue and I wanted to get it out of it
09:35 <seb128> so exp sync or I can upload to vivid if you want
09:35 <seb128> then we can sync on the next debian upload
09:36 <pitti> seb128: I'd upload it as 0.7.6-2svn1
09:36 <pitti> seb128: svn commit running for 2 mins now (alioth is clogged..)
09:36 <seb128> pitti, feel free, or let me know if you want me to do that
09:39 <pitti> seb128: I'll do it, after svn commit ever finishes..
09:40 <seb128> pitti, danke, I nudged on the debian rt to know if I need to do anything for the key replacement still
09:43 <Laney> pitti: let me know if/when you have time to debug suspend - I've tried pm-suspend 20 times or so without failure now so seems this method is working properly
09:47 <pitti> Laney: ah, interesting; do you have anything in /var/cache/pm-utils?
09:47 <pitti> like a last_known_working.quirkdb
09:50 <Laney> pitti: nothing there, empty directory
09:50 <Laney> I have a pm-suspend.log if that's interesting to you?
09:51 <pitti> Laney: possibly; but I suppose one needs to enable debugging for it to actually say which quirks it does
09:51 <Laney> is PM_DEBUG=true pm-suspend enough?
09:51 <pitti> Laney: could be (I don't remember any more, sorry)
09:52 <Laney> nod, let's see
09:52 <pitti> /usr/share/doc/pm-utils/README.debugging:  PM_DEBUG="true" to have the script log each action as it performs it.
09:52 <pitti> sounds good :)
09:52 <Laney> one second
09:52 <pitti> Laney: so you just did "sudo pm-suspend" 20 times?
09:53 <pitti> Laney: i. e. without all the indicator/desktop integration/screen lock/etc. overhead?
09:58 <Laney> pitti: indeed; I think those call suspend via logind now?
09:58 <Laney> http://paste.ubuntu.com/10253345/ <- don't see any quirks there
09:59 <pitti> Laney: right; could you do the same loop with just "echo mem | sudo tee /sys/power/state"?
10:00 <Laney> ack
10:00 <Laney> is this poking the kernel to suspend directly?
10:04 <pitti> Laney: yes
10:04 <pitti> Laney: that's essentially what pm-utils and logind do
10:04 <pitti> but without the desktop overhead
10:04 <pitti> Laney: I'm interested in whether any of the other pm-utils hooks make a difference here, as it's not the quirks
10:04 <Laney> pitti: ok, 20 times it worked
10:04 <pitti> seb128: libnotify uploaded
10:04 <seb128> pitti, danke!
10:05 <flexiondotorg_> Morning
10:05 <flexiondotorg_> I noticed that gsettings is misbehaving, to some extent in 15.04.
10:06 <flexiondotorg_> This is confirmed by the MATE maintainers in Fedora rawhide also.
10:06 <flexiondotorg_> rawhide is glib2 2.43.4 and vivid is glib2 2.43.3
10:07 <flexiondotorg_> Editing some gsettings key/value pairs in dconf-editor doesn't make the change immediately. Requires a log in/out for changes to be active.
10:08 <flexiondotorg_> In MATE, some control center applets don't make a change until a log in/out. Such as Appearance and Sound themes, where changes are not applied directly.
10:09 <seb128> flexiondotorg_, thanks, that's likely buggy code impacted by a glib change
10:09 <flexiondotorg_> seb128, One sec...
10:10 <seb128> flexiondotorg_, https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
10:10 <flexiondotorg_> seb128, I thought this commit looked "interesting" - https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
10:10 <seb128> indeed
10:10 <flexiondotorg_> 😁
10:10 <flexiondotorg_> Yes. I was reading the commit log last night.
10:10 <seb128> flexiondotorg_, typically your fix looks like https://git.gnome.org/browse/nautilus/commit/?id=c84f4e0039353e3846afda132a53d96fcadc0715
10:10 <seb128> you need to connect first and then read the value
10:11 <seb128> some code does it the other way around
10:11 <flexiondotorg_> seb128, So, this is not a regression is glib2?
10:11 <seb128> no
10:12 <flexiondotorg_> seb128, This is a change to enforce the intended use?
10:12 <seb128> it unfortunately making code that seemed to work stop working though
10:12 <flexiondotorg_> seb128, Thanks. Useful feedback.
10:12 <seb128> but the code was wrong before, it just happened to work
10:12 <seb128> yw
10:12 <flexiondotorg_> I'll progress this upstream.
10:12 <flexiondotorg_> MATE upstream that is.
10:12 <seb128> the goal was not to enforce the intended use just for the sake of doing that
10:13 <seb128> but rather to fix a performance issue, explained in the glib commit you pointed
10:13 <seb128> the side effect is that it does less work than before and make incorrect code stop working
10:15 <seb128> pitti, debian rt guys said you didn't send the inline-signed email, fwded you their reply
10:15 <seb128> in fact replying and Ccing you if you prefer?
10:15 <seb128> so maybe you can resend it, in case it got lost?
10:18 <pitti> seb128: ack
10:20 <pitti> seb128: sent again (gosh, complicated!)
10:23 <seb128> pitti, danke!
10:29 <marga> xnox, your latest gnome-keyring upload is giving me pain again.
10:30 <marga> xnox, do I need to change the upstart override that I had created before? (/etc/xdg/gnome-keyring.override containing manual)
10:30 <xnox> marga: go on.
10:31 <xnox> marga: yes.
10:31 <marga> xnox,  how do I stop gnome-keyring from getting the ssh sock?
10:31 <xnox> marga: instructions in the bug report. To kill gnome-keyring ssh agent, you can - GUI Open Startup Applications untick gnome-keyring-ssh
10:32 <marga> heh, I want this globally, GUI is not a good solution...
10:32 <xnox> marga: or use any of the xdg paths to override gnome-keyring-ssh (like in 12.04 and before)
10:32 <xnox> which are in /etc
10:32 <xnox> marga: or the name of the ovveride is now gnome-keyring-ssh.override
10:32 <xnox> (upstart jobs')
10:32 <marga> Ah
10:33 <marga> So, instead of /etc/xdg/upstart/gnome-keyring.override containing manual, it should be /etc/xdg/upstart/gnome-keyring-ssh.override containing manual?
10:33 <xnox> marga: you probably want to override gnome-keyring-gpg agent as well. Then one can use GPG subkeys on e.g. yubikey u2f neo ;-)
10:33 <xnox> marga: yes.
10:33 <marga> I only care about ssh
10:33 <marga> Ok, thanks.
10:35 <xnox> marga: instead of upstartish override, the desktopish override is supported as well now. `find /usr/share -name gnome-keyring-ssh.desktop`, cp that to /etc/xdg/autostart/gnome-keyring-ssh.desktop, echo X-GNOME-Autostart-enabled=false >> /etc/xdg/autostart/gnome-keyring-ssh.desktop .....
10:36 <xnox> marga: that would be very forward looking, e.g. if we switch to systemd for user sessions in 16.04 the xdg/autostart override method will persist.
10:36 <marga> ok
10:36 <marga> I'll look into that then, thanks
10:37 <marga> In the past, we used to actually remove that file from /etc/xdg/autostart
10:37 <xnox> marga: that's the "system-wide" way to disable xdg-autostart files (and is the same action that startup applications thing does, but on user-level, into ~/.config/autostart)
10:38 <xnox> marga: good point.
10:39 <xnox> marga: in the upstart job, i didn't check for presence of the /etc/xdg/autostart/gnome-keyring-ssh.desktop, but rather for the "X-GNOME-Autostart-enabled=false" inside it.
10:40 <marga> Right, I understand but it's a bit cumbersome that this keeps changing...
10:40 <xnox> marga: another sru, but now to be compatible with good old ways to kill gnome-keyring-ssh?
10:40 <marga> Anyway, I'll fix it, it's not such a big deal.
10:40 <xnox> such that removal of /etc/xdg/autostart/gnome-keyring-ssh.desktop works once again ?! =)))))
10:40 <xnox> marga: if only you would have told me that months ago =)
10:40 <marga> heh :)
10:41 <marga> You think it will work like that for systemd?
10:41 <marga> Instead of removing files from /etc/xdg/autostart, we will modify them to say Autostart-enabled=false?
10:41 <marga> (I have no idea how systemd works :)
10:42 <xnox> yes. X-GNOME-Autostart-enabled=false is the best one - it will work for systemd, upstart, gnome-desktop, and all the other alternatives (e.g. forked mints, cinnamons, etc)
10:42 <marga> ok, thanks again.
10:43 <xnox> marga: systemd --user is not that capable at the moment, the plan will be similar to how systemd support init.d scripts. There will be a binary that will parse .desktop files in autostart paths, and generate systemd units to run.
10:43 <xnox> there is code on github to do that already, which was part of demos that my current manager did back in the moblin/meego days
11:54 <Laney> pitti: suspended 20 times using the logind dbus call...
11:54 <Laney> ...maybe it's fixed
11:54 <pitti> Laney: hm, my gut feeling is rather that the bits around it (screen saver, etc.) change this
11:55 <pitti> Laney: unless it was fixed in the kernel itself; I kinda hoped it would turn up with the mem > /sys/power/state test
11:55 <larsu> pitti: still not seeing any entries in the journal unless I'm root (or in the systemd-journal group). Is there a bug tracking tha issue?
11:55 <larsu> *that
11:55 <Laney> last thing is to try with an actual lid close
11:56 <pitti> larsu: debian bug 771980
11:56 <ubot5> Debian bug 771980 in systemd "systemd: /run/log/journal is not readable by the adm group" [Minor,Open] http://bugs.debian.org/771980
11:56 <larsu> pitti: thanks1
11:56 <pitti> larsu: it's fixed in upstream master (i. e. 219), but as that probably won't get released this week, I'll add a little hack to it (easier than backporting the large patches for generic ACL support in tmpfiles)
11:57 <larsu> pitti: it's not urgent. I just wanted to know the status. I'm fine with adding myself to systemd-journal for now
12:00 <Laney> hmm
12:00 <Laney> now I'm in some differently borked state where lid suspend doesn't suspend at all (screen stays on)
12:01 <Laney> ...and after I say that, it works again /o\
12:06 <pitti> some inhibitor? (systemd-inhibit)
12:07 <Laney> Just looks like normal stuff
12:07 <Laney> maybe there's a timeout or so preventing you suspending again too fast
12:08 <Laney> or one of these inhibitors does that
12:08 <Laney> anyway I've lid closed 15 times now without error
12:08 <davmor2> Laney: that or it just hates you ;)
12:08 <Laney> of course the system knows I'm trying to reproduce a bug and I'm not putting the laptop in my bag for a few hours, so it would work. :)
12:09 <Laney> davmor2: I feel like a QA engineer atm ;-)
12:10 <davmor2> Laney: Welcome to our world of machines hating you :)
12:16 <mitya57> #endmeeting
12:17 * Laney peers at mitya57
12:18 <Laney> are we still meeting?
12:18 <mitya57> I just thought that having "Desktop Weekly Meeting 2015-02-10 | Current topic: endmeeting" in topic is not sane
12:18 <Laney> haha
12:18 <Laney> willcooke: care to #endmeeting ?
12:20 <willcooke> #endmeeting