[03:33] <skellat> Oops...I made it go kaboom again... LP Bug #1214691
[03:33] <ubottu> Launchpad bug 1214691 in chromium-browser (Ubuntu) "chromium-browser crashed with SIGSEGV" [Undecided,New] https://launchpad.net/bugs/1214691
[08:45] <knome> micahg, ping.
[09:01] <cub> Hi ochosi , knome asked me to check with you with a non-shrinking icon for the power indicator. I suppose it's elementary Dark that is included in Ubuntu Studio, but not entirely sure. Are you available?
[09:01] <ochosi> cub: hi, i'm semi-available atm, might have to go every second (awaiting important call)
[09:01] <ochosi> but you can tell me bout it and to the worst i read and reply later
[09:03] <cub> np. I changed the size of the upper panel on my netbook running Saucy from 24 to 16, but the icon in the tray for Power/battery stays the same and you can't see the whole icon. I also tried that same thing on my Ubuntu Studio 13.04 with the same result. Seems 24 is the only size for that icon.
[09:04] <Noskcaj> ochosi, cub: i can confirm it affects xubuntu saucy
[09:04] <Noskcaj> while running elementary darker
[09:04] <ochosi> yeah, that's a semi-known issue
[09:05] <ochosi> cub: there's no 16px version of those icons (there are quite a few of them)
[09:05] <ochosi> as not many ppl use such a tiny panel and no-one complained so far, i never added those icons
[09:06] <cub> hehe, I'm picky with my small screen.
[09:06] <cub> but then I know. thanks.
[09:06] <ochosi> btw, the same is true if you're using just elementary-xfce
[09:06] <cub> yes I tried a few different just now.
[09:06] <ochosi> theoretically when you use an earlier version, the icon would scale down
[09:07] <ochosi> but it would then always be fuzzy unless panel-height=24
[09:09] <ochosi> i'm happy to accept patches, if anyone here wants to draw those icons :}
[09:10] <cub> It's on my list to learn how to do icons and themes. Just very far down on the list.
[09:13]  * Noskcaj needs something he can do for xubuntu one-handed. will look icon icon making
[09:13] <Noskcaj> *into icon
[09:16] <Noskcaj> ochosi, Where is the branch so i can try making icons?
[09:17] <ochosi> Noskcaj: https://github.com/shimmerproject/elementary-xfce
[09:17] <ochosi> starter-tip: always align everything to the grid, otherwise we can't use the icon/s
[09:18] <Noskcaj> That means nothing to me so far
[09:22] <Noskcaj> ochosi, Any tools you recommend i use?
[09:22] <knome> Noskcaj, TBE: if you are drawing a 16x16 icon, there is a virtual grid of 16x16. try not to cross those lines.
[09:23] <knome> Noskcaj, inkscape.
[09:23] <Noskcaj> knome, ty
[09:33] <Noskcaj> Any how-to guides? i have no idea what i'm doing
[09:37] <cub> Noskcaj, http://www.microugly.com/inkscape-quickguide/
[09:37] <Noskcaj> cub, ty
[09:38] <cub> I haven't gone through myself but got the link when I asked the same question a couple of weeks ago.
[09:42] <knome> Noskcaj, my #1 step in a guide would be to understand what you're doing first
[09:42] <knome> Noskcaj, try looking for examples in other icons, see how they are aligned to the grid
[09:43] <knome> Noskcaj, get a grasp of what the icon should look zoomed in inkscape with a grid visible
[09:44] <knome> s/the/an/
[09:44] <knome> Noskcaj, then get an image in your head of what you want to make the new icon look like, what kind of elements it should have
[09:44] <knome> Noskcaj, then worry about knowing how to use inkscape.
[09:46] <smartboyhw> knome, you guys better get started on testing 12.04.3
[09:46] <smartboyhw> elfy, ^
[09:46] <knome> smartboyhw, yeah yeah, sure sure. ;)
[09:46] <smartboyhw> LOL
[09:47] <lderan> i can do some testing if need be :P
[09:47] <smartboyhw> lderan, I think you are needed:P
[09:47] <smartboyhw> (LOL)
[09:47] <lderan> \o/
[10:01] <knome> lderan, hey
[10:01] <knome> lderan, i was thinking the other day
[10:01] <knome> lderan, do we need an extra "version-details" tag?
[10:01] <knome> lderan, couldn't you just put the , inside "version-id"?
[10:02] <lderan> easily enough to make it do that. will there be a case where the , is unneeded? 
[10:03] <knome> hmm, i see now that being a bit problematic regarding the spot where you'd put the ID itself
[10:03] <knome> i mean if it's inside version-id, you'd have to put the ID either after or before the comma
[10:03] <lderan> could have several classes for the variations
[10:03] <knome> lderan, yeah, the case when you don't get the version number ;)
[10:03] <knome> i'd just rather go with one
[10:04] <knome> i'm thinking this fallback is overcomplicating things.
[10:04] <knome> but that might be needed.
[10:04] <knome> also thinking: instead of span replacements, couldn't we do text replacement?
[10:05] <knome> eg, if you type $versionID in the text, it gets replaced
[10:05] <knome> i know that's not as easy with JS as element replacement
[10:05] <knome> what i'm wondering about might be just a non-problem :)
[10:05] <lderan> regex to save the day :P
[10:05] <knome> i mean, it's not something you poke every day
[10:05] <knome> even less when that's automated
[10:06] <lderan> indeed
[10:08] <knome> i just poked the usage a bit
[10:13] <lderan> poke away :P
[10:14] <lderan> its very unlikely the slideshow will not get the version number, more likely the version name wont be passed.
[10:15] <lderan> thats unlikely in of itself as well
[10:15] <knome> :)
[10:37] <knome> bbl
=== cyphermox_ is now known as cyphermox
[12:06] <elfy> smartboyhw: please don't be telling me what to do. Thanks.
[16:39] <olli> hi there
[16:42] <elfy> hi olli 
[16:42] <olli> knome, skellat wanted to give you guys a quick heads up on the status of xmir
[16:42] <olli> hey elfy
[16:42] <knome> hey olli
[16:42] <knome> i'm not actively around right now, but go ahead
[16:43] <olli> skellat, knome we are targeting a call for testing for the remaining 2 big features (Multimonitor, composite bypass) for either Thu or Fri this week
[16:43] <olli> I am saying "or Fri" in case there are issues in our internal preliminary testing
[16:44] <olli> knome, ack, just wanted to share that with you guys in advance of tomorrows meeting
[16:44] <elfy> olli: my biggest issue at the moment is that I still see what I did in xmir or not when I boot in and out
[16:44] <elfy> got screenshots here
[16:44] <olli> elfy, yeah, you are probably still on .8 or .9
[16:44] <olli> we had to stop landing to fix an ATI related issue
[16:45] <elfy> http://imgur.com/cPAmyNC,irF8k6K,DCfJ9j0#0
[16:45] <olli> and hence the "switch" branch hasn't hit archive yet
[16:45] <elfy> I updated/upgraded last night about 2000utc
[16:45] <olli> we should have turned landing on as of this AM European (didrocks') time
[16:45] <olli> let me check
[16:46] <elfy> so you're saying that if the updates have gone through I won't see that ^^ anymore
[16:46] <olli> that's my expectation
[16:46]  * olli checks on reality 
[16:47] <elfy> so will elfy ;)
[16:55] <ochosi> elfy: did you just ping yourself?
[16:55] <elfy> olli: have you checked? is it worth me booting the mir install to upgrade?
[16:55] <elfy> ochosi: not that I noticed 
[16:55] <elfy> but it's been a 25 hour day
[16:55] <ochosi> :)
[16:55] <olli> elfy, still discussing with ppl in #ubuntu-mir
[16:55] <elfy> full of 61 minute hours :p
[16:56] <elfy> olli: okey doke
[17:02] <elfy> olli: that bug that you're talking of in -mir isn't what I'm seeing
[17:03] <elfy> it might have got talked about in one of the other bugs I read though - but I can't be sure which one now
[17:06] <olli> elfy, arg, misread you
[17:06] <olli> elfy, I'll have kgunn or tvoss come back to you
[17:07] <elfy> ok - well they can do it with forestpiskie in -mir :)
[17:08] <knome> erm, if it's a xubuntu issue, i'd appreciate if it happened here
[17:08] <knome> just for the sake of logs and others being able to chime in
[17:09] <elfy> well they can come here then 
[17:09] <knome> (and generally it's nice to see that the mir team is willing to travel around, there might be other things people want to ask them etc)
[17:09] <knome> olli, so thanks for being here! :)
[17:23] <elfy> olli: so - is it going to be worth me upgrading to see what it looks like now - I'm going to be away tomorrow and need to make my views known prior to our meeting
[17:24] <olli> elfy, it should not regress, in a mtg atm with Kevin, can't look at it in the next 1h
[17:24] <elfy> ok 
[17:24] <olli> so, if you can I'd say give it a spin
[17:26] <elfy> ok - thanks
[17:50] <elfy> olli: slightly different - still get corruption in whatever I boot after I've been in mir
[17:51] <elfy> thanks for your help 
[17:51] <olli> elfy, weird
[17:51] <elfy> yep
[17:51] <olli> do you have a bug to track that issue?
[17:52] <elfy> no - though last time I did a bug and had a screenshot I just got sarcasm
[17:52] <elfy> which tends to put you off bothering
[17:52] <elfy> but I'm happy enough to do it again - what package to report against? 
[18:05] <olli> elfy, sarcasm? i'd be interested to see the initial report 
[18:05] <elfy> olli: I booted it again - just doing a bug report - which package should I report against?
[18:05] <olli> elfy, file it against unity-system-compositor and subscibe me
[18:06] <elfy> and that wasn't necessarily a mir bug :)
[18:06] <elfy> ok will do
[18:07] <elfy> olli: what's you LP name?
[18:08] <olli> ories
[18:12] <elfy> https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1215053
[18:12] <ubottu> Launchpad bug 1215053 in unity-system-compositor (Ubuntu) "Corruption in login window following reboot" [Undecided,New]
[18:13] <elfy> oh dear - found one that I didn't have yesterday now - in firefox in mir - cursor is now a rather large box when you've got an image to enlarge
[18:14] <olli> elfy, off to another round of mtgs
[18:14] <elfy> I'll screenshot that - attach it 
[18:14] <elfy> good luck - I'm getting close to putting my feet up 
[18:14] <knome> honestly speaking, mir still has quite a lot of bugs :/
[18:15] <ochosi> huge undertaking, little time > quite a lot of bugs
[18:15] <lderan> i would like to see it running on my pc :(
[18:15] <elfy> not having any luck capturing this oddity in a screeny
[18:15] <ochosi> hah, even managed to make the lines sync :}
[18:15] <knome> yeah, i'm not blaming anybody about it
[18:15] <knome> ochosi, heh, yeah ;)
[18:18] <elfy> http://i.imgur.com/sTkdYPe.jpg
[18:18] <elfy> that's what I see in a large image in firefox
[18:18] <elfy> brb
[18:49] <lderan> knome, shall i start on the text replacing for the slideshow?
[18:50] <knome> lderan, did dylan reply to your last commit?
[18:50] <lderan> no replies yet
[18:50] <lderan> shall check to make sur
[18:50] <lderan> e
[18:50] <knome> i'd wait for that
[18:50] <knome> he's the go-to guy on the slideshows anyway, so want to make sure he's comfortable with it
[18:51] <lderan> okay :)
[18:52] <knome> (at least before poking others' slideshows)
[18:53] <lderan> :P
[19:27] <elfy> I'd forgotten how old 12.04 looks 
[19:27] <elfy> or different perhaps
[19:32] <ochosi> elfy: artwork-wise?
[19:33] <elfy> yea
[19:34] <elfy> 13.10 looks just a whole different beast altogether 
[19:35] <Unit193> Mailing list user had the same issue as elfy.
[19:37] <elfy> that 12.04 looks different than 13.10 ?
[19:37] <elfy> :)
[19:38] <drc> well, greybird does look different on those two (to these eyes anyway)
[19:38] <elfy> yea - just a long long time since I saw it
[19:40] <ochosi> so what's the verdict then?
[19:41] <ochosi> (old doesn't necessarily mean bad/worse)
[19:41] <Unit193> Greybird?  I see it on live systems, but that's it.
[19:41] <drc> guilty...35 years sentence
[19:42] <elfy> ochosi: I much prefer what I see now 
[19:42] <ochosi> good to hear
[19:43] <elfy> indeed :)
[19:43] <ochosi> i'm trying to do incremental changes overall, but i know the switch away from the dark menus was harsh for many (at least in the beginning)
[19:44] <elfy> well I'd not really have noticed that as I never used dark menus - tended to change that 
[19:44] <drc> ochosi: since the topic came up :)...why is the appmenu light while the rest of the theme is dark?
[19:44] <ochosi> elfy: well all menus had a dark bg, now the bg is bright
[19:45] <ochosi> drc: how/where is greybird dark (apart from the panel)?
[19:45] <drc> the old greybird (say 12.04 era) it was closer to the panel color.
[19:45] <ochosi> yeah, i know
[19:45] <drc> well, I ment the panel...sorry
[19:46] <ochosi> i tried that, making only the panel-related menus dark, but it just felt very inconsistent with the rest
[19:46] <ochosi> so it turned out to be an all or nothing decision
[19:47] <ochosi> another issue was icon-colors
[19:48] <ochosi> with gtk3 this won't be as big a problem anymore
[19:48] <ochosi> but until then you have to decide what colors they should have
[19:48] <elfy> well - I didn't mean to start a discussion - was just a comment about how I prefer what we have now lol 
[19:49] <ochosi> hehe, artwork discussions have become rare anyways
[19:49] <drc> elfy: sorry, it's just that I've never seen ochosi in the (any) channel when the subject of greybird came up, so I <had> to ask
[19:49] <ochosi> people seem to be fed up with them or simply satisfied :)
[19:50] <ochosi> drc: you can always ask me about these things if you want to
[19:50] <elfy> a pair of :)'s 
[19:52] <drc> ochosi: I know, but it just normaly seems, well, silly to ask about such a small thing.
[20:04] <Unit193> Crap, I hate to bring it up before tonight, but I don't see anything majorly interesting in the latest two releases: https://launchpad.net/ubuntu/saucy/+source/mir/+changelog
[20:16] <lderan> yeah :(
[20:18] <elfy> anyone able to do a 32bit test for 12.04.3 - I've done the others but got nothing to do an entire disk test
[20:18] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/301/builds/51847/testcases/130/results
[20:18] <elfy> if they can
[20:21] <cub> Noskcaj, you disconnected earlier before I got to paste two more inkscape links: http://fullcirclemagazine.org/inkscape-special-edition-volume-one/ and http://fullcirclemagazine.org/inkscape-special-edition-volume-two/
[20:23] <Noskcaj> cub, thanks. i still don't understnd it
[20:24] <Noskcaj> elfy, i'll have a look
[20:24] <elfy> cheers Noskcaj 
[20:25] <Noskcaj> however, crappy laptop, internet and wrist will make things slow
[20:26] <elfy> it's just the one - I've done the 64bit and 3/4 of the 32bit
[20:53] <knome> elfy, feel free to mark the ISOs ready then :)
[20:53] <elfy> forget I can do that ... 
[20:54] <knome> heh
[20:54] <elfy> tick the 64 bit desktop and then mark as ready from the dropdown I assume
[20:54] <elfy> knome: ^^
[20:55] <knome> elfy, yup
[20:55] <elfy> ok - done that then :)
[20:56] <knome> nice
[20:57] <Noskcaj> elfy, What'sthe bug for the grey background boxes in precise?
[20:57] <elfy> not sure - didn't see them 
[20:58] <elfy> didn't see anything untoward at all 
[20:58] <Noskcaj> i've got three already
[20:59] <elfy> oh yea - waht bit of the testcase are they failing on ?
[20:59] <Noskcaj> i'll have bugs soon.
[20:59] <elfy> yea - but what bit of the testcase is failing? 
[21:00] <Noskcaj> The first bits
[21:00] <elfy> http://testcases.qa.ubuntu.com/Install/DesktopWhole
[21:00] <elfy> which first bit :p
[21:00] <knome> it's not a fail if it doesn't stop you from finishing the testcase - the grey bg areas won't
[21:01] <knome> those are bleh, but... we have 14.04 soon.
[21:02] <elfy> as far as I'm concerned if it passes the testcase it's a pass
[21:10] <elfy> Noskcaj10: did you catch our last comments? 
[21:10] <Noskcaj10> no
[21:11] <elfy> <knome> it's not a fail if it doesn't stop you from finishing the testcase - the grey bg areas won't
[21:11] <elfy> <knome> those are bleh, but... we have 14.04 soon.
[21:11] <elfy> <elfy> as far as I'm concerned if it passes the testcase it's a pass
[21:12] <elfy> I'm off up the wooden hill now anyway - thanks for doing that one
[21:12] <knome> thanks elfy and have fun
[21:13] <elfy> I'll do the 32bit alternate ones tomorrow
[21:14] <knome> nice
[21:14] <knome> i'll see if i can do one or two today or tomorrow
[21:14] <elfy> if you can manage the entire disk ones that'd help me
[21:14] <elfy> night
[21:14] <knome> nighty1
[21:14] <knome> ! too
=== mhall119_ is now known as mhall119
[23:49] <Unit193> mhall119: Why hello! :P
[23:50] <mhall119> hi Unit193