Comment 32 for bug 159594
Revision history for this message
| shanen (Shannon Jacobs) (shanen) wrote | #32 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Well, I can now confirm that the .gnomerc approach did not solve the problem. There was one crash since I added that file. Just to confirm I did it right, here is the cat result:
shanen@
export WINDOW_
I need to run another memory check from GRUB, but I basically don't believe it is hardware. Not sure because I think the best check is running in Windows, and I haven't been running the machine in Windows very much. What I can say is that I have never seen the crash when I was running in Windows, and there was about a year when I only used the machine in Windows. The crashes started only after Ubuntu was installed.
With regards to the recommended "stack/back traces from X", this part seems too complicated for me, though I may tackle it again. However, what I'd much prefer is that I *NOT* spend lots of time trying to fix Ubuntu's problems. It's bad enough when I lose work in a crash--and I'm getting antsy now and feel the pressure to save this before it crashes.
Look. Ubuntu is realizing that a crash has occurred. After the crash it does the disk scan and an extra reboot before it's ready to go again. That's the place where it should trigger it's debugging procedures and install whatever needs to be installed to do fancy traces or backtraces or whatever. If they can't fully automate it, at least the system should report the problem to the Ubuntu people and they should be able to get back to me (assuming there are enough similar crash events to be worth worrying about).
Anyway, time to save it before it crashes again...