[07:05] <oSoMoN> good morning
[07:31] <andyrock> is there something of the unity team?
[07:31] <andyrock> someones sorry :)
[08:03] <andyrock> DBO around?
[08:03] <andyrock> gord, around?
[08:04] <gord> andyrock, hey, whats up?
[08:04] <andyrock> gord, about the dash dnd problem
[08:05] <andyrock> well we use nux::GetWindow().GetDndData("text/uri-list")
[08:05] <andyrock> and when we dragging something from the dash this value is null
[08:06] <andyrock> it should be "application:://etc.dekstop" or something like this
[08:08] <gord> andyrock, have you upgraded your stack? iirc that value is provided by the lens'es and until late yesterday, they were giving out null values
[08:09] <andyrock> gord, unity lense application Version: 0.4.2-0ubuntu1
[08:17] <andyrock> gord, btw how can i show in terminal the LOG_DEBUG stuff?
[08:18] <gord> andyrock, tim posted a mail to ayatana-dev explaining all that, export UNITY_LOG_SEVERITY="<root>=INFO;" gets you all the debug calls in unity iirc
[08:19] <andyrock> gord, thx
[08:20] <gord> andyrock, trying to get a grip on whats going on with this dnd stuff, seems like it should be working =\
[08:21] <andyrock> gord, well i worked on dnd stuff, but everything is based on nux::GetWindow().GetDndData("text/uri-list")
[08:22] <andyrock> also with the "old dnd" this functions was the "pivot"
[08:22] <gord> yeah we just return the same string for whatever getdnddata you ask for
[08:22] <andyrock> btw in resultgridview should be the error
[08:24] <andyrock> let me debug :)
[09:32] <andyrock> gord, around?
[09:34] <gord> andyrock, yup
[09:35] <andyrock> gord, so current_drag_uri_ is filled in ResultViewGrid::DndSourceDragBegin()
[09:35] <andyrock> and then it is used in ResultViewGrid::DndSourceDragBegin()
[09:36] <andyrock> sorry in DndSourceGetDataForType
[09:37] <andyrock> maybe DBO can confirm, but i think that DndSourceGetDataForType is called first that ResultViewGrid::DndSourceDragBegin
[09:40] <gord> andyrock, heh really? lets try flipping it around a bit, hold on
[09:41] <andyrock> gord, i'm doing the same thing
[09:43] <andyrock> gord, so copying the init code in the dndsourcegetdatafortype
[09:43] <andyrock> works well, but a question icon is displayed :)
[09:44] <gord> andyrock, neat, what is the icon that has a question icon? typically means it couldn't find the icon in the theme or elsewhere
[09:45] <gord> the icon loading code for dnd just isn't as robust as what we have for the rest of the dash
[09:45] <andyrock> application-default-icon
[09:46] <andyrock> i'will try to solve it... if i'm not able you will do it :)
[09:58] <andyrock> gord, fixed ;)
[09:59] <gord> andyrock, woo :) ping me when you have a mp and i'll take a look
[09:59] <andyrock> maybe something more special could be done but who has time for special?
[10:00] <andyrock> i have other fixes another branch about dnd
[10:00] <andyrock> with two other fixes
[10:00] <andyrock> i have to do another branch?
[10:01] <gord> andyrock, please :) i can review this branch about the resultsview and then i'll give jason a poke about your other dnd related branches later
[10:01] <andyrock> ok thx
[10:38] <andyrock> gord, do not be frightened by the length of the patch
[10:38] <andyrock> :)
[10:38] <andyrock> https://code.launchpad.net/~andyrock/unity/dnd-dash-fixes/+merge/73013
[10:38] <andyrock> XD
[10:38] <andyrock> the old nux worked as said few minutes ago, the new one not
[10:44] <gord> yeah testing here it didn't work :)
[10:47] <andyrock> gord, have you seen the patch? :)
[10:48] <gord> andyrock, yeah, looks like a silly mistake that crept in last night as some changes were made :)
[10:48] <andyrock> gord, i know... :)
[10:49] <andyrock> no problem
[10:49] <andyrock> you rock anyway
[11:41] <fagan> I just installed oneiric on my netbook and the resolution is off
[11:42] <fagan> some of the content is off the screen
[11:56] <andyrock_> seb128, what can we use to open the trash instead of xdg-open?
[11:59] <andyrock_> seb128, btw xdg-open trash://
[11:59] <andyrock_> gvfs-open: trash://: error opening location: Operation not supported
[14:32] <jjardon> tedg: hey, any reason why the time label has to be updated through the service and not when the datetime menu is open ?
[14:32] <jjardon> like the calendar widget?
[14:33] <tedg> jjardon, Which label?  The one on the panel?
[14:33] <jjardon> tedg: no, the menu item
[14:34] <tedg> jjardon, Because mixing standard menu items and dbusmenu items results in tears.
[14:34] <tedg> jjardon, When the menu is resorted it doesn't know where to put the standard ones, so the result is confusing at best.
[14:34] <tedg> jjardon, The cost of updating it is very cheap.
[14:35] <om26er> gord, Hi! is there any chance we'll have bigger icon size in the result view for Unity?
[14:37] <jjardon> tedg: oh, I see, but the problem is that the label is updated with a timeout set in this function: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk/view/head:/src/datetime-service.c#L298
[14:37] <jjardon> but this causes problems when the user change the date manually or after a suspend cycle
[14:38] <tedg> jjardon, That function can be called repeatedly though, so could it just be called in those cases?
[14:40] <jjardon> tedg: yeah, but how can I know that the date changed? the changes in the panel are sent to through the SetTime signal, but the indicator datetime doesnt get notified
[14:41] <tedg> jjardon, Listen to the same signal?  It seems the service should be sending the UpdateTime()
[14:41] <tedg> jjardon, So perhaps the service should be the one driving more.
[14:45] <jjardon> tedg: mmm, the update of the menu item time is done in the service itself, not in the indicator
[15:00] <Trevinho> Hi guys... I'm back! :)
[15:01] <Trevinho> seb128: around?
[15:01] <om26er> Trevinho, thats totally awesome ;)
[15:01] <om26er> Trevinho, welcome back :)
[15:01] <Trevinho> thanks om26er ;)
[15:31] <kenvandine> welcome back Trevinho
[15:34] <jjardon> tedg: so, What do you think is the best way to get notification in the service when the system time changes? to not relay on the timeouts?
[15:36] <tedg> jjardon, Is there a signal from gsd?
[15:37] <tedg> jjardon, Assuming someone set the time with gcc it seems we should be able to watch for it's signal if nothing else.
[15:40] <seb128> hey Trevinho
[15:41] <jjardon> tedg: I'll take a llo to gsd, we can listen to SetTime, but that wouldnt work with the suspend problems
[15:41] <tedg> jjardon, I believe that upower gives us a signal on suspend
[15:42] <tedg> jjardon, I don't remember if it's before or after, but if it's before we can just set a timer and wait for the time to be noncontiguous.
[15:48] <jono> seb128, where should I file bugs for Unity for the design team to look at?
[15:48] <jono> unity project?
[15:48] <jono> or ayatana?
[15:48] <seb128> jono, the ayata-design project
[15:49] <seb128> jono, usually what others do is to open an unity bug, set it to incomplete and do "also affect" ayatana-design
[15:49] <tedg> jono, Usually we have two bug tasks, on the SW project and one on ayatana-design.
[15:49] <tedg> Yeah, like seb128 said.
[15:49] <jono> seb128, thanks, will do that now
[15:49] <jono> seb128, so the unity bug should be for the project, not the source package?
[15:50] <seb128> jono, we tend to do both
[15:50] <seb128> to keep things in sync
[15:50] <jono> ok, so file it for the source package and then also affect unity (project) and ayatana-design
[15:50] <seb128> but either work
[15:50] <seb128> didrocks has a script that will sync the status between upstream and ubuntu unity
[15:50] <seb128> jono, correct
[15:51] <jono> thanks seb128
[15:51] <seb128> launchpad makes it suboptimal to trunk bugs for projects like unity or ubiquity or...
[15:51] <seb128> i.e things which basically are tracked by the same people upstream and in ubuntu
[15:52] <jono> right
[15:54] <nxvl> hi, i'm having an issue with unity, for some reason, when i open unity3D it seems to open (it even runs network-manager and connects me to the wifi) but i don't get the panels, just a nautilus menu bar and that's it
[15:54] <nxvl> (i'm running oneiric)
[15:54] <AlanBell> is the tablet PC with touchscreen a supported or targeted device for Oneiric?
[15:57] <om26er> nxvl, can you open a terminal?
[15:58] <nxvl> om26er: i can get a tty
[15:58] <om26er> nxvl, Unity worked for you before the update or was it a new install ?
[15:59] <nxvl> it worked until, like yesterday or a day before
[15:59] <nxvl> unity2D works fine
[15:59] <nxvl> gnome3 too
[15:59] <Trevinho> Ah, hey kenvandine!
[15:59] <Trevinho> seb128: about the nautilus thing....
[15:59] <om26er> nxvl, in a tty 'export DISPLAY=:0'
[15:59] <Trevinho> What should I do?
[15:59] <nxvl> i saw update-manager removing some unity package, (no idea which ones) and it never worked again
[15:59] <om26er> nxvl, and unity --reset
[15:59] <seb128> Trevinho, what mpt suggested on the merge request seemed ok?
[15:59] <nxvl> ok let me re-login
[16:00] <om26er> nxvl, you could check if you have it actually installed
[16:00] <jono> seb128, I need to file a bug in the indicator with my name on it - is that the Me Menu?
[16:00] <nxvl> om26er: how?
[16:00] <Trevinho> seb128: I've already added the unity support...
[16:00] <nxvl> om26er: ubuntu-desktop is installed
[16:00] <om26er> nxvl, maybe an update removed it, someone I known had a similar problem yesterday
[16:00] <seb128> jono, indicator-session
[16:00] <Trevinho> so I should only disable the indicator... Isn't it?
[16:00] <jono> thanks seb128
[16:00] <om26er> nxvl, try sudo apt-get install unity
[16:01] <kenvandine> Trevinho, if you have any awesome, wild, crazy ideas for gwibber 3.4... feel free to start hacking on it :)
[16:01] <nxvl> already in newest version
[16:01] <Trevinho> kenvandine:  I've some... But I've to sync with upstream yet... :P
[16:01] <om26er> nxvl, then try unity --reset (did you happen to change anything in ccsm ?)
[16:01] <Trevinho> You know, coming back is an hard resync time! :P
[16:02] <nxvl> om26er: i did, while in natty
[16:02] <om26er> nxvl, try the reset in a tty then
[16:02] <AlanBell> I am looking at bug 739812 what would be required on a technical level to have an on-screen keyboard type into a dash or lens search field?
[16:03] <AlanBell> would it need a new on screen keyboard to be written and rendered by NUX or something?
[16:04] <jono> seb128, I filed the wider user-accounts issue as https://bugs.launchpad.net/indicator-session/+bug/834830
[16:04] <seb128> jono, ok
[16:04] <jono> I am going to mail the design team about this
[16:04] <seb128> thanks
[16:04] <seb128> or email the ayatana list
[16:05] <seb128> brb
[16:05] <nxvl> om26er: ok, running, does it take a while?
[16:05] <nxvl> om26er: or it's having issues?
[16:06] <nxvl> om26er: it claims that is not finding unity-panel-service
[16:06] <om26er> nxvl, oh
[16:07] <om26er> nxvl, after running unity --reset you did switch to the previous tty?
[16:07] <nxvl> om26er: and it stops at kde4-window-decorators: could not enable decorators on :0-0
[16:07] <nxvl> om26er: define previuos tty
[16:07] <om26er> nxvl, sudo apt-get install compiz-gnome
[16:07] <jono> DBO did you manage to track down the Launcher issue?
[16:07] <om26er> you seem to have removed compiz-gnome with some update
[16:07] <nxvl> om26er: so i got a hanged unity on F7 i'm running the command on F1 and irc on F2
[16:08] <jono> for it not showing when you slowly touch the side of the screen?
[16:08] <DBO> jono, everything but fix it
[16:08] <jono> awesome
[16:08] <jjohansen> what value is supposed to be in ccsm -> Window Decoration-> Command
[16:08] <nxvl> om26er: yes, compiz-gnome wasn't installed
[16:08] <om26er> jjohansen, /usr/bin/compiz-decorator
[16:09] <jjohansen> om26er: thanks
[16:09] <om26er> /usr/bin/gtk-window-decorator should work too
[16:09] <om26er> jjardon, yw :0
[16:09] <om26er> * :)
[16:09] <jjohansen> well that is just it, it doesn't I have no decorators
[16:10] <nxvl> yay! i'm in unity once again
[16:10] <jjohansen> nxvl: lucky, its still broken for me
[16:11] <nxvl> jjohansen: yeah same here, it was just a couple of minutes of lies!
[16:12] <nhaines> jono: +1 on that bug from me.  :)
[16:12] <jono> :-)
[16:12] <jjohansen> nxvl: oh in that case I don't have hate you anymore, lies I can live with but unity working for you and not me is a bit much
[16:14] <nxvl> jjohansen: i wasn't liying, unity lied to me pretending to be working just to crash 2 minutes after
[16:14] <jjohansen> nxvl: oh! well even better ;)
[16:20] <nhaines> jono: do you have a couple minutes for me in PM right now?
[16:22] <AlanBell> DBO: did you get somewhere with bug 739812?
[16:23] <DBO> AlanBell, it's actively being worked on, I have done the part I could do (make it so that the dash doesn't grab mouse/keyboard)
[16:24] <DBO> IM support in dash is up to the dash guys now (they have some test work done)
[16:24] <jjardon> tedg: ok, so seems the proper solution is using this: http://lwn.net/Articles/432395/
[16:24] <jono> nhaines, sure
[16:26] <nhaines> Thanks.
[16:28] <tedg> jjardon, Is that in the Oneiric kernel?  (it's git, so you have no idea what the version numbers mean :-)
[16:29] <jjardon> tedg: good news, we will have api in glib for this soon.
[16:29] <jjardon> I'll track the bug: https://bugzilla.gnome.org/show_bug.cgi?id=655129
[16:29] <jjardon> For now we can watch for suspend changes and update the clock
[16:30] <AlanBell> DBO: ok, thanks
[16:31] <jono> DBO, quick q: the text in the dash, sometimes it is not particularly readable, any chance we could have a small black shadow behind it to make it stand out more?
[16:31] <DBO> jono, if you pick a darker wallpaper is it better?
[16:33] <jono> DBO, not tried, but I presume so
[16:34] <DBO> jono, the dash needs to have a "max brightness" so it wont wash out the text
[16:34] <DBO> it's known
[16:37] <jono> DBO, I just figured a very thin black shadow (maybe only 2px) could solve that
[16:38] <DBO> Im no designer
[16:38] <DBO> you mean give the text a shadow?
[16:38] <DBO> noooooooooooo
[16:38] <DBO> shadows are slow to draw for text (you have to trace)
[16:38] <AlanBell> and they look blurry
[16:39] <jjohansen> DBO: you don't have to trace, you can do the old draw and swear trick, but yeah they look blurry
[16:40] <DBO> we dont do ugly
[17:17] <jo-erlend> some launcher tiles have numbers and other information on them to reflect the state of the application. How do I do this in Python?
[17:21] <datenshi> jo-erlend: there are examples in libunity
[17:22] <jo-erlend> datenshi, something a little more specific?
[17:22] <jo-erlend> what is it called? What do I search for? Are there any written documentation for it?
[17:23] <datenshi> bzr branch lp:libunity, there is examples folder
[17:24] <jo-erlend> does that mean it has no name that I can refer to when talking about it?
[17:24] <datenshi> jo-erlend: http://bazaar.launchpad.net/~unity-team/libunity/trunk/view/head:/examples/launcher.py
[17:25] <jo-erlend> so it has no name and documentation?
[17:26] <nhaines> Ooh, useful.
[17:26] <jo-erlend> yes, very useful. But this is for a question on askubuntu and I'd like to refer to names or a documentation URL.
[17:26] <jo-erlend> but if it doesn't exist, then it doesn't.
[17:27] <nhaines> jo-erlend: well, that'd definitely be more useful.  But unfortunately Canonical seems to like to leave the code as documentation.  :/
[17:27] <nhaines> Can't say I'm not guilty of the same though.
[17:39] <jono> DBO, who is working on the Music Lens?
[17:40] <DBO> jono, lamalex
[17:40] <jono> cool, I have found some bugs I am going to file
[17:41] <jono> hmmm seems I can't do ubuntu-bug unity-music-lens
[17:41] <jono> will report it at http://edition.cnn.com/2011/TECH/gaming.gadgets/08/25/linux.20/index.html
[17:41] <jono> oops
[17:41] <jono> not there
[17:41] <jono> https://bugs.launchpad.net/unity-music-lens/+filebug
[17:43] <jono> lamalex, are you seeing https://bugs.launchpad.net/unity-music-lens/+bug/834910 ?
[17:45] <lamalex> jono, yah that's not a bug
[17:45] <lamalex> i mean i guess it could be a "bug"
[17:45] <jono> lamalex, what do you mean?
[17:45] <lamalex> but it's in the code to limit to just a result set
[17:45] <lamalex> it's limited to like 50 or 100 or something
[17:45] <lamalex> jono, you should be able to search for any of it though
[17:46] <jono> surely it should say Songs See 16,033 more results
[17:46] <jono> right now it presents an inaccurate representation of the number of songs I have
[17:47] <lamalex> yah i suppose
[17:47] <jono> the searching does work wel
[17:47] <jono> well
[17:48] <lamalex> hah wtf i can't set bug priorities on my lens >:(
[17:48] <jono> lamalex, is that the right project?
[17:48] <jono> I see some pretty old comments on bugs in there
[17:48] <jono> wasn't sure if it was a community project
[17:49] <lamalex> ha oh
[17:49] <lamalex> jono you're on the wrong one
[17:49] <lamalex> this is going to be confusing
[17:49] <lamalex> our lenses are of the form unity-lens-<title>
[17:49] <lamalex> https://launchpad.net/unity-lens-music/
[17:49] <nhaines> ha!
[17:50] <jono> lamalex, aha!
[17:51] <jono> lamalex, you need to enable bug tracking there
[17:51] <lamalex> just report it on the ubuntu package for no
[17:51] <lamalex> w
[17:52] <lamalex> i dont seem to have access to set up things on this project
[17:52] <lamalex> dbarth, ^^
[17:53] <jono> will do lamalex
[17:53] <jono> DBO, btw, I just filed https://bugs.launchpad.net/ubuntu/+source/unity/+bug/834921
[17:54] <DBO> you can do that?
[17:54] <DBO> why the hell are you changing virtual desktops with the dash open...
[17:54] <DBO> you crazy
[17:54] <lamalex> oh yeah look at all that lag
[17:54] <lamalex> but yo
[17:54] <jono> DBO :-)
[17:54] <lamalex> you crazy dawg
[17:55] <jono> I also noticed the same thing with the indicators and filed https://bugs.launchpad.net/ubuntu/+source/unity/+bug/834415 last night
[17:55] <jono> sorry guys
[17:57] <DBO> jono, thats it, I am not buying you beer next UDS
[17:57] <jo-erlend> datenshi, thanks for the link and help :)
[17:57] <jono> DBO lol
[17:57] <jono> you never buy me beer anyway
[17:57] <jono> :-)
[17:57] <DBO> you never buy me the beers you said you owe me
[17:57] <DBO> so I figure I can not buy you beers I dont owe you
[17:58] <DBO> the fake beer economy can also have fake beer speculation
[17:59] <jono> DBO, I will definitely buy you beer at UDS
[17:59] <jono> lamalex, https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/834928
[17:59] <jono> lamalex, is the plan to show album art in the lens?
[18:00] <lamalex> yes
[18:00] <jono> cool
[18:00] <lamalex> theres a branch
[18:00] <jono> want me to file a bug for that?
[18:00] <jono> ahhh sweet
[18:00] <lamalex> waiting for a banshrr release with a patch
[18:01] <jono> gotcha
[18:02] <jono> lamalex, should clicking on an album load the full album into the queue in Banshee?
[18:05] <jono> I just noticed another interesting bug
[18:07] <om26er> lamalex, if i click on a song in the lens its added to the queue but shouldnt it play instantly?
[18:10] <jono> lamalex, not sure if you saw https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/834933 too
[18:11] <jono> om26er, I think that is a bug too, filing it
[18:12] <om26er> i'll play the 'confirm' part ;-)
[18:13] <om26er> could be the way banshee handles it though
[18:14] <jono> om26er, https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/834937
[18:14] <lamalex> jono, yah i have to patch banshee
[18:14] <lamalex> banshee's kind of messed up there
[18:14] <jono> I am filing one more bug and then should be done
[18:14] <jono> these are all small issues
[18:14] <jono> thanks lamalex
[18:14] <lamalex> music lens is a focus for next week, but go nuts
[18:14] <lamalex> give me a list of things to work on :)
[18:15] <om26er> music lens is not up for bugs as well (yet) :/
[18:15] <lamalex> i know
[18:15] <lamalex> dbarth, ^ please set up bugs for music lens
[18:16] <lamalex> om26er, you can file on the ubuntu package though
[18:16] <om26er> jono, thanks, confirmed :)
[18:17] <jono> thanks om26er
[18:17] <jono> ok I added https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/834943
[18:18] <jono> lamalex, om26er so the full bugs list is at https://bugs.launchpad.net/ubuntu/+source/unity-lens-music - would be cool if you could confirm and prioritize them
[18:18] <jono> the music lens is gonna kick ass when it is working
[18:18] <lamalex> jono, yah, will do on monday most likely
[18:18] <jono> well, it works now, I mean these bugs are fixed
[18:18] <jono> thanks lamalex :-)
[18:18] <lamalex> yup! it's going to rock
[18:22] <jono> grabbing lunch, biab
[18:27] <DBO> jono, do we know anyone using a german keyboard?
[18:32] <lamalex> all of germany
[18:36] <jcastro> I'm going to go out on a limb and guess "Mirco"
[18:36] <htorque_> öäüß ;-)
[18:48] <DBO> htorque_, oh oh
[18:48] <DBO> I need your help
[18:48] <DBO> lp:~unity-team/unity/unity.keyboard-util
[18:48] <DBO> get and build that branch
[18:48] <DBO> then run tests/test-keyutil
[18:49] <DBO> and give me the output
[18:49] <htorque> DBO: on it
[21:28] <jono> DBO, yo
[21:28] <DBO> hey jono
[21:28] <jono> you know how I mentioned the readability of the text in the dash?
[21:28] <jono> see https://bugs.launchpad.net/ubuntu/+source/unity/+bug/835095
[21:28] <jono> I added a screenshot there
[21:29] <kenvandine> i really liked the dash better black
[21:30] <kenvandine> playing with opacity is "cool" and all... but sometimes it just isn't the best way to solve the problem
[21:30] <jono> I think it looks cool if it had an underlying blackness to it
[21:30] <jono> and then mixed in the shade of your wallpaper
[21:30] <jono> the effect of the wallpaper color does look cool
[21:30] <kenvandine> yeah
[21:30] <jono> just that some colors look weird as the base
[21:30] <kenvandine> it just really needs to be darker i think
[21:31] <jono> yup
[21:31] <DBO> jono, release the bug report
[21:31] <kenvandine> and maybe blur even more
[21:31] <DBO> thats how you report a design bug
[21:31] <jono> DBO, release what?
[21:31] <DBO> reload
[21:31] <DBO> sorry
[21:31] <DBO> my brain has given up
[21:32] <jono> DBO why is it incomplete?
[21:32] <DBO> because its a design problem
[21:32] <DBO> so in unity its incomplete
[21:32] <jono> surely it should be Confirmed then?
[21:32] <DBO> in ayatana-design it's new
[21:32] <kenvandine> jono, he is saying that isn't a unity bug, it is a design choice
[21:33] <DBO> yeah
[21:33] <kenvandine> so we need to plead to them
[21:33] <jono> right
[21:33] <jono> but the bug is still confirmed in Unity though
[21:33] <jono> it is not incomplete
[21:33] <DBO> not a bug
[21:33] <jono> look at the screenshot
[21:33] <jono> it's a bug :-)
[21:33] <DBO> not a bug
[21:33] <kenvandine> if design changes their mind, we re-open the unity task
[21:33] <DBO> that is how it was designed
[21:33] <kenvandine> to fix it
[21:33] <jono> I think it wasn't designed to have the effect in the screenshot
[21:33] <jono> I think it was designed to have the effect if you have the purple wallpaper
[21:34] <DBO> jono, they gave use the exact color algorithm to use
[21:34] <jono> therefore it is a bug
[21:34] <DBO> we told them it would let it go too bright
[21:34] <jono> DBO do you honestly think the design team desire the effect in the screenshot?
[21:34] <DBO> they did not change it
[21:34] <jono> I am not denying it is a design problem, but I disagree it is not a Unity bug - it makes the dash unreasonable
[21:34] <DBO> I have no choice but to believe that
[21:35] <DBO> we told them
[21:35] <jono> as such it should be marked as Complete
[21:35] <jono> dude, come on
[21:35] <kenvandine> jono, but it isn't something the unity team can fix
[21:35] <jono> they dont want it that way
[21:35] <DBO> dude, I showed them
[21:35] <jono> kenvandine, I agree it is a design problem
[21:35] <jono> not disagreeing
[21:35] <jono> and they should provide a solution
[21:35] <jono> full agreement there
[21:35] <kenvandine> jono, it is effectively blocked on design right now
[21:35] <jono> I take issue though that this is not a bug in Unity
[21:35] <htorque_> isn't that a dupe anyway? bug 824916
[21:36] <jono> htorque ahhh oops :-)
[21:36] <DBO> jono, it's not marked invalid
[21:36] <DBO> it's marked incomplete
[21:36] <jono> DBO, right, but the bug is complete, the solution is not complete though
[21:36] <DBO> incomplete on unity means DX cant fix it for some reason
[21:36] <DBO> erm more accurately
[21:36] <DBO> it means DX cant fix it because some information about how to fix it is missing
[21:37] <DBO> (more than just coding/technical issues)
[21:37] <jono> DBO, well that is inconsistant with most other triage as incomplete means the bug report needs more info to determine if it is actually a bug
[21:38] <DBO> yeah but we're inconsistent in the fact that the people who design the product are not on the same team as the people who make the product
[21:38] <jono> thats not the point though
[21:38] <jono> again, I sympathize with the team issues
[21:38] <jono> and I sympathize you need input from design
[21:38] <jono> but marking the bug as incomplete is not accurate
[21:38] <jono> and thinking that they deliberately want it that way in the screenshot seems misguided to me
[21:39] <jono> I Think they dont intend it that way
[21:39] <jono> but they didnt listen to your guidance and warnings
[21:39] <kenvandine> not invalid or anything...
[21:39] <kenvandine> just need them to decide
[21:39] <jono> right
[21:39] <jono> wasnt there gonna be a NEEDSDESIGN status?
[21:40] <jono> or could it be marked Complete and tagged with needsdesign ?
[21:40] <jono> anyway, it's up to you guys, just my $0.02c
[21:40] <DBO> if design says to me to keep the algorithm when I ask them tomorrow
[21:40] <jono> it's your bug :-)
[21:40] <DBO> I will mark it wishlist
[21:40] <DBO> if they say to modify it, they will prioritize their bug
[21:40] <DBO> and fix it
[21:40] <jono> DBO, if they deliberately reject that it is a bug, then we will have a different conversation
[21:40] <jono> makes sense
[21:41] <jono> remember, we are all on the same team here :-)
[21:41] <jono> anyway, I have to run, thanks guys
[21:41] <jono> Unity is rocking :-)
[21:41] <DBO> then when they fix release their stuff to us, we mark confirmed
[21:41] <DBO> and then we need a UI freeze exception
[21:41] <DBO> (which we wont get)
[21:41] <DBO> so yeah :)
[21:41] <DBO> fun fun fun
[21:41] <kenvandine> DBO, you would for this
[21:42] <DBO> kenvandine, depends on timing
[21:42] <kenvandine> it isn't really going to break translations or terribly affect screenshots
[21:42] <DBO> sure but in 4 days is final freeze
[21:42] <DBO> design team turn around is not 4 days short
[21:42] <kenvandine> you just can't wait for design to notice the bug
[21:42] <kenvandine> someone needs to ping them
[21:42] <DBO> I pinged them today, yesterday, and last week
[21:42] <DBO> how many times can I do that?
[21:43] <DBO> so has gord
[21:43] <DBO> actually I dont know if gord has but I assume it is so
[21:43] <kenvandine> DBO, i understand... the workflow is a bit broken
[21:44] <kenvandine> just you can't assume they will see the bug..
[21:44] <kenvandine> jono, that screenshot looks terrible dude
[21:44] <DBO> one more tiny issue
[21:44] <DBO> final freeze is monday
[21:44] <DBO> right?
[21:44] <DBO> erm whoa
[21:44] <kenvandine> we should mark the bug invalid and say you aren't using the default wallpaper
[21:44] <DBO> I am off by a month
[21:45] <kenvandine> DBO,  no
[21:45] <kenvandine> it isn't even beta yet
[21:45] <DBO> sorry, I am very tired :(
[21:45] <DBO> and compiz wont do as I tell it
[21:45] <kenvandine> DBO, we are in beta freeze now :)
[21:45] <kenvandine> does it ever?
[21:45] <DBO> yes
[21:45] <DBO> frequently
[21:45] <DBO> but right now
[21:45] <DBO> it hates me
[21:45] <kenvandine> well i am outta here... have a great weekend guys
[21:46] <nhaines> kenvandine: \o_
[22:30] <DBO> htorque, present?
[22:31] <htorque> DBO: ya
[22:32] <DBO> htorque, please pull the branch again
[22:32] <DBO> and test
[22:32] <DBO> rev 1406 is what you want
[22:38] <DBO> htorque, also, if you are wondering, yes, it took me THAT long to fix
[22:38] <DBO> KILL me
[22:38] <htorque> poor you :-)
[22:39] <htorque> DBO: \o/
[22:39] <htorque> sweet
[22:39] <DBO> htorque, please leave a note here that you have tested and confirmed this working: https://code.launchpad.net/~unity-team/unity/unity.keyboard-util/+merge/73116
[22:42] <htorque> DBO: if it should fail to get a preview of the window, that's not to fix in that feature, right?
[22:43] <DBO> htorque, is that window maybe minimized?
[22:43] <DBO> basically, right now, NEVER restart compiz with a minimized window
[22:43] <htorque> no no, that was just hypothetical
[22:43] <DBO> no its not related
[22:43] <DBO> but, that shouldn't happen anymore
[22:43] <DBO> unless you restart compiz with a minimized window
[22:43] <DBO> (compiz wont see the window)
[22:44] <DBO> and then all sorts of funny things happen
[22:44] <DBO> we of course need to fix that
[22:44] <htorque> ok, in that case i'll add the comment :)
[22:46] <DBO> thanks :)
[22:47] <DBO> htorque, do you also do community code reviews?
[22:48] <htorque> nope, just testing
[22:48] <htorque> and i already broke it: with two terminals opened, run "sleep 5 ; exit" in one and initiate the preview → unity crashes
[22:49] <DBO> haha
[22:49] <DBO> thats not related to this
[22:49] <DBO> but okay
[22:49] <DBO> I'll fix it :)
[22:49] <DBO> thanks, I never even thought to try something silly like that
[22:50] <htorque> i'm a living fuzzy testing tool ;-)
[22:50] <DBO> I like it
[22:50] <DBO> do you use the blur?
[22:50] <htorque> yeah
[22:51] <DBO> does it hurt your performance?
[22:51] <DBO> when the launcher is blurring
[22:51] <htorque> there was a recent commit that made things much better
[22:51] <htorque> wouldn't call it a problem anymore
[22:55] <htorque> heh, i'm loving that feature! wouldn't have used it with the down arrow but accessing it with one hand = win.
[22:55] <htorque> DBO: you earned your weekend! ;-) i'm off, cya!