[08:24] looks like the DPMS issues should be solved by pulling c1d901d723 to the server [09:01] lool: do you have something for the xorg-server git? [09:02] tjaalton: Yes but needed bryce to push first [09:02] he did that already [09:02] Ah cool let me rebase and puhs [09:02] ok [09:06] tjaalton: Pushed [09:06] ah no [09:08] now it's pushed [09:08] ce13d12..80a6590 [09:08] tjaalton: I shall build, test, and upload it now [09:09] tjaalton: We don't do ubuntu tags right? [09:09] lool: nope [09:31] lool: hah, I was about to add the same :) [09:31] the same patch I mean [09:33] tjaalton: Well I had commented on bug report that I had it ready to avoid duplication :-) [09:35] lool: I was following the wrong bug then :) [09:49] isn't that patch in 1.6.4? [09:56] jcristau: Apparently we're still at 1.6.3 [09:56] 1.6.4 might make it post beta, but I wouldn't want to pick up a new upstream today myself; perhaps bryce or tjaalton can though [09:57] tjaalton: Built, tested, debdiffed, uploaded [09:57] So I'm logging in with startx [09:57] And on the second login I don't have keyboard or mouse [09:58] i think i've seen that, too [09:58] i.e. my system boots, gdm starts, I can move the mouse, I stop gdm and startx, I can use mouse and keyboard, I logout, startx, and then I'm stuck [09:58] the system is working fine though [10:15] confirmed it's in 1.6.4, fwiw. you'll probably want to update to that before release, as it's all bugfixes [10:18] tormod, could you also observe gtkperf differences between KMS and non-KMS on ATI as discussed a few days ago? [10:18] diverse_izzue: yes, I made the wiki page [10:18] link? [10:19] https://wiki.ubuntu.com/X/RadeonKMS [10:20] brilliant, i'll add my values when i get around doing that [10:22] you can see my gtkperf numbers are not so different on DRI/DRI2, but the broken glblur is bad [10:24] yeah. for me it's really perceived speed which is lacking - the system is no fun to work with under KMS [10:25] did you fullscreen the glblur? [10:26] no I didn't [10:28] are the upstream people hanging out on some channel? [10:36] upstream radeon is on #radeon of course :) [10:49] have you bothered them with that issue already? [10:51] diverse_izzue: which issue in particular? [11:21] jcristau: The IDLETIME/DPMS change is in 1.6.4 you mean? [11:21] * lool filed LP #438044 about the no kbd+mouse issue [11:21] Launchpad bug 438044 in xorg "No keyboard and mouse on second startx login" [Undecided,New] https://launchpad.net/bugs/438044 [11:22] lool: yeah [11:23] all logs in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/438044 show the devices being added. which one corresponds to the bug? [11:23] Launchpad bug 438044 in xorg "No keyboard and mouse on second startx login" [Undecided,New] [11:40] tormod, the reduction in drawing speed, especially the gtkperf result [12:55] sweet, DisplayPort is full of JustWork goodness \o/ [19:57] good afternoon [19:58] the most recent x-swat intel driver seems to die on resume from sleep (suspend to ram) - I'm just curious whether the updates in the edgers ppa has corrected that or not? is there a changelog somewhere I can query instead of bugging people here? [20:00] tzanger, git log [20:01] tzanger, and honestly if you're still running the xswat git snapshot rather than what we're shipping in karmic, you should be bugging folks on #intel-gfx, not here. [20:01] ahh, okay, I wasn't sure where to go [20:01] I'm running 9.04 so I didn't think it'd be prudent to try and run drivers from a newer release [20:08] what's the preferred way to do synaptics config in karmic? [20:08] xorg.conf? hal? something else? [21:13] hmm, the #intel-gfx people suggest I check to make sure the GPU's not being posted on resume, but when I asked how one goes about checking that and preventing it if so, he suggested asking ubuntu-people, so I'm asking here... [21:31] tzanger, try: grep vbe-post /var/log/pm-suspend.log [21:32] hmm, I have a vbetool but not a vbe-post, is there a special package for that [21:35] hmm the log is just a text file concatenating a few sources that look like they came from /proc, is that expected? [21:35] nevermind I missed your grep command [21:36] no sign of vbe-post in the log file === seb128_ is now known as seb128