[00:45] <akiva-thinkpad> Hey check this out https://www.youtube.com/watch?v=zt_hkSKQp6k pretty interesting first time use of 14.10 by a illiterate user
[06:21] <pitti> Good morning
[06:22] <pitti> Laney: hm, it's running here, so bug report appreciated; stgraber or hallyn are certainly interested
[07:28] <didrocks> good morning
[07:28] <akiva-thinkpad> didrocks, morning
[07:59] <pitti> bonjour didrocks !
[07:59] <pitti> didrocks: as-tu eu un bon voyage ?
[07:59] <didrocks> pitti: bof, le train est parti avec 15 minutes d'avance sur l'heure prévue
[08:00] <didrocks> pitti: donc obligé de prendre un thalys pour Paris, changer de gare du Nord -> gare de Lyon à Paris avec le RER
[08:00] <didrocks> pitti: puis TGV Paris -> Lyon
[08:00] <didrocks> arrivé avec ~2h de retard par rapport à l'heure prévue initiallement
[08:01] <pitti> didrocks: uh, trop de neige ?
[08:02] <didrocks> pitti: non, juste qu'ils ont changé l'horaire du premier train sans prévenir personne
[08:03] <pitti> nous avons eu quelque rétard hier à cause de la neige
[08:03] <didrocks> pitti: là, c'était parti en avance, (de 15 minutes), pas en retard :)
[08:07] <seb128> good morning desktopers
[08:07] <seb128> hey didrocks pitti
[08:07] <pitti> bonjour seb128, ça va ? bon voyage chez toi ?
[08:08] <didrocks> re seb128!
[08:08] <seb128> pitti, salut, oui, très bien, le train c'est facile :-)
[08:08] <seb128> pitti, et toi, bon w.e ?
[08:10] <pitti> seb128: oui ! nous sommes allès à Zurich, pour visiter un ami
[08:10] <pitti> seb128: he had a new theater play (he has done amateur acting for quite some years now)
[08:12] <seb128> oh, nice
[08:12] <seb128> did you have fun there?
[08:13] <pitti> seb128: yes, we did indeed! he had 6 guests altogether, so nice theater play and some Zurich sightseeing plus some nice drinking and fun in the evenings
[08:13] <seb128> sounds fun indeed
[08:13] <didrocks> great!
[08:49] <mlankhorst> Ggood morning, desktop!
[08:50] <akiva-thinkpad> o/
[08:52] <darkxst> hey seb128 didrocks
[08:52] <darkxst> seb128, did you have a try of my totem build with menus?
[08:53] <willcooke> Morning desktoppers
[08:53] <didrocks> hey darkxst, mlankhorst, willcooke
[08:55] <mlankhorst> everyone made it back home safely?
[08:55] <seb128> darkxst, hey, not yet. Where is it again? And what's the status with the new depends, grilo, etc?
[08:55] <seb128> mlankhorst, hey, yes! how is your fosdemflu, feeling better?
[08:55] <darkxst> seb128, gnome3 ppa
[08:55] <mlankhorst> just a cough remaining
[08:55] <darkxst> grilo-plugins MIR is approved pending split
[08:55] <darkxst> I patched totem to make the tracker plugin optional
[08:58] <darkxst> seb128, bug 1394731
[08:58] <seb128> darkxst, so without those it just behaves as a "normal" player?
[08:59] <darkxst> seb128, no without those the recents/channels view is completely broken
[09:00] <darkxst> you would only be able to play things by passing the video file as an argument
[09:00] <seb128> hum
[09:00] <seb128> is that something we consider acceptable?
[09:02] <darkxst> seb128, no, its needs grilo-plugins
[09:02] <darkxst> but we will split them so there is not a whole lot of random/useless plugins in main
[09:03] <darkxst> seb128, but consider the tracker plugin a soft-dep
[09:03] <seb128> k
[09:03] <seb128> well, ideally I would like to try with the minimal set to see what's working and not and how much it pulls in
[09:03] <darkxst> seb128, I summarised required plugind in https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/comments/2
[09:04] <seb128> I guess e.g youtube doesn't add much extra depends?
[09:04] <seb128> in which case we should probably seed it as well
[09:04] <seb128> the feature is useful
[09:05] <darkxst> seb128, not sure they even pull in any extra deps
[09:05] <darkxst> the only thing in universe is dleyna-server and that is suggests
[09:06] <seb128> k
[09:06] <darkxst> (alot of the earlier discussions were based around tracker but that is in main anyway now, and its only one small lib for non-GNOME environments, that is already there)
[09:07] <seb128> yeah, as long as it doesn't force us to run the disk indexer...
[09:08] <darkxst> seb128, only if you have tracker-fied your system
[09:09] <Laney> HEY!
[09:09] <didrocks> it's a Laney!
[09:10] <seb128> hey Laney, how is u.k today? had a good w.e?
[09:10] <darkxst> hey Laney
[09:11] <larsu> morning Laney!
[09:13] <darkxst> Laney, re Gtk+ looks like we need a full core update for GNOME
[09:14] <darkxst> and wouldnt even consider that really until after .90 or .91 but thats well FFe territory
[09:14] <Laney> there's somethign terrible going on with my interwebs, one second
[09:14] <Laney> buh
[09:14] <Laney> had to restart n-m
[09:14] <seb128> just curious, why a gtk update enforces a GNOME update?
[09:15] <Laney> darkxst: do you know what the problem is there?
[09:15] <darkxst> seb128, gtk window decorations
[09:15] <seb128> GTK is supposed to be abi/api compatible, what did they change? is that theming?
[09:15] <Laney> it'd probably be enough to make us not do it I guess, don't want to ruin your stuff
[09:15] <seb128> not going to make larsu happy :-(
[09:16] <darkxst> seb128, GTK is now drawing window decorations for GNOME theme
[09:16] <Laney> and hello, yes I had a good weekend!
[09:16] <larsu> darkxst: what's your problem with that? You need to update your theme?
[09:16] <Laney> we did some DIY in preparation for a bike shed ;-)
[09:16] <larsu> what color does it have?
[09:16] <darkxst> larsu, no mutter 3.14 don't support that
[09:16] <seb128> darkxst, how does that work? if you don't update g-s, etc, can't you just get decoration drawed the way they currently are?
[09:17] <darkxst> seb128, gnome theme is packaged in gtk+ now
[09:17] <seb128> can't we undo that easily?
[09:17] <darkxst> we could backport the old theme, and loose any fixes made
[09:17] <seb128> e.g keep using adwaita
[09:17] <larsu> or just update mutter?
[09:17] <seb128> larsu, well, that's what he meant by update GNOME
[09:17] <larsu> update mutter != update gnome
[09:17] <seb128> larsu, they don't want an out of sync versions between g-s etc
[09:17] <larsu> but meh
[09:18] <darkxst> larsu, there has been another major reworking of input device handling
[09:18] <seb128> but you know how things up when you try to mismatch components
[09:18] <seb128> +turn
[09:18] <darkxst> I don't feel comfortable splitting on mutter and g-s-d with that
[09:18] <Laney> lolz, bugzilla seems busted
[09:18] <larsu> seb128: fair enough
[09:18] <darkxst> Laney, Maintenance
[09:18] <Laney> ah some kind of upgrade
[09:18] <larsu> Laney: scheduled updatd
[09:18] <larsu> status.gnome.org
[09:19] <Laney> darkxst: is this a problem because adwaita is in gtk now?
[09:21] <desrt> Laney: old problem
[09:21] <desrt> darkxst: i don't get why old mutter couldn't go on drawing the decorations.  is it because they'd mismatch the theme?
[09:21] <darkxst> Laney, well partly, but the main reason we use Adwaita is because upstream keep it in sync
[09:21] <desrt> that's sort of a problem we already had for server-decorated windows
[09:22] <darkxst> desrt, they scrapped the metacity window themes, and switched to gtk/css
[09:22] <desrt> darkxst: ya.. .i get that
[09:22] <darkxst> mutter- 3.14 knows nothing of that
[09:22] <desrt> but you seem to want to keep the old matter
[09:22] <desrt> *mutter
[09:22] <darkxst> desrt, I am all for updating to 3.16
[09:22] <darkxst> but not now
[09:22] <desrt> so it will still have the code for drawing old themes....
[09:23] <desrt> i just don't understand why it would possibly cause a problem to upgrade gtk now
[09:23] <darkxst> desrt, theme issues I guess
[09:23] <desrt> they didn't remove the mutter theme drawing code from gtk... they removed it from mutter
[09:23] <desrt> darkxst: ya... so the theme will be slightly out of sync... but nothing more than it was before
[09:23] <darkxst> desrt, they changed the adwaita theme to accomadate the new decorations that is the problem
[09:24] <darkxst> desrt, its pretty broken black titlebars etc
[09:24] <desrt> darkxst: if you're planning to upgrade mutter later in the cycle anyway, then is a slight theme mismatch during development really a huge issue?
[09:24] <desrt> ... something else sounds wrong
[09:25] <desrt> because if mutter is drawing server-side decorations then it should still be using the old theme (ie: nothing gtk does could affect it)
[09:25] <darkxst> desrt, there is no metacity theme anymore
[09:25] <darkxst> adwaita is packaged in gtk+
[09:26] <desrt> only the gtk css
[09:26] <larsu> add it back?! Doesn't sound that hard
[09:26] <desrt> the metacity theme is in gnome-themes-standard-data
[09:26] <desrt> as an xml file in /usr/share/themes/Adwaita/metacity-1
[09:35] <darkxst> desrt, maybe as an intermin solution
[09:35] <desrt> well -- yes.... the longterm solution would be to upgrade to the new mutter
[09:35] <desrt> and until then there is no sense in blocking a gtk upgrade because of one little xml file
[09:35] <desrt> (okay... it's not particularly little, admittedly....)
[09:36] <darkxst> and it may not be that simple either
[09:36] <darkxst> though I havent tried
[09:47] <willcooke> ARGH!  I cant live like this any more....
[09:47] <larsu> darkxst: only non-focused titlebars are black for me
[09:47] <willcooke> I'm going to have to
[09:47] <larsu> darkxst: same for you?
[09:47] <willcooke> tidy my desk
[09:47] <larsu> willcooke: happy monday!?
[09:47] <willcooke> \o/
[09:48] <darkxst> larsu, yes
[09:48] <xnox> I love Mondays, they are so good and lovely. Not tired at all, happy to wake up early!
[09:48] <didrocks> Monday decisions!
[09:48] <willcooke> larsu, my "office"  looks like a bomb went off in a rubbish dump and then a pig went to live there
[09:48] <larsu> xnox: you're not welcome here.
[09:48] <larsu> xnox: not with this attidude
[09:49] <larsu> *attitude
[09:49] <desrt> who is this xnox guy?
[09:49] <desrt> >:|
[09:51] <larsu> darkxst: I wonder how this can happen with a gtk update - gtk is not involved in drawing those at all, is it?
[09:51] <larsu> (before mutter 3.16, I mean)
[09:51]  * pitti ^5s xnox
[09:52] <xnox> desrt: yo, how do send you glib patches?
[09:52] <desrt> xnox: bugzilla.gnome.org
[09:53] <xnox> desrt: connection is not private
[09:53] <xnox> This server could not prove that it is bugzilla-test.gnome.org; its security certificate is from nagios.gnome.org. This may be caused by a misconfiguration or an attacker intercepting your connection.
[09:53] <desrt> uh oh
[09:53] <xnox> desrt: looks like it has hick-ups
[09:53] <desrt> sounds like some upgrade troubles
[09:53] <larsu> no
[09:53] <larsu> scheduled update
[09:53] <larsu> http://status.gnome.org
[09:54] <desrt> so wait
[09:54] <desrt> bugzilla.gnome.org is maintained as a launchpad.net project?
[09:54] <desrt> this is delicious
[09:55] <larsu> err, what?
[09:55] <desrt> https://launchpad.net/bugzilla.gnome.org
[09:55] <larsu> lol, last commit message: "I think I am merging here, but I don't really know"
[09:56] <desrt> ya..... apparently they ended up using git to coordinate the merge due to some bzr fail
[09:56] <desrt> not sure what their plan will be going forward
[10:00] <desrt> i wonder what this is going to do to my bug downloader
[10:00] <desrt> probably ruin everything :)
[10:16] <darkxst> larsu, I suspect it the theme updates that are the problem
[10:16] <larsu> darkxst: which ones?
[10:16] <darkxst> larsu, adwaita is packaged with gtk+ these days
[10:19] <larsu> darkxst: even the metacity parts?
[10:59] <didrocks1> larsu: I assigned to you the u-c-c task as we discussed on https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5
[11:00] <didrocks1> larsu: seems that robert-ancell still have the indicator-bluetooth task, but I guess he stopped working on it?
[11:00] <didrocks1> seb128: did you chat recently with him on this? ^
[11:06] <larsu> didrocks: I guess he did. I'm fine working on both
[11:06] <didrocks> larsu: doing the paperwork then, thanks man :)
[11:07] <didrocks> sane behavior on pip at last, checking other package managers \o/
[11:07] <didrocks> aquarius would be happy
[11:08] <larsu> maybe he is?
[11:09] <didrocks> larsu: seems not from the email I forwarded to you from a month and half, but he started working on it, I guess he just didn't both with changing the blueprint status
[11:12] <willcooke> Erk.  Click new email in GMail and Google suggest perhaps I'd like to send money to someone with my debit card.
[11:12] <willcooke> How about Noooo
[11:14] <didrocks> thanks willcooke, donations really appreciated :)
[11:15]  * willcooke sends didrocks 1 pence
[11:16] <didrocks> willcooke: that's how all rich long path started I guess \o/
[11:16] <willcooke> :)
[11:18] <Laney> eaten up in currency conversion fees, sorry, better luck next time
[11:24] <willcooke> Just followed up with bjkeyser re: new theme.  It's officially on the list now for 15.10
[11:24] <willcooke> I will follow up again in a couple of months to make sure it's on track
[11:29] <larsu> nice!
[11:30] <Laney> sweet!
[11:30] <Laney> willcooke: did they schedule working on the wallpaper for 15.04 too?
[11:32] <willcooke> Laney, emailed JohnLea_ - I will follow up again once he's back from his sprint
[11:32] <Laney> righto
[11:46]  * Sweet5hark still accepts donations for his director-helicopter.
[11:46] <jpds> Only helicopter I've donated to is: https://londonsairambulance.co.uk/2nd-helicopter
[11:49] <Sweet5hark> jpds: admittedly, thats a much better use of a helicopter.
[11:50] <jpds> Sweet5hark: Did you always have the 5?
[11:50] <Sweet5hark> jpds: nope
[11:52] <Sweet5hark> jpds: sad story actually. Me irrsi was running on a pandaboard and it failed boot through one day. So as a temporary solution I used pidgin from my notebook.
[11:53] <jpds> Sweet5hark: What you need is a raspberry pi 2.
[11:53] <mlankhorst> ah, I use a cloud for that ;-)
[11:53] <Sweet5hark> There is nothing as permanent as a temporary solution.
[11:53] <mlankhorst> though for a while I used pandaboard as my bedtime computer
[11:54] <ogra_> jpds, where is the irissi snap package for that RPi2 ?
[11:54] <ogra_> :)
[11:54] <ogra_> mlankhorst, to cuddle with it before sleeping ?
[11:55] <mlankhorst> no because it drew so little power I could just keep it on, only had to move the mouse to get it to respond
[11:56] <mlankhorst> I only stopped using it because I no longer sleep in that bed :P
[12:34] <seb128> didrocks, no, didn't talk to robert_ancell recently
[12:38] <willcooke> seb128, didrocks  - I'm going to talk to him tonight if you have anything you want me to ask
[12:42] <seb128> willcooke, ask what he's working on/if he still plans to help on the transition to bluez5 (and please mention that larsu is about to pick that up because it has been stucked for a while, to make sure they don't dup work)
[12:46] <willcooke> ack
[12:46] <didrocks> thanks willcooke :)
[12:47] <larsu> willcooke: I'm planning to pick it up when I get back to Berlin (so starting on Wed)
[12:50] <seb128> willcooke, please tell Robert to hand over to larsu if he can/if there is anything to handover
[12:50] <seb128> like status update email, making sure to push what he had
[12:50] <seb128> thanks!
[12:53] <willcooke> kk
[12:55] <didrocks> seb128: I already forwarded some weeks ago to larsu robert's latest branches (which didn't change since)
[12:56] <seb128> didrocks, did you ask robert if he had offline work he didn't push?
[12:56] <seb128> just in case
[12:56] <seb128> doesn't hurt to ask, we never know
[12:58] <didrocks> seb128: asked a week ago, nothing more, but I may have missed his answer
[12:58] <seb128> didrocks, email?
[12:59] <seb128> well, anyway, if willcooke gets a reply that should do
[12:59] <didrocks> seb128: IRC
[12:59] <seb128> we have little overlap with robert
[12:59] <didrocks> yeah
[12:59] <didrocks> seb128: last email was quite clear that he would stop working on this, I was just surprised to see the WI status didn't change though
[12:59] <seb128> didrocks, k, all good then
[12:59] <seb128> didrocks, thanks for tracking it!
[13:00] <didrocks> yw! :)
[13:31] <ichilton> I apt-get install'd ubuntu-gnome-desktop on a standard ubuntu-14.10 install (thinking I could switch between standard ubuntu desktop and gnome) and it's messed up ubuntu desktop - it's now half unity (panel, background, title bars etc) and half gnome (the system panel/tray, the system theme terminal is using etc).
[13:31] <ichilton> How do I fix unity, and can I have both unity and gnome co-exist independantly so I can switch at login?
[13:40] <seb128> ichilton, hey, try #ubuntu for user questions
[13:41] <ichilton> thanks
[14:44] <xclaesse> seb128, does ubuntu's theme on vivid has support for GtkHeaderBar ?
[14:45] <seb128> xclaesse, what do you mean by "support"?
[14:45] <xclaesse> make it look like ubuntu
[14:45] <seb128> not really
[14:45] <seb128> also unity doesn't handle csd well
[14:45] <seb128> so you get no border on the windows using gtkheaderbar as decorations
[14:45] <seb128> they are difficult to resize as well
[14:46] <xclaesse> ok, was trying gedit master in jhbuild on ubuntu 14.04, csd is indeed not well supported
[14:46] <xclaesse> was wondering if on vivid I would get nicer result
[14:46] <xclaesse> http://people.collabora.com/~xclaesse/tmp/gedit.png
[14:46] <larsu> xclaesse: did you try with the Ambiance theme, like I suggested in #gtk?
[14:47] <xclaesse> larsu, that's why I asked here, they don't theme GtkHeaderBar, so that won't gain much
[14:47] <xclaesse> well, on the tabs it will probably
[14:47] <larsu> xclaesse: "they"? I added support for those a while ago. Not sure if it landed in utopic, though
[14:49] <xclaesse> larsu, GTK_THEME=Ambiance doesn't change anything, but I think I have to install the theme in jhbuild, no?
[14:49] <xclaesse> maybe some symlinking could do the trick
[14:50] <larsu> xclaesse: no, just include /usr/share in gedit's XDG_DATA_DIRS
[14:51] <larsu> or run it with GTK_DATA_PREFIX=/usr GTK_THEME=Ambiance
[14:51] <larsu> (iirc)
[14:51] <xclaesse> ah... bah just did ln -s /usr/share/themes/Ambiance/ /opt/gnome/share/themes/
[14:51] <xclaesse> ok indeed that's way smaller now
[14:54] <Laney> hey larsu, do you know anything about GdkVisual? https://git.gnome.org/browse/gtk+/commit/?id=4cf6edda55edb57228e9a1b545dd72c90c3d22af breaks opacity on the 'flash' thing that gnome-screenshot has
[14:56] <Laney> it sets one here https://git.gnome.org/browse/gnome-screenshot/tree/src/cheese-flash.c#n98 and that makes _set_opacity not get called after that gtk+ commit
[14:56] <kenvandine> seb128, don't forget about silo 7, whenever you have time
[15:04] <larsu> Laney: not sure why they'd explicitely set the default visual - it should always be that
[15:04] <larsu> Laney: what happens if you take the set_visual() line out?
[15:05] <Laney> works but sometimes there's another white flash when the fade is finished
[15:05] <larsu> eek
[15:05] <Laney> the comment says something about shadows, could be that
[15:06]  * larsu wonders why setting a visual will cause it not to render shadows
[15:06] <larsu> I think GTK_WINDOW_POPUP should do that
[15:07] <larsu> hm, they set a notification type hint as well
[15:15] <larsu> Laney: seems to work for me?!
[15:15] <larsu> Laney: are you testing on a composited wm?
[15:16] <Laney> i'm using compiz
[15:16] <Laney> are you on a new enough gtk?
[15:16] <seb128> kenvandine, oh, right, thanks for the reminder
[15:16] <kenvandine> seb128, thank you!
[15:16] <larsu> Laney: what's new enough?
[15:16] <larsu> I'm on the one in the ppa
[15:16] <Laney> 3.15.something
[15:16] <Laney> ya, that is
[15:17] <larsu> I see the same problem as you, but commenting the set_visual() line seems to make it work
[15:18] <larsu> ugh, the fallback code is wrong :/
[15:18] <larsu> puts events on the main loop and then unrefs the object
[15:19]  * larsu found out while trying to debug with a longer flahs
[15:19] <larsu> Laney: about to head out now (there's still sun!), but I'll take a look at it
[15:19] <larsu> Laney: is it urgent?
[15:19]  * larsu might sit down in a cafe for a while
[15:19] <Laney> not hugely
[15:20] <Laney> something which breaks with 3.15
[15:20] <seb128> kenvandine, is that rtm7 or vivid7?
[15:20] <Laney> I noticed that the callback is called forever too
[15:20] <Laney> because of some double comparison lolz
[15:20] <larsu> Laney: ok. I'll try to get something until tomorrow when I step out of the plane (afternoon) at the latest
[15:20] <Laney> that's the reason it's displayed forever
[15:20] <Laney> the visual thing just causes it not to fade in
[15:20] <Laney> out*
[15:20] <Laney> in and out?
[15:21] <xclaesse> seb128, was trying gtk master, the file chooser does recursive search on type ahead. Ubuntu thanksfully reverted that in nautilus. Will you consider reverting that in gtk as well please? :D
[15:21] <larsu> Laney: ya, it's all kinds of messed up :/
[15:21] <larsu> Laney: I guess just nobody tested the fallback
[15:21] <seb128> xclaesse, not typeahead anymore?!
[15:21] <larsu> since it's all gnome-shell now
[15:21] <kenvandine> seb128, vivid
[15:21] <seb128> larsu, Laney, ^ btw, might be another issue with new gtk
[15:21] <Laney> I guess so
[15:22] <seb128> kenvandine, anything specific you want me to try?
[15:22] <kenvandine> the bluetooth fixes at least
[15:22] <kenvandine> you know how to test those, i think
[15:22] <seb128> k
[15:22] <seb128> yeah
[15:22] <kenvandine> if you can test the translation fix too :)
[15:22] <seb128> sure
[15:22] <kenvandine> which i think is basically all the fixes :)
[15:22] <xclaesse> seb128, didn't try vivid, but with gtk master in jhbuild when I type ahead in the file chooser it lookup in all sub-dirs
[15:23] <xclaesse> seb128, so I get thousands of matches
[15:23] <xclaesse> seb128, and I cannot simply naviguat my folder hierarchy
[15:23] <larsu> I'll look into it
[15:23] <seb128> xclaesse, do you know if that's a setting we can turn off?
[15:23] <xclaesse> seb128, didn't investigate anything, was about to open an upstream bug to tell it's unusable, but bugzilla is down :p
[15:24] <seb128> hehe
[15:24] <seb128> please do what's it back up
[15:24] <larsu> scheduled maintenance
[15:24] <xclaesse> seb128, but given that's the default on nautilus as well upstrema, I guess it makes sense... in a way...
[15:24] <seb128> yeah
[15:25] <larsu> doesn't seem to be a setting
[15:25] <seb128> https://git.gnome.org/browse/gtk+/commit/?id=de4427304c680c4d111ba92477a30f70befa2d06
[15:26] <seb128> not sure what that setting ^ does but looks like it could be it
[15:26] <seb128> setting in browse rather than search?
[15:27] <xclaesse> seb128, note that ctr+f does bring the old type ahead
[15:27] <larsu> seb128: looks like it, thanks. Maybe we'll need a small patch to make the old behaviour the default
[15:27] <seb128> right
[15:27] <xclaesse> seb128, but IMO the default should be the old way, then ctr+f for a recursive search
[15:27] <seb128> +1
[15:27] <xclaesse> that's how it's made in nautilus on ubuntu
[15:28] <xclaesse> and IMO it makes much more sense
[15:28] <seb128> xclaesse, thanks for pointing it out
[15:28] <xclaesse> you're welcome :)
[15:44] <seb128> kenvandine, bah, sorry, I screwed the translation one, they changed the order of context/text, pushed a fix for that to https://code.launchpad.net/~seb128/ubuntu-system-settings/security-use-ctr/+merge/248771
[15:44] <seb128> kenvandine, I tested with that fix, should be fix, bluetooth, etc work as expected
[15:45] <kenvandine> ok, i'll rebuild
[15:45] <seb128> kenvandine, thanks, and sorry about that
[15:45] <kenvandine> np
[15:45] <seb128> kenvandine, https://code.launchpad.net/~seb128/ubuntu-system-settings/categories-no-effect/+merge/248272 should also be trivial if you want one more
[15:46] <kenvandine> i'll do that one separately... already got 5 branches in this silo
[15:46] <seb128> but if not that can be in the next round
[15:46] <kenvandine> and i already clicked build :)
[15:46] <seb128> k
[15:46] <seb128> wfm
[16:12] <Laney> test failed email → click link → "oh look, transient failure, let's retry" → connect to vpn → click private link → "Started by user Martin Pitt"
[16:12] <Laney> this guy is too fast :-)
[16:13] <Laney> "Started 1.8 sec ago", ha!
[16:15] <didrocks> he is! :)
[16:27] <seb128> cyphermox, hey
[16:27] <cyphermox> seb128: hey
[16:28] <seb128> cyphermox, have some minutes to talk settings/bt?
[16:28] <cyphermox> sure
[16:28] <seb128> cyphermox, remember https://code.launchpad.net/~mathieu-tl/ubuntu-system-settings/unbreak-hid/+merge/243592 ?
[16:28] <seb128> cyphermox, I'm pondering adding that function back, wanted your opinion first
[16:29] <cyphermox> hum, what for?
[16:29] <seb128> cyphermox, currently it lists all device, but if you try to pair with i.e a laptop, it's going to hit the
[16:29] <seb128>     default:
[16:29] <seb128>         qWarning() << "Nothing to connect: Unsupported device type.";
[16:29] <seb128>         return;
[16:29] <seb128> case
[16:30] <seb128> which means you click on "connect" in the ui and it brings you back to the device list
[16:30] <seb128> without any feedback on what happened and why
[16:30] <cyphermox> hum, there is that
[16:30] <seb128> that's not good user experience :-)
[16:30] <cyphermox> but perhaps a better idea would be to grey the connect button in that case
[16:30] <cyphermox> rather than not showing the devices at all
[16:30] <seb128> well, that's what that the code you dropped was doing
[16:30] <seb128> oh
[16:30] <seb128> it was showing the device by disabled
[16:31] <seb128> sure, we could move to disable the connect instead
[16:31] <cyphermox> right
[16:31] <seb128> I should maybe first try what happens if I add the computer type to the case
[16:31] <seb128> maybe pairing a computer works
[16:32] <cyphermox> hmm, not sure
[16:32] <seb128> even if we can't do much once it's paired
[16:32] <cyphermox> even if it did pair
[16:32] <cyphermox> yeah ;)
[16:32] <seb128> e.g no file transfert or anything
[16:32] <seb128> hum
[16:32] <cyphermox> there's no one good answer for this, there's a couple of ways we can handle these devices we "don't support yet"
[16:32] <seb128> if I pair my laptop to my android phone I can use it to play music
[16:33] <cyphermox> yeah
[16:36] <seb128> cyphermox, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1419866
[16:37] <seb128> cyphermox, opened that and assigned to mpt
[16:37] <seb128> just as a fyi
[16:37] <seb128> cyphermox, thanks for the feedback :-)
[16:37] <cyphermox> argh
[16:38] <cyphermox> so yeah, we really do need mpt or someone from design to make a decision :)
[16:39] <seb128> cyphermox, indeed
[16:41] <seb128> cyphermox, also my krillin advertize itself as a computer on bt, is that right?
[16:41] <seb128> cyphermox, my android phone advertize itself as a phone
[16:41] <cyphermox> yeah
[16:42] <cyphermox> we need to fix up bluez to split out the config in two separate packages, make one for a "I'm a phone" and another one for "I'm a computer.
[16:42] <seb128> k
[16:42] <cyphermox> otoh, much of that will be done automatically once we're on bluez 5
[16:43] <cyphermox> by way of systemd and some updated system code
[16:43] <seb128> cyphermox, oh, also it seems that the device is always discoverable, where the spec states it should only be when you are on the bluetooth screen
[16:43] <seb128> is that known?
[16:43] <cyphermox> it shouldn't be always discoverable no
[16:43] <seb128> and where should it be reported?
[16:43] <cyphermox> that was working fine
[16:43] <cyphermox> mark it against u-s-s, bluez by itself doesn't usually put devices discoverable
[16:43] <cyphermox> but I wonder if that might be different based on the bluetooth driver
[16:45] <seb128> cyphermox, not a settings issues, I just rebooted my device
[16:45] <seb128> it's discoverable as soon as it boot
[16:45] <seb128> I didn't use/unlock it yet
[16:45] <cyphermox> yuck
[16:45] <seb128> can't be setting since that never ran
[16:45] <cyphermox> heh, bluez then
[16:45] <seb128> thanks
[16:45] <cyphermox> but I'm pretty sure we had tried this and it was working properly
[16:45] <seb128> that one might be an important issue
[16:46] <cyphermox> that's why it seems like it's possibly a driver issue
[16:46] <seb128> isn't that sort of a security problem?
[16:46] <seb128> also use power?
[16:46] <cyphermox> well, yes
[16:46] <cyphermox> it's bad
[16:46] <cyphermox> someone will need to figure out why that is
[16:46] <cyphermox> were you testing this on mako?
[16:48] <seb128> cyphermox, no, bq
[16:48] <seb128> cyphermox, who do you recommend pinging about the issue?
[16:49] <cyphermox> hum, you already pinged them I guess
[16:50] <seb128> cyphermox, if them is you :-)
[16:50] <cyphermox> yeah
[16:50] <seb128> I didn't mention it out of here, well out of the bug
[16:50] <cyphermox> maybe let ChickenCutlass know too. I see he doesn't seem to be here
[16:51] <cyphermox> I'll see if I get the same thing on my mako, at least so I know whether bluez is really busted of if it's a driver thing like I really hope it is
[16:54] <cyphermox> boo, it seems good here on mako :/
[16:54] <cyphermox> at least, according to bluez-test-adapter
[16:55] <seb128> what is that command supposed to say?
[16:56] <seb128> $ bluez-test-adapter discovering
[16:56] <seb128> 0
[16:56] <seb128> on the bq
[16:57] <cyphermox> hum
[16:57] <seb128> that seems to always return 0, on desktop as well
[16:57] <cyphermox> yes the device still shows up elsewhere?
[16:57] <seb128> visibility turned off or on
[16:57] <seb128> yes
[16:57] <seb128> my laptop lists it
[16:57] <cyphermox> well, it behaves correctly on my mako
[16:57] <cyphermox> 1 when u-s-s bt page is open, 0 otherwise
[16:58] <seb128> well, 0 here
[16:58] <seb128> but the device is listed by other computers
[16:58] <cyphermox> right
[16:58] <seb128> so that flag is not respected
[16:58] <seb128> driver issue I guess?
[16:58] <cyphermox> possibly, but I'm not done testing :)
[16:59] <cyphermox> gah
[16:59] <cyphermox> still getting the right behavior on mako :/
[17:00] <seb128> cyphermox, thanks for testing
[17:00] <cyphermox> this is not good, I don't like driver issues like this
[17:01] <cyphermox> the android drivers are already busted enough as it is that we don't need to find more issues ;)
[17:01] <seb128> cyphermox, is "bluez-test-adapter discovering" supposing to return 1 when visibility = true?
[17:02] <seb128> cyphermox, because on my vivid desktop it always returns 0, even when I toggle the visible switch in the indicator or gnome ui
[17:02] <cyphermox> no
[17:02] <cyphermox> bluez-test-adapter discoverable
[17:02] <seb128> oh
[17:03] <seb128> cyphermox, that returns 1 on krillin
[17:03] <seb128> without using settings
[17:03] <cyphermox> discovering is for whether you're currently running a scan, but that part is more less simple
[17:03] <cyphermox> yeah, I believe you
[17:04] <pmcgowan> seb128, I get 0 on krillin right now
[17:04] <seb128> cyphermox, "disoverable off" works
[17:04] <seb128> pmcgowan, what happens if you open the settings bluetooth page and close settings?
[17:05] <cyphermox> seb128: ok
[17:05] <pmcgowan> seb128, seems to work right, 1 when on page and 0 otherwise
[17:05] <seb128> pmcgowan, hum, k, I wonder what is wrong on my krillin
[17:05] <pmcgowan> oh let me do what you said
[17:05] <seb128> pmcgowan, do you run rtm or vivid?
[17:06] <pmcgowan> seb128, aha if you close settings while on the page it stays on
[17:06] <seb128> k
[17:06] <kenvandine> seb128, silo 7 is rebuilt, can you mark it as tested on the spreadsheet?
[17:06] <seb128> cyphermox, is something storing the state accross reboots?
[17:06] <cyphermox> seb128: it's not supposed to be saved
[17:06] <seb128> seems to be
[17:06] <cyphermox> hum, I was on vivid though
[17:07] <seb128> pmcgowan, ^ I guess that's the issue maybe?
[17:07] <seb128> pmcgowan, like if you do that it stays to 1
[17:07] <seb128> and that persists over reboot for me
[17:07] <pmcgowan> seb128, let me reboot and see what it is
[17:07] <cyphermox> seb128: you are right, it's saved in /var/lib/bluetooth/<address>/config
[17:07] <seb128> pmcgowan, ^
[17:08] <pmcgowan> seb128, confirmed both, stays set over reboot and in the config file
[17:09] <seb128> cyphermox, pmcgowan, commented on the bug
[17:09] <cyphermox> seb128: I wonder if you had a bad crash while the bt window was open?
[17:10] <seb128> cyphermox, no, I just worked on that panel and it's easier to swipe settings out and restart
[17:10] <seb128> rather than exit the panel and close it
[17:10] <seb128> e.g I use the switched and close it from there
[17:10] <seb128> switcher
[17:10] <cyphermox> hum
[17:13] <seb128> kenvandine, done
[17:14] <kenvandine> seb128, thx
[17:15] <seb128> need to drop offline for a bit, back in less than half an hour
[18:15] <didrocks> and with all those tests passing, have a good evening everyone!
[18:30] <willcooke> ahahah!  I have learned another new C thing.  "a++" increments after the action, where as ++a does it first.  So my strings were getting null terminated 1 character too long
[18:41] <JanC> that's very basic C knowledge  :)
[18:43] <willcooke> I am very basic
[18:47] <ogra_> goto 10
[18:48] <willcooke> Now your talking my language
[18:48] <ogra_> :)
[18:48] <willcooke> except it should all be in caps
[18:49] <mlankhorst> Can we have COBOL now? :P
[18:50] <willcooke> :D
[19:34] <willcooke> morning robert_ancell
[19:34] <robert_ancell> willcooke, hi
[19:40] <seb128> hey robert_ancell, how are you?
[19:40] <robert_ancell> seb128, hi good. otp at the moment
[19:40] <seb128> robert_ancell, just saying hello, I didn't see you for a while! we missed you in Brussels
[19:41] <robert_ancell> seb128, yeah, me too
[20:22] <willcooke> g'night
[20:22]  * willcooke -> EOD
[20:22] <robert_ancell> seb128, looked like you guys had fun!
[20:22] <robert_ancell> seb128, and you've grown quite a beard there :)
[20:24] <seb128> robert_ancell, indeed! got the beard a bit shorter after coming back from Brussels though, it was starting getting a bit too much :-)
[20:26] <chrisccoulson> seb128, are you going for the hobo look with the beard?
[20:26]  * seb128 slaps chrisccoulson
[20:26] <chrisccoulson> :)
[20:28] <robert_ancell> chrisccoulson, hobo-chic
[20:28] <chrisccoulson> heh