[08:18] <dholbach> hey
[08:18] <seb128> hey dholbach
[08:19] <dholbach> could it be that alt-drag was disabled somehow?
[08:19] <seb128> hum
[08:19] <seb128> yeah, seems to not work for me as well
[08:20] <seb128> sil2100, Mirv: ^ is that known? alt-leftclick-dnd not moving dialogs anymore with the compiz-gsettings update?
[08:36] <sil2100> seb128, dholbach: yes, I also noticed it doesn't work - but maybe just the move plugin got disabled?
[08:36] <sil2100> I'm using still the old versions of packages, so my ccsm crashes
[08:36]  * sil2100 has to update
[08:37] <dholbach> is there no way to do it without ccsm? :)
[08:37] <seb128> dholbach, according to ccsm it's binded to super-leftclick
[08:38] <dholbach> ugh :(
[08:38] <sil2100> huh, indeed
[08:38] <seb128> that "works" but it triggers the unity-help if you let super pressed which makes it really slow
[08:38] <sil2100> Why did it change?
[08:38] <dholbach> yes
[08:38] <seb128> dholbach, can you open a bug against compiz?
[08:38] <dholbach> sure
[08:38] <seb128> danke
[08:39] <seb128> weird
[08:39] <seb128>   <schema id="org.compiz.move" gettext-domain="compiz">
[08:39] <seb128>     <key type="s" name="initiate-button">
[08:39] <seb128>       <default>'&lt;Alt&gt;Button1'</default>
[08:39] <seb128>  
[08:39] <seb128> in the schemas
[08:41] <sil2100> hm, indeed strange
[08:43] <dholbach> seb128, https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1041105
[08:45] <davidcalle> sil2100, your videos lens release is missing quite some files in the package :/
[08:47] <sil2100> davidcalle: huh? It is? I did it exactly as Ken instructed...
[08:47] <sil2100> davidcalle: I did python setup.py sdist
[08:47] <davidcalle> http://bazaar.launchpad.net/~sil2100/unity-lens-videos/ubuntu_ff2/revision/87 all the removed files shouldn't be removed
[08:47] <sil2100> davidcalle: and the newly prepared distro branch was building
[08:48] <sil2100> Crap...
[08:48] <sil2100> Ok, I was in a hurry, but what did I wrong then? python setup.py sdist is not the right way?
[08:49] <davidcalle> sil2100, it's the right way, so I don't know what happened
[08:49] <sil2100> davidcalle: are those files really missing from the tarball? Or maybe bzr merge-upstream did something strange?
[08:50] <seb128> dholbach, thanks
[08:50] <seb128> sil2100, what files are missing?
[08:52] <seb128> sil2100, dholbach: gsettings set org.gnome.desktop.wm.preferences mouse-button-modifier '<Alt>'
[08:52] <davidcalle> sil2100, trying to check if they are missing from the tarball, but Lp is super slow
[08:52] <seb128> sil2100, dholbach: sam says the GNOME integration use the mouse-button-modifier and GNOME changed that to Super
[08:52] <seb128> sil2100, dholbach: that call should fix it
[08:52] <dholbach> fixed :)
[08:52] <dholbach> you're a hero
[08:52] <davidcalle> sil2100, yes, they are missing
[08:52] <sil2100> davidcalle: I just checked, and they are missing... so what did happen during my python setup.py sdist ?
[08:52] <sil2100> Eh
[08:52] <seb128> davidcalle, sil2100: that's not a packaging mistake, I checked the packaging
[08:52] <seb128> the diff.gz has no change out of the debian dir
[08:52] <sil2100> Everything fucked up AGAIN
[08:52] <dholbach> maybe files/dirs missing in setup.py?
[08:52] <sil2100> davidcalle: can you re-do the tarball? Since obviously, my sdist just blows
[08:53] <davidcalle> sil2100, don't know, if you give me ten min, I'll roll a new tarball
[08:53] <davidcalle> Sure :)
[08:54] <sil2100> seb128: sorry about that, could have double-checked what files were removed when I was doing merge-upstream - that could have given me clues that something is wrong
[08:54] <sil2100> seb128: I just wrongly assumed  that when bzr bd doesn't fail, then everything is ok
[08:54] <seb128> sil2100, I saw the .lens dropping from the installed file but since that was in the vcs I though it was wanted
[08:58] <sil2100> davidcalle: every time I do python setup.py sdist I get the same tarball with those files not in it...
[08:59] <sil2100> davidcalle: so either something's f'd up on my system, or something wrong with the sdist rules
[08:59] <davidcalle> sil2100, are you doing it on the branch without the debian folder?
[09:00] <sil2100> davidcalle: yes, I'm doing it on lp:unity-lens-videos
[09:00] <davidcalle> sil2100, odd
[09:01] <sil2100> davidcalle: http://paste.ubuntu.com/1164069/
[09:01] <sil2100> This is the output I'm getting
[09:01] <seb128> davidcalle, src/unity-lens-video is missing for me as well if I run "python setup.py sdist"
[09:02] <seb128> unity-lens-video.service as well missing
[09:03] <seb128> and why the heck the source in ubuntu is called unity-lens-video and the sources files as well but the project is unity-lens-video*s*
[09:07] <sil2100> Yes, that's a bit confusing indeed...
[09:07] <davidcalle> seb128, old mistake from me. I'm checking the recent commits on trunk to see what happened.
[09:15] <davidcalle> sil2100, found the issue. In MANIFEST.in, should have include video.lens.in instead of video.lens
[09:15] <davidcalle> sil2100, does it work on your side?
[09:15] <Mirv> indeed that alt->super is annoying now that I noticed it
[09:16] <seb128> Mirv, you can workaround it with "gsettings set org.gnome.desktop.wm.preferences mouse-button-modifier '<Alt>'"
[09:17] <sil2100> davidcalle: so how come it was working before?
[09:17] <Mirv> seb128: ok, thanks
[09:18] <davidcalle> sil2100, 0.3.7 was not working actually, it just wasn't noticed, the upgrade wasn't removing video.lens from /usr/share/unity/lenses/video
[09:18] <seb128> Mirv, we are tracking that with https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1041105
[09:18] <davidcalle> sil2100, well, it *was* working, but by using existing files from 0.3.6
[09:18] <Mirv> seb128: yeah, I'm there :)
[09:19] <sil2100> davidcalle: ah, ok, so probably the previous tarball that Ken made was also buggy
[09:19] <davidcalle> sil2100, I've checked, it was
[09:20] <sil2100> We just didn't release it before because of the new dependency
[09:20]  * sil2100 sighs
[09:20] <sil2100> davidcalle: could you roll out the new tarball ;) ?
[09:20] <davidcalle> sil2100, yes
[09:20] <popey> sil2100, alt-tab seems fixed for me in 12.04 with your package
[09:22] <Mirv> popey: what about the alt-thekeyontheleftsideofnumber1?
[09:23] <popey> that too
[09:23] <Mirv> \o/
[09:23]  * Mirv upgrades
[09:23] <popey> still flickers
[09:23] <popey> but I am resigned to the fact that i seem to be the only person with fingers that can reproduce that
[09:27] <sil2100> popey: ;)
[09:28] <sil2100> popey: you should fill a bug against your fingers then!
[09:28] <popey> :)
[09:28] <sil2100> davidcalle: ping me when you roll out the new tarball
[09:28] <davidcalle> sil2100, for some reason, I don't have the controls in Launchpad to create a milestone and release...
[09:28] <davidcalle> That's interesting.
[09:29] <sil2100> davidcalle: huh? Ok, now this is strange - you were the one rolling out tarballs in the past, right ;p ?
[09:29] <sil2100> Since I remember poking you about that once
[09:30] <davidcalle> sil2100, oh, I suppose it's because the maintainer is now PS project management team :p
[09:31] <davidcalle> sil2100, well you can python setup.py sdist in trunk, should be fine ;) Just check if video.lens.in is in it
[09:31] <davidcalle> it = the tarball
[09:33] <sil2100> davidcalle: we need to fix those permissions anyway ;p
[09:33] <sil2100> popey: ^
[09:33] <davidcalle> popey, oh yeah, just add me to project management ;)
[09:35] <popey> :)
[09:38] <sil2100> Anyway, that's nice, 3 video lens tarballs in 3 days
[09:38] <sil2100> Quite nice indeed
[09:38] <sil2100> ;)
[09:39] <sil2100> I wonder why seb128 didn't yet choke me to death
[09:40] <sil2100> davidcalle: still, the po files got removed
[09:40] <sil2100> davidcalle: the whole po/ directory
[09:40] <sil2100> davidcalle: is this anticipated?
[09:40] <davidcalle> sil2100, include po/*
[09:41] <davidcalle> sil2100, fixing
[09:42] <seb128> sil2100, too busy with other things, your time will come :p
[09:42] <sil2100> davidcalle: phew, good thing I didn't upload - since ANOTHER version bump is something we would probably not want ;)
[09:42] <seb128> don't worry ;-)
[09:42] <sil2100> seb128: I'm starting to worry now ;)
[09:43] <davidcalle> sil2100, fixed
[09:44] <davidcalle> sil2100, by the way, do you know when the next Unity release is coming?
[09:48] <sil2100> davidcalle: next week, I hope
[09:48] <sil2100> davidcalle: thanks
[09:49] <davidcalle> sil2100, no problem :)
[09:51] <popey> s/, I hope//
[09:51] <popey> :)
[09:51] <sil2100> ...;)
[09:52] <seb128> sil2100, popey: it better has to be next week, you don't want didrocks to come back from holidays to see that no release went out ;-)
[09:56] <sil2100> seb128: https://code.launchpad.net/~sil2100/unity-lens-videos/ubuntu_ff3 <- new 'thing' for the video lens ;p
[09:57] <sil2100> Should be ok now, publishing the tarballs
[09:57] <seb128> sil2100, it better be ok, you will own me beers otherwise :p
[09:58] <sil2100> seb128: I'll buy you one beer anyway, just in case ;p
[09:58] <seb128> ;-)
[09:59] <sil2100> davidcalle: can you check the repo I pasted?
[09:59] <sil2100> If all the files are in ;) ?
[10:02] <sil2100> davidcalle: if you ACK, I just press 'Upload'
[10:03] <dholbach> seb128, I don't care about "some applications (mostly graphics)" :)
[10:03] <dholbach> but well spotted :)
[10:04] <seb128> dholbach, what?
[10:04] <dholbach> just commented on your last bug comment
[10:06] <seb128> dholbach, ah ;-)
[10:08] <davidcalle> sil2100, looks fine to me, but you haven't released the tarball on the project
[10:10] <davidcalle> sil2100, I mean, if this is for the tarball, it shouldn't include the packaging
[10:10] <sil2100> davidcalle: no, this is distro ;)
[10:10] <sil2100> davidcalle: it's the distro branch with the tarball merged in
[10:11] <davidcalle> sil2100, oh ok then :) I've builded just to be sure, and everything is here
[10:11] <sil2100> davidcalle: ok, so tarball uploaded
[10:12] <sil2100> seb128: if anything, new tarball uploaded for video lens, the packaging is in https://code.launchpad.net/~sil2100/unity-lens-videos/ubuntu_ff3
[10:12] <seb128> sil2100, I'm on it!
[10:13] <sil2100> seb128: thanks !
[10:13] <davidcalle> sil2100, great :) I'm pretty sure there was a change made to python setup.py sdist this cycle, the MANIFEST file was working fine before.
[10:14] <davidcalle> sil2100, or maybe it was failing but ken was always supervising and fixing it. ;)
[10:17] <seb128> davidcalle, sil2100: what was not working with the buggy package? the lens was still showing in my dash and listing local and remote videos
[10:17] <seb128> davidcalle, sil2100: I would like to know what to test next time ;-)
[10:17] <sil2100> seb128: I have no idea ;p davidcalle ^ ?
[10:18] <sil2100> seb128: I just know it was missing some files, translations and something more
[10:18] <davidcalle> seb128, it was working because of files still here from previous versions. If you remove everything and install 0.3.8, it won't show up in the Dash, because of the missing video.lens
[10:19] <seb128> davidcalle, what file? local user ones?
[10:19] <sil2100> During upgrade, existing files should have been removed
[10:20] <sil2100> And only those in package included, hm
[10:20] <davidcalle> seb128, hmm, then it was something else :/ A lens can't be in the Dash without it's .lens file.
[10:21] <seb128> davidcalle, I think I screwed my testing, I still had the previous deb installed on that box it seems
[10:21] <seb128> that explains it
[10:21] <davidcalle> seb128, let's hope it does. Anyway, the new package contains everything at the right place.
[10:25] <seb128> davidcalle, is the photo lens supposed to show anything if you don't have remote photo services activated?
[10:25] <seb128> like is there a local shotwell scope or something?
[10:25] <seb128> it's empty for me
[10:26] <davidcalle> seb128, yes, there is a local shotwell scope
[10:27] <seb128> davidcalle, is it known to not work?
[10:28] <davidcalle> seb128, nope, which version do you have? Should be unity-lens-photos 0.2.1
[10:29] <seb128> davidcalle, bah, still had 0.1.1 ... updating ;-)
[10:29] <seb128> davidcalle, oh
[10:30] <seb128> /usr/lib/unity-lens-photos/unity-lens-photos
[10:30] <seb128> ...
[10:30] <seb128>   File "/usr/lib/python3/dist-packages/gi/overrides/Signon.py", line 17, in process
[10:30] <seb128>     for (key, value) in session_data.iteritems():
[10:30] <seb128> AttributeError: 'dict' object has no attribute 'iteritems'
[10:30] <seb128> I guess I need other updates :p
[10:30] <davidcalle> seb128, yeah, the signon one to work with py3
[10:30] <seb128> davidcalle, better, thanks ;-)
[10:31] <davidcalle> seb128, currently, the shotwell scope fails if Shotwell hasn't been opened at least once. It's fixed in trunk.
[10:33] <seb128> davidcalle, it lists 96 photos where my shotwell has like 5000 photos
[10:33] <seb128> is that normal?
[10:33] <seb128> I guess it is, similar to the music lens
[10:34] <davidcalle> seb128, normal, the Dash doesn't handle so much results on slow machines.
[10:34] <seb128> right
[10:36] <davidcalle> seb128, I'm not sure if you have results deduplication yet with your Unity version. So you should see pretty similar results in two cats
[10:36] <seb128> davidcalle, yeah, recent and my photos are the same
[10:38] <davidcalle> seb128, hopefully it will land soon, with all results sorted by timestamp. it's pretty cool to see Facebook and Flickr friends photos all mixed :)
[10:38] <seb128> ;-)
[11:08] <popey> has CTRL+ALT+T broken for anyone else in latest quantal?
[11:08] <popey> i.e. doesn't open a terminal?
[11:21] <davmor2> popey: it is working for me currently let me upgrade and see
[11:29] <davmor2> popey: it's now not working
[11:31] <popey> sil2100, ^^ gsettings migration fallout? keyboard shortcut CTRL+ALT+T no longer works
[11:32] <sil2100> popey: it's part of the gnome compatibility compiz plugin, right?
[11:32] <sil2100> We didn't migrate settings for that one...
[11:33] <sil2100> But the default should be ctrl+alt+t anyway
[11:33] <sil2100> popey, davmor2: I think the reason for this are the invalid defaults for plugin settings ;/
[11:34] <sil2100> Since as Sam pointed out, in the bast we basically modified the defaults by a distro patch and now this one got removed
[11:34] <sil2100> And probably the new gsetting settings didn't get distro-patched in any way as well
[11:34] <sil2100> We'll need some overrides probably
[12:10] <Mirv> popey: confirming, ctrl-alt-t doesn't work
[12:11] <Mirv> additionally, shortcuts settings say ctrl-alt-t is it, but even if removed and put in again, it still doesn't work
[12:13] <Mirv> popey: file a bug (if you didn't already)
[12:14] <Mirv> even though I don't know exactly against which package :)
[12:27] <popey> bug 1041161
[12:44] <eroach> unity
[12:48] <eroach> anybody free now?
[12:49] <sil2100> Hi, not really free, but what's up?
[12:51] <eroach> nothing serious, first time come here,just to say hello
[13:19] <bobweaver> can any one tell me where the data dir is located for unity 3d like in unity 2d ?
[13:19] <bobweaver> thanks for your time
[13:19] <bobweaver> in  unity 6.1
[13:19] <bobweaver> er 6.2 *
[13:21] <bobweaver> is it as simple as I think and it is under /usr/share/dconf/services ?
[13:22] <bobweaver> dbus-1 not dconf *
[13:25] <Mirv> bobweaver: /usr/share/dbus-1/services/com.canonical.Unity.Panel.Service.service exists in the package unity-services
[13:25] <bobweaver> thanks Mirv
[13:26] <bobweaver> I am trying to change the formfactor and can not figure out the scema dir
[13:26] <bobweaver>  gsettings set  com.canonical.unity.form-factor 'TV'
[13:27] <bobweaver> should it be
[13:27] <bobweaver>  gsettings set  com.canonical.Unity  form-factor 'TV'
[13:28] <popey> the latter
[13:28] <bobweaver> seemed to work just dont understand (coming from QT )
[13:29] <bobweaver> Like in 2d I have the source in my home dir so
[13:29] <bobweaver> GSETTINGS_SCHEMA_DIR=ubuntu-tv/data gsettings set com.canonical.Unity2d form-factor tv
[13:31] <bobweaver> or in this case maybe it is in the generated dir ?
[13:33] <bobweaver> GSETTINGS_SCHEMA_DIR=Desktop/unity-6.2.0+bzr2616ubuntu0+762/<WHAT GOES HERE >  gsettings set com.canonical.Unity2d form-factor tv
[13:36] <bobweaver> ./com.canonical.Unity.gschema.xml   looks to be the ticket
[13:37] <Mirv> seb128: if you have time at some point, please push https://code.launchpad.net/~timo-jyrinki/compiz/ubuntu_quantal_GLES to lp:ubuntu/compiz so we'll have working staging / GLES builds again. it's rebased gles work on top of lp:ubuntu/compiz
[13:38] <bobweaver> Is there any compair charts any where for NUX like thike compaired to qt-quick or qt ?
[13:39] <bobweaver> So I can learn Nux faster
[13:39] <bobweaver> and for all the others that may be coming from a qt/c++ background
[13:40] <bobweaver> revierce enginering comes easy to me but alittle bit of reading would be nice :)
[13:40] <dandrader> bobweaver, I don't think so
[13:40] <dandrader> and the lack of documentation won't help either :)
[13:40] <bobweaver> +1
[13:41] <bobweaver> someone said to me that NUX is new that is why there is not documentation , I said yeah so is qt-quick
[13:41] <dandrader> but there is lp:nuxplayground. it contains some examples
[13:41] <seb128> Mirv, merged and pushed
[13:41] <bobweaver> thanks dandrader
[13:42] <bobweaver> brb time to boot into the new formfactor and see how it looks
[13:44] <bobweaver> Compiz does not like this formfactor :)
[13:45] <bobweaver> sigserc in brw_upload_state
[13:51] <Mirv> seb128: thanks
[13:51] <bobweaver> If anyone that is qualified to teach me NUX I would trade a laptop for it it is a compaq cq60 nothing special but yeah its a laptop that is working and in ok condition
[13:52] <bobweaver> I know C++ pretty well
[13:55] <bobweaver> I also know python ,vala C , javascr ip (all the web stuff ) haskell , perl
[13:56] <bobweaver> but nothing with gnome
[13:57] <Mirv> bobweaver: if the formfactor happens to use OpenGL ES only, you may want to check https://launchpad.net/~timo-jyrinki/+archive/compiz-gsettings-test which happens to have one snapshot of the OpenGL ES supporting Compiz
[13:58] <bobweaver> thanks a ton Mirv
[13:59] <Mirv> bobweaver: ah but sorry, no armhf build there (if it'd be an ARM device), use https://launchpad.net/~unity-team/+archive/staging instead although it has a lot of other components as well
[13:59] <bobweaver> Yeah lets just say that this is not in good shape at the moment , but I have no job and am smart and powerful so I think that I could handle / help with this even if it is just putting in comments
[14:00] <bobweaver> Mirv,  yeah I can only see like to top 2 lines of my ircclient I am going to join on my TV remote (system 76 starling )
[14:00] <bobweaver> can not wait to put a touch screen on this thing
[14:01] <bobweaver> brb
[14:13] <bobweaver> Mirv,  I have the stagging ppa installed upgrading again now
[14:13] <bobweaver> Thanks
[14:15] <Mirv> bobweaver: ok, that's the latest stuff there is
[14:16] <Mirv> seb128: to be pedantic, you could cherry-pick rev. 3279 from again rebased lp:~timo-jyrinki/compiz/ubuntu_quantal_GLES to clean the one changelog entry caused by your original merge of sam's branch. then it'd 1:1 what's actually in quantal now, + GLES
[14:19] <seb128> Mirv,  111 files changed, 7705 insertions(+), 4788 deletions(-)
[14:19] <seb128> Mirv, that's the diff between lp:ubuntu/compiz and that branch ... is that normal for a changelog update?
[14:20] <Mirv> seb128: you've something funny there, it's branched from lp:ubuntu/compiz? https://code.launchpad.net/~timo-jyrinki/compiz/ubuntu_quantal_GLES
[14:21] <Mirv> the original problem was that lp:~smspillaz/compiz/ubuntu_quantal_gles was not a proper branch to merge to a packaging branch
[14:22] <seb128> Mirv, ? I did bzr branch lp:ubuntu/compiz; cd compiz; bzr merge lp:~timo-jyrinki/compiz/ubuntu_quantal_GLES
[14:22] <seb128> Mirv, that gives me that diff ... can you try or tell me what I did wrong?
[14:24] <Mirv> seb128: http://pastebin.ubuntu.com/1164519/
[14:30] <seb128> Mirv, ok, dunno what was going on, I redid a clean round and it worked, merged, pushed
[14:30] <seb128> Mirv, thanks
[14:31] <Mirv> seb128: ok thanks!
[14:40] <bobweaver> Sorry to be naggy all. that is not my intentions I just want to learn :) . that said . can anyone please tell me if I am going about this wrong or if there is a different way that is quicker or "better". I am using QT-creator to to build Unity 6.2  I am using gnome-fallback  then I build and launch. can I use Unity 3d and then launch over the top ? or is there a sturt manager that will freak out ? or anything like that ? If there is an
[14:40] <bobweaver> y documentation on things of this nature plz by all means (maybe I am missing it). Thanks again
[14:40] <bobweaver> gnome fallback as DE
[17:46] <mikeit> hi
[18:17] <bobweavertv> Hello again. questtion if I wanted to start hacking away at the stanbdalone of unity 6.2 and adding code to the dash and other places who to talk to about that so I dont 1 step on toes and 2) dont put things in the wrong place if there is ideas already ? thanks
[19:05] <tgm4883> Have Unity previews made it into Quantal yet? I attempted to add the staging PPA, but the version of Unity in quantal is higher than the PPA, yet I don't seem to have previews enabled
[19:15] <bobweavertv> tgm4883,  what is unity version ? 6.2 ?
[19:16] <tgm4883> yea 6.2.0
[19:16] <bobweavertv> and you reinstalled the lens and scopes ?
[19:16] <tgm4883> and unity-lens-application is 6.4.0
[19:16] <bobweavertv> I had to reinstall unity a couple  of times
[19:16] <bobweavertv> drop to tty and reinstall
[19:17] <bobweavertv> tgm4883,  I got unity standalone running working but needs alot help
[19:22] <bobweavertv> tgm4883,  if that dont work could always use synaptic
[19:23] <tgm4883> bobweavertv, I'd imagine it will get into the repos sooner rather than later. I can just grab the code off the PPA and start working on my lens, I just won't be able to test it
[19:23] <bobweavertv> ill test the myth one correct
[19:24] <bobweavertv> err I can not get NUX to change its hlayout
[19:24] <bobweavertv> annoying
[19:26] <bobweavertv> but I am not sure if that in in scope or not . tgm4883 I have noticed that the music remote scope and also the videos remote scope are acting like RenderCoverFlow.qml with the formfactor on TV
[19:26] <bobweavertv> there has to be something there
[20:08] <bobweavertv> err so furstrating none of this documentation is correct
[20:09] <bobweavertv>   http://unity.ubuntu.com/getinvolved/development/unity
[22:00] <bobweavertv> OK I have changed the json data like 4 times dash.cpp and rendercoverflow  re-compiled it and it still change's  nothing what Am I doing wrong ?
[22:14] <bobweavertv> Ok Finally unity standalone built with kde as de
[22:30] <bobweavertv> ok it is all starting to come togeather now !!
[22:31] <bobweavertv> wonder if I can add case statements for form-factor or if there is something doing that
[23:12] <bobweavertv> sorry for all my crying just want to learn :)
[23:12] <bobweavertv> http://imagebin.org/225770