Desktop freezes

qpoint · July 4, 2008, 11:44am

Hi,

I have a problem with OpenSUSE 11.0. The Desktop freezes a few seconds after logging in. This happens with KDE 3.5.9, KDE 4 and GNOME as normal user and root. I don’t have the problem when using IceWM or Enlightenemnt.

I tried uninstalling Beagle because I read about a beagle-related freezing problem in another thread but this did not help.

My PC has an Intel Core Duo E8200 and a Nvidia 8500 GT graphics card.

Thanks,

Qpoint

buckesfeld · July 4, 2008, 12:11pm

qpoint,

any ReiserFS partitions on the machine?

Uwe

qpoint · July 4, 2008, 1:17pm

No. There are 2 ext3 partitions, one swap partition and one ntfs partition.

Qpoint

buckesfeld · July 4, 2008, 1:54pm

I’d try the latest NVidia drivers from their site. A shot in the dark, yes.

Uwe

qpoint · July 4, 2008, 3:15pm

Still the same problem with the new nvidia drivers.

I installed xfce4 and that works as well although there are no window borders. The freezes still happen with kde3, kde4 and gnome after about 10 seconds.

Cryovac · July 4, 2008, 5:20pm

Any useful info in your ~/.xsession-errors file?

DenverD · July 4, 2008, 6:05pm

was all hardware correctly identified by the install routine?
if using a wireless mouse/keyboard, does it make any difference if you
use wired?
have anything plugged into a USB port?
32 or 64 bit (does it do the same if the other is installed)?
logs give any hints?
you say it freezes after logging in…logging in how? that is are
manually typing in your id/pass? in a GUI (KDE) environment?

–
DenverD (Linux Counter 282315)
A Texan in Denmark

qpoint · July 5, 2008, 8:18pm

As far as i could see all Hardware was detected successfully.
mouse and keyboard are wired but usb. except those no other usb device is plugged in
i am logging in through kdm by entering a username / password.
root is local and the users are from active directory of a windows domain. a few seconds after the desktop loads everything freezes for root and other users.
the version was 64bit. i don’t have access to the PC until in a week’s time. i will try the 32bit version then.
didn’t see anything in the logs but will post them when i’m back at the PC. are there any log files except Xorg.0.log and Xorg.99.log which i should look at?

thanks,

qpoint

DenverD · July 8, 2008, 8:26am

> As far as i could see all Hardware was detected successfully…mouse
> and keyboard are wired but usb. except those no other usb device is
> plugged in

take a look at (careful don’t change anything) /etc/X11/xorg.conf scroll
down to the sections dealing with mouse and keyboard…

under keyboard mine is “Keyboard[0]” because it is generic/wired
but, under mouse mine says: “Logitech USB Receiver”

are your correctly identified there?

you might TRY a shutting down and switching out the usb and pluggin in
non-usb keyboard and mouse…i read a posting somewhere
here about someone having such trouble…but the fact is i don’t know if
the boot routine will detect the change and reset all the system params
needed…hmmmmm…

–
DenverD (Linux Counter 282315)
A Texan in Denmark

qpoint · July 16, 2008, 8:48am

Thanks for the replies.

I have now tried with the 32bit version and with non-usb mouse and keyboard but it’s still the same.

I noticed that I can use XFCE without a problem until I launch nautilus. The machine locks up about 5 seconds after starting nautilus. I get the follwoing message in the konsole:

Initializing nautilus-share extension
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized

** (nautilus:3808): WARNING **: Unable to add monitor: Not supported
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg “net”
Nautilus-Share-Message: spawn arg “usershare”
Nautilus-Share-Message: spawn arg “info”
Nautilus-Share-Message: end of spawn args; SPAWNING

Nautilus-Share-Message: returned from spawn: SUCCESS:
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called “net usershare info” but it failed: ‘net usershare’ returned error 255: net usershare: usershares are currently disabled

Here are the .xsession-errors files for the kde3 and gnome freezes. The first part is the same for all .xsession-errors files:

all files:

/etc/X11/xim: Checking whether an input method should be started.
/etc/X11/xim: user environment variable LANG=en_GB.UTF-8
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_GB.UTF-8 …
There is no default input method for the current locale.
Warning: Type “ONE_LEVEL” has 1 levels, but <RALT> has 2 symbols
Ignoring extra symbols
Warning: No symbols defined for <SYRQ> (keycode 92)
**[There are about 100 of these warnings, but I get them for an working XFCE session as well. ] **

gnome:

SESSION_MANAGER=local/suse:@/tmp/.ICE-unix/3600,unix/suse:/tmp/.ICE-unix/3600
Window manager warning: Failed to read saved session file /home/qpoint/.metacity/sessions/default0.ms: Failed to open file ‘/home/qpoint/.metacity/sessions/default0.ms’: No such file or directory
Failed to get the list of printers from cupsd
MSG: /org/freedesktop/DBus org.freedesktop.DBus NameAcquired
12
Initializing nautilus-share extension
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized

** (nm-applet:3737): WARNING **: nm_object_get_property: Error getting ‘WirelessHardwareEnabled’ for /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files

** (nm-applet:3737): WARNING **: No connections defined

** (nautilus:3724): WARNING **: Unable to add monitor: Not supported

** (nm-applet:3737): WARNING **: nm_object_get_property: Error getting ‘ActiveConnections’ for /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files

kde3:

Unknown splash state: initial
startkde: Starting up…
/usr/bin/iceauth: creating new authority file /home/qpoint/.ICEauthority
kbuildsycoca running…
Invalid entry (missing ‘=’) at /tmp/kde-qpoint/kconf_updateFNcJsa.tmp:1
KMenuBase::setProperty( “frameShadow”, value ) failed: property invalid, read-only or does not exist
KMenuBase::setProperty( “frameShape”, value ) failed: property invalid, read-only or does not exist
QObject::connect: No such signal Kicker::settingsChanged(SettingsCategory)
QObject::connect: (sender name: ‘kicker’)
QObject::connect: (receiver name: ‘animtt’)

qpoint

qpoint · July 16, 2008, 9:36am

I have also now discovered that the system locks up when I am trying to mount a cd on the command line without the xserver running.

qpoint

DenverD · July 17, 2008, 6:05pm

WOW! i am fresh out of ideas…perhaps someone will come along and know
how to help you…i have looked back through all your posts in this
forum and see that i have a few more questions:

has any version of any flavor of SuSE run successfully on your
hardware, ever?

if the answer to that question is that your first attempt with Linux on
that machine with its current hardware and heat profile was openSuSE
11.0 let me ask you to download and try the 32 bit version of openSuSE 10.3

now, be advised it is gonna spend a good deal of time updating and
patching after the from DVD/CD install because there has been a LOT of
bugs squashed since that installation media was birthed…

let it complete all updates and then if you can, don’t start adding
stuff to it it or changing settings right away…see if you can’t use
like it is born a few days and lets see if it will run at least close to
stable…

oh well, even 10.3 is gonna be born with beagle…disable that HOUND
right away…

good luck, and check back (maybe a REAL guru who knows how to make 11.0
run on your machine might come by)

–
DenverD (Linux Counter 282315)
A Texan in Denmark

DenverD · July 17, 2008, 6:13pm

and, another thing…plop that install CD/DVD you have into the slot
before you go to bed tonight…boot from it and when the screen comes
up where you can select install, instead select the memory test
program…launch that and let’er run all night long, AT LEAST…(you can
turn off you monitor to save that electricity)…

you didn’t say how much ram you have but it can takes DAY and DAYS to
touch every part of all the RAM with every test…

but, for sure if you get up the first morning and find errors you then
have a new path to follow to enlightment…

(i’d start by removing all ram, and moving each to a new slot while
carefully making each is inserted absolutely correctly and clicked into
position) and while the case is open check for spider webs or ANYTHING
that might be blocking air flow…both heat and a too weak power supply
could also be part, or all of your problem)

–
DenverD (Linux Counter 282315)
A Texan in Denmark

heseltine · July 23, 2008, 5:03am

I ran into a similar problem with 10.2. I solved it by adding a command at the command line of the boot screen (ie the screen prior to the log-on screen that provides the choice to boot into normal suse or into safe suse.

The command was: noapic

I had to do this every time I logged on. Novel were supposed to have fixed the problem. I have not needed to resort to this command since I moved to 10.3 and now 11.

Regards

Mark

qpoint · August 14, 2008, 7:29am

Hi again.

I have been away from the pc for a while. I finally got around to try again this week and managed to get Opensuse 11 to work.

The problem was related to one of my CDROM Drives (atapi dh16d2p). I noticed that I always had the install CD in the drive when logging in. The result was the same with Opensuse 10.3 ad Fedora. Once I disconnected the CDROM Drive everything worked fine.

Thanks for all the replies,

qpoint