/srv/irclogs.ubuntu.com/2009/04/12/#ubuntu-x.txt

superm1oh i should look at what i was reverting ;) it was a comment.  so it must be a commit near there then, and the comment threw bisect off00:34
=== maxb_ is now known as maxb
=== albert231 is now known as albert24
=== albert24 is now known as albert23
tjaaltonbryce: assign me to the bugs, and I'll have a look16:45
tjaaltonit's really unfortunate that these regressions happened, but maybe the 7.4 branch has fixes for them already16:46
tjaaltons/me to the bugs/the bugs to me/16:47
tjaaltonI'll make sure upstream knows about these if they're not fixed already16:52
tjaaltonit's high on my list since  i've been so vocal to follow upstream on this :)16:54
brycetjaalton: 359392 is the master bug for this19:40
brycetjaalton: other possibly related bugs are at https://wiki.ubuntu.com/X/Bugs/IntelDriver19:41
brycenotice all the i965-specific freezes starting from early april19:41
tjaaltonok, I'll hunt them once I get back home19:48
bryced805c820: fix potential recursive locking deadlock in _mesa_HashWalk() maybe?19:49
brycethanks, we're heading out for easter brunch.  bbiab19:49
knomehello.19:52
tjaaltonyeah if it's 965 related I should be able to reproduce and test potential fixes19:52
knomeon hardware drivers, nvidia-180 says first that another version of the driver is in use19:53
knomeand when i activate it, it says that it is disabled, but still in use19:53
knomewhat can i do to activate it?19:53
tjaaltonknome: upgraded from intrepid?19:58
knometjaalton, yes.19:58
tjaaltonso is 180 installed now?19:58
knomeit is19:58
tjaaltonis it used? (look at the logfile)20:02
knomewhich logfile?20:02
tjaaltonXorg.0.log20:02
tjaaltondmesg should tell as well20:02
superm1checking dpkg -l | grep nvidia would probably be useful too to make sure none of the 177 bits are still installed20:03
knometjaalton, LoadModule: "nvidia"20:05
knomesuperm1, there is even some 96-bits20:05
tjaaltonknome: the version string would tell which version is used20:05
knometjaalton, 180.4420:06
knomeafter boot jockey insists that 180 isn't used.20:07
knomeand can't activate20:07
tjaaltonso it's lying20:07
knomesupposedly20:07
knome3d is working fine, though.20:07
knomejust wondering20:07
tjaaltondunno why20:07
knomeshould i file a bug?20:08
tjaaltonnot sure20:09
tjaaltonmaybe :s20:09
tjaaltons/s/)/20:09
knomewhich files should i include?20:10
knomeand against which package?20:10
tjaaltonuse ubuntu-bug20:14
tjaaltonjockey I suppose20:15
knomefiled bug #36016120:23
ubottuLaunchpad bug 360161 in jockey "Jockey can't activate a driver even if Xorg.0.log tells it used" [Undecided,New] https://launchpad.net/bugs/36016120:23
knomemy screen also goes partly black now and then20:26
knomeeg. if browsing web with firefox, part of the window background might become black.20:26
knomeis this known?20:27
knomethere is no exact steps to reproduce.20:27
knomethis *might* have something to do with my gtk theme, but i'm very sceptical about that.20:28
tjaaltonhaven't seen it myself20:28
knomeright20:28
knomei'll try to get a screenshot of it once it happens again20:29
knomeor a photograph20:29
=== james_w` is now known as james_w
andresmujicabryce: please check bug #360193, i was able to reproduce the freeze using mesa 7.3 and the application alarm-clock21:45
ubottuLaunchpad bug 360193 in ubuntu "x server freezes consistently" [Undecided,New] https://launchpad.net/bugs/36019321:45
bryceandresmujica: interesting.  My gut suggests it may be a separate freeze issue23:31
bryceafter all, we already have about 20 known freezes before we even got to april 3rd.  ;-)23:32
brycefrom what I've gathered, the april-3rd freeze is not triggerable by a specific user action, it just comes on "randomly" (gods I hate that term!)23:33
brycewhich is why my gut thinks that freezes that are reproducible easily with a specific application, and that aren't resolved by going 7.4->7.3, really sound like a separate issue23:34
andresmujicahi bryce23:34
andresmujicawell23:34
andresmujicai'm testing a lot23:34
brycegood! :-)23:34
bryceyeah I will try reproducing on my laptop too23:34
andresmujicaand found 2 freeze actions23:34
andresmujicaand 1 "natural" freeze with mesa 7.323:34
andresmujicasudo apt-get install alarm-clock23:34
andresmujicaand then start alarm-clock23:35
bryceoh, also keep in mind there are issues that 7.4 actually fixes, it's not all just new bugs ;-)23:35
andresmujicayour laptop is frozen23:35
andresmujicassh from a remote machine and kill the alarm-clock 23:35
bryceok23:35
andresmujicaand get your system back23:35
brycehmm23:35
andresmujicaaslo with strace gcalctool or strace firefox23:35
bryceok that sounds like a very different issue, that's not a classic X freeze23:35
andresmujicayeap23:35
andresmujicai believe a focus thing23:35
bryceif you can freeze on strace glxinfo, there's a known bug on that23:36
andresmujicai' m waiting to get another "natural" freeze to kill app per app23:36
brycecool23:36
bryceok, switching computers23:36
andresmujicahmm nop freeze with strace glxinfo23:36
andresmujica1just got the freeze again, and effectively is not the same as the alarm-clock one, as i cannot recover the system by killing apps... 23:54
andresmujica1the bad thing is i'm using mesa 7.3 23:54
andresmujica1and xserver-xorg-core/xserver-common 1.6.0-0ubuntu123:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!