[01:55] ARGH: http://seclists.org/oss-sec/2012/q1/191 [02:00] Win? [02:01] mdeslaur: Given that we're preparing to upload a 1.11-based server to Precise I guess that should be considered a blocker? :) [02:01] control-alt-...multiply? [02:02] oh whoa...that's awesome. can we please, please at least keep that in hidden under an xorg.conf option? :) [02:03] It looks like it *should* require you to explicitly add those keybindings. [02:06] We should at least have prgrabs available. [03:23] If I press reset default in compizconfig-settings-manager I would expect that I would get back what Ubuntu has on install. [03:28] I believe the correct rune would be ‘unity --reset’ [03:28] I'm not sure that ccsm's reset button does the right thing. [03:34] RAOF: ah thanks [03:35] If that doesn't work I saved a snapshot just before testing a bunch of old bugs from our internal bugzilla. [03:36] :) [03:50] ROAF: so, xmodmap gives me this: keycode 63 = KP_Multiply XF86ClearGrab KP_Multiply XF86ClearGrab [03:51] ROAF: that means it's binded, right? [03:51] was anyone able to reproduce it? [03:56] RAOF: unity --reset seems to do the trick. [04:02] ah! it's in 1.11 [04:02] ROAF: yes, that would be a blocker for the 1.11 upload :) [04:08] mdeslaur: Yes, I think that means it's bound. [04:09] Ok. One more thing added to the 1.11 queue :) [04:18] RAOF, I think I *might* have an MT version of synaptics tomorrow :) [04:18] cnd: Cool! [04:18] just fyi [04:19] it seems to be working here, but it's a bunch of spaghetti commits that I need to untangle [04:19] and then port as patches in a dpkg [04:19] if nothing bad turns up, I'd rather get this in to the push to precise [04:20] hopefully I'll be faster than qt4-x11 on armel with a 24 hour head start :) [04:20] :) [04:20] Ok. [04:21] I'm doing some work for DX right now, and then we need to ensure we're not bitten by the security bug mdeslaur pointed out. Then I think we're ready to do some upgrade testing. [04:42] RAOF, development releases don't really need to have 0 security bugs :) [04:42] cnd: Right, but it would be nice to not have lockscreens be trivially bypassable. [04:42] psh [04:42] And it seems like it should be reasonably easy to fix & verify :) [04:43] I just realized that the qt patch will need a small fix so MT events from touchpads come through too... [04:43] I think that fix can wait till after the push though [04:44] it doesn't cause a crash or anything, it merely doesn't emit any touch events [04:45] Yeah, sounds fair enough. [06:26] ARGH! GIT SEND EMAIL! [06:27] Why is your default behaviour to throw away my message when I mistype the smtp password the first time? [12:56] RAOF: there's a patch available on the xorg security list [12:56] debian has disabled it in git already [12:56] either works [12:57] s/git/sid/ :) [12:57] oh ok :) [12:57] of course [13:29] jcristau, hi [13:29] ? [13:29] jcristau, could you take a look at this http://people.ubuntu.com/~ricotz/g-c-c/ [13:30] this is suppose to be a libx11 bug [13:30] i am not sure who can drag this upstream [13:30] what am i supposed to be looking at? [13:30] ickle already looked at it and blames libx11 or deeper [13:31] jcristau, at the valgrind log [13:31] it seems it is using an uninitialized mutex [13:32] this is running libx11 1.4.4, but i will try to confirm it with 1.4.99.1 [13:33] well, look at the source? [13:33] shouldn't be hard to find out [13:33] right, i was hoping someone with more insights could look at it [13:34] which made me pinging you ;) [13:35] what's needed is not insight, it's an xlib checkout and vim... [13:36] alright, i have both [13:56] ricotz: do you call XInitThreads before any other xlib function btw? [14:11] jcristau, i dont know [14:11] because afaict NewDatabase does _XCreateMutex, which does pthread_mutex_init [14:11] but it looks like NULL isnt handled properly here [14:12] "here"? [14:12] right, but if the creation fail db will be NULL [14:12] in NewDatabase [14:13] seems unlikely to be your issue [14:15] but could be [14:15] XrmCombineDatabase handles the null case [14:17] http://people.ubuntu.com/~ricotz/g-c-c/gnome-control-center.log says db=0x555555936cc0 [14:17] hmm, right === JanC_ is now known as JanC [16:11] RAOF, micahg asked that we contact the security team before uploading 1.11 [16:11] I told him you were on top of things [17:21] Who do I need to by a truckload of beer to get a option in ccsm/unity to turn of the menus on top bar? [17:21] buy* [17:26] Prf_Jakob: just deinstall appmenu-gtk & appmenu-gtk3 [17:27] and appmenu-qt if you have it [17:27] or edit /etc/X11/Xsession.d/*appmenu* === yofel_ is now known as yofel [20:00] * JanC wants menus in the top bar for maximized windows but not for other windows ;) [20:15] JanC: that be pretty pimp actually. [20:20] Prf_Jakob: it's mostly about usability for me; for maximized windows it maximizes them more, but for normal windows it doesn't make me travel half around the world to find an application's menu ;) [20:21] JanC: tell me about it I have 30" monitor. [20:22] mine is only 22", but still at "Full HD" resolution... === chrisccoulson_ is now known as chrisccoulson