[00:54] <storrgie> How do I do multiple firefox instances with unity?
[00:54] <storrgie> it seems to only want me to have one
[01:04] <hyperair> i think if you middle click the icon it'll launch another instnace
[01:05] <hyperair> firefox also has a ctrl+n button you can use
[01:05] <ion> That’s just multiple windows.
[01:06] <ion> The last time i checked Firefox didn’t seem to support multiple instances at all. Which sucks. But neither did, say, Gnome.
[01:10] <hyperair> well i'm assuming that's what he meant by multiple instances.
[01:11] <ion> Unity-2D doesn’t seem to do anything when i middle-click a launcher button.
[01:23] <bcurtiswx> jono, re: new icons.  I don't know if it makes a difference, but empathy's new icons are in 2.91.X and we'll see them in OO. AFAIK
[01:24] <jono> bcurtiswx, cool
[01:24] <bcurtiswx> jono, wasn't sure if the others are the same or not
[08:01] <MacSlow> greetings everybody
[08:05] <oSoMoN> good morning
[08:18] <didrocks> good morning
[08:31] <htorque> good morning, everyone! what's currently the right way to disable the global menu in unity? still UBUNTU_MENUPROXY= <application>?
[08:33] <didrocks> htorque: hey!
[08:33] <didrocks> htorque: yeah
[08:33] <didrocks> just unset the variable
[08:34] <htorque> didrocks, interesting, because that doesn't work for the latex editor Kile
[08:41] <didrocks> htorque: are you sure it doesn't fork or something like that? I'm not sure KDE qt application are using this variable. Something to ask to agateau
[08:42] <agateau> htorque: didrocks: Qt does not use this variable (surprisingly, it does not load gtk modules! :) )
[08:42] <htorque> didrocks, seems they don't. just tested it with the editor Kate and it eouldn't work there either.
[08:43] <agateau> htorque: didrocks: iirc the appmenu wiki page mentions the correct var
[08:44] <agateau> mmm it does not
[08:44]  * agateau fixes the wiki
[08:45] <agateau> htorque: QT_X11_NO_NATIVE_MENUBAR=1 myapp should do the job
[08:45] <htorque> agateau, great, that worked, thanks!
[08:45] <agateau> (htorque: and don't forget to report a bug if you find an app which is broken with appmenu)
[08:45] <htorque> agateau, that was the next thing on my list ;)
[08:46] <agateau> htorque: good!
[08:46] <htorque> agateau, i forgot, which one was the right package for such bug reports?
[08:47] <agateau> htorque: appmenu-qt (sometimes the bug is in libdbusmenu-qt, but in this case I take care of reassigning)
[08:47] <htorque> agateau, good, thanks again
[15:06] <czajkowski> kenvandine: I have a wee problem with Gwibber being a tad special today. upgraded work machine to natty. No tweets, tried to stop and restart stuff, and now gwibber is crashing  https://bugs.launchpad.net/gwibber/+bug/724918/comments/4
[15:08] <kenvandine> czajkowski, can you get me a traceback from the gwibber-service?
[15:08] <kenvandine> killall gwibber gwibber-service
[15:08] <kenvandine> gwibber-service -d -o
[15:20] <czajkowski> czajkowski@Penny:~$ gwibber-service -d -o
[15:20] <czajkowski> Found gwibber-service already running, exiting
[15:20] <kenvandine> killall gwibber gwibber-service
[15:20] <kenvandine> then run it
[15:20] <kenvandine> oh... maybe it isn't dieing
[15:21] <czajkowski> aye I did the kill all
[15:21] <kenvandine> killall -9 gwibber gwibber-service
[15:21] <czajkowski> ahh that killed it
[15:22] <czajkowski> saying my accounts need to be reauthorised
[15:22] <czajkowski> loads and then crashes again
[15:23] <czajkowski> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/744997
[15:23] <coz_>   hey guys
[16:38] <rodrigo_> njpatel, didrocks: can I get a 2nd approval for https://code.edge.launchpad.net/~rodrigo-moya/unity/fix-740360/+merge/55319 ?
[16:40] <njpatel> rodrigo_, +!
[16:40] <njpatel> +1
[16:40] <njpatel> even
[16:40] <rodrigo_> njpatel, ok thanks
[16:49] <tedg> Cimi, When we're making something insensitive should we blend with white or the background color in the theme?  https://code.launchpad.net/~mterry/indicator-datetime/bevel+utc/+merge/54684
[16:50] <mterry> tedg, good point, probably background
[16:55] <tedg> mterry, Yeah, I was asking Cimi as I thought he might know how other people handle it.
[16:55] <tedg> mterry, It seems like the background color is the best we have.
[16:56] <mterry> tedg, alright, I'll look into patching it
[17:00] <Cimi> tedg: what's that?
[17:00] <Cimi> what's this cairo drawing
[17:02] <Cimi> tedg: and static colors are always wrong
[17:02] <Cimi> tedg: so you should pick the right one
[17:02] <tedg> Cimi, This is a custom widget
[17:02] <tedg> Cimi, We want it to "look insensitive" when it is.
[17:02] <tedg> Cimi, The idea was to dim it slightly.
[17:03] <Cimi> tedg: please don't mess with UI without asking me
[17:03] <tedg> Cimi, ?
[17:03] <Cimi> tedg: I will take care with the approval with Otto
[17:03] <tedg> Cimi, There is no approval with Otto here.
[17:03] <Cimi> tedg: I'm in charge of controlling the style guidelines
[17:04] <Cimi> tedg: so, if you're doing a cusstom widget/whatever, poke me before
[17:04] <Cimi> tedg: so we are sure to do it correctly and compatible with radiance/ambiance and other themes as well
[17:04] <Cimi> (High Contrast too)
[17:05] <Cimi> a fill with pure white seems an issue
[17:05] <tedg> Cimi, Frankly, that's impractical.  But, I'd your advice on this question.  What color do you think should be used?
[17:05] <Cimi> tedg: for what?
[17:05] <tedg> Cimi, To dim the map.
[17:05] <Cimi> I repeat, I'd like to see the widget to tell you
[17:05] <tedg> Cimi, Okay, go to datetime, pull up the settings.
[17:05] <Cimi> tedg: I would say
[17:05] <Cimi> base[INSENSITIVE] or bg[INSENSITIVE]
[17:06] <Cimi> LET ME SEE
[17:06] <Cimi> ops :D
[17:06] <Cimi> one second tedg
[17:06] <Cimi> tedg: does the color of the map change?
[17:06] <tedg> Cimi, No, they're PNGs
[17:06] <Cimi> tedg: ok, so white sounds ok
[17:07] <Cimi> tedg: we just don't care
[17:07] <Cimi> tedg: I would say again bg[INSENSITIVE]
[17:07] <tedg> Cimi, Won't that look odd in a dark theme?
[17:07] <Cimi> tedg: or maybe bg[NORMAL]
[17:07] <tedg> Yeah, I think bg[INSENSITIVE] makes the most sense.
[17:08] <Cimi> tedg: either insensitive or normal
[17:08] <Cimi> normal could be good as it blends with the borders around the picture
[17:08] <tedg> Cimi, Which would you prefer?
[17:08] <Cimi> ops, with the frame around
[17:09] <Cimi> tedg: I would say bg normal just for this reason
[17:09] <Cimi> what do you think?
[17:09] <Cimi> if your goal is to make the png dimmed
[17:10] <Cimi> tedg: though I would desaturate it a bit or make it transparent
[17:10] <Cimi> instead covering it
[17:10] <Cimi> or a combo
[17:11] <Cimi> tedg: anyway I know that poking me could slow down things, but it's better to slow down now than fixing visual bugs in the future :)
[17:12] <Cimi> tedg: also, what happened to my branch proposed for indicator-messages with the updated bubbles and text?
[17:12] <tedg> Cimi, It was crashing indicator messages, like I replied on the merge request.
[17:14] <Cimi> tedg: let me catch it
[17:15] <mterry> tedg, branch updated to use background color
[17:15] <tedg> mterry, Great, thanks!
[17:40] <cimi_> tedg: I've updated the patch
[17:41] <tedg> cimi_, Sweet!
[17:41] <cimi_> tedg: https://code.launchpad.net/~cimi/indicator-messages/update-fixes-to-right-label-and-icon-dimension/+merge/55377
[17:41] <cimi_> ubot5: you're stupid
[17:43] <tedg> cimi_: What happened to all the old revisions?
[17:43] <Cimi> tedg: I've created a new branch
[17:44] <tedg> cimi, Still, where are the older revisions?  Did you merge them in?
[17:44] <Cimi> yes
[17:51] <tedg> Cimi, I'm unclear on what you fixed in the lp:~cimi/indicator-messages/fixes-to-right-label-and-icon-dimension to branch to make it stop crashing.  Can you highlight that for me?
[17:52] <Cimi> tedg: it was not crashing before
[17:52] <Cimi> tedg: was your own branch maybe
[17:52] <Cimi> I just updated it to trunk and using gvariant
[17:53] <Cimi> tedg: I've just grabbed a clean version from trunk, applied that, installed... works
[17:53] <tedg> Cimi, Uhm.  It crashes in time, what did you do to test?
[17:53] <Cimi> tedg: I've tested with empathy, gwibber, evolution
[17:53] <Cimi> tedg: where does it crash for you?
[17:53] <Cimi> do you have a reproduciable case? a bt?
[17:53] <tedg> Cimi, After about an hour or two of use.
[17:54] <tedg> Cimi, Nope.
[17:54] <Cimi> tedg: ok, let's keep it opened
[17:54] <tedg> Cimi, I think that I commented to that extent on the merge request.
[17:54] <Cimi> no iirc tedg
[18:14] <Cimi> tedg: you didn't say anything about any issue in the previous merge request
[18:14] <Cimi> tedg: just a general "messaging menu gets corrupted every so often"
[18:15] <Cimi> tedg: I'm not experiencing any of this, could you please try my branch again in a clean installation?
[18:15] <Cimi> tedg: here was working fine, and is working fine
[18:15] <Cimi> tedg: I can't reproduce your issues at all, and the code seems quite ok
[18:20] <tedg> Cimi, Okay, so why don't your run that version for a couple of days and get back to me.  It's going to be on the order of hours.  I'd also recommend running liferea, as it hits the menu pretty hard.
[18:20] <Cimi> tedg: ok I am running it
[18:26] <Cimi> tedg: what kind of corruption did you have?
[18:26] <tedg> Cimi, The menu lost all it's entries.  And other menus would as well.
[18:26] <tedg> Cimi, Probably a stray pointer of some such.
[18:27] <Cimi> could be, i bet the font dimensioin tedg
[18:27] <Cimi> AndreaAzzarone: would you mind fixing a bug for ayatana-scrollbars? :)
[18:28] <AndreaAzzarone> cimi, telle me! :)
[18:28] <AndreaAzzarone> *tell
[18:29] <Cimi> AndreaAzzarone: https://bugs.launchpad.net/ayatana-scrollbar/+bug/736992
[18:29] <Cimi> AndreaAzzarone: should be trivial to fix, we need to deal with dimensions
[18:30] <Cimi> like translating absolute coordinates (whole screen) into relative dimensions
[18:30] <Cimi> (per monitor)
[18:31] <AndreaAzzarone> Cimi, there is already a branch... lp:~bilalakhtar/ayatana-scrollbar/fix-736992
[18:31] <Cimi> AndreaAzzarone: broken
[18:32] <Cimi> AndreaAzzarone: that branch does nothing
[18:32] <AndreaAzzarone> Cimi, ok i will look to that!
[18:32] <Cimi> gord: ^^
[18:33] <Cimi> AndreaAzzarone: grande!
[18:33] <AndreaAzzarone> Cimi, :)
[18:36] <AndreaAzzarone> Cimi, There is an expiry date? Because i don't know if i can fix today! :(
[18:36] <Cimi> AndreaAzzarone: when you want, better before thursday
[18:37] <Cimi> AndreaAzzarone: otherwise next thursday
[18:37] <AndreaAzzarone> Cimi, thursday should be ok!
[18:37] <Cimi> awesome
[19:47] <fta> smspillaz, yt?
[20:13] <Islington> how can I bother about mech in ubuntu store?
[20:13] <Islington> *merchandize
[21:39] <nhaines> Grr, I can't pull the Unity panel down to restore a maximized window today.  :(
[22:48] <coz_> hey all
[23:14] <hv> the shortcut key for the unity launcher behaves strange: <Super> is mapped to show-launcher, but even when I press <Super>Tab, the launcher shows up. It is as if the keys pressed very shortly after <Super> are being ignored.
[23:15] <hv> s/strange/strangely
[23:16] <nhaines> hv: Super-Tab no longer works for me as a window flippy deal.
[23:17] <hv> nhaines: maybe it is set to Alt-Tab for you?
[23:18] <nhaines> hv: that's just the standard window switcher for me.
[23:18] <hv> nhaines: I have to hold <Super>, pause a moment, and then pres Tab for it act properly.
[23:19] <nhaines> hv: in Ubuntu 10.10 (for example), it displays all windows and lets you "flip" through them with an animation.  So I presumed that maybe you were looking for that.
[23:19] <nhaines> hv: If you've remapped Alt-Tab to Super-Tab, then that's another issue.  :)
[23:20] <hv> nhaines: there are a bunch of switcher plugins for compiz, that one is called shift I guess.
[23:20] <hv> nhaines: even if I did that it should still work
[23:20] <nhaines> hv: I was just thinking that a default install of natty does not have anything mapped to Super-Tab.
[23:21] <nhaines> So if you've customized it, then yes it should work as you intend.
[23:21] <hv> nhaines: you can enable the shift plugin in gconf-editor if you want.
[23:25] <hv> nhaines: my the problem is with the [apparently] screwed up logic used for showing the launcher: When another shortcut key matches the launcher should not still show up. currently, the shortcut key you pressed (e.g. Super+W, if you pressed them fast enough) is acted upon and ADDITIONALLY the launcher show up!