I did some testing and found that I was unable to reproduce the bug, even after uninstalling 3.7.3-1 and returning to 3.2.35-2. Gnome3 loaded; Opera and Tor both launched. It's as if running 3.7.3-1 cleared some sort of logjam. I then tried 3.4.4-1 ( http://snapshot.debian.org/archive/debian/20120627T101242Z/pool/main/l/linux/linux-image-3.4-trunk-amd64_3.4.4-1~experimental.1_amd64.deb<http://snapshot.debian.org/package/linux/3.4.4-1~experimental.1/#linux-image-3.4-trunk-amd64_3.4.4-1:7e:experimental.1>) and found it to work as well, but I don't know what you would be able to glean from that. I'll keep running 3.2.35-2 for the time being to see if the bug pops up again. Thanks again.
~Tim G. On Sat, Feb 2, 2013 at 7:24 PM, Tim Graham <autofyr...@gmail.com> wrote: > Thanks guys! > > I'm sorry to report that kernel 3.7.3-1 ( > http://packages.debian.org/experimental/linux-image-3.7-trunk-amd64) > seems to have cleared up these problems! :-D > > Gnome3 loads as it should. Opera and TorBrowser both launch. Chromium has > not yet shown any signs of trouble. If you'd like, I can try plugging in > the kernels at http://snapshot.debian.org/package/linux/ to see which > ones, if any, reproduce the bug. > > ~Tim G. > > > On Thu, Jan 31, 2013 at 1:52 PM, Jonathan Nieder <jrnie...@gmail.com>wrote: > >> Hi Tim, >> >> Tim Graham wrote: >> >> > Your assumption was correct. I was using 3.2.35-2. >> > >> > I tried >> > >> http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-486_3.2.35-3~jcristau.1_i386.deb >> > first. >> > Then I tried >> > >> http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb >> > . >> > >> > Neither of these affected my situation, but I will be on the lookout for >> > future kernel upgrades. >> >> Thanks. >> >> One more test and then we can take this upstream and in the hands of >> friendly AMD folks: >> >> Please test a 3.7.y kernel from experimental. Hopefully it reproduces >> the bug, in which case please report this at bugs.freedesktop.org, >> product Mesa, component Drivers/Gallium/r600 and let us know the bug >> number so we can track it. >> >> If it doesn't reproduce the bug, then our next step would be to sift >> through the versions at http://snapshot.debian.org/package/linux/ >> to find the version that fixed it. So in either case we have a way >> forward. >> >> Sorry for the trouble, and hope that helps. >> >> Regards, >> Jonathan >> > >
