[01:32] <sethj> hmm, I just noticed two finger tap doesn't open the context menu on 15.10. Anyone else experiencing that?
[01:32] <sethj> just to be clear, I mean two finger tap on the touchpad.
[02:40] <pitti> Good morning
[03:06] <duflu> pitti: Yes good morning (still is in Australia too)
[03:07] <pitti> duflu: heh yes, couldn't sleep any more
[05:04] <didrocks> good morning
[05:04] <pitti> bonjour didrocks !
[05:07] <didrocks> salut pitti, ça va ?
[05:07] <pitti> didrocks: un peu fatigué, je m'ai levé à 4h15 ..
[05:07] <pitti> (avec Annett)
[05:08] <pitti> mais bien, merci ! et toi ?
[05:08] <didrocks> tu n'es pas resté encore une heure au lit cette fois ?
[05:08] <didrocks> ça va, merci!  mais pas mal occupé avec du snappy…
[05:08] <pitti> didrocks: on va à Dresden cet après-midi, alors je veux encore utiliser "bandwidth"
[05:09] <didrocks> ah, d'accord :)
[05:09] <pitti> didrocks: oui, je vais faire ça (snappy demo) aussi aujourd'hui ou le prochaine semaine
[05:41] <hikiko> hello
[05:44] <didrocks> hey hikiko ! How are you?
[05:44] <hikiko> bonjour didrocks :)
[05:44] <hikiko> i am good, you?
[05:45] <didrocks> I'm fine, thanks !
[06:15] <larsu> bonjour!
[06:19] <didrocks> bonjour larsu !
[06:20] <larsu> hey how are you didrocks?
[06:21] <pitti> hellas hikiko!
[06:21] <pitti> guten Morgen larsu
[06:22]  * larsu winkt pitti
[06:22] <didrocks> larsu: I'm good, thanks!
[06:22] <didrocks> yourself?
[06:22] <larsu> great thanks!
[06:22] <larsu> sun is shining so much I have problems seeing the screeen
[06:22] <larsu> which is *awesome* in this season
[06:22] <pitti> lol
[06:22] <pitti> yeah, chilly but sunny autumn, nice!
[06:24] <larsu> indeed
[06:25] <hikiko> hey :) hi pitti and larsu
[06:26] <larsu> good morning hikiko!
[07:04] <seb128> good morning desktopers
[07:05] <pitti> bonjour seb128 !
[07:05] <seb128> hey pitti, wie gehts?
[07:06] <pitti> seb128: gut, danke! je suis travaillé depuis 4h20, on va à Dresden aujourd'hui à nouveau
[07:07] <seb128> pitti, c'est déjà l'après-midi pour toi alors !
[07:07] <pitti> seb128: en effet !
[07:11] <seb128> oh, pitti is piloting
[07:11] <pitti> *soooarrrrrrrr*
[07:12] <seb128> that queue is going to be back in 0 today ;-)
[07:12] <pitti> 57 → 42 so far
[07:12] <pitti> I think I achieved that only once :/
[07:12] <seb128> that's quite good, it was up to 80 earlier in the week
[07:12] <pitti> and with FF it won't be today
[07:12] <seb128> Laney did a good shift yesterday
[07:12] <seb128> I was pondering having a look today, but after you guys I bet only the difficults one are going to be left ;-)
[07:13] <seb128> I might still pick a few ones and at least nag server team or whoever should review them
[07:14] <didrocks> cyphermox did quite some as well overnight, that was nice :)
[07:15] <seb128> great
[07:31]  * pitti -> train station, bbl
[08:00] <willcooke> o/
[08:00] <hikiko> hello willcooke
[08:01] <willcooke> morning hikiko - did you see my message re: old bugs in Compiz...
[08:01] <willcooke> script says 708 Compiz bugs > 2 years old, and of those only 64 have had any comments in the last year
[08:01] <willcooke> Seems like we can auto-close a lot of them
[08:01] <willcooke> or rather, auto-incomplete
[08:02] <hikiko> no I didn't :s but I closed all the bugs before aug 2010
[08:02] <seb128> hey willcooke hikiko Laney
[08:02] <hikiko> it's not in my inbox :S
[08:02] <hikiko> hi Laney seb128
[08:03] <Laney> hey hey
[08:03] <Laney> I just checked the calendar and it is indeed Friday
[08:03] <Laney> chrisccoulson: oxide> no, I didn't look further than that push-state thing
[08:06] <seb128> Laney, don't be sad, monday is not that far and then you can hack again on cool Ubuntu things ;-)
[08:06] <hikiko> lol
[08:06] <Laney> I know, I just hate the weekend and going to work at the climbing centre
[08:06] <seb128> :-p
[08:07] <Laney> all the time I'm there I am just looking forward to being back at launchpad.net
[08:07] <seb128> going climing this w.e? ;-)
[08:07] <Laney> ALWAYS!
[08:07] <Laney> not outdoors though... maybe I should...
[08:07] <Laney> how's it going? ;-)
[08:08] <Laney> hey hikiko
[08:08] <seb128> going good!
[08:08] <hikiko> willcooke, I can't find your email :/
[08:08] <seb128> I spent another hour triaging unity bugs, but start having enough of those so time to do something else
[08:08] <willcooke> hikiko, was IRC
[08:08] <seb128> I'm going to try to keep doing one hour in the morning for a bit
[08:08] <willcooke> thanks seb128 !
[08:08] <seb128> yw!
[08:09] <willcooke> btw - please let me know (or fill in the spreadsheet) the days you expect to need a hotel room everyone
[08:09] <willcooke> quite surprised how few people have done that
[08:10] <Laney> people usually look at their travel options first
[08:11] <hikiko> willcooke, I can't find it, but I closed some bugs before so we have even fewer
[08:11] <willcooke> We need to get the hotel book asap, otherwise we're sleeping under desks in Blue Fin
[08:11] <willcooke> *booked
[08:18] <pitti> willcooke: I'm sure London has better places to spend the nights at :)
[08:18] <Laney> sleepover at willcooke's house
[08:18] <Laney> hey pitti
[08:19] <pitti> hey Laney, how are you?
[08:19] <willcooke> I think there is a direct correlation between hotels with rooms available at short notice and the murder rate for that area
[08:19] <Laney> feeling strangely fine (/me puts that album on)
[08:19] <Laney> went round a friend's for cheese and board games last night
[08:19] <Laney> you?
[08:21] <pitti> Laney: feeling quite okay too, although a bit tired; started early today as we go to Dresden over the weekend
[08:23] <Laney> that means you're closer to being finished for the week :)
[08:24] <pitti> Laney: exactly :)
[08:25]  * Laney swears at mips* https://buildd.debian.org/status/package.php?p=gdk-pixbuf&suite=experimental
[08:52] <willcooke> Trevinho, hey - any thoughts on when/if the dash overlay scroll bars will land?
[09:44] <Sweet5hark> hmm, when did we cross the border to insanity: When we had a ./configure script with more then 10.000 lines? Or when we had a ./configure.ac with more than 10.000 lines?
[10:02] <willcooke> hi Laney, seb128 - I've opened a bug with the new wallpaper.  I will speak to the doc team about exceptions
[10:02] <willcooke> https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1497177
[10:02] <seb128> willcooke, popey, that screen corruption on monitor config changes (like plugin one or undocking), did you ever try changing workspaces? does that workaround it for you?
[10:03] <willcooke> seb128, I tried it, made no difference.  I think it's a different bug.  Things like vt1 were effected as well
[10:03] <Laney> willcooke: thx, will look later/monday
[10:03] <willcooke> thanks Laney
[10:03] <popey> seb128: i dont recall, but andyrock has made a patch which I am using now
[10:03] <seb128> willcooke, k, I just saw it here with an external vga monitor but changing workspace fixed it
[10:03] <popey> and have been able to change monitor config without it breaking
[10:04] <seb128> popey, is that working?
[10:04] <popey> so far, yes
[10:04] <seb128> so it was a compiz/unity issue?
[10:04] <popey> looks like it
[10:04] <seb128> andyrock, ^ should https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1421575 be marked invalid?
[10:04] <willcooke> popey, so your wife-problems are fixed ;)
[10:04] <popey> lp:~azzar1/unity/lp-1485727/
[10:04] <popey> IKR
[10:04] <seb128> lp #1485727
[10:05] <willcooke> but
[10:05] <willcooke> I spoke to andyrock yesterday about this
[10:05] <seb128> what I though, they seem similar problems
[10:05] <willcooke> and he said there was no way I should be seeing it on 14.04
[10:05] <seb128> but then changing workspaces should workaround it
[10:05] <seb128> willcooke, your bug might be different from the one others are seeing then...
[10:05] <popey> seb128: ok, let me revert back to stock unity and try that
[10:05] <seb128> popey, thanks
[10:05] <willcooke> seb128, yeah, I think so
[10:14] <popey> seb128: reverted to stock wily unity, rebooted, logged in (had a separate issue I will mention in a moment) screen config changed, screen freaked out, switched desktops, desktop back to working!
[10:14] <popey> So yes, switching workspaces _does_ work around the issue
[10:17] <seb128> good
[10:17] <seb128> popey, thanks for testing
[10:17] <seb128> popey, I bet you wish you knew about that workaround before ;-)
[10:18] <popey> Yes. I was thinking exactly that :)
[10:19] <seb128> well at least it's good, we have a workaround and andyrock has a fix
[10:19] <seb128> just suck to be willcooke who seems to have a different issue :-/
[10:19] <popey> willcooke: does switching workspaces not "fix" it for you?
[10:19] <willcooke> it didn't, but let me try again now...
[10:20]  * willcooke saves everything first
[10:21] <popey> Well, seb128 has made my day. So that's good. Thanks seb128 :)
[10:21] <seb128> popey, yw!
[10:23] <willcooke> that's a no then
[10:23] <willcooke> although, actually vt1 is fine
[10:24] <seb128> :-/
[10:26] <willcooke> mine smells like drivers to me
[10:27] <popey> mine smelled like drivers too
[10:28] <popey> did you not test vanilla 14.04 from a stick?
[10:28] <popey> pre-HWE stack?
[10:28] <willcooke> well, seb128 and I tried a load of old kernels
[10:28] <willcooke> I can't remember what we found out though.  I'll try again later
[10:28] <seb128> the iso from usb didn't have the issue
[10:29] <seb128> we didn't find what update started it by doing updates of xorg&co and restarting session
[10:29] <seb128> we also tried to boot old kernel from the installed laptop
[10:29] <seb128> but those didn't fix it
[10:30] <willcooke> I should try andyrock's fix then, just out of interest
[10:31] <andyrock> hey
[10:31] <andyrock> well that patch applies to 15.10 (15.04 too?)
[10:31] <willcooke> but not 14.04 right?
[10:32] <andyrock> well you should try to merge hikiko's branches
[10:32] <andyrock> then my fix
[10:32] <andyrock> and see what happens
[10:32] <andyrock> or just try to reproduce the problem on 15.10 + that fix
[10:33] <willcooke> this sounds like something for the weekend
[10:33] <andyrock> if you can't reproduce the problem anymore we can try to build a ppa with all the patches
[10:33] <andyrock> to test on 14.04
[10:33] <andyrock> and see what happens
[10:34] <hikiko> yes you need the save_state() restore_state() otherwise the unity transformations will be applied in all running compiz plugins causing weird artifacts
[10:34] <hikiko> and then andyrock's fix
[10:34] <andyrock> makes sense
[10:34] <andyrock> I'll try to build a ppa in the weekend
[10:44] <willcooke> thanks
[10:44] <popey> andyrock: dunno if it's related, but when I tried your patched unity, if I changed the desktop config (via pulling my laptop out of the docking station) the display froze
[10:44] <popey> if I plug it back in again it recovers
[10:45] <seb128> Laney, larsu, lol, I found how to use youtube in totem, usability fail imho
[10:45] <popey> its not the whole system that freezes, because on the frozen laptop display if I "click" (blindly) things, then it catches up, or does them without showing me the result, so when I plug it back into the display, I suddenly see all the apps I launched
[10:47] <seb128> Laney, larsu, it's not in the channels, you need to be on the "videos" tab, type something on the keyboard and then click on the "filesystem" label on the right of the text entry, which is a combo, and pick "youtube"
[10:47] <seb128> I wonder if I'm just a dumb user
[10:47] <seb128> or if that's really non obvious
[10:48] <andyrock> popey so without the patch what's the problem?
[10:49] <andyrock> it's the same right?
[10:49] <popey> without the patch the screen goes crazy when I change monitor config
[10:49] <popey> with the patch the screen freezes
[10:49] <popey> will test some more though.
[10:50] <larsu> seb128: that is really dumb
[10:50]  * larsu is off for lunch though
[10:50] <seb128> larsu, lunch is a good idea, I should do the same
[10:50] <seb128> larsu, enjoy ;-)
[10:50] <larsu> :)
[10:50] <larsu> thanks
[10:51] <andyrock> k thanks i'll try to test it too
[11:10] <Trevinho> willcooke: OSB... I've fixed the bugs in nux, I'm almost done now... But there's one last bug in nux that I'd need to clear
[11:10] <willcooke> Trevinho, coolio, thanks.  You're already on the case
[11:12]  * Trevinho finally got a silo!
[11:13] <didrocks> Trevinho: happy siloing :)
[11:14] <popey> willcooke: did the new font land on the desktop?
[11:15] <willcooke> popey, heh - which one?
[11:15] <popey> ours :) Ubuntu Font.
[11:15]  * Trevinho heard that they were testing it yet?
[11:15] <willcooke> right, it's not quite that easy
[11:15] <popey> oh okay.
[11:15] <willcooke> v. 0.83 of the Ubuntu font is release which includes fixes for Mac
[11:15] <popey> just noticed my desktop font looks horrid, and wondered if that was why
[11:16] <popey> probably just my eyes :)
[11:16] <willcooke> popey, humm, worth looking in to.  Can you do a screen grab?
[11:20] <popey> willcooke: http://i.imgur.com/zxuuUJa.png
[11:22] <willcooke> popey, humm, doesn't look quite as smooth as it should does it
[11:22] <willcooke> popey, what about the dash?
[11:22] <popey> same
[11:22] <popey> i have logged in to other (non-unity) desktops on this laptop recently, wonder if that's messed my font settings up
[11:22] <popey> nvm, will have a play
[11:23] <willcooke> popey, let me check my vanilla 15.10 vm...
[11:35] <tkamppeter> hi, I have a problem with bug 1449875. I could fix it by adding a dependency to Ghostscript but the new dependency recommends tons of unneeded packages. Do all these get installed then, too?
[11:47] <popey> willcooke: do you still have an iphone kicking around?
[11:48] <popey> the #4 crash on errors.u.c is upower, on 14.04 (which you're running?) I have a theory that it only happens when an iphone is left plugged in and charging off the computer - i see it here on my 15.10 system.
[11:49] <popey> I can tell upower has crashed because I get randomly sent to the lock screen while I'm working, and my machine slows as apport does its dance :)
[11:50]  * davidcalle reports popey for not using the Ubuntu font
[11:51]  * popey runs away to the French Foreign Legion 
[11:55] <Sweet5hark> seb128: libreoffice 5.0.2 for wily building in ppa (and locally) fwiw ...
[12:43] <seb128> Sweet5hark, great
[12:43] <seb128> Sweet5hark, did you get the ffe approved?
[12:44] <Sweet5hark> for 5.0.2? not yet
[12:45] <Sweet5hark> seb128: building != finished building for libreoffice. and I need build logs for a FFE, dont I?
[12:45] <seb128> Sweet5hark, ignore me, I was asking about 5.0 but it looks like that landed during my holidays
[12:46] <Sweet5hark> seb128: yes, it did. kudos to cyphermox for that.
[12:46] <seb128> Sweet5hark, now you have more sponsors for the DMB application, right? ;-)
[12:46] <Sweet5hark> seb128: he wondered how it can be that Im not either drunk or in a asylum when seeing the packaging.
[12:46] <seb128> lol
[12:47] <Sweet5hark> seb128: hopefully insane packages need insane maintainers.
[12:47] <Sweet5hark> (there is supposed to be a dot between hopefully and insane)
[12:55] <willcooke> popey, I do have an iphone kicking around
[12:56] <popey> willcooke: bet upower crashes if you leave it plugged into your ubuntu laptop :)
[12:57] <willcooke> popey, will find cables and such and try it
[12:57] <popey> ta
[13:00] <willcooke> hi aquarius
[13:00] <aquarius> willcooke, hey
[13:01] <willcooke> seb128, do you happen to know off the top of your head if any ibus or fcitx changes landed in 14.04 recently?
[13:01] <willcooke> aquarius, are these keyboard oddities limited to Unity and/or Gtk apps, Qt apps?
[13:02] <aquarius> OK. Ctrl-arrows fail in Telegram (which is Qt), gnome-terminal, xchat-gnome (Gtk)
[13:02] <aquarius> as does ctrl-f
[13:03] <aquarius> ctrl-s works fine in xchat-gnome
[13:03] <willcooke> and xev shows that ctrl is being seen?
[13:03] <willcooke> Trevinho, is Unity doing any extra keyboard grabbing in 14.04 recently?
[13:04] <willcooke> aquarius, you dont happen to have another keyboard kicking around?
[13:04] <seb128> willcooke, not that I know, why?
[13:04] <seb128> tkamppeter, don't add that depends/recommends if it pulls too much in
[13:04] <seb128> willcooke, I guess for what aquarius is asking
[13:04] <seb128> aquarius, do you get the issue in a guest session?
[13:04] <aquarius> willcooke, yup; xev shows ctrl is being seen, and as noted some other ctrl combinations work, so the key's not broken
[13:05] <willcooke> seb128, aquarius is suddenly having strange kbd issues, ctrl-arrows stopped working, ctrl-f stopped working
[13:05] <willcooke> seb128, yeah
[13:05] <aquarius> another keyboard -- you mean, another physical keyboard? Um. Somewhere :)
[13:05] <seb128> willcooke, do you see the same?
[13:05] <aquarius> guest session: good idea, I'll try that.
[13:05] <willcooke> aquarius, yeah, I dunno, would be good to rule that out
[13:05] <willcooke> seb128, nope, everything is fine here
[13:07] <aquarius> confirmed: I see the same issue in a guest session
[13:07] <willcooke> daflip
[13:08] <seb128> well at least it's not user config
[13:08] <willcooke> aquarius, do you happen to have a spare USB stick kicking around.  Would be interesting to see if a live 14.04 or 15.04 do that too
[13:09] <aquarius> and the other ctrl key on the keyboard exhibits the same problem too, having just thought of tsting that
[13:09] <aquarius> so it's not that someone hexed the ctrl key with "now you hate F and the arrows" :)
[13:10] <desrt> seb128: this is not strictly a behaviour change
[13:10] <desrt> seb128: the old glib would have done this too if it was "fast enough" (or if you moved the file slow enough)
[13:10] <desrt> but the thing where events were always delayed 1s means that you never got the chance to see that before
[13:10] <seb128> desrt, in practice it is though, enough to make working code behave differently
[13:10] <desrt> so now that event reporting is faster, it makes sense of course that you have a chance to see more events
[13:10] <seb128> hum, k
[13:11] <desrt> i'd argue that the existing code wasn't _really_ working because there were cases where it could have still failed (like if the fs was super-heavy-loaded or something)
[13:11] <desrt> although in practice, i have to agree with you :(
[13:11] <seb128> same argument that the gsettings change some cycles ago
[13:11] <desrt> but i'm really not sure what we should do to fix it....
[13:11] <seb128> yeah, dunno either
[13:11] <desrt> well, this one was weaker, and had an easy fix
[13:11] <seb128> I guess we can fix unity, which is where we noticed it and too bad for other potential users
[13:12] <desrt> (which i still didn't do, i admit... i still think people should just "fix" their code) :)
[13:12] <desrt> but this case.... really, we fixed a bug that we had before, which is that events were being missed
[13:12] <desrt> (due to the mandatory delay)
[13:13] <seb128> yeah, same good old "apps relying on the runtime behaviour, not the theorical one"
[13:13] <desrt> which is fair enough
[13:13] <desrt> TDD is a thing, right?
[13:13] <desrt> nobody writes code to be correct anyway -- only to pass tests
[13:13] <desrt> because the first way is apparently impossible
[13:13] <desrt> btw: good morning :)
[13:13] <seb128> good morning, happy friday ;-)
[13:14] <desrt> hells ya friday
[13:14] <seb128> I hope you had some coffee already before jumping on IRC§
[13:14] <desrt> gotta go to the airport and rent a car tomorrow
[13:14] <seb128> !
[13:14] <desrt> actually, i didn't
[13:14] <desrt> and there's a story about that, and i _should_
[13:14] <seb128> you should ;-)
[13:14] <desrt> basically, i owe money to the store downstairs
[13:14] <desrt> went yesterday and tried to pay with my credit card, which was cancelled
[13:15] <desrt> (new one was in the mail and they got too 'excited' about transfering the account too soon)
[13:15] <desrt> so i couldn't pay... so i really do have to go down today to get a coffee.... and pay for two :)
[13:15] <desrt> bbiab
[13:15] <seb128> enjoy! :-)
[13:16] <aquarius> OK, crisis over
[13:16] <aquarius> It is the keyboard's fault
[13:16] <aquarius> Using a different keyboard; works fine
[13:16] <seb128> good
[13:17] <aquarius> well, it's good from the point of view of the Ubuntu desktop team
[13:17] <willcooke> phew
[13:17] <aquarius> er!
[13:17] <willcooke> sucks to be aquarius
[13:17] <willcooke> ;p
[13:18] <aquarius> it was good
[13:18] <willcooke> aquarius, Logitech k720
[13:18] <aquarius> but this one keeps failing
[13:18] <aquarius> keys don't register sometimes
[13:18] <aquarius> which I suppose might be *this* keyboard also failing
[13:18] <aquarius> willcooke, the broken one is a Logitech K520 :)
[13:18] <aquarius> I like logitech stuff
[13:20] <aquarius> all the spacing is wrong on this one and everything :)
[13:20] <aquarius> still, things work now at least.
[13:56] <desrt> so lol.  got my new 20Ah usb battery yesterday, plugged it in overnight to charge
[13:56] <desrt> ...it's still charging
[13:58] <Laney> oh yeah, the unity fix
[13:58]  * Laney buildz
[14:13] <tkamppeter> seb128, and as I do not know whether it pulls to much in, I am asking.
[14:40] <Laney> ummmm
[14:41] <Laney> why do I have some kind of fcitx indicator in a wily live session?
[14:42] <Laney> happyaron: any clue?
[14:50] <seb128> Laney, "some kind"?
[14:51] <seb128> Laney, what locale?
[14:51] <Laney> it's a tux penguin
[14:51] <Laney> en_US I guess, didn't change anything
[14:51] <seb128> ps aux | grep fcitx?
[14:52] <Laney> fcitx-qimpanel?
[14:52] <Laney> it's in /etc/xdg/autostart
[14:54] <Laney> if I kill that it gets replaced with a normal fcitx one
[14:54] <Laney> then kill fcitx and both gone
[14:57] <seb128> I lost track, I though we wouldn't install fcitx by default by pull them through langpack/language-selector?
[14:58] <seb128> we probably need GunnarHj and/or happyaron for the details
[14:58] <Laney> it's meant to be shipped as a .deb on the iso so that you can install it if you have internet
[14:58] <Laney> but not actually installed
[14:58] <Laney> not working right anyway
[14:58] <seb128> if you have "no" internet?
[14:58] <Laney> ye
[14:59] <seb128> k
[14:59] <seb128> so why is it installed? ;-)
[14:59] <seb128> but yeah, seems buggy
[14:59] <seb128> please open a bug?
[14:59] <seb128> or
[14:59] <seb128> https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1489717
[14:59] <Laney> https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1489717
[14:59] <Laney> ha
[15:00]  * seb128 assigns, High, tag rls-w-incoming
[15:00] <seb128> Laney, thanks for pointing it out!
[15:03] <Laney> quality triaging
[15:03] <Laney> would report bug again
[15:05] <Laney> maybe I'm wrong about how it was meant to be installed in the iso
[15:05] <Laney> it might be that it should be installed there and removed after if you don't have chinese
[15:05] <Laney> can't quite remember the discussion
[15:05] <Laney> but if so then fixing that bug would be enough
[15:07] <seb128> yeah
[15:07] <Laney> I saw that it was me who merged the change into the seeds
[15:07] <Laney> and thought hey that guy is usually right, it's probably *me* that is wrong
[15:07] <Laney> :P
[16:09] <seb128> desrt, larsu, Laney, can any of you remind me the environment variable that can be set to see the gdbus traffic?
[16:11] <Laney> G_DBUS_DEBUG=all
[16:14] <desrt> =message is better
[16:14] <desrt> all is too verbose
[16:17] <seb128> Laney, desrt, thanks
[16:17] <seb128> brb, session restart
[16:18] <larsu> desrt: it's all too verbose
[16:19] <Laney> no YOU'RE too verbose
[16:20]  * larsu shuts up
[16:23] <Laney> :(
[16:44]  * willcooke switches the light on
[16:44] <willcooke> it's not even 6pm yet, and its too dark
[16:44] <willcooke> :'(
[16:46] <Trevinho> oh... so sad... :(
[16:46] <Trevinho> willcooke: ah, you asked me about new grabs in 14.04 somewhere?  But well, I don't think anything changed recently
[16:47] <willcooke> Trevinho, s'ok it was aquarius dodgy keyboard all along ;)
[16:47] <aquarius> I am exceedingly sad about this, since now I've gotta buy a new keyboard
[16:47] <aquarius> and I liked my logitech one
[16:48] <Trevinho> oh, well mechanical ones are the new old stuff :)
[16:48] <willcooke> buy a new one the same
[16:48] <aquarius> trying to decide whether I should ask G+ and get a billion answers to make myself feel popular
[16:48] <Trevinho> I'd just love to get a full keyboard with trackpad... but lenovo doesn't care about that :(
[16:49] <willcooke> aquarius, screw that, go on eBuyer, wireless keyboards, sort my popularity, done
[16:49] <aquarius> willcooke, but... this one's bust. This is not encouraging me to buy another. especially since I've only had it 18 months!
[16:49] <willcooke> ah, I have a picture of your keyboard round here somewhere....
[16:50] <willcooke> popey sent it to me...
[16:50] <willcooke> http://i.imgur.com/ZaSx2eu.jpg
[16:51] <aquarius> blimey, that's horrid
[16:51] <Trevinho> Speaking of membrane keyboards, I'm experiencing lot of pleasure with this one http://www.logitech.com/en-us/product/wireless-illuminated-keyboard-k800?wt.mc_id=global_social-k800_redirect_FY11
[16:51] <aquarius> my keyboard is not like that :)
[17:02] <robert_ancell> desrt, decided not to come in to XDC today then?
[17:05] <desrt> robert_ancell: no.  had too much work to do
[17:06]  * desrt has been dealing with travel, emails, etc. for most of the morning
[17:12] <willcooke> happy weekend all
[17:12] <willcooke> safe travels robert_ancell
[17:20] <Laney> happy weekend!
[17:20] <desrt> Laney: take care!
[17:20] <larsu> have fun!
[17:21] <mterry> seb128, this bluetooth fix...
[17:22] <seb128> mterry, yes?
[17:22] <mterry> seb128, am I supposed to see a dialog when trying to pair?  I still don't see one  :(
[17:22] <mterry> i mean, a pin prompt
[17:22] <mterry> seb128, I install the package and then restart the control center
[17:23] <seb128> mterry, yes, for me when I select the keyboard in settings and do next I get pincode to enter
[17:23] <mterry> humph
[17:25] <mterry> seb128, well the code change seems similar to the old one.  But I don't know if I should comment in the bug, since it doesn't seem to change things for me.  Maybe my keyboard has additional special problems
[17:25] <mterry> comment in the MP I meant
[17:25] <seb128> mterry, I Cced you mainly so you could try
[17:25] <seb128> you might have more issues
[17:25] <seb128> feel free to ignore the mp if that doesn't do it for you
[17:26] <seb128> mterry, I get that with the patch here, http://people.canonical.com/~seb128/bluetooth.png
[17:26] <seb128> where it was spinning/failing before
[17:26] <mterry> seb128, you are living the dream
[17:26] <seb128> lol
[17:26] <mterry> seb128, now you're just bragging  :)
[17:26] <seb128> :-(
[17:26] <mterry> haha
[17:27] <mterry> seb128, that's a nice dialog though
[17:27] <seb128> mterry, you can try to  G_DBUS_DEBUG=all bluetooth-wizard
[17:27] <seb128> and see if there is anything useful in the log
[17:28] <mterry>  >>>> METHOD ERROR org.bluez.Error.Rejected
[17:28] <mterry>       message 'Rejected bluetoothd generated PIN code'
[17:28] <mterry>       in response to org.bluez.Agent1.DisplayPinCode()
[17:28] <mterry>       on object /org/bluez/agent/gnome
[17:28] <mterry> seb128, ^
[17:28] <mterry> seems bad
[17:28] <seb128> yeah
[17:29] <seb128> unsure why, but it's a different method that the one used on my keyboard (DisplayPasskey)
[17:33] <mterry> fascinating
[17:33] <seb128> mterry, I'm about to call it a week, unsure what's going on but I can try having a look on monday if I see something in that code (a bit difficult to debug without device to test though)
[17:33] <seb128> mterry, did you find something?
[17:33] <mterry> seb128, my keyboard is a weird combo keyboard/touchpad
[17:33]  * Trevinho probably got nux under control to get the new scrollbars not to be badly rendered...
[17:33] <mterry> seb128, don't worry about it, go eod
[17:33] <seb128> Trevinho, great
[17:33] <mterry> seb128, no didn't find any thing, just slowly responding to your message  :)
[17:33] <seb128> mterry, I'm still interested if you figure out something so please comment on the bug if you do ;-)
[17:34] <mterry> seb128, yar
[17:34] <seb128> have a nice w.e everyone!
[17:34] <mterry> bye!
[17:34] <Trevinho> yah... using nux is always like guessing random numbers
[17:47]  * Trevinho leaves for WE