I'm the original reporter for this bug, more than 3 years ago, on Dapper. I don't want to criticize anyone, but it amazes me to see that this bug is still causing problem on Karmic...
Here's what I think:
It's OK to point out that Babara's problem was caused by a buggy Chromium installation. But still, a Ubuntu installation should not allow any buggy program to cause a disk saturation with an out of control growing .xsession_errors file... It has to be some better ways to deal with error logs caused by a faulty program, no?
Also, we should keep in mind that emptying this file on session startup may not be sufficient. For those of us who use suspend (sleep) on laptop, a session may last forever (well, almost...), so the file will never be cleaned up on time to prevent serious problems when a buggy program starts to create error logs.
I'm the original reporter for this bug, more than 3 years ago, on Dapper. I don't want to criticize anyone, but it amazes me to see that this bug is still causing problem on Karmic...
Here's what I think:
It's OK to point out that Babara's problem was caused by a buggy Chromium installation. But still, a Ubuntu installation should not allow any buggy program to cause a disk saturation with an out of control growing .xsession_errors file... It has to be some better ways to deal with error logs caused by a faulty program, no?
Also, we should keep in mind that emptying this file on session startup may not be sufficient. For those of us who use suspend (sleep) on laptop, a session may last forever (well, almost...), so the file will never be cleaned up on time to prevent serious problems when a buggy program starts to create error logs.