Ok, so this is happening again in 10.10. I've noticed a few more things though:
1. This bug sometimes causes X to crash. I've experienced it a few minutes ago. I had resumed from suspend maybe 4 hours ago and worked on a bunch of things in Emacs, Firefox and Evolution and a few other X clients (like xpdf). Then I turned to Open Office writer to check something in a document. The document was very slow to scroll. Writer was in effect exhibiting the symptoms described earlier in this bug report.
After paging up maybe 4 or 5 times, X crashed.
The only X client started before the suspend-resume cycle and which showed any trouble was Open Office. (Emacs, FF, Evolution were also all started before the suspend-resume cycle: no problem with them.)
2. The soffice.bin process remained running from the previous X session. Note that everything else which was X related died when the X session died. Only, soffice.bin remained. Running oowriter from the command line does nothing. The old soffice.bin must be killed before OO can be used again.
3. I checked to see whether the HD was being accessed abnormally (e.g. thrashing) but did not see anything abnormal there.
Why did I not experience X crashes before? I think the answer is just that in the past, I would very quickly close OO as soon as I experienced the bug so I was removing the opportunity for a crash. This time, I insisted on scrolling to a bit of text I needed to cut and paste to emacs. I thought I was really close to the passage I wanted to cut and paste but I was wrong and X crashed before I could get there.
It may also have to do with the document I was scrolling. This is the largest OO document I have. It also happens to contain about as much Chinese as English. So of all the documents I work with this is the one which is most taxing on oowriter.
Here are the results of apt-cache policy on the usual suspects:
Ok, so this is happening again in 10.10. I've noticed a few more things though:
1. This bug sometimes causes X to crash. I've experienced it a few minutes ago. I had resumed from suspend maybe 4 hours ago and worked on a bunch of things in Emacs, Firefox and Evolution and a few other X clients (like xpdf). Then I turned to Open Office writer to check something in a document. The document was very slow to scroll. Writer was in effect exhibiting the symptoms described earlier in this bug report.
After paging up maybe 4 or 5 times, X crashed.
The only X client started before the suspend-resume cycle and which showed any trouble was Open Office. (Emacs, FF, Evolution were also all started before the suspend-resume cycle: no problem with them.)
2. The soffice.bin process remained running from the previous X session. Note that everything else which was X related died when the X session died. Only, soffice.bin remained. Running oowriter from the command line does nothing. The old soffice.bin must be killed before OO can be used again.
3. I checked to see whether the HD was being accessed abnormally (e.g. thrashing) but did not see anything abnormal there.
Why did I not experience X crashes before? I think the answer is just that in the past, I would very quickly close OO as soon as I experienced the bug so I was removing the opportunity for a crash. This time, I insisted on scrolling to a bit of text I needed to cut and paste to emacs. I thought I was really close to the passage I wanted to cut and paste but I was wrong and X crashed before I could get there.
It may also have to do with the document I was scrolling. This is the largest OO document I have. It also happens to contain about as much Chinese as English. So of all the documents I work with this is the one which is most taxing on oowriter.
Here are the results of apt-cache policy on the usual suspects:
compiz-core: us.archive. ubuntu. com/ubuntu/ maverick- updates/ main amd64 Packages dpkg/status 0.8.6-0ubuntu9 0 us.archive. ubuntu. com/ubuntu/ maverick/main amd64 Packages
Installed: 1:0.8.6-0ubuntu9.1
Candidate: 1:0.8.6-0ubuntu9.1
Version table:
*** 1:0.8.6-0ubuntu9.1 0
500 http://
100 /var/lib/
1:
500 http://
openoffice. org-core: us.archive. ubuntu. com/ubuntu/ maverick/main amd64 Packages dpkg/status
Installed: 1:3.2.1-7ubuntu1
Candidate: 1:3.2.1-7ubuntu1
Version table:
*** 1:3.2.1-7ubuntu1 0
500 http://
100 /var/lib/
nvidia-current: us.archive. ubuntu. com/ubuntu/ maverick/restricted amd64 Packages dpkg/status
Installed: 260.19.06-0ubuntu1
Candidate: 260.19.06-0ubuntu1
Version table:
*** 260.19.06-0ubuntu1 0
500 http://
100 /var/lib/
xserver-xorg: us.archive. ubuntu. com/ubuntu/ maverick/main amd64 Packages dpkg/status
Installed: 1:7.5+6ubuntu3
Candidate: 1:7.5+6ubuntu3
Version table:
*** 1:7.5+6ubuntu3 0
500 http://
100 /var/lib/