Dale wrote:
Dale wrote:
Let me add some more confusion. I'm in KDE right now. I took the
sides off and blew out a VERY little bit of dust and replugged
things, video card, mobo power cables and such as that. I also
booted to the newly created .kde directory instead of my old one.
This is the old install tho. I logged in with nothing running, blank
session, and then took a nap. I got up a few minutes ago and KDE is
still running. I opened Kpat, card game, and played a little of it.
After a few minutes, I opened Seamonkey and am typing as you can
see. Same kernel, same nvidia, same packages and same hardware.
I did notice something a bit ago but have not posted since I noticed
it. It seems to crash when I open Konsole as root. I have my menu
set up to run it as root and that is where I do my sync and updates.
As soon as the window pops up, my mouse pointer freezes. I thought
it was a coincidence until now. After I send this reply, I'm going
to open Konsole and nothing else. I want to see if it does it
again. Since it has been running this long with Konsole closed, it
would be odd if it fails when I open that up here shortly.
I have tried to eliminate things one by one. I tried a different
kernel before I ever posted anything but I'm not sure I mentioned
it. Doing that is almost like breathing. If I run into issues, I
try a old kernel first. I have also tried both nvidia drivers that
are in portage with a few different kernels. As mentioned, I also
tried a fresh install as well. This makes me question hardware but
since everything has to work together, who knows where to start.
Could it be the extra ram that Konsole accesses? Could it be a bad
instruction that the CPU doesn't like? Could it be the video card
trying to redraw the screen? Lots of questions with few answers.
Well, I'm going to send this then open Konsole. See if it locks up
again.
Dale
:-) :-)
I forgot to answer one question you had. Yes, this is my new rig that
was built a while back.
As I was suspecting, I opened Konsole after sending the last message
and it locked up real good. I did manage to get the SysReq keys to
work tho. I opened Konsole from the menu, the password window popped
up and I typed in my root password. After that, the Konsole window
popped up and as soon as I touched the mouse, lock up.
After I rebooted and logged in, I wanted to see if it could be a bad
memory issue or even the video card itself. I opened a HD video,
Asteroid Galaxy Tour, and played it back to back. It never missed a
beat. I'm going to avoid Konsole and see what all else I can open
until it fails again. I'll post back what happens.
Any of you gurus figure out why my system hates to open Konsole as
root? I might add, I used konsole from inside Fluxbox with no problems.
Dale
:-) :-)
A little more info. After my last message, I opened Firefox. It locked
up. That runs as a regular user of course. So, I wanted to test a
theory. I logged into Fluxbox after my reboot. I opened Firefox and it
locked up. Nothing else was running. My first lock up in Fluxbox!!
So, Firefox will lock up in BOTH KDE and Fluxbox. What do Konsole in
KDE, Fluxbox in both KDE and Fluxbox have in common? Keep in mind,
Konsole works fine in Fluxbox.
I thought of something tho. I upgraded glibc a while back. I had some
KDE updates and a Firefox update just a little bit before this
happened. Could this be related somehow?
Also, when Firefox locked up, I went to my old rig and tried to login to
this rig. The network connection was dead. So, that time at least, it
was a serious lock up. Sometimes the SysReq keys work, sometimes not.
Thoughts? Anyone think of anything that could cause this?
Dale
:-) :-)
