[06:23] sforshee: Ok. I'm not entirely sure why libgnome-desktop is trying to use the "ConnectorType" property, because it's a filthy lie; nothing implements it, and I see no reason to expect it to be implemented in the near future (unless we want to; it couldn't be *that* hard ☺) [06:23] sforshee: Patch libgnome-desktop away! [07:41] tjaalton: which bot is normally here? [07:42] ahh looks like ubot4. [07:42] jussi: can't recall, but sounds familiar-ish [07:44] bug 933710 [07:44] Launchpad bug 933710 in xserver-xorg-video-intel (Ubuntu Precise) "Laptops with eDP panels do not suspend when lid closed" [Critical,Confirmed] https://launchpad.net/bugs/933710 [07:44] yeah, works [07:44] yup, of course it does :D [07:44] but when the other one comes back it will double up on things, so one needs to be removed [07:44] so how to kill it? [07:45] grab a memeber of the irc council, mithrandir or a freenode staffer and get it quieted. or grab me or tsimpson and we will remove one. [07:46] also, you peoples dont have operators in here - you really need to fix that. [07:46] ok cool [07:46] .) [07:46] :) [07:46] * jussi writes mail. [07:46] yeah don't think we've ever had [07:47] my memory goes back 5y [07:47] tjaalton: who are the people here who could do that - I assume they arent needed a lot anyway. but a few is a good idea to have. [07:47] jussi: me, bryceh, RAOF, Sarvatt, cnd for instance [07:48] ok, Ill zap one of the ircc and get things sorted. [07:48] maybe some of the more active community ones too [07:48] thanks! [07:54] tjaalton: Mithrandir isnt around anymore, correct? [07:56] jussi: not working for canonical no [07:56] ok, thanks. :) [07:56] tjaalton: AlanBell will sort out the bits and peices (I am not on the IRCC anymore) [07:57] jussi: ok great to see this happen at last.. [07:57] tjaalton: I dont know why we didnt do anything about it when I was on the ircc. :/ [07:57] should be all set now (unless I messed it up) [07:58] AlanBell: any reason you missed an A on tjaalton? :P [07:58] see I said I got it wrong [07:58] :) [07:58] fixed [07:59] tjaalton: try /msg chanserv op #ubuntu-x tjaalton [07:59] \o/ [07:59] whee [07:59] tjaalton: now try /msg chanserv deop #ubuntu-x tjaalton [08:00] rocks [08:00] tjaalton: https://wiki.ubuntu.com/IRC/IrcTeam/OperatorGuide [08:00] hmm I think bryceh was there already, since he has set the topic before? [08:00] nope [08:00] ok.. [08:01] tjaalton: also, "/msg chanserv access #ubuntu-x list" will give you the full list [08:01] we will be doing some fun and interesting classes for new ops in #ubuntu-classroom soon, you might want to tag along with them [08:01] anyhow, I am off out now, laters all o/ [08:01] hmm why bryce2 not bryceh? [08:01] someone probably had the channel set -t or manually opped him [08:02] tjaalton: /msg nickserv info bryceh [08:02] ah ok :) [08:02] :) [08:03] the mysteries of irc [08:03] tjaalton: now you can set a nice topic (the current one is a bit sparse [08:03] hum :) [08:04] maybe later, can't think of a better one yet [08:04] tjaalton: also, you have ubuntulog here, and that means you need to sort out the t&c's as per here: https://wiki.ubuntu.com/IRC/Bots [08:04] AlanBell: I dont think tjaalton can actually do that because he has no s flag. [08:05] the joys of getting things up to date. [08:05] t&c's? [08:05] tjaalton: look at the link ;) [08:06] looking, but what exactly? [08:06] oh the disclaimer? [08:06] basicallyn says you need to follow the coc and the channel will be logged [08:06] sure [08:07] however, as I mentioned, I dont think you can use the set command [08:07] ok [08:08] so we have to wait for AlanBell or someone else from the ircc to sort things a little more. [08:08] anyway, carry on, glad its mostly sorted :) [08:09] yeah, thanks [09:09] tjaalton: you now have a +s flag [09:10] AlanBell: thanks [10:09] anyone else seeing an odd lensing or combing effect on the left edge of some characters on atom h/w on precise? [10:12] RAOF, how do i find out what sub-pixel layout is being used ? [10:13] this feels a little like the wrong layout is being used on my atom [10:13] or something odd === chrisccoulson_ is now known as chrisccoulson === yofel_ is now known as yofel === JanC_ is now known as JanC [21:53] bryceh, what are your thoughts on the locked drags stuff [21:55] it's hard to discern if it's a vocal minority who have a problem with it [21:56] at the same time, if I get the clickpad stuff landed, I can see easily reverting the behavior since it was simply to fix clickpads [21:56] apw: Like so many things, you've got two options. “xrandr --verbose” will tell you the subpixel ordering the hardware thinks it has, looking at /org/gnome/settings-daemon/plugins/xsettings/rgba-order will tell you what GTK thinks it is. [21:57] cnd: The locked drags stuff is the reason why alt-tab sometimes doesn't work for me, right? :) [21:57] oh wait, I thought beta 1 was tomorrow [21:57] I see it's quite a ways away [21:57] RAOF, maybe? [21:57] RAOF, no, I can alt-tab inside a locked drag [21:58] I think the way I use the trackpad I quite frequently hit the draglock; perhaps some apps take out grabs on drag? [22:03] cnd, the locked drag doesn't really do it for me, but I can imagine for some people or some use cases it may make a lot of sense [22:03] cnd, my druthers would be to have it as a non-default option [22:06] bryceh, ideally it would be a setting in the mouse prefs [22:06] unfortunately we're passed UI freeze [22:06] that's what I wanted to do originally, but ran out of time [22:07] I'll revert it hopefully as soon as the ffe is granted [22:07] cnd, ask for a UI freeze exception [22:07] bryceh, that would require me to actually find time to develop it [22:07] I haven't investigated at all, and I have other bugs that are higher prio [22:07] and a revert of this + clickpad fixes is probably the best option anyways [22:12] RAOF, were you able to easily trigger the X crash before, and if so has the update fixed it? [22:12] cnd: I was not, no. [22:13] ok [22:13] cnd: But, then again, I wasn't actually using a multitouch synaptics device :) [22:13] hmm... [22:16] Rick was hitting that, as was asac; I pointed asac at the new synaptics and it seemed to quiet him? :) [22:21] cnd, was this the crash fixed in 0ubuntu3? [22:22] bryceh, yeah [22:22] the one I told you about yesterday [22:23] right, so, turns out there's been a ton of different crash reports that have come in that seem to be solved with that [22:23] oh great [22:23] :) [22:23] still got a bunch I'm waiting on people testing, but it looks like it fixed a lot of the recent xserver crashes [22:23] cnd: hate to pester but do you have 0ubuntu3 locally and just forgot to push by any chance? :P [22:24] Sarvatt, maybe? [22:24] I did it late last night in vienna [22:24] mesa 8.0.1 looks like it'll solve another good chunk [22:24] before I slept 6 hours and flew home [22:24] Sarvatt, so I very well could have forgotten [22:24] let me make sure [22:27] bryceh: Does that include the WriteToClient weirdness? [22:28] RAOF: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/925341 no synaptics being used [22:28] Launchpad bug 925341 in xorg-server (Ubuntu) "Xorg crashed with SIGSEGV in WriteToClient()" [High,Confirmed] [22:29] Sarvatt: Quite true. Boo :( [22:29] Sarvatt, pushed [22:29] thanks for noticing that [22:30] cnd: appreciate it! updated today thinking the fix was in it [22:32] RAOF, no, we have more xserver crash bugs beyond these two :-/ [22:32] and I think the WriteToClient bug may pre-date the synaptics changes anyway, but not sure [22:33] bryceh: Oh! What version of the nvidia driver is that? DBO was seeing some corruption when using FBOs with the pre-295.20 driver that he said eventually took down the server. [22:34] that one was 295.10 [22:34] I'll have them retest, good idea [22:36] O rhythmbox why you no love? === broder_ is now known as broder