[05:37] <tjaalton> oh cool, we now have the wacom goodness in g-c-c
[06:52] <broder> ugh. the new vmware svga3d rendering is incredibly glitchy
[07:20] <tjaalton> broder: really? Prf_Jakob said it worked great when we first got it working
[07:20] <tjaalton> broder: sure you are not using normal swrast?
[07:20] <tjaalton> well, llvmpipe normal
[07:21] <broder> tjaalton: not positive. it was running unity 3d
[07:21] <tjaalton> _that_ is glitchy
[07:21] <broder> let me bring the vm back up and check
[07:21] <tjaalton> pastebin the logfile
[07:21] <tjaalton> I'm not convinced yet :)
[07:21] <broder> but there was a lot of flickering back to past frames and ghost images
[07:22] <tjaalton> sounds familiar
[07:23] <broder> yeah, it's llvmpipe. what do i need to do to switch it?
[07:24] <broder> dri-experimental?
[07:25] <tjaalton> that's empty
[07:25] <tjaalton> I'm not sure what's needed.. pastebin the logfile
[07:27] <broder> http://paste.ubuntu.com/844056/
[07:28] <tjaalton> [  1374.489] (WW) vmware(0): Failed to initialize Gallium3D Xa. No render acceleration available.
[07:28] <broder> ...oh. i bet i need to tick the box in the vm's configuration, don't i?
[07:28] <tjaalton> whatever that means
[07:28] <tjaalton> maybe
[07:33] <tjaalton> so bug 926859 remains unfixed
[07:33] <tjaalton> ah, no ubotu
[07:51] <broder> huh. i can't figure this out - vmwgfx is getting loaded, and i have a /dev/dri/card0
[07:54] <tjaalton> and still doesn't work?
[07:55] <broder> nope
[07:55] <broder> still getting the same message
[07:58] <tjaalton> weird
[08:00] <broder> where is that message even coming from? i can't find it in xserver-xorg-video-vmware or mesa
[08:10] <tjaalton> no idea
[11:49] <ara> tseliot, hola!
[11:51] <tseliot> hola, ara!
[11:52] <ara> tseliot, hey! one of the bugs that are blocking certification for 11.10 has been marked as incomplete (and assigned to you) waiting on your input for a little while:
[11:52] <ara> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/877682
[11:52] <ara> tseliot, can you check it, please?
[11:54] <tseliot> ara: sure. I have a thinkpad w520, maybe I can reproduce it here
[11:55] <ara> cool, thanks
[13:51] <tjaalton> great, can't turn numlock off
[13:51] <tjaalton> does nothing
[13:51] <tjaalton> though I get the event
[13:53] <seb128> tjaalton, going to be fixed soon
[13:53] <seb128> I'm impressed by how many people actually turn numlock off
[13:53] <seb128> I got surprised because I'm use to the screensaver having it wrong so I usually do an off-on
[13:53] <seb128> which didn't change the led
[13:53] <seb128> but I never turn it off otherwise
[13:54] <seb128> tjaalton, g-s-d issue, you can "gsettings set org.gnome.settings-daemon.peripherals.keyboard remember-numlock-state false"
[13:54] <tjaalton> well my keyboard doesn't have a separate keypad
[13:55] <tjaalton> numpad that is
[13:55] <seb128> tjaalton, let me know if the gsettings commands work
[13:55] <tjaalton> it's a lenovo thinkpad usb keyboard, so hitting numbers instead of letters atm :)
[13:56] <seb128> I didn't try it but I assume it does
[13:56] <tjaalton> I'll try
[13:56] <tjaalton> didn't hit Fn+ScrLk but some combination of Fn, shift and capslok apparently
[13:59] <tjaalton> seb128: didn't seem to help
[13:59] <tjaalton> the running session anyway
[13:59] <seb128> tjaalton, trying stop gnome-settings-daemon
[14:00] <seb128> stopping
[14:00] <seb128> doh, can't type, "try stopping..." ;-)
[14:01] <tjaalton> surprisingly hard to "type" kill, I get 2533
[14:02] <tjaalton> nope
[14:06] <tjaalton> well, g-s-d is just reflecting what the state is, it apparently can't change it
[14:19] <tjaalton> looks like not even numlockx can change it, the led stays on on xkbvleds
[14:24] <tjaalton> seb128: what's the bug# :)
[14:25] <seb128> tjaalton,  the gsd one is bug #933405
[14:25] <tjaalton> thanks
[14:25] <seb128> tjaalton, but that one is confirmed a gsd issue, downgrading gsd or settings that key to false fixes it
[14:25] <seb128> tjaalton, so I recommend you open a new one if yours isn't that
[14:26] <tjaalton> well I'm not sure where the bug is
[14:27] <tjaalton> uh oh
[14:27] <tjaalton> now the keyboard thinks it's got a numpad
[14:28] <tjaalton> even though I managed to turn numlock off (via VT)
[14:28] <tjaalton> so the keys act as a numpad or cursor keys
[14:28] <tjaalton> wth
[14:36] <tjaalton> ok it is a bug in g-s-d, I can't change the state of numlock back to off with 3.3.5
[14:36] <tjaalton> 3.2 works
[14:37] <tjaalton> though to fully fix the state I had to go to the VT
[14:39] <tjaalton> i'll upgrade my laptop to confirm
[14:40] <seb128> tjaalton, ok, the gsd bug is about to be fixed
[14:40] <tjaalton> seb128: do you want me to test it before filing this one?
[14:40] <tjaalton> in case it's the same
[14:40] <seb128> tjaalton, yes please
[14:42] <tjaalton> the workaround probably works if you reboot after it
[14:46] <tjaalton> seb128: btw, the new wacom capplet works great
[14:47] <seb128> tjaalton, excellent, thanks for testing!
[14:47] <seb128> can you calibrate with it?
[14:49] <seb128> tjaalton, g-s-d with the fix uploaded btw
[14:49] <tjaalton> no need, the one I have is not a tablet
[14:49] <tjaalton> great
[14:49] <tjaalton> actually, the "map buttons" button is greyed out
[15:10] <tjaalton> seb128: thanks! the new g-s-d works
[15:10] <seb128> tjaalton, excellent
[15:11] <tjaalton> printscreen doesn't fire the screenshot app though :)
[15:11] <tjaalton> after the updates this morning
[15:24] <seb128> tjaalton, it's not since today, it's since a few days, or a week
[15:24] <seb128> tjaalton, it stored the images in your xdg Images directory
[15:24] <seb128> stores
[15:24] <seb128> upstream GNOME design decision
[15:24] <seb128> it should do the graphical effect and sound though
[15:24] <seb128> like tablets,phones do it
[15:25] <tjaalton> ah ok, yeah there they are..
[15:25] <jcristau> do people actually enable sound effects on their computers?
[15:26] <tjaalton> they don't need to, it's on by default :)
[15:27] <jcristau> well ok, leave them enabled then
[16:44] <Sarvatt> bryceh: bah whoops, need to remove .git from the cgit urls too
[18:01] <bryceh> Sarvatt, oh, ok
[18:01] <bryceh> Sarvatt, cgit hasn't been working for me the past couple days
[18:01] <tjaalton> so, mesa and wayland* merges before FF?
[18:02] <tjaalton> 3h to go :)
[18:02] <Sarvatt> 1h?
[18:02] <tjaalton> 2100UTC
[18:02] <Sarvatt> oh
[18:03] <Sarvatt> eh 8.0.1 was supposed to be released today, might as well wait
[18:03] <tjaalton> we're still on rc2, debian has 8.0
[18:03] <bryceh> I fear for upgraders right now
[18:04]  * Sarvatt hasn't been able to upgrade for over a week
[18:04] <Sarvatt> i keep hitting it at bad times