[00:11] <snadge> ergh.. thats right.. i busted my work pc
[00:11] <snadge> with unity from trunk
[00:14] <bschaefer> DBO, hey. would you mind taking a look at a merge into LauncherController.cpp
[00:14] <bschaefer> https://code.launchpad.net/~brandontschaefer/unity/new.fix-896122/+merge/90981
[00:32] <snadge> when you run unity from your home dir
[00:33] <snadge> it still runs many of the unity processes from /usr/lib
[00:33] <snadge> eg.. unity-panel-server and bamfdaemon (which i compiled into my homedir)
[00:34] <snadge> so i just renamed them to .orig and symlinked them
[00:34] <snadge> however.. i still have to run unity --replace after i log in
[00:34] <snadge> i couldn't figure out how to get lightdm, to exec unity from my homedir instead of /usr/bin
[00:37] <snadge> on the flip side.. i havn't noticed the focus bug yet
[01:49] <snadge> :(
[02:10] <htorque> a little progress indication in checkbox would be nice, e.g. "Checkbox Unity Tests (9/38) - launcher/expose-minimizedapp"
[02:13] <mhall119> thumper: did you see my invite to the unity.u.c/get-involved sitemap?
[02:13] <thumper> hi
[02:13] <mhall119> hey
[02:14] <thumper> yes... been firefighting emails mostly today
[02:14] <mhall119> no worries, just wanted to make sure it went through
[02:24] <snadge> i know im a pain in the ass outsider.. but.. can someone off the top of their heads explain why the default "filter" in dash, isnt displaying anything ?
[02:25] <snadge> eg.. its meant to have.. apps, blah etc.. and thunderbird.. but its just blank ;)
[02:25] <snadge> someone did warn me that compiling from trunk was problematic atm.. and that several libs needed to be merged
[02:26] <snadge> ive only recompiled the bare minimum.. nux, bamf (probably screwed that up) and unity
[02:29] <DBO> thumper, I dont think I can do the OMG ubuntu thing
[02:29] <DBO> I am not very good at representing stuff to the public :)
[02:30] <mhall119> DBO what OMG Ubuntu thing?
[02:31] <DBO> introducing the MM work
[02:31] <mhall119> DBO writing something, or doing an interview?
[02:31] <DBO> I dont know
[02:31] <DBO> nothing was official anyhow
[02:31] <DBO> we never talked to them
[02:31] <DBO> it was just a
[02:31] <mhall119> DBO can be a middle-man if you'd like
[02:31] <DBO> "hey someone should do something with OMGubuntu about the multi-monitor work"
[02:31] <mhall119> I can write articles for OMG
[02:33] <mhall119> DBO: if you're interested, I can write up the article, with a little bit of Q&A between you and I thrown in
[02:33] <mhall119> if you'd feel better doing it that way
[02:33] <DBO> ehhhhh
[02:33] <DBO> one second
[02:35] <thumper> DBO: I'll do it
[02:35] <DBO> thanks dude :)
[02:37] <htorque> question about one checkbox test: two nautilus instances, one on workspace 1, one on workspace two - what arrows should i expect to see?
[02:37] <htorque> the test description says "two arrows", but where? one left, one right? two on the left?
[02:54] <ali1234> how do i report bugs in this checkpoint-unity thing?
[02:54] <ali1234> checkbox-unity sorry :)
[03:00] <snadge> mhall119: can you update the compiling unity from source article whilst you're at it ? :P
[03:01] <mhall119> snadge: no, I can write, I can't edit :(
[03:01] <mhall119> and even the things I write have to be approved by the site's editors
[03:01] <snadge> let me check who wrote it
[03:01] <htorque> snadge: is this not working? http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source
[03:02] <snadge> it needs some modifications or something
[03:02] <htorque> (the workarounds probably are no longer necessary, haven't checked)
[03:02] <snadge> workaround #2 isnt needed
[03:02] <snadge> i did workaround #1 without testing whether its still needed
[03:03] <snadge> the article doesnt mention that you should update your path to include unity in your home directory.. before /usr/bin
[03:03] <snadge> problem is.. i did that in my .bashrc .. so of course lightdm ignores that
[03:03] <snadge> the instructions incorrectly say that you should just log in.. and it will magically work.. not true
[03:04] <snadge> i log in.. unity starts crashing.. have to quickly open a shell and type unity --replace
[03:04] <snadge> before it completely crashes and you lose ability to input into the terminal.. if you run unity from console.. it crashes
[03:05] <snadge> also it would appear that most parts of unity completely ignores $PREFIX
[03:05] <htorque> i'll finish the unity ppa test and then try to compile from trunk
[03:05] <snadge> i had to compile bamf from trunk.. in addition to nux
[03:05] <htorque> (could take a while)
[03:05] <snadge> otherwise unity wouldn't compile
[03:07] <snadge> and then unity continues to use bamf from /usr/lib/bamf/bamfdaemon (which i renamed to .orig and symlinked to the one in $PREFIX)
[03:07] <snadge> also the panel service.. i also renamed .orig and symlinked
[04:25] <htorque> is the alt+tab switcher supposed to show windows from different workspaces?
[04:55] <thumper> htorque: not any more
[04:55] <htorque> then the checkbox-unity test should see an update ;-)
[04:58] <thumper> haha
[05:00] <htorque> thumper: that probably also affects the pips next to launcher items (only one instead of two for one window on WS1 and one on WS2)?
[05:12] <thumper> htorque: hmm...
[05:12] <thumper> htorque: we need a way to file bugs against the tests :)
[05:12] <thumper> htorque: if you are around in an hour or so, didrocks will turn up
[05:12] <thumper> he is the man
[05:13] <htorque> i just can't do a lot if i don't know the expected behavior. :-P
[05:13] <imnichol> Does unity control the screen locking?  Or is that a different program?
[05:14] <htorque> thumper: should bugs about checkbox-unity go to checkbox or unity (multi-monitor tests don't run for me)?
[05:14] <thumper> imnichol: different program right now (gnome-screensaver)
[05:14] <thumper> htorque: I'm not sure
[05:15] <imnichol> thumper, would that hold true when I suspend my computer?
[05:15] <thumper> imnichol: I think so, but not 100%
[05:15] <imnichol> thumper, thanks.  I'm filing a bug and I want to make sure it's filed against the correct package
[05:15] <thumper> htorque: if you want to, file under unity, but add a tag "checkbox"
[05:16] <thumper> kk
[05:16]  * thumper EODs
[05:16] <htorque> thumper: will do, thanks
[07:51] <ivoks> anyone interested in unity 5.2 feedback? :)
[07:56] <ivoks> well, the mouse thing works great as far as i can tell; the only problem i see are the icons in the launcher... those are all black; just black squares
[08:59] <Saviq> greyback, do you remember such a bug being filed: make the launcher hide with a window; try dragging something to the launcher edge, close the offensive window => launcher doesn't show?
[09:00] <Saviq> what's weird is that we have that in both trunk and shell
[09:00] <Saviq> that work completely different with regards to intellihide
[09:00] <Saviq> so that suggests it's a WM issue
[09:07] <greyback> Saviq: hmmm, that's not familiar to me
[09:08] <greyback> Saviq: will it be an issue with autohide? Intellihide is being dropped
[09:08] <spikeb> it is? :(
[09:09] <greyback> spikeb: autohide is currently considered superior. But that might change
[09:09] <Saviq> greyback, I would assume it's not an issue with autohide
[09:09] <Saviq> since it doesn't care about windows
[09:10] <greyback> Saviq: me too
[09:10] <Saviq> yeah, looks good
[09:10] <Saviq> btw, first I've heard about dropping intellihide... I must say I'm surprised, it was a good compromise, IMO
[09:11] <greyback> I was too
[09:15] <greyback> Saviq: for the "who lives in a colder place right now" competition, I'm looking at a thermometer with -8 on it
[09:16] <Saviq> you lost
[09:16] <Saviq> -10.9
[09:16] <Saviq> it's supposed to be -24 Friday night
[09:16] <Saviq> F*CK
[09:16] <greyback> jaysus
[09:17] <Saviq> that's, incidentally, when I'm leaving for a week's holidays
[09:17] <greyback> No snow here :(
[09:17] <greyback> Ah! To the sun I hope :)
[09:17] <Saviq> no snow here, either
[09:17] <Saviq> too cold
[09:18] <Saviq> greyback, snowboarding, so yes, sun is very much wanted for
[09:19] <greyback> Saviq: boarding! Anywhere I know?
[09:19] <Saviq> Livigno
[09:19] <Saviq> Italy
[09:20] <greyback> They've plenty of fresh snow I think. It'll be great!
[09:23] <snadge> sudo apt-get install indicator-weather
[09:24] <snadge> 26C
[09:26] <Saviq> greyback, yeah, looking forward to it
[09:26] <Saviq> snadge, you're melting!
[09:26] <greyback> snadge: niice :)
[09:27] <greyback> JohnLea: hello!
[09:27] <greyback> JohnLea: I hope you've had your cup of coffee, cause I've a couple of questions for you
[09:32] <JohnLea> greyback; just drinking my coffee now ;-)
[09:32] <JohnLea> greyback; and good morning!
[09:32] <greyback> JohnLea: good morning to you too, I hope you're well
[09:34] <greyback> JohnLea: I hear you've lots of visual tweaks to the HUD in Unity. Do any of the changes deviate from the mockups?
[09:36] <JohnLea> greyback; where did you hear that?  we have not touched the HUD visual design at all in the last 3 months.   However we are going to make one small update, which is adding keyboard shortcuts, but this doesn't change any other elements
[09:38] <greyback> JohnLea: ok.
[09:39] <greyback> JohnLea: I heard you generated a list of bugs on the current implementation of the HUD in the PPA. I just wanted to check nothing changed
[09:40] <greyback> JohnLea: second question, and more technical: dyams was asking about keyboard shortcut problem.
[09:40] <greyback> It is possible for user to set wildly different keyboard shortcuts to switch workspaces & move windows between workspaces.
[09:41] <greyback> Possible to have Super+left to move right, and Alt+down to move up - as extreme example
[09:41] <greyback> In shortcut overlay, how can we reflect that?
[09:50] <JohnLea> greyback; ideally the overlay will would by dynamically built using the current keyboard shortcuts, I know this is what they are trying to do for the 3d version
[09:51] <snadge> who else is building unity from trunk atm
[09:51] <snadge> a bunch of libs have been updated .. and i found the running it from your home dir thing
[09:51] <snadge> just doesnt work out so well
[09:51] <greyback> JohnLea: ok, so we can expand the list in the mockup to encompass what also is needed
[09:53] <JohnLea> greyback; we should only display the keyboard shortcuts that correspond to actions in the keyboard shortcut overlay document & design.  e.g. the shortcuts themselves can change, but shortcuts for other actions will not be added
[09:55] <dyams>  JohnLea: yes, but the issue is 'Switch workspaces' alone can have four different key combinations, its possible in metacity
[09:57] <greyback> It's possible to set "Switch to workspace right" to Alt+right, and "Switch to workspace left" to Super+left
[09:58] <greyback> How to express that in the overlay is our problem
[10:00] <JohnLea> greyback; in the case where the keycombo is not symmetrical we could not display it at all?  A user will only arrive at that state if they change the keycombo themselves, in which case we can assume it is a shortcut they remember
[10:25] <kamstrup> mhr3: does https://code.launchpad.net/~mhr3/libunity/dbus-activation-fixes/+merge/90919 fix the issue with the files lens not initially populating the home screen?
[10:26] <mhr3> kamstrup, dunno really, waiting for the packages to hit archives to test proper dbus-activation
[10:27] <kamstrup> mhr3: how did you end up debugging it btw?
[10:28] <mhr3> kamstrup, adding breakpoint(); before app.run() and doing a search when it was waiting there
[10:29] <mhr3> (cause the service is dbus-registered before app.run)
[10:29] <snadge> ahh okay so its not just me having an issue with unity from trunk then
[10:29] <kamstrup> ah
[10:29] <snadge> i have already pulled bamf from trunk to get it to compile.. but there are other dbus issues yeah, and the default home lens is not populated
[10:30] <snadge> but at least the annoying focus bug is fixed :D
[10:31] <snadge> would be nice if there was a unity trunk ppa ;) *massive hint* *extreme nudging*
[10:32] <mhr3> snadge, you mean like the staging ppa?
[10:32] <snadge> is dbus and bamf in there as well?
[10:32] <mhr3> it's building trunk every day
[10:34] <snadge> not familiar with the staging ppa.. and i would probably only want to selectively install things from there
[10:34] <mhr3> kamstrup, btw it's nicely testable with the test tool... if your dbus service file points to correct version of the lens :)
[10:35] <mhr3> just kill it and let the test tool spawn it
[10:35] <tsdgeos> snadge: there's a unity staging ppa, not whole distro staging ppa
[10:35] <tsdgeos> snadge: https://launchpad.net/~unity-team/+archive/staging
[10:35] <snadge> ahh right.. the instructions here: http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source
[10:35] <kamstrup> mhr3: test tool ftw!
[10:35] <snadge> dont mention that :) .. and they're slightly out of date.. you need to build more than just nux and unity
[10:35] <snadge> to get the latest trunk build to work
[10:36] <snadge> plus.. unity doesnt like running from your home dir it seems.. it still tries to run things in /usr/lib
[10:36] <kamstrup> snadge: if you really really want bleeding edge then you should use lp:unity-jhbuild
[10:36]  * mhr3 grins
[10:36] <kamstrup> it builds all necessary components for the unity and unity-2d stack
[10:37] <kamstrup> but if you're not into fixing weird build issues then I'd go with the staging ppa which is also highly uptodate
[10:37] <snadge> well i was just trying to verify that the window focus problem had been fixed.. which it has been :)
[10:37] <kamstrup> the benefit with jhbuild is that it will not hose your system if it breaks, as everything runs out of your home dir
[10:37] <snadge> well at least ive been using it all day at work.. and didnt notice the problem.. so thats a good sign that it has been fixed
[10:38] <kamstrup> nice :-)
[10:38] <snadge> however.. i was annoyed at having to run unity --replace every time i login
[10:38] <snadge> since lightdm automatically starts /usr/bin/unity instead of $PREFIX/bin/unity
[10:38] <snadge> as i have my path set in my .bashrc.. and obviously lightdm doesnt use that
[10:40] <snadge> jh-build doesnt exist for precise ?
[10:40] <snadge> ahh its just a script
[10:41] <kamstrup> mhr3: ! configure.ac:157: required file `tools/Makefile.in' not found
[10:42] <mhr3> kamstrup, run autogen?
[10:42] <kamstrup> mhr3: that is what I *get* from running autogen.sh
[10:42] <kamstrup> mhr3: you forgot to add the tools/Makefile.am
[10:42] <mhr3> ah..
[10:43] <kamstrup> :-)
[10:43] <mhr3> kamstrup, and pushed
[10:46] <kamstrup> mhr3: can you choke the warnings from the tool about unhandled errors? Considering that it is one file 4 warnings from valac is maybe a bit much :-)
[10:46] <kamstrup> mhr3: down the road i'd like us to compile everything without valac warnings - so let's start by not having new code emit warnings :-)
[10:46] <mhr3> kamstrup, but at least you see it got compiled :)
[10:47] <kamstrup> mhr3: indeed!
[10:52] <mhr3> kamstrup, there, no more nicely formatted warnings... it's like cpp now :)
[10:53] <kamstrup> ah, nice boring compiler output
[10:53] <kamstrup> mhr3: why explicitly unity-lens-test-tool and not just unity-tool?
[10:54] <kamstrup> mhr3: the reason why I proposed unity-tool was that enterprising terminal junkies could conceivably use it to drive unity via shell scripts
[10:54] <mhr3> kamstrup, it can't really introspect unity, can't it?
[10:55] <kamstrup> mhr3: it can (in theory) do all instrumentation that is publicly available
[10:55] <kamstrup> on both lenses and unities
[10:55] <mhr3> kamstrup, right, but we already have tools to talk to unity itself, don't we?
[10:55] <kamstrup> we have?
[10:55] <mhr3> or is it just internal to autopilot?
[10:56] <kamstrup> afaik we just have the autopilot tools
[10:56] <kamstrup> and the dbus debuggin introspection, but I don't consider that "public api"
[10:57] <mhr3> kamstrup, so what else would the tool do other than talking to lenses?
[10:57] <mhr3> cause besides the introspection there's not much to use, is there?
[10:57] <kamstrup> mhr3: list favorites, whether unity is running, if we support querying unity capabilities then also that
[10:58] <kamstrup> like 2d/3d, vendor patch level etc
[10:59] <kamstrup> mhr3: listing installed lenses, etc etc
[10:59] <mhr3> oh well... afterall it's just a name, feel free to "Needs fixing" :)
[10:59] <kamstrup> mhr3: i know I am anal:-)
[11:00] <Andy80> hello
[11:07] <kamstrup> mhr3: ok, comments up on https://code.launchpad.net/~mhr3/libunity/test-tool/+merge/91027
[11:11] <mhr3> kamstrup, thx, as for the --test-server-mode - it allows you to pass a couple of executable test scripts (or directory) and it will run each of those as a test case (failing it they return != 0)
[11:11] <mhr3> kamstrup, so like with test cases for apps-lens you'd just do `unity-tool --test-server-mode ./tests`
[11:12] <mhr3> i imagined we could use that to run make check
[11:13] <kamstrup> mhr3: ah, right. Nice! Figured it out after toying with the apps lens test branch
[11:14] <mhr3> right, there's a readme :)
[11:14] <tsdgeos> greyback: i hope that i understood you correctly in https://code.launchpad.net/~aacid/unity-2d/unity-2d_tests_for_rtl/+merge/90849 and what you meant was removing your name from the new file
[11:14] <greyback> tsdgeos: yep, that's all
[11:14] <tsdgeos> ok :-)
[11:15] <greyback> tsdgeos: I don't see the point in keeping it there, unless we all want to keep adding names everywhere
[11:15] <tsdgeos> yeah
[11:15] <greyback> but it's a nice solution for the ltr and rtl tests. I was not sure what to do myself
[11:16] <tsdgeos> agreed, gets crazy, in poppler we have the policy to do it right, and you end up with stuff like http://cgit.freedesktop.org/poppler/poppler/tree/poppler/Gfx.cc where there's 21 names there :D
[11:22] <greyback> JohnLea: sorry I disconnected earlier, but thank you for sorting out our problem
[11:22] <greyback> tsdgeos: lol, yeah that's bad
[11:23] <greyback> also it doesn't really make sense, if you make a one line change, that doesn't give you copyright on the whole file. IANAL tho :)
[11:23] <snadge> i can understand why you would want your name removed from unity.. *bdom tish* ;)
[11:23] <greyback> snadge: oh the harshness
[11:24] <greyback> snadge: we're unity2d anyway ;)
[11:24] <snadge> naw.. seriously im one of the few non involved fanbois.. its okay ;)
[11:24] <snadge> the community has reacted a bit over the top i think.. but its okay, some of the hate is equally directed towards gnome-shell
[11:25] <snadge> im just pleased as punch my two main gripes with unity have been fixed in trunk.. which should mean that they'll make their way into 12.04 :)
[11:26] <greyback> snadge: yay!
[11:26] <snadge> alt tab now defaults to apps on the current workspace.. high five to whomever did that
[11:27] <snadge> a friend of mine griped that you cant move the launcher anywhere other than the left side of the screen
[11:28] <snadge> i hadn't even noticed that.. but apparently some weirdos run their monitors in portrait mode
[11:28] <snadge> so it would make sense to be able to move it to the top or the bottom in that case
[11:29] <snadge> also other weirdos would like to have it on the right hand side of the screen.. i personally dont see the issue with allowing people to do that
[11:33] <kamstrup> mhr3: some more nitpicking on https://code.launchpad.net/~mhr3/libunity/test-tool/+merge/91027
[11:37] <jasox>  freeze for Alpha
[11:37] <jasox> ups
[11:37] <jasox> Hi guys, I was wondering what font size (small/normal) do you use in ubuntu on 24" monitor(16:10) ?
[11:43] <tsdgeos> greyback: can you merge those patchse in already, i think some will conflict between themselves so if you merge them now i'll fix the conflicts
[11:43] <greyback> tsdgeos: ah boo, I meant to check that.
[11:44] <tsdgeos> the rtl one will conflict with the bfb one
[11:44] <tsdgeos> it's fine
[11:44] <tsdgeos> just the sooner you merge them the sooner i fix them D
[11:45] <Saviq> hey, sorry for not being there for the standup, got caught up in stuff :
[11:45] <Saviq> greyback, I'm sure you've taken over, anything I need to know?
[11:46] <Saviq> greyback, also, I've built the package just fine, are you sure your env is clean?
[11:46] <greyback> Saviq: nope, nothing major to report
[11:46] <Saviq> greyback, try bzr bd
[11:46] <greyback> Saviq: hmm, ok I will
[11:46] <Saviq> and cleaning up build-area first
[11:47] <jasox> I am just testing ubuntu 12.04 alpha, lots of improvements. I would be nice if we had when you type alt-F1 emacs of vim key bindings. What do you think ?
[11:51] <Saviq> jasox, please take that up in #unity-design
[11:52] <Saviq> jasox, or best file a bug against ayatana-design
[11:52] <jasox> Thanks Saviq ;)
[11:52] <jasox> didn't know for unity-design
[11:52] <Saviq> jasox, sorry
[11:52] <Saviq> meant #ubuntu-design
[11:52] <jasox> :D np
[11:53] <Saviq> JohnLea, btw, with all the ayatanas going away, will there be a ubuntu-design project taking over?
[12:08] <JohnLea> Saviq; yes, we are just renaming everything (well the irc and mailing list at least) from ayatana to ubuntu-design
[12:08] <Saviq> JohnLea, will that be true for the LP project?
[12:09] <JohnLea> Saviq; that would be a good idea, but not no.1 priority atm
[12:09] <Saviq> ok, just curious, thanks
[12:33] <Saviq> dyams, is CopyAction what's used un Unity, too?
[12:34] <Saviq> dyams, btw, you _do_ have mouse cursor feedback :)
[12:34] <Saviq> the setAction() in onDragEnter takes care of that
[12:35] <Saviq> it's a bit slow, though
[12:35] <Saviq> like, I need to wait a second for the icon to get updated
[12:35] <Saviq> I'm wondering if caching the mime types on the launcher items might be a good idea
[12:35] <Saviq> but we might leave that for later
[12:36] <dyams> saviq: ah...
[12:37] <dyams> saviq: checking mouse feedback
[12:37] <Saviq> dyams, the cursor changes to a hand with + sign
[12:38] <Saviq> but after a second or so
[12:38] <Saviq> dyams, another question... when validatingUrisForLaunch, you're checking against the .desktop file and the MimeType there
[12:38] <Saviq> ah wait
[12:38]  * Saviq needs to read about the gio APIs
[12:38] <dyams> saviq: yes, nearly half a sec delay i see here
[12:39] <dyams> :)
[12:39] <Saviq> dyams, can you try and find out where is the delay? whether you're not getting the onDragEnter event earlier
[12:39] <Saviq> or maybe the file parsing takes so long?
[12:42] <dyams> saviq: I don't think parsing takes so long..but i can check it out later
[12:42] <Saviq> dyams, ok, I'll have a quick check myself what's going on
[12:42] <dyams> saviq: ok
[12:44] <Saviq> dyams, you don't get the onDragEnter event soon enough
[12:44] <Saviq> dyams, so that's something that needs to be addressed higher up the stack
[12:44] <Saviq> branch approved, then
[12:44] <tsdgeos> greyback|lunch: confused about last comment in https://code.launchpad.net/~aacid/unity-2d/unity-2d_tests_for_rtl/+merge/90849 that branch is fully merged and it seems the conflicts would happen when mergning the other branches, and anyway that one is not set to merge yet
[12:45] <Saviq> dyams, assuming you pushed the .append() fix/
[12:45] <Saviq> dyams, I'll wait for that before approving
[12:45] <dyams> saviq: i made the fix, lemme push it
[12:46] <Saviq> dyams, also, please add a comment about the mouse cursor change in the manual test
[12:46] <dyams> saviq: ok
[13:02] <dyams> saviq: Updated
[13:03] <Saviq> dyams, thanks
[13:05] <dyams> saviq: no prob
[13:07] <Saviq>  dyams, oh one more style issue, please add brackets around g_object_unref
[13:07] <Saviq> line 1096
[13:08] <Saviq> sorry for that
[13:08] <Saviq> after that I'm approving
[13:11] <dyams> saviq: one sec
[13:19] <dyams> saviq: updated
[13:19] <Saviq> dyams, thanks, approving
[13:19] <dyams> saviq: thank you
[13:22] <mhall119> dyams: could you take a look at https://code.launchpad.net/~haggai-eran/unity/rtl-menu-popup/+merge/71541 and let me know what it's waiting on?
[13:24] <dyams> mhall119: one sec
[13:24] <mhall119> thanks
[13:25] <dyams> mhall119: this is for Unity
[13:26] <dyams> mhall119: not for unity-2d
[13:26] <Andy80> Saviq: hi :) you have a minute to give a look to a unity-2d library compilation error?
[13:26] <Saviq> Andy80, there's a bunch of us here
[13:26] <Saviq> Andy80, pastebin it and we'll try and help
[13:27] <Andy80> Saviq: ok :)
[13:28] <mhall119> dyams: oh, sorry, thought you were a unity guy
[13:28] <dyams> mhall119: it's ok, no prob
[13:29] <Andy80> the error is this one http://pastebin.com/1p9v5HeH and the complete explaination is written in this email https://lists.launchpad.net/unity-dev/msg00404.html - please note that I'm trying to compile these libraries using Qt5, not Qt4 (that's what I want, not a mistake).
[13:29] <Saviq> mhall119, if you want we can give you a status update on RTL in unity-2d ;)
[13:30] <Saviq> Andy80, looks like some APIs for QML plugins has changed between Qt4.7 and Qt5
[13:30] <mhall119> Saviq: dyams: yeah, looks like this is the -2d MP: https://code.launchpad.net/~haggai-eran/unity-2d/4.0-rtl/+merge/81377
[13:31] <Andy80> Saviq: so we need to first change the code for these libs and patch them before being able to recompile, right?
[13:31] <Saviq> mhall119, this is mainly waiting for our merge of unity-2d-shell, that's going to happen this week
[13:31] <Saviq> Andy80, yes, it can't find the headers for QDeclarativeExtensionPlugin
[13:32] <mhall119> Saviq: it's been waiting since november?
[13:32] <Saviq> mhall119, no, then it was waiting on someone to review it
[13:32] <Saviq> mhall119, problem with those things is that we have noone that actually uses RTL
[13:32] <Saviq> to verify the fixes
[13:32] <Saviq> mhall119, and obviously time is a problem
[13:33] <Saviq> but I really think that's going to get into 12.04
[13:33] <Andy80> Saviq: ok. Florian suggested me some changes to do for unity-2d, probably the same changes also apply to the unity-2d libraries. I'll try to implements them and see if I can patch them, thanks for now :)
[13:33] <Saviq> if noone else, I'll do it myself
[13:33] <mhall119> Saviq: reading the comments, it looks like dyams approved it back in november, but there was an issue with it being associated with bugs it didn't close, so it wasn't applied, or something to that effect
[13:34] <Saviq> mhall119, I don't think it was reviewed properly was it? let me take a look
[13:34] <Saviq> mhall119, but yes there was definitely some weirds stuff
[13:34] <Saviq> mhall119, https://code.launchpad.net/~haggai-eran/unity-2d/rtl-rebased/+merge/82151 that's the "new" MR
[13:35] <Saviq> it's only a 300 LOC diff
[13:35] <mhall119> Saviq: ah,thanks, it appears it wasn't marked as superceded
[13:35] <Saviq> so it will definitely get in before 12.04
[13:35] <Saviq> mhall119, the other one was rejected
[13:36] <dyams> mhall119: oh that one...somehow that branch was messed up..
[13:36] <dyams> mhall119: so, we asked to resubmit
[13:36] <mhall119> ok, do either of you have the ability to remove/delete/mark superceded that old MP?
[13:37] <Saviq> mhall119, it's rejected, isn't that enough?
[13:37] <mhall119> MacSlow|lunch: ping me when you're back
[13:37] <Saviq> mhall119, deleted
[13:38] <mhall119> Saviq: you're right, I'm looking at this MP for -3d
[13:38] <mhall119> I still need someone to look at that for me
[13:39] <greyback> tsdgeos: yep, but when the freeze ends, the branches will merge in order, meaning if I approve your tests_for_rtl now, tarmac will fail to merge it
[13:39] <greyback> tsdgeos: it was just a warning
[13:50] <tsdgeos> greyback: ok
[13:51] <tsdgeos> greyback: when does the freeze end?
[13:52] <Saviq> tsdgeos, tomorrow, I think
[13:52] <tsdgeos> ok
[13:52] <Saviq> didrocks, is that right ^ ?
[13:54] <MacSlow> mhall119, what's up?
[13:55] <mhall119> MacSlow: can you give me an update on https://code.launchpad.net/~haggai-eran/unity/rtl-menu-popup/+merge/71541 ?
[13:56] <mhall119> I'm told the unity-2d patch for this is already being handled, but this one doesn't appear to have had any feedback
[14:00] <Saviq> brb, going to test some MM stuff
[14:00] <MacSlow> mhall119, since that branch needs a patched nux before it can land and that particular nux-branch is still nowhere near landing (being approved) I'd say this is on hold still
[14:05] <mhall119> MacSlow: can you respond to him in https://code.launchpad.net/~haggai-eran/nux/rtl/+merge/71538 then?  He asked back in november if he should just push with --overwrite after he rebases
[14:05] <mhall119> that's the last comment on the MP
[14:05] <mhall119> or maybe jaytaoko would be the better person to respond
[14:06] <MacSlow> mhall119, indeed Jay would be the better person to contact... as he seems to have arleady looked at Haggai's nux-branch
[14:07] <mhall119> jaytaoko: ^^ can you respond to Haggai on that nux MP?
[14:12] <greyback> Saviq: yep, you're right
[14:12] <greyback> tsdgeos: ^^
[14:14] <tsdgeos> tomorrow meaning we can commit stuff tomorrow or that tomorrow is still freeze day?
[14:41] <kenvandine> mhall119, you have a couple lines in you copyright file that should be removed, looks like you redirected grep output into it
[14:41] <mhall119> in the copyright?
[14:41] <mhall119> huh, let me check
[14:41] <kenvandine> debian/copyright
[14:43] <mhall119> kenvandine: which lines?
[14:43] <greyback> tsdgeos: freeze takes at least 3 days. I can't say with certainty when it ends
[14:43] <kenvandine> mhall119, in singlet
[14:43] <tsdgeos> well
[14:43] <mhall119> this was generated by python-mkdebian, IIRC
[14:43] <tsdgeos> if it's much longer i'll end up with 20 MR
[14:43] <tsdgeos> i'm on 12 already
[14:43] <kenvandine> mhall119, ok... bug there
[14:43] <kenvandine> you just need the 2 lines
[14:43] <kenvandine> and remove the binary file matches line
[14:44] <mhall119> kenvandine: pushing the changes
[14:46] <mhall119> rev 2
[14:46] <mhall119> I don't need to update the changelog for this do I?
[14:48] <kenvandine> not yet
[14:56] <kenvandine> mhall119, http://paste.ubuntu.com/825152/
[14:56] <kenvandine> hopefully reading the diff will help explain
[14:57] <kenvandine> mhall119, and the list in the Format field explains all the values
[14:59] <htorque> agateau: hi! can you (or someone else that knows the unity specs in detai) look over the current checkbox-unity test descriptions? see bug 924669
[14:59] <ubot5`> Launchpad bug 924669 in unity (Ubuntu) "checkbox-unity: test descriptions need an update" [Undecided,New] https://launchpad.net/bugs/924669
[15:01] <agateau> htorque: will look into this, thanks
[15:01] <htorque> thanks :)
[15:01] <mhall119> kenvandine: pushed, do you know who maintains python-mkdebian?
[15:01] <kenvandine> nope
[15:02] <mhall119> ok, I'll try to find out
[15:02] <kenvandine> mhall119, also you should use dh_python2 instead of pysupport
[15:02] <kenvandine> http://paste.ubuntu.com/825165/
[15:02] <kenvandine> and i added a watch file for you too
[15:03] <kenvandine> although not tested since there are no released tarballs
[15:03] <kenvandine> this is a simpler rules file and uses python2 properlyt
[15:05] <kenvandine> mhall119, you also need to fix the description, replace the UNKNOWN
[15:05] <htorque> does anyone have an idea why indicator-loader3 freezes the desktop when running the appmenu indicator? here's its output: http://paste.ubuntu.com/824509/
[15:17] <tsdgeos> greyback: if you're doing reviews, i have a few of them i just created to backport from -shell to unity-2d that assigned to Saviq but can add you too if you feel like... ;-)
[15:19] <greyback> tsdgeos: :) I'm finishing up Kaleo's MR now, then have blog post to write. Then I'll either attack your MRs or make a few of my own
[15:20] <greyback> tsdgeos: there's one there I assigned to Saviq, maybe you can have a look, take the pressure off him
[15:20] <Saviq> guys, I'm very close to fixing the damn ScreenInfo thingy
[15:20] <tsdgeos> Saviq: awesome
[15:20] <greyback> Saviq: nice
[15:20] <jaytaoko> mhall119: I will respond to haggai
[15:21] <tsdgeos> greyback: i can take taht MR if you want and Saviq doesn't mind
[15:21] <Saviq> you will be able to either a) bind to a particular screen b) particular corner c) follow the widget
[15:21] <Saviq> tsdgeos, I'm fine
[15:21] <mhall119> thanks jaytaoko
[15:23] <tsdgeos> greyback: https://code.launchpad.net/~gerboland/unity-2d/shell-background-isolate/+merge/90850 ?
[15:26] <mhall119> kenvandine: updated debian/rules, debian/control and added debian/watch (also uploaded tag.gz download to Launchpad)
[15:26] <kenvandine> cool
[15:26] <greyback_> tsdgeos: that's the one
[15:26] <mhall119> kenvandine: I can bzr builddeb from the package branch now
[15:40] <gord> mhr3, is it just me, or are the filter stage changes blocked by the model updates?
[15:40] <gord> s/stage/state
[15:41] <mhr3> gord, not sure what you mean
[15:41] <davidcalle> gord, not just you
[15:41] <gord> mhr3, it looks like the filter stage changes don't update until we get more results from the model
[15:42] <gord> s/stage/state
[15:42] <gord> geez what is it with me and that word
[15:42] <Saviq> nerochiaro, hey, you around?
[15:42] <nerochiaro> Saviq: yes, what's up ?
[15:42] <mhr3> gord, perhaps unity isn't listening to the changed signal?
[15:43] <Saviq> nerochiaro, hey, "static const int DASH_MIN_SCREEN_WIDTH = 1280; static const int DASH_MIN_SCREEN_HEIGHT = 1084;"
[15:43] <Saviq> is this right? my desktop is 1600x900, meaning I get fullscreen dash
[15:43] <mhr3> gord, or is that in unity-core?
[15:44] <nerochiaro> Saviq: as far as i know it's right, but the algo in u3d is a bit different. last i talked with Kaleo IIRC we thought it was ok like this for now
[15:44] <nerochiaro> Saviq: but i might recall wrong
[15:44] <mhr3> gord, but yea kenvandine also mentioned hickups when trying to update the filter models
[15:44] <Saviq> nerochiaro, yeah Unity isn't going fullscreen here
[15:45] <Saviq> and unity-2d wasn't, either
[15:45] <Saviq> 1084 height sounds very high
[15:45] <Saviq> it's 1080p
[15:45] <Saviq> more, even
[15:45] <gord> mhr3, hrm, i guess it might be unity not queuing a draw or something - i'll have a look later. was just an idle observation :)
[15:45] <Kaleo> Saviq, nerochiaro: these figures look wrong
[15:45] <Kaleo> 1084?
[15:45] <Saviq> yeah exactly my point
[15:45] <Kaleo> nerochiaro: does not look like we used to have
[15:46] <nerochiaro> IIRC they have been like that all the time
[15:46] <Saviq> Kaleo, the values were the same it seems
[15:46] <Saviq> but the algo must've been different
[15:46] <mhr3> gord, feel free to open a bug, so we dont loose track of it
[15:46] <Kaleo> Saviq: why do you think so?
[15:46] <nerochiaro> Saviq: at this point i suggest we just go ahead and implement the same algo as unity
[15:46] <Saviq> Kaleo, I'm looking at the diff
[15:46] <nerochiaro> it'n not that complicated anyway
[15:47] <Saviq> Kaleo, r875 in trunk
[15:47] <gord> mhr3, yeah, after i've taken a look, just need to get through this one thing i'm doing
[15:47] <mhr3> ok
[15:47] <Saviq> wrong
[15:48] <Saviq> actually no, right
[15:49] <Saviq> Kaleo, nerochiaro, before _both_ the values had to be smaller
[15:49] <Kaleo> Saviq: the check seems identical
[15:49] <Kaleo>     bool alwaysFullScreen = rect.width() < minSize.width() && rect.height() < minSize.height();
[15:49] <Kaleo> Saviq: is the new code
[15:49] <Kaleo> Saviq:     if (rect.width() < minSize.width() && rect.height() < minSize.height()) {
[15:49] <Kaleo> Saviq: was the code before
[15:49] <Saviq> ok let me look again
[15:50] <Saviq> hmm
[15:50] <Saviq> ok the code is fine, something else makes my dash fullscreen
[15:50] <Saviq> right
[15:51] <Saviq> ok so here's what's wrong
[15:51] <Saviq> nerochiaro, if at any point you display the dash on a small screen
[15:51] <Kaleo> Saviq: the fullscreen dconf key?
[15:51] <Saviq> the dconf key gets changed
[15:51] <Kaleo> Saviq: then it will be fullscreen by default
[15:51] <Kaleo> Saviq: nice onee
[15:51] <Kaleo> Saviq: bug report
[15:51] <Saviq> and here I am wondering wth :P
[15:52] <Saviq> Kaleo, yup
[15:52] <tsdgeos> Saviq: once you have the buttons in the dash you can just go and toggle the fullscreen with them ;-)
[15:52] <Saviq> tsdgeos, I'm working in trunk
[15:52] <Saviq> tsdgeos, so I actually can regardless
[15:52] <Saviq> well, not regardless but I can, since that's fine in trunk
[16:02] <nerochiaro> Saviq: so the first thing we need to fix for sure is the issue of putting back that &&
[16:02] <Saviq> nerochiaro, ?
[16:03] <nerochiaro> Saviq: you said before it went fullscreen is both h and w were < of the limit values. doesn't it go fullscreen now even if one of them is < only ?
[16:03] <Saviq> nerochiaro, no, I was wrong
[16:03] <Saviq> nerochiaro, the code is same, the only issue is that the dconf is reset when you launch dash on a small screen
[16:05] <nerochiaro> Saviq: ok, and you're right, it shouldn't save the value when the fullscreen is forced by the small screen
[16:05] <Saviq> yup
[16:16] <Saviq> tsdgeos, can you take a look at screeninfo.{cpp,h} (in either trunk or shell) and tell me where do you see m_workspacesInfo being instantiated?
[16:17] <tsdgeos> Saviq: in the constructor
[16:17] <tsdgeos> it's a member, so gets constructed there
[16:17] <Saviq> tsdgeos, implicitly?
[16:17] <tsdgeos> yep
[16:17] <Saviq> ok, makes sense
[16:17] <Saviq> you learn something new every day :)
[16:21] <Saviq> tsdgeos, last thing, does this make sense re your comment about screenNumber() only working when widget is shown http://pastebin.ubuntu.com/825268/ ?
[16:21] <Saviq> or should I check for .visible?
[16:23] <tsdgeos> the first if doesn't make sense no
[16:24] <tsdgeos> the event->type() == QEvent::Show looks nice though
[16:24] <Saviq> my head is kind of steaming right now with that
[16:25] <Saviq> so .visible for the first one should be enough you think?
[16:26] <Saviq> .isVisible(), rather
[16:26] <tsdgeos> i don't think you even need it
[16:26] <tsdgeos> once it gets visible the show even will happen and it will get right
[16:26] <Saviq> oh right
[16:26] <Saviq> it won't fail when it's not visible
[16:26] <Saviq> and then will update as soon as it is shown
[16:27] <tsdgeos> sure the m_screen will be "wrong" for a while, but you'd still need to give it a value
[16:27] <tsdgeos> and since there's no "right" value for a non visible widget
[16:27] <tsdgeos> whatever screenNumber returns should be "good enough"
[16:27] <tsdgeos> imho
[16:28] <Saviq> ok makes sense
[16:28] <Saviq> tsdgeos, re activeWindowChanged, I couldn't find any code that actually used that
[16:28] <Saviq> so I dropped it
[16:29] <tsdgeos> hmmm
[16:29] <tsdgeos> let me see, i thought i saw something the other day when grepping
[16:29] <Saviq> if you can, please tell
[16:30] <Saviq> ah wait
[16:30] <Saviq> it's probably there in shell
[16:30] <Saviq> not in trunk
[16:31] <tsdgeos> Saviq: that's what i thought, but no, just grepped again and found nothing in -shell either
[16:32] <Saviq> yeah, windowsintersectmonitor is connecting to the signal itself
[16:32] <Saviq> so yeah, dropping it
[16:32] <Saviq> ok, r888, what a nice number, is finally ready for review, I think
[16:33] <Saviq> tomorrow morning I will merge that into shell and make sure we have MM working fine
[16:33] <Saviq> and will get back to reviews
[16:35] <Saviq> EOD
[16:35] <Saviq> see you all tomorrow
[16:36] <tsdgeos> Saviq: we still have lots of wnck_screen_get_default that don't look all nice MM
[16:36] <tsdgeos> but well
[16:36] <tsdgeos> Saviq: tty tomorrow
[16:37] <Saviq> tsdgeos, yeah, that will need to be fixed during the "proper" MM support
[16:37] <Saviq> what I was doing was just "launcher / dash always on topleft screen"
[16:37] <Saviq> but doing it a future-proof way that will allow reusing ScreenInfo easily
[16:38] <Saviq> thanks, see you laters
[16:38] <greyback_> Saviq: good evening!
[16:38] <Saviq> greyback_, you too
[16:39] <greyback_> tsdgeos: thanks for your comments, you're absolutely right, will fix
[16:39] <greyback_> mmrazik: pig?
[16:39] <greyback_> mmrazik: ping even :D
[16:39] <mmrazik> greyback_:  mhm.... bacon :)
[16:40] <greyback_> mmrazik: grr, now I'm hungry again
[16:40] <mmrazik> he he. Sorry for that.
[16:40] <mmrazik> but you started :)
[16:40] <greyback_> mmrazik: I've written up blag post into Wordpress, and now noticed I can't save it so people can read it before I publish
[16:41] <mmrazik> weird
[16:41] <greyback_> mmrazik: or am I such a Wordpress ogre that I'm missing the option
[16:42] <greyback_> I've been cursing it for the last hour tbh. How did they make it so buggy
[16:42] <mmrazik> I'm just looking at it
[16:42]  * mmrazik is no wordpress expert either
[16:43] <greyback_> I've got about 20 identical preview frames below my post. No wonder Firefox is chugging!
[16:45] <davmor2> hey gord you'll know who's responsible for the applications lens?
[16:45] <mmrazik> greyback_: does this help http://en.support.wordpress.com/posts/post-visibility/ ?
[16:47] <greyback_> mmrazik: should do, I just don't see the option anywhere.
[16:47] <greyback_> mmrazik: I'm gonna publish, then very quickly try to hide it again
[16:47] <greyback_> mmrazik: that ok?
[16:47] <mmrazik> fine with me
[16:47] <greyback_> ok cool
[16:48] <mmrazik> the dialog mentioned in that article is on right hand side
[16:49] <om26er> davmor2, kamstrup is or mhr3
[16:50] <davmor2> om26er: thanks
[16:50] <gord> davmor2, mhr3
[16:50] <gord> leave poor kamstrup alone ;)
[16:50] <davmor2> gord: oh alright then
[16:51] <greyback_> mmrazik: yep, all done. You got mail :)
[16:51] <greyback_> mmrazik: apologies for the lateness
[16:51] <mmrazik> greyback_: thx!
[16:51] <davmor2> mhr3: in applications lens filters there is a new category that isn't in precise but is in the USC of books and magazines do you need a bug to add this filter?
[16:52] <mmrazik> greyback_: don't worry. it is still earlier than I planned...
[16:52] <greyback_> mmrazik: I'm always happy to exceed expectations :)
[16:52] <mmrazik> greyback_: so it is private and I should publish it if I'm happy with it?
[16:53] <mhr3> davmor2, yes, please open a bug
[16:53] <greyback_> mmrazik: yep
[16:53] <mmrazik> ok
[16:53] <davmor2> mhr3: no worries
[16:53] <mmrazik> then I'll send the link to the other QA engineers and will publish tomorrow
[16:56] <greyback_> mmrazik: good stuff. Thanking you
[17:00] <davmor2> mhr3: bug 924982, and thanks :)
[17:00] <ubot5`> Launchpad bug 924982 in unity-lens-applications (Ubuntu) "USC has added a new section called books and magazines this is missing from filters" [Undecided,New] https://launchpad.net/bugs/924982
[17:02] <kenvandine> mhr3, i proposed a dee  branch earlier which adds a cleared signal
[17:03] <mhr3> kenvandine, i think we talked about it with kamstrup long time ago and decided we can't do that
[17:04] <mhr3> but i'll let him explain :)
[17:04] <mhr3> gtg..
[17:05] <kenvandine> o
[17:05] <kenvandine> ok
[17:05] <davmor2> kenvandine: I so expected that O to be followed up by :'(
[17:14] <nloewen> I found a bug in unity 5.2
[17:15] <nloewen> When using a transparent panel, the text fades to black, then disappears instead of fading to transparent.
[17:24] <jono> didrocks, do you know if Alt Tab is only supposed to show apps on a given virtual desktop now?
[17:24] <jono> I am getting that is the latest Unity
[17:25] <didrocks> jono: yeah, it's the new default
[17:25] <jono>  gotcha
[17:25] <didrocks> jono: same if you click on a launcher icon, you only see apps on the current ws
[17:25] <jono> do we know if this will be configurable?
[17:25] <Daekdroom> It is configurable
[17:26] <Daekdroom> It's even on ccsm
[17:26] <jono> Daekdroom, I mean configurable in GNOME Control Panel
[17:26] <Daekdroom> Ah.
[17:26] <jono> I suspect some people will miss the functionality of showing all apps
[17:26] <jono> I certainly will
[17:26] <Daekdroom> I would
[17:28] <nloewen> Oh, I hated haveing all windows in the alt tab.
[17:28] <nloewen> I like this a lot better.
[17:30] <Daekdroom> Has anyone looked into the issue that some people can't make the launcher appear using the cursor?
[17:50] <om26er> Daekdroom, its kind of knonw I believe
[17:51] <om26er> since the new mechanism is not fully working atm
[17:51] <om26er> Daekdroom, try "pusing harder" though
[17:51] <om26er> I meant the left of the screen
[17:51] <Daekdroom> I've tried enough to tell it's not working.
[17:52] <om26er> try the experimental tab for Unity plugin in CCSM
[17:54] <Daekdroom> It won't reveal even with launcher reveal pressure at 1
[17:56] <nloewen> oooh, I like the launcher reveal pressure setting.
[17:56] <nloewen> 20 was a bit high.
[18:06] <igerth> Hey
[18:16] <doctormon> Hey guys,
[18:17] <doctormon> I'm trying to make a lens and I keep getting a segfault (python using introspection)
[18:17] <doctormon> libunity-WARNING **: unity-scope-factory.vala:78: Unable to search for scopes: No such file or directory
[18:17] <doctormon> That's the last warning before the segfault
[18:24] <DBO> doctormon, you would need to run the lens in gdb and get a backtrace
[18:24] <DBO> but it sounds like you dont have the xml files installed in the right place
[18:29] <doctormon> DBO: Remind me how one restarts unity?
[18:29] <DBO> doctormon, compiz --replace
[18:30] <doctormon> DBO: And is it likely to complain if I'm running other dbus objects from the same daemon?
[18:30] <DBO> doctormon, no idea :)
[18:30] <DBO> im not really that involved with lens devel
[18:31] <DBO> I do mostly visual work
[18:31] <DBO> gord, ^^ maybe?
[18:32] <mhall119> thumper: dbarth: did you guys have any feedback on the unity.u.c/get-involved sitemap?
[18:33] <doctormon> DBO: Thanks for your help, I'm not sure what to do with a segfault, the lens file is there but what else.
[18:33] <DBO> doctormon, the segfault is in your lens?
[18:34] <mhall119> thumper: dbarth: specifically I have some gaps in the "Design" section where I'm not sure how the community can get involved
[18:36] <DBO> mhall119, is the site supposed to be live?
[18:36] <DBO> ah nevermind it works
[18:36] <doctormon> DBO: Yeah, it doesn't like lens.props.anything = something
[18:37] <DBO> goooooord gord gord get your english butt in here
[18:38] <mhall119> DBO: I'm planning a content cleanup for what's currently there
[18:38] <DBO> mhall119, its very busy...
[18:38] <mhall119> DBO: yes, hence the need for a cleanup :)
[18:39] <mhall119> DBO: if you're interested in helping, send me your email so I can invite you to the google doc
[18:39] <DBO> Im about as clear at articulating my thoughts as a drunken rhino
[18:39] <mhall119> it's just a list of lists right now
[18:39] <DBO> (though, I guess he gets his point across, groan pun)
[18:40] <mhall119> a sitemap, not actual content
[19:24] <imnichol> I upgraded to unity5.2 and ran the test application.  When it got to the test where it restarted unity, compiz crashed.  I was unable to report the crash because I wasn't running an ubuntu version of compiz.  Anyone else seen this?
[19:31] <balloons> imnichol, yes at the moment the apport tool doesn't work with ppas
[19:31] <imnichol> Ok thanks
[19:31] <balloons> however, you can still report the crash manually
[19:31] <imnichol> How?
[19:39] <balloons> imnichol, you can manually run 'ubuntu-bug compiz' and then file a bug
[19:39] <imnichol> Can I still do it if I restarted my computer after the crash?
[19:40] <imnichol> When compiz went down, it took unity3d with it, so I didn't have the launcher, menu bar, or window decorations
[19:40] <balloons> well the applicable logs went with the restart sadly.. however if you can reproduce the crash you can note how to reproduce and file a bug manually giving the logs from the crash when it happens
[19:41] <balloons> thanks for testing imnichol
[19:45] <imnichol> Ok
[19:45] <imnichol> No prob, thanks for explaining it
[19:45] <balloons> hopefully the tools will support this in the future
[19:45] <imnichol> Actually, it just occurred to me that I was able to switch to tty1 after the crash.  Is it possible to run ubuntu-bug from a non-graphical terminal?
[19:47] <balloons> imnichol, it is possible :-)
[19:47] <imnichol> Awesome
[19:47] <imnichol> Gonna have to do that tonight
[19:47] <imnichol> How long until the window to run these tests closes?
[19:48] <balloons> 8 am utc on thursday
[19:48] <imnichol> Ok
[19:48] <imnichol> I'm in UTC-6, so I'll have plenty of time
[19:48] <balloons> excellent :-)
[19:48] <imnichol> Thanks much all
[19:49] <imnichol> Or, I guess: thanks much balloons!
[19:49] <balloons> yvw
[19:49] <balloons> thanks for sending in your results!
[20:01] <thumper> morning...
[20:04] <balloons> NZ <3
[20:08] <mhall119> thumper: ping
[20:09] <mhall119> is everyone in dx a member of ~unity-team ?
[20:14] <thumper> mhall119: dx is an old term now...
[20:16] <thumper> mhall119: who are you concerned about?
[20:20] <mhall119> thumper: trying to determine whether an MP is coming from the community or employees for stats graphs
[20:20] <mhall119> and launchpadlib won't let me check if someone is in ~canonical or not
[20:21] <mhall119> not with anonymous logins anyway, which the current stats code uses
[20:21] <mhall119> but it can tell me if someone can do reviews for lp:unity or not
[20:23] <DBO> mhall119, yes
[20:23] <DBO> everyone in dx is a member of ~unity-team
[20:24] <DBO> mhall119, and feel free to call us DX damnit, my job title is still officially GNOME Developer
[20:24] <DBO> so I guess, you know, I develop gnomes
[20:45] <thumper> mhall119: I think that the unity-team has all the canonical unity developers
[20:46] <thumper> mhall119: and some extras by the look of it
[20:46] <thumper> mhall119: but it looks like a good indicator
[21:03] <mhall119> ok, thanks
[21:24] <swat_> hi all
[21:24] <swat_> i got the upgrade to the latest version of unity in precise yesterday, it seems nice, very quick
[21:24] <swat_> is it possible to change the amount of "force" needed to pop the launcher open?
[21:25] <swat_> at the moment it takes me a good few swipes on my netbook to open it
[21:27] <mhall119> thumper: DBO: is ~unity-team the default reviewer for anything besides unity mps?
[21:30] <DBO> mhall119, no idea :)
[21:44] <JonOomph> Hi! Has anyone else noticed that the GtkRecentChooserMenu widget is broken in Unity?  All apps that use this type of widget are broken too... but only when running Unity.  The 1st item listed in the "Recent" menu is always selected, regardless of what item was clicked.
[21:55] <Daekdroom> swat_, yes
[21:55] <Daekdroom> You can use ccsm to do that.
[22:00] <swat_> Daekdroom: i'll take a look
[22:00] <Daekdroom> swat_, I think it's Ubuntu Unity Plugin > Experimental tab > Launcher reveal pressure
[22:01] <swat_> Daekdroom: result :-) ta v.m.
[22:26] <thumper> JonOomph: can you file a bug on unity with more info?
[22:29] <JonOomph> thumper, https://bugs.launchpad.net/indicator-appmenu/+bug/752674 (36 people affected, 13 duplicates).
[22:29] <ubot5`> Launchpad bug 752674 in inkscape (Ubuntu) "GtkRecentChooserMenu always selects first entry" [Low,Triaged]
[22:30] <JonOomph> The bug report has been around for a while... but nobody wants to take ownership of it.  =)
[22:35] <thumper> JonOomph: thanks
[22:35] <JonOomph> thumper, I updated that bug report with an easy step by step way to reproduce it.  No problem.