[07:02] <MCR1> thumper: Hi :). Followed your suggestions, hope it is okay now: https://code.launchpad.net/~mc-return/unity/unity.merge-more-optimizing/+merge/118265
[07:13] <didrocks> sil2100: hey, how are you?
[07:20] <sil2100> didrocks: hi! Not bad, how about you?
[07:20] <didrocks> sil2100: I'm good thanks!
[07:20] <didrocks> sil2100: I wanted to know if you got some clarifications on the branches that were merged without tests
[07:21] <sil2100> didrocks: the recent ones?
[07:21] <didrocks> sil2100: the one I pinged you on Friday about
[07:21] <didrocks> they are listed for 2 weeks on the google doc :)
[07:21] <didrocks> https://docs.google.com/a/canonical.com/document/d/1kiVPg0U7VJpHt21y-Qm9VtnLxsTmKHfBmA2B16yLGzc/edit# (still the same doc)
[07:21] <didrocks> and you should have noticed them when merged ;)
[07:22] <didrocks> the good news is that I got some clarification for the first one
[07:22] <didrocks> but there is still the second one which will block the release before having a good answer
[07:22] <didrocks> (I just moved the "resolved" one)
[07:23] <sil2100> Ok, will ping Jay then
[07:23] <didrocks> thanks ;)
[07:23] <didrocks> and remember to act on the preemptively next time
[07:23] <didrocks> sil2100: apart from that, how is the release coming?
[07:23] <didrocks> I saw that Nux is now building with the new glew, right?
[07:24] <sil2100> Will do, this particular merge was a refactoring one, I could have looked at it closer
[07:24] <didrocks> yeah, not sure if it's already covered
[07:24] <didrocks> if not, it should to ensure no regression
[07:24] <didrocks> hence maybe just a clarification is enough
[07:47] <sil2100> grrrr
[07:47] <sil2100> Why is staging broken again?!
[07:47] <sil2100> unityshell segfaults in nux
[07:49] <sil2100> jaytaoko: ^
[07:51] <sil2100> seb128: hello!
[07:52] <seb128> sil2100, hey, got nux fixed ;-)
[07:52] <sil2100> seb128: what do you mean ;)?
[07:58] <seb128> sil2100, remember the glew issue and the geis merge failing to build and to be merged when you left yesterday?
[07:58] <sil2100> seb128: yes, I see it all got in \o/ Thanks
[07:58] <sil2100> :)
[07:59] <sil2100> But still, it seems that nux is broken right now - maybe because the new glew?
[07:59] <sil2100> Since when using staging, my unityshell plugins segfaults in NuxGraphics somewhere
[08:00] <seb128> sil2100, well, rebuild it locally with the old glew and see?
[08:00] <didrocks> sil2100: ensure that you rebuild unity with latest nux, so that they use the same glew
[08:00] <sil2100> didrocks: ah, right - that might be even it, since unity wasn't really rebuilt, right?
[08:01] <didrocks> sil2100: it's my bet, already happened in the past
[08:01] <didrocks> sil2100: try a local build I would say with latest stack
[08:01] <didrocks> ensure you have the right glew version locally before building :)
[08:01] <sil2100> didrocks: will do ;)
[08:01] <sil2100> Thanks for the hint
[08:02] <didrocks> hope it will be useful :)
[08:17] <davidcalle> mhr3, hey
[08:18] <mhr3> davidcalle, hey
[08:18] <davidcalle> mhr3, can I annoy with, ahem, another bug report? :)
[08:18] <davidcalle> you*
[08:18] <mhr3> davidcalle, no :P
[08:18] <mhr3> davidcalle, so what is it?
[08:19] <davidcalle> https://bugs.launchpad.net/unity/+bug/1034786
[08:19] <ubot5`> Ubuntu bug 1034786 in Unity "Sources options notify::filtering signal is sent twice" [Undecided,New]
[08:19] <davidcalle> mhr3, ^
[08:20] <mhr3> davidcalle, there are no guarantees on notify signals, i think you should check yourself if the value has really changed
[08:21] <alo21> hi all
[08:21] <davidcalle> mhr3, that's what I'm doing. Thanks ;)
[08:21] <alo21> can I add a count in my applet indicator?
[08:40] <alo21> can someone help me, please?
[08:47] <sil2100> seb128, didrocks: it works! Just an unity rebuild is needed, as you guys said
[08:47] <seb128> great
[08:47] <sil2100> Would be nice to rebuild unity in staging
[08:47] <seb128> just approve a merge request I guess
[08:48] <seb128> there are over 40 waiting ones, there is probably a trivial you can unblock?
[08:48] <sil2100> Will have to find a trivial one
[08:48] <sil2100> True true, will try - hope not all are complicated, complex branches
[08:48] <seb128> well otherwise do a trivial one, find a typo to fix or something :p
[08:49] <sil2100> seb128: evil, but I like iit ;)
[08:49] <seb128> sil2100, there you go
[08:49] <seb128> $ intltool-update -m
[08:49] <seb128> The following files contain translations and are currently not in use. Please
[08:49] <seb128> consider adding these to the POTFILES.in file, located in the po/ directory.
[08:49] <seb128> hud/StandaloneHud.cpp
[08:49] <seb128> launcher/HudLauncherIcon.cpp
[08:49] <seb128> shortcuts/StandaloneShortcuts.cpp
[08:49] <seb128> unity-shared/UScreen.cpp
[08:49] <seb128>  
[08:49] <seb128> sil2100, want me to put a merge request up to update the POTFILES.in?
[08:50]  * seb128 does that, so you can approve it
[08:50] <sil2100> seb128: thanks!
[08:57] <seb128> sil2100, https://code.launchpad.net/~seb128/unity/potfiles-in-update/+merge/118899
[08:59] <sil2100> seb128: approved
[09:00] <seb128> sil2100, great
[09:33] <alo21> I tried to import indicate, but it failed? Why?
[09:53] <didrocks> sil2100: seb128: you do know that you didn't put UNBLOCK and then it won't be merged in https://code.launchpad.net/~seb128/unity/potfiles-in-update/+merge/118899, right?
[09:55] <seb128> didrocks, good catch
[09:55] <seb128> done
[11:10] <shuerhaaken> hi all! What does Unity rely on for thumbnailing? I was looking for "org.freedesktop.thumbnails.Thumbnailer1" service, but it isn't installed. Any hints?
[11:11] <shuerhaaken> One of the service files in /usr/share/dbus-1 should contain that Name
[11:12] <shuerhaaken> at least if Unity follows the standard here
[11:15] <Mirv> seb128: compiz SRU? or should I try to ask someone else if you prospect you'll not have time?
[11:16] <shuerhaaken> Nobody knows where the thumbnails in unity are coming from?
[11:21] <seb128> didrocks, you did the compiz upload during GUADEC, is there any chance you could just pull the extra fix for the armel build and dput that? I've it on my list still but have been swamped in other things and didn't have a chance yet to look again at where is the current SRU vcs, etc
[11:25] <didrocks> seb128: sure, will do after my shower :)
[11:25] <seb128> didrocks, thanks
[11:26] <didrocks> do you have the branch handy? (if not, I'll dig into my historic, no worry)
[11:30] <seb128> didrocks, https://code.launchpad.net/~timo-jyrinki/compiz/precise_SRU-1
[11:31] <seb128> didrocks, 'ci
[11:39] <didrocks> seb128: thanks :)
[11:43] <seb128> didrocks, yw, thank you for doing the upload!
[12:00] <didrocks> Mirv: hey
[12:00] <didrocks> Mirv: your branch diverged from the one we pushed to precise-proposed
[12:00] <didrocks> Mirv: can you resync it on it?
[12:03] <Mirv> didrocks: I think it did not, I diffed it to the precise-proposed one?
[12:03] <Mirv> in the upload phase the bzr url was changed so I changed it accordingly
[12:05] <didrocks> Mirv: well, your branch is missing the commits for 1:0.9.7.8-0ubuntu1.1, 1:0.9.7.8-0ubuntu1.2 and 1:0.9.7.8-0ubuntu1.3 that are in lp:~ubuntu-desktop/compiz/precise
[12:05] <didrocks> Mirv: can you please rebase on that one?
[12:06] <Mirv> didrocks: well, they weren't there five minutes ago until you pushed those...
[12:07] <Mirv> but sure can be done
[12:07] <didrocks> Mirv: yeah, it seems that I missed the last 3 commits, sorry
[12:07] <didrocks> Mirv: still, when you see commit missing, do not bundle in one, ask for refresh :)
[12:07] <Mirv> didrocks: yeah, I just based on sil2100's branch since it seemed identical to the uploaded one aside from the url change
[12:08] <didrocks> Mirv: yeah, it's quite similar :)
[12:08] <Mirv> just a second
[12:12] <Mirv> didrocks: lp:~timo-jyrinki/compiz/precise_SRU-1_try2
[12:13] <didrocks> Mirv: awesome! let me build that in my pbuilder (even if I'm on amd64, this should work)
[12:14] <didrocks> Mirv: you built it on an armel machine, right?
[12:15] <Mirv> didrocks: arhmf, yes
[12:15] <Mirv> both on my own device and later in PPA as well
[12:15] <didrocks> Mirv: excellent, thanks!
[12:17] <sil2100> mhr3: hi! :)
[12:18] <sil2100> mhr3: will you be very very busy in 1-2 hours ;)?
[12:30] <didrocks> Mirv: you are not building with the gpkg_gensymbol = 4, right?
[12:33] <didrocks> uploaded btw
[12:36] <ikey> I saw something on the Unity mailing list wrt. nautilus and different options (namely using solusos patches) http://osdir.com/ml/general/2012-08/msg15140.html
[12:36] <ikey> How likely is this and do you need any help/further patches ?
[12:36] <ikey> @ anyone unity dev related ^^
[12:40] <zcoob> sil2100: you were the one that helped me with the whole ubuntu config thingy last week right? :)
[12:42] <sil2100> ikey: I think you should ask someone from design about that
[12:42] <sil2100> zcoob: yes, I was lucky ;p
[12:43] <ikey> Not sure who to speak with lol, any pointers ?
[12:43] <sil2100> ikey: maybe try pinging poor JohnLea ;)
[12:43] <ikey> Ubuntu's not really my thing just I heard they were interested in using my patches
[12:44] <ikey> Well I'll wait coz you just done it for me xD thanks lol
[12:44] <ikey> Shame about nautilus 3.5 eh? :/
[12:44] <zcoob> i have a new issue maybe related to this :)
[12:45] <zcoob>  i use FAI so i run some scripts for a few clients. when i put the dbus-launch gsettings set thing in one of the scripts my dbus daemon segfaults
[12:45] <Mirv> didrocks: no, I'm not
[12:45] <Mirv> didrocks: thanks
[12:45] <didrocks> Mirv: you should change with what I showed you during the sprint for the future and getting new symbols updates :)
[12:46] <didrocks> not important for this one, we decided to not upload the .symbols
[12:46] <didrocks> just that I stumble upon it :)
[12:50] <sil2100> zcoob: segfaults? Every time?
[12:50] <zcoob> i'm checking again
[12:51] <zcoob> how do i redirect stderr to stdout again? :)
[12:51] <zcoob> i always forget
[12:51] <Zhenech> 2>&1
[12:52] <zcoob> so its program | 2>&1 tee > bla.txt ?
[12:53] <didrocks> program 2>&1 | tee bla.txt
[12:53] <zcoob> alright
[12:54] <Mirv> didrocks: I'll set it in my environment now, I had it in my notes
[12:56] <didrocks> great :)
[12:57] <sil2100> jaytaoko: ping
[12:57] <zcoob> hmm sil2100 the dbus-launch gsettings line doesn't produce any errors it seems, however in /var/log/syslog i get this [ 1248.578480] dbus-daemon[7238]: segfault at 40 ip 00007f50f54abdba sp 00007fffe6af3720 error 4 in libc-2.15.so[7f50f5462000+1b3000]
[12:59] <sil2100> zcoob: strange thing, it never segfaulted on dbus-launch before for me, hm hm
[12:59] <zcoob> it doesn't for me either
[12:59] <zcoob> if i run the script locally
[12:59] <zcoob> if i run it through the network it segfaults
[13:00] <zcoob> although i
[13:00] <zcoob> am not 100% certain how FAI actually handles scripts
[13:00] <sil2100> When you run it through the network, what user does start the script?
[13:00] <zcoob> root
[13:14] <zcoob> oh sil2100 i found a new error :) executing: dbus-launch gsettings set org.gnome.desktop.interface monospace-font-name "Monospace 11"  ** (process:18630): WARNING **: The connection is closed
[13:15] <seb128> if the dbus service is segfaulting you have an issue
[13:16] <seb128> you should try to get a stacktrace
[13:17] <zcoob> it's probably a simple solution
[13:17] <zcoob> or me screwing up
[13:28] <zcoob> i mean tbh i don't even know why Ubuntu Mono 13 looks like shit on this installation
[13:28] <zcoob> if i install default ubuntu 12.04 it looks just fine :(
[13:28] <zcoob> i guess looking into that might be the easier solution
[13:41] <zcoob> oh boy ofc i was missing a font ... not sure why it isnt provided by the unity package though
[13:56] <sil2100> zcoob: oh ;)
[13:56] <sil2100> jaytaoko: piiiing
[13:56] <zcoob> yeah ttf-ubuntu-font-family wasnt installed
[13:56] <zcoob> now Ubuntu Mono 13 looks exactly like Monospace 11
[13:59] <jaytaoko> sil2100: pong
[14:00] <sil2100> jaytaoko: \o/ hello!
[14:00] <sil2100> jaytaoko: I have two things right now:
[14:00] <jaytaoko> sil2100: hello!
[14:01] <sil2100> jaytaoko: Didier pointed me to a merged-in branch (refactoring branch) that wasn't covered with tests, and we wanted to get some clarification as to whether it is tested
[14:01] <sil2100> jaytaoko: https://code.launchpad.net/~unity-team/nux/nux-timer-backend-fixes/+merge/114642
[14:01] <sil2100> jaytaoko: are all the changes there tested by existing tests?
[14:02] <jaytaoko> sil2100: no, not yet. This is the refactoring of existing code. t we are not using the timer backend in Unity
[14:03] <jaytaoko> sil2100: but we are not using
[14:04] <sil2100> didrocks: ^
[14:06] <didrocks> jaytaoko: when do you plan to use it? when it will be done, will you add tests for it?
[14:07] <jaytaoko> didrocks: eventually yes, we will have tests covering that part
[14:08] <didrocks> jaytaoko: I don't like this "eventually" :)
[14:08] <sil2100> ;)
[14:08]  * sil2100 is already in a state of despair
[14:08] <sil2100> ;)
[14:09] <didrocks> jaytaoko: can we have a commitment from your side that it will be tested when used?
[14:14] <sil2100> jaytaoko: the other thing:
[14:14] <sil2100> jaytaoko: I was trying to run make distcheck on nux just now, and it failed on distuninstallcheck
[14:14] <sil2100> ERROR: files left after uninstall:
[14:15] <sil2100> And a whole list of Textures, fonts and things like that
[14:15] <jaytaoko> sil2100: what does it say?
[14:16] <sil2100> ERROR: files left after uninstall:
[14:16] <didrocks> sil2100: ok, talked with jaytaoko, I moved the branch to another category, seems you are fine
[14:16] <sil2100> And then a big list afterwards
[14:16] <sil2100> didrocks, jaytaoko: thanks!
[14:16] <sil2100> jaytaoko: how are you rolling out tarballs in nux btw.?
[14:17] <sil2100> make distcheck usually?
[14:17] <jaytaoko> sil2100: no, I haven't done it recently
[14:17] <jaytaoko> sil2100: do you want me to try it
[14:18] <sil2100> jaytaoko: if you have a spare moment, could you just check if make distcheck does what it should?
[14:18] <sil2100> Since I would like to release the new tarballs today after tests
[14:18] <sil2100> didrocks: although we're stalled on autopilot right now :( Still...
[14:19] <didrocks> sil2100: yeah, I read what you were telling :(
[14:20] <didrocks> sil2100: so not really confident about rolling tarballs before having autopilot results
[14:21] <jaytaoko> sil2100: making distcheck
[14:22] <sil2100> Neil's gonna kill me ;(
[14:30] <jaytaoko> sil2100: still running distcheck
[14:37] <jaytaoko> sil2100: I get an error toward the end of the "make distcheck"... FakeGestureEvent.h is missing
[14:40] <sil2100> jaytaoko: oh, didn't have that, maybe it didn't reach that state yet on my system?
[14:42] <jaytaoko> sil2100: I am going to fix this issue locally and then continue the make distcheck
[14:42] <sil2100> jaytaoko: thanks!
[14:43] <sil2100> didrocks: I think we need to really start discussing a switch to another trunk-freeze method, I'll try pinging fginther and mmrazik
[14:43] <sil2100> Since this is counter productive
[14:44] <mmrazik> sil2100: actually this is something I wanted to talk with you
[14:44] <mmrazik> but was postponing until the release is ready
[14:44] <sil2100> mmrazik: excellent
[14:44] <sil2100> mmrazik: maybe we could have a chat about it somewhere tomorrow?
[14:44] <sil2100> Since stalling other development just because there are testing problems is bad
[14:44] <mmrazik> sil2100: yes. I would prefer to schedule something just to make sure it will happen
[14:45] <mmrazik> sil2100: you are in CEST, right?
[14:45] <sil2100> Yes
[14:45] <mmrazik> sil2100: 3pm ?
[14:45] <mmrazik> tomorrow
[14:46] <mmrazik> or 9am
[14:46] <sil2100> mmrazik: maybe 3pm CEST?
[14:46] <mmrazik> sideffect: okay
[14:47] <sil2100> mmrazik: will you add it to the callendar?
[14:47] <mmrazik> sil2100: done
[14:48] <sil2100> mmrazik: thanks!
[14:48] <mmrazik> sideffect: sorry. the previous message was supposed to go to sil2100 (autocomplete error)
[14:48] <sil2100> ;)
[14:51] <didrocks> sil2100: yeah, I told you at the sprint you need to start this discussion :)
[14:51] <didrocks> sil2100: I still think that you need to find a way to have the release tag on the mainline (which you can achieve with the examples I showed to you and to mmrazik)
[14:51] <fginther> mmrazik, sil2100, I can also attend at that time
[14:51] <mmrazik> fginther: adding you
[14:52] <fginther> mmrazik, thanks
[14:52] <mmrazik> btw feel free to add anybody else. the guests can modify the event
[15:07] <mhr3> sil2100, eh, you were saying? :)
[15:10] <sil2100> mhr3: heh, wanted to ask you for some tarballs, but we need to wait with that ;p
[15:20] <jaytaoko> sil2100: I am still resolving the missing files with distcheck. almost done...
[15:30] <sil2100> jaytaoko: ok, thanks
[15:31] <jaytaoko> sil2100: I have a branch with a fix for the make distcheck
[15:32] <sil2100> jaytaoko: does it fix all make distcheck troubles?
[15:55] <jaytaoko> sil2100: sorry, I am in a meeting, will get back to you
[17:20] <niadh> Hi all, I am curious about getting unity running on Arch Linux and there's some packages available but they're beginning to get a bit out of date and wondered if anyone was about that might be able to help me?
[18:05] <jaytaoko> sil2100: ping
[18:07] <jaytaoko> sil2100: here is my fix with for the "make distcheck" : https://code.launchpad.net/~unity-team/nux/nux.fix-distcheck/+merge/119002
[18:21] <sil2100> jaytaoko: thanks! Approving
[18:23] <jaytaoko> sil2100: I forgot to add the UNBLOCK
[18:23] <sil2100> I added
[18:24] <jaytaoko> sil2100: cool!
[18:24] <jaytaoko> sil2100: can I merge it now?
[18:25] <sil2100> jaytaoko: I already set it to 'Approved' ;)
[18:25] <jaytaoko> sil2100: of you did it! good!
[18:29] <sil2100> Ok guys, I need to finish for today, it's dark already
[18:30] <sil2100> Later
[20:03] <nmarques> anyone around maintains compiz on ubuntu ?
[20:04] <seb128> nmarques, you should just ask your question, is that an issue if anyone not maintaining them can reply?
[20:05] <nmarques> seb128, my question is quite simple... I've packaged compiz and the required packages from Ubuntu 12.10 sources (no crazy hacks)
[20:05] <nmarques> I'm just wondering what changes are to be done for Unity
[20:05] <nmarques> since I've resumed my 2 year old project of packaging Unity on SUSE
[20:06] <nmarques> so far the utouch stack is build properly, and some of the base/support libraries for Unity
[20:06] <seb128> "changes to be done for Unity"
[20:06] <nmarques> the next piece is compiz (and then the indicators, testing and integration)
[20:06] <seb128> what do you mean "for Unity"?
[20:06] <nmarques> I mean that from what I remember from 2 years ago
[20:06] <nmarques> there were a lot of hacks for keybindings and some in the base schemas
[20:07] <seb128> not sure what you are asking
[20:07] <nmarques> I'm wondering if all of that is still required, or if a plain upstream deployment will get it working
[20:07] <seb128> do you ask how to do packaging?
[20:07] <seb128> like how write a gconf schemas?
[20:07] <seb128> or change default configs?
[20:08] <nmarques> I'm probably not going to use gconf schemas, instead plain text files
[20:08] <nmarques> the traditional .ini backend
[20:08] <nmarques> gconf is somehow deprecated :)
[20:09] <seb128> ok, I don't get was you ask for
[20:09] <seb128> what about keybindings?
[20:09] <nmarques> I don't mind dropping them and adding them later when working on integration :)
[20:09] <nmarques> so far the most important thing is to get that stuff running
[20:10] <seb128> what is your question?
[20:10] <seb128> "what changes are to be done for Unity" is not a question
[20:10] <seb128> it lacks a "to ..
[20:10] <nmarques> seb128, are there any hacks required for Unity or a plain deployment from ubuntu sources is known to work ?
[20:10] <seb128> like "for Unity to run"
[20:10] <seb128> or "for Unity to be shiny"
[20:10] <seb128> no
[20:11] <nmarques> not to much shiny hopefully, I forgot my sun glasses :P
[20:11] <seb128> well, I'm just trying to say that "for Unity" doesn't mean anything I can understand
[20:11] <seb128> you can build and run unity without hacks
[20:12] <seb128> you need a GTK patch for appmenu for program not using the new gmenu gtk api
[20:12] <seb128> there is also a small patch for ido sliders to work correctly
[20:12] <seb128> but otherwise things should work fine on any distro
[20:12] <zgreg> wow, the latest changes to unity/compiz/nux in 12.04 boost performance nicely
[20:12] <seb128> zgreg, does it? good ;-)
[20:12] <DebolazW> seb128: I think he's asking about what modifications needs to be done to third party libraries for Unity to compile/run. Unity has been a bit notorious in the past for requiring some customization done to the environment.
[20:13] <zgreg> yes, I just updated
[20:13] <seb128> DebolazW, if that's the question I just replied ;-)
[20:13] <DebolazW> Well, I *think* anyway. :)
[20:13] <DebolazW> zgreg: I feel 12.04 in general has been a massive, massive, massive improvement to Unity performance and stability. :)
[20:14] <zgreg> yes, but 12.04 release was a bit buggy and suffered from some regressions
[20:15] <DebolazW> (To be fair, most of the bugs in previous releases seems to have been compiz bugs and not the unity specific stuff as such)
[20:15] <zgreg> yeah, especially compiz massively improved
[20:16] <DebolazW> I think 12.04 was the first release I haven't had any problems with compiz actually.
[20:16]  * DebolazW remember back in the pre-unity days, when compiz would actually leak so much resources that videos couldnt even be played fullscreen after a few hours.
[20:19] <zgreg> I've been using compiz for over four years and never had problems that big
[20:27] <DebolazW> Now if I could only get applications to start fullscreen without installing ccsm, life would be rather perfect in a vanilla installation. But I can live with that. :)
[20:56] <heavensmile> Hi I just want to post my opinions on Unity
[20:56] <heavensmile> I will say it right out, I love unity, in compassion with GNOME Shell, which  I think look good on screen-shots don't work do to "serious work" with multiple apps open.
[20:56] <heavensmile> With Unity I'm even more productive then with  GNOME 2.xx. Unity is designed with "real use" in mind,
[20:57] <heavensmile> polished is still needed but when it  gets that polished, Unity it will truly rock.
[20:57] <heavensmile> don't care about all the haters, history will prove them wrong.
[21:09] <zgreg> both gnome-shell and unity have their strengths, the issue with the shell is lack of focus and vision
[21:10] <zgreg> and of course all the interface experiments right in the masterbranch (like the recent changes in nautilus)
[21:15] <heavensmile> gnome-shell feels like proptoype interface
[21:15] <heavensmile> *like a
[21:16] <heavensmile> *prototype
[21:20] <heavensmile> my problem with the shell is that it interrupts the user experience