[00:01] <andrzejr> checked on 13.10 Greybird from master - still the same
[00:01] <ochosi> so it's about padding in between the indicators, right?
[00:02] <ochosi> (i'll take another look when i'm less tired)
[00:02] <andrzejr> internal padding of GtkButtons in the indicator plugin
[00:02] <ochosi> i tried to control that with margin (which should do what we want), but that didn't work the last time i tried it
[00:03] <andrzejr> stock 13.10 Greybird has correct padding (and wrong bg-color), the one from git has correct bg-color and zero padding.
[00:03] <andrzejr> or margin - not sure about naming
[00:06] <ochosi> i removed all special theming that i added (which basically gives me greybird from 13.10) and it still doesn't look any different
[00:06] <ochosi> the buttons are all next to each other
[00:08] <ochosi> i
[00:08] <ochosi> 'll do a screenshot compilation to illustrate
[00:12] <ochosi> andrzejr: http://imagebin.org/270090
[00:12] <ochosi> left is the panel with color-changes applied, right is the panel without any special theming applied
[00:12] <ochosi> ali1234: do you also get the spacing issue that andrzejr described? ^
[00:14] <andrzejr> I removed /* workaround to fix size of indicator-icons */ (and restarted the panel) - the size is now fine
[00:14] <ochosi> ok
[00:14] <ochosi> i'll change that in git too
[00:15] <andrzejr> but now the border around hovered button is brighter than for Gtk2 plugins
[00:15] <ochosi> i know
[00:15] <ochosi> i've just started to tinker with that
[00:16] <ochosi> i'll take a look at it on the weekend
[00:16] <andrzejr> Another issue - labels are much darker than in gtk2 plugins
[00:16] <ochosi> yeah, colors aren't 100% ok yet
[00:16] <ochosi> satya pushed a commit to git without consulting me, changing everything to symbolic colors
[00:16] <ochosi> which is fine, but it means i have to adjust them again
[00:18] <andrzejr> ttyl, good night
[00:19] <ochosi> night!
[00:22] <Unit193> Good night.
[03:38] <ali1234> ochosi: i'm not 100% sure but i think maybe i do
[03:38] <ali1234> all the other buttons on the panel have a slightly different colour border but the indicators don't - they are just solid
[03:39] <ali1234> with greybird git only that is
[03:40] <ali1234> probably an old version too
[05:03] <Unit193> Bug #1222021 hit, but not me.
[05:03] <ubottu> bug 1222021 in xfce4-power-manager (Ubuntu) "Laptop sleeps when lid is closed, regardless of Power Manager Settings." [Undecided,New] https://launchpad.net/bugs/1222021
[06:13] <XRS1> Confirmed Bug #1222021 in Xubuntu 13.10 Beta 1 x64: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1222021
[06:13] <ubottu> Launchpad bug 1222021 in xfce4-power-manager (Ubuntu) "Laptop sleeps when lid is closed, regardless of Power Manager Settings." [Undecided,Confirmed]
[09:52] <ali1234> ochosi: the bug with blueman-applet not showing any menus is not specific to xfce (or blueman): https://bugs.launchpad.net/ubuntu/+source/glipper/+bug/1203888/
[09:52] <ubottu> Launchpad bug 1203888 in glipper (Ubuntu) "appindicator doesn't work in Saucy" [Undecided,Confirmed]
[09:53] <ali1234> bluetooth-indicator (which is completely different) is broken because com.canonical.indicator.switch menu model is not available
[09:59] <ali1234> actually it looks like python-appindicator is broken
[15:20] <knome> pleia2, i will. there hasn't been any activity since i filed though
[17:49] <ali1234> ok, i tested each and every indicator bug and all of them are not specific to xfce
[18:01] <ali1234> i suspect this child-added bug is the reason pidgin stuff isn't showing in the message indicator
[18:04] <ali1234> it's broken in regular unity as well anyway
[18:26] <andrzejr> ali1234, I've been trying to nail down that scrolling bug.
[18:26] <ali1234> you know that the sound menu doesn't work in unity either right?
[18:26] <ali1234> i just tested it
[18:26] <andrzejr> WrapperPlug (GtkPlug) still gets the events but the IndicatorPlugin object doesn't
[18:27] <ali1234> actually all the remaining bugs also affect unity
[18:27] <andrzejr> so maybe there are two bugs
[18:27] <andrzejr> The problem with my scroll event handler is that it doesn't even receive events.
[18:28] <ali1234> the one i made most progress on is this one: https://bugs.launchpad.net/ubuntu/+source/glipper/+bug/1203888/
[18:28] <ubottu> Launchpad bug 1203888 in libappindicator (Ubuntu) "appindicator doesn't work in Saucy" [Undecided,Confirmed]
[18:28] <ali1234> but neither libappindicator nor glib contains the string "child-added" so i reached a dead end
[18:29] <ali1234> i asked a question the other day on #gtk
[18:29] <ali1234> is it allowed for a gtk widget to have more than one parent? ie to be added to more than one container?
[18:31] <ali1234> if we have two indicator plugins, does each get the same GtkMenu or is it a copy?
[18:33] <ali1234> i suspect this stuff is all related - events aren't coming through when menu items are added, and scroll events aren't being passed in the opposite direction
[18:37] <ochosi> hey folks
[18:37] <ochosi> man, so much backlog
[18:37]  * ochosi starts reading
[18:39] <ochosi> how weird that there are such severe indicator bugs that also affect unity...
[18:41] <ali1234> it got rewritten again... it's to be expected unfortunately
[18:42] <ali1234> http://paste.ubuntu.com/6075999/ is the current status
[18:43] <brainwash> indicators really seem to cause some trouble
[18:44] <ochosi> ali1234: you could post that in a blueprint or somewhere so that people see it
[18:44] <ochosi> or even on the ML
[18:44] <ochosi> brb (gotta test greeter-patch)
[18:44] <ali1234> actually i have it as a draft ready to send to the ML
[18:44] <ali1234> i don't know how to do blueprints
[18:47] <ochosi> starting with the ML is fine i guess
[18:52] <ali1234> sent
[18:54] <ochosi> cool, thanks!
[18:55] <ochosi> also thanks for the orion-patch and the script
[18:55] <ochosi> will take a look at it as soon as i can
[18:55] <ochosi> sounds extremely useful
[18:55] <ochosi> bbl
[19:56] <Noskcaj> The latest xubuntu-icon-theme is failing to update
[20:05] <brainwash> Noskcaj: https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1222156
[20:05] <ubottu> Launchpad bug 1222156 in xubuntu-artwork (Ubuntu) "unable to open '/usr/share/icons/elementary-xfce/actions/16/zoom-fit-best.png.dpkg-new': No such file or directory" [Undecided,Confirmed]
[20:06] <Noskcaj> brainwash, thanks
[20:06] <brainwash> I haven't updated this particular package yet
[20:08] <brainwash> Noskcaj: so you are encountering the exact same problem?
[20:08] <elfy> I did
[20:08] <Noskcaj> brainwash, yep
[20:12] <elfy> changelog shows - fix missing 16px dir for elementary-xfce-darker 
[20:12] <brainwash> hopefully the package gets fixed fast, so I can finally enjoy properly sized close buttons on the tabs in firefox :)
[20:12] <elfy> ochosi: ^^
[20:12] <brainwash> yeah
[20:12] <brainwash> remember me talking about the big close buttons in firefox? :D
[20:13] <elfy> vaguely
[20:14] <Unit193> Yep.
[20:14] <elfy> not my fault I'm always vague :(
[20:15] <brainwash> the bug report about the missing 
[20:15] <brainwash> systemd-shim package does not get much attention though
[20:16] <elfy> wait till it's not the weekend ;)
[21:00] <drc> Does anyone know if the lack of "app competion" in the New Item feature of Main Menu is 1) an oversight, 2) a bug, or 3) a brand spanking New Feature which we are sure to love and enjoy for the next LTS cycle ?
[21:01] <elfy> not even sure what you're talking about?
[21:01] <drc> sorry...in 1310b1
[21:02] <elfy> what's app competition?
[21:03] <drc> elfy: It's sort of a tab completion (without the <tab> In MM, when you chose New Item (to add a new menu item) in 1304 (and before) typing in, say, "File" (for File Manager) would bring up several different instances of File Manager/Thunar, etc.
[21:03] <drc> Now...not so much :)
[21:04] <elfy> in alacarte?
[21:04] <drc> And when you picked one (say, exo-open) it would add the command/icon/etc to the New Item for you.
[21:05] <drc> well, I assume it's alacarte...it's labeled Manin Menu in the Settings manager.
[21:05] <elfy> I've no idea - never seen it before to be honest so wouldn't know it was missing 
[21:05] <drc> Main Menu...typing in 13.10 LiveCD wirh rediculously small fonts.
[21:05] <elfy> yea that's alacarte
[21:07] <elfy> I'm either not understanding what you think is missing or never ever saw it or used it so don't know :)
[21:08] <drc> OK, thanks :(
[21:09] <elfy> sorry 
[21:16] <ali1234> screenshot?
[21:16] <drc> elfy: Who usually handles things like MM (so know who to ask) ?
[21:17] <ali1234> you mean in eg the Name field?
[21:17] <drc> ali1234: Are you talking to me?
[21:17] <elfy> drc: what is MM >
[21:17] <ali1234> yes
[21:17] <ali1234> elfy: alacarte for sure
[21:18] <drc> sorry, I <was> in 1310 and then reboot back to 13.04
[21:18] <drc> let me get a screenshot...wait
[21:18] <ali1234> alacarte isn't really a xfce app, it's from old gnome/old ubuntu
[21:18] <ali1234> and they don't use it any more, so it's kind of ... not really maintained
[21:18] <elfy> drc: I'd assume that we'd just use whatever gets done by others for alacarted
[21:19] <ali1234> the other day someone suggested a new menu editor, but i forgot what it was called
[21:19] <elfy> probably lubuntu one 
[21:20] <knome> menulibre?
[21:20] <elfy> that'll be the one
[21:20] <knome> elfy, that's not a "lubuntu one", that's created by bluesabre ;)
[21:20] <elfy> which isn't the lubuntu one - I'm getting confused with their synaptic
[21:21] <knome> didn't they have their own
[21:21] <ali1234> yeah that was it
[21:21] <elfy> knome: yea - I should learn to touchtype too so I don't waste my time ... 
[21:21] <knome> lubuntu software center or sth
[21:21] <elfy> yea - that - confused 
[21:22] <knome> iirc, somebody said there was some changes to that and they could be renaming if to "light software center" or something
[21:23] <knome> i only vaguely remember the discussion, but i think there was some discussion about us co-maintaining it (which i said "no, not really" to, because that wouldn't have made sense with menulibre around)
[21:23] <drc> ok here's the screenie http://imagebin.org/270177
[21:23] <knome> might've been phillw
[21:23] <elfy> I vaguely remember that
[21:23] <ali1234> drc: yeah that's alacarte, and no i don't get that dropdown in 13.10
[21:24] <elfy> drc - me neither
[21:24] <drc> neither did I...hence the question :)
[21:25] <elfy> but as ali1234 said - I can't see much being done by ubuntu for it - they don't use menus anymore ;)
[21:26] <drc> Then why change anything if they don't use it ?
[21:26] <drc> Nevermind, rhetorical question
[21:26] <elfy> no idea - nor have I any idea why it stopped working 
[21:26] <ali1234> speaking of alacarte, did anyone reproduce that panel and desktop crash when doing: mkdir -p ~/.local/share/desktop-directories/ && truncate --size 0 ~/.local/share/desktop-directories/xfce-accessories.directory
[21:27] <elfy> I don't know anything about that one - must have been asleep
[21:27] <elfy> which I'm off to do shortly - cya tomorrow
[21:27] <knome> what's not working? i though the bug was about small fonts which i don't see at all in the screenshot
[21:28] <drc> So...No one really knows about it (alacarte), it's not xubuntu's or xfce's and therefore a bug report is probably worthless ?
[21:28] <ali1234> well the worst that will happen is it gets ignored, so bug report it if you like
[21:28] <knome> well, there was a new version in june
[21:29] <knome> https://launchpad.net/alacarte
[21:29] <ali1234> it's been converted to python3 at least
[21:29] <ali1234> that's why it crashes now - python3 does not like when you write none-ascii characters without an encoding
[21:30] <ali1234> so it write 0 byte .desktops and .directory files - which crash the panel and the xfdesktop
[21:36] <Unit193> knome: Only "Lubuntu menu app" is lxmed, and they don't use it because it is java.
[21:39] <knome> heh.
[21:40] <Unit193> (Not part of LXDE too.)
[21:40] <knome> yup, that i knew
[21:49] <Noskcaj> The light software center thing was phillw and i. There's been some talk of it becoming an active project again, i need to check with mh0 if he still wants to do that
[23:27] <brainwash> regarding systemd-shim and systemd/logind in general.. can anyone explain this systemd/upstart mix? can't we get rid of upstart, because it's developed by Canoncial?
[23:28] <Unit193> Of the two, I think upstart is the lesser evil.
[23:29] <brainwash> but currently things appear to be mixed
[23:30] <brainwash> or is it some sort of hidden transition?