=== brainwash_ is now known as brainwash
[07:16] <pitti> Good morning
[07:16] <darkxst> hey pitti
[07:21] <pitti> hey darkxst
[07:38] <ochosi> tedg: hi there! quickly wanted to ask what the rationale was behind dropping sync notification on scroll in indicator-sound. http://bazaar.launchpad.net/~indicator-applet-developers/indicator-sound/trunk.15.04/revision/462.4.2
[07:58] <seb128> good morning desktopers
[07:58] <seb128> hey pitti
[08:55] <willcooke> morning
[08:56] <seb128> hey willcooke
[08:57] <happyaron> morning willcooke
[09:03] <Laney> hey hey
[09:05] <willcooke> Got snow Laney ?
[09:05] <Laney> little dusting, therefore the world's probably ended
[09:06] <willcooke> :)
[09:09] <darkxst> Laney, my world starts when it snows ;) been cooler this week but summer here is pretty brutal ;(
[09:10] <Laney> darkxst: come up to northern europe, it's the place for you
[09:10] <darkxst> Laney, I plan to eventually!
[09:16] <Noskcaj> darkxst, Does melbourne get any snow?
[09:21] <darkxst> Noskcaj, no, I have to drive 4-5 hours to get to the mountains where the snow is!
[09:21] <darkxst> (Mt Hotham)
[09:23] <Noskcaj> way closer than me
[11:15] <darkxst> seb128, hey did you get to look at my gnome-session wayland split?
[11:37] <Laney> 4G \m/
=== MacSlow is now known as MacSlow|lunch
=== alan_g is now known as alan_g|lunch
[12:49] <seb128> darkxst, hey, not yet no, is that blocking things?
=== MacSlow|lunch is now known as MacSlow
=== alan_g|lunch is now known as alan_g
[13:48] <qengho> willcooke: Your Twitter name is good.
[13:51] <willcooke> qengho, hehe!  Thanks
[13:51] <larsu> is it willcooke?
[13:52] <willcooke> lol
[13:52] <willcooke> for once, it is not
[14:02] <tedg> ochosi, The biggest reason was that we couldn't find any use-case for it. Do you have one?
[14:03] <seb128> tedg, hey
[14:03] <tedg> Good morning seb128
[14:03] <seb128> tedg, does it mean that mousewheel scrolling over the indicator doesn't displays bubbles anymore?
[14:03] <tedg> seb128, No, it should mean that it always does. There was an option to disable.
[14:03] <tedg> seb128, But no UI for it and set to show by default.
[14:03] <seb128> oh, ok
[14:04] <seb128> k, wfm then
[14:06] <seb128> tedg, btw https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416233 might be a regression from your recent changes
[14:06] <ubot5> Launchpad bug 1416233 in indicator-sound (Ubuntu) "Sound indicator notification shows each time the a sound starts or stops" [Undecided,New]
[14:08] <tedg> Yeah, I agree, it's kinda the design though.
[14:08] <seb128> tedg, can you comment saying that?
[14:08] <tedg> Yup
[14:08] <seb128> thanks
[14:08] <tedg> Looking up the design :-)
[14:08] <seb128> :-)
[14:12] <tedg> seb128, Actually seems I was wrong, there's a little sentence at the end I missed covering this :-/
[14:16] <seb128> tedg, k, please fix it then :-)
[14:16] <tedg> Heh, yeah.
[14:43] <rsalveti> tedg: I can't control music playback anymore from the indicator-sound (play/pause/back/forward) on vivid
[14:43] <rsalveti> is that expected?
[14:44] <rsalveti> on desktop
[14:44] <tedg> rsalveti, Could you before?
[14:44] <tedg> Oh, on desktop.
[14:44] <rsalveti> tedg: yup
[14:44] <tedg> rsalveti, Definitely not expected, let me try.
[14:45] <seb128> rsalveti, you mean that the controls are missing in the menu?
[14:45] <rsalveti> seb128: yup
[14:46] <seb128> rsalveti, want to try the deb from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-006 and confirm if it fixes it for you?
[14:46] <seb128> tedg, ^
[14:46] <rsalveti> sure
[14:46] <seb128> thanks
[14:46] <tedg> Oh, okay. WFM with Rhythmbox.
[14:47] <tedg> Well, I've got Utopic base but the indicator-sound trunk.
[14:47] <seb128> tedg, yeah, the issue is due to the new gtk/theming
[14:47] <tedg> Ah, I see.
[14:47] <seb128> so you wouldn't get it on utopic
[14:48] <tedg> Need to upgrade to Vivid. Used to always upgrade the week before UDS. Still haven't got a new routine.
[14:48] <rsalveti> seb128: nops
[14:48] <rsalveti> still broken
[14:49] <seb128> rsalveti, what did you restart?
[14:49] <rsalveti> seb128: just indicator-sound, do I need to restart the entire unity?
[14:49] <seb128> rsalveti, unity-panel-service
[14:49] <seb128> that's the frontend side
[14:49] <seb128> the indicator is just backend
[14:50] <rsalveti> seb128: got it
[14:50] <rsalveti> seb128: awesome, can see them again :-)
[14:50] <rsalveti> and seems to be working fine as well
[14:50] <seb128> rsalveti, great, thanks for confirming ;-)
[14:53] <ochosi> tedg: dunno, we used that setting in xubuntu and it seemed to provide better visual feedback of the scroll-event than just the small icon in the panel changing
[14:54] <tedg> ochosi, I think that the default is to provide the notification, so I think you guys were just setting it again.
[14:55] <ochosi> a-ha
[14:55] <tedg> ochosi, It was only used to disable the notification. (non-default)
[14:55] <ochosi> so wait, that commit is not dropping the notification then?
[14:55] <tedg> ochosi, No, it is not. In fact I was too aggressive with the notification, got to scale it back a little this morning :-)
[14:55] <ochosi> oh ok then :)
[14:56] <ochosi> if the notification sticks around, there's nothing to worry about then
[14:56] <ochosi> thanks for the heads up!
[15:14] <mitya57> Laney: notify-osd itself installs some icons into /usr/share/notify-osd/icons/hicolor/, why not use the same path?
[15:14] <mitya57> That will also work for users whose icon theme does not inherit from Humanity
=== ochosi is now known as ochsoi
=== ochsoi is now known as ochosi
[15:24] <larsu> mitya57: the same path as whaT?
[15:25] <Laney> mitya57: tedious file conflicts if you do that
[15:25] <Laney> can't quite be bothered to sort it out
[15:25] <larsu> why don't we just add the icons to hicolor?
[15:25] <larsu> or are they very notify-osd specific?
[15:26] <larsu> bah, s/hicolor/Humanity
[15:26] <Laney> /usr/share/notify-osd/icons/*
[15:27] <Laney> they probably only look good in notify-osd
[15:28] <larsu> okay, makes sense then
[15:28] <ochosi> hey larsu
[15:28] <larsu> hi
[15:29] <ochosi> i recently noticed an oddity/bug in gtk3.14, so i thought i'd quickly ask you whether it was possible that it's a problem in ubuntu only before putting a bugreport upstream...
[15:30] <ochosi> the gtkfontchooser's preview-text is generally an empty string by default, as opposed to what it should be: https://developer.gnome.org/gtk3/stable/GtkFontChooser.html#GtkFontChooser--preview-text
[15:30] <ochosi> you can see that e.g. in gedit
[15:30] <ochosi> i noticed it with a different app i'm maintaining
[15:31] <ochosi> explicitely setting some preview-text in the code works though
[15:34] <Laney> ochosi: what does python -c 'from gi.repository import Gtk; print Gtk.FontChooserDialog().get_property("preview-text")' give you?
[15:34] <Laney> seems right here
[15:34] <larsu> ochosi: I see "The quick brown fox..." as preview text in gedit
[15:34] <ochosi> weird
[15:34] <ochosi> could this be a xubuntu-only issue then?
[15:34] <ochosi> Laney: that outputs the expected pangram
[15:35] <larsu> seems correct, then
[15:35] <ochosi> not that this is spectacular or anything, but just so you know i'm not messing with you, this is how it looks in xubuntu: http://i.imgur.com/W5U1mDP.png
[15:35] <ochosi> and i see the same behavior with different gtk3 apps
[15:35] <ochosi> (gedit, parole)
[15:36] <larsu> ochosi: maybe a theme issue? Is the text set on the property?
[15:36] <larsu> ochosi: (check with inspector)
[15:36] <ochosi> the text isn't set
[15:36] <ochosi> wait, the theme can modify that property?
[15:37] <ochosi> lemme check with ambiance then...
[15:37] <larsu> ochosi: no, but the theme can make the text invisible
[15:37] <larsu> just and idea...
[15:37] <ochosi> ah sure
[15:37] <ochosi> yeah, no, that's not it
[15:37] <ochosi> it really is set to ""
[15:38] <seb128> gedit looks like your screenshot for me on unity
[15:38] <larsu> can you debug gedit with a breakpoint on gtk_font_chooser_set_preview_text?
[15:38] <seb128> is it supposed to contain text?
[15:38] <larsu> seb128: yes
[15:38] <larsu> ochosi: hm, gtkfontchooser uses pango_language_get_sample_string()
[15:39] <larsu> maybe that only works in some languages?
[15:39] <ochosi> i'm using the default en_US locale
[15:43] <ochosi> larsu: what/how exactly should i debug?
[15:43] <ochosi> i mean i have parole's code here and i've inspected it quite a bit, it just adds a gtkfontbutton so everything is handled by gtk itself
[16:01] <larsu> ochosi: is gtk_font_chooser_set_preview_text() called?
[16:01] <larsu> and if so, with which string?
[16:01] <ochosi> in parole you mean?
[16:02] <ochosi> aha
[16:02] <larsu> or gedit
[16:02] <ochosi> well in parole it isn't explicitely called, that i know for sure
[16:02] <larsu> doesn't matter if if happens in both apps
[16:02] <ochosi> but i presume by debug you meant checking whether it happens implicitely?
[16:04] <larsu> yes
[16:04] <ochosi> tbh i've never done that :]
[16:05] <seb128> is gedit supposed to set a preview text?
[16:05] <larsu> ah don't worry about that then
[16:06] <larsu> seb128: gtk sets a default if gedit doesn't override it
[16:06] <larsu> seb128: and it doesn't seem to, because I see it
[16:06] <ochosi> larsu: what's your locale btw?
[16:06] <larsu> ochosi: en_US
[16:06] <seb128> ochosi, larsu, https://git.gnome.org/browse/gedit/commit/?id=af6d3204ec4a71efff8521f2df7ffb69960279f4
[16:07] <seb128> larsu, running your new gtk by chance?
[16:07] <ochosi> a-ha
[16:07] <ochosi> that is interesting
[16:07] <larsu> seb128: and the new gedit ;)
[16:07] <seb128> larsu, that's what I meant
[16:07] <seb128> new gedit :-)
[16:07] <seb128> sorry
[16:07] <ochosi> i'll quickly try that with parole, i presume adding that line gives you the preview text..?
[16:07] <larsu> I figured
[16:07] <larsu> ochosi: no, it removes it
[16:08] <larsu> ochosi: grep for preview.text in your source and ui files
[16:08] <ochosi> alright, i'll check whether parole sets that
[16:09] <ochosi> darn, there you go...
[16:09] <ochosi> i guess that was automatically set by glade-gtk3 or something
[16:09] <ochosi> thanks a lot larsu!
[16:10] <larsu> ochosi: probably the same that happened for gedit. Thank seb128 -- he found the issue!
[16:10]  * larsu hugs seb128
[16:10] <larsu> too bad you won't nbe here until sunday
[16:10] <ochosi> indeed, thanks a bunch seb128!
[16:11]  * seb128 hugs larsu back
[16:11] <seb128> yw!
[16:14]  * Laney is continent-side
[16:14] <ari-tczew> larsu: are you going to prepare gedit 3.14 for vivid?
[16:15] <Laney> need to make sure to have turned off data roaming when we get into .be
[16:45] <qengho> willcooke: about email, that bug report probably won't influence to different conclusion, but you should know of it.
[16:46]  * willcooke reads
[16:48] <willcooke> ok, things get a bit baffling towards the end of that report
[16:49] <willcooke> qengho, so is that a fix in the works then?
[16:53] <qengho> willcooke: not soon. Hard to say, but not this release.
[16:53] <willcooke> qengho, oki
[16:54] <willcooke> qengho, so options available to us?  Disable HiDPI?
[16:55] <seb128> willcooke, are the shifted menu worth that unreadably small ui elements?
[16:56] <willcooke> seb128, yeah, plus AIUI you cant click on the menu items either
[16:57] <willcooke> oh
[16:57] <willcooke> sorry misread
[16:57] <willcooke> I dont think the menu items are clickable - and if that is the case, then yes - I think it probably is
[16:57] <willcooke> what do you reckon?
[16:58] <willcooke> Has anyone got a HiDPI screen we can test it on?
[16:59] <seb128> do we have a bug report on launchpad with details?
[16:59] <seb128> willcooke, just run "chromium-browser --force-device-scale-factor=2" to test
[17:00] <seb128> you can use the menus
[17:00] <seb128> at least the top right main one
[17:00] <qengho> willcooke: Menu-items are clickable, but hover-to-expand submenus doesn't work very well. Coordiate mis-map on that part.
[17:00] <qengho> But in some weird relative way.
[17:01] <seb128> yeah, it's not really usable
[17:01] <seb128> if you try to open a submenu it pops over the main menu and open/close in turns
[17:01] <willcooke> heh
[17:02] <willcooke> Stephane is looking up the LP bug...
[17:02] <seb128> but yeah, looks like maybe we should disable hidpi until that it resolved
[17:02] <willcooke> I find it strange that upstream aren't all over this bug though
[17:02] <willcooke> I would have expected the new shiny to get some love :)
[17:05] <qengho> willcooke: endless refactoring and breaking all my patches has a higher priority.
[17:06] <willcooke> ha!
[17:12] <willcooke> oooohh
[17:12] <willcooke> who was it that liked steak tartare?
[17:12] <seb128> the frenchs
[17:13] <willcooke> hehehe
[17:21] <mlankhorst> how do people get from FOSDEM to the hotel?
[17:22] <willcooke> looks like quite a long way. taxi it
[17:37] <mlankhorst> shrug, I go by car :p
[17:37] <mlankhorst> though 5 km is fun to walk too
[17:37] <willcooke> On a sunny day I would agree
[17:38] <willcooke> < 15 degrees - no way :D
[17:38] <mlankhorst> pfft
[17:38] <mlankhorst> I cleaned up some horse feces today in the snow, though it was still 5°c or so :p
[17:44] <willcooke> The things you guys do for fun....
[17:53] <mlankhorst> oh definitely!
[17:54] <mlankhorst> https://www.youtube.com/watch?v=YyvN8eDS3lY
[17:55] <willcooke> O_o
[17:57] <mlankhorst> sometimes I do normal things too
[17:57] <willcooke> haha
[17:57] <willcooke> right - EOW
[17:57] <willcooke> See you next week
[17:57] <willcooke> o/
[17:58] <mlankhorst> bb
=== alan_g is now known as alan_g|EOW
=== qengho is now known as CardinalFang
=== CardinalFang is now known as qengho
[18:55] <seb128> kenvandine, could be useful to bump the indicator-power upstream version, more reliable than depending on a daily snapshot date
[18:55] <seb128> especially if you start backporting to rtm
[19:00] <kenvandine> ok
[19:00] <kenvandine> charles, ^^
[19:00] <kenvandine> can you bump that in your branches and i'll match it in my branches?