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