[00:08] <mhall119> woohoo, community lens + LTP scope is working
[00:09] <davidcalle> mhall119, awesome! This is great :)
[00:24] <mhr3> thumper, all icons are now ;)
[00:25] <mhr3> anyway, time to sleep... gn
[00:27] <thumper> cool
[00:49] <mhall119> what triggers cancellable to be is_cancelled?
[00:50] <mhall119> is it only useful for asynchonous results?
[00:54] <jono> mhall119, you are working on a community lens?
[00:55] <jono> that is awesome :-)
[01:00] <mhall119> jono: yup, now I just need to get with didrocks tomorrow and get some quickly packaging goodness
[01:01] <mhall119> unlike my first attempt, the community lens is very generic now, the locoteams scope is separate
[01:01] <mhall119> so we can plug in non-locoteams from Launchpad, events from google calendar, whatever
[01:01] <mhall119> even news from planet
[01:02] <jono> mhall119, sweet!
[01:03] <mhall119> actually, a planet scope might be easy enough to bang out tonight
[01:03] <jono> mhall119, I think I might have my U1 syncing plan all sorted
[01:03] <jono> mhall119, cool
[01:20] <TheMuso> Ooo a planet scope, nice!
[01:42] <mhall119> well that was easy: http://ubuntuone.com/5kGYzSMOlKtCfFxaIWeFJA
[03:56] <agu10^_> hey
[03:56] <agu10^_> wobbly windows aren't smooth
[04:26] <snadge> ive been waiting for smspillaz to come back
[04:28] <mhall119> jono: did you see http://ubuntuone.com/5kGYzSMOlKtCfFxaIWeFJA ?
[04:42] <jono> mhall119, nice!
[04:42] <jono> I can't wait to see the community lens as it fleshes out
[04:50] <mhall119> jono: more on that tomorrow, hopefull didrocks will be able to help me get things packaged nicely for others to play with it
[04:51] <mhall119> and since it's 10 minutes until 'tomorrow' for me, I'm out
[04:58] <jono> mhall119, night!
[04:58] <jono> good work!
[08:13] <Daviey> Hi, how can i make HUD not use alt? thanks.
[08:31] <Saviq> didrocks, hey, you're the packaging guru here,
[08:31] <didrocks> Saviq: not sure about guru, but let's say that :)
[08:31] <Saviq> didrocks, we will soon have a unity-2d-shell package that replaces unity-2d-launcher and unity-2d-places
[08:31] <Saviq> and we need to sync that up with an update to gnome-session
[08:32] <didrocks> Saviq: hum, any particular reason for that?
[08:32] <Saviq> didrocks, yes, we merged the two components into a single one
[08:32] <Saviq> well, are merging
[08:32] <didrocks> Saviq: let's differ a little bit that
[08:32] <Saviq> there's only one executable
[08:32] <didrocks> Saviq: it's not what it in trunk, isn't it?
[08:32] <Saviq> didrocks, not yet
[08:32] <didrocks> Saviq: this week, we are releasing 5.2
[08:32] <didrocks> so I have frozen trunk
[08:32] <Saviq> didrocks, we'll probably merge wednesday
[08:32] <Saviq> didrocks, that's fine
[08:33] <Saviq> I just want to plan ahead
[08:33] <didrocks> the unfreeze but will be on thursday at the earliest :)
[08:33] <didrocks> Saviq: yeah, do you need help to prepare that?
[08:33] <Saviq> that's fine, then a MR will be awaiting that
[08:33] <Saviq> didrocks, just wanted to know how would you approach taht
[08:33] <Saviq> a simple Replaces: entry in debian/control?
[08:33] <Saviq> and a version Req in gnome-session?
[08:33] <didrocks> Saviq: we need 2 transitional packages
[08:34] <didrocks> then, I'll hanle gnome-session
[08:34] <didrocks> handle*
[08:34] <didrocks> (if needed, didn't check)
[08:34] <Saviq> yes, we need to modify ubuntu-2d.session to require unity-2d-shell instead of unity-2d-launcher and -places
[08:35] <Saviq> didrocks, anywhere in particular I can read about preparing those transitional packages?
[08:36] <didrocks> ah the binary, yes
[08:36] <didrocks> Saviq: http://wiki.debian.org/Renaming_a_Package
[08:36] <Saviq> didrocks, ok great, I'll have that as part of the merge, thanks
[08:37] <didrocks> Saviq: subscribe me to it :)
[08:37] <Saviq> didrocks, will do
[08:55] <Saviq> didrocks, does this diff look sane http://pastebin.ubuntu.com/822323/ ?
[08:55] <Saviq> hey greyback
[08:55] <greyback> Saviq: Good morning
[08:58] <dyams> greyback: morning
[08:58] <Saviq> greyback, how's the temperature in Prague?
[08:58] <Saviq> hey dyams
[08:58] <greyback> dyams: hey
[08:58] <dyams> saviq: hey
[08:58] <tsdgeos> Saviq: it's cold even here :D 3º
[08:59] <Saviq> tsdgeos, lol
[08:59] <Saviq> tsdgeos, -10 here
[08:59] <tsdgeos> well has 15º on thursday ;-)
[08:59] <didrocks> Saviq: the diff looks sane, some comments:
[08:59] <didrocks> - section for transitional packages should be oldlib
[09:00] <didrocks> - remove the description for them and add "this is a transitional…"
[09:00] <didrocks> Saviq: look at the netbook-launcher package as an example
[09:00] <greyback> Saviq: my thermometer says -4, but it's gonna get colder during the week
[09:00] <Saviq> didrocks, ok
[09:01] <Saviq> lol AccuWeather says "sunny" for today, "sunny/cloudy" for tomorrow...
[09:01] <Saviq> and then it's "bloody cold" for the remainder of the week :D
[09:02] <Saviq> probably straight translation from "freezing"
[09:02] <greyback> :)
[09:02]  * greyback wants to go back to bed, only got 4 hours sleep :(
[09:03] <Saviq> but in the sense of "damn, it's freezing in here", not in "the water is freezing here"
[09:03] <Saviq> greyback, had fun yesterday?
[09:04] <greyback> Saviq: I had a really nice day, sat in a cafe with book, met friends for dinner, couple of beers, but nothing crazy
[09:05] <greyback> Just one of those nights when my brain refuses to turn off
[09:05] <Saviq> greyback, ah that one
[09:05] <greyback> which means today I'll have a constant headache :(
[09:05] <greyback> stupid brain
[09:18] <tsdgeos> nerochiaro: have a sec to talk about the getshape stuff?
[09:18] <tsdgeos> s/talk/write :D
[09:18] <nerochiaro> tsdgeos: sure
[09:18] <tsdgeos> nerochiaro: i have to create new tests for shaping when we are in rtl mode
[09:19] <tsdgeos> and i've been thinking it'd be easier if the getshape code returned the whole screen
[09:19] <tsdgeos> instead of only the "region" there's stuff on
[09:21] <tsdgeos> because at the moment, the image returned by getshape of the launcher in rtl and non rtl is just the same, a vertical stripe of black, but i think it'd make sense that there is white on the left/right of that stripe depening if you are in rtl or not
[09:21] <nerochiaro> tsdgeos: unfortunately the getshape uses x11 functions that can return only the shaped region
[09:21] <tsdgeos> not sure if i'm explaining myself/making any sense
[09:21] <nerochiaro> it makes sense
[09:21] <nerochiaro> what you can do is
[09:21] <tsdgeos> sure, but i can do QDesktopWidget.width
[09:21] <tsdgeos> or something like that
[09:21] <nerochiaro> yes, probably easy to do it in ruby using IM
[09:22] <tsdgeos> fill that with white and then what XShapeGetRectangles returns in black
[09:22] <tsdgeos> IM=
[09:22] <tsdgeos> IM?
[09:22] <nerochiaro> imagemagick
[09:22] <tsdgeos> ah
[09:22] <nerochiaro> that's what i use to generate the verification images for most tests
[09:22] <nerochiaro> you will find code in the shape tests that do pretty much what you need to do
[09:23] <nerochiaro> just it does it to the verification images, not to the image returned by getshape
[09:23] <nerochiaro> but the idea is the same
[09:23] <Saviq> tsdgeos, nerochiaro yeah it makes sense for getshape to only return the shape of the window
[09:23] <Saviq> and then paint that on top of a workspace-sized white background
[09:23] <nerochiaro> i have no problem with that, it's just harder to do from QT
[09:23] <tsdgeos> Saviq: but then you don't know where it's located
[09:23] <tsdgeos> that is the important part
[09:23] <Saviq> tsdgeos, it's x and y will be the window's x and y, no?
[09:23] <Saviq> -'
[09:24] <tsdgeos> yeah
[09:24] <nerochiaro> ok, let me clarify something first
[09:24] <tsdgeos> i just find it much easier to do in the cpp Qt code that hacking it on top in ruby with IM
[09:24] <tsdgeos> it's like 1 line of .cpp code
[09:24] <nerochiaro> tsdgeos: if the window shape has only a launcher on the right side, what do you get out of getshape ?
[09:24] <nerochiaro> i mean, right now
[09:24] <tsdgeos> it's wrong
[09:25] <tsdgeos> white rectangle
[09:25] <tsdgeos> because tries to paint a painter path on the right
[09:25] <tsdgeos> and the bitmap is not wide enough
[09:25] <tsdgeos> since you create the bitmap with width/height
[09:25] <tsdgeos> but that does not account for the painterpath not starting at 0
[09:25] <nerochiaro> ah, i see. ok then if you know how to fix that, and you're ok fixing all the existing tests too, i'm ok with it
[09:26] <tsdgeos> now we only need to convince Saviq ;-)
[09:26] <Saviq> tsdgeos, rename the tool, then
[09:26] <nerochiaro> i just did it the way i did it because it was simpler, but returning from getshape the full shape of the window isn't wrong
[09:26] <nerochiaro> Saviq: why ? it does still get the shape
[09:26] <Saviq> tsdgeos, or ignore me completely
[09:26] <nerochiaro> Saviq: the shape and the position
[09:26] <tsdgeos> Saviq: well, it returns you the shape, black on white
[09:27] <nerochiaro> getshape sounds better than getpositionedshape ;)
[09:27] <Saviq> tsdgeos, ok, go for it
[09:27] <nerochiaro> just make sure you fix the existing tests. they will choke on it currently
[09:27] <tsdgeos> sure
[09:27] <Saviq> I'll make sure he does ;)
[09:32] <Saviq> didrocks, MR went your way, you'll have to check out the diff against --old=lp:unity-2d, 'cause parts of the changes went in earlier
[09:32] <Saviq> didrocks, and I'll fix the missing "Architecture: any" for unity-2d-dbg in a separate MR
[09:32] <Saviq> didrocks, thanks
[09:33] <didrocks> Saviq: ok, thanks :)
[09:33] <didrocks> Saviq: anyway, not before next thursday
[09:34] <dyams> JohnLea: ping
[09:36] <dyams> JohnLea: https://bugs.launchpad.net/unity-2d/+bug/855532 - Keyboard shortcuts displayed in overlay hint are only the ones mentioned in the gdoc. no?
[09:36] <ubot5`> Launchpad bug 855532 in unity-2d (Ubuntu) "Keyboard shortcut - Add keyboard shortcut hint overlay that is displayed when a user presses and holds the Super key" [High,Confirmed]
[09:36] <JohnLea> dyams; yes, the keyboard shortcuts displayed in the overlay hint should exactly match those in the google doc
[09:37] <dyams> JohnLea: Ok, but there are few configurable keys too
[09:38] <greyback> JohnLea: hey, can you point me to most recent mockups of the HUD please?
[09:38] <Saviq> didrocks, that MR is going into unity-2d-shell, not lp:unity-2d
[09:39] <Saviq> didrocks, so you can approve before then if/when you have time
[09:39] <didrocks> Saviq: ah ok, I'll review when I get the time to do so :)
[09:39] <didrocks> not right now, handling the unity release
[09:39] <JohnLea> dyams; yes, if the user updates their shortcut configurations this should be reflected in the overlay hint.  But by default the shortcuts should be the same as in the doc
[09:39] <Saviq> and the whole thing will get into lp:unity-2d later
[09:39] <Saviq> didrocks, sure, no pressure
[09:40] <Saviq> didrocks, thanks again
[09:40] <didrocks> yw ;)
[09:40] <JohnLea> greyback; see https://chinstrap.canonical.com/~sabdfl/12_04/desktop_and_netbook/matrix/
[09:41] <greyback> JohnLea: blast, I missed that directory on my search. Thanks
[09:47] <didrocks> greyback: hey, you didn't get any work done yet on multimonitor support, isn't it?
[09:48] <greyback> didrocks: it's in progress, but nothing is in yet
[09:48] <didrocks> greyback: ok, thanks for confirming :)
[09:52] <Saviq> nerochiaro, sorry to be bothering you, but did we drop the new assets for panel buttons for now?
[09:53] <Saviq> I remember you writing something to me on friday, but the details slipped my mind
[09:53] <nerochiaro> Saviq: no we didn't, there's a sepate MR for them
[09:53] <Saviq> nerochiaro, oh ok
[09:53] <nerochiaro> Saviq: there's one MR for making hte buttons work in -shell, and one for adding the new assets, also in -shell
[09:53] <Saviq> nerochiaro, ok thanks
[09:53] <nerochiaro> Saviq: you're welcome
[09:54] <Saviq> nerochiaro, can you point me to the one with the new assets?
[09:55] <nerochiaro> Saviq: https://code.launchpad.net/~unity-2d-team/unity-2d/unity-2d-shell-panel-newbuttons/+merge/90458
[09:55] <Saviq> I wonder why it doesn't show in unity-2d active reviews...
[09:55] <nerochiaro> it shows in mine
[09:56] <Saviq> hrmpf
[09:56] <Saviq> now it's here..
[09:56] <Saviq> some caching issues, probably
[09:56] <nerochiaro> Saviq: i think it's because gerry claimed it ?
[09:56] <Saviq> nerochiaro, thanks again
[09:56] <nerochiaro> anytime
[09:58] <Saviq> nerochiaro, as I understand it we need to take over any fixes to those from you?
[09:59] <nerochiaro> Saviq: well, i can help out if needed
[09:59] <Saviq> nerochiaro, I assume you have enough on your plate
[10:00] <Saviq> nerochiaro, we'll manage
[10:00] <nerochiaro> Saviq: i do. they're pretty simple MRs anyways, so fixing should be simple
[10:00] <Saviq> yup
[10:00] <nerochiaro> Saviq: but feel free to poke me anytime if you guys have questions
[10:00] <nerochiaro> it's not like i'm disappearing in a black hole
[10:00] <nerochiaro> ;)
[10:00] <Saviq> ;)
[10:28] <Saviq> nerochiaro, can you just answer https://code.launchpad.net/~unity-2d-team/unity-2d/unity-2d-shell-panel-dash-buttons/+merge/90450/comments/195402 ?
[10:30] <nerochiaro> Saviq: done
[10:31] <Saviq> thanks
[10:36] <Saviq> tsdgeos, just so you know, we have two MRs from Ugo that we need to take over fix-wise, and since I've been reviewing them... you're it!
[10:37] <tsdgeos> ok
[10:37] <tsdgeos> Saviq: urls?
[10:37] <Saviq> tsdgeos, https://code.launchpad.net/~unity-2d-team/unity-2d/unity-2d-shell-panel-newbuttons/+merge/90458 https://code.launchpad.net/~unity-2d-team/unity-2d/unity-2d-shell-panel-dash-buttons/+merge/90450
[10:38] <Saviq> tsdgeos, but focus on what you're doing now, nothing of huge prio there
[10:58] <Saviq> greyback, standup?
[10:58] <greyback> Saviq: yarp
[11:05] <dyams> nerochiaro: ping
[11:05] <nerochiaro> dyams: yes ?
[11:06] <dyams> nerochiaro: multi monitor stuff with shell, shall we discuss it
[11:06] <nerochiaro> dyams: yes, but we need Kaleo too. he was doing the tests for performance on the multimonitor stuff
[11:06] <dyams> nerochiaro: ok
[11:07] <dyams> kaleo: ping
[11:07] <nerochiaro> dyams: and i don't know what results he got. and without the results we can't say if the solution we tried is good or not
[11:07] <dyams> nerochiaro: ah
[11:09] <dyams> nerochiaro: is it not a lot of work to bypass QDeclarativeView & depend on QGraphicsView directly?
[11:11] <Kaleo> nerochiaro: still not done the performance testing
[11:13] <nerochiaro> dyams: it turned out easier than expected
[11:19] <dyams> nerochiaro: ah..nice
[11:27] <greyback> Saviq|afk: when you get back, I'm guessing were maintaining the dbus service filename as unity-2d-launcher.service because we're keeping the dbus service name com.canonical.Unity2d.Launcher ?
[11:31] <greyback> Saviq|afk: tsdgeos: tiagosh's Home Lens work: lp:~tiagosh/unity-2d/unity-2d-shell-homelens
[11:31] <greyback> depends on lp:~tiagosh/+junk/libqtdee-local-models
[12:30] <Saviq> greyback, tsdgeos: how can I count() the amount of objects returned by @app.Whatever()?
[12:38] <greyback> Saviq: it returns an array, so can just use 'count'
[12:39] <Saviq> greyback, .count?
[12:39] <greyback> yeah
[12:39] <Saviq> greyback, another thing - can I check for an object that doesn't have attribute x?
[12:40] <greyback> Saviq: you can try checking for it, and use it in verify_not. The check will fail & throw an exception, which verify_not catches
[12:40] <Saviq> greyback, let me rephrase - I want to find the first item in the launcher that is _not_ BFB
[12:40] <Saviq> so it won't have the isBfb attr
[12:41] <greyback> Saviq: sure, lemme see..
[12:41] <Saviq> and also... "@app.LauncherContextualMenu().QAction().count" yields "MobyBase::MultipleTestObjectsIdentifiedError: Multiple test objects found with rule: {:type=>"QAction"}"
[12:42] <dyams> saviq: no object name is assigned to QActions
[12:43] <Saviq> dyams, I don't care
[12:43] <Saviq> at least not in the tests I'm doing
[12:43] <dyams> saviq: QActions in context menu, i mean
[12:43] <dyams> "@app.LauncherContextualMenu()..childrenCount?
[12:44] <dyams> "@app.LauncherContextualMenu()['children'] ?
[12:44] <dyams> saviq: ^^
[12:46] <greyback> Saviq: https://pastebin.canonical.com/59031/
[12:47] <Saviq> greyback, ok thanks
[12:47] <greyback> Saviq: see the "Launcher hide delay on tile removal" test
[12:47] <Saviq> greyback, yup
[12:53] <Saviq> greyback, hmm, is the "if tiles.empty?" necessary there? shouldn't the verify() handle the case when there is nothing found?
[12:53] <greyback> Saviq: true dat
[12:54] <Saviq> greyback, okies
[13:12] <mhall119> didrocks: ping
[13:13] <didrocks> mhall119: yeah
[13:13] <mhall119> hey, I got singlet upgraded to support unity 5 over the weekend
[13:13] <mhall119> and have a package in the scopes-packagers PPA
[13:13] <didrocks> mhall119: yeah, I saw that, awesome! :)
[13:13] <mhall119> any chance you can look at it today and see if it's ready to go to REVU?
[13:14] <didrocks> mhall119: not really, trying to get unity 5.2 out
[13:14] <didrocks> mhall119: and I have no acceleration, which is an issue
[13:14] <didrocks> (nvidia)
[13:14] <mhall119> :(
[13:14] <mhall119> I don't suppose you've had a chance to start a quickly template for it have you?
[13:15] <didrocks> mhall119: not really as well, it will be really hard this week :/
[13:15] <didrocks> mhall119: will try as soon as possible
[13:16] <mhall119> who else could help me?
[13:16] <mhall119> mterry?
[13:17] <mterry> mhall119, quickly template for scopes?
[13:19] <didrocks> mhall119: I can though use some unity testing help btw :)
[13:19] <didrocks> hey mterry
[13:19] <mterry> didrocks, hi!
[13:23] <mhall119> didrocks: tell me what to test
[13:24] <didrocks> mhall119: can you update from ppa:unity-team/staging
[13:24] <didrocks> mhall119: and tell me if it generally works :)
[13:26] <mhall119> hmmm.....this is going to make me less productive today....isn't it?
[13:27] <kamstrup> any unity-2d guy looking at https://bugs.launchpad.net/unity-2d/+bug/761851 ?
[13:27] <ubot5`> Launchpad bug 761851 in software-center (Ubuntu) "Software Centre - automatically add app icon to launcher" [Medium,In progress]
[13:28] <didrocks> mhall119: well, this will help getting a new unity earlier and spot issues
[13:28] <didrocks> mhall119: jorge did that normally, not sure if you are supposed to do it
[13:28] <mhall119> didrocks: dist-upgrading now
[13:28] <didrocks> thanks :)
[13:28] <mhall119> if I suddenly get real quiet, things have gone horribly wrong
[13:29]  * mhall119 feels so dangerous running from the staging ppa
[13:30] <mhall119> didrocks: you guys didn't change the lens api again with this release did you?
[13:30] <Saviq> tsdgeos, aren't you doing "Port input_shaping..." as part of your RTL test work?
[13:31] <didrocks> mhall119: I'm not the one changing it :)
[13:31] <didrocks> mhr3: kamstrup ^^
[13:31] <mhall119> Unpacking replacement python-dbus ...
[13:31] <mhall119> Selecting previously unselected package python-dbus-dev.
[13:31] <mhall119> Unpacking python-dbus-dev (from .../python-dbus-dev_1.0.0-1ubuntu1_all.deb) ...
[13:31] <mhall119> (Reading database ... 399051 files and directories currently installed.)
[13:31] <mhall119> Removing ubuntu-desktop ...
[13:31] <mhall119> Removing unity ...
[13:31] <mhall119> Processing triggers for man-db ...
[13:31] <mhall119> is that right?
[13:31] <mhr3> mhall119, why would we do such nasty things to you? :)
[13:32] <mhall119> mhr3: because I keep asking for things like categories over dbus
[13:33] <mhr3> mhall119, we can't didrocks would kill us for breaking the api then :P
[13:33] <didrocks> mhr3: hum removing unity, doesn't seem right
[13:33] <didrocks> mhall119: ^
[13:33] <kamstrup> right, libunity is not just frozen, it has entered permafrost ;-)
[13:34] <didrocks> mhall119: try install it to see what's happening
[13:37] <mhall119> mterry: sorry, missed your reply earlier
[13:38] <mhall119> mterry: yes, quickly template for lenses/scopes, using Singlet
[13:38] <mterry> mhall119, I don't have any time right now to help create that, but I could provide pointers?
[13:39] <mhall119> mterry: that would be appreciated, thanks
[13:39] <mhall119> not sure if I'll be able to do much on my own, but I'll take a look anyway
[13:39] <mterry> mhall119, do you want the help now or later, when you start working on it?
[13:40] <mhall119> mterry: if you have anything I can read later, I'll take that now
[13:40] <mhall119> I likely won't have time to work on it today
[13:41] <mterry> mhall119, I don't think we actually have any nice documentation for writing new templates.  didrocks?
[13:41] <didrocks> mterry: no, apart from my blog psot
[13:41] <didrocks> post*
[13:41] <mhall119> the only documentation I know of simply says "ask didrocks"
[13:41] <didrocks> I wanted to help mhall119 doing that, it's just that I can't this week
[13:41] <didrocks> mhall119: there is one, describing the system
[13:42] <didrocks> http://blog.didrocks.fr/post/Build-your-application-quickly-with-Quickly:-Inside-Quickly-part-1
[13:42] <didrocks> part 6
[13:42] <didrocks> "creating templates"
[13:43] <mhall119> didrocks: cool, thanks
[13:43] <didrocks> yw
[13:50] <mhall119> didrocks: well, dist-upgrade finished and nothing exploded
[13:51] <mhall119> I guess I should reboot, huh?
[13:51] <tsdgeos> Saviq: no, i'm actually not doing that, but should be easy
[13:51] <didrocks> mhall119: hum, wasn't it telling that unity was uninstalled?
[13:51] <mhall119> yeah
[13:51] <Saviq> tsdgeos, sure, and since you're dug into that anyway, will you do that please?
[13:51] <didrocks> you shouldn't reboot then :)
[13:51] <mhall119> mhall@mhall-laptop:~$ uni
[13:51] <mhall119> unicode_start           units                   unity-window-decorator
[13:51] <mhall119> unicode_stop            unity-2d-launcher       unix2dos
[13:51] <mhall119> uniconvertor            unity-2d-panel          unix2mac
[13:51] <mhall119> unify                   unity-2d-places         unix_chkpwd
[13:51] <didrocks> 14:34:00   didrocks | mhall119: try install it to see what's happening
[13:52] <mhall119> uniq                    unity-2d-spread         unix_update
[13:52] <tsdgeos> Saviq: sre
[13:52] <mhall119> unit-get                unity-greeter
[13:52] <mhall119> mhall@mhall-laptop:~$ which unity
[13:52] <mhall119> mhall@mhall-laptop:~$
[13:52] <didrocks> reinstall unity and see what it is telling you
[13:52] <mhall119> The following packages have unmet dependencies: unity : Depends: libnux-abiversion-20111214
[13:52] <mhall119> E: Unable to correct problems, you have held broken packages.
[13:52] <didrocks> mhall119: apt-cache policy unity ?
[13:53] <mhall119> http://paste.ubuntu.com/822549/
[13:53] <mhall119> conflicts with the HUD ppa?
[13:54] <didrocks> yeah
[13:54] <didrocks> apt-get install unity=5.0.0+bzr1879ubuntu0+622
[13:55] <mhall119> The following packages have unmet dependencies: unity : Depends: unity-common (= 5.0.0+bzr1879ubuntu0+622) but 5.1.0-hud2 is to be installed
[13:57] <didrocks> apt-get install unity=5.0.0+bzr1879ubuntu0+622 unity-common=5.0.0+bzr1879ubuntu0+622
[13:57] <didrocks> and so on :)
[14:00] <mhall119> didrocks: that seems to have worked
[14:00] <mhall119> does this mean I'll be losing the HUD?
[14:00] <didrocks> mhall119: yeah
[14:00] <didrocks> it's not in the 5.2 release
[14:00] <mhall119> I'd be sad, but honestly I didn't use it much
[14:04] <gord> didrocks, we can push out a new hud ppa version later in the week right?
[14:04] <gord> based on 5.2
[14:05] <didrocks> gord: indeed
[14:06] <mhall119> \o/
[14:06] <cyphermox> dbarth: too late to fix the korean IM/ibus bug in oneiric and precise? :)
[14:06] <cyphermox> (I mean, did someone fix it yet? I have something that seems to work properly)
[14:06] <mhall119> didrocks: if the current 5.2 updates land, will it break things for people using the HUD ppa?
[14:07] <didrocks> mhall119: yeah, it won't work anymore, we will update the ppa for it
[14:08] <didrocks> mhall119: did you restart successfully?
[14:08] <mhall119> didrocks: not yet, I'll let you know when I do
[14:09] <mhall119> didrocks: by "break things" I didn't mean just that HUD stops working, I meant package dependency breakage like I had
[14:09] <didrocks> mhall119: yeah
[14:09] <didrocks> mhall119: but we don't support 2 unstable ppas
[14:09] <mhall119> still might be a good idea to send out a warning so people know, and the commands to fix it
[14:12] <didrocks> mhall119: we will in the call for testing, asking to purge the hud ppa first
[14:12] <mhall119> cool
[14:14] <tsdgeos> Saviq: ping
[14:15] <Saviq> tsdgeos, pong
[14:15] <tsdgeos> Saviq: not sure i can do the port to whole guest/target thing
[14:15] <tsdgeos> Saviq: we are using http://projects.developer.nokia.com/dav/Testabilitydriver/doc/api/qt_windows/#QtSUT:execute_shell_command  that does not seem to return the exit status of the command, which nerochiaro was using
[14:15] <Saviq> oh
[14:16] <Saviq> craps
[14:16] <Saviq> greyback, ^
[14:17] <Saviq> tsdgeos, well, we could abuse it by going `... && echo $?`
[14:17] <Saviq> not that I'd like that
[14:17] <tsdgeos> Saviq: but i don't think it'll work if it's a remote stuff
[14:17] <Saviq> tsdgeos, so yeah
[14:17] <Saviq> tsdgeos, getshape needs to print its output to stdout
[14:18] <tsdgeos> it does
[14:18] <Saviq> tsdgeos, then all the imagick comparison stuff should happen locally
[14:18] <Saviq> not remotely
[14:18] <tsdgeos> it's not getshape i'm concerned about
[14:18] <tsdgeos> why?
[14:18] <Saviq> 'cause you might not want to have imagick on the other side
[14:19] <Saviq> just run getshape remotely
[14:19] <Saviq> and the rest locally
[14:19] <tsdgeos> ok, then getshape does not outout to stdout
[14:19] <Saviq> that's what I thought
[14:19] <tsdgeos> as in what you meant as output :D
[14:19] <Saviq> it should
[14:19] <tsdgeos> it has some otuput to stdout
[14:19] <Saviq> or you can maybe grab a file from the other side?
[14:20] <Saviq> but I'd rather it just have an output file of "-" that will feed the image data to stdout
[14:20] <Saviq> and you can then deal with it locally
[14:21] <tsdgeos> ok, i can do that
[14:21] <tsdgeos> just pushed the rtl stuff
[14:21] <tsdgeos> it is working
[14:21] <tsdgeos> but
[14:22] <tsdgeos> i have a off by one somewhere
[14:22] <tsdgeos> because if you open the dash you see it overlap the launcher
[14:22] <tsdgeos> by one pixel
[14:22] <Saviq> you should be able to catch that with tdriver, no?
[14:23] <Saviq> _visualizer, that is
[14:23] <tsdgeos> catch what?
[14:23] <tsdgeos> i can see it :D
[14:24] <tsdgeos> or you mean check the x, y values tehre?
[14:25] <Saviq> tsdgeos, I mean you can catch where the problem is
[14:25] <Saviq> greyback, so... my "The application with Id 2102 is no longer available..." errors seem to be spread-related
[14:26] <Saviq> doesn't $SUT.run require the app to become visible within the timeout provided?
[14:29] <burli> If I want to develop Apps for Tablet and Smartphone, what is the recommended Language and Toolkit?
[14:31] <burli> I mean for Ubuntu Tablets
[14:32] <Saviq> burli, there is a Ubuntu Tablet out there? where?
[14:32] <mhall119> burli: any of the languages and toolkits supported by Ubuntu will, in all likelyhood, be supported by Ubuntu on tablets and phones when they come out
[14:33] <burli> Saviq, not yet. But for the future
[14:33] <mhall119> it's hard to give definitive answers, since we just plain don't know yet
[14:33] <burli> mhall119, so I can use Python and Qt/QML
[14:33] <Saviq> burli, no idea then, nothing was decided about that, AFAIK
[14:33] <mhall119> burli: most likely, yes
[14:34] <burli> and what I have to do if the app should appear in the software center?
[14:34] <mhall119> though having a bunch of python apps on a phone's hardware may not be the best user experience
[14:34] <mhall119> burli: you'll need to submit it
[14:34] <greyback> Saviq: I didn't think it had anything to do with visibility. Does /logs/testability/qttasserver.log have anything that looks relevant?
[14:34] <greyback> Saviq: can you point me to tests which fail this way, so I can have a look?
[14:35] <mhall119> burli: http://developer.ubuntu.com/ has all the information about building apps for Ubuntu and getting them into Software Center
[14:35] <burli> mhall119, thx
[14:35] <mhall119> burli: we'll also be holding a 3-day developer workshop in #ubuntu-classroom starting tomorrow
[14:35] <burli> ah, ok.
[14:35] <mhall119> burli: https://wiki.ubuntu.com/UbuntuDeveloperWeek
[14:35] <mhall119> you should attend some of the sessions if you can
[14:35] <burli> I try
[14:36] <burli> mhall119, which language and toolkit would YOU use or recommend for Smartphones and Tablets?
[14:37] <mhall119> well, I'm a Python dev, so that's usually my go-to language
[14:37] <mhall119> but an interpreted language on limited hardware may not work as well as on desktops
[14:37] <mhall119> so probably Vala, if not C/C++
[14:38] <burli> hm, I have no Vala experience and I don't like GTK
[14:38] <mhall119> QT/QML will very likely be available
[14:38] <burli> for Vala?
[14:38] <burli> Great
[14:39] <mhall119> Vala is a lot like Java and C#, but it get's compiled down to a native binary
[14:39] <burli> yes, afaik it's compiled to C.
[14:40] <burli> I guess, I'll take a look
[14:46] <burli> mhall119, do you have some reference for Vala and Qt?
[14:48] <mhall119> burli: I don't, sorry
[14:49] <mhall119> like I said, I'm a python dev
[14:50] <Saviq> greyback, places-tests
[14:50] <Saviq> greyback, the output is:
[14:50] <greyback> Saviq: ok, will check them out
[14:54] <Saviq> greyback, here's some logs http://pastebin.ubuntu.com/822621/
[14:56] <mhall119> can I get a couple of you guys to review and upload my unity-singlet package to the precis universe? https://launchpad.net/~scopes-packagers/+archive/ppa/+sourcepub/2207463/+listing-archive-extra
[14:56] <mhall119> didrocks: ^^
[14:56] <greyback> Saviq: well I can reproduce anyway, but still digging as to why
[14:57] <didrocks> mhall119: again, I really can't doing that before unity is released as I told you last week, is there in emergency?
[14:57] <didrocks> any*
[14:57] <mhall119> didrocks: no, just wanted to keep the ball rolling
[14:58] <tsdgeos> Saviq: greyback: i'm ultra confused, i have http://paste.kde.org/~tsdgeos/196532/ and out contains nothing, any idea why?
[14:58] <didrocks> mhall119: please, be patient :)
[14:58] <mhall119> :)
[14:58] <Saviq> tsdgeos, oh, that's bad
[14:58] <tsdgeos> wait
[14:58] <tsdgeos> probably the command is not even being executed
[14:59] <tsdgeos> i changed getshape to lalsaaslfsa
[14:59] <tsdgeos> and nothing complained
[14:59] <Saviq> tsdgeos, yeah, ruby seems to do that to me, too
[15:00]  * Saviq is going to check out / verify multimonitor support in shell, expect me being away for some time
[15:02] <greyback> Saviq: testability not happy with spread for some reason, it is executing it, but fails to connect somehow
[15:02] <greyback> Saviq: https://pastebin.canonical.com/59043/
[15:03] <greyback> Saviq: since that test doesn't need to inspect the application, can just run spread with $SUT.execute_shell_command as a workaround until I can delve more
[15:03] <Saviq> greyback, I worked it around fine, just wanted to let you know that happens
[15:04] <greyback> Saviq: thanks. Yeah I'm confused about that
[15:04] <greyback> tsdgeos: look at /logs/testability/qttasserver.log, it might have a clue
[15:04] <tsdgeos> greyback: well i guess some "i don't know ruby at all" mistake
[15:04] <tsdgeos> shuffled variables around and it works now
[15:04] <tsdgeos> D:
[15:05] <greyback> tsdgeos: execute_shell_command is very dodgy. Don't use > < or &
[15:05] <greyback> tsdgeos: is bug, the string needs to be xml-escaped
[15:06] <greyback> the log help you figure out what string the server is actually executing
[15:06] <greyback> note also commands run in a QProcess
[15:06] <dbarth> cyphermox: i haven't had contacts with bschaefer on that bug for a while
[15:06] <cyphermox> dbarth: ok, I was looking into it, but I've been testing my "fix" more this morning and it fails for some languages, so it's no good
[15:07] <dbarth> cyphermox: can you ask him and also ping thumper about to make sure it pops on htheir radar for 5.4
[15:07] <cyphermox> sure. when do they usually come online?
[15:07] <dbarth> cyphermox: have you also checked how the network indicator refreshes the network list with dbusmenu? did you get rid of the "flashing"?
[15:08] <cyphermox> dbarth: next on my list. I was technically on +1 maint this month
[15:09] <cyphermox> dbarth: got a good idea on how to fix it, just didn't finish implementing the fix yet
[15:10] <cyphermox> (also, tbh, the flashing happens because dbusmenu can't handle the menu changing, this was working just fine for however many years we've had nm-applet implemented with a GtkStatusIcon)
[15:10] <cyphermox> but I'll work around that by updating the menu differently
[15:14] <mhall119> okay, here goes the reboot into Unity 5.2...
[15:40] <mhall119> didrocks: so 5.2 isn't working so well for me
[15:41] <didrocks> mhall119: what doesn't work?
[15:41] <mhall119> unity
[15:41] <mhall119> seems to be crashing
[15:42] <didrocks> can you get a traceback, please?
[15:46] <mhall119> didrocks: where would I get that?
[15:47] <didrocks> mhall119: run compiz under gdb, but you need to rebuild with debug symbol. I'm sure an unity dev can help you there ^
[15:47] <seb128> mhall119, can you pastebin your .xsession-errors?
[15:48] <mhall119> http://paste.ubuntu.com/822691/
[15:48] <mhall119> seb128: ^^
[15:48] <seb128> compiz: symbol lookup error: /usr/lib/compiz/libunityshell.so: undefined symbol: _ZN5unity4dash8HomeLensC1ERKSsS3_S3_
[15:48] <seb128> it's the same issue I had
[15:48] <seb128> mhall119, update libunity-core
[15:48] <didrocks> missing libunitycore
[15:48] <seb128> didrocks, libunity-core-5.0-5
[15:48] <seb128> didrocks, see, I'm not alone running into it :p
[15:49] <seb128> ups
[15:49] <seb128> mhall119, libunity-core-5.0-5
[15:49] <mhall119> seb128: apt said I already have it
[15:49] <seb128> mhall119, dpkg -l | grep libunity-core-5.0-5
[15:49] <seb128> mhall119, ldd /usr/lib/compiz/libunityshell.so | grep libunity
[15:50] <didrocks> seb128: well, don't ask for miracle from autogenerated packages :)
[15:50] <mhall119> mhall@mhall-laptop:~$ ldd /usr/lib/compiz/libunityshell.so | grep libunity libunity-misc.so.4 => /usr/lib/libunity-misc.so.4 (0xb65c8000) libunity-core-5.0.so.5 => /usr/lib/libunity-core-5.0.so.5 (0xb6485000)
[15:51] <seb128> mhr3, what about the dpkg -l ?
[15:51] <mhr3> mhall119, ^^
[15:51] <mhall119> one second, doing this all from byobu
[15:51] <seb128> mhr3, sorry
[15:52] <mhall119> ii  libunity-core-5.0-5                           5.1.0-hud2                                 Core library for the Unity interface.
[15:52] <mhall119> mha
[15:52] <mhall119> dbarth: I may be late to our call
[15:52] <seb128> doh
[15:52] <mhall119> didrocks: seb128: what's the fastest way for me to get a working unity again?
[15:53] <mhall119> oh, is this hud stuff again?
[15:53] <seb128> mhall119, sudo apt-get install libunity-core-5.0-5=5.0.0+bzr1880ubuntu0+623
[15:53] <didrocks> mhall119: indeed, do what seb128 told ^
[15:53] <seb128> yes
[15:53] <didrocks> and probably
[15:53] <seb128> the hud version is newer than the 5.2 candidate one
[15:53] <didrocks> unity-services
[15:53] <seb128> mhall119, or ppa-purge the hud
[15:55] <mhall119> what's the command to purge the hud ppa?
[15:57] <seb128> mhall119, ppa-purge?
[15:59] <mhall119> yay! got a working Unity again
[15:59] <mhall119> I don't have a ppa-purge
[15:59] <mhall119> just moved the files from sources.list.d
[16:03] <dbarth> mhall119: my other call is running out of schedule as well
[16:04] <mhall119> dbarth: they got me all fixed up now, so I'm ready anytime you are
[16:04] <mhall119> didrocks: seb128: thanks for the help\
[16:04] <didrocks> yw :)
[16:04] <mhall119> didrocks: was this the testing you wanted, or do you need me to do something now that my hud-dependency-hell is resolved?
[16:05] <didrocks> mhall119: just testing and telling me if you discover new issues
[16:05] <didrocks> mhall119: we will surely have one additional commit going
[16:05] <didrocks> if everything is fine then, this will become 5.2
[16:05] <mhall119> didrocks: ok, will do
[16:05] <mhall119> any fun new toys for me to play with in 5.2?
[16:07] <dbarth> mhall119: ping
[16:12] <Saviq> I hate wifis...
 tsdgeos, you will probably know - how can I update the screen number as returned from QX11Info::appScreen()?
 tsdgeos, regardless of the fact that I actually move the window to the left/topmost screen
 which is, for example, screen 1 when default screen is not the left/topmost
 QX11Info::appScreen() returns 0, which breaks some stuff
 I wonder if that's related to the window being a dock :/
 nope, doesn't look like it
 Kaleo, greyback, maybe you guys will know ^ ?
[16:14] <tsdgeos> Saviq: you mean appScreen always returns the same wheter screen the window is in?
[16:14] <Saviq> tsdgeos, yes
[16:15] <Saviq> tsdgeos, QDesktopWidget::screenNumber(QPoint(0,0)) returns 1
[16:15] <Saviq> so I move the window to availableGeometry(1).topLeft()
[16:15] <Saviq> but appScreen still returns 0
[16:15] <Saviq> :/
[16:15] <tsdgeos> yeah well, i would not trust appScreen much
[16:15] <tsdgeos> there's some methods that actually accpet a window
[16:15] <tsdgeos> those seem safer
[16:16] <Saviq> oh that's a good idea
[16:16] <tsdgeos> QDesktopWidget::screenNumber()
[16:17] <Saviq> tsdgeos, and how do I get current app's root widget again?\
[16:17] <tsdgeos> you can't
[16:17] <tsdgeos> there's no a "root widget" per se
[16:18] <Saviq> tsdgeos, please take a look at screeninfo.cpp:93
[16:18] <Saviq> tsdgeos, what would you do there?
[16:18] <Saviq> instead of appScreen()?
[16:20] <tsdgeos> Saviq: make ScreenInfo have a QWidget mebmer so you could ask use QDesktopWidget::screenNumber :D
[16:20] <tsdgeos> i mean we use ScreenInfo always associated to a widget, no?
[16:20] <Saviq> tsdgeos, it's a singleton
[16:20] <Saviq> it could be associated to a the QDeclarativeView of current app
[16:20] <tsdgeos> well
[16:20] <Saviq> - a
[16:21] <Saviq> why would they expose an appScreen method that's broken like that :[
[16:21] <tsdgeos> i see
[16:21] <Saviq> nasty
[16:21] <tsdgeos> Saviq: well, it's broken by design
[16:21] <tsdgeos> i mean
[16:21] <tsdgeos> your app can have N windows
[16:21] <tsdgeos> in X screens
[16:22] <tsdgeos> so what would appScreen return?
[16:22] <Saviq> true
[16:22] <tsdgeos> Saviq: sincerely i don't think that having a ScreenInfo::geometry() that belongs to a singleton makes sense
[16:22] <tsdgeos> either it should stop being a singleton
[16:22] <Saviq> tsdgeos, it will
[16:23] <tsdgeos> or it should a screen parameter
[16:23] <Saviq> I will move it to QML and add a property with current QDeclarativeView
[16:23] <Saviq> makes total sense what you're saying
[16:24] <tsdgeos> that should fix all our problems
[16:24] <tsdgeos> hopefully
[16:24] <tsdgeos> otoh
[16:25] <tsdgeos> a widget can in theory also be in two screens
[16:25] <tsdgeos> but not in our use case i guess
[16:25] <Andy80> Kaleo: ping
[16:25] <Saviq> I need to resync with Kaleo and dyams about MM for that, too
[16:26] <Saviq> tsdgeos, so the other thing - with providing a screen number - might be a better - more deterministic approach
[16:27] <Saviq> esp. when we will have multiple launchers and stuff - each of them will request a geometry of their own screen
[16:27] <Saviq> ok, my head is killing me, time to EOD for today
[16:27] <Saviq> cheers all, see you tomorrow
[16:28] <greyback> Saviq: take it easy
[17:01] <mhall119> didrocks: so far it's been smooth sailing
[17:01] <mhall119> I'm liking the new Dash home
[17:01] <mhall119> but what will be on there after a fresh install?
[17:01] <didrocks> mhall119: nothing, per default, until you open a file/app
[17:02] <didrocks> mhall119: so yeah, will look weird, I agree :)
[17:02] <didrocks> glad you like it!
[17:02] <mhall119> maybe it can have the Examples documents, or an introductory slideshow or video
[17:03] <didrocks> yeah, can be a good idea :)
[17:03] <didrocks> mhall119: raise that on the ayatana (for design) mailing list
[17:08]  * mhall119 makes a note
[19:07] <mhall119> davidcalle: I sent you an invite to a google doc, could you fill in whether your lenses and scopes work on oneiric and/or precise, and which are ready for the ARB (including ones already sent)
[19:09] <davidcalle> mhall119, sure
[19:09] <mhall119> thanks
[19:12] <davidcalle> mhall119, do you want me to differentiate experimental branches (likes scopes without a lens) from the really working ones?
[19:13] <mhall119> davidcalle: do I have experimental ones on there?
[19:13] <davidcalle> mhall119, yeah, like desura, scummvm, 9gag. They "work", but don't have a lens to host them.
[19:14] <mhall119> davidcalle: ah, for those let's put something like "needed" in the 2nd column (the one labeled "lens")
[19:14] <davidcalle> mhall119, ok
[19:25] <davidcalle> mhall119, do you mind if I remove the branches that have been dropped or merged, or are irrelevant from a user pov?
[19:26] <mhall119> davidcalle: if it's not available on either oneiric or precise, yes
[19:26] <mhall119> if it's still available on oneiric, but dropped from precise, go ahead and leave it
[19:27] <davidcalle> mhall119, by not available, you mean not packaged?
[19:27] <mhall119> no, I mean not working
[19:28] <mhall119> if it works I want to keep it in the list, just mark it as not being ready for the ARB
[19:31] <davidcalle> mhall119, ok
[19:33] <JonOomph> Hi!  There is a bug with Unity where clicking on a GtkRecentChooserMenu always selects the first entry (lp:752674).  It only happens with Unity.  Gnome Shell and Gnome classic work fine.  The bug was marked as "Invalid", but I can confirm the bug still exists in 12.04 (daily build) and 11.10.  Any thoughts or suggestions?
[19:35] <davidcalle> mhall119, done.
[19:36] <davidcalle> mhall119, I will add the screenshots I find.
[19:38] <mhall119> awesome, thanks
[19:40] <thumper> morning
[19:40] <mhall119> morning thumper
[23:56] <bschaefer> thumper, ping. Have a question about a merge