I had been running 32bit opensuse. I’ve just re-installed w/ 11.2 64 bit, and am having crashes a couple of times a day. Always have Amarok, Amsn and Firefox open. I usually have more apps than that open, but I’ve always got those 3, and it has crashed w/ only those 3 open.
Everything freezes, audio starts skipping. The mouse still moves, but nothing else works. keyboard commands are unresponsive.
I’ve let it sit for 5 minutes or more like this, and it never recovers. I restart, and it’s good.
Can you advise me of any tests to perform, or logs to look at? I tried var/log/messages, and don’t see anything unusual, but I’m not the most experienced there… (never had trouble in the past, so never needed to learn!)
turn off desktop effects, and see if that alone solves the problem…
if not, then with desktop effects off, turn off Firefox also…(use,
for example, knoqueror instead)…
or, leave Firefox running (and with desktop effects off) use Banshee
(or similar) instead of Amarok…
continue until you find the bad actor, OR the combo of death…
hmmmmm…you had 32 and you installed 64, keeping your /home (i guess)
which probably has some settings in configs for 32…could be a
problem to sort though…TRY this, in YaST add a new user (maybe
named something like Test1) give Test1 a good stong password and then
log out and then back in as Test1…crank up firefox, etc etc etc etc
and see if you have the same problems or not…if you don’t then it
is almost guaranteed that something is different (and wrong) in
/home/[you]/.* compared to the working ok /home/Test1/.*
with a LOT of patience and a tool like diff you can probably find the
little bad spot…otherwise . . .
–
palladium
down up hours iso
4.33G 4.98G 48 11.2 DVD (64)
692M 1.06G 30 11.2 GNOME LiveCD (64)
693M 748M 34 11.2 GNOME LiveCD (32)
Ok thanks. i didn’t save my home DIR, so it’s just all 64bit from the ground up, now. I only mentioned it, because I used the exact same apps, only the 32 bit versions, for years w/out a single crash! I was hoping there was some magic log file somewhere that still managed to get written after a crash… (memory dump or something) but I’ll just use some good old fashioned detective work to get it sorted…
wicked1 wrote:
> but I’ll just use some good old fashioned detective work to get it sorted…
understand…and, maybe someone else will pop in here with a log file
to try…
as you go on detecting, you might wanna add a new user anyway, and see
if the problem is also there…at least, that way you rule out it
being a single user’s problem…