Mailinglist Archive: opensuse (3065 mails)

< Previous Next >
[opensuse]
  • From: Richard Ibbotson <richard.ibbotson@xxxxxxxxx>
  • Date: Sun, 1 Jun 2008 20:45:08 +0100 (BST)
  • Message-id: <alpine.LSU.1.10.0806012036070.23256@xxxxxxxxxxxxxxxxxxx>
AArgghh !!

Oh... I feel much better now :)

Probably best to include the full saga here so that someone might be
able to help. Recently my 32-bit hardware died due to old age. The
1.2 Ghz Athlon just couldn't make it through the day any more. I had
to switch to AMD64 hardware even though I didn't want to. Nothing but
64-bit hardware available. Little did I know that my adventure
through the world of 64-bit Linux software was going to be more hard
work than a trip that I once did to the bottom of Everest with very
little food in my backpack. I kicked off with Debian Etch AMD64. It
just about worked but no printer drivers forced me to try various
versions of Kubuntu and Ubuntu. No, printer drivers for my Samsung
printer in there either. Crashing kernels. Crashing KDE. Crashing
Gnome. Bits of ceiling falling off. Time to go and see the doctor
for some of those strange tablets.

So, next up (after wasting time with Fedora - screams loudly) I tried
OpenSuSE 10.3 for AMD64. Worked first time. Printer prints. Rock
solid. Nvidia graphics card just works as well.

Until last Friday when after an update with YaST(2) I played a game of
Doom on my workstation. At the end of the game it exited abnormally
and the KDE screen came back up at about 640x480 resolution. Should
have been about 1400x1280 (or similar). Couldn't fix it. After a
reboot I find that X-windows and KDM/KDE try to start and then fall
over. Back to the black screen and command line. I use Alpine for
mail and so for me it's not too bad. However, the usual things like
OpenOffice.org and Inkscape are no longer accessible.

Can anyone out there suggest what could be wrong and how to fix it ?
I've tried the OpenSuSE rescue disk. It just bombs out. Can't start
YaST. Can't access and library in /usr/lib64/ since the update which
means that no part of the system can start or do anything. I can run
smart and update the system with that but even that complains and not
being able to access /usr/lib64/. Perhaps a chmod or chown in
/usr/lib64 might be of some use ? Below is the output of
.xession-errors............................



xauth: creating new authority file /home/richard/.serverauth.3878


X Window System Version 7.2.0
Release Date: Tue Jan 22 17:03:42 UTC 2008
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux sheflug 2.6.22.17-0.1-default #1 SMP 2008/02/10
20:01:04 UTC x86_64
Build Date: 22 January 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 27 22:11:06 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
No profile for user 'richard' found
===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) =====
MainThread 2008/05/27 22:11:08.8916 (sabayon-apply): Fatal exception! Exiting
abnormally.
MainThread 2008/05/27 22:11:08.8923 (sabayon-apply): Traceback (most recent
call last):
File "/usr/sbin/sabayon-apply", line 99, in <module>
sys.exit (util.EXIT_CODE_FATAL)
SystemExit: 1

===== END MILESTONES (/usr/sbin/sabayon-apply) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) =====
MainThread 2008/05/27 22:11:08.8916 (sabayon-apply): Fatal exception! Exiting
abnormally.
MainThread 2008/05/27 22:11:08.8923 (sabayon-apply): Traceback (most recent
call last):
File "/usr/sbin/sabayon-apply", line 99, in <module>
sys.exit (util.EXIT_CODE_FATAL)
SystemExit: 1

===== END RING BUFFER (/usr/sbin/sabayon-apply) =====


This configuration for the debug log can be re-created
by putting the following in ~/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
/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.
kde-config: error while loading shared libraries: /usr/lib64/libidn.so.11:
cannot read file data: Invalid argument
startkde: Starting up...
/opt/kde3/bin/kdeinit: error while loading shared libraries:
/usr/lib64/libidn.so.11: cannot read file data: Invalid argument
startkde: Could not start kdeinit. Check your installation.
Warning: connect() failed: : Connection refused
ksmserver: error while loading shared libraries: /usr/lib64/libidn.so.11:
cannot read file data: Invalid argument
ERROR: Couldn't attach to DCOP server!
startkde: Shutting down...
arts-start: error while loading shared libraries: /usr/lib64/libidn.so.11:
cannot read file data: Invalid argument
Warning: connect() failed: : Connection refused
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done.

waiting for X server to shut down


--
Richard
www.sheflug.org.uk
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >