RAOF | ayan: Hi again :) | 03:28 |
---|---|---|
RAOF | Also, the contents of /var/log/Xorg.0.log and the output of dmesg are likely to be useful in debugging this. | 03:29 |
ayan | ROAF: hi! | 03:29 |
RAOF | (In a pastebin, if that's not obvious ☺) | 03:29 |
RAOF | ayan: Still here? | 03:49 |
RAOF | Hm, interesting. Compiz seems to have kernel-panicked nouveau, but ssh soldiers on. | 03:50 |
RAOF | Balls. There's an X crasher in -radeon's DRI2 swapbuffers handling again. | 05:58 |
tjaalton | what, have I pushed something to our xorg-server branch.. | 09:42 |
tjaalton | oh, the merge. just the diff post on debian-x@ looks funny | 09:43 |
RAOF | tjaalton: Would you like to test some mesa 7.10.2? :) | 09:45 |
tjaalton | RAOF: sure | 09:45 |
RAOF | I'll push it to git. | 09:45 |
tjaalton | ok, I'll build from there | 09:45 |
RAOF | Oh, yeah. | 09:46 |
RAOF | I'll throw my binaries into http://cooperteam.net/Packages for you! | 09:46 |
tjaalton | cool, clean it up a bit and I can wget the whole dir :) | 09:47 |
tjaalton | i have intel to test it on | 09:47 |
tjaalton | 965 | 09:47 |
=== lilstevie|lagche is now known as lilstevie | ||
RAOF | tjaalton: Now available for your pleasure. i386 & amd64! | 09:50 |
tjaalton | RAOF: thanks, downloading.. | 09:54 |
JanC | I suppose Radeon HD 6950's are supposed to work in natty? | 10:14 |
RAOF | Are, or aren't? | 10:15 |
RAOF | I *think* they are, actually. | 10:15 |
JanC | are | 10:21 |
JanC | somebody complained his new HD 6950 didn't work in 10.10, I told him to try the natty beta live cd | 10:21 |
tjaalton | what happened? | 10:23 |
RAOF | It should be supported by fglrx if nothing else. | 10:23 |
JanC | he's downloading... | 10:24 |
tjaalton | heh, ok | 10:24 |
JanC | I'll let you know ;) | 10:25 |
JanC | download is going to take 3 hours... :-( | 10:26 |
tjaalton | at 64k/s? | 10:27 |
tjaalton | slow.. | 10:27 |
tjaalton | RAOF: mesa seems to not burst into flames here | 10:30 |
RAOF | It also hasn't burst into flames on my radeon card, where the bulk of the changes were. | 10:31 |
RAOF | However, I don't have an r300 to test, and that would be good. | 10:31 |
tjaalton | i do, actually | 10:31 |
tjaalton | at least I think it is one | 10:31 |
RAOF | Anything r300-r500 would do; that's 9600 (I think) - HD 2xxx (again, I think) :) | 10:32 |
tjaalton | yesh, R300 NG [FireGL X1] | 10:41 |
tjaalton | seems to work | 10:47 |
tjaalton | RAOF: ^ | 10:47 |
tjaalton | so, we have libdrm, xorg-server, mesa, libx11 bugfix releases pending.. next thursday is beta2 | 10:51 |
tjaalton | when do we start uploading these?-) | 10:51 |
RAOF | Now, I think. | 10:56 |
RAOF | Although we might not want libdrm 2.4.24 | 10:58 |
tjaalton | ok | 10:58 |
tjaalton | because of then nouveau changes? | 10:58 |
tjaalton | great, the 10.10 installer doesn't recognize my ssd drive | 11:00 |
tjaalton | so I can't test the joystick patch on it | 11:01 |
tjaalton | don't have a spare hd | 11:01 |
tjaalton | tseliot: looks like the dvi-dsub -dongle works after all, just had to make sure it's connected to the right dvi port | 11:08 |
tjaalton | and the "no ssd" problem is a bios failure | 11:09 |
tjaalton | sometimes it doesn't seem to probe it | 11:09 |
tseliot | tjaalton: what is it that makes a dvi port the right port? | 11:15 |
tseliot | does it have to be the 1st dvi connector? | 11:16 |
tjaalton | probably | 11:19 |
tjaalton | dvi cable works on both | 11:19 |
=== yofel_ is now known as yofel | ||
tjaalton | cnd: hey, there's bug 745065 which says that wacom multitouch is broken in natty when it worked in lucid & maverick | 13:43 |
ubot4` | Launchpad bug 745065 in xf86-input-wacom (Ubuntu) "Touchscreen not detected as multi-input (affects: 1) (heat: 6)" [Low,Confirmed] https://launchpad.net/bugs/745065 | 13:43 |
tjaalton | cnd: ideas about that on? | 13:43 |
tjaalton | *one | 13:43 |
cnd | tjaalton, I'll take a look | 13:45 |
tjaalton | cnd: thanks | 13:46 |
tjaalton | RAOF: forgot to push mesa? | 16:17 |
tjaalton | probably too late to ask :) | 16:17 |
=== soreau_ is now known as soreau | ||
lamont | so when I resize a window, it should actually resize, right? | 16:43 |
lamont | (natty beta) | 16:43 |
lamont | though to be fair, that's from a day or 3 ago - dist-upgrading now | 16:44 |
tjaalton | works here | 16:44 |
lamont | tjaalton: uxterm and resize it | 16:44 |
lamont | pulling down the bottom of the window | 16:44 |
lamont | and then resize it again | 16:44 |
tjaalton | lamont: yep | 16:45 |
tjaalton | looks fine to me | 16:45 |
Sarvatt | yep thats busted here too, the xterm doesn't resize | 16:45 |
lamont | I'm using "ubuntu classic" atm | 16:45 |
tjaalton | me too :) | 16:45 |
Sarvatt | ah wait | 16:45 |
Sarvatt | it works on an updated system | 16:45 |
tjaalton | Sarvatt, bryceh_: the archive will beta-freeze on monday :/ | 16:46 |
lamont | let me finish the dist-upgrade and confirm that I'm still broken (hoping I can just go "all better, thanks") | 16:46 |
Sarvatt | 3 day old natty + nvidia blob doesnt resize, fully up to date intel resizes properly | 16:46 |
lamont | and that says 8 minutes | 16:46 |
lamont | intel chipset here | 16:46 |
tjaalton | nvidia here, upgraded yesterday | 16:46 |
lamont | 1 day 25 min uptime here, but that's 12-18 hours post-upgrade | 16:47 |
lamont | 8 min download, nfc how long after that for processing | 16:47 |
tjaalton | xterm hasn't changed | 16:47 |
lamont | the server has | 16:47 |
Sarvatt | compiz has | 16:47 |
lamont | yeah - was just going to say "or has the server..." compiz has | 16:48 |
lamont | gnmoe has | 16:48 |
lamont | gnome even | 16:48 |
Sarvatt | lamont: | 16:48 |
Sarvatt | compiz (1:0.9.4+bzr20110406-0ubuntu1) natty; urgency=low | 16:48 |
Sarvatt | * new upstream bzr tarball: | 16:48 |
Sarvatt | - display/size problems with xterm (LP: #748137) | 16:48 |
Sarvatt | sure is nice when bugs are already fixed :P | 16:49 |
tjaalton | hehe | 16:49 |
lamont | heh | 16:58 |
lamont | ta | 16:58 |
Sarvatt | ok got 7.10.2 on all my machines, now to break things! | 17:00 |
tjaalton | it's indestructible | 17:01 |
tjaalton | i'll upload libx11 1.4.2-1u1 | 17:02 |
tjaalton | 1.4.3 would need newer xutils-dev | 17:03 |
tjaalton | bryceh_: btw, xutils-dev doesn't show on versions-current.html? | 17:03 |
Sarvatt | [ 5.435] | 17:06 |
Sarvatt | X.Org X Server 1.10.0 | 17:06 |
Sarvatt | so friggin fast! | 17:06 |
tjaalton | heh | 17:06 |
tjaalton | ssd luv | 17:07 |
lamont | it does, indeed, appear to be fixed. | 17:09 |
tjaalton | libx11 uploaded | 17:16 |
tjaalton | guinness-time \o\ |o| /o/ :) | 17:19 |
* Sarvatt is jealous | 17:20 | |
Sarvatt | speaking of which, need to put more in the fridge :) | 17:20 |
Sarvatt | darn, new libva in sid but its too late for natty | 17:25 |
Sarvatt | into x-updates it goes | 17:26 |
Sarvatt | hrm 270.40 nvidia driver but its not a normal release, just on the CUDA page | 17:32 |
Sarvatt | tjaalton: looks like the buildds are screwed up? libx11 failed | 17:37 |
Sarvatt | oh nevermind klingon failed | 17:38 |
tjaalton | Sarvatt: great, i get to drop it | 17:42 |
tjaalton | oh | 17:42 |
tjaalton | how the hell did it build here then | 17:43 |
tjaalton | series file was all fail | 17:43 |
Sarvatt | tjaalton: 100_latin_locale_alias.diff101_klingon_locale_alias.diff yea :) | 17:47 |
Sarvatt | 102_double_arrows_Compose.diff is failing after fixing that | 17:48 |
tjaalton | yeah i dropped the double | 17:48 |
tjaalton | err, the other entry i mean | 17:48 |
Sarvatt | klingon is fine | 17:49 |
bryceh_ | tjaalton, ah, +packagebugs changed from "in ubuntu" to "in Ubuntu", which broke my regex. So it has been using an old list of our X packages. Page is being refreshed now. | 17:49 |
tjaalton | bryceh_: great, thanks | 17:49 |
Sarvatt | tjaalton: http://sarvatt.com/downloads/patches/102_double_arrows_Compose.diff | 17:54 |
Sarvatt | oh bah wait | 17:56 |
Sarvatt | 102_double_arrows_Compose.diff was in the series twice.. | 17:56 |
Sarvatt | lol | 17:56 |
bryceh_ | http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/versions-current.html updated | 17:59 |
Sarvatt | https://bugs.launchpad.net/ubuntu/natty/+source/nvidia-graphics-drivers/+bug/752634 -- isn't that the intended behavior from the nvidia blob? I've never used multi monitor on it but fairly sure you have to set up additional monitors through the nvidia-settings gui and not xrandr | 18:15 |
ubot4` | Launchpad bug 752634 in nvidia-graphics-drivers (Ubuntu Natty) (and 1 other project) "[Lenovo T410] Displayport cannot output to a monitor (affects: 1) (heat: 6)" [Medium,New] | 18:15 |
bryceh_ | Sarvatt, yes that's correct | 18:30 |
Sarvatt | phew, only 2 bugs from the cert runs, I was worried :) | 19:11 |
bjsnider | ram usage with the blob in natty is outrageous | 19:14 |
bjsnider | compiz ends up at >500 mb after a couple of days | 19:14 |
Sarvatt | bjsnider: update | 19:14 |
Sarvatt | new cairo should be published now | 19:14 |
bjsnider | well, i ran all updates as of this morning | 19:14 |
Sarvatt | it was uploaded like an hour ago I think | 19:14 |
bjsnider | what is it, libcairo? | 19:15 |
bjsnider | it's not in there so far | 19:16 |
Sarvatt | https://lists.ubuntu.com/archives/natty-changes/2011-April/011061.html | 19:19 |
Sarvatt | hmm should be published, might not be on your mirror yet | 19:19 |
Prf_Jakob | Sarvatt: what are the issues? | 19:21 |
Sarvatt | cairo linking to a 24MB nvidia libGL making the world use outrageous amounts of memory :) | 19:24 |
Sarvatt | https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/725434 | 19:24 |
ubot4` | Launchpad bug 725434 in nvidia-graphics-drivers (Ubuntu Natty) (and 3 other projects) "Nvidia drivers lead to extra memory usage for each process using libGL (affects: 32) (dups: 1) (heat: 188)" [Medium,Won't fix] | 19:24 |
Prf_Jakob | Sarvatt: eh? clearly the Linux VM should handle that well or is allocating a lot of data as well? | 19:26 |
kees | RAOF, bryceh_ : what are your thoughts on bug 738687? should that patch be added to our mesa? | 21:55 |
ubot4` | Launchpad bug 738687 in mesa (Ubuntu) "R600 driver crashes when adding effects in kwin (affects: 2) (heat: 18)" [Medium,Triaged] https://launchpad.net/bugs/738687 | 21:55 |
Sarvatt | kees: thats actually queued up to upload in mesa 7.10.2 whenever RAOF comes on next | 22:04 |
bryceh_ | kees, yeah if it's in the stable tree should be a no-brainer to include | 22:04 |
bryceh_ | kees, how'd you run into this issue? | 22:05 |
kees | cool; thanks guys. how should I mark that bug so it disappears from the sponsorship queue? | 22:05 |
kees | bryceh_: I'm patch pilot, and it was marked for sponsorship | 22:05 |
bryceh_ | oh patch piloting, of course | 22:05 |
bryceh_ | kees, hmm | 22:06 |
bryceh_ | kees, good question... | 22:07 |
bryceh_ | kees, raof probably won't be on until monday and since the freeze comes monday there could be a chance it gets missed | 22:08 |
bryceh_ | kees, so maybe go ahead and sponsor the patch in? | 22:08 |
bryceh_ | sarvatt, what do you think? | 22:08 |
kees | I'd rather not disrupt RAOF's schedule... | 22:09 |
seb128 | bryceh_, the freeze will not be before the european day so there is time for an upload for .au guys | 22:10 |
tjaalton | but RAOF is no core-dev | 22:10 |
kees | okay, I'll just mention in the bug it's scheduled... | 22:11 |
tjaalton | if he could just push the git branch we could upload during the weekend | 22:11 |
seb128 | kees, yeah do that | 22:11 |
bryceh_ | ok well fwiw, I'm on vacation monday7 | 22:11 |
seb128 | it's likely we will clean pending uploads on monday | 22:11 |
tjaalton | I've tested 7.10.2 on r300 and intel | 22:11 |
tjaalton | and RAOF took care of r600 i think | 22:12 |
Sarvatt | i've been running it on 945 and sandybridge | 22:12 |
bryceh_ | kees, sounds like assign to RAOF I guess | 22:12 |
kees | bryceh_: yeah, was just doing that :) | 22:13 |
tjaalton | 965 intel here | 22:13 |
tjaalton | if the archive is frozen at 9:00 UTC on monday, I'll have plenty of time uploading it :) | 22:14 |
ScottK | I've got a Sandybridge laptop that is having what seems to be KDE specific screen corruption issues. Is there a way I can turn specific driver features on/off at runtime to see if I can narrow down where the issue is? | 22:33 |
ScottK | It's not tied to compositing as it happens with that totally disabled. | 22:33 |
bryceh_ | ScottK, modinfo on the drm driver gives the kernel tunables; man intel gives some X driver options; driconf has the mesa tunables | 22:36 |
ScottK | bryceh_: The bug is https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/750964 - Any suggestions on where best to start? | 22:38 |
ubot4` | Launchpad bug 750964 in xorg (Ubuntu) "Screen corruption in menus and titlebars (affects: 2) (heat: 12)" [Undecided,New] | 22:38 |
bryceh_ | ScottK, maybe rerun apport-collect xorg and see if it'll pick up the missing log files | 22:39 |
ScottK | I'll try it. | 22:39 |
bryceh_ | ScottK, if you suspect it's particular to kwin, I'd suggest starting with driconf since that controls 3D and is pretty easy to use | 22:40 |
bryceh_ | also, an important factoid is when the issue first started happening | 22:41 |
ScottK | It happened since I got the laptop on Monday. | 22:41 |
bryceh_ | since if it's a recent regression, then downgrading packages one by one can be a straightforward way to pinpoint things | 22:41 |
ScottK | So no idea how long it's been a problem. | 22:42 |
bryceh_ | ah, so not a regression then | 22:42 |
ScottK | Nope. | 22:42 |
ScottK | Just really, really annoying. | 22:42 |
ScottK | I assume I need to restart X after making changes in driconf? | 22:44 |
bryceh_ | you can also flip on kernel drm debug (drm.debug=0x03) although it'll spew a lot of output | 22:44 |
bryceh_ | yep | 22:44 |
ScottK | Let me play with driconf first. It's got a lot of knobs to turn. | 22:45 |
bryceh_ | yep | 22:45 |
tjaalton | i really don't understand bug 754565 | 22:47 |
ubot4` | Launchpad bug 754565 in xorg (Ubuntu) (and 1 other project) "Regression: shift+click on a launcher icon to open a new application instance gone (affects: 2) (heat: 10)" [High,Triaged] https://launchpad.net/bugs/754565 | 22:47 |
bryceh_ | tjaalton, hum yeah me neither | 22:49 |
bryceh_ | tjaalton, isn't really much of a bug report | 22:49 |
tjaalton | bryceh_: nope | 22:49 |
bryceh_ | tjaalton, close it and tell them we're not mind readers? ;-) | 22:49 |
tjaalton | hehe | 22:50 |
tjaalton | I'll think of something | 22:50 |
tjaalton | there | 22:55 |
ScottK | No luck with driconf | 23:10 |
albert23 | ScottK: the config in freedesktop bug 35808 comment 11 may be worth to test | 23:50 |
ubot4` | Freedesktop bug 35808 in Driver/intel "[SNB] KDE graphic glitches" [Normal,New] http://bugzilla.freedesktop.org/show_bug.cgi?id=35808 | 23:50 |
ScottK | albert23: Thanks. | 23:50 |
Sarvatt | ScottK: also if it doesn't and you want to see if it does with updated drivers - https://launchpad.net/~sarvatt/+archive/gold | 23:52 |
ScottK | Thanks. | 23:52 |
ScottK | Mine is a 6320 (vice 6420) so it's very close. | 23:53 |
ScottK | I don't have the kms issue he has. | 23:53 |
Sarvatt | i've got 2 6420's here, it must really be KDE specific | 23:53 |
ScottK | Ah. That did it. | 23:56 |
ScottK | Option "DebugFlushBatches" "True" and it's all better. | 23:57 |
ScottK | Sarvatt: I do believe it's KDE specific. Even non-KDE apps in a KDE session are OK. | 23:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!