On 07/17/2013 03:28 PM, Craig McCluskey wrote:
goodwin wrote:
On 07/15/2013 09:33 PM, Craig McCluskey wrote:
>
I was browsing on a web page, clicked a link, and my monitor went black.
A few seconds later the BIOS boot screen started up. I had this about a
week ago, but I think I was running 2.17.1 then.
At any rate, I am not a happy camper.
Any suggestions on how to fix this? I don't like having to take the time
to recover my computer and check that the files have not been corrupted
by the unceremonious shutdown.
Also, anyone know why e2fsck clears orphaned inodes instead of attaching
them to the appropriate lost+found directory?
This question is beyond the scope of this group - judging from the
responses so far, you may want to check this in a linux group or SM dev
ng.
what makes you think this is a SM issue?
Twice having a crash the instant I clicked on a web browser link.
This doesn't indicate SM necessarily. I've dropped gnome some time ago
and currently use e17. It crashes on its own when it feels like it in
whatever app. It recovers itself quite nicely as well. I just haven't
had the time to ferret this out and it is infrequent enough I don't feel
the need. Point being, what you describe can be caused by any number of
things - s/w or hardware - and you haven't provided any useful
information as of yet to aid in diagnosis.
Distro?
video card?
using compiz?
what desktop you using?
Gnome
what do your logs say?
There is no information in /var/log/messages about the crash.
then .xsession-errors?
The entry at Jul 15 16:43:51 is a message about the firewall rejecting a
connection.
this certainly isn't directly SM related...
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
