[07:47] <sil2100> didrocks: hi!
[07:48] <sil2100> didrocks: me and Mirv we've been looking into the keybinding migrations just now, and there is a small problem that we noticed
[07:50] <sil2100> didrocks: in the current state of things it seems we can't really use gsettings-data-convert for the keybindings, because it fails converting some (or even all?) keybindings
[07:50] <sil2100> didrocks: I just looked at this today, so I didn't really follow the discussion, but it seems g-d-c can
[07:50] <sil2100> ekhm
[07:50] <sil2100> Enter pressed to soon
[07:51] <sil2100> What I wanted to say:
[07:51] <sil2100> ...but it seems g-d-c can't do the conversion from type 's' to 'as'
[07:52] <sil2100> didrocks: it seems in gconf, during the conversions, the keybindings are normal strings, where the schema expects arrays of strings
[07:53] <sil2100> didrocks: not sure what we could do here - the two options I currently see are either patching g-d-c to do the conversion from 's'->'as', or just dropping g-d-c in favor of a python/bash script doing the conversions manually for keybindings
[07:53] <sil2100> didrocks: since modification of existing schemas would be more trouble
[07:57] <didrocks> sil2100: it's not new, Mirv noticed that mid-day on Friday
[07:57] <didrocks> sil2100: any news from upstream as I asked?
[07:57] <didrocks> patchin g-d-c will do it for me
[07:58] <didrocks> sil2100: btw, as told on Friday, I'm quite unimpressed that the script was outpting some warning when you tested the migration in august and that noone noticed it
[07:59] <sil2100> didrocks: what warnings? You mean the 's' -> 'as' conversion ones?
[08:00] <didrocks> yeah
[08:03] <sil2100> didrocks: I think those keybinding conversions were added a bit later, when I was just testing the packages - during my migration testing, keybindings were just broken and not converted at all
[08:03] <sil2100> At least not those
[08:03] <sil2100> But yeah, fail
[08:09] <didrocks> well, when adding them anyway, it should have been checked :))
[08:11] <sil2100> I know :( I checked the wrong thing - since I just checked the non-unity keybindings = fail
[08:14] <MCR1> duflu: Hi :) I am not sure if it is a good solution to present plug-ins to the user he will never get to work, that is why I proposed to disable them...
[08:14] <MCR1> duflu: showmouse is also broken btw
[08:15] <MCR1> duflu: and loginout is just working for KDE users, although this does not get explained to the user anywhere - it is just confusing
[08:16] <MCR1> duflu: we should at least make it depend on KDEcompat in CCSM, so that the user is warned when enabling it...
[08:16] <duflu> MCR1: It's a bug so should be discussed in a bug and be fixed, rather than disabling the code
[08:16] <duflu> I looked at the loginout code. It's not dependent on KDE, even if it does only work on KDE
[08:17] <MCR1> I have filed bug reports about that also, btw - you just don't seem to get my reports
[08:17] <duflu> MCR1: OK, please mention the bug numbers in proposals etc, or mark my bug as a dupe of yours
[08:18] <MCR1> duflu: I think every KDE user will enable KDEcompat first, so it would be logical to warn in CCSM and also to present the info that it is currently KDE only
[08:19] <duflu> MCR1: No, string changes should be permanent. And saying it only works on KDE is definitely not permanent
[08:19] <MCR1> It is frustrating for the user if he turns on plug-ins -> no warning -> no functionality at all...
[08:20] <MCR1> duflu: Do you know that showmouse is also broken ?
[08:20] <duflu> MCR1: No. Got a bug?
[08:20] <MCR1> sure
[08:21] <MCR1> bug 1048267
[08:25] <duflu> MCR1: I can't explain it but Launchpad had deleted all my direct bug subscriptions
[08:26]  * MCR1 had a problem with gmx detecting launchpad as spam and had them in the spam folder
[08:28] <duflu> MCR1: No, within Launchpad it had deleted subscriptions I created on a couple of months ago
[08:57] <tsdgeos> guys, any easy bug for a newbie to start off? ted told me to have a look at http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-tracking-bug-tasks.html bug all the compiz/unity bugs i find there seem to be a bit too difficult for someone like me that is just entering the unity/compiz land
[09:01] <duflu> tsdgeos: Maybe look through these lists:
[09:01] <duflu> https://launchpad.net/compiz/+milestone/0.9.8.4
[09:01] <duflu> https://launchpad.net/unity/+milestone/6.6
[10:11] <mhr3> bilal, ping ping ping
[13:06] <Mirv> compiz 0.9.8.2 packaging brewing at lp:~timo-jyrinki/compiz/ubuntu.0982
[13:55] <Mirv> packaging otherwise quite near complete, but have to continue on the associated gsettings-data-convert patch testing tomorrow
[13:58] <sil2100> \o/
[13:59] <sil2100> Mirv: for now let's maybe just distro-patch it for ubuntu
[13:59] <Mirv> sil2100: yes, that's what I was thinking, although also posting it to gnome bugzilla
[14:28] <Kircle> Is there anyway to add blurring to the unity launcher?
[14:46] <tsdgeos> so i created https://code.launchpad.net/~aacid/compiz/do_not_change_viewport_on_resize/+merge/123564 which fixes https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/776435 for me
[14:48] <tsdgeos> seems at least i didn't break the tests :D
[14:50] <MCR1> tsdgeos: Cool thing - a new contributor :)
[14:50] <tsdgeos> MCR1: well, just until my squad gets assigned somewhere else