[06:23] <RAOF> 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] <RAOF> sforshee: Patch libgnome-desktop away!
[07:41] <jussi> tjaalton: which bot is normally here? 
[07:42] <jussi> ahh looks like ubot4.
[07:42] <tjaalton> jussi: can't recall, but sounds familiar-ish
[07:44] <tjaalton> bug 933710
[07:44] <tjaalton> yeah, works
[07:44] <jussi> yup, of course it does :D
[07:44] <jussi> but when the other one comes back it will double up on things, so one needs to be removed
[07:44] <tjaalton> so how to kill it?
[07:45] <jussi> 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] <jussi> also, you peoples dont have operators in here - you really need to fix that.
[07:46] <tjaalton> ok cool
[07:46] <tjaalton> .)
[07:46] <tjaalton> :)
[07:46]  * jussi writes mail. 
[07:46] <tjaalton> yeah don't think we've ever had
[07:47] <tjaalton> my memory goes back 5y
[07:47] <jussi> 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] <tjaalton> jussi: me, bryceh, RAOF, Sarvatt, cnd for instance
[07:48] <jussi> ok, Ill zap one of the ircc and get things sorted. 
[07:48] <tjaalton> maybe some of the more active community ones too
[07:48] <tjaalton> thanks!
[07:54] <jussi> tjaalton: Mithrandir isnt around anymore, correct?
[07:56] <tjaalton> jussi: not working for canonical no
[07:56] <jussi> ok, thanks. :)
[07:56] <jussi> tjaalton: AlanBell will sort out the bits and peices (I am not on the IRCC anymore)
[07:57] <tjaalton> jussi: ok great to see this happen at last..
[07:57] <jussi> tjaalton: I dont know why we didnt do anything about it when I was on the ircc. :/
[07:57] <AlanBell> should be all set now (unless I messed it up)
[07:58] <jussi> AlanBell: any reason you missed an A on tjaalton? :P
[07:58] <AlanBell> see I said I got it wrong
[07:58] <tjaalton> :)
[07:58] <AlanBell> fixed
[07:59] <jussi> tjaalton: try /msg chanserv op #ubuntu-x tjaalton
[07:59] <AlanBell> \o/
[07:59] <tjaalton> whee
[07:59] <jussi> tjaalton: now try /msg chanserv deop #ubuntu-x tjaalton
[08:00] <tjaalton> rocks
[08:00] <jussi> tjaalton: https://wiki.ubuntu.com/IRC/IrcTeam/OperatorGuide
[08:00] <tjaalton> hmm I think bryceh was there already, since he has set the topic before?
[08:00] <jussi> nope
[08:00] <tjaalton> ok..
[08:01] <jussi> tjaalton: also, "/msg chanserv access #ubuntu-x list" will give you the full list
[08:01] <AlanBell> 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] <AlanBell> anyhow, I am off out now, laters all o/
[08:01] <tjaalton> hmm why bryce2 not bryceh?
[08:01] <jussi> someone probably had the channel set -t or manually opped him
[08:02] <jussi> tjaalton: /msg nickserv info bryceh
[08:02] <tjaalton> ah ok :)
[08:02] <jussi> :)
[08:03] <tjaalton> the mysteries of irc
[08:03] <jussi> tjaalton: now you can set a nice topic (the current one is a bit sparse
[08:03] <tjaalton> hum :)
[08:04] <tjaalton> maybe later, can't think of a better one yet
[08:04] <jussi> 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] <jussi> AlanBell: I dont think tjaalton can actually do that because he has no s flag. 
[08:05] <jussi> the joys of getting things up to date. 
[08:05] <tjaalton> t&c's?
[08:05] <jussi> tjaalton: look at the link ;)
[08:06] <tjaalton> looking, but what exactly?
[08:06] <tjaalton> oh the disclaimer?
[08:06] <jussi> basicallyn says you need to follow the coc and the channel will be logged
[08:06] <tjaalton> sure
[08:07] <jussi> however, as I mentioned, I dont think you can use the set command
[08:07] <tjaalton> ok
[08:08] <jussi> so we have to wait for AlanBell or someone else from the ircc to sort things a little more. 
[08:08] <jussi> anyway, carry on, glad its mostly sorted :)
[08:09] <tjaalton> yeah, thanks
[09:09] <AlanBell> tjaalton: you now have a +s flag
[09:10] <tjaalton> AlanBell: thanks
[10:09] <apw> anyone else seeing an odd lensing or combing effect on the left edge of some characters on atom h/w on precise?
[10:12] <apw> RAOF, how do i find out what sub-pixel layout is being used ?
[10:13] <apw> this feels a little like the wrong layout is being used on my atom
[10:13] <apw> or something odd
[21:53] <cnd> bryceh, what are your thoughts on the locked drags stuff
[21:55] <cnd> it's hard to discern if it's a vocal minority who have a problem with it
[21:56] <cnd> 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] <RAOF> 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] <RAOF> cnd: The locked drags stuff is the reason why alt-tab sometimes doesn't work for me, right? :)
[21:57] <cnd> oh wait, I thought beta 1 was tomorrow
[21:57] <cnd> I see it's quite a ways away
[21:57] <cnd> RAOF, maybe?
[21:57] <cnd> RAOF, no, I can alt-tab inside a locked drag
[21:58] <RAOF> I think the way I use the trackpad I quite frequently hit the draglock; perhaps some apps take out grabs on drag?
[22:03] <bryceh> 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] <bryceh> cnd, my druthers would be to have it as a non-default option
[22:06] <cnd> bryceh, ideally it would be a setting in the mouse prefs
[22:06] <cnd> unfortunately we're passed UI freeze
[22:06] <cnd> that's what I wanted to do originally, but ran out of time
[22:07] <cnd> I'll revert it hopefully as soon as the ffe is granted
[22:07] <bryceh> cnd, ask for a UI freeze exception
[22:07] <cnd> bryceh, that would require me to actually find time to develop it
[22:07] <cnd> I haven't investigated at all, and I have other bugs that are higher prio
[22:07] <cnd> and a revert of this + clickpad fixes is probably the best option anyways
[22:12] <cnd> RAOF, were you able to easily trigger the X crash before, and if so has the update fixed it?
[22:12] <RAOF> cnd: I was not, no.
[22:13] <cnd> ok
[22:13] <RAOF> cnd: But, then again, I wasn't actually using a multitouch synaptics device :)
[22:13] <cnd> hmm...
[22:16] <RAOF> Rick was hitting that, as was asac; I pointed asac at the new synaptics and it seemed to quiet him? :)
[22:21] <bryceh> cnd, was this the crash fixed in 0ubuntu3?
[22:22] <cnd> bryceh, yeah
[22:22] <cnd> the one I told you about yesterday
[22:23] <bryceh> 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] <cnd> oh great
[22:23] <cnd> :)
[22:23] <bryceh> 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] <Sarvatt> cnd: hate to pester but do you have 0ubuntu3 locally and just forgot to push by any chance? :P
[22:24] <cnd> Sarvatt, maybe?
[22:24] <cnd> I did it late last night in vienna
[22:24] <bryceh> mesa 8.0.1 looks like it'll solve another good chunk
[22:24] <cnd> before I slept 6 hours and flew home
[22:24] <cnd> Sarvatt, so I very well could have forgotten
[22:24] <cnd> let me make sure
[22:27] <RAOF> bryceh: Does that include the WriteToClient weirdness?
[22:28] <Sarvatt> RAOF: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/925341 no synaptics being used
[22:29] <RAOF> Sarvatt: Quite true.  Boo :(
[22:29] <cnd> Sarvatt, pushed
[22:29] <cnd> thanks for noticing that
[22:30] <Sarvatt> cnd: appreciate it! updated today thinking the fix was in it
[22:32] <bryceh> RAOF, no, we have more xserver crash bugs beyond these two :-/
[22:32] <bryceh> and I think the WriteToClient bug may pre-date the synaptics changes anyway, but not sure
[22:33] <RAOF> 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] <bryceh> that one was 295.10
[22:34] <bryceh> I'll have them retest, good idea
[22:36] <bryceh> O rhythmbox why you no love?