=== jalcine_ is now known as jalcine
[01:07] <valdur55> Hello. how can i port systray icons to appindicator icons ?
[01:11] <jalcine> valdur55: you using Qt?
[01:12] <jalcine> If so, make sure your application depends on sni-qt (status notification indicator)
[01:12] <jalcine> It'll appear as an indicator.
[01:12] <valdur55> gtk
[01:12] <jalcine> O.O
[01:12]  * jalcine awkward.
[01:12] <jalcine> I'm not sure, more of a Qt buff :)
[01:13] <jalcine> Actually, I think that libappindicator is written using GTK.
[01:13] <jalcine> It'd be merely rewriting your systray code to it.
[01:21] <valdur55> jalcine, ok. but where i should put appindicator icons ?
[01:21] <jalcine> The code itself or the indicator itself?
[01:21] <jalcine> The indicators place themselves in the panel.
[01:23] <valdur55> jalcine, :) yea, i know it. but where is correct image path ?
[01:24] <jalcine> That, I'm not sure of.
[01:28] <valdur55> jalcine, radiotray main GUI is systray/appindicator menu.
=== jalcine is now known as JackyAlcine
=== JackyAlcine is now known as jalcine
=== smb` is now known as smb
[09:01] <davidcalle> mhr3, ping
[09:01] <mhr3> davidcalle, pong
[09:02] <davidcalle> mhr3, I would need you for a couple of things on the rb scope.
[09:02] <mhr3> davidcalle, sure, what do you need
[09:03] <davidcalle> mhr3, the filters and the max number of items displayed
[09:03] <davidcalle> mhr3, then it should be good to go
[09:04] <mhr3> davidcalle, as for filters, you need to add stuff into the model which represents the filtered properties
[09:05] <mhr3> then you can just filter out the items that don't matches the filters (after the search is done)
[09:05] <davidcalle> mhr3, I've added the genre in the dee model we search on.
[09:05] <mhr3> yea, good
[09:05] <didrocks> hey davidcalle!
[09:05] <didrocks> davidcalle: how are you?
[09:05] <davidcalle> didrocks, good, and you ?
[09:05] <didrocks> davidcalle: I'm fine thanks!
[09:06] <didrocks> davidcalle: about the rhythmbox scope, when do you think it will be ready?
[09:06] <mhr3> davidcalle, and basically you can do the same for the max results - keep a counter in the final loop that is adding stuff to the model and when you reach the limit, just break from the loop
[09:06] <didrocks> davidcalle: beta2 freeze is thursday, would be good to have something for it
[09:07] <mhr3> davidcalle, anything unclear?
[09:08] <davidcalle> mhr3, indeed, but I still have trouble doing these simple things in Vala and something that would take you ten minutes will take me two hours, but if you don't have the time, that's fine :)
[09:09] <didrocks> mhr3: do you think you can take some time to help davidcalle so that we get the scope for tomorrow freeze? ^
[09:10] <mhr3> yea
[09:12] <didrocks> thanks mhr3 ;)
[09:23] <didrocks> greyback: hey, good morning!
[09:29] <greyback> didrocks: greetings!
[09:29] <didrocks> greyback: hey hey ;) waiting to know where we are at with the multimonitors issues we saw on thursday?
[09:29] <greyback> didrocks: fyi I've a small metacity patch to test
[09:30] <didrocks> ah, metacity :)
[09:30] <greyback> which should fix the nautilus icons-under-launcher problem
[09:30] <didrocks> greyback: didn't really see merges related to fixes on unity-2d (the other on the monitor position on nvidia and fglrx), I maybe missed it :)
[09:30] <greyback> didrocks: yes, more bull due to NET_WORKAREA being crap
[09:30] <didrocks> greyback: great! fire on! :)
[09:31] <greyback> didrocks: nvidia, Saviq just couldn't reproduce. He's adamant that there's always a primary monitor set.
[09:32] <greyback> didrocks: I met get him to chat to you about it
[09:32] <Saviq> didrocks, let me know if you can reproduce and the steps
[09:32] <didrocks> greyback: link for the metacity merge?
[09:32] <Saviq> didrocks, but we never got anything else than 0 for Primary (on all the different systems we tested)
[09:32] <greyback> didrocks: fglrx, driver sucks, you cannot set the primary monitor.
[09:33] <didrocks> Saviq: on nvidia:
[09:33] <greyback> didrocks: none just yet, I need to test locally before pushing
[09:33] <didrocks> - have two monitor set with monitor on the right, laptop screen on the left
[09:33] <Saviq> didrocks, when I "deselected" the primary monitor on nvidia-settings, the other got selected as primary,
[09:33] <Saviq> is that not the case for you?
[09:34] <didrocks> - on nvidia-settings ensure none are selected as primary monitor
[09:34] <didrocks> Saviq: hum, I got a case when none was selected
[09:34] <didrocks> let me check
[09:35] <didrocks> ok, I can't get back to the case of both unselected :/
[09:35] <Saviq> good :)
[09:35] <didrocks> what about fglrx, it's not possible to set a primary monitor?
[09:36] <Saviq> yes, it seems it doesn't care what you do
[09:36] <Saviq> didrocks, sil2100 knows more
[09:37] <didrocks> hum… that's kind of anyone then
[09:37] <didrocks> let's see with him and did you talked with the 3d guys?
[09:37] <didrocks> they probably had the same issue
[09:37] <didrocks> (dbo will know more)
[09:38] <greyback> didrocks: that's something I didn't do. I checked their code, they just choose the primary monitor. But I'll ask in case they do something fancy
[09:38] <greyback> s/choose/use/
[09:40] <didrocks> greyback: thanks!
[09:40] <didrocks> greyback: so, once the metacity is here and I confirm it works
[09:40] <didrocks> we probably can release
[09:40] <greyback> didrocks: sweet
[09:40] <didrocks> (saw that some additional commits got it, they are safe?)
[09:41] <greyback> didrocks: they are, one strut fix for the bug you noticed, couple of RTL fixes too
[09:42] <didrocks> ok :)
=== fenris is now known as Guest97336
[10:16] <greyback> sil2100: hey, with the ATI driver problems we had with primary monitor setting, if you have a minute can you check that <primary> is being set correctly in ~/.config/monitors.xml
[10:17] <sil2100> greyback: sure thing, just one moment - since right now I'm using a single monitor only
[10:17] <greyback> sil2100: no rush, just good to confirm it
[10:21] <sil2100> Ok, need to restart the session
[10:21] <sil2100> One moment
[10:25] <sil2100> greyback: what should I look for in that config? Since it seems to be correct, as the laptop screen (the one I set as primary) is on the first position
[10:26] <greyback> sil2100: in the Displays panel, could you drag the panel to the non-laptop screen
[10:27] <greyback> sil2100: check the config file is correct. Then reboot and check again
[10:27] <greyback> sil2100: log out/in again is enough, no need to reboot
[10:31] <sil2100> greyback: ok, it seems to change the "primary" property correctly, but the Launcher is still on the same monitor everytime
[10:32] <greyback> sil2100: ok, it's definitely the driver that's just not doing anything when we ask it to switch the primary monitor
[10:32] <greyback> sil2100: thank you for confirming that for me
[10:33] <sil2100> greyback: I noticed one strange thing when I was on unity 3d though
[10:34] <greyback> sil2100: go on
[10:34] <sil2100> greyback: when I was switching the primary monitor in the Displays panel, I noticed that my mouse cursor - after pressing Apply - was changing screens according to what I set as the primary screen
[10:35] <sil2100> greyback: i.e. when I set the laptop screen as primary, my cursor was teleported to the laptop screen
[10:35] <sil2100> greyback: so hm...
[10:35] <greyback> sil2100: hmmm.
[10:35] <greyback> I've no idea :)
[10:36] <greyback> perhaps compiz listens for the screen changes and moves cursor around to suit
[10:37] <greyback> But for now, I see nothing obvious we can do to work around this issue
[10:37] <sil2100> Could be, but then maybe you could hook up to that in unity-2d?
[10:38] <greyback> sil2100: I'll have look at compiz to see if it's doing something clever
[10:40] <greyback> sil2100: thanks for the help, I'll ping if I need anything
[10:40] <sil2100> greyback: thanks!
[11:40] <Klap-in> hi, recent i fixed a issue in the wall-plugin of compiz and added a diff. Bug #904205 Can i ask somebody to include it in 12.04? or what the way to go?
[11:40] <ubot5> Launchpad bug 904205 in Compiz "Desktop wall: Bindings for next/previous don't work." [Medium,Confirmed] https://launchpad.net/bugs/904205
[11:43] <rye> Hello, regarding the thumb for the scrollbars - if you move window far to the left, the thumb appears inside the window, but cannot be grabbed
=== MacSlow is now known as MacSlow|lunch
[12:03] <didrocks> greyback: hey, any progress on metacity? :)
[12:03] <greyback> didrocks: yep, just fighting with dpkg :)
[12:04] <greyback> didrocks: https://code.launchpad.net/~gerboland/metacity/workarea_fix
[12:04] <didrocks> greyback: thanks :)
=== _salem is now known as salem_
[12:14] <rye> is current unity using Alt+F10 too/
[12:15] <rye> unity2d - yes, unity - seems yes too, from ppa
[12:15] <sil2100> rye: yes, at least it should
[12:15] <rye> pressing Alt+F10 twice renders keyboard and mouse input impossible
[12:15] <didrocks> greyback: so, the icon are now shifted \o/
[12:15] <rye> sil2100: if you try, to revert - unity --reset in terminal only :(
[12:15] <didrocks> greyback: however, the fix for "on the second monitor, maximizing an application takes the STRUT" is in unity-2d?
[12:16] <didrocks> rye: compiz is bad at dealing with configuration upgrade
[12:16] <greyback> didrocks: yes. We forgot to remove all other struts when using 1 launcher
[12:16] <rye> didrocks: well, alt+f10 is indeed set in the preferences, and it works, however pressing Alt+F10 twice made me want to smash the keyboard, which does not appear to fix the issue
[12:17] <sil2100> rye: the thing you described is a bug that happened in the past when alt is still pressed and f10 more times than one - not sure if it was fixed or not
[12:17] <sil2100> I think I saw a bug for that, need to look for it
[12:17] <sil2100> (since it's rather serious)
[12:17] <didrocks> greyback: let me grab trunk
[12:18] <rye> sil2100: i am also tracking the gtk bug https://bugzilla.gnome.org/show_bug.cgi?id=661973 which makes terminal receive both F10 key and pop up the menu...
[12:18] <ubot5> Gnome bug 661973 in gtk "gtk+ reacts on F10 press incorrectly with xkeyboard-config-2.4.1" [Major,Unconfirmed]
[12:20] <rye> aha, looks like bug #948522
[12:20] <ubot5> Launchpad bug 948522 in unity "Alt-F10 locks up Unity" [High,Confirmed] https://launchpad.net/bugs/948522
[12:32] <didrocks> greyback: no more STRUT on unity-2d trunk here with hide-mode 0
[12:33] <greyback> didrocks: you mean there's a launcher but it has no strut?
[12:33] <didrocks> greyback: right
[12:33] <didrocks> greyback: sorry, there is some STRUT
[12:33] <didrocks> but nautilus isn't respecting it again
[12:35] <greyback> didrocks: can you give me steps to reproduce?
[12:35] <didrocks> greyback: hum, no real steps for that
[12:36] <didrocks> "start unity-2d"
[12:36] <didrocks> "ensure hide-mode is 0"
[12:36] <didrocks> "check that nautilus icon are still under the launcher"
[12:36] <didrocks> can restart my session if you think that's a transient issue
[12:37] <greyback> didrocks: would you mind? I'm not reproducing it here
[12:37] <didrocks> ok, one sec
[12:41] <didrocks> greyback: confirmed, getting the issue with unity-2d trunk
[12:41] <greyback> didrocks: I think I know what's happening. Can we mumble?
[12:41] <didrocks> sure
[12:44] <greyback> didrocks: good old Mumble :)
[12:54] <didrocks> multiple launchers work fine
[12:54] <didrocks> pushing the release then :)
[12:54] <greyback> yay!
[12:54] <didrocks> nice work!
[13:02] <Klap-in> Who can give some advice? recent i fixed a issue in the wall-plugin of compiz and added a diff. Bug #904205 . Can i ask somebody to include it in 12.04? or what is the way to go?
[13:02] <ubot5> Launchpad bug 904205 in Compiz "Desktop wall: Bindings for next/previous don't work." [Medium,Confirmed] https://launchpad.net/bugs/904205
=== greyback is now known as greyback|lunch
=== MacSlow|lunch is now known as MacSlow
[13:41] <didrocks> Klap-in: try to ping sam (smspillaz) or duflu when they are around
[13:42] <didrocks> Klap-in: australian time most of the time
=== greyback|lunch is now known as greyback
[13:56] <MCR1> Klap-in: Please do more :)
[14:07] <Klap-in> MCR1: i will try :) sofar my understanding of c++ is basic, but it's to do :)
[14:08] <MCR1> Klap-in: Great news :) I would be very happy if someone could fix Emerald compilation for Precise as it is not working anymore...
[14:08] <MCR1> Compiz is not Compiz anymore without Emerald ;)
[14:10] <Klap-in> MCR1: but that's an extra decorator beyond compiz?
[14:12] <MCR1> yep, but it was made to accomplish compiz
[14:13] <MCR1> git clone git://anongit.compiz.org/fusion/decorators/emerald
[14:15] <MCR1> Klap-in: it would be really nice if you could take a look at it - probably a minor issue
[14:15] <MCR1> :)
[15:39] <bilal|web> seb128: there?
[15:40] <seb128> bilal|web, sort of, why?
[15:40] <bilal|web> seb128: I nedeed further clarification on bug #955147, and whether design decisions should be a blocker for freeze exceptions
[15:40] <ubot5> Launchpad bug 955147 in unity (Ubuntu) "[FFe, UIFe] Automatically add launchers for newly installed applications" [Undecided,New] https://launchpad.net/bugs/955147
[15:42] <bilal|web> rather, shouldn't the design team be left off to ponder over it?
[15:42] <bilal|web> (that has already been approved by designers, btw)
[15:43] <seb128> bilal|web, don't ask me, but yeah, something to deal between design team and release team
[17:10] <Andy80> om26er: cool :) (faster here than on Twitter :D )
[17:14] <om26er> Andy80, ;-)
=== yofel_ is now known as yofel
[20:41] <thomi> mhall119: ping?
[20:41] <mhall119> thomi: pong
[20:42] <thomi> mhall119: Hi - I tried to get in touch last week, but forgot about timezones ;) - we were going to talk about the best place to put tutorials / documentation relating to the testing effort in Unity (autopilot)
[20:42] <mhall119> thomi: yes!
[20:43] <thomi> It'd be super-cool to have the documentation at the point where people from outside the unity team / canonical can contribute autopilot tests for unity
[20:44] <mhall119> thomi: can you view https://docs.google.com/a/canonical.com/document/d/14G-BDOxb6h9jI9DADHEC74Hhv6fp0yMk-4c8LmSiYGY/edit?authkey=CJbH-OUB ?
[20:45] <thomi> mhall119: yep, once I fight with google's multiple-signon stuff :)
[20:45] <mhall119> blegh
[20:45] <mhall119> thomi: I can invite your main google email to it, if that helps
[20:45] <thomi> mhall119: I'm in now
[20:46] <mhall119> cool
[20:46] <mhall119> thomi: so this is what I'll be working on this week
[20:46] <mhall119> I already did the design section, thanks to JohnLea's blog about the steps in the design process
[20:46] <mhall119> I was going to start writing the coding page next, using the docs we collected for developer.u.c
[20:47] <mhall119> I suppose writing autopilot tests should be in there
[20:47] <thomi> OK, I guess autopilot falls under "Coding" rather than "Testing", since some python experience is required?
[20:48] <mhall119> yeah, Testing was really going to be about how to run existing tests and provide feedback
[20:49] <thomi> ok. When do these changes go public? Is this something for the 12.04 release?
[20:49] <mhall119> thomi: yeah
[20:49] <mhall119> the current target publish date is "as soon as we finish writing them"
[20:50] <mhall119> developer.u.c docs are mostly done, but unity.u.c docs are just starting
[20:53] <mhall119> thumper: dbarth: you guys might be interested in this, I'm trying to get meaningful stats from the unity, unity-2d and nux bzr branches:
[20:53] <mhall119> Total Committers: 119
[20:53] <mhall119> Internal: 14772 commits from 45 people
[20:53] <mhall119> External: 794 commits from 74 people
[20:53] <mhall119> Unknown: 12
[21:01] <thumper> mhall119: interesting
[21:02] <mhall119> thumper: http://paste.ubuntu.com/891299/ is the script if you're curious
[21:02] <mhall119> thumper: any member of one of the "unity_teams" is considered an Internal contributor
[21:03] <mhall119> if you know of a more accurate set of teams, let me know and I'll update it
[21:04] <mhall119> sadly it counts contributions from current employees as Internal, even if they were hired after some of those contributions were made
[21:04] <mhall119> so it's a bit skewed in favor of Internal
[21:12] <htorque> hi all! can you tell me whether 6 million invalid writes of size 1 in one hour from compiz/unityshell are a problem: http://paste.ubuntu.com/886919/ sounds like a lot.
=== salem_ is now known as _salem
[22:51] <bilal> When is the merge window for new features in Unity 5.8 closing?
=== Jens is now known as Guest5079
[23:43] <htorque> Trevinho: hi! bug 938082 - what version of unity are you running? i'm on 5.6.0-0ubuntu4 and about to re-test.
[23:43] <ubot5> Launchpad bug 938082 in unity (Ubuntu Precise) "Multi-monitor: indicators acting up when second monitor disconnected with indicator opened" [High,Triaged] https://launchpad.net/bugs/938082
[23:52] <htorque> Trevinho: great, i'm too not able to reproduce it. :-)