I just installed Suse 11.0 and am in the process of setting up my Desktop such as themes, toolbars and etc. Even using Yast for updates, the Desktop suddenly freezes and I have to hit the reset or Power button to reboot the system. Is anyone else having similar problems? Any Ideas to solutions? I’ve got to be missing something, I don’t think they would release the product to the general public with this constant issue.
Thanks in advance for any input…
How often desktop freezes? Does it happen doing something particular procedure or is seemingly random? And is it complete computer freeze or only X e.g can you tap Ctrl-alt-backspace to restart X or not.
It freezes randomly under my own user ID. Doesn’t seem to be happening under root. Using Ctrl+Alt+backspace is new to me, I’ll give it a try and see what happens. I’m also going to delete my user ID and add it back in again. Then I will have to reset all of my personal choices again. Perhaps it is corrupted in some way? I’ll find out…
Thanks
Also, please show the output of these two cmds:
uname -a
df --print-type
Sorry it took so long to respond. For the last couple of hours I haven’t been able to get back on to the forum. As I said eariler, I deleted the user account and re-added it. Unfortunately, the KDE GUI is still hanging a lot. The Ctrl + Alty + Backspace the reset x did not work as there isn’t a response to anything once it hangs.
Below is a listing for the two command you requested:
uname -a Linux www 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux
df --print-type Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/mapper/system-root
ext3 10321208 340052 9456868 4% /
udev tmpfs 1557384 116 1557268 1% /dev
/dev/sda1 ext3 202219 18694 173085 10% /boot
/dev/mapper/system-home
ext3 154818540 199152 146755068 1% /home
/dev/mapper/system-local
ext3 20642428 176200 19417652 1% /local
/dev/mapper/system-opt
ext3 10321208 594736 9202184 7% /opt
/dev/mapper/system-srv
ext3 20642428 176320 19417532 1% /srv
/dev/sdb1 vfat 19541504 16 19541488 1% /storage
/dev/mapper/system-tmp
ext3 10321208 155552 9641368 2% /tmp
/dev/mapper/system-usr
ext3 20642428 2675984 16917868 14% /usr
/dev/mapper/system-var
ext3 10321208 344816 9452104 4% /var
Thanks for the help
Jim
FYI, I did discover that the problem was a wireless keyboard and mouse I was using was causing all of the lockups. Since I have replaced them with a standard PS2 Keyboard and mouse it hasn’t locked up since…
[reason for questions: the forum is littered with folks having random
freeze problems…i’m looking for a similarity in the causes/cures…]
are the wireless ones a major brand? were they correctly detected during
install?
did you use those same keys/mouse with SuSE 10.x (or before) with no
problems?
and, if so, do you happen to have a copy of the /etc/X11/xorg.conf file
from the working ok pre-11.0 system…
that is, maybe a bug was introduced in 11.0 (maybe in the install
routine, maybe in the hardware detection routine, maybe in…) which
caused your problem…and, if so, that bug probably needs to be squashed…
also wonder if you happen to use reiser file system, or if beagle was
running when you had the problems, but maybe is not now…
–
DenverD (Linux Counter 282315)
A Texan in Denmark
I tried to answer your questions earlier but it looks like they were lost when I posted them. More than likely a user error. I’ll give it a try again!
are the wireless ones a major brand? were they correctly detected during
install?
They are both made by Microsoft. During installation, they installed with out any problems.
did you use those same keys/mouse with SuSE 10.x (or before) with no
problems?
Yes I have used them with Windows and a couple of other Linux distros without any problems including Suse 10.2 and 10.3.
and, if so, do you happen to have a copy of the /etc/X11/xorg.conf file
from the working ok pre-11.0 system…
I “may” have a backup where I can restore it to another disk but I think I reformatted the old drive and have used it for other things. I’ll look for the backup but have my doubts that it is still there by now. I’ll let you know
also wonder if you happen to use reiser file system, or if beagle was
running when you had the problems, but maybe is not now…
I’m using ext3 and LVM. Initially, beagle was running and seemed to be hogging to much resources so I disabled it early on in my debugging process and haven’t turned it back on. But the lockups continued until I changed the Keyboard and Mouse.
Ever since I installed the PS2 Keyboard and USB Mouse they system has not locked up since. I did have a couple of KDE Crashed, popups since then, but just dismissed them as I was very busy at the time and didn’t pay to much attention to them. If they re-occur I will document them and get them to you.
Hope this is some help.
Jim Taitt
jtaitt@gmail.com
Anyone find a solution to this problem?
I am using a Kyocera wireless broadband card, which seems to be causing the problem. Here is generally what happens:
I connect to the internet using Kinternet, then open Firefox and begin browsing. My connection speed begins to slow down, then stop completely. At some point the system will lock up, with the keyboard and mouse being non-responsive, and the lights on the keyboard flashing on and off. The only way to fix the problem is to disconnect the power.
I have not checked my system log yet but am considering doing that. I also plan to install Gnome and see if the problem occurs there too.
I’m leaning toward Firefox as the culprit here.
Thanks for all the helpful responses.
If I’m still in a good enough mood when I finally do figure out the solution, I might even share it with the rest of the board.
I’ve got the same problem. OpenSuSE 11.0, KDE 3.5, Firefox 3.x, and Microsoft ‘Wireless’ Keyboard and Mouse.
Display goes blank. Does not respond to ping/SSH etc. Only option was to reset.
Initially I was led to believe it might be Beagle/Kerry related, so I uninstalled them. Problem seemed to go away for a day. But it happened again. Only apps running were Firefox, openoffice 3.1. I was just going through the menus and the screen dissappeared. System was still available through remote SSH sessions this time.