[06:10] <larsu> good morning!
[06:40] <mpt> “Unhandled Lockdown Error” would be a great name for a band
[07:10] <seb128> good morning desktopers
[07:16] <larsu> "I'm not an expert, but I don't think I need 114 instances of indicator-sound-service."
[07:17] <mpt> Oh dear, did the 115th one crash? That’s the one that plays the sound
[07:18] <larsu> haha
[07:18]  * larsu updates the counter inside indicator-sound service to make it go to 115
[07:21] <willcooke> o/
[07:21] <larsu> morning willcooke!
[07:22] <seb128> hey willcooke
[07:22] <larsu> no pitti today?
[07:22] <seb128> seems not...
[07:22] <seb128> nah, I miss the time where I had scrollbars
[07:22] <seb128> Laney, larsu!!!!
[07:23] <larsu> I was the first person to talk in here at 8:10 today, so I guess not :)
[07:23] <larsu> seb128: you have *no* scrollbars?
[07:23] <seb128> no
[07:23] <seb128> no thumb, no bar, no color, no handle
[07:23] <seb128> nothing
[07:23] <seb128> in gedit or nautilus
[07:23] <seb128> I do have the overshot effect if I scroll with the pad though
[07:24] <larsu> mitya57: I see the point of not wanting to make it slower, but it's producing incorrect results now...
[07:24] <seb128> the overshot effect is buggy btw
[07:24] <seb128> if I'm of the top of a nautilus view and try to scroll up, it displays fully in a non smooth way and stay there for like 3s
[07:25] <larsu> you should see a scrollbar when hovering the window
[07:26] <seb128> not happening
[07:26] <larsu> trackpad?
[07:26] <seb128> dell lattitude with trackpad and nibble
[07:26] <seb128> I use the nibble
[07:26] <seb128> but seems the same with the trackpad
[07:26] <larsu> do you have the new overlay-scrollbar package? (is that even uploaded yet?)
[07:26] <seb128> touchpad
[07:27] <seb128> I upgraded with the ppa which is in the topic
[07:27] <seb128> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ww
[07:27] <seb128> that has a new o-s
[07:29] <larsu> weird, I'm not getting that yet
[07:30] <seb128> oh, it works after unsetting GTK_MODULES
[07:30] <seb128> nothing forced to uninstall o-s-gtk3 for me and I didn't restart my session so the env is still set
[07:30] <seb128> that seems to make o-s not work and gtk scrollbars bug
[07:30] <larsu> Laney fixed that in the MR - we're only loading the module for gtk2
[07:31] <seb128> k
[07:31] <larsu> dunno if we need to handle that case tbh
[07:31] <seb128> oh man, those scrollbars are not nice :-/
[07:31] <larsu> well, they're not themed yet
[07:31] <seb128> k
[07:31] <seb128> I hope they are better once themed, but atm it feels like quite an user regression :-/
[07:32] <seb128> they are width
[07:32] <larsu> we can make them look however you want
[07:32] <larsu> and actually I'd like some input. notadesigner
[07:32] <seb128> my first reaction is "thinner"
[07:32] <larsu> the only thing we're regressing on is that they're not outside the window
[07:32] <larsu> seb128: ya, definitely!
[07:33] <larsu> even Adwaita has them thinner ... and that's saying something ;)
[07:33] <seb128> also the fact that they are rounder at the top/bottom looks weird in e.g gedit
[07:34] <seb128> in nautilus as well in fact
[07:34] <seb128> it looks weird to have a circle against a line
[07:34] <seb128> imho it would be nicer to just have flat borders
[07:34] <larsu> or none if you ask me, android style
[07:34] <larsu> just the thumb
[07:35] <larsu> but then, nobody's asking me
[07:35] <seb128> can we do that?
[07:35] <seb128> mpt, do you think somebody from design could help us and give some recommendation on how new gtk scrollbars should look like?
[07:36] <mpt> ha ha
[07:36] <seb128> mpt, atm they are like on http://tinyurl.com/nhkn93v
[07:37] <larsu> seb128: I've asked for a theme update countless times. We're not getting it.
[07:37] <seb128> larsu, https://blogs.gnome.org/mclasen/files/2013/08/zoomscrollbar.png looks much nicer
[07:37] <seb128> larsu, there is a difference between a theme update and UI recommendations
[07:38] <larsu> fair enough
[07:38] <seb128> like I guess a theme update would require work from an engineer
[07:38] <larsu> so does theming the scrollbars
[07:38] <seb128> where advising on UI details is a pure design thing
[07:38] <seb128> if they do the change
[07:39] <seb128> but it seemed you said you would be happy with them telling us what to do
[07:39] <seb128> like visual
[07:39] <seb128> even if they don't do the actual css changes
[07:39] <larsu> ya I would be, but they're not
[07:39] <seb128> larsu, I would start by doing what is on https://blogs.gnome.org/mclasen/files/2013/08/zoomscrollbar.png with orange as color
[07:39] <seb128> that doesn't have the round corner issue
[07:39] <seb128> nor the width one
[07:39] <larsu> yes, that was my first plan as well
[07:39] <seb128> why is GTK making default widget look buggy?
[07:40] <seb128> just to punish their non GNOME users?!
[07:40] <larsu> this is our theme :)
[07:40] <seb128> we made scrollbars wider on purpose?
[07:40] <larsu> yes
[07:40] <seb128> oh, ok
[07:40] <seb128> why?!
[07:40] <larsu> I don't know :)
[07:40] <mpt> Surely not
[07:40] <larsu> it's old code
[07:40] <larsu> but it's in there
[07:41] <seb128> oh, ok
[07:41] <larsu> I guess for people that turn off o-s?
[07:41] <TheMuso> Hey willcooke.
[07:41] <TheMuso> Hey folks.
[07:41] <seb128> let's delete scrollbar customizations then
[07:41] <larsu> seb128: default gtk is Adwaita now, regardless of if you're on GNOME or not
[07:41] <seb128> just change the color
[07:41] <Sweet5hark> moin
[07:41] <seb128> larsu, k, so it doesn't make sense we are keeping those old hacks
[07:41] <seb128> let's clean them out
[07:41] <seb128> less code ;-)
[07:41] <larsu> I agree
[07:42] <mpt> seb128, yes, just changing the background of the corners so that it is the same color as the trough border would be an improvement
[07:42] <larsu> mpt: no work has gone into theming those yet. All we did was turn off overlay-scrollbars
[07:42] <seb128> mpt, would the ones from https://blogs.gnome.org/mclasen/files/2013/08/zoomscrollbar.png with orange instead of blue look fine to you?
[07:44] <mpt> larsu, then how come the thumb looks the same (e.g. three little grooves) as Ambiance/Radiance in 14.04 with overlay scrollbars uninstalled?
[07:44] <mpt> I’m pretty sure Ambiance+Radiance aren’t inheriting from some other theme there
[07:45] <mpt> seb128, I don’t understand what’s going on in that screenshot. Is the thumb getting *smaller* when you mouse over it?
[07:45] <mpt> I.e. what’s the difference between those three states?
[07:46] <seb128> larsu, ^ do you know?
[07:46] <larsu> mpt: because Ambiance/Radiance has code for theming them when you uninstall overlay-scrollbars...
[07:46] <mpt> larsu, so it still has that same theming in Wily, right?
[07:46] <larsu> yes
[07:47] <seb128> mpt, https://blogs.gnome.org/mclasen/2013/08/05/scrolling-in-gtk/
[07:47] <larsu> mpt, seb128: no, these screenshots are misleading. It gets wider as you mouse-over it
[07:47] <larsu> GTK_THEME=Adwaita gedit to try them out
[07:48] <seb128> the thinner line is when you hold the click
[07:48] <seb128> it goes in autoscrolling mode
[07:48] <mpt> larsu, so we have exactly the same problem with the trough now as we did with the scrollbuttons before: pasty-grey crevices in each corner of the overall area.
[07:48] <seb128> or follow the mouse
[07:49] <larsu> mpt: I can make them #ff0000 if that helps visibility
[07:50] <mpt> larsu, you’re talking about the thumb. I’m talking about the crevices.
[07:51] <larsu> mpt: I don't understand. Which crevices do you mean?
[07:54] <larsu> mpt: where the background shines through between trough and the window border?
[07:56] <mpt> larsu, these bits: http://imgur.com/SvZ4Ezd
[07:57] <mpt> That’s what I thought seb128 was talking about with “<seb128> it looks weird to have a circle against a line”
[07:59] <larsu> mpt: ya, this is the window's background shining through because of the rounded corners. I agree with seb128 that we should flatten them
[08:02] <mpt> larsu, there are two ways to solve the problem: (1) square the corners or (2) fill them with something
[08:02] <mpt> I was suggesting a very simple approach to (2), just fill them with the same color as the scrollbar is already using for its border
[08:04] <mpt> though ideally they’d have their own 3-D appearance, like the thumb does, to make them look intentional
[08:06] <Laney> sup
[08:06] <seb128> hey Laney, wie gehts?
[08:08] <larsu> mpt: hm, I think 3-D might make them look a bit off. They appear only when you're in the window or when swiping
[08:08] <larsu> morning Laney!
[08:09] <Laney> doing good thanks
[08:10] <Laney> I added a breaks to gtk
[08:10] <Laney> it's in a silo now, didn't update that ppa
[08:12] <seb128> so it would force uninstall o-s-gtk3?
[08:13] <Laney> nah it upgrades you to a version which doesn't set GTK_MODULES and doesn't depend on it
[08:13] <Laney> so autoremove should get rid of it
[08:14] <mpt> larsu, fair enough, but if that’s the rule, the whole scrollbar needs redesigning, not just the corners
[08:15] <seb128> Laney, yeah, I didn't restart my session though, so the env is still set and I've no scrollbars in my apps now
[08:15] <seb128> need to restart later ;-)
[08:15]  * seb128 doesn't want to close ongoing work though
[08:15] <larsu> mpt: tell me about it...
[09:29] <seb128> Laney, do you remember if in u-s-s we had/have a way to dynamically list or not plugins from the main grid?
[09:29] <Laney> yes we do
[09:29] <Laney> the battery plugin does it
[09:31] <seb128> thanks
[09:34] <Laney> what will you do
[09:34] <Laney> try to activate the s-i service and hide if that fails?
[09:36] <seb128> Laney, undecided yet, I'm pondering
[09:36] <seb128> 1. check for something that tells me s-i or snappy and hide in the second case, and change the depends to be | snappy-cli
[09:36] <seb128> 2. split the update panel in a new binary which has the depends and see that only in touch
[09:37] <seb128> 2. makes more sense if we plan to write a new panel for snappy updates
[09:38] <seb128> unsure yet, the backend is not going to have a lot on common but maybe the UI can be reused
[09:38] <seb128> or maybe it makes more sense to just start fresh
[09:38] <Laney> larsu: does (g)dbus have any way of asking 'could I activate this name' without actually activating it?
[09:38] <Laney> probably the existing one will get thrown away
[09:38] <Laney> I would have thought
[09:38] <Laney> if snappy it just a completely different thing
[09:39] <Laney> s/it/is/
[09:39] <seb128> the backend at least
[09:39] <seb128> the UI is lilely to stay the same
[09:39] <larsu> Laney: yes: gdbus call -e --dest org.freedesktop.DBus --object-path / --method org.freedesktop.DBus.ListActivatableNames
[09:39] <seb128> but then it's not  a complex bit to copy over
[09:39] <Laney> ah nice
[09:40] <Laney> might be good to use that ^ to tell if system-image is there
[09:40] <larsu> Laney: well, that doesn't do exactly what you want, but there's nothing for individual names
[09:40] <larsu> Laney: other than looking in /usr/share/dbus-1/services
[09:40] <Laney> and yes, I think the UI has some complex state module so is going to be easier to do it over
[09:40] <Laney> larsu: why doesn't it?
[09:41] <larsu> Laney: hm?
[09:41] <larsu> why doesn't it what
[09:43] <Laney> why doesn't it do what we want?
[09:44] <larsu> it gives you a list of activatable names
[09:44] <larsu> doesn't tell you if a specific name is activatable
[09:44] <larsu> of course, you can find out from the liest
[09:45] <larsu> *list. I can't type today. drunk from the smoothie maybe?
[09:45] <Laney> liszt
[09:45] <Laney> I'm missing a piece of knowledge here
[09:45] <seb128> larsu, are you following dholbach on that green smoothie diet?
[09:45] <larsu> Laney: https://www.youtube.com/watch?v=4BJDNw7o6so
[09:45] <larsu> seb128: urgh, no
[09:46] <seb128> k, was wondering :-)
[09:46]  * larsu doesn't like green stuff in smoothies
[09:46] <larsu> unless kiwi
[09:46] <seb128> I see
[09:46] <Laney> nice tune
[09:46] <larsu> phoenix!
[09:46] <larsu> Laney: what are you missing?
[09:47] <Laney> 04/06 10:44:30 <larsu> it gives you a list of activatable names
[09:47] <Laney> 04/06 10:44:43 <larsu> doesn't tell you if a specific name is activatable
[09:47] <Laney> this concept
[09:47] <larsu> you asked for something like IsThisNameActivatable("com.something")
[09:47] <Laney> ya
[09:47] <larsu> but that doesn't exist. What does exist is ListActivatableNames()
[09:47] <Laney> you mean that we have to search the list?
[09:47] <larsu> yes
[09:48] <Laney> oh right
[09:48] <Laney> I get that :P
[09:48] <Laney> I thought that you were trying to tell me about some weird dbus thing
[09:48] <larsu> sorry if that wasn't clear. Just wanted to make the small point that my answer wasn't exactly what you were looking for
[09:48] <Laney> like you can't find out if it is activatable until you actually attempt to activate it
[09:48] <Laney> just that it /might/ be
[09:48] <larsu> no, I think it has to be
[09:48] <larsu> if it's in that list
[09:49] <Laney> nod
[09:49] <larsu> by ... err ... "definition"
[09:49] <seb128> Laney, I'm just going to look for the file on disk
[09:49] <larsu> but at least I got to listen to some phoenix because of this
[09:49] <Laney> haha
[09:49] <Laney> oh man :'(
[09:49] <Laney> this is one of those laney times
[09:50] <larsu> seb128: look into everywhere that's in $XDG_DATA_DIRS
[09:50] <larsu> actually that seems wrong
[09:50] <larsu> that var doesn't contain my .local/share
[09:50] <larsu> but dbus definitely activates stuff for me from there
[09:51] <larsu> oh! that's a defined fallback
[09:51] <larsu> neat
[10:02] <seb128> larsu, no, just for /etc/dbus-1/system.d/com.canonical.SystemImage.conf
[10:02] <seb128> it's basically a "is that package installed"
[10:02] <seb128> or /usr/share/dbus-1/system-services/com.canonical.SystemImage.service
[10:05] <seb128> Laney, the way you did it for battery seems to be from the battery plugin ... does it mean we have to load the backend on the main view only to get the dynamic visibility?
[10:08] <Laney> seb128: it's a different "plugin"
[10:08] <Laney> see plugins/battery/plugin - this isn't the full panel
[10:08] <Laney> (great naming)
[10:08] <seb128> Laney, so I would need to do a different "plugin" for system-updates only to deal with the visibility?
[10:09] <seb128> I wonder if it wouldn't be easier to just special case that in the visibility main function
[10:09] <Laney> yeah, it's quite minimal though
[10:09] <Laney> ...
[10:10] <seb128> was that a "..." = "no comment", like in reaction to "lets do a hack"?
[10:11] <Laney> indeed
[10:11] <Laney> you could convince kenvandine though and ignore me ;-)
[10:11] <seb128> well, I don't think it makes sense to have plugins added for each panel just to tweak the visiblity
[10:11] <seb128> need a better way ;-)
[10:11] <seb128> need to go for some erands/get food, biab, going to think about it while walking
[10:12] <Laney> then come up with a better way
[10:12] <Laney> the plugins should handle this themselves
[10:12] <Laney> one way or another - for example you could add a new key into the .pluginfile
[10:12] <Laney> VisibleIf : DbusActivatable:...
[10:12] <Laney> FileExists: ...
[10:21] <darkxst> Laney, what happened to your gtk upload? anyway mutter and shell are queued up in proposed, so let it through whenever
[10:22] <Laney> It's in a CI train silo because I'm uploading it with the overlay scrollbars
[10:22] <Laney> will go in shortly
[10:25] <darkxst> Laney, np, not concerned about delays really, was just letting you know shell was ready really
[10:48] <Laney> darkxst: done
[10:48] <Laney> enjoy your breakage!
[10:50] <darkxst> Laney, pretty sure I avoided major breakage with the shell update, so should be ok
[10:50] <Laney> I mean my breakage really :)
[11:08] <darkxst> Laney, ha ok
[11:11] <Laney> it is too nice to be inside
[11:11]  * Laney relocates
[11:13]  * Laney goes blind in a good way
[11:13]  * larsu had a nightmare about going blind
[11:14] <willcooke> this is a good plan Laney.  I think a lunch break is called for in the sunshine...
[11:14] <Laney> woah you just reminded me
[11:14] <willcooke> food?
[11:14] <Laney> I had one last night where I lost half of both of my ring fingers
[11:14] <willcooke> oh
[11:14] <willcooke> ok then
[11:14]  * willcooke backs slowly away
[11:14] <Laney> was obviously most concerned about not being able to climb
[11:14] <willcooke> or type
[11:14] <Laney> good nightmare would have again
[11:15] <larsu> obviously
[11:15] <larsu> haha
[11:15] <larsu> willcooke: went for a run in the sun. Can recommend. Now eating a carrot instead of lunch
[11:15] <larsu> notsurehowthathappenend
[11:17] <willcooke> :D
[11:45] <Laney> larsu: do you have a version of your totem menubar patch on top of 3.14?
[11:46] <larsu> Laney: nope. Want one?
[11:46] <Laney> would be good
[11:46] <Laney> it's got some conflicts
[11:46] <larsu> why not just take 3.16?
[11:47] <Laney> need that to SRU it
[11:47] <darkxst> or my original 3.14 patches?
[11:47] <Laney> it's a fix to those
[11:48] <darkxst> oh ok
[11:48] <larsu> Laney: fixing some food right now, but will do it right after
[11:49] <Laney> darkxst: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1447224
[11:50] <Laney> larsu: actually it might be easy to resolve them, let me try
[11:55] <darkxst> Laney, I can't track every single bug in the ubuntu sphere
[11:57] <Laney> I didn't ask you to
[11:57] <Laney> we were just fixing it
[12:01] <darkxst> ok
[12:11] <larsu> Laney: let me know if you need help
[12:12] <Laney> sure, test building atm
[12:14]  * darkxst needs to sleep. night all
[12:15] <Laney> nn
[12:15] <larsu> night
[12:56] <kenvandine> seb128, Laney: i like the idea of extending the plugin settings file, VisibleIf could be very useful
[12:57] <Laney> would be good to abstract some common patterns if they might be used more in future
[12:57] <Laney> like if we expect applications to plug in there
[13:34] <Laney> larsu: so my backport doesn't work
[13:34] <Laney> also if I run from master on that Sintel video I don't get any languages in the menu
[13:34] <Laney> and because the app menu is gone it's not possible to change languages in full screen
[13:34] <larsu> Laney: yes, I have plans for that, but gotta run now (will look at it later)
[13:35] <Laney> ok thanks!
[13:35] <Laney> subtitles do work on master & trad menu though
[13:36] <Laney> ah wait, maybe it's just that this video doesn't have any languages
[13:36] <Laney> in that case it might be an idea to disable the menu item or otherwise indicate that
[13:36] <Laney> currently just shows an empty menu (i.e. a line)
[13:50] <maxb> Hi. I'm using gitg in vivid, and I can't seem to find its preferences dialog. I'm suspicious it's something to do with the ubuntu menuproxy stuff, but setting UBUNTU_MENUPROXY=0 doesn't seem to fix things.
[13:50] <maxb> Are there any related suggestions about troubleshooting inaccessible menus that are configured in an application's vala code via Gtk.Applicationn.add_action_entries ?
[13:51] <maxb> Something to do with 'application' vs. 'window' menus, and these not being well translated into Unity?
[14:11] <Laney> maxb: Weird!
[14:12] <maxb> yes
[14:12] <Laney> It breaks for me with in-app menus  but works without although it is called "Unknown Application Name" then
[14:12] <maxb> Hmm, so running 'UBUNTU_MENUPROXY=0 gitg' actually gives you a visibly different display, then?
[14:12] <Laney> no
[14:12] <maxb> ph
[14:12] <Laney> I go to Appearance in the control centre and then Behaviour
[14:13] <Laney> and change it to In the menu bar
[14:13]  * maxb tries that
[14:13] <Laney> then it's back in the global menu and works
[14:13] <Laney> I guess it's LIM being broken with header bars
[14:13] <maxb> wait, what, now it's working
[14:14] <maxb> ish
[14:14] <maxb> My setting was already 'in the menu bar'
[14:14] <maxb> However, this time I actually git some entries dropping down from the 'gitg' menu
[14:15] <maxb> I was getting a zero-item menu before
[14:15] <Laney> If you can reproduce then T_revinho is the Unity guy to talk to
[14:15] <maxb> Though, now I seem to have a different bug, as as soon as I clicked on a checkbox, it went into a tight-loop logging Gtk-CRITICAL **: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
[14:16] <maxb> Ah
[14:17] <maxb> I've figured out one portion of the confusion. I was using sudo to run gitg on /etc
[14:17] <maxb> In retrospect it is 'obvious' how that could break the integration
[14:17]  * maxb will pause, reconsider, and attempt to isolate one underlying issue at a time
[14:19] <maxb> (I also have an issue that I can't seem to rebuild vivid's gitg source package on vivid, with build-depends installed - it dies with error: Package `ggit-1.0' not found in specified Vala API directories or GObject-Introspection GIR directories )
[14:34] <seb128> kenvandine, Laney, what do you think about http://paste.ubuntu.com/11566702/ ?
[14:35] <kenvandine> seb128, pretty good
[14:36] <kenvandine> i'd kind of like it to handle cases of than file
[14:36] <seb128> other than file you mean?
[14:36] <kenvandine> like gsettings key?
[14:36] <kenvandine> yeah
[14:36] <kenvandine> so visible-if-file-exits
[14:37] <kenvandine> visible-if-settings-key
[14:37] <kenvandine> etc
[14:37] <seb128> k
[14:37] <seb128> I can rename it
[14:37] <kenvandine> just a though
[14:37] <kenvandine> thought
[14:37] <kenvandine> i'd imagine we might find other cases like that, so yeah renaming it would be more concise
[14:37] <kenvandine> unless we made it a dict
[14:38] <kenvandine> visible-if-cond ?
[14:38] <kenvandine> then file: "some/path/to/file"
[14:38] <kenvandine> visible-if-condition maybe
[14:38] <seb128> I'm still undecided if we should have keys
[14:39] <kenvandine> or just visible-if
[14:39] <seb128> we currently have a "has-dynamic-visibility: boolean value, telling whether the plugin visibility can be determined by the plugin itself only "
[14:39] <kenvandine> yeah, i don't love that
[14:39] <kenvandine> it means the plugin has to load before deciding
[14:39] <seb128> right
[14:39] <kenvandine> which caused a ton of headache making it faster
[14:39] <seb128> also it means UI builds and then change/flickers
[14:39] <kenvandine> yeah
[14:40] <kenvandine> i spent a bunch of time on that in DC
[14:40] <seb128> should I just submit with the rename?
[14:40] <seb128> I don't want to spend much time on that now
[14:40] <seb128> just unblock the snappy image
[14:40] <kenvandine> what do you think of the idea of a dict?
[14:40] <seb128> extra parsing to do
[14:40] <kenvandine> ok
[14:41] <kenvandine> just submit with the rename :)
[14:41] <seb128> thanks
[14:41] <seb128> we can rename/change it later for a dict or shell commands return value or something
[14:41] <kenvandine> ok
[14:47] <cyphermox> seb128: can we talk about bluez 5 ?
[14:47] <seb128> cyphermox, sure
[14:47] <cyphermox> have you heard anything / plans to move to it this cycle finally?
[14:47] <cyphermox> I'm just asking out of interest :)
[14:53] <seb128> cyphermox, not more than previous cycle
[14:53] <seb128> check with rsalveti I guess
[14:53] <cyphermox> ok
[14:53] <seb128> the phone guys were still looking at it before vivid
[14:53] <cyphermox> thanks
[14:53] <seb128> yw!
[14:54] <cyphermox> yeah.. sad that it takes so long to get back to 2015
[14:54] <cyphermox> soon we'll be at the point where more people are going to complain that their dynamically pairing mice don't work well, and stuff like that. or want BLE
[14:55] <rsalveti> cyphermox: there is ongoing conversations to get this on track quite soon actually
[14:55] <cyphermox> ok
[14:55] <rsalveti> we found out we have aosp based trees with the required kernel work already
[14:55] <seb128> kenvandine, https://code.launchpad.net/~seb128/ubuntu-system-settings/visible-file-exists/+merge/261096
[14:55] <rsalveti> the main blocker atm is porting the patches for krillin
[14:55] <rsalveti> but we might have a 3.10 kernel for krillin soon
[14:55] <rsalveti> which would help quite a bit
[14:55] <cyphermox> ok
[14:56] <rsalveti> cyphermox: ping john-mcaleely if you want to know more, he was on top of it
[14:56] <rsalveti> (or should be soon)
[14:56]  * rsalveti is mostly involved with snappy atm
[14:56] <cyphermox> rsalveti: thanks, that's really all I wanted to know
[14:56] <rsalveti> cool
[18:09] <willcooke> g'night