[02:15] <furkan> does anybody know why installing the xserver-xorg-lts-utopic package in 14.04 removes the ubuntu-desktop package? is it no longer needed?
[02:46] <sarnold> furkan: no idea, but ubuntu-desktop is (mostly? entirely?) a metapackage; once you've got the other packages installed, it should be fine to remove it
[02:47] <sarnold> furkan: maybe when you upgrade to a newer release it'll be awkward or won't compute as convenient an upgrade if it is missing.. if a future upgrade path looks silly, recall this conversation :)
[03:00] <furkan> sarnold: haha thanks, based on historical data, i will probably go through an inevitable period of frustration, followed by an "ah" moment when i do recall this conversation :)
[03:01] <sarnold> furkan: that's the one! :)
[04:26] <tjaalton> furkan: probably some deps are still in transition and you're not supposed to try that yet
[04:58] <furkan> tjaalton: yeah i think that's what it is - some packages (like the 32-bit libraries) are missing
[04:58] <furkan> seems like the xserver-xorg-lts-utopic just appeared today
[06:07] <darkxst> larsu, seems things like gtk:bg[NORMAL] don't work anymore in metacity themes
[06:08] <darkxst> maybe affect ubuntu themes also, but they use lots of hardcoded values so probably not immediately obvious (but I do get black window borders for eg on Ambiance)
[06:32] <pitti> Good morning
[06:51] <happyaron> seb128 morning!
[07:22] <seb128> good morning desktopers
[07:22] <seb128> hey happyaron
[07:22] <happyaron> :)
[07:23] <didrocks> hey seb128, happyaron!
[07:23] <seb128> re didrocks
[07:24] <happyaron> seb128: need your help on two things
[07:25] <happyaron> 1) binNEW fcitx-qt5
[07:25] <happyaron> 2) subscribe desktop-bugs to packages in bug 1356222
[07:26] <seb128> happyaron, I can look at 1
[07:26] <seb128> happyaron, for 2, don't you have an im team/group you can subscribe?
[07:27] <happyaron> yes I do have, but I realized didrocks asked for desktop-bugs... not sure if that's a requirement
[07:27] <happyaron> didrocks: ^^^^^^
[07:27] <didrocks> happyaron: as long as there is at least one team subscribed to all packages, that's fine
[07:27] <seb128> no
[07:27] <happyaron> ok
[07:27] <happyaron> then no need
[07:27] <seb128> the requirement is that somebody subscribes/look after the bugs
[07:27] <didrocks> a team your are in, of course :)
[07:27] <happyaron> :)
[07:35] <pitti> bonjour seb128 et didrocks, comment allez-vous ?
[07:35] <pitti> hey happyaron
[07:36] <happyaron> hey pitti
[07:36] <happyaron> :)
[07:36] <didrocks> pitti: ça va, dealing with politics, et toi ? :)
[07:36] <pitti> didrocks: dealing with jenkins :)
[07:37] <seb128> hey pitti, wie gehts?
[07:37] <pitti> seb128: gut, danke!
[07:37] <seb128> didrocks, are you getting elected? ;-)
[07:37]  * pitti holds his "didrocks for president" cardboard sign
[07:38] <didrocks> let me answer and post the reference :)
[07:38] <pitti> err -- "Notre président: didrocks !"
[07:42] <didrocks> seb128: pitti: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1419695
[07:42] <didrocks> seb128: pitti: context is "pip install by default try to install in /usr/local", and of course, shows a traceback because it's not protected.
[07:43] <didrocks> nice that it opened the discussion back after stalling for month upstream :)
[07:52] <seb128> I see
[07:52] <seb128> good luck with that!
[07:52] <didrocks> seb128: well, it's simple, it's patched
[07:52] <didrocks> so either they come with an upstream solution by then
[07:52] <didrocks> and I change for that
[07:52] <didrocks> either it stands :p
[07:53] <didrocks> seems it's the only way to get them moving on that topic
[08:01] <darkxst> hey seb128, didrocks
[08:01] <didrocks> evening darkxst
[08:02] <darkxst> didrocks, been a hot day here;( but cooling now
[08:02] <darkxst> didrocks, can you look over bug 1416617?
[08:02] <didrocks> darkxst: just curious, when did you subscribe the Mir team to it? (mterry is looking at the incoming queue regularly)
[08:03] <didrocks> darkxst: I'll have a look anyway today, I have some spare cycles
[08:03] <darkxst> didrocks, I would think jackson did that when he filed it so 31/1
[08:04] <didrocks> interesting… Anyway, will have a look!
[08:04] <darkxst> didrocks, or not, seems he did it today
[08:04] <seb128> hey darkxst
[08:04] <didrocks> darkxst: ah, that would explain :)
[08:05] <darkxst> seb128, metacity themes just seem broken now, looks to be affecting your themes and mitya's also
[08:05] <didrocks> seb128: are we going to ship the new totem this cycle, do you know?
[08:05] <seb128> darkxst, now being with the new gtk?
[08:05] <didrocks> (regarding this appstream-glib bug)
[08:06] <didrocks> to know who should take maintainer ownership
[08:06] <darkxst> yes with 3.15.4,  the things like 'gtk:bg[NORMAL] ' don't seemed to get substitued
[08:06] <seb128> didrocks, not decided yet afaik, Laney and larsu were discussing it
[08:06] <seb128> new totem is quite a different application
[08:07] <seb128> it's also more integrated with grilo, tracker, etc
[08:07] <seb128> not a simple player anymore
[08:07] <didrocks> well, seeing that it requires appstream-glib, I would have bet so!
[08:07] <darkxst> seb128, its a lot more subtle with ubuntu themes since many of the colours are hardcoded there
[08:07] <darkxst> didrocks, appsteam-glib is nothing to do with the UI
[08:08] <didrocks> darkxst: well, it's the "store" integration I guess
[08:08] <didrocks> darkxst: so codecs and so on
[08:08] <darkxst> didrocks, yes its related to the  metadata
[08:08] <didrocks> darkxst: I just mean, if the ubuntu desktop team isn't going to take the new totam and depends on appstream-glib, I will ask your team to take maintainer ownership until then
[08:09] <darkxst> didrocks, all GNOME apps will likely need appstream-glib next cycle
[08:09] <didrocks> darkxst: yeah, but we are talking about this cycle though :)
[08:09] <didrocks> those things can evolve over time
[08:10] <darkxst> seb128, why do you keep on about grilo and tracker? they are non issues
[08:11] <seb128> darkxst, they are new depends and extra bloating to our installion
[08:11] <mlankhorst> morning
[08:11] <seb128> hey mlankhorst
[08:11] <seb128> darkxst, they also mean more code to have in main/support
[08:12] <larsu> seb128: discussing?
[08:12] <larsu> morning!
[08:12] <seb128> hey larsu
[08:12] <didrocks> morning larsu, mlankhorst!
[08:12] <darkxst> seb128, its just a half dozen little plugins once we split grilo-plugins
[08:13] <darkxst> and tracker libs are already there, but wont run on !GNOME
[08:13] <seb128> darkxst, "just half a dozen"
[08:14] <didrocks> override_dh_auto_test:
[08:14] <didrocks>     # Don't run tests, they are always failing at time (20140924)
[08:14] <didrocks> nice!
[08:15] <seb128> larsu, I didn't follow, Laney mentioned that new totem was quite different and needed consideration/looking at the user experience
[08:15] <darkxst> didrocks, most people don't know how to run tests (plus often upstreams do crappy stuff), though I haven't looked at these
[08:15] <seb128> larsu, I though you were talking with him about it, sorry for misremembering
[08:15] <larsu> seb128: ah right - we never quite finished that discussion
[08:15] <larsu> seb128: maybe we should :)
[08:15] <seb128> yeah
[08:15]  * larsu is about to go to the airport though
[08:16] <didrocks> seb128: btw, funny to see appstream-glib depending on libqt4-dev :)
[08:16] <seb128> larsu, safe flight!
[08:16] <darkxst> larsu, seb128 all this is news to me, I originally suggested forking the source for totem3 we could use
[08:16] <seb128> didrocks, what for?
[08:16] <didrocks> seb128: dunno, looking at debian/control :)
[08:16] <didrocks>                libglib2.0-dev (>= 2.40),
[08:16] <didrocks>                libgtk-3-dev,
[08:17] <didrocks>                libqt4-dev,
[08:17]  * didrocks will look at the code later
[08:17] <darkxst> but instead wrote patches to bring back menus, fix grilo, and titlebars for you guys
[08:17] <larsu> seb128: thanks!
[08:17] <larsu> darkxst: news
[08:18] <larsu> darkxst: news? nothing has been decided yet
[08:18] <larsu> darkxst: forking seems like a lot of work
[08:18] <darkxst> larsu, seb128  said he was happy enough with the UI at the time I guess
[08:18] <didrocks> seb128: seems to be just some packaging cruft, doesn't seem like a hard depend
[08:18]  * didrocks is going to ask on the MIR bug
[08:19] <darkxst> didrocks, appsteam-glib is meant to be distro/DE agnostic
[08:20] <didrocks> darkxst: right, but I mean, nothing I can see in the code is using qt4
[08:20] <darkxst> didrocks, oh I see
[08:21] <seb128> darkxst, well, ignore what I said, Laney is the one deciding for that update and I didn't pay much attention to it, so maybe I understood wrongly what he plans to do
[08:23] <seb128> darkxst, the UI looks fine to me, what you said yesterday (that you might be able to play video only by passing them as argument) seems like more worrying
[08:23] <seb128> but again I didn't try it
[08:23] <seb128> so let's wait for testing to see how it works exactly
[08:24] <seb128> happyaron, NEWed
[08:24] <happyaron> thanks
[08:26] <darkxst> seb128, that is only without grilo-plugins
[08:26] <darkxst> and we already have agreed to split those up into the essential ones only, and DM seems ok with that also
[08:27] <seb128> darkxst, k, well as said, I need to test the experience, I'm just waiting for the plugins to be split so I can test what we want to ship (and not the experience when installing things we are going to split out)
[08:28] <darkxst> seb128, you could test it now, most of the stuff that will be split out is remote plugins
[08:28] <darkxst> except I guess youtube
[08:29] <darkxst> The recent tab doesn't use any remote plugins unless you select one and search
[08:29] <darkxst> the channels tab is obiously populated mostly by the remote plugins
[08:30] <willcooke> morning
[08:31] <seb128> hey willcooke
[08:32] <willcooke> larsu, didrocks seb128 -> Spoke to robert_ancell, he's happy to hand over bluez5.  He was only working on a small part of it, rather than bringing the whole thing in
[08:34] <seb128> willcooke, k, was he still working on it?
[08:35] <didrocks> thanks for clearing that up
[08:36] <didrocks> darkxst: MIR commented: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1416617
[08:37] <willcooke> seb128, nope - he'd pretty much stopped
[08:38] <darkxst> didrocks, thanks I'll follow up on tests, and get Noskcaj to look into copyright/qt4 deps
[08:39] <seb128> willcooke, good, the handover makes sense then :-)
[08:39] <willcooke> :)
[08:39] <didrocks> darkxst: yw!
[08:48] <willcooke> Laney, the plan for Gtk 3.16 in 15.04.  Is the idea that those issues you mentioned, plus the others raised would be fixed before release, or that we'd live with them?
[08:51] <willcooke> larsu, Gtk overlay scroll bars - can they be themed as well?
[09:03] <darkxst>  didrocks looks like --as-needed is causing the test failures (so not actual test failures), I will get it sorted upstream
[09:03] <darkxst> (^ appstream-glib tests)
[09:03] <didrocks> thanks darkxst :)
[09:04] <Laney> yo
[09:05] <darkxst> willcooke, I'm going to propose blocking on my multiple monitor issues
[09:06] <darkxst> willcooke, theme issues should be fixable
[09:06] <Laney> willcooke: fix most of them, but there are more issues so maybe we shouldn't do it, let's talk in the meeting
[09:07] <darkxst> Laney, has more than one monitor right?
[09:07] <seb128> hey Laney, how are you?
[09:07] <willcooke> kk, thanks darkxst Laney.  From my position of little knowledge, it doesn't seem like the best plan right now :)
[09:07] <darkxst> can you boot gdm with gtk 3.15?
[09:08] <Laney> darkxst: ya
[09:08] <Laney> umm, dunno, lemme see
[09:10]  * Laney haz ubuntu-gnome plymouth theme
[09:11] <darkxst> Laney, isnt it nice ;)
[09:11] <Laney> it is
[09:11] <Laney> who made it?
[09:12] <darkxst> Laney, me, though the artwork guy did the logos
[09:13] <darkxst> I just wrote a bit of code to fit his design
[09:13] <Laney> gdm worked for me
[09:14] <seb128> hum, GNOME bugzilla lost its identity
[09:14] <seb128> looks like the fdo one now
[09:14] <seb128> that sucks
[09:14] <darkxst> Laney, maybe a NVIDIA blob issue then, but 3.14 doesnt hava a problem with same drivers
[09:14]  * Laney forgot how it looked before clearly
[09:15] <ogra_> are you sure its not your firefox ?
[09:15] <Laney> because I didn't notice :P
[09:15] <darkxst> Laney, antique like
[09:15] <darkxst> (bugzilla)
[09:15] <Laney> darkxst: maybe, I think I'm using nouveau
[09:15] <Laney> try that?
[09:15] <darkxst> Laney, I have a maxwell GPU ;(
[09:15] <Laney> dunno what that means LA LA LA
[09:15] <darkxst> a little too new for nouveau support
[09:15] <seb128> darkxst, you find the new look better?
[09:15] <seb128> it lost useful things though
[09:16] <seb128> like canveat replies
[09:16] <darkxst> seb128, have not really played much with it, since it came back up
[09:17] <Laney> so where's the latest totem test package?
[09:17] <Laney> let's have a look at it
[09:17] <darkxst> Laney, gnome3 ppa
[09:17] <Laney> ok
[09:18] <Laney> I think my system is trackered
[09:18] <darkxst> you can just pull binaries down from there, no transitions or what to bother with
[09:18]  * Laney should kill that first
[09:18] <darkxst> Laney, if you intsalled ubuntu-gnome-desktop then yeh it is
[09:19] <Laney> rm -r .cache/tracker?
[09:20] <darkxst> Laney, it will only rebuild that on next reboot, you probably want to remove traacker binaries/desktop files
[09:21] <Laney> the packages are gone
[09:21] <Laney> the processes are killed
[09:21] <Laney> and that directory is now HISTORY
[09:22] <darkxst> Laney, that should be enough, but if not there is a script in git to clean out everything
[09:22] <Laney> totem-mozilla RIP :'(
[09:23] <darkxst> Laney, https://git.gnome.org/browse/tracker/tree/utils/clean-prefix
[09:24] <Laney> ok, running it
[09:24] <Laney> fullscreen videos have a headerbar that doesn't go away, and when I move the mouse another one appears
[09:25] <darkxst> Laney, Headerbar or titlebar?
[09:25] <Laney> every time I relaunch the saved videos are duplicated
[09:26] <Laney> looks like a headerbar to me
[09:26] <Laney> inspector's pick a widget thing won't get it
[09:26] <Laney> ah there we go, TotemMainToolbar
[09:27] <Laney> there's something called toolbar-revealer too, probably just a simple de-headerbar thing I'd guess
[09:27] <darkxst> Laney, if it only happens in fullscreen, yes would be simple fix
[09:28] <Laney> prefs dialog has a headerbar
[09:28] <Laney> I could fix that one, done a ton of that kind of work
[09:29] <darkxst> Laney, ok, I don't think I have fixed dialog headers
[09:29] <Laney> there's a property dialogs-use-headerbar or something that you have to fiddle with
[09:29] <Laney> on GtkDialog
[09:29] <darkxst> but the fullscreen issue sholuld be an easy fix
[09:30] <Laney> some of the channels are a bit busted
[09:30] <darkxst> which ones?
[09:30] <darkxst> they all come through plugins but seem to work here
[09:30] <Laney> guardian seems to require authentication (forbidden on console), euronews doesn't play
[09:31] <darkxst> Laney, I doubt they will be in the package that get MIR'd
[09:32] <darkxst> so wouldn't show up
[09:32] <Laney> fair
[09:32] <Laney> still it sounds like a good feature so worth a bug at least
[09:34] <darkxst> Laney, euronews was working
[09:34] <darkxst> not sure about guardian
[09:35] <darkxst> I can't even launch totem currently (probaby the same gtk bug that breaks gdm)
[09:36] <darkxst> my laptop needs a sledge hammer or a new screen ;(
[09:36] <Laney> I get "The movie could not be read"
[09:37] <Laney> wonder what the video duplication thing is about
[09:37] <darkxst> and alot of the remote content comes through lua factory or whatever its called, so maybe just bad links/lack of codecs
[09:37] <darkxst> Laney, in recents?
[09:37] <Laney> the first screen
[09:37] <darkxst> yeh
[09:37] <larsu> willcooke: thanks. Yes, they can
[09:38] <Laney> hmm, I deleted them and then restarted
[09:38] <Laney> back from the dead!
[09:38] <larsu> hi Laney :)
[09:38] <willcooke> larsu, nice - could you (at some point this week) send me a quick screenshot of what a styled Gtk scrollbar might look like)?
[09:38] <darkxst> back in grilo-bookmarks matbe?
[09:38] <Laney> hey larsu
[09:38] <Laney> darkxst: can I view it outside of totem?
[09:40] <seb128> wth libtool
[09:40] <seb128> /bin/bash ../../libtool   --mode=install /usr/bin/install -c   libgbtgeoclue.la '/tmp/install/usr/lib/gnome-bluetooth/plugins/'
[09:40] <seb128> libtool: install: error: cannot install `libgbtgeoclue.la' to a directory not ending in /usr/lib/gnome-bluetooth/plugins/
[09:40] <seb128>  
[09:40] <seb128> '/tmp/install/usr/lib/gnome-bluetooth/plugins/' does end with /usr/lib/gnome-bluetooth/plugins/ no?!
[09:41] <larsu> willcooke: sure
[09:44] <darkxst> laney, bpp
[09:44] <larsu> willcooke: depens a bit on how design wants them, of course :)  We can't have them like we did before (with a separate thumb thingy), but style wise we can go crazy on those two bars (the trough and the slider)
[09:44] <darkxst> bookmarks shoujld inly pick up things explicitely added via the + menu
[09:45] <Laney> darkxst: ah it's just sqlite
[09:45] <Laney> I see 16 copies of the same video in there
[09:45] <willcooke> larsu, understood - I think for now, if we can just match the colours that will be fine
[09:45] <darkxst> filesystem scans your drive, but thats not configured currently I believe
[09:45] <willcooke> fine enough for me to run past Mark & John anyway
[09:45] <larsu> ok
[09:46] <larsu> fun
[09:46] <seb128> hate libtool
[09:47] <larsu> seb128: welcome to the club. Everyone is in it.
[09:47]  * darkxst needs dinner back in a bit
[09:47] <seb128> larsu, :-)
[09:47] <seb128> srly
[09:48] <larsu> Laney: figured out the gnome-screenshot problem: it exits before the flash finishes
[09:48] <larsu> also, it does everything synchronously
[09:48] <larsu> so if you have a slow drive, you'll see longer white screen in the beginning
[09:49]  * larsu is looking into a fix
[09:49] <Laney> really?
[09:49] <Laney> I thought it was flash then show the UI
[09:49] <Laney> at least if you just run gnome-screenshot
[09:50] <larsu> depends on the mode
[09:50] <larsu> I was running it like it's run when you hit prtnscrn
[09:51] <larsu> gah, the print screen button
[09:52] <Laney> I did this http://paste.ubuntu.com/10156184/
[09:53] <larsu> yes, this solves the "stays opaque all the time" bug
[09:53] <larsu> I fixed this too, but a bit differently
[09:53] <Laney> ya
[09:53] <larsu> Laney: should we fix the other bug at all, then? Or are we ok with short flashes when hitting print screen?
[09:53] <Laney> it's meant to flash
[09:53] <Laney> but the opacity doesn't work
[09:54] <Laney> that's the visual thing
[09:54] <Laney> we should fix it
[09:54] <larsu> right, remove the set_visual() call
[09:54] <larsu> that fixes it for m
[09:54]  * larsu is talking about yet another bug, but Laney doesn't seem to have noticed it
[09:54] <Laney> don't think so
[09:57] <Laney> cheese's flash seems to still work btw
[09:58] <larsu> cheese needs a cluttervideosink for me
[09:58] <Laney> probably got blacklisted at some point
[09:58] <Laney> rm ~/.cache/gstreamer-1.0/registry*
[09:59] <larsu> indeed, thanks
[09:59] <larsu> lol
[09:59] <larsu> flash works, but "there was an error playing video from the webcam" right after it took the pic
[09:59] <larsu> and it didn't actually take it
[09:59] <Laney> amigadaveeeeeeeee
[09:59] <larsu> :)
[10:00] <Laney> anwyay I guess from gnome-screenshot's filename that it stole this code from cheese at some point, could presumably do so again
[10:01]  * larsu is on it
[10:01] <darkxst> gnome-screenshot would be pretty dead upstream, unless the flashback guys have resurrected it
[10:01] <Laney> cool
[10:02] <Laney> darkxst: AFAIK it is used but the actual screenshotting is done by gnome-shell
[10:02] <Laney> like the ui to select an area and save the picture and stuff is still in it
[10:03] <larsu> ya, the ui was updated as well
[10:03] <darkxst> Laney, gnome-shell has no external UI for screenshots
[10:03] <Laney> so gnome-screenshot still is alive
[10:03] <Laney> it got ported to this new itnerface
[10:03]  * larsu read it-nerdface
[10:04] <Laney> me typey good
[10:05] <darkxst> Laney, still not convinced that gnome-shell uses it at all
[10:05] <Laney> maybe not if you press print screen but you can still use the application
[10:06] <robertoper> Hi! I would like to try Ubuntu Next (Unity8) on my desktop. And It worked one time in the past, but now It doesn't log in. It shows the LightDM but when I click on the login button it only shows the lightdm again with blank login window. Any idea?
[10:06] <darkxst> not in gnome-shell
[10:06] <Laney> btw I just ran the appstream-glib tests and they worked
[10:06] <darkxst> that gives you a flash and then nothing
[10:06] <darkxst> Laney, I was running upstream 3.15.x tests so maybe the issue is there
[10:14] <robertoper> I found the bug: https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1320356
[10:14] <robertoper> Any idea or a workaround?
[10:26] <seb128> robertoper, try maybe #ubuntu-unity
[10:27] <robertoper> seb128: thanks, I'll give it a try
[10:34]  * xnox is giggling at http://youtu.be/4KNRzdeUaC4
[10:34] <xnox> i don't think i want to use desktop next as my main DE yet
[10:39] <xnox> popup "sign into U1 to get update" -> presenter "is u1 even a thing still?....."
[10:41] <seb128> xnox, sure is
[10:42] <seb128> xnox, it's what handle the log-in to ubuntu services (websites, click store on touch, etc)
[10:45] <didrocks> yeah, the sso part is
[10:46] <xnox> i know, he doesn't =)
[10:47] <didrocks> yeah
[10:47] <xnox> the video is funny. wifi connection didn't work for some reason, thus scopes & updates didn't work and then the presenter says "i guess that's what the future looks like for canonical...."
[10:47] <xnox> a bit of a fail video to be honest.
[10:47] <didrocks> seb128: we should probably hack system-settings to disable system update proposals until we have the image based layout
[10:48] <didrocks> xnox: argh :/
[10:48] <xnox> pretty much every other screen says it's a phone
[10:48] <xnox> (at least in that video)
[10:48] <xnox> as in "connect this phone to computer to transfer videos on it"
[10:49] <seb128> didrocks, where does it propose system updates?
[10:49] <didrocks> seb128: it doesn't propose, it's just spinning forever (but I'm unsure if it's because it doesn't have the layout it expects or that udm isn't aware of the "no network" thing)
[10:50] <seb128> didrocks, the updates panel works on desktop for me, I can update clicks from it
[10:50] <seb128> didrocks, the keep checking is probably a connectivity issue
[10:50] <xnox> i want to pilot plasma5 and possibly switch to that....
[10:50] <seb128> with u-d-m
[10:51] <seb128> xnox, "pilot"?
[10:51] <xnox> as in try-out, like tv-series have pilots
[10:51] <seb128> ah
[10:52] <seb128> hum
[10:52] <seb128> Laney,
[10:53] <seb128> "  * Fallback icon themes are deprecated & ignored upstream, drop the patch and
[10:53] <seb128>     the setting in debian/settings.ini."
[10:53] <seb128> isn't that a problem?
[10:53] <didrocks> seb128: yeah, I guess connecitivity as a "not on network, but it thinks it is"
[10:53] <Laney> it happened ages ago
[10:53] <Laney> so clearly not
[10:53] <seb128> ages being 3.12 or before?
[10:53] <didrocks> dart support added to ubuntu make in less time than the unity8 video trial :)
[10:54] <seb128> didrocks, lol
[10:54] <Laney> 3.10
[10:55] <seb128> hum, k
[10:55] <seb128> I wonder if that means we regressed on some icons without noticing
[10:59] <seb128> k, can't find the original bug on why we added that change
[10:59] <seb128> I'm pretty sure that's going to create some bugs in some cases
[10:59] <seb128> but could be in cases where a settings daemon is not running
[11:00] <seb128> oh, well, I gave up trying to not have regressions for non standard uses anyway
[11:00]  * seb128 goes back to bluetooth hacking
[11:05] <Laney> Then you get the gtk-icon-theme-name theme being used no?
[11:06] <seb128> Laney, well, I don't remember why it was useful, but in fact it's ok, upstream sort of took the patch
[11:06] <seb128> https://git.gnome.org/browse/gtk+/commit/?id=a093cd2a22173369424878eb6d8c38124e7aa1f9
[11:07] <seb128> and I think the issue was when using an icon theme that doesn't inherit "gnome"
[11:07] <tjaalton> colord seems outdated and still getting crash reports
[11:07] <seb128> like that comment says, under KDE
[11:08] <seb128> that would result in buggy icons in GTK apps, since often they rely on icons from the gnome theme
[11:08] <Laney> ya, they just removed the configuration
[11:08] <seb128> that comment didn't state that they add "gnome" to the standard fallback :-)
[11:08] <seb128> but all is fine, good
[11:08] <Laney> tjaalton: RAOF has been maintaining that
[11:08] <seb128> tjaalton, is the second statement having to do with the first one?
[11:08] <seb128> but other what Laney says
[11:09] <tjaalton> seb128: assuming 1.2.1...1.2.8 would fix something
[11:09] <tjaalton> Laney: yeah noticed raof is the maintainer
[11:10] <Laney> If you're interested in helping with it, mail him and see if you can be an Uploader? :-)
[11:12] <tjaalton> I'll do that
[11:13] <Laney> \o/
[11:14] <pitti> seb128: I finally got around to sending an MP for bug 1411972 FTR
[11:15] <seb128> pitti, danke
[11:17] <pitti> Laney, seb128: are you still interested in testing gtk 3.15.4 from the PPA, or does the ML discussion (and some IRC discussions) made that first version obsolet?
[11:17] <Laney> pitti: will follow up after the meeting later
[11:18] <pitti> *nod*
[11:18] <seb128> pitti, what Laney said I guess :-)
[11:18] <pitti> I mean, pretty much the only thing that has to work for me is terminal :) (firefox is still GTK 2)
[11:18] <Laney> you're so demanding!
[11:19] <pitti> oh, and gtimelog of course!
[11:23] <Sweet5hark> http://www.google.com/trends/explore#q=libreoffice%2C%20openoffice&date=today%203-m&cmpt=q&tz= <- so in cause anyone is wondering: it takes about 4,5 years to move a brand.
[11:57] <seb128> Sweet5hark, doesn't seem to be much change over the years, that's weird?
[12:00] <Sweet5hark> seb128: AOO did approx. nothing for 5 years, we did a lot, and still it took 5 years to even get parity. is that weird? well, to someone with a clue on the topic it should appear so ...
[12:02] <seb128> Sweet5hark, well, I'm unsure how you read this graph, but it doesn't seem you reached parity to me
[12:02] <seb128> or closed the gap
[12:02] <Sweet5hark> seb128: I assumed some of that, but the extend of that was a lesson learned for me: in the end inertia is huge with brands. You have to be very actively evil to destroy them. technology isnt that relevant there.
[12:02] <seb128> right
[12:03] <seb128> http://www.google.com/trends/explore#q=libreoffice%2C%20openoffice&cmpt=q&tz= gives a better view
[12:03] <seb128> so you are closing the gap indeed :-)
[12:04] <Sweet5hark> seb128: well, we broke above "openoffice" for the first time this month. so we will finally get to the point were people are not saying "openoffice" even when they mean "libreoffice" ;)
[12:04] <seb128> Sweet5hark, yeah
[12:05] <Sweet5hark> seb128: If you look at news search, you will find "libreoffice" wiped the floor with the other brand year after year .... but: inertia.
[12:06] <seb128> right
[12:06] <seb128> most people I know still use openoffice
[12:06] <seb128> as a name
[12:17] <Sweet5hark> seb128: yep, see also below at related searches/top: "openoffice libreoffice", "openoffice", "libre office" are the top 3 ... for libreoffice
[12:40]  * mlankhorst revives willcooke 
[12:49]  * mlankhorst searches for libreoffice.org
[12:51] <mlankhorst> excuse me, apache libreoffice.org :P
[13:58] <xnox> desrt: https://bugzilla.gnome.org/show_bug.cgi?id=744273 please pull =)
[13:59] <desrt> :(
[13:59] <desrt> why don't you have a runtime dir?
[13:59] <desrt> the fallback to ~/.cache/ is really just meant to be a fallback
[13:59] <xnox> desrt: and as per spec, things that use that should create it if it doesn't exist.... no?
[14:00] <desrt> well, i wrote that spec
[14:00] <xnox> desrt: maybe you can consult with xdg spec author..... as in yourself =)
[14:00] <desrt> so it only follows that..... uh... i don't remember :)
[14:00]  * desrt checks
[14:00] <xnox> desrt: i don't have ~/.cache, cause it's a headless buildd without a systemd logind session....
[14:01] <desrt> anyway... spec says no such thing
[14:01] <desrt> it specifically says that the system needs to create/delete the dir
[14:01] <desrt> but for the fallback case it doesn't say anything at all
[14:01] <xnox> desrt: so.... the test-suite polutes the user's ~/.cache, instead of making it's own?
[14:02] <desrt> maybe?
[14:02] <xnox> how do you know current run succeeds, vs left-overs magically pass the tests?
[14:02] <desrt> note that ~/.cache/ is not hardcoded here
[14:02] <desrt> we will obey the xdg spec again for the definition of XDG_CACHE_HOME
[14:03] <desrt> not saying that we actually bother to set that one, mind you ;)
[14:03] <xnox> desrt: also "If, when attempting to write a file, the destination directory is non-existant an attempt should be made to create it with permission 0700."
[14:03] <xnox> desrt: from the xdg spec.
[14:04] <xnox> Under referencing this specification.
[14:04] <desrt> under the section about XDG_CONFIG_HOME
[14:05] <desrt> anyway... i don't want to argue about this more because i think you're probably mostly right
[14:05] <desrt> despite what the spec says
[14:05] <desrt> i just have to figure out a nice way to deal with this
[14:05] <xnox> it's for all of them..... My solicitor will be in touch with your lawyer to discuss the details of the argument.
[14:06] <desrt> man
[14:06] <xnox> =) but yeah, ideally one way or the other test-suite should do something sensible.
[14:06] <desrt> sure glad lawyers don't write our specs :)
[14:06] <xnox> that patch is just a hack =)
[14:06] <xnox> but it works, so it must be beautiful and upstream worthy
[14:06] <desrt> so i'm thinking that i want g_get_user_runtime_dir() to make the directory
[14:06] <desrt> but then i could extend the same logic to all of the xdg basedir APIs
[14:07] <xnox> desrt: i also have the ugly patch to plug things when xdg-mime, update-desktop-*, user session dbus is missing -> http://paste.ubuntu.com/10158946/
[14:07] <desrt> which is a bit lame, considering that most of the time those dirs are used for read-only
[14:08] <xnox> but that one sprinkles g_test_skip all of the place with no real checks =)
[14:08] <desrt> really, we need a better test framework
[14:08] <desrt> but that's a yak that i'm not going to be the one to shave :p
[14:08] <desrt> (with XDG_CONFIG_HOME, XDG_CACHE_HOME, etc. all setup properly)
[14:08] <xnox> desrt: well, the spec is about attempts to write.... so i guess something does later on tries to write into it and fails =(
[14:09] <xnox> g_write_user_cache_file_with_create() ? =)
[14:09] <desrt> ya.... this is what i want to avoid, precisely :)
[14:09] <xnox> i don't even know what all the mime databases crap is, and whether i want that on the server or not.
[14:18] <DS-McGuire> larsu, I was referred from Ubuntu-design to ask you about some Ubuntu gtk work that needs to be done, I am good with CSS and I thought I could help, any idea as to what I can help with?
[14:32] <Sweet5hark> *grumble* --- my libreoffice-dbg install seems to take ages for the download.
[15:03] <seb128> not sure I'm going to be used to the new GNOME bugzilla, seems a step backward
[15:07] <xclaesse> seb128, didn't notice any difference, tbh
[15:08] <seb128> it looks like the fdo one
[15:08] <seb128> standard replies have been dropped it seems
[15:08] <seb128> so I guess they dropped the GNOME niceties to go standard bugzilla instead
[15:08] <willcooke> DS-McGuire, larsu is travelling, he'll might be back on later, or more likely tomorrow
[15:08] <xclaesse> seb128, FYI, I reported https://bugzilla.gnome.org/show_bug.cgi?id=744205 and https://bugzilla.gnome.org/show_bug.cgi?id=744204 for the new file chooser
[15:09] <seb128> xclaesse, thanks
[15:09] <DS-McGuire> willcooke, Thank you for the update. Do you know of anyone I can talk to in the meantime?
[15:09] <willcooke> DS-McGuire, larsu will be the best person for sure
[15:09] <DS-McGuire> willcooke, Okay, thanks :)
[15:10] <willcooke> DS-McGuire, sorry to put you on hold, but it'll be best to wait
[15:10] <DS-McGuire> willcooke, It's not a problem at all :)
[15:10] <willcooke> cool, thx DS-McGuire
[15:10] <DS-McGuire> :)
[15:14] <willcooke> seb128, team, going to do the school run - should be back by half past the hour, if not please stand by for a couple of mins :)
[15:14] <seb128> willcooke, k
[15:16] <larsu> DS-McGuire: hi! )
[15:16] <DS-McGuire> larsu, Hello! I wasn't expecting to hear from you today now haha!
[15:17] <larsu> DS-McGuire: I don't have that much time indeed :)
[15:17] <larsu> DS-McGuire: ubuntu's desktop theme could use a refresh
[15:18] <larsu> DS-McGuire: don't worry too much about the css yet, it's quite specific to gtk
[15:18] <DS-McGuire> larsu, Very much.
[15:18] <larsu> but having new visuals would be nice
[15:18] <larsu> haha, yeah
[15:18] <DS-McGuire> larsu, Where do you think I should start?
[15:19] <larsu> DS-McGuire: a small refresh for next cycle would be awesome .Just make it look a bit more modern
[15:20] <larsu> DS-McGuire: do you want to hack on the theme directly?
[15:20] <DS-McGuire> larsu, I would think that would be the best bet. Shall I grab an 15.04 ISO and hack that directly?
[15:20] <larsu> DS-McGuire: otherwise I'm fine implementing it (it's normal css, but requires some knowledge about the internals of gtk)
[15:21] <larsu> DS-McGuire: and our theme is all over the place right now. I've cleaned it up a bit, but didn't get nearly far enough
[15:21] <DS-McGuire> larsu, I am sure I can pick up and learn the GTK as I go along, I am a software engineering student so that should play into what I do/.
[15:22] <DS-McGuire> larsu, What files do you look at mostly? Say in the file system?
[15:22] <larsu> DS-McGuire: ok cool. It's a bit much to get you started on the spot (I'm in a bit of a hurry, too). Can we talk again tomorrow in the morning (ECT) or so?
[15:23] <larsu> DS-McGuire: 15.04 contains an outdated version, I've done quite some fixes for V
[15:23] <DS-McGuire> larsu, Not a problem. IRC?
[15:23] <seb128> larsu, V [15:24] <DS-McGuire> seb128, I assume he means 15.04 still has the old code
[15:24] <seb128> could be yeah
[15:24] <larsu> seb128: thanks for watching. /me just stepped out of a plane
[15:24] <seb128> larsu, had a uneventful flight?
[15:24] <larsu> anyhow, it's better if I get DS-McGuire properly started :)
[15:24] <seb128> yeah
[15:24] <larsu> seb128: ya, but being sick didn't help
[15:25] <seb128> :(
[15:25] <larsu> seb128: everything's fine though
[15:25] <seb128> good
[15:25] <Laney> darkxst: I think the duplicate entries are a bug in the grilo plugin
[15:25] <Laney> FYI
[15:25] <DS-McGuire> larsu, Wow, dude. I don't want to make you worse, rest if you need, I/this can wait :)
[15:25] <Laney> It's got some facility to make thumbnails but this seems to always create a new entry
[15:25] <Laney> Probably fixed upstream but there's no new release yet and it depends on some library called gom
[15:26] <larsu> DS-McGuire: thanks it's not that bad :) Sitting in a cafe drinking a mint tea already ;)
[15:27] <larsu> DS-McGuire: let's have a chat tomorrow. Where are you located?
[15:27] <larsu> Laney: that library is a sqlite wrapper by hergertme and hadess
[15:27] <larsu> Laney: let me know if you have any questions about it
[15:27] <DS-McGuire> larsu, Awesome :) Geographically? Wales in the UK.
[15:28] <Laney> larsu: not atm, just seeing that they ported some parts of grilo to it
[15:28] <Laney> but there's no release using it yet
[15:28] <Laney> would be nice if there was because of ^^^ issue at least
[15:29] <larsu> DS-McGuire: just figuring out if your morning is the same as mine :)
[15:29] <willcooke> back
[15:29] <larsu> Laney: there's a totem/grilo that depends on it but no release yet?
[15:29] <Laney> no
[15:29] <DS-McGuire> larsu,  I will be here most of the day
[15:30] <Laney> I mean if they released what is in git it would probably have some bugs fixed
[15:30] <Laney> due to porting to use gom
[15:30] <larsu> poke hadess :)
[15:30] <Laney> SCARY
[15:30] <larsu> ?
[15:31] <seb128> larsu, did you try to communicate with the guy? ;-)

[15:31] <Laney> now we both pinged him
[15:31] <larsu> seb128: look at the date!
[15:31] <Laney> shit's going to go down
[15:32] <larsu> DOWN
[15:32] <seb128> lol
[15:32] <seb128> larsu, not friday?
[15:32] <larsu> nope
[15:32] <larsu> doesn't even feel like it
[15:32]  * seb128 hugs larsu
[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> 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] <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] <dgadomski> - back to analyzing bug #1104230 fix regression since kernel ~3.16.0-27
[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] <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: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] <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] <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: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?