[05:32] <kamstrup> kenvandine: good morning :-) I pushed up some updates to the dee gir stuff on lp:~unity-team/dee/gir-fixes. It's still not working perfectly but it's getting there...
[07:00] <kvalo> morning
[07:00] <kvalo> kamstrup: you are up really early!
[07:04] <kamstrup> kvalo: yeah :-S
[07:05] <kamstrup> kids got me up at 5:00
[07:05] <kvalo> kamstrup: ouch
[07:05] <kvalo> kamstrup: I feel the pain
[08:12] <MacSlow> greetings
[08:16] <didrocks> good morning
[08:16] <kvalo> MacSlow, didrocks: good morning guys
[08:16] <MacSlow> hey kvalo, didrocks
[08:16] <didrocks> hey kvalo, MacSlow
[08:17] <kvalo> kamstrup: hey, what was the best way to create a vapi file from gir?
[08:17] <kvalo> kamstrup: or should I do it manually? I need to use libconnman from vala
[08:23] <kamstrup> kvalo: I use http://paste.ubuntu.com/551411/
[08:24] <kamstrup> kvalo:  and AC_PATH_PROG([VALA_API_GEN], [vapigen]) in configure.ac
[08:25] <kvalo> kamstrup: looks good. thanks!
[08:42] <kamstrup> hmmm... i just installed some python -dev and -dbg packages and now pygi no longer loads the override modules...
[08:42] <kamstrup> any ideas anyone?
[08:50] <kvalo> what on earth is "national and Latin mode" keyboard-configuration? natty upgrade is asking me about it
[09:03] <kamstrup> kvalo: yeah, I got that question about 4 times...
[09:03] <kamstrup> kvalo: and now the keyboard indicator swicthes me to US layout every now and then
[09:11] <kvalo> kamstrup: I actually use US layout most of the time
[09:26] <kamstrup> ronoc: woohoo, the latest valac does indeed clear up a lot of the dbus warnings (not all though)
[09:27] <ronoc> kamstrup, excellent, just updating now
[09:32] <ronoc> session restart
[10:05] <klattimer> dbarth_: why is your internet SO bad?
[10:32] <rodrigo_> njpatel, can you please have a look at this merge proposal -> https://code.launchpad.net/~rodrigo-moya/unity/no-warnings/+merge/45231 ?
[10:34] <njpatel> rodrigo_, approved, are you able to merge
[10:34] <njpatel> or should I?
[10:34] <rodrigo_> njpatel, no, can't merge afaik
[10:34] <njpatel> okay, will try and do  it before I head off
[10:35] <njpatel> rodrigo_, thanks
[10:36] <rodrigo_> njpatel, thanks to you :-)
[10:38] <njpatel> merged :)
[11:08] <coz_> good day guys
[11:09] <spikeb> hi
[11:11] <coz_> spikeb,  hey guy
[12:03] <kamstrup> didrocks: my latest upgrade corrupted /var/lib/dpkg/available do you know how I can regenerate it?
[12:04]  * kamstrup was hoping apt-get update would be enough, but alas
[12:04] <didrocks> kamstrup: I think that's a question for mvo :)
[12:46] <KuriKai> if someone was to make an indicator applet for gnome-control-centre (the network proxy part) where should it go?
[12:46] <KuriKai> should it go in it's own indicator?
[12:58] <kvalo> kamstrup: I updated now https://code.launchpad.net/~kvalo/indicator-network/settings-vala-convert/+merge/45244
[12:59] <kvalo> kamstrup: yikes, how can an update break the available file?
[13:48] <kenvandine> kamstrup, cool, thx
[13:51] <kamstrup> kenvandine: the gir stuff is shaping up, but pygi has a weird bug marshalling an array of gvariants... setting it to NULL somewhere even though I've stepped through and the variants are parsed from Python -> C correctly and everything...
[13:52] <kamstrup> kenvandine: meaning that all the append() prepend() methods etc can't work... meaning you can't put stuff in your models :-)
[13:54] <kenvandine> ugh
[13:55] <kamstrup> indeed
[14:03] <kenvandine> kamstrup, can you file a bug for that? or talk to tomeu or someone?
[14:03] <kamstrup> kenvandine: already on it :-)
[14:03] <ronoc> kenvandine, how was that release, if you had a chance (looked like you were busy with ted's babies)
[14:04] <kenvandine> ronoc, next thing on my todo list :)
[14:04] <kenvandine> although i might review it today and wait until monday to upload
[14:04] <spikeb> I say this every so often, but it is true - I think you guys are doing a great job on Unity and related stuff
[14:04] <kenvandine> ronoc, don't want to break things right before we all travel
[14:04] <kenvandine> spikeb, thx :-D
[14:04] <ronoc> kenvandine, sounds good
[14:05] <kenvandine> kamstrup, tomeu might be familiar with it already
[14:05] <kenvandine> ronoc,  i hate breaking ubuntu right before we all get on airplanes
[14:06] <kamstrup> kenvandine: I talked to tomeu earlier today... he recommended using gslist or glist instead of arrays, but that's not really an option in the given context
[14:06] <kenvandine> :/
[14:07]  * kenvandine just realized i wasn't auto-joining those channels on gimpnet
[14:37] <kenvandine> tedg, good morning
[14:37] <kenvandine> tedg, btw, i noticed i am now getting the wrong icons for appindicators
[14:38] <spikeb> oh dear
[14:38] <kenvandine> all the other indicators have the right icons
[14:38] <kenvandine> spikeb, don't worry, this is using his crack gdbus branch for libappindicator
[14:38] <kenvandine> not in natty yet :)
[14:38] <spikeb> ahh okay
[14:39] <tedg> Good morning kenvandine
[14:39] <kenvandine> tedg, so two things... gnome-power-manager is getting the other icon, not the mono one
[14:39] <kenvandine> and
[14:39] <kenvandine> bluetooth is getting the virtualbox icon
[14:39] <tedg> kenvandine, Hmm, that's odd.  I'm getting the correct icons on my machine.
[14:39] <spikeb> haha
[14:39] <tedg> kenvandine, It must have gotten out of sync?
[14:40] <kenvandine> tedg, and it happens across reboots
[14:40] <kenvandine> consistently the same wrong icons :)
[14:40] <tedg> kenvandine, Woah!  Really?
[14:40] <kenvandine> the appindicator right next to the bluetooth one happens to be indicator-virtualbox
[14:40] <kenvandine> oh... and to top it off...
[14:40]  * tedg didn't know there was an indicator-virtualbox
[14:41] <kenvandine> nm-applet looks like it has the mono icon
[14:41] <kenvandine> yup
[14:41] <kenvandine> it's very cool ;)
[14:41] <kenvandine> let me remove the virtualbox indicator and see if it stops breaking
[14:42] <spikeb> i saw something on omg! ubuntu the other day about a virtualbox indicator
[14:45] <Amaranth> oh, the fix for my issue was in NotifyStateChange
[14:45]  * Amaranth was poking IsWindowMaximized
[14:46] <Amaranth> I guess I should have grep'ed for MAXIMIZE_STATE instead of maximize
[14:46] <Amaranth> Although i did -i so I'm surprised I didn't find that
[14:46] <Amaranth> oh well
[14:49] <jcastro> the proper name for min/max buttons is ... window decorators?
[14:49] <jcastro> or window controls? or something like that?
[14:52] <Amaranth> jcastro: The decorator is the entire top bar and (depending on theme) side and bottom bars around the window
[14:53] <Amaranth> Not sure what you'd call just the buttons
[15:04] <didrocks> Amaranth: yeah, quite funny you just notice it the day I fixed it :)
[15:08] <dbarth> didrocks: i'm looking at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/526642
[15:08] <kenvandine> tedg, appindicator icons are fine in the classic panel and in indicator-loader
[15:08] <kenvandine> just get messed up in unity
[15:08] <dbarth> didrocks: can this one be dropped from the natty list, since its against compiz 0.8
[15:09] <dbarth> ?
[15:09] <tedg> kenvandine, Cool.  Then it's obviously njpatel's problem now ;)
[15:09] <kenvandine> tedg, and.... removing indicator-virtualbox means i get the bluetooth icon for the bluetooth indicator
[15:09] <kenvandine> but...
[15:09] <didrocks> dbarth: agreed, there are little chance to get a fix now
[15:09] <kenvandine> changing bluetooth state doesn't change the icon
[15:10] <kenvandine> i bet it has something todo with rebuilding unity against this crack version of dbusmenu :)
[15:10] <tedg> kenvandine, Oh, you did that?
[15:10] <kenvandine> yup
[15:10] <tedg> kenvandine, Don't do that :)
[15:10] <kenvandine> wouldn't work without it!
[15:10] <kenvandine> well, maybe it would
[15:10] <tedg> kenvandine, The problem is that one of the signals changed and GTK has no typechecking on signals, so it could be sending wrong data.
[15:11] <tedg> kenvandine, It needs my menu proxy fix, but it should build with that and the old dbusmenu.
[15:11] <kenvandine> sigh...
[15:11]  * kenvandine feels like he is walking on a tight rope
[15:11] <tedg> You really can't just change the pkgconfig line and hope things will work.
[15:12] <tedg> kenvandine, the gtk transition one, the gir transition one, or the dbusmenu transition one?  ;)
[15:12] <kenvandine> good times
[15:12] <kenvandine> well i can hope!
[15:12] <kenvandine> ok... so we also really need unity to be ported too
[15:12] <tedg> Yes, or it will become FTBFS.
[15:12] <kenvandine> so we are having fun now!
[15:13] <dbarth> didrocks: how do you remove it from the list, ie "un-track" it?
[15:13] <kenvandine> tedg, you know how i feel about making things FTBFS right?
[15:13] <kenvandine> :-D
[15:14] <kenvandine> tedg, so we need all the indicators ported to gdbus
[15:14] <kenvandine> and unity ported to dbusmenu-0.4
[15:14] <tedg> kenvandine, indicators to dbusmenu-0.4 as well.
[15:14] <kenvandine> tedg, apparently the indicator ports are easy...
[15:15] <tedg> They shouldn't be too bad.
[15:15] <kenvandine> how easy is the dbusmenu-0.4 port?
[15:15] <didrocks> dbarth: I just added a maverick series and invalidate the natty one
[15:15] <tedg> It's pretty easy, you just need to check to see if it's using GValue anywhere.  If so, just change it to GVariant
[15:15] <tedg> *most* people don't as it was an internal thing.  But need to check.
[15:19] <dbarth> didrocks: ok, thanks
[15:20] <didrocks> yw :)
[15:23] <ronoc> jcastro, did you  ever find anyone to do the mono bindings for gsettings ?
[15:23] <jcastro> alan was looking at it, I'll catch up with him today
[15:23] <jcastro> thanks for the reminder
[15:26] <kenvandine> i guess it is time to polish up a belt buckle, or they won't let me
[15:27] <ronoc> jcastro, cool
[15:28] <jcastro> ronoc: are you going to fosdem by any chance?
[15:28] <kamstrup> kenvandine: I filed https://bugzilla.gnome.org/show_bug.cgi?id=638915 for the gvariant marshalling issue if you care :-)
[15:28] <ronoc> jcastro, no, just the LAC later in the year so far
[15:29] <kenvandine> kamstrup, oh i care... thx!
[15:43] <Amaranth> jaytaoko: do you have a computer that uses an open source graphics driver? at least the intel driver and anything based on the gallium stack actually supports EGL and GLES2 on the desktop with hardware acceleration
[15:45] <jaytaoko> amaranth: yes, I have 2 systems with intel gpu
[15:45] <Amaranth> although for intel you need to do export EGL_DRIVER=egl_dri2 otherwise it uses egl_gallium so you'll get broken software rendering
[15:46] <kvalo> kamstrup: hi. I'm going to merge https://code.launchpad.net/~kvalo/indicator-network/settings-vala-convert/+merge/45244 unless you have any objections
[15:46] <jaytaoko> amaranth: I haven't done anything with EGL, but you are saying that the intel driver has a GLES2 compatibility mode?
[15:47] <Amaranth> jaytaoko: yep, it even supports the egl version of texture_from_pixmap :)
[15:47] <kamstrup> kvalo: i'll have a quick scan
[15:47] <mterry> unity trunk doesn't compile with latest valac it seems?  Anyone seen errors like "Argument 2: Cannot convert from `GLib.realloc' to `size_t'" ?
[15:47] <kvalo> kamstrup: thanks. just take a look at my latest commit
[15:47] <kvalo> kamstrup: it's pretty small and that's all I changed
[15:48] <jaytaoko> amaranth: interesting! has this been announced somewhere? Is there some support on how to get started?
[15:48] <kamstrup> kvalo: looks fine at a glance
[15:48] <kvalo> kamstrup: thanks, I'll merge it then
[15:48] <Amaranth> jaytaoko: just install libegl-mesa and libgles2-mesa, stick that export in your .bashrc, and start using it
[15:49] <ronoc> kenvandine, I got to leave early
[15:49] <Amaranth> jaytaoko: I don't remember any announcement other than the gallium support for it but there is some sort of software rendering for it as well as the intel driver accelerating it
[15:49] <kenvandine> ronoc, i'll see you in dallas!
[15:49] <jaytaoko> amaranth: thanks for the tip!
[15:50] <ronoc> kenvandine, cool, lets figure it out there, I take it you have not had a chance to look at the release ?
[15:50] <kenvandine> i looked some
[15:50] <Amaranth> jaytaoko: no problem
[15:50] <kenvandine> ronoc, getting back to a sane unity before testing it though
[15:50] <kenvandine> ronoc, i think it'll be fine.. :)
[15:50] <Amaranth> it's much nicer to just compile and run rather than crossbuild, transfer to device, and run on a different screen
[15:50] <kenvandine> we'll get it uploaded on monday
[15:51] <ronoc> kenvandine, ah cool,  it should be
[15:51] <ronoc> kenvandine, grand sounds good
[15:51] <kenvandine> have a good trip!
[15:51] <Amaranth> jaytaoko: just try to avoid the extensions if possible, I think the mesa stack supports pretty much all of them but afaik most actual devices don't
[15:51] <ronoc> kenvandine, you too !  I'll be around for a bit more.
[15:53] <Amaranth> jaytaoko: oh, it's libegl1-mesa
[15:53] <jaytaoko> amaranth: ok
[16:05] <tedg> kenvandine, FYI, I'm landing this in trunk now.  So you can start looking at using it for Gwibber: https://code.launchpad.net/~ted/libindicate/always-interest-signal/+merge/45485
[16:09] <mterry> DBO, could https://code.launchpad.net/~mterry/unity/modelines/+merge/43565 get a 'what, what' before it runs into conflicts again?
[16:09] <mterry> (or anyone really)
[16:14] <mterry> What's an easy way to test unity, like inside a window or something, so I don't have to restart compiz?
[16:15] <Amaranth> mterry: virtualbox :)
[16:15] <jcastro> is occasional unity-sucking-in-all-my-mouse-clicks "normal" or known about? I can't quite figure out what's going on, but it has to be something mouse click related
[16:15] <mterry> Amaranth, OK.  I thought there was a cleverer way, but I can do that
[16:15] <Amaranth> jcastro: does it act like button1 is held down?
[16:15] <Amaranth> mterry: restarting compiz is easier :)
[16:15] <mterry> Amaranth, agreed  :)
[16:15] <jcastro> Amaranth: no, I just lose all ability to click on anything, keyboard stuff works fine though
[16:15] <mterry> At least, faster
[16:16] <Amaranth> mterry: just make sure compiz isn't running when you copy over the new unityshell.so, guaranteed crash there
[16:16] <mterry> hmm, ok
[16:16] <Amaranth> I still haven't figured out why installing a package update that updates compiz plugins is fine but manually copying one in to /usr/lib/compiz/ crashes
[16:18] <didrocks> Amaranth: hum, I regularly do that (well, I sudo make install, so in ~/.compiz-1), and I get no crash
[16:18] <Amaranth> didrocks: yeah, I guess it doesn't always crash for me either
[16:18] <Amaranth> didrocks: but it happened both times I built a new unityshell.so while trying to figure out that maximize bug
[16:18] <didrocks> Amaranth: bad luck then :)
[16:19] <didrocks> Amaranth: think about assigning the bug to yourself to avoid conflicts btw
[16:19] <mterry> didrocks, ooh, quick on the valac-0.12 branch.   If you're in the merging mood, I have another I'd like to get done before it hits conflicts again: https://code.launchpad.net/~mterry/unity/modelines/+merge/43565
[16:19] <didrocks> oh, you didn't find the duplicate, it's true, nevermind :)
[16:19] <didrocks> mterry: I looked at it, let me look at it again :)
[16:20] <didrocks> Amaranth: it's weird that launchpad wasn't showing the other bug when you filed it, the title were quite similar. Still a long way to go
[16:20] <Amaranth> didrocks: oh, I filed the bug once I gave up on the fix
[16:21] <Amaranth> didrocks: I even had launchpad search the unity bugs for "maximize" and "maximise", didn't find that one
[16:21] <om26er> will there be a unity release today?
[16:21] <mterry> om26er, word is no
[16:21] <om26er> :/
[16:22] <didrocks> om26er: there won't, some people in the team were sick and so no release. As we are all travelling to Dallas this week-end, it's not safe to potentiallly push a buggy version :)
[16:22] <Amaranth> because njpatel is still out, right?
[16:22] <coz_> is the daily build working yet/
[16:23]  * om26er grabs from trunk now :p
[16:23] <didrocks> Amaranth: that's weird… but well, nevermind. What would be cool is to be able to look for package and upstream bugs in one search btw :)
[16:23] <didrocks> mterry: hum, as there are still a lot of branch to merge and you will make everyone angry with conflicts, maybe the rally is the right time to merge it and make everyone sync to it, what do you think?
[16:23] <didrocks> mterry: like, just after next Thursday release
[16:24] <didrocks> coz_: the daily build is partially fix, but we need to make a nux release for fixing everything
[16:24] <didrocks> fixed*
[16:25] <mterry> didrocks, or, I could take out the bits that changed indenting, and just add modelines.  That is unlikely to conflict
[16:25] <didrocks> mterry: oh sure in that case
[16:32] <and471> kvalo, this better?
[16:33] <kvalo> and471: oh yes. welcome :)
[16:33] <and471> hehe
[16:33] <kvalo> and471: kamstrup and mpt also hangaround here
[16:33] <and471> ok
[16:33] <and471> well I will let you get on with packing :)
[16:33] <and471> kvalo, have a good time in dallas
[16:34] <kvalo> and471: thanks. and good luck with exams! I wll come back later in the evening, though. I'll try to merge your latest changes to trunk
[16:34] <and471> hey mpt
[16:34] <and471> thankyou :)
[16:34] <kvalo> mpt: hi. good stuff with the spec updates
[16:34] <and471> mpt, you have a good christmas/new years ?
[16:37] <and471> kvalo, if I am working this evening on flight mode stuff, should I base it off of settings-vala-convert or settings-vala-port? lp:indicator-network doesn't have the vala stuff yet
[16:39] <kvalo> and471: oops, forgot to push. give me a min
[16:39] <and471> no problem
[16:40] <mpt> and471, warm, sunny, and full of truffles
[16:40] <mpt> and471, how was yours?
[16:41] <and471> mpt, hehe, very different but good :)
[16:42] <and471> mpt, just one question for you today (he said) what does 'Show network status in the menu bar' do? https://wiki.ubuntu.com/Networking?action=AttachFile&do=get&target=settings-window-flight-mode.png
[16:42] <mpt> and471, that's for whether the menu is present at all.
[16:42] <mpt> and471, I just haven't migrated it to the other wireframes yet.
[16:42] <and471> ah okay
[16:42] <and471> mpt, so menubar is panel
[16:42] <and471> ?
[16:43] <mpt> Menu bar is to Unity as panel is to Gnome 2
[16:43] <and471> cool thanks
[16:44] <mpt> So for example, if it's a desktop machine that always always connects by Ethernet, you probably don't want the menu taking up space in the menu bar
[16:45] <mpt> so you uncheck the checkbox
[16:45] <and471> yeah that makes sense
[16:45] <kvalo> and471: pushed now. sorry for taking so long, I had weird bzr conflicts
[16:45] <and471> kvalo, thats no problem
[16:46] <kvalo> and471: so please lp:indicator-network from now on.
[16:46] <mpt> Are menus working in Unity today? :-)
[16:46] <and471> kvalo, yup
[16:46] <mpt> When I installed on the 4th they were all invisible
[16:47] <kvalo> mpt: I need to always left click the desktop background image to see the menus
[16:48] <mterry> didrocks, https://code.launchpad.net/~mterry/unity/modelines/+merge/43565 again
[16:48] <kvalo> mpt: here's a bug about the issue: https://bugs.launchpad.net/unity/+bug/693073
[16:51] <didrocks> mterry: done
[16:51] <mterry> didrocks, sweet!  /me tabs to his hearts content
[16:51] <didrocks> :)
[16:53] <kenvandine> didrocks, for some reason, if i rebuild unity there are symbols being removed from libunity3
[16:54] <kenvandine> even rebuilding with no change...
[16:54] <didrocks> kenvandine: yeah, it's depending on your build-dep
[16:55] <kenvandine> pbuilder for natty
[17:21] <and471> mpt, you you mind if instead of just using an (unresizable) hbox, that I use a (resizable) hpane? http://imgur.com/H2iru
[17:21] <tedg> ronoc, Did you see doctormo's post on ayatana-dev?  Do you have a custom menuitem done in Vala that you could give him a link to?
[17:23] <DBO> mterry, sorry was on the netbook, doing so now
[17:23] <mterry> DBO, didrocks got me covered, thanks
[17:23] <DBO> mterry, okay
[17:31] <and471> kvalo, there is an issue with trunk at the moment. GTKBuilder autconnect of signals isn't working
[17:31] <and471> kvalo, any idea what it is?
[17:33] <kenvandine> ronoc, indicator-sound is another one that needs to be ported to the new dbusmenu
[17:33] <kenvandine> sounds like more fun for next week
[17:34] <kenvandine> tedg saw what i was griping about and ran away :)
[17:40] <kvalo> and471: hmm, I don't know
[17:40] <mpt> and471, that's giving a 503 error at the moment
[17:41] <kvalo> and471: could these cause it: http://bazaar.launchpad.net/~kvalo/indicator-network/settings-vala-port/revision/18
[17:42] <and471> mpt, does this work? http://imagebin.org/131481
[17:42] <and471> kvalo, no, it would be in either main.ui, app.vala or main.vala
[17:43] <and471> kvalo, is it okay if we use 4 spaces as tab in *.vala files ?
[17:43] <kvalo> and471: I think unity has style guides for vala, it would be good if we can follow those
[17:44] <kenvandine> ronoc, ok... with indicator-sound 0.5.4 banshee won't play anything
[17:45] <kvalo> and471: https://wiki.ubuntu.com/Unity/CodingStyle
[17:45] <and471> kvalo, hmm, it is just that all is already done with spaces, and also I prefer them :)
[17:45] <mpt> and471, hm, what advantage is there to making it resizable?
[17:45] <and471> kvalo, also there are things like the use of 'this.'
[17:46] <and471> mpt, well some people may have smaller screens, in which case the default size we set may not be optimal
[17:46] <and471> mpt,  or they may have a normal size screen larger font, in which case they may want to use the extra space
[17:46] <and471> mpt, or larger icon theme... etc.
[17:46] <kvalo> and471: yeah, don't worry about style too much right now
[17:46] <mpt> and471, eventually it will go inside the System Settings window which won't be resizable anyway
[17:47] <and471> mpt, I am just worried that the arbitary size we set, won't be good for everyone, and so we should offer the ability for users to resize it, at the cost of adding size little lines
[17:48] <mpt> and471, I have no problem with the little lines. I just know that some measurable fraction of people will accidentally resize it and not know what they've done. :-)
[17:49] <mpt> and think that the pane is just always annoyingly narrow (or annoyingly wide)
[17:50] <and471> mpt, that is the same for software-center though :)
[17:50] <and471> mpt, is that not the problem that the widget is not user-friendly then?
[17:50] <mpt> and471, that's true. But (a) archive names vary in length much more than connection type labels do, and (b) I'm thinking of possibly getting rid of the left pane anyway
[17:50] <mpt> (in USC, I mean, not in the network settings)
[17:52] <nnnaji> mpt, (b) would be awesome, just sayin.. ;)
[17:52] <mpt> nnnaji, it needs a lot of rather boring design work first though
[17:53] <mpt> danrabbit has done some of it but not all
[17:54] <nnnaji> mpt, hehe.. i could imagine.. i'll do some more inkscape work next week, hopefully my inkscape skills will allow me to be of use at some point :S
[17:54] <mpt> that would be nifty
[17:55] <nnnaji> i really had to check the dictionary for "nifty"
[17:55] <nnnaji> :D
[17:58] <and471> mpt, I suppose what I would say to that is yes, there is a chance that people will resize it accidentally and thus it will not be optimal for them, however without a hpaned, there is a chance that it won't be optimal for people, when they themselves have not done anything (default)
[17:58] <and471> mpt, at least WITH the hpaned, there is the possibility of correcting either situation
[17:59] <mpt> and471, can you give an example of how it will be non-optimal by default?
[18:00] <and471> mpt, (when I say default, I am not saying default install settings, but default as in, they themselves have not resized it at all)
[18:00] <mpt> I understand
[18:00] <mpt> but all the connection type names are completely static
[18:00] <mpt> except if you have more than one wireless card, and then they're of the form "Wireless (wl0)"
[18:01] <mpt> So the pane just needs to be wide enough for the German translation of "Wireless (wl0)"
[18:01] <mpt> What am I missing?
[18:02] <and471> mpt, for example, here it is without the hpaned, and the 'high contrast Large print inverse' theme http://imagebin.org/131485
[18:03] <mpt> hmm
[18:03] <and471> mpt, and in other languages, it could be even less forgiving
[18:03] <mpt> yes
[18:03] <mpt> I think in the long run we should replace those accessibility themes with zooming and accessibility compositing features
[18:03] <mpt> but in the short run, you have a point
[18:05]  * mpt admires https://wiki.ubuntu.com/MenuLayout
[18:07] <and471> mpt, so are you giving the thumbs up to the hpaned?
[18:07] <mpt> and471, a thumb sideways. :-) I don't mind for now, but in the long run I think we won't need it.
[18:08] <and471> hehe okay :)
[18:08]  * mpt -> home
[18:51] <ronoc> kenvandine, right okay, it works with rb, I couldn't test with banshee on the account of banshee not exposing an mpris interface on dbus
[18:51] <ronoc> kenvandine, my banshee crashes when I try to play something
[18:51] <ronoc> even though i have the standard natty package
[18:52] <ronoc> kenvandine, can you check on dfeet if banshee is raising org.mpris.mediaplayer2.banshee
[18:53] <kenvandine> one sec
[18:53] <kenvandine> ronoc, fwiw, with indicator-sound 0.5.4 banshee did crash once
[18:53] <ronoc> obviously there is something up with my banshee install,
[18:53] <kenvandine> but i haven't had banshee crash in ages before 0.5.4
[18:54] <kenvandine> ronoc, it crashed for me when i tried to play something
[18:54] <ronoc> kenvandine, right well indicator sound is just calling mpris dbus methods so that would mean banshee's mpris interface is buggy
[18:54] <ronoc> i'm seeing this here also
[18:54] <ronoc> lets debug this Monday and release into the distro once we have it resolved
[18:54] <ronoc> I need to pack now
[18:54] <kenvandine> org.mpris.MediaPlayer2.banshee
[18:55] <kenvandine> from banshee
[18:55] <kenvandine> so just having i-s 0.5.4 keeps banshee from playing at all
[18:55] <kenvandine> downgrading i-s banshee is fine
[18:55] <kenvandine> we'll look on monday
[18:55] <ronoc> okay on my system it appears briefly and then disappears
[18:56] <ronoc> the dbus mpris interface that is
[18:56] <kenvandine> it stays fo rme
[18:56] <kenvandine> with i-s 0.5.3
[18:56] <ronoc> weird, have you tried 0.5.4 with rb
[18:56] <kenvandine> no, but i can
[18:56] <kenvandine> also...
[18:56] <kenvandine> with 0.5.4 i get a colored banshee icon
[18:56] <kenvandine> with 0.5.3 i don't
[18:57] <kenvandine> intentional?
[18:57] <ronoc> kenvandine, I know I have reopened that bug, thought I fixed that before xmas
[18:57] <kenvandine> ok
[18:57] <kenvandine> i get the mono one in 0.5.3
[18:57] <kenvandine> ok, more to debug :)
[18:57] <ronoc> yup
[18:57] <kenvandine> next week will be fun :-p
[18:57] <kenvandine> have a good trip
[18:57] <ronoc> cheers boss, speak Monday, good w/end
[19:34] <ronoc> kenvandine, just tested quickly it appears that 0.5.4 is crashing the banshee mpris interface, i.e. interface is fine all good, I run the new release and the interface disappears ! will investigate on route tmrw, can't see how I could be doing anything dodgy
[19:34] <ronoc> at start up the service scans the bus for mpris clients, must be this scan that banshee doesn't like
[19:34] <ronoc> rb doesn't mind though ...
[19:35] <ronoc> anyhoo, till anon
[19:57] <tedg> The GOP is honoring the heartwarming story of the homeless man by voting to take away his health care.
[19:57] <tedg> Oops, sorry.
[19:57] <nigelb> lol
[20:26] <Amaranth> dang, it seems no one is arriving in dallas around the same time as me
[21:15] <KuriKai> if someone was to make an indicator applet for gnome-control-centre (the network proxy part) where should it go?
[21:15] <KuriKai> should it go in it's own indicator?
[21:38] <sense> KuriKai: There is already an indicator for Network Manager, I think it would be best to have one single indicator for every part of the system, so one network indicator. But if you want to write your own, not meant for inclusion in the default installation, then you should use Application Indicators.
[21:38] <KuriKai> ok, thanks :)
[21:41] <sense> you're welcome
[21:48] <Omega> Hey Ayatana, just wanted to let you know that you guys rock.
[22:37] <coz_> mm trying to open quadrapassel ;   failed to create drawable
[22:37] <coz_> Failed to initialise clutter: Unable to select the newly created GLX context