[01:12] yay, new -intel, thank you [01:21] james_w, yep, hope it's stable. Was looking like the number of issues fixed by updating it was greater than my interest in continuing to cherrypick ;-) [01:22] well, it closed the bug that I thought was mine, so I'll be happy if that was the case [01:22] I'll hopefully be able to suspend next time I'm away from home :-) [01:22] yeah the suspend fix was the biggie [01:23] I was a bit aggressive at guessing on some bugs that I *think* are going to be fixed. I figure the users will be bold in reopening the bugs if I'm wrong :-) [01:27] yeah, I don't think you'll have a problem with that :-) [01:28] I saw Jesse's post on possibly being able to capture a GPU dump when it freezes, that would be great [01:33] i made sure every bug closer i added to the dpms off fix was fixed for the original reporter by the update in x-updates, resume from suspend would be more in a kernel fix i would think unless dpms is getting turned off before suspend for some reason? there was a fix for most peoples suspend/resume problems in 2.6.31-rc2 and 2.6.30.1 [01:34] james_w, yeah I need to pull that patch and take a look at it [01:35] Sarvatt, yeah I actually went and added several more bug#'s on top of yours. I'm sure yours are accurate, but less confident on mine :-) [01:35] Sarvatt: I could suspend and resume fine, but I had no X afterwards, and dpms would sometimes lead to the same thing as well [01:35] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9e06dd39f2b6d7e35981e0d7aded618686b32ccb [01:36] ah, any idea if it only happen when compiz was enabled james_w? [01:36] I'm happy to have the bug marked as fixed either way, as I never did what I should and invested the time to delve in to the problem [01:36] if it's not fixed then I will do so [01:36] yeah, I never tried without it actually [01:37] -intel has been too solid otherwise so far for me in karmic that I never thought to try without it :-) [01:37] theres someone reporting that 965+ isnt resuming right with compiz enabled still even after the ordering fix but he hasnt been able to figure out why [01:38] I'm 945 for what it's worth [01:38] ah good [01:38] do you use KDE? [01:39] i think KDE locks the session and does a dpms off on suspend [01:44] seemed like most of the people having problems with it were using KDE, thats why I filed one of the bugs against acpi-support because it was using the screenblank script in there under KDE causing problems, getting rid of the screenblank script and letting just KDE handle dpms fixed it for a few people before it was fixed in the driver [01:47] that was just for people with hangs on lid close though [01:48] nah, GNOME [01:54] heads up btw [01:54] Setting up xserver-xorg-core (2:1.6.99.1+git20090709.e8121033-0ubuntu0sarvatt) ... [01:54] dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. [01:57] whenever xserver gets updated, new dpkg change [01:58] xorg-server/debian/xsfbs/xsfbs.sh:ARCHITECTURE="$(dpkg --print-installation-architecture)" [02:02] ah it'll be pulled in from debian anyway http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=7deebf983f53c505bc25171ab77fdc408f250a6e [02:03] adding patches on top of the current xserver will give the error though (not that it hurts anything) [02:04] :-) "Launchpad can now import code from Git repositories." whoa [02:09] bryce: http://blog.launchpad.net/bazaar/git-imports [02:11] kees: bryce@chideok:/tmp$ bzr branch lp:xserver-xorg-video-intel [02:11] bzr: ERROR: Invalid url supplied to transport: "lp:xserver-xorg-video-intel": xf86-video-intel has no default branch. [02:11] hrm [02:15] woop, seems to be fixed. Thanks all [02:20] bryce: do you have to link it first somewhere? [02:22] probably [02:22] james_w, nice :-) [02:23] https://code.edge.launchpad.net/+code-imports/+new [02:33] bzr branch lp:ubuntu/karmic/mesa and libdrm work [05:33] Sarvatt, sweet! [06:38] ~[6~[6~[6~[6~/win 13 [06:38] argh [08:35] speak of the devil, they fixed that bug in pixman tjaalton -- http://cgit.freedesktop.org/pixman/commit/?id=0fce356762864572ae126733f657600fbb9116ce [08:39] Sarvatt: nice [08:43] FYI, I'll be more or less offline the next two weeks.. [08:43] bryce: ^^ [08:44] here's hoping that 1.7beta is released by then ;) [08:45] tjaalton, okay hope it's for something fun :-) [08:45] bryce: yeah, back to vacation. tomorrow I'll participate in a rowing contest, but just for fun [08:46] 60km on a boat with seven pairs and a captain [08:46] my butt will be sore :/ [08:48] other than that it's just lazying at the summer cottage [08:48] ah good, was worrying a bit you might be rowing to Ireland for some plundering ;-) [08:49] yeah, there must be some viking blood in my veins :) [08:59] ooh, -intel update [09:10] Yeah, with bonus crazy 60Hz mode. [09:11] crazy 60Hz mode? [09:14] RAOF, you mean return of vblank sync? [10:53] bryce: No, I mean trying to drive my LVDS with a 60Hz mode that the display doesn't like one bit. [10:53] There'll be a bug filed with cool screenshots. [10:57] ok [13:17] Sarvatt, how far away do we think the ati kms userspace support is? [13:55] james_w: It looks like dontzap is still setting xorg.conf, but that doesn't have the effect in Karmic that it did in Jaunty. Do you know how that's supposed to be set now? [13:56] through the keyboard layout [13:56] so it's now per-user and doesn't require an X restart [13:56] I see. [13:56] tseliot: Did you plan on updating dontzap? [13:57] ScottK: yes, sure [13:57] what's the use for dontzap at this point? [13:58] jcristau: Making ctal-alt-backspace work. [13:58] well, no [13:58] the gnome kbd applet does that [13:59] * ScottK doesn't use Gnome. [13:59] the kde kbd applet, then [14:00] the last time I tested it, setting dontzap with setxkbmap didn't work [14:00] jcristau: It doesn't support that. [14:00] in Karmic but it worked in Fedora [14:00] tseliot: so fix the server to have DontZap off by default [14:01] jcristau: isn't it off by default again now? [14:01] it is upstream and in fedora [14:02] in the past we used what upstream decided so as to minimise maintenance [14:03] tseliot: I built xserver-xorg-input-synaptics for karmic in my PPA with your patch for settling the touchpad down and it's made a huge difference with my mini 10v [14:03] ScottK: yes, unfortunately it can't be upstreamed as it's very specific to the mini 10v [14:04] tseliot: Thanks for the patch. [14:04] james_w: does setxkbmap work for you to enable/disable zapping in Karmic? (I'm still using jaunty) [14:04] Haven't tried actually [14:04] ScottK: it's my job (OEM) ;) [14:05] tseliot: Just because you got paid to do it doesn't mean I can't appreciate it. [14:05] tjaalton: ^^ (setxkbmap) [14:05] ScottK: I'm glad it helped :-) [14:07] I'll also look at the KDE systemsetting module and see how hard that would be to patch instead. [14:07] Maybe maco will do it since she want's to improve her C++ [14:08] ScottK: you don't need to [14:08] as I see it [14:08] How so? [14:08] I could confirm if I could fathom the way through this twisty path [14:08] the magic of good software design :-) [14:08] where will ./kcontrol/kxkb/kxkb_part.cpp end up? [14:09] or how can I access that part I mean? [14:09] do what? [14:09] maco: We're discussing making dontzap work for KDE in Karmic [14:09] it doesnt? [14:10] doesn't work for anyone in karmic [14:11] oh. good to know, i was just about to try it [14:11] since suddenly, today, my vga claims to have nothing connected to it. which is a lie. and it worked on wednesday [14:12] and no, this isnt the 13 hours ago upload of -intel. im still on the version from a few days ago. and randomly deciding to ignore my VGA port after resuming from suspend isn't a first :-/ [14:12] I wanted to set the xkb option in xorg.conf and use setxkbmap to apply settings without having to restart X. This way it's DE agnostic [14:13] that's because there's no need for it in karmic... if the default is changed to off in the server, and kde/gnome both use libxklavier, they'll just have the option in their applet already [14:13] and things will just work [14:13] jcristau: OK. So how come I don't have this option then? [14:14] i don't know. i don't use kde :) [14:14] jcristau: OK. So there is work to do and I'm trying to understand what. [14:19] james_w: That should be in systemsettings [14:20] found it [14:21] Only-Show-In=kde for half of the parts used by systemsettings is a bit odd [14:22] I think I found it [14:22] click on Regional & Language [14:22] james_w: KDE gets yelled at for 'duplicate' menu entries if stuff like that isn't done. [14:22] tseliot: Yes? [14:23] there's a label which says "Command" and then there's a text entry which says something like setxkbmap -model pc104 -layout it,es -variant , [14:23] it only shows [14:23] in the system settings though doesn't it? [14:23] not found it in my menu [14:23] http://people.ubuntu.com/~jamesw/layout.png [14:24] Interesting. [14:24] I have that section, but it's greyed out/locked. [14:24] james_w: did you set the xkb option manually? [14:25] you need to "Enable keyboard layouts" on the first tab there [14:25] Ah [14:26] james_w: or was the "Key sequence to kill the X server" already there? [14:27] I did nothing [14:27] just chased down the GNOME stack and then up the KDE stack to find where the equivalent settings are [14:27] nice, so, problem solved? [14:28] when X is updated [14:28] Interesting. Works too. [14:29] james_w: Very nice. Thanks. [14:29] tseliot: Yes. Problem solved. [14:29] ScottK: ok, so we can remove my patch from kdebase [14:29] \o/ [14:29] tseliot: Yes. [14:30] key sequence to kill the X server is in the Advanced tab [14:32] jcristau: do you know if gnome has something similar in its xkb applet? [14:32] * tseliot hopes so [14:34] tseliot: it does [14:34] So the remaining question is xfce? [14:35] that uses xklavier as well [14:35] great, this means that we can drop dontzap (the package) [14:35] \o/ [14:35] so it should just work, reading the options from /usr/share/X11/xkb/evdev.xml [15:16] hello..iḿ quite confused about ATi drivers...can anyone help? Thenka a lot! [15:21] hello..i'm quite confused about ATi drivers...can anyone help? Thanks a lot! [15:22] Hello I have an ATi x1950pro video card, but there is no more support from ATi/AMD since they say that this 2 years old card (worth u$s 200 at buytime) is no longer supported by ATi [15:22] In this repo I see theese two drivers: [15:22] fglrx-installer - 2:8.620-0ubuntu3~jaunty [15:22] xserver-xorg-video-ati - 1:6.12.2-0ubuntu1~xup~1 [15:22] I have added the repo and installed xserver-xorg-video-ati - 1:6.12.2-0ubuntu1~xup~1, but the program glmark just hangs wit message "Segmnentation fault" [16:09] tseliot, why can't that patch be upstreamed? [16:10] * ScottK wonders too. [16:10] While Mini 10v is where it really helps it seems like a generally good idea. [16:10] superm1: because it's a workaround. A generic solution can't be found as the touchpad doesn't support multi-finger detection and reports some weird finger width/pressure values [16:11] tseliot: Are there cases where the values it supresses are valid with other hardware? [16:11] ScottK: yes [16:12] tseliot, so if that's the case, why not just try to detect the specific model of this one, and only do the weird stuff on this one then? [16:12] superm1: I thought about that too but I doubt that upstream would include it [16:13] tseliot, well it's not like it's some archaic wanna-be synaptics touchpad. it's a real synaptics touchpad that just reacts a little differently than others. [16:14] tseliot: I'd settle for something we could ship in our package as a quirk. [16:14] so i can't see why upstream wouldn't want to see it fully functional albeit with a separate code path for its quirks [16:15] ScottK: that could be done [16:15] superm1: I'm not upstream ;) but I can ask them [16:16] Upstream is better, but if it's something we can at least get in the archive, that'll help a lot of users. [16:16] here's the bug report in upstream's bugzilla: http://bugs.freedesktop.org/show_bug.cgi?id=21614 [16:16] Freedesktop bug 21614 in Input/synaptics "Touchpad cursor jumps when two fingers are used" [Normal,New] [16:17] my second patch will be adopted (well, sooner or later): http://bugs.freedesktop.org/show_bug.cgi?id=21613 [16:17] Freedesktop bug 21613 in Input/synaptics "Property to make part of the touchpad insensitive to movements" [Enhancement,Assigned] [16:21] so both patches help it in different ways then, or are these two separate problems? [16:22] yes [16:23] i suppose i worded that poorly, did you mean yes to the former or latter? [16:23] * tseliot missed the "or" [16:24] yes, they are separate problems [16:25] ah okay [16:25] so the first one is what would need such a case statement to flag on the broken model # [16:26] yep [16:29] superm1: if you want you can add a comment in the 1st report and ask upstream directly about adding the quirk [16:29] tseliot, so the thing is i think that's actually a problem on all synaptics touchpads though, is it not? [16:30] i'm on a studio 1340 right now, and the same thing happens, but it's not as frequent because the buttons aren't built into the pad [16:30] superm1: no as there are different kinds of Synaptics touchpads [16:30] but if i touch the top right and bottom left corners of the "pad" it will happen just the same [16:31] superm1: therefore, if the touchpad has multi-finger detection (not emulation), a different solution can be found [16:31] ah [19:56] jbarnes: seen this? xrandr broke in UMS somewhere between git20090630.cec9fc6f and git20090701.1e4784bf https://bugs.edge.launchpad.net/ubuntu/+source/xrandr/+bug/394490 [19:56] Ubuntu bug 394490 in xrandr "xrandr: Configure crtc 0 invalid time" [Undecided,Confirmed] [20:03] Sarvatt: hm, maybe 7e79fc? [20:04] from fdo bug #19578 [20:04] Launchpad bug 19578 in initramfs-tools "initramfs-tools: can't install from scratch" [High,Fix released] https://launchpad.net/bugs/19578 [20:11] actually it might have been something in the xserver update at the same time [20:11] http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branch&id=8d65439d5c950ea01ec8e1e4dd989aff0fb4c3f0 [20:11] ah possible yeah [20:11] uploaded that on july 1st [20:52] yeah for sure it is an xserver problem, sorry about that jbarnes. one guy reverted to xserver-xorg-video-intel_2%3a2.7.99.901+git20090611.6d062e9e-0ubuntu0sarvatt~jaunty_i386.deb [20:52] and still had the problems [20:52] when it was working before [20:53] cool [20:53] should be reported upstream if it hasn't been already [20:58] jbarnes, btw I finally went through all the 8xx reports that confirmed their problem on karmic alpha-2 and sent them up. There were actually fewer than I initially estimated since some were dupes, and others were mis-tested. [20:59] there's another dozen tested/confirmed of 9xx bugs I'll be sending up hopefully today [20:59] if its dri support in KMS dont they need mesa 7.6? [21:00] and then there's another 120 which no one's replied at all, that we can probably just close :-) -- but I'm going to give them a couple more weeks to respond [21:04] bryce: cool [22:40] do you want us to test the newer pixman on edgers server 1.6 branch at all? or any other packages that might have problems getting updated? [22:46] yep for sure this is a problem in xserver 1.6.2 that will pop up when karmic updates to it https://bugs.edge.launchpad.net/bugs/394490 [22:46] Ubuntu bug 394490 in xorg-server "xrandr: Configure crtc 0 invalid time" [Undecided,Confirmed] [22:50] i'm knee deep in a ton of packaging and need to get it uploaded asap and am working at the same time if anyone else wouldnt mind upstreaming it, will try to do it later tonight if not [22:55] uploading mesa on a 15kb/second cellphone connection is fun :) [23:44] There we go. One funky scanout bug filed at bug #398026 [23:44] Launchpad bug 398026 in xserver-xorg-video-intel "[GM45] Default 60Hz display mode drives LVDS incorrectly" [Undecided,New] https://launchpad.net/bugs/398026 [23:51] hmmmm http://launchpadlibrarian.net/28897374/buildlog_ubuntu-karmic-amd64.xserver-xorg-video-intel_2%3A2.7.99.901%2Bgit20090710.4e4b947f-0ubuntu0sarvatt_FAILEDTOBUILD.txt.gz [23:52] http://cgit.freedesktop.org/xorg/xserver/commit/?id=aafcae79d17c1f802bc880d2142af7171fed75d8 ....? [23:53] compiles fine on i386 but fails everywhere else