[00:42] <snadge> so theres been a few unity updates in precise lately.. whats new? ;)
[00:44] <snadge> zless /usr/share/doc/unity/changelog.Debian.gz
[00:44] <snadge> i see.. fascinating :P
[06:42] <kancerman> best past change to unity - freezing the launcher bar on the left - yeah, autohide is optional but, to me, that's gotten annoying, thanx to whosoever froze it in place ;)
[07:01] <MCR> Latest Unity version does not want to start here (Precise). I have to remove Unity completely to make my desktop boot. I am not using any Compiz/Unity PPAs anymore. Also my right mousebutton problem is back (right mousebutton kills Compiz). Can someone help me with that ?
[07:30] <MCR> Another thing: When trying to compile Emerald from source under Precise it won't compile anymore. The errors are undefined references to exp, pow, dlclose, dlerror, dlopen, dlsym. Can someone help me with fixing this ?
[07:32] <MCR> If someone knows if those references just got a name change I could maybe fix it myself... I want Emerald back !
[07:44] <angeloc> opening dash remembers last searched word and shows only results relatives to this word, is this the expected behaviour?
[07:45] <angeloc> i think that dash should clear the search bar, could be really a pain for new users find applications if dash shows always last used one
[07:50] <didrocks> Saviq: hey, the press to reveal or barriers don't work here (nvidia)
[07:50] <didrocks> Saviq: with the patched metacity and unity-2d
[07:50] <angeloc> didrocks: dash remembers last searched word and shows only results relatives to this word, is this the expected behaviour?
[07:50] <didrocks> angeloc: yeah, it is
[07:50] <angeloc> didrocks: i think that dash should clear the search bar, could be really a pain for new users find applications if dash shows always last used one
[07:51] <didrocks> angeloc: tallk to JohnLea about design discussions. There are quite a lot of reasons to wanting this behavior
[07:51] <angeloc> didrocks: ok
[08:04] <Saviq> didrocks, did you get it from packages or built yourself?
[08:05] <didrocks> Saviq: built myself (both metacity and unity-2d)
[08:05] <Saviq> didrocks, which xfixes?
[08:06] <didrocks> Saviq: the latest upload from RAOF specific for unity-2d, one sec
[08:07] <didrocks> Saviq: 1:5.0-4ubuntu4
[08:07] <didrocks> Saviq: can't that be related to nvidia?
[08:07] <Saviq> didrocks, not really, I've been testing on nvidia and worked fine, as long as I built with the correct xfixes
[08:08] <didrocks> yeah, should be the right xfixes for this one
[08:08] <Saviq> but never had something "specific for unity-2d"
[08:08] <Saviq> just the latest from staging ppa
[08:08] <Saviq> didrocks, let me investigate
[08:08] <didrocks> Saviq: I'm using the distro ones, I know that you needed that version
[08:08] <didrocks> Saviq: thanks!
[08:09] <Saviq> didrocks, no, we need 1:5.0-4ubuntu1"
[08:09] <Saviq> wait
[08:09] <didrocks> hum
[08:09] <Saviq> didrocks, ok let me check it out
[08:09] <Saviq> will get back to you
[08:10] <didrocks> Saviq: thanks :)
[08:10] <didrocks> I asked RAOF to join the party
[08:10] <didrocks> Saviq: can be something I'm doing wrong as well, if I can check some part? (like strut?)
[08:13] <Saviq> didrocks, hide-mode 0?
[08:13] <Saviq> erm
[08:13] <Saviq> 1?
[08:13] <Saviq> and what's the symptom? can't get launcher to reveal?
[08:13] <didrocks> Saviq: yeah, I set it to 1
[08:13] <didrocks> the launcher hides
[08:14] <didrocks> but then, I can't reveal it
[08:14] <didrocks> nor I have barriers between screens
[08:14] <Saviq> not at all?
[08:14] <didrocks> nothing
[08:14] <Saviq> can you make check?
[08:14] <Saviq> we tests for barriers
[08:14] <didrocks> sure
[08:14] <Saviq> +have
[08:15] <didrocks> Saviq: will it screw my environment?
[08:15] <Saviq> didrocks, should not
[08:15] <Saviq> didrocks, you can run just the barrier ones
[08:15] <didrocks> ok, /me will keep vim opened on tarmac then :)
[08:15] <Saviq> but the others would only open your dash at the most anyway
[08:15] <didrocks> some command line? ;)
[08:15] <Saviq> didrocks, libunity-2d-private/tests/
[08:15] <Saviq> there's a bunch of binaries
[08:20] <didrocks> Saviq: so, I should run the test in launcher, isn't it?
[08:20] <didrocks> Saviq: not sure I have the testability setup though
[08:20] <didrocks> any advice? (README doesn't help)
[08:20] <didrocks> Testability installation instructions
[08:20] <didrocks> et's start with tht :)
[08:22] <didrocks> Saviq: I have some missing packages though: testability-qttas, ruby-testability-driver-qt-sut-plugin, testability-visualizer
[08:27] <Saviq> didrocks, you don't need testability for that
[08:27] <Saviq> didrocks, the barrier tests are unit tests
[08:27] <Saviq> just run the binary from libunity-2d-private/tests
[08:27] <Saviq> or make check to run them all
[08:28] <didrocks> ok :)
[08:28] <didrocks> 100% tests passed, 0 tests failed out of 7
[08:28] <didrocks>     Start 7: pointerbarriertest
[08:28] <didrocks> 7/7 Test #7: pointerbarriertest ...............   Passed    6.06 sec
[08:28] <Saviq> so barriers seem to work
[08:28] <Saviq> in essence
[08:28] <didrocks> yeah, I just don't have them :/
[08:29] <didrocks> so hide_mode set to 1
[08:29] <didrocks> can't reveal, no barrier in between
[08:29] <Saviq> yeah that's all that should be needed
[08:29] <Saviq> didrocks, updating now (stoopid out of date mirror)
[08:29] <Saviq> didrocks, and will check on both nvidia and intel
[08:30] <didrocks> Saviq: thanks :)
[08:30] <didrocks> isn't there any particular STRUT I should check?
[08:30] <didrocks> on the root window
[08:30] <didrocks> _NET_WM_STRUT_PARTIAL, _NET_WM_STRUT
[08:30] <Saviq> there should be no struts applied from the launchers in hide-mode 1
[08:31] <Saviq> only from panels
[08:31] <didrocks> ok
[08:31] <Saviq> brb
[09:24] <MCR> compiz[3440] trap int3 ip:7f8471cc613b sp:7fffd54c9bd0 error:0
[09:24] <MCR> ^^^when clicking right mousebutton. HELP !
[09:26] <MCR> I can reproduce this crash easily.
[09:46] <seb128> MCR, it's bug #954079 and comments suggest you should disable "shift switcher"
[09:57] <MCR> seb128: Thanx a lot. Do you know if this is intertwined with Unity not starting here ?
[09:57] <seb128> MCR, could be
[09:59] <MCR> seb128: Thx
[10:00] <seb128> yw
[10:09] <MCR> seb128: Got my right mousebutton back :) GREAT
[10:09] <seb128> cool
[10:10] <MCR> seb128: but Unity still does not want to start :-(
[10:10] <seb128> can you pastebin your stdout or .xsession-errors?
[10:13] <MCR> seb128: Can you instruct me how to get to those ?
[10:14] <seb128> MCR, log into unity, ctrl-alt-f1 to go to a vt, log in, cp .xsession-errors somewhere
[10:14] <seb128> then go back to whatever works for you and pastebin the file you copied
[10:15] <MCR> seb128: .xsession-errors is in ~ ?
[10:15] <seb128> yes
[10:15] <MCR> ok
[10:15] <MCR> one momentos
[10:16] <MCR> installing unity
[10:16] <MCR> rebooting
[10:24] <mhr3> kamstrup, btw there are some reviews piling up for ula and ulf, could you look at them when you have a moment?
[10:25] <MCR> seb128: back
[10:25] <seb128> MCR, wb
[10:25] <MCR> seb128: the file has 17MB =-O
[10:26] <seb128> MCR, can you grep unity in it?
[10:26] <seb128> and pastebin that only?
[10:26] <seb128> MCR, or just select the most recent loggin if it was not rotated
[10:27] <kamstrup> mhr3: I am pretty tied up elsewhere I have promised some dates to some evil overlords I am afraid...
[10:27] <kamstrup> mhr3: how about njpatel (it's not like he is ever doing anything! ;-) or RainCT?
[10:28] <kamstrup> or the honorable steve lofty?
[10:28] <mhr3> kamstrup, k, i'll try to get someone to look at them
[10:28] <njpatel> wtf
[10:28] <mhr3> njpatel, sooo... :)
[10:29] <njpatel> I no worky
[10:29] <mhr3> good good, now you can :)
[10:31] <mhr3> njpatel, so, here you go
[10:31] <mhr3> https://code.launchpad.net/~mhr3/unity-lens-files/fix-947856/+merge/97440
[10:31] <mhr3> and https://code.launchpad.net/~mhr3/unity-lens-files/fix-955229/+merge/97603
[10:31] <mhr3> and https://code.launchpad.net/~mhr3/unity-lens-applications/no-recent-apps-search-just-filtering/+merge/97087
[10:31] <kamstrup> njpatel: sorry dude ;-)
[10:31] <MCR> seb128: It looks like the log is getting appended to .xsession-errors. I will paste the tail of the file. If this does not help, I will delete the whole file and create a new log...
[10:32] <seb128> ok
[10:32] <njpatel> wth
[10:33] <njpatel> mhr3, its on the TODO, give me ~ 1hr
[10:33] <mhr3> njpatel, sure
[10:34] <seb128> njpatel, stop swearing!
[10:35] <MCR> seb128: http://pastebin.com/1mjgMRxs
[10:35] <seb128> MCR, seems like you try to use unity2d
[10:35] <MCR> seb128: I do not know where one session stops and another new one starts, but I copied the tail of the file...
[10:36] <seb128> MCR, does a guest session works?
[10:36] <njpatel> seb128, ahem, I obviously meant "What the flip?" and "What the heck?"
[10:36] <seb128> njpatel, ;-)
[10:36] <didrocks> Saviq: tsdgeos: greyback: multimonitor merged \o/
[10:36] <greyback> didrocks: woo!
[10:36] <MCR> seb128: I used 2d, because I had intel driver troubles, but those are gone now...
[10:36] <Saviq> didrocks, yup
[10:37] <MCR> seb128: unity --replace would always use the 3d version. no ?
[10:38] <didrocks> also, it seems my committer change worked in production for tarmac :)
[10:39] <seb128> MCR, not sure
[10:39] <seb128> well maybe ping greyback about 2d not working
[10:39] <seb128> I've no clue about unity-2d
[10:39] <MCR> seb128: I just had fbdev as driver for a short period of time that's why I used 2d. I should use and want to use 3d.
[10:40] <seb128> try to select 3d back on the login screen then and see how it goes
[10:41] <MCR> ok, I will also delete .xsession-errors so we get a fresh one...
[10:41] <seb128> good
[10:41] <MCR> seb128: Thx 4 being so patient.
[10:41] <seb128> yw ;-)
[10:43] <sil2100> geh, have to add auto-join for freenode ;)
[10:43] <MCR> How can I log out without having Unity nor another DE running ?
[10:45] <MCR> exit will just close the terminal (guake) and logout does not work (bash: logout: not login shell: use 'exit'
[10:45] <MCR> hmm
[10:46] <MCR> nevermind, I will simply reboot - the standard DE is Unity-3d here, so it should try to log in there
[10:47] <MCR> Or is there a way to choose the DE to log in at startup ?
[10:47] <MCR> like holding ALT during boot or something like that ?
[10:48] <MCR> seb128: Any idea ^^ ?
[10:49] <seb128> MCR, do you use autologin? edit /etc/lightdm/lightdm.conf to turn it off and reboot?
[10:50] <MCR> seb128: ah, yeah - sure - thx
[10:50] <seb128> yw
[10:50]  * popey welcomes sil2100 
[10:50] <popey> ☺
[10:53] <MCR> seb128: user-session=ubuntu in lightdm.conf so it should be ok - rebooting
[10:53] <sil2100> :)
[11:05] <MCR> seb128: fresh .xsession-errors file: http://pastebin.com/t5pjwyCr
[11:05] <didrocks> greyback: so, it's working fine
[11:05] <didrocks> however, just a note
[11:05] <didrocks> on nvidia, I can have no "primary monitor" set
[11:05] <didrocks> in this case, what unity-3d used to do was to put the launcher on the leftmost monitor
[11:05] <didrocks> which is what makes sense IMHO
[11:06] <didrocks> in this case, I put on the right one (I guess it's seen as the first monitor as it's the laptop one)
[11:06] <didrocks> it*
[11:06] <seb128> MCR, can you try using one of the Ubuntu themes and see if that makes a difference and also move .config/autostart away (keep it for debugging)
[11:06] <greyback> didrocks: hmm ok
[11:06] <didrocks> on the left, I have: an external monitor, on the right: my laptop monitor
[11:06] <didrocks> greyback: if I define a primary monitor on nvidia-settings, all is fine
[11:06] <didrocks> greyback: that's not blocking the release, but you maybe want a bug about it?
[11:06] <greyback> didrocks: I will
[11:06] <MCR> seb128: I do whatever is to do to get Unity back ;)
[11:06] <didrocks> thanks greyback ;)
[11:07] <didrocks> do not hesitate to ping me if you need more testing/info
[11:07] <didrocks> sil2100: hey
[11:07] <didrocks> sil2100: can you just take lp:unity-2d again
[11:07] <greyback> didrocks: thanking you
[11:07] <didrocks> sil2100: build it and test it?
[11:07] <seb128> MCR, can you try those, maybe one and after the other, to figure if any fixes the issue?
[11:07] <sil2100> didrocks: ACK
[11:07] <didrocks> greyback: just waiting for sil2100's feedback and if all is green, I'm pushing :)
[11:07] <didrocks> greyback: nice work!
[11:08] <sil2100> didrocks: should I test something in particular?
[11:08] <didrocks> greyback: (please target the bug above for 5.8 to not loose it)
[11:08] <greyback> didrocks: thanks to Saviq & tsdgeos
[11:08] <didrocks> sil2100: you have an ATI? isn't it?
[11:08] <sil2100> didrocks: yes, fglrx driver
[11:08] <didrocks> yeah, thanks to Saviq and tsdgeos, spendid work :)
[11:08] <didrocks> sil2100: and more than one monitor?
[11:08] <MCR> seb128: okay - so first I will change the theme.
[11:08] <sil2100> Yes
[11:08] <didrocks> sil2100: ok, so first, install the new version
[11:09] <didrocks> see that you can still reveal the launcher
[11:09] <didrocks> then, on g-c-c, change the primary monitor
[11:09] <Saviq> didrocks, tsdgeos, greyback: good stuff!
[11:09] <seb128> MCR, rm the .xsession-errors as well between reboots
[11:09] <didrocks> to the one on the right
[11:09] <MCR> seb128: ok
[11:09] <didrocks> and ensure that you have some barrier between the two
[11:09] <sil2100> ACK
[11:09] <didrocks> thanks sil2100 :)
[11:11] <sil2100> np ;)
[11:11] <MCR> seb128: What is the original theme called: Ambience ?
[11:11] <seb128> MCR, Ambiance
[11:11] <MCR> seb128: ok, thx
[11:11] <seb128> yw
[11:11] <MCR> theme is changed
[11:12] <MCR> .xsession-errors removed
[11:12] <MCR> installing Unity (once again ;))
[11:12] <MCR> reboot
[11:20] <sil2100> Ok, switching sessions
[11:22] <sil2100> didrocks: is a metacity rebuild required as well?
[11:22] <sil2100> Or just the trunk from unity-2d is sufficient?
[11:23] <didrocks> sil2100: the metacity I pointed to you yeah
[11:23] <didrocks> Saviq: ah, I got the launcher stucked
[11:23] <didrocks> greyback: ^
[11:23] <sil2100> didrocks: since ok, launcher revealing still works fine, but hm, I can't seem to have the barrier between screens
[11:23] <Saviq> didrocks, yes, two issues we have to address
[11:23] <didrocks> sil2100: the barrier only appear if the launcher is on the right screen
[11:24] <didrocks> Saviq: you should use the unity hidemachine btw ;)
[11:24] <sil2100> didrocks: ah, ok, then one moment ;)
[11:24] <didrocks> Saviq: at least you would have a state machine, which is reliable
[11:24] <Saviq> didrocks, 1) spread-induced 2) !mouse-over the launcher when it's still animating
[11:24] <didrocks> (with all the corner cases done)
[11:24] <sil2100> didrocks: how can I force the launcher being on a different screen?
[11:24] <Saviq> didrocks, I think we have the hide modes working fine, just two bugs there
[11:25] <sil2100> Killing places and starting them on a given screen?
[11:25] <didrocks> sil2100: see what I told above, change the primary monitor
[11:25] <Saviq> didrocks, known, and to be addressed (there in trunk, too)
[11:25] <didrocks> Saviq: ok :)
[11:25] <didrocks> Saviq: but you don't handle some corner cases still
[11:25] <didrocks> Saviq: like, click on a launcher item
[11:25] <didrocks> don't move
[11:25] <didrocks> the launcher hides
[11:25] <didrocks> and click on a launcher item
[11:25] <didrocks> move
[11:25] <didrocks> the launcher should stay
[11:25] <greyback> yep, lots lf small launcher interactions are wrong
[11:26] <didrocks> also put the mouse under the launcher area
[11:26] <sil2100> Ah, ACK ;)
[11:26] <didrocks> super
[11:26] <didrocks> the launcher shows
[11:26] <didrocks> release
[11:26] <didrocks> the launcher should hide
[11:26] <didrocks> and super, launcher shows, move the mouse, release, launcher should not hide
[11:26] <didrocks> all of this is handled by what we have done as a state machine in -3d
[11:27] <didrocks> I think having a similar thing can works well for 2d (there is even a Qt state handler that sounds promising :))
[11:27] <greyback> would be great. much of that logic is determined by various qml rules, which isn't that elegant
[11:28] <sil2100> didrocks: hm, where exactly can I switch that? *is a bit confused*
[11:28] <didrocks> greyback: yeah, we started with something similar in 3d
[11:29] <didrocks> greyback: and then, got more and more hit by this kinds of bug
[11:29] <didrocks> greyback: maybe not something for P, but for Q
[11:29] <greyback> sil2100: you set primary monitor in the Displaysa applet, drag the black panel depicted to the monitor you want to be primary
[11:29] <didrocks> the state machine is awesome to avoid this :)
[11:29] <sil2100> WOW
[11:29]  * sil2100 didn't know that he could drag that black panel
[11:33] <MCR> seb128: back - with bad news:
[11:33] <MCR> seb128: changing gtk+ theme did not help
[11:34] <seb128> it should have reduced the .xsession-errors spamming with pixel errors though
[11:34] <MCR> seb128: renaming the whole autostart folder did not help (although I found quite a lot of deprecated symlinks there (moved from old system))
[11:34] <MCR> seb128: yes.
[11:34]  * sil2100 sighs
[11:34] <seb128> ok :-( I was hoping the autostart stuff would have to do with it
[11:34] <sil2100> Even though I dragged the black panel, the launcher still appears on my big screen
[11:35] <didrocks> sil2100: what does xrandr tells you?
[11:35] <didrocks> which one is your primary monitor?
[11:36] <seb128> MCR, btw who do you "reinstall unity"? you should be able to install i.e gnome-session-fallback and gnome-panel and log into a gnome classic session
[11:37] <MCR> seb128: If you mean how: sudo apt-get install unity / sudo apt-get remove unity
[11:37] <seb128> MCR, no, I mean "why"
[11:37] <seb128> you should be able to pick a gnome classic session on lightdm
[11:37] <seb128> MCR, can you pastebin your current .xsession-errors?
[11:37] <MCR> seb128: AFAIK all other DEs work here - just Unity (the one I want to use) does not. :(
[11:38] <seb128> MCR, does it work in a guest session?
[11:38] <MCR> seb128: did not try that - I will first post the actual .xsession-errors file.
[11:39] <sil2100> didrocks: the laptop screen is listed first, so it seems to be the primary one
[11:39] <sil2100> Which is good, since I wanted it to be like that
[11:39] <sil2100> But the launcher still appears on the monitor
[11:39] <didrocks> so, maybe you need tsdgeos, Saviq to look at this ^
[11:39] <didrocks> sil2100: I guess you logout/login after the change?
[11:39] <Saviq> sil2100, where is it "listed first"?
[11:39] <sil2100> didrocks: I did, but maybe a reboot I should try?
[11:40] <sil2100> Saviq: in xrandr
[11:40] <Saviq> sil2100, why aren't you using g-c-c?
[11:40] <didrocks> shouldn't, apart from nvidia, changing the primary monitor is instant IIRC
[11:40] <sil2100> Saviq: I set it with g-c-c
[11:40] <sil2100> And g-c-c also says the laptop is the primary one
[11:40] <sil2100> But the launcher still appears on my monitor
[11:41] <Saviq> sil2100, can you try changing the geometry? move monitors a bit or change their resolutions?
[11:42] <sil2100> Saviq: changing positions and geometry works, but still launcher is on the same place
[11:42] <sil2100> I even tried killing and restarting unity-2d-shell
[11:42] <Saviq> sil2100, log out and back in, please
[11:42] <Saviq> sil2100, I did get something similar when my display setup got condused
[11:43] <Saviq> *confused
[11:43] <Saviq> sil2100, the "listed first" in xrandr doesn't really say anything, afaik
[11:43] <sil2100> I'll reboot even
[11:44] <MCR> seb128: Now I also changed the window theme to ambience also.
[11:44] <MCR> seb128: because the win theme was also causing errors
[11:44] <seb128> does it make any difference?
[11:44] <MCR> seb128: Not tried yet
[11:45] <seb128> MCR, you should try a guest session to see if that works
[11:45] <MCR> seb128: How can I start a guest session ?
[11:45] <MCR> hehe
[11:45] <seb128> MCR, pick "guest session" on the lightdm login scren
[11:45] <seb128> screen
[11:47] <MCR> I have to remove autologin first, moment
[11:49] <sil2100> Still the same, sadly
[11:49] <MCR> seb128: Is changing autologin-guest to true in lightdm.conf enough ?
[11:49] <sil2100> g-c-c says laptop is primary, but launcher prefers the monitor
[11:49] <seb128> MCR, ?
[11:50] <seb128> MCR, no, just don't autologin, you will get the lightdm screen on boot and you can choose an user and session from there
[11:50] <sil2100> Maybe I need to change something in amdccle?
[11:50] <MCR> seb128: http://pastebin.com/n2YtUtvd
[11:51] <seb128> MCR, just delete all the autologin- lines
[11:51] <didrocks> Saviq: greyback|lunch: ^
[11:51] <MCR> this is my lightdm.conf - what should I change to disable autologin - okay, thx - can I comment them out also (with #) ?
[11:51] <seb128> MCR, yes
[11:51] <MCR> ok, thx
[11:52] <Saviq> sil2100, damn, we didn't have ATI to test on :/
[11:52] <MCR> saved
[11:53] <MCR> reinstalling Unity... <- it is my running gag
[11:53] <MCR> rebooting
[11:53] <Saviq> tsdgeos, ideas ^ ?
[11:53] <Saviq> tsdgeos, we need a small app to query / print screen setup
[11:53] <Saviq> tsdgeos, let me take care of that
[11:55] <tsdgeos> Saviq: sorry, was away
[11:55] <Saviq> tsdgeos, no worries
[11:55] <tsdgeos> Saviq: basically something that loops QDesktopWidget ?
[11:55] <Saviq> tsdgeos, yeah, doing that
[11:55] <tsdgeos> okidoki
[11:59] <Saviq> tsdgeos, QDesktopWidget::primaryScreen()? wtf?
[12:00] <tsdgeos> wops
[12:00] <tsdgeos> how did we miss that?
[12:00] <Saviq> tsdgeos, I was sure 0 is the primary screen
[12:01] <tsdgeos> seems its not :D
[12:01] <didrocks> Saviq: ah no, I confirm it's not in any case :)
[12:01] <didrocks> Saviq: normally, the number remains the same once a monitor is "tagged"
[12:01] <tsdgeos> didrocks: well, 0 in Qt terminology
[12:01] <tsdgeos> which always goes from 0 to N
[12:02] <didrocks> ok, maybe not mapping the other APIs then
[12:05] <sil2100> Session restart
[12:08] <sil2100> Still the same problem, but at least I can get better screen resolutions when modifying some things in amdcccle
[12:16] <phoenix560> Hello I am phoenix560
[12:17] <phoenix560> this is my first time using IRC so please forgive my inexperiance
[12:17] <MCR> seb128: I think I have to give up now - starting a guest session worked, but started Ubuntu-2d although it was not even fully installed and I chose Ubuntu as session.
[12:18] <sil2100> Hello phoenix560
[12:18] <seb128> MCR, ok
[12:19] <sil2100> Saviq: any leads regarding the primary monitor problem? Is it something wrong on my side or in unity-2d?
[12:19] <Saviq> sil2100, read #dx
[12:19] <Saviq> sil2100, sorry, pasted there
[12:20] <MCR> seb128: Now I've installed ubuntu-2d and this at least worx, so thanx again 4 your time - at least I learned some stuff about lightdm & co ;)
[12:22] <seb128> MCR, yw, your way to uninstall and reinstall unity is really inefficient ;-)
[12:22] <seb128> usually you can just log out and in
[12:23] <MCR> seb128: Still do not know how to logout without DE...
[12:23] <seb128> MCR, ctrl-alt-del should work
[12:23] <seb128> it should open the gnome-session logout dialog
[12:23] <MCR> seb128: yes it does :)
[12:23] <seb128> or power button maybe, that should also display a dialog
[12:37] <Klap-in> i try to debug something in the compiz wall-plugin. so i add some printf(), this out put to 'stdout' now it appears in .xsession-errors. but not directly It seems needed that happens something before it appears. Do i observer the correct log?
[12:38] <Klap-in> *observe
[12:40] <greyback> MCR: you may be able to log-out by hitting Ctrl+Alt+T to bring up a terminal, and then enter "gnome-session-quit"
[12:42] <greyback> Klap-in: you should see if if you run compiz from a shell with "compiz --replace"
[12:51] <Klap-in> greyback: thnx
[13:24] <rye> hello, I am experiencing bug #943851 again on the latest system, is compiz-core task the one that should have fixed it?
[13:32] <Daekdroom> Is the global menu now supposed to never hide?
[13:32] <Daekdroom> Ah. Nevermind, now it's working alright.
[13:38] <Klap-in> i have a fix for the compiz wallplugin. What is the preferred way to supply this?
[13:58] <cr3> is there a proper place to run commands when a xsession is started, that I used to have in my ~/.xsession file: setxkbmap -layout us,ca -option grp:alt_shift_toggle
[13:58] <didrocks> greyback: I'm seeing some regressoins with hide-mode = 0 as well
[13:58] <Zhenech> cr3, ~/.xinitrc?
[13:58] <didrocks> taking a picture
[13:59] <greyback> didrocks: please do
[14:00] <seb128> cr3, why not just configuring your keyboard with those layout in the system settings dialog?
[14:00] <hallyn> hi - super-up isn't working for me, and the dash overlay still says alt-f10 is fullscreen (but that doesn't work any more)
[14:01] <cr3> seb128: because I'm a curmudgeon, but I'll give that a try
[14:02] <didrocks> greyback: http://people.canonical.com/~didrocks/unity-2d-multimonitor.png
[14:02] <didrocks> greyback: multiples thingss here
[14:03] <didrocks> greyback: the primary monitor is the left one
[14:03] <didrocks> greyback: the STRUT works for windows here (if I maximize them, they go alongside the panel)
[14:03] <didrocks> greyback: however, nautilus icons are not moved (as they are when you set your STRUT)
[14:03] <didrocks> greyback: though, the second monitor has a STRUT set as well, see the maximized terminal leaving a space for the launcher
[14:04] <greyback> didrocks: yeah I see that
[14:05] <greyback> didrocks: yes both are problems, leave them with me
[14:05]  * didrocks hands off :-)
[14:05] <greyback> I can't reproduce your useless strut-on-second-monitor tho
[14:05] <didrocks> wondering if it's not related to nvidia?
[14:05] <greyback> no actually I just have
[14:06] <hallyn> i need to get a second monitor so i can be cool
[14:06] <didrocks> ah :)
[14:20] <cr3> didrocks: regarding multimonitor, either 2d or 3d, is there something planned so that when you full screen an application on one monitor, the file/edit/etc. menus don't appear on the first monitor?
[14:20] <cr3> I haven't tried multimonitor in a long time, but it's one of the pain points I often hear when talking with people in the community
[14:24] <didrocks> cr3: yeah, the appmenu shouldn't appear on the other monitor
[14:24] <didrocks> cr3: it's a logged bug
[14:25] <cr3> didrocks: does it planned to be fixed in precise?
[14:25] <didrocks> cr3: well, it's on the priority list, not high on it though as it's minor compared to other issues we have
[14:26] <cr3> didrocks: I understand, I'll keep my fingers crossed then
[14:26] <mhall119> didrocks: I created 2 FF3 bugs for updates to unity-singlet and quickly-unity-lens-template, is there something you can do to promote them?
[14:26] <didrocks> cr3: better to do :)
[14:26] <mhall119> s/FF3/FFe/
[14:26] <didrocks> mhall119: please ping the release team members
[14:26] <cr3> didrocks: yeah, but I also have "other issues" :)
[14:26] <didrocks> mhall119: it's the fatest way to get them accepted :)
[15:31] <Klap-in> i have a fix for the compiz wallplugin. What is the preferred way to supply this and to get it accepted in 12.04(if possible..)?
[15:51] <JackyAlcine> Klap-in: I'm guessing that a reporting a bug to the compiz package related to Unity and then providing a diff there would be useful.
[16:17] <Klap-in> JackyAlcine: ok. it's now reported to compiz, and the its wallplugin. So it's helpfull to add unity too?
[16:19] <JackyAlcine> Yup, since it's Unity-specific.
[16:19] <JackyAlcine> These are suggestions, though.
[16:20] <JackyAlcine> Report back to this channel occasionally to mention the bug and try poking it at the mailing list.
[17:51] <kenvandine> Trevinho, ping
[17:51] <Trevinho> kenvandine: pong
[17:51] <Trevinho> hi
[17:52] <kenvandine> Trevinho, what do you know about time stuff in vala?
[17:52] <kenvandine> like converting gmt and handing DST
[17:52]  * kenvandine found a patch from Trevinho doing a google search :)
[17:53] <Trevinho> Mhmh... Which one? I don't recall thatt...
[17:53] <kenvandine> it wasn't specifically that, but it changed some code that did some timestamp stuff
[17:53] <kenvandine> it was for freesmartphone or something
[17:54] <kenvandine> anyway...
[17:54] <kenvandine> Time.gm (time_t ()) gets the right utc time
[17:54] <kenvandine> but
[17:54] <kenvandine> Time.gm (time_t ()).mktime () gets a timestamp that is off by 1 hour
[17:54] <kenvandine> only when on DST
[17:54]  * kenvandine was just hoping you had any idea how to hack around that
[17:55] <Trevinho> Mh I don't think it was actuyally my code... Maybe I only stored on my git...
[17:56] <kenvandine> perhaps :)
[17:56] <Trevinho> Anyway... I'm not too much into that now, sorry :/
[17:56] <kenvandine> Trevinho, ok... so you don't know?
[17:56] <kenvandine> ok, no problem
[19:09] <PaoloRotolo> Hi all!
[20:48] <rasmushaglund> hi, I'm about to try to add a few features to unity and have started to get familliar with the code. But I've got stuck trying to find how the menu triggered by right clicking a window is created.
[20:48] <rasmushaglund> Could anyone point me in the right direction?
[20:49] <rasmushaglund> I've found the code for creating menus, but not where it actually instanciates that menu.
[20:50] <rasmushaglund> My goal is to add that menu so that it works even when maximized
[20:51] <rasmushaglund> right clicking the title menu bar that is
[20:57] <JackyAlcine> Sahweet. :)
[21:08] <thumper> rasmushaglund: what is your plan exactly?
[21:19] <rasmushaglund> thumper: my plan is to grasp the general structu4
[21:19] <rasmushaglund> ops
[21:20] <rasmushaglund> my plan is to grasp tHe general structure, so that I can find where I should start
[21:21] <rasmushaglund> and I figured that I start with a feature that sounds simple enough for me to implement
[21:23] <rasmushaglund> so when a window is floating you can right click the window panel and choose, for example, "move to desktop x". But when the window is maximized, and the window panel is part of the top unity panel you cannot right click to invoke the menu.