[03:18] <PsxMeUP> anybody know if Unity will have decent ATI graphics driver support? My laptop's fan (HP nx9420 - Mobility Radeon X1600) will thank you if it does (lol)
[03:22] <spikeb> PsxMeUP, yes.
[03:23] <spikeb> PsxMeUP, unity will support running on ati decently. whether the driver itself is any better or not, we cant say
[03:24] <hyperair> PsxMeUP: if compiz works on ati, then unity will, because it's essentially a compiz plugin, afaik
[03:27] <PsxMeUP> hmm, ok. Well I don't have problems with compiz and all that jazz (Mint 8). But the fan simply doesn't know when to calm down. It does that in Windows too, but XP/7 has a useful feature that allows you to select "Maximum Battery Life". That immediately calms things down
[03:29] <spikeb> tried that under mint?
[03:30] <PsxMeUP> Ya, so far I haven't been able to find anything similar and I've tried various packages/tools
[03:31] <spikeb> hmm yeah i see that
[03:31]  * spikeb just checked
[03:35] <PsxMeUP> in Win 7 it's under Power Options > Advanced Settings > ATI PowerPlay Settings. Anyway... I'm happy you're finally moving away from the old Windows taskbar look and going with something more original :)
[03:37]  * spikeb mutters
[03:37] <spikeb> eventually, support will be better for your chipset and fan
[06:47] <kvalo> morning
[07:20] <didrocks> good morning
[07:23] <kvalo> didrocks: good morning. how are you?
[07:23] <didrocks> kvalo: I'm fine, thanks, and you?
[07:23] <kvalo> didrocks: I'm good, thanks
[07:24] <kvalo> didrocks: had few extra heartbeats yesterday because of the exim vulnerability
[07:25] <didrocks> kvalo: exim vulnerability? Sorry I didn't follow that
[07:25] <kvalo> didrocks: http://www.debian.org/security/2010/dsa-2131
[07:26] <kvalo> didrocks: I heard about it on friday but didn't pay enough attention. but on sunday my vm provider sent me email demanding immeadiate update. they had two breakins already at that time.
[07:28] <didrocks> kvalo: waow, right, scary :/
[07:49] <TheMuso`> kvalo: Its insidents such as you have described which justify my personal decision to use shared/administered hosting, even if I lose a little flexibility. I don't want to have to worry myself over such possibilities and keep things up to date etc. Any services I open up on my home connection are checked for sure, but I don't serve mail from home. :)
[07:50] <TheMuso`> incidents*
[07:51] <reno1979> hello?
[07:53] <kvalo> TheMuso`: yes, it makes a difference. it's a lot of work to maintain a server.
[12:12] <ronoc> seb128, should i use gsetting or gconf ?
[12:13] <ronoc> seb128, was researching the different ways I need to handle this new sound menu registration per application settings
[12:13] <ronoc> i heard gconf is deprecated
[12:22] <nmarques> kenvandine, ping
[12:27] <seb128> ronoc, hey, gconf is deprecated indeed
[12:27] <seb128> ronoc, use gsettings for new code
[12:27] <ronoc> seb128, cool looking at it new
[12:42] <ronoc> seb128, just trying to work out the best way for this registration process, have you a sec ?
[12:43] <seb128> yes
[12:43] <ronoc> when a client starts i will be notified by watching the dbus mpris interface
[12:43] <ronoc> currently i then request the desktop file
[12:44] <ronoc> can i , from information that is already in the desktop file, find a relevant entry in gsettings
[12:44] <ronoc> sorry haven't used gsettings before
[12:44] <ronoc> so newb questions galore
[12:45] <ronoc> so for instance banshee starts, I detect the new mpris interface, fetch the desktop file (via mpris)
[12:45] <ronoc> and then from there check to ensure in gsettings that  banshee wants to be seen in the desktop file ?
[12:45] <ronoc> sound plausible ?
[12:46] <seb128> hum
[12:47] <nmarques> anyone can gimme some guidance? trying to build indicator-sound but getting a nasty error
[12:47] <seb128> ronoc, gsettings is just an api for settings
[12:47] <seb128> ronoc, it's not really different from using a key file or gconf
[12:47] <seb128> ronoc, what would set those entries on wheter a software should be listed?
[12:47] <seb128> ronoc, the indicator?
[12:47] <ronoc> nmarques, whats the error
[12:48] <nmarques> ronoc, error: Package `Dbusmenu-Glib-0.2' not found in specified Vala API directories or GObject-Introspection GIR directories
[12:48] <nmarques> ronoc, missing a patch somewhere? maybe vala ?
[12:48] <ronoc> seb128,  packages could ship a gsettings schema in a /indicator-sound/clients/ registry subdir or something?
[12:49] <ronoc> seb128, and if the users wishes to make the client invisible to the menu the prefs ui would simple change this setting
[12:49] <seb128> ronoc, so you envision the clients to ship a true or false key?
[12:50] <seb128> ronoc, why would some client not want to be listed in the indicator?
[12:50] <ronoc> seb128, it is more to allow the user to easily make a client invisible to the menu
[12:50] <ronoc> seb128, currently once its 'remembered' the user needs to edit a cache file to remove it
[12:51] <ronoc> not very nice
[12:51] <ronoc> nmarques, do you have dbusmenu dev package ?
[12:51] <seb128> well it seems you doesn't need any package for that
[12:51] <ronoc> it should have the vapi you are missing
[12:51] <seb128> just key a list in a key and let user edit it
[12:53] <ronoc> seb128,  so you suggest I should manage the gsetting myself and inform the clients what key to look for when changing their preferences
[12:55] <nmarques> ronoc, yeap
[12:56] <ronoc> nmarques, so can you find a similarly named vapi in /usr/share/vala/vapi*
[12:56] <ronoc> it might be in the wrong directory
[12:56] <ronoc> nmarques, what vala are you running ?
[12:57] <seb128> ronoc, well you didn't say there would be a preference for that in the player before
[12:57] <nmarques> 11.2
[12:57] <seb128> ronoc, I though you just wanted the equivalent of a gconf key where people can list things they don't want in the indicator
[12:57] <nmarques> ronoc, need to check out this vapi stuff
[12:57] <seb128> ie power user thing
[12:58] <ronoc> seb128, okay so we need to be able to provide the ability for users to easily optin  a player or opt out a player
[12:58] <ronoc> at any time
[12:58] <ronoc> obviously the service / indicator will need to be restarted to take effect
[12:59] <seb128> you want that to be power user options?
[12:59] <seb128> to come from settings in each player?
[12:59] <seb128> or to come from an indicator dialog?
[12:59] <ronoc> seb128, each player
[12:59] <ronoc> as the spec outlines
[12:59] <ronoc> so far the work has been done to certain extent in each player
[13:00] <ronoc> quick recap
[13:00] <ronoc> player starts, i see the mpris interface come up, I try to load the desktop file from the root mpris object
[13:00] <ronoc> if all is good and then need to check 'somewhere' that this player wants to shown in the menu
[13:00] <seb128> well, you have some libindicate code in the player as well?
[13:01] <seb128> like a "register as ayatana"?
[13:01] <ronoc> seb128, thats going away very shortly once I get a new registration process outlined
[13:01] <seb128> hum ok
[13:01] <ronoc> its a good thing no ?
[13:01] <seb128> I was going to suggest to make the option in the player make this call being done or not done
[13:02] <seb128> which would mean you wouldn't need any extra key
[13:02] <nmarques> ronoc, my dbusmenu package has no vapi files... :(
[13:02] <seb128> nmarques, what distribution do you use?
[13:02] <nmarques> seb128, I'm tryng to build this on opensuse
[13:02] <ronoc> " make this call being done or not done" what do you mean by this ?
[13:02] <seb128> seems your libdbusmenu package is incomplete
[13:03] <ronoc> seb128, ^
[13:03] <seb128> ronoc, well, the "register on ayatana"
[13:03] <seb128> that's what makes the player be listed now
[13:03] <nmarques> seb128, just one question more... any software needs to be patched for dbusmenu ?
[13:03] <seb128> if you add a preference in banshee, it would be banshee using the preference to register or not on the ayatana bus
[13:03] <seb128> nmarques, no
[13:04] <ronoc> seb128, well there is no registration as such just a flag, it will bring up the mpris interface regardless
[13:04] <ronoc> that is all i need
[13:05] <seb128> well mpris != sound indicator
[13:05] <seb128> you might want to use mpris but not the indicator
[13:05] <ronoc> exactly
[13:05] <ronoc> that is why i need this flag
[13:05] <seb128> but right now if you don't do that ayatana libindicate registration the indicator doesn't list it, does it?
[13:05] <ronoc> so i need to be able to get from some entry in the desktop file to a gsetting
[13:06] <ronoc> not in any current release
[13:06] <ronoc> but trunk has the new mpris interface watching registration merged in
[13:06] <seb128> ok
[13:08] <seb128> ronoc, so yeah, it seems you want to set a convention
[13:08] <ronoc> seb128, yup
[13:08] <ronoc> seb128, forwarding on an email i sent last week to the mailing list
[13:08] <seb128> like the settings path is "/desktop/ayatana/indicator/<player>"
[13:08] <seb128> where player is the .desktop name
[13:08] <seb128> which is a boolean key
[13:10] <ronoc> seb128, okay just so we are on the same page, in gsettings you are suggesting  there should be a "/desktop/ayatana/indicator/<player>" entry with a boolean value
[13:10] <seb128> njpatel, I still get the "empathy buddy list" issue
[13:10] <ronoc> my food is ready, continue this after lunch seb ?
[13:11] <ronoc> seb128, ^
[13:11] <seb128> ronoc, ok, enjoy your lunch
[13:11] <seb128> ronoc, and yes, though the path was an example
[13:11] <seb128> you should probably check with ted what he's using
[13:11] <ronoc> cool understood
[13:11] <seb128> having a consistent naming schemas for the indicator stack
[13:11] <ronoc> sure
[13:15] <nmarques> seb128, thing I got the source of the problem... GTK needs to be patched ;)
[13:45] <hyperair> ronoc: are you familiar with massif's output?
[13:46] <hyperair> ronoc: http://people.ubuntu.com/~hyperair/massif-output
[13:47] <hyperair> ronoc: that's valgrind's massif analyzing indicator-applet's memory usage. there's an interesting stack trace from indicator-sound that i can't seem to reproduce easily somewhere there that has allocated 45.6M of data
[13:48] <hyperair> and at that time i didn't have debug symbols so i can't figure out what function that was
[13:49] <hyperair> hmm there's only one function that calls gdk_pixbuf_new_from_file
[13:49] <hyperair> aha!
[13:49] <hyperair> ronoc: when you resize the album art, you don't free the original pixbuf!
[13:54] <hyperair> oh my god, metadata-widget.c is a mess of tabs and spaces.
[13:54] <hyperair> >_>
[13:54] <hyperair> i can't even tell what the setting is supposed to be
[13:55] <ronoc> hyperair, have you grabbed trunk ?
[13:55] <hyperair> ronoc: nope.
[13:55] <ronoc> hyperair, spacing problems should be fixed
[13:55] <hyperair> ronoc: i just grabbed maverick's package, which is where i'm seeing my memleaks.
[13:56] <hyperair> ronoc: could you look at metadata-widget.c, in metadata_image_expose()?
[13:56] <ronoc> sure
[13:56] <hyperair> there's this line here..
[13:56] <hyperair> 200             pixbuf = gdk_pixbuf_scale_simple(pixbuf,60, 60, GDK_INTERP_BILINEAR);
[13:56] <hyperair> see that?
[13:56] <hyperair> you need to free the original pixbuf.
[13:56] <hyperair> it leaks memory otherwise
[13:56] <hyperair> g_object_unref
[13:57] <hyperair> something like GdkPixbuf *orig_pixbuf = pixbuf; pixbuf = gdk_pixbuf_scale  blah blah; g_object_unref(orig_pixbuf);
[14:01] <ronoc> hyperair, ah of course
[14:01] <ronoc> whoops
[14:02] <hyperair> ronoc: =) so i was half-right when i said indicator-sound was at fault for my memleaks
[14:02] <ronoc> hyperair, who/what was responsible for the other half ?
[14:03] <hyperair> ronoc: indicator-messages.
[14:03] <hyperair> ronoc: it does a lot of icon resizing, which in the long run leaks
[14:03] <ronoc> hyperair, you must love the indicators :)
[14:04] <hyperair> lol no i don't
[14:05] <hyperair> i just got so irritated with them that i stuck a shell script running valgrind --tool=massif
[14:05] <hyperair> then all i have to do is wait for 6 hours or so
[14:05] <hyperair> it's annoying to think you've fixed it, and then in the next 6 hours it leaks again, and you have to stick it in massif and wait for another 6 hours
[14:05] <hyperair> i think i can safely say i hate indicators now.
[14:06] <hyperair> on the other hand i ♥ sbuild which gives me 3 second deb builds
[14:06] <hyperair> er 3 minute
[14:06] <ronoc> hyperair, okay well I'll talk to seb and co to get a SRU out for the memleak and ensure it doesn't go into natty
[14:07] <ronoc> hyperair, thx for spotting that
[14:07] <hyperair> ronoc: =)
[14:07] <hyperair> ronoc: i'm not done with messages though. it still leaks in weird spots
[14:07] <ronoc> hyperair, tedg might be able to help you there
[14:07] <hyperair> yeah but he isn't around
[14:08] <ronoc> oh yeah he is on holidays now i think until the 4th :(
[14:09] <hyperair> haha okya
[14:09]  * hyperair can't wait for his own holidays
[14:09] <ronoc> indeed
[14:09]  * hyperair is in the middle of exams but gets this impulsive desire to hack on something
[14:10] <ronoc> hyperair, where you based ?
[14:10] <hyperair> ronoc: singapore. once my exams end i'll be heading back to malaysia.
[14:10] <hyperair> ronoc: i'm malaysian, studying in singapore
[14:10] <ronoc> hyperair, cool, when do the exams finish ?
[14:11] <hyperair> 16th.
[14:11] <hyperair> i've to be back in malaysia by the 20th (internship begins)
[14:11] <ronoc> hyperair, do you take holidays around christmas at all ?
[14:12] <hyperair> yeah, christmas itself is a public holiday
[14:12] <hyperair> usually have dinner with family or something
[14:14] <ronoc> hyperair, memleak fixed
[14:14] <hyperair> thanks =)
[14:14] <ronoc> hyperair, thank you more like :)
[14:14] <hyperair> haha
[14:14] <hyperair> thank the massif devels
[14:14] <ronoc> indeed
[14:15] <hyperair> the only real time i spent staring at the code was like 5 minutes?
[14:15] <hyperair> massif truly rocks
[14:16] <hyperair> ronoc: are you familiar with dbusmenu's api?
[14:16] <ronoc> hyperair, yup
[14:16] <hyperair> ronoc: http://paste.debian.net/102272/ <-- this is my indicator-messages patch
[14:16] <hyperair> there's a comment there saying that pixbufs should be freed by dbusmenu
[14:16] <hyperair> but they aren't
[14:16]  * ronoc looks
[14:17] <hyperair> it's dbusmenu_menuitem_property_get_image
[14:17] <hyperair> i checked the dbusmenu source code, it doesn't look like it keeps track of the pixbuf for freeing anywhere
[14:18] <ronoc> hyperair, right did you file a bug?
[14:18] <hyperair> ronoc: nope, there's an existing indicator-applet bug about memleaks, so i just dropped my patch there
[14:18] <hyperair> ronoc: but it's hard to tell if it's this one leaking or something else
[14:19] <ronoc> hyperair, well ted will pick this just after xmas
[14:19] <hyperair> right, i'll ping him then
[14:19] <hyperair> i'm not sure whether dbusmenu is wrong or indicator-messages is wrong in this case
[14:19] <hyperair> although it's a GdkPixbuf* rather than a const GdkPixbuf*, so i'm more inclined to believe that indicator-messages is wrong
[14:20] <hyperair> (iirc standard gtk+ conventions were to add const to stuff you're not supposed to free/modify)
[14:21] <ronoc> hyperair, sure
[14:23] <ronoc> seb128, hyperair has found a memleak in indicator-sound for maverick , should i prepare a sru with the fix
[14:24] <hyperair> seb128: people with super-hi-res album arts will experience really fast memleaks.
[14:24] <seb128> ronoc, you can if there is a clear bug report about the issue, talk to kenvandine about it maybe to know the details?
[14:24] <ronoc> hyperair, ted should be on in a bit
[14:24] <seb128> doing a sru with the backport patch seems ok
[14:25] <ronoc> seb128, okay will file a bug now
[14:25] <hyperair> ronoc: oh that's cool
[14:33] <ronoc> kenvandine, I should really put out a sru for this -> https://bugs.launchpad.net/indicator-sound/+bug/689686
[14:33] <ronoc> what do you think ?
[14:48] <kvalo> kamstrup: hey, how hard would it be to create python bindings for libconnman?
[14:50] <hyperair> ronoc: there's still a leak.
[14:50] <ronoc> hyperair, oh yeah ?
[14:50] <hyperair> ronoc: i'm not sure where, but it's still there. i'm going to loop a playlist of songs with hi-res album art with massif there and check again later.
[14:51] <ronoc> hyperair, okay keep me posted
[14:51] <hyperair> hm no wait that wouldn't work
[14:51] <hyperair> indicator-sound needs to be opened once per song change
[14:51] <hyperair> then mem usage goes up, and doesn't come back down
[14:54] <jcastro> didrocks: thanks for assigning that bug to me, I might have missed it otherwise
[14:57] <didrocks> jcastro: no worry, with the flow of bugs, I prefered to notice you directly about it :)
[14:58] <jcastro> didrocks: also, jason told me floating mode is going away, so I'm wondering if we should unbitesize those
[14:58] <didrocks> oh really?
[14:59] <didrocks> didn't know that
[14:59] <didrocks> in that case, yeah, stratch it
[14:59] <didrocks> scratch*
[15:00]  * hyperair probably needs to run massif on notify-osd too. looks like it's leaking memory as well
[15:00]  * hyperair hopes unity isn't this leaky as well >_>
[15:04] <kamstrup> kvalo: if you're using GIR it's mostly some autotools foo and then maybe adding a few annotations where needed (for mem management)
[15:06] <kvalo> kamstrup: but how much work is to start using gir?
[15:07] <kvalo> ah, there is g-ir-scanner
[15:07] <kvalo> so it's not a manual process?
[15:08] <kvalo> apparently not, cool
[15:20] <jcastro> njpatel: any idea what cando needs in comment #1? https://bugs.launchpad.net/unity/+bug/688407
[15:22] <njpatel> jcastro, he can use the code from old unity (it's in lp:unity still, unity-private/places/place-place-trash.vala, or something like that)
[15:46] <dbarth> seb128: hey, what was the trick you used this morning to get the panel working?
[15:46] <dbarth> seb128: i'm seeing weird blockings on dbus calls here
[15:46] <dbarth> like duplicate unity-panel-service processes and 3 or 4 for gwibber
[15:46] <dbarth> gwibber-service that is
[15:51] <sense> good afternoon
[15:51] <hyperair> ronoc: okay, seems like a non-issue. my massif output shows the memory usage going up and down (as expected, since it loads super-large artwork and frees it again)
[15:52] <didrocks> seb128: I'm letting bug #689692 as I can't reproduce it. But I have a new compiz also that fix some focus issues, maybe related…
[15:52] <seb128> didrocks, ok
[15:53] <ronoc> hyperair, okay good
[15:53] <hyperair> ronoc: =)
[15:55] <dbarth> DBO: hi Jason, i've noticed a weird bug with the launcher where tooltips don't appear on certain entries if you hover over them from from botton to top
[15:55] <dbarth> DBO: seen that before?
[15:55] <DBO> dbarth, when was the last time you updated compiz?
[15:56] <dbarth> DBO: i'm using the natty version from the last 2 weeks or so
[15:56] <DBO> dbarth, that may not be recent enough
[15:56] <DBO> I fixed a major damage issue in compiz recently
[15:56] <DBO> it fixes that bug
[15:56] <dbarth> ah interesting
[15:57] <dbarth> didrocks is preparing a new upload i think, so i'll check that with the update
[15:57] <DBO> yes I believe his upload should remedy the problem
[16:00] <didrocks> DBO: dbarth: I opened bug #688468 some days ago
[16:00] <didrocks> DBO: dbarth: I confirm the new compiz snapshot fix that
[16:00] <didrocks> (or at least, I can't trigger it anymore)
[16:01] <DBO> awesome
[16:43] <jcastro> DBO: njpatel: the second unity update goes out EOD today my time, so if you have any bitesizers you want highlighted tag em and lmk.
[17:24] <nnnaji> speaking of Bitsize thingies, here's one: https://bugs.launchpad.net/synaptic/+bug/688811
[17:24] <nnnaji> i'm a little ashamed, but i need some help on where to start..
[17:25] <nnnaji> :P
[17:46] <Kuische> Hello. I upgraded to 10.10 and got Unity installed. Now nothing works. How do I re-enable main menu (Alt-F1)? How do I start Synaptic? How do I launch console? How do I launch other applications (Alt-F2)?
[17:46] <Kuische> And how do I remove the side bar?
[17:47] <Kuische> And how do I change the applets on the top bar?
[17:48] <kklimonda1> Kuische: you can''t change the applets on the top bar, you can't remove the side bar, there is no main menu.
[17:48] <kklimonda1> there is no replacement for alt+f2 and as for the rest of your questions - you can launch terminal by clicking the button in the left top part of the screen
[17:49] <Kuische> How do I start any othe applications? The only thing still accessible is Firefox.
[17:49] <nnnaji> Kuische, Unity doesn't ship with an Alt-F2 "run application" dialog afaik
[17:49] <spikeb> not the 10.10 version anyway
[17:49] <kklimonda1> Kuische: the ubuntu button should open an overlay where you can launch applications..
[17:50] <Kuische> Clicking Ubuntu logo shows 6 huge icons. None work
[17:50] <nnnaji> Kuische, you could try a ALT+CTRL+T to open the terminal
[17:51] <nnnaji> Kuische, if everything fails, try resetting the desktop session by doing CTRL+ALT+1, then login with your username and password, then do a "killall gnome-session"
[17:52] <nnnaji> CTRL+ALT+7 or CTRL+ALT+8 should return you to the greeter screen
[17:52] <Kuische> By the way, if you've managed to make GUI useless, what do I need to install to get non-English fonts in the console?
[17:53] <Kuische> Ctrl-Alt-number do not work, do you mean Ctrl-AltFn?
[17:53] <Kuische> Ctrl-Alt-number do not work, do you mean Ctrl-Alt-Fn?
[17:53] <nnnaji> sorry, omg, yes
[17:54] <Kuische> So, do you no, how to change fonts in the Ctrl-Alt-F1 console? Other than running everything with LC_ALL="C".
[17:55] <nnnaji> sry, i pass on that one
[17:55] <didrocks> jcastro: hey dude
[17:55] <didrocks> jcastro: so, with the nux issue we got last time, I was thinking about changing strategy for next release
[17:55] <jcastro> ok
[17:55] <didrocks> jcastro: basically, asking people after next nux release to run /usr/lib/nux/unity_support_test
[17:56] <didrocks> and report their configuration if there are still some issues for them
[17:56] <jcastro> ok, what does that actually do? (mine was segfaulting)
[17:56] <Kuische> Any way to remove Unity side bar?
[17:56] <didrocks> (and if they still can run unity)
[17:56] <didrocks> jcastro: that should be the entry point before deciding to launch unity or not
[17:56] <jcastro> didrocks: ok but you need a bunch of people to run it first?
[17:57] <jcastro> to determine a baseline or ... ?
[17:57] <didrocks> jcastro: well, last time, it was working for me on nvidia, but it wasn't on intel and ati or a second user on nvidia
[17:58] <didrocks> jcastro: no need for big testing, but still if people are aware about the command and we can make some advertisement to report bugs if it doesn't work for them, that will be good before using it as the detection module
[17:58] <jcastro> yep.
[17:58] <jcastro> we should add it to the project page
[17:58] <jcastro> "If unity doesn't work, run /usr/lib..."
[17:58] <didrocks> jcastro: neat idea. in any case, it won't be before next release (Thursday I guess)
[17:59] <jcastro> nod
[17:59] <didrocks> the segfault has been fixed by jaytaoko btw
[17:59] <jcastro> nice
[17:59] <didrocks> just before you have a cheap card with no vsync :p
[17:59] <jcastro> this morning my unity session doesn't work, but I don't think that's your fault
[18:00] <didrocks> yeah, the indicator issue?
[18:00] <didrocks> jcastro: you mean, you have a blank top panel?
[18:00] <kvalo> ronoc: hi. time for yet another review? https://code.launchpad.net/~kvalo/indicator-network/settings-backend-begin/+merge/43548
[18:00] <jcastro> I am not sure, it was working this weekend, I was just going to sit it out in fallback today
[18:00] <jcastro> yeah the indicators are also broken, but my unity log in just logs into a blank wallpaper
[18:00] <didrocks> oh? weird
[18:01] <jcastro> didrocks: but I don't have time to investigate now so I was just going to work today in classic mode and then investigate later
[18:01] <didrocks> empty panel because of indicators is known, but yeah, keep me in touch
[18:01] <jcastro> yeah I figured that out when I saw I wasn't the only one
[18:01] <jcastro> I'll use it as an opportunity to move off of dailies this evening. heh.
[18:02] <didrocks> jcastro: oh, you are in the dailies?
[18:02] <didrocks> jcastro: ok, there is a bamf breakage, you should have latest unity and latest bamf
[18:02] <jcastro> yeah that's why I wasn't bothering you. :D
[18:02] <didrocks> of course, it's not dealt packaging-wise as it's the dailies:)
[18:03] <jcastro> I'll move to natty proper later, now that I have intellihide I'm not so anxious to bleed
[18:03] <didrocks> hehe :)
[18:13] <lamalex> can one of yous guys ping me? Doing some triaging. need to test something that requires urgency
[18:14] <didrocks> lamalex: ping
[18:15] <lamalex> thanks didrocks
[18:15] <didrocks> yw :)
[18:15] <lamalex> didrocks, it's your bug actually :P https://bugs.launchpad.net/unity/+bug/688471
[18:15] <lamalex> I'm not experiencing it
[18:15] <lamalex> launcher hides normally for me
[18:16] <didrocks> lamalex: let me try to reproduce
[18:17] <didrocks> lamalex: can you ping me, please?
[18:17] <lamalex> didrocks, ping
[18:18] <noob> hi, how i can configure the unity interface? it is too slow and i can't edit menu entries :(
[18:18] <didrocks> lamalex: weird, I don't get it anymore
[18:21] <kvalo> lamalex: hi. would you mind doing some review? https://code.launchpad.net/~kvalo/indicator-network/settings-backend-begin/+merge/43548
[18:21] <lamalex> kvalo, sure thing
[18:22] <kvalo> lamalex: excellent, thanks. I have to go now, but I will be back in 30 mins or so
[18:23] <lamalex> sure thing
[18:25] <lamalex> DBO, how do I run the panel?
[18:25] <DBO> ?
[18:25] <lamalex> my panel is empty and I can't get it to populate
[18:26] <lamalex> do you usually have to do anything to get your panel to have things in it?
[18:46] <lamalex> :\ I can't get anything to show up in my panel
[21:05] <jcastro> tareth: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/686182
[21:05] <jcastro> this was the bug fix that got merged afaict
[21:05] <jcastro> do you happen to know why it's still open?
[21:07] <tareth> I have no idea
[21:14] <kvalo> lamalex: thanks for the review. I pushed updates now.
[21:14] <lamalex> kvalo, good stuff
[21:18] <kvalo> lamalex: if you can take a look at the updates today and hopefully I can merge them to trunk tomorrow morning :)
[21:18] <kvalo> but now I need to get sleep
[21:18] <lamalex> kvalo, if you fixed those things and make checks passes, merge it
[21:36] <rbnswartz> Will calling activate on a compiz window bring it to front of all windows?
[21:40] <rbnswartz> DBO you on?
[21:40] <DBO> yes
[21:41] <DBO> rbnswartz, it performs the logical activate and raise function yes
[21:41] <rbnswartz> I think I have that bug fixed. But I have a few questions
[21:42] <DBO> sure
[21:42] <rbnswartz> can I call bamf_view_is_urgent on a child window not just on the app itself?
[21:43] <DBO> rbnswartz, you can yes
[21:44] <DBO> but there are other ways to check for urgency
[21:46] <DBO> assuming window is a CompWindow *
[21:46] <DBO> if (window->state () & CompWindowStateDemandsAttentionMask)
[21:46] <DBO> tells you if a window needs attention
[21:46] <rbnswartz> I have a fix now that I think will work by using an existing loop to find out which window is urgent and then after the loop uses m_screen->findWindow to get the window and window->activate to bring it to the front
[21:46] <rbnswartz> would you like me to email you the code?
[21:47] <DBO> push it to a branch in launchpad
[21:47] <DBO> I will review it
[21:47] <rbnswartz> how do I do that?
[21:47] <DBO> whats your launchpad id?
[21:47] <rbnswartz> rbn-swartz
[21:47] <DBO> bzr push lp:~rbn-swartz/unity/unity.fix-urgent-focus
[21:48] <DBO> well first
[21:48] <DBO> bzr commit
[21:48] <DBO> so you save your changes
[21:48] <DBO> then do the push
[21:50] <rbnswartz> I'm a complete newbie here I don't know how to do that?
[21:51] <DBO> rbnswartz, you can email me the patch :)
[21:51] <DBO> jason.smith@canonical.com
[21:52] <rbnswartz> I think I got it I found the register branch is that how I do it?
[21:53] <DBO> you can do it from the command line if you have your launchpad account hooked with bzr
[21:53] <DBO> but yes, you can also register a branch
[21:54] <rbnswartz> bzr is a program I need to install right?
[21:54] <DBO> how did you get the code if you dont have bzr already installed?
[21:55] <rbnswartz> downloaded the source from launchpad
[21:55] <DBO> oh wow
[21:56] <DBO> I did not even know you could do that...
[21:56] <DBO> in that case you're going to have to send a patch
[21:59] <rbnswartz> the patch is on its way
[22:01] <DBO> awesome
[22:01] <DBO> you are a scholar and a gentleman
[22:01] <DBO> may a thousand chocolate chips find their way unto your mouth by days end
[22:01] <rbnswartz> next bug to work on?
[22:02] <DBO> oh boy
[22:02] <DBO> uhm...
[22:02] <rbnswartz> I'm very industrious
[22:02] <DBO> indeed
[22:03] <DBO> lemme look over this patch really quick
[22:04] <rbnswartz> everything is in the onclick event
[22:04] <rbnswartz> I made no other modifications besides a variable
[22:04] <rbnswartz> everything is contianed in the function
[22:05] <DBO> yep, source has changed a bit while you were working on it so the merge is a bit more difficult :)
[22:06] <rbnswartz> well send me the current source and I'll fix that.
[22:07] <rbnswartz> I have to go now thanks for your help
[22:08] <DBO> cheers :)
[22:57] <lamalex> DBO, the dnd animation is really nice
[22:57] <DBO> thanks buddy
[22:58] <lamalex> DBO, is it intended that if you drag off the launcher, and move vertically, then release it moves the icon?
[23:06] <DBO> lamalex, for now
[23:07] <DBO> I am still implementing in full