[09:36] <knome> Noskcaj, btw, did you check if the OEM installation works for xubuntu?
[09:36] <Noskcaj> no
[09:36] <knome> okay, you should have
[09:36] <knome> Noskcaj, i haven't had luck in getting oem-config (the end-user set up) to actually run, so if that's the case, there's no way for anybody to ever see the slideshow
[09:37] <knome> the problem is that the system simply refuses to boot into the end-user desktop
[09:37] <Noskcaj> I never got an iso, but when i made it, the emulator said it worked fine
[09:37] <knome> the what emulator?
[09:37] <Noskcaj> The slideshow test thing, whatever that is called
[09:37] <knome> i tested with the regular ISO as well, the system doesn't boot into the end-user mode even with that
[09:38] <knome> right... so you checked the HTML validity and such. that's nice, but it doesn't help
[09:38] <smartboyhw> Noskcaj, the emulator only plays the slideshow. Don't think that it runs like ubiquity
[09:39] <knome> lunchtime
[09:39] <knome> i'll be back after that for a while
[09:39] <xnox> Noskcaj: thanks for persistently marking lubuntu not showing the correct release notes URLs. This has been fixed on the cdimage building side & on the redirector side, so friday's images release notes url should finally work properly (and e.g. studio, gnome, kylin flavours as well)
[09:40] <Noskcaj> xnox, :) 
[09:40] <smartboyhw> xnox, great to hear that;)
[09:40] <smartboyhw> Noskcaj, great job in doing that:)
[09:41] <Noskcaj> nearly a year of reporting that, and finally it get's fixed
[09:41] <Noskcaj> I think kubuntu did well having it point to "news", but daily build info would be heaps better
[09:49] <Noskcaj> Do we have our own tag on the ubuntuwire FTBFS list?
[09:49] <smartboyhw> Noskcaj, I think FTBFS has each flavour specifically tagged
[09:49] <Noskcaj> ok, then yay us, for not having any
[09:50] <smartboyhw> Noskcaj, where's the page?
[09:50] <Noskcaj> http://qa.ubuntuwire.org/ftbfs/
[09:50] <Noskcaj> studio has 4, kubuntu 14
[09:51] <smartboyhw> Noskcaj, in Kubuntu, some ftbfs cannot be fixed by us
[09:52] <Noskcaj> I know, most of the PPC stuff. That will all be fixed for 14.04
[10:01] <knome> ok, i'm off ->
[10:04] <Noskcaj> bye knome 
[11:40] <elfy> ochosi: is there something missing from git checkout andrzejr/wrapper3 - cos it fails 
[11:40] <ochosi> did you cd into the dir the clone created?
[11:40] <ochosi> (as in: cd xfce4-panel)
[11:41] <elfy> no 
[11:41] <elfy> but then I'm not awake either ... 
[11:41] <ochosi> ok )
[11:41] <elfy> that works ok then :p
[11:43] <elfy> I'll look later - need to install abunch of stuff as well :)
[11:44] <ochosi> sure :)
[12:02] <elfy> ochosi: so got to the last bit ... and then *** The required package libxfce4panel-2.0 was not found on your system.
[12:02] <ochosi> did you run sudo ldconfig?
[12:03] <ochosi> (oh and where did you install the panel etc. to?)
[12:03] <elfy> opened a terminal and did it all there 
[12:04] <elfy> so it's all in my home
[12:04] <ochosi> so you never ran "sudo make install"?
[12:04] <elfy> yea
[12:05] <ochosi> then you'd have to add your home subdir to the library paths or something
[12:05] <ochosi> are you on a testbox?
[12:05] <elfy> ok - I'll look properly a bit later 
[12:06] <elfy> sort of - this is a running 13.10 almost prod machine
[12:06] <ochosi> well to the worst you'd have to run "sudo apt-get install xfce4-panel --reinstall"
[12:06] <ochosi> that'd give you back your old panel
[12:06] <elfy> yep
[12:06] <ochosi> if you build with --prefix=/usr and overwrite your panel
[12:06] <elfy> I still have the old panel at the moment 
[12:07] <ochosi> if you build without prefix, it gets installed into /usr/local/share
[12:07] <ochosi> so you can cleanly uninstall
[12:07] <elfy> yep - well Iwent the whole hog and have been using  --prefix=/usr :)
[12:07] <ochosi> well you need the panel installed in order for the plugin to find the lib
[12:08] <ochosi> unless you modify the library paths
[12:08] <elfy> just been following the mail 
[12:08] <ochosi> but i can't help you much with that
[12:08] <elfy> :)
[12:10] <elfy> I'll possibly have another go in a vm later - gtg now
[12:10] <ochosi> seeya
[12:53] <jjfrv8> elfy, is it too late to add a bug to a beta testcase? Looks like I missed one.
[13:02] <elfy> jjfrv8: what bug 
[13:03] <jjfrv8> a new one, as far as I can tell. Settings Manager -> Printers does not even open.
[13:03] <jjfrv8> system-config-printer gives an import error.
[13:03] <ochosi> interesting, works here (on saucy)
[13:04] <jjfrv8> In case it was my hardware, I installed Raring on it and it works there, but not with Saucy.
[13:04] <elfy> not working in this machine 
[13:05] <elfy> bunch of updates for cups etc today
[13:06] <jjfrv8> running them now...
[13:07] <elfy> see if you can edit your result and add the bug - if not I'll add it
[13:08] <jjfrv8> I can't figure out how to file the bug. ubuntu-bug doesn't recognize the system-config-printer package.
[13:09] <jjfrv8> still doesn't work after running latest updates.
[13:11] <elfy> ubuntu-bug system-config-printer-gnome or -common 
[13:12] <jjfrv8> which should I use?
[13:14] <elfy> no idea 
[13:14] <elfy> I'd use the gnome one - someone will move it if it's wrong
[13:14] <elfy> once you've done it - I'll confirm it 
[13:15] <jjfrv8> Okay, they both work but I'll use the gnome one.
[13:25] <jjfrv8> elfy, edited testcase result. https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1221219
[13:33] <elfy> jjfrv8: confirmed that 
[13:35] <jjfrv8> my bad for not finding that first time through :(
[13:36] <elfy> wonder if knome saw it on the 64bit one
[13:40] <jjfrv8> I can install the 64bit and check. Would that be a separate bug, an update to existing one, or neither?
[13:40] <elfy> mine's 64bit
[13:40] <elfy> same bug I'd assume
[13:40] <jjfrv8> oh, okay.
[13:41] <elfy> we'll have to follow it on the dailies as well
[13:42] <elfy> I'd guess that it's not xubuntu specific 
[13:45] <jjfrv8> bbs
[14:30] <pitti> hello everyone
[14:30] <pitti> in #u-devel we just discussed bug 1221254 (just filed that for tracking)
[14:31] <pitti> does anyone know here whether we still need squeeze?
[14:31] <pitti> it's XFCEish, but not even seeded in xubuntu, and if it actually wants to use hal it's definitively broken now
[14:31] <pitti> (no idea if hal actually still worked in earlier releases)
[14:31] <pitti> so I wanted to check with you before I kill squeeze, and thus thunar-vfs
[14:31] <ochosi> hey pitti 
[14:31] <pitti> (main XFCE moved to gvfs ages ago)
[14:32] <pitti> hey ochosi, how are you?
[14:32] <ochosi> fine fine :)
[14:32] <ochosi> you too i hope?
[14:32] <ochosi> (looking out of the window at canale grande in venice, so how could i not be?)
[14:32] <ochosi> there were upstream plans to rewrite squeeze
[14:32] <ochosi> in fact there is a branch
[14:32] <ochosi> but it was never finished
[14:32] <ochosi> and we haven't shipped in it ages
[14:33] <ochosi> xubuntu did s/squeeze/file-roller/ a longer while ago (can't even remember when that took place)
[14:33] <skellat> And noskcaj just filed a pretty huge bug against squeeze yesterday
[14:33] <ochosi> i personally don't see any reason why we would keep it around if you wanna kick out hal, but i'd try and get mr_pouit's opinion on it
[14:34] <ochosi> but i can also get in touch with one of the squeeze devs if you want
[14:35] <pitti> ochosi: wow, Venice!
[14:35] <pitti> never been there
[14:35] <pitti> ochosi: ah, so it sounds xubuntu wouldn't be hurt a lot by it?
[14:35] <ochosi> i don't think so
[14:35] <pitti> ochosi: of course, once there's a gvfs port of squeeze it can always be reactivated
[14:35] <skellat> pitti: LP Bug #1220902 was the latest crash bug for squeeze as it was reported in 13.10 testing.
[14:35] <pitti> but I doubt that you guys are fancy supporting thunar-vfs still?
[14:36] <ochosi> but as i'm not one of the packagers i wouldn't like be the one to "pull the trigger"
[14:36] <ochosi> no, thunar-vfs is not really in use anymore
[14:36] <pitti> ochosi: except by squeeze :)
[14:36] <pitti> which might explain quite a few crashes, too
[14:36] <ochosi> hehe
[14:36] <ochosi> yeah
[14:36] <pitti> mr_pouit: perhaps you can give a "yay" or "nay" for slashing thunar-vfs and squeeze in the bug?
[14:37] <ochosi> but it's a good motivation to give squeeze another look
[14:37] <ochosi> i'll talk to upstream and see whether we can port it
[14:38] <pitti> ochosi: thanks, appreciated
[14:38] <skellat> pitti: micahg is unavailable until the weekend and I am unsure about the availability for mr_pouit.  If you could throw an e-mail on xubuntu-devel@lists.ubuntu.com it would be helpful.
[14:38] <ochosi> no problem
[14:38] <ochosi> skellat: +1
[14:38] <pitti> skellat: can you moderate this? 
[14:38] <ochosi> (i was about to mention that)
[14:38] <skellat> Only pleia2 & knome can do that
[14:38] <skellat> But I can also forward anything you send me at skellat@ubuntu.com
[14:39] <ochosi> if you do send an email to the ML, please cc mr_pouit directly
[14:39] <ochosi> and maybe also micahg 
[14:39] <skellat> I'm okay with squeeze & thunar-vfs being nuked from orbit at this point but I'd really prefer micahg and mr_pouit to have final say.
[14:41] <ochosi> +1
[14:41] <skellat> Wait
[14:41] <skellat> Never mind
[14:41] <skellat> Scratch that "Wait"
[14:41] <pitti> skellat: sent
[14:42] <pitti> skellat: thanks for relaying
[14:45] <skellat> pitti: Sent.  No problemo.  I added Micah on to the bug and added xubuntu-bugs so I can watch proceedings.
[14:45] <pitti> skellat: thanks
[14:45] <ochosi> thanks for getting in touch pitti 
[14:49] <pitti> thanks to you!
[14:49] <ochosi> pitti: upstream squeeze-dev also suggested dropping it btw (just asked)
[14:50] <pitti> ochosi: ah, good
[15:16] <pitti> ochosi: so, I fixed a few others and deal with some removals, but looks like this is the main leftover
[15:16]  * pitti waves good night
[18:36] <brainwash> selecting shutdown in logout dialog returns me back to the lightdm greeter
[18:36] <brainwash> this is not the expected behavior, right?
[18:49] <Unit193> ochosi: He's got your bug.
[18:49] <Unit193> brainwash: Update or fresh install?
[18:53] <brainwash> Unit193: upgraded
[18:53] <Unit193> He did as well, while I'm pretty sure elfy (fresh install) didn't.
[18:54] <brainwash> guess I start checking some log files
[18:55] <Unit193> There may be a package in proposed to fix it, though I'm not sure I'd want to enable proposed.
[18:57] <brainwash> well, looks like there has to be a bug report for this issue, because it seems to be reproducible
[18:58] <xubuntu750> Installing 1310b1, Just a note (I'm sure you all realize this,but...) during install, the "Your Web Experience"  slide still references 13.04 and RR
[18:59] <Unit193> https://bugs.launchpad.net/xfce4-session/+bug/1178373
[18:59] <Unit193> xubuntu750: Oh?  Thanks, someone may have but I didn't.
[18:59] <xubuntu750> In the e-mail show on the right.
[19:00] <brainwash> uhm, exo-open now prefers chromium for displaying urls..
[19:01] <brainwash> so many little issues due to the upgrade I simply can't explain :D
[19:01] <Unit193> brainwash: Preferred Applications list firefox?  Also check ~/.local/share/applications/mimeapps.list
[19:01] <Unit193> I normally get kinks on upgrade, just takes a little time to work them out.
[19:02] <brainwash> "exo-open --launch WebBrowser" opens firefox
[19:02] <brainwash> exo-open <url> does not
[19:03] <brainwash> and speaking of firefox, some icons like the one used for the tab close button are bigger now
[19:04] <lderan> exo-open "http://bbc.co.uk" works for me
[19:05] <brainwash> it works, but does not open my preferred web browser
[19:05] <Unit193> brainwash: I'd check that file in .local
[19:06] <brainwash> Unit193: done, it contains nothing related to the http protocol
[19:06] <Unit193> Poop.
[19:06] <brainwash> maybe the global mimeapps file
[19:07] <Unit193> lderan: Your fixup for calling version in the ubiquiry slideshow got pushed, right?
[19:07] <lderan> its still pending i think, shall check
[19:08] <Unit193> Yeah. :/
[19:09] <lderan> yeah 
[19:10] <brainwash> Unit193: the patched xfce4-session package has been already moved from proposed to release
[19:11] <Unit193> That's weird, ubiquity-slideshow is updated, and doesn't even use "Your Web Experience", it's now "Your internet experience" and I remember that happening.
[19:12] <lderan> think the plan is to get some more opinions on the changes on my MP
[19:12] <Unit193> lderan: In case you missed it, thanks a ton for checking the EFI thing!
[19:13] <lderan> no problem at all :)
[19:18] <Unit193> brainwash: Don't think it'll help you much, but I'll boot my Saucy VM, install chromium there and see how it goes.
[19:20] <brainwash> Unit193: no worries, I'm just a little bit confused about all these minor issues, they all seem so random
[19:34] <brainwash> Unit193: the firefox/chromium issue appeared to be related to exo-open, but it isn't
[19:35] <Unit193> And my VM is borked anywho.  Triggered elsewhere?
[19:36] <Unit193> xdg I'd assume does it as well, but that's pretty needless to say.
[19:36] <brainwash> a perl script does not call exo-open anymore (passes as paramter), it calls "sensible-browser" instead, which appears to be chromium on my system
[19:36] <brainwash> (passed as parameter)
[19:37] <Unit193> Ah, so chromium has it in it's postinst to set update-alternatives.
[19:38] <brainwash> one issue solved so far, hooray :)
[19:42] <brainwash> always fun when you avoid doing a fresh install
[19:42] <Unit193> Pains of upgrade are far less for me than it would be to reinstall.
[19:45] <brainwash> Unit193: can you confirm that some icons/symbols in firefox are slightly bigger than expected?
[19:45] <brainwash> like the tab close button
[19:53] <Unit193> They seem to be typical...
[19:58] <Unit193> knome: Meetings still seem to work best at the time they are?
[19:59] <knome> Unit193, yeah, pretty much. how so?
[20:00] <Unit193> Just was wondering.
[20:01] <knome> sure
[21:17] <Unit193> andrzejr: Howdy!
[21:17] <knome> fyi, i just posted http://xubuntu.org/news/saucy-salamander-b1/
[21:17]  * Unit193 looks.
[21:18] <andrzejr> hi
[21:18] <andrzejr> knome, what's the status of xfce4-indicator-plugin, are you still considering shipping it (gtk3 version) in 13.10?
[21:19] <knome> andrzejr, unfortunately, no
[21:19] <knome> andrzejr, we're looking to get it in saucy-backports though
[21:19] <knome> andrzejr, and if xfce 4.12 isn't ready for 14.04, it'll be definitely on our list for inclusion by default for 14.04
[21:21] <andrzejr> have you found any particular problems with it (and xfce4-panel)?
[21:23] <knome> i haven't personally been too involved with it, but there has been at least some minor problems and then problems with theming, but the the main reason why we're not making it default for 13.10 is the tight timeframe and too little testing time
[21:23] <Unit193> I think they were hopeing for an official release rather than snapshots or branches, perhaps more testing as well.
[21:24] <Unit193> knome: No pointers at currently known issues?
[21:24] <knome> you should ask ochosi and ali1234 
[21:24] <ali1234> andrzejr: i found some problems, yeah
[21:24] <knome> or read the channel logs :)
[21:24] <ali1234> nothing serious, only cosmetic stuff
[21:25] <andrzejr> hi ali1234 :-)
[21:25] <andrzejr> so what did you find?
[21:26] <ali1234> well, you know that is_small() function?
[21:26] <ali1234> it makes a lot of bad assumptions
[21:26] <ali1234> like small indicators will always be square - they're not
[21:26] <ali1234> or that they will be pixbufs
[21:26] <ali1234> or that they will be 22px or smaller
[21:27] <ali1234> none of these is necessarily true
[21:27] <ali1234> also, padding labels to 22px makes them unaligned with other things on the panel
[21:28] <ali1234> since is_small breaks quite a bit, the row stacking usually doesn't work either
[21:30] <andrzejr> you mean number of rows in the panel > 1?
[21:30] <ali1234> not in the panel, just in the indicator
[21:30] <andrzejr> padding labels is indeed questionable - I'd have to replicate relevant code of gtkbox(?)
[21:30] <ali1234> like if you make the panel 60px tall it tries to do two rows of indicators
[21:31] <andrzejr> you mean you want 3?
[21:31] <ali1234> no, i want one
[21:31] <ali1234> i think that whole row stuff should go, because it doesn't work
[21:31] <andrzejr> well, that's a feature
[21:31] <andrzejr> we could have an option to disable it
[21:32] <ali1234> it would be a feature if it worked :)
[21:32] <ali1234> the padding on labels isn't real padding
[21:32] <ali1234> it just does a hack with the space allocation
[21:33] <andrzejr> well, I'm using it all the time and it works for me.
[21:33] <andrzejr> (multiple rows)
[21:33] <ali1234> yeah it does make multiple rows
[21:33] <ali1234> but only with "small" indicators
[21:33] <ali1234> sound, bluetooth, datetime don't fit the criteria
[21:34] <ali1234> sound because it's icon is 24x22, bluetooth because it's icon is 16x22
[21:34] <ali1234> and datetime because it is a label
[21:34] <andrzejr> sound, bluetooth work here, if it doesn't it is a bug
[21:34] <ochosi> sey folks, bedri e for me, i'll have to read the backlog and comment tomorrow
[21:34] <ali1234> yeah, it's a bug, because a label is only considered small if width=height
[21:34] <andrzejr> datetime is not a "small" button because it is not small :-)
[21:34] <ochosi> (still dont have a stable place to live)
[21:35] <ali1234> but this isn't a valid assumption
[21:35] <ali1234> but the bigger problem comes from the way the child allocation is done with small indicators
[21:35] <ali1234> even if you have only one row, they still don't vartically align properly
[21:36] <ali1234> the only way to fix the vertical alignment is to make them all not-small
[21:36] <andrzejr> seems like a bug
[21:36] <ali1234> or to try to fix the allocation routines, which are horribly complicated
[21:36] <ali1234> btw, what is the "maximum row height" thing in settings?
[21:36] <ali1234> i don't understand what this option is supposed to do
[21:37] <ali1234> if it's related to row stacking code, i recommend changing it to "maximum number of rows" or something
[21:37] <andrzejr> The reason I went for a custom container is precisely to avoid complexity. It was far worse before (trying to workaround) issues with stock containers
[21:37] <ali1234> then i can just set it to 1 and have is_small() return false always in this case
[21:37] <ali1234> sure but the problem isn't the custom containers... it's the implementation...
[21:38] <andrzejr> AFAIR that is a leftover from previous versions (when icons were scaled), no longer needed.
[21:38] <ochosi> andrzejr: i think one thing we should resolve is libxfce4ui not having had a dev release wi gtk3 as an option
[21:38] <andrzejr> ochosi, that, and the panel
[21:38] <ochosi> andrzejr: i've already pinged nick, but no response so far
[21:39] <ochosi> yeah but releasing a new lib version is easier than the huge merge
[21:39] <andrzejr> but knome has just said xubuntu is not shipping gtk3 version, so we have time
[21:39] <ochosi> so i ought one at a time :)
[21:39] <ochosi> yeah, indeed
[21:39] <ochosi> well backports means that people would be able to install later
[21:39] <andrzejr> ali1234, I'll add an option to disable multi-row layout - that's a fair use-case.
[21:40] <ochosi> so if they want a gtk3 indicator, all the panel, libyfce4ui and new indicator-plugin would be pulled as dependa
[21:40] <andrzejr> but multi-row layout is there to stay - I'm using it all the time in deskbar mode
[21:40] <ochosi> (i'm no packager, but that's how i understood micahg )
[21:41] <andrzejr> ochosi, and gtk2 indicators would get removed?
[21:41] <andrzejr> (are there any gtk2 indicators in 13.10?)
[21:42] <ali1234> i think appindicator and sound-gtk2 (which is broken) are the only ones
[21:43] <ochosi> yup those two
[21:43] <ochosi> but sound is borked atm
[21:43] <ochosi> (afaik)
[21:43] <ochosi> anyhoo, sorr for the quick appearance, will get read the rest tomorrow
[21:44] <ochosi> thanks for your work, andrzejr and ali1234 
[21:44] <ochosi> nighty
[21:44] <ali1234> andrzejr: so the thing is, even when there's only one row, the labels etc still don't line up right without hacks
[21:44] <ali1234> it's very theme dependent though
[21:45] <ali1234> but it should not be - it should line up when there's no explicit theming
[21:45] <andrzejr> ali1234, can you tell me (exactly) how to reproduce layout issues? (theme, panel conf, size, indicator name etc.)
[21:46] <ali1234> theme = orion, icons = ubuntu-mono-light
[21:46] <ali1234> put an indicator-datetime on, and put a xfce clock next to it
[21:46] <ali1234> now resize the panel to each size between 16px and 50px
[21:46] <ali1234> sometimes they line up, sometimes they don't
[21:47] <ali1234> if you don't have orion, raleigh also does the same thing
[21:47] <andrzejr> OK, I see it. Thanks!
[21:47] <ali1234> any theme that doesn't explicitly set panel themes should do it
[21:47] <ali1234> also, if you add lots of indicators, sometimes you'll see that they bob around relative to each other
[21:48] <ali1234> that depends on whether they are small or not
[21:48] <Unit193> knome: Do you happen to know/think these will be in backports upon release?
[21:48] <knome> you need to ask micahg
[21:49] <ali1234> i found a way to fix the labels - hack the prefered height to be minimum 1px instead of ICON_SIZE and then also set the GtkAlignment valign to center instead of fill
[21:49] <ali1234> this also fixes the icons, but only if they're not small
[21:50] <ali1234> basically this: https://github.com/ali1234/xfce4-indicator-applet/commit/d0573ec25bd615b6a5cb4758d240b0ae7f9b56a2
[21:50] <ali1234> but the thing is, if you do this, it makes the multirow misalignment even worse
[21:50] <andrzejr> ali1234, please make a branch and commit it
[21:50] <knome> bbl
[21:50] <knome> probably later tomorrow ->
[21:51] <Unit193> Adios.
[21:51] <ali1234> it's not a proper solution
[21:53] <andrzejr> OK, I'll have a look at it
[21:54] <ali1234> hmm how do i specify username on the git remote?
[21:54] <andrzejr> sorry, no idea
[21:54] <ali1234> i guess it's not necessary
[21:57] <ali1234> also, indicator-multiload doesn't work when the panel is rotated. did i mention that?
[21:57] <ali1234> if a pixbuf indicator is longer than a certain amount it needs to be rotated like labels are
[21:59] <ali1234> i would rather not have special casing everywhere for single row mode, but it might be the only way
[21:59] <ali1234> what i really don't understand though, is why the / 2 everywhere
[22:00] <ali1234> i'm fairly sure that is what makes it become misaligned
[22:00] <andrzejr> indicator-multiload is designed for a horizontal panel - nothing I can do about it.
[22:00] <ali1234> gtk can't rotate pixbufs?
[22:00] <andrzejr> Before I was stretching the pixbuf but I've decided not to support it any longer
[22:01] <andrzejr> I don't know but xfce4-panel doesn't rotate icons in vertical panel so I follow the same convention
[22:01] <ali1234> ok
[22:02] <andrzejr> bbl
[22:09] <ali1234> andrzejr: if you can add the config setting for single row mode, i'll hammer the calculations until they work in both modes and for any icons/panel size, but i don't know how to do the config panel change
[22:19] <ali1234> actually it could just select mode based on the panel height
[22:19] <ali1234> it already kind of does that
[22:20] <ali1234> hmm
[22:25] <ali1234> ok i'll take another look at this tomorrow
[22:26] <andrzejr> I've pushed the change (a new option)
[22:28] <ali1234> oh, one other totally unrelated thing while i remember. can we fudge the class names so that unity styles are picked up by the indicators?
[22:31] <andrzejr> what should be the class name?
[22:33] <ali1234> i'm not sure but this is what the css looks like: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/light-themes/saucy/view/head:/Ambiance/gtk-3.0/apps/unity.css#L18
[22:34] <ali1234> i suspect actually we can't due to how the styles are nested
[22:34] <ali1234> and because menubar is already a class and not the one we're using
[22:42] <andrzejr> I wonder if some of these misalignments are coming from gtk2/gtk3 differences in themes
[22:42] <andrzejr> btw, I have an ugly workaround for padding error in gtk3 gtkbutton
[22:43] <andrzejr> #6890030
[22:43] <ali1234> no, i;m fairly sure it's not the themes
[22:43] <ali1234> orion doesn't apply anything special to any buttons, so they should all be the same
[22:44] <ali1234> also i inspected with gtkparasite
[22:54] <andrzejr> ali1234, looks like it is enough to pass y & height through to a child widget
[22:55] <andrzejr> that fixes label alignment
[22:55] <ali1234> it does?
[22:55] <ali1234> even when the panel is 16px?
[22:58] <andrzejr> yes
[23:02] <ali1234> ok. found a bug btw - the new config option is gint instead of gboolean
[23:07] <ali1234> hmm
[23:08] <ali1234> so did there used to be an nrows option?
[23:21] <ali1234> hmmmm... almost working. i'll fix this tomorrow
[23:57] <andrzejr> ali1234, pushed some layout fixes