I thought I would start with a posting here to see what feedback I might
get. I searched KDE bugs but did not find this particular issue and if
the consensus here in this news group is that I should report this as a
bug I will...
I am running SuSE 10.3 and have been working for quite a while now
trying to track down a problem that starts to occurs near the end of
boot up and then occurring intermittently thereafter. The problem I am
experiencing is freezes where the GUI becomes unresponsive for several
minutes at a time, or it becomes extremely sluggish. This freeze always
occurs near the end of booting up and each of the final steps will take
several minutes to report that it as completed. As X becomes active and
the KDE desktop comes up this process will take upwards of 15 minutes to
complete. After a while the KDE desktop will become intermittently quite
responsive for a bit, then will become quite unresponsive again for a bit...
I have tried removing all services except those required by X11 without
success, and am now going through log files to see what complaints are
showing up there and trying to clean them up. I have looked at TOP and
VMSTAT to see if I have a process taking up all the CPU time or am
having swapping troubles. Again so far without success. I then decided
to take a look at KDE itself to see what I might try and there I learned
about a bunch of services that KDE is running and so I tried to stop
them. This had no effect on this problem either.
Next I found there is something called a Session Manager and when I
tried to open it, it crashes! So I now suspect I should get that working
to see if this may be the cause of my GUI unresponsiveness. The KDE
Crash reporter gave me a walkback which I have included below. Any one
got any ideas on what this means? Thanks in advance for any help offered
and please remember I am NOT a Linux guru by any means... So if you have
a suggestion for me to try, please don't use any advance terms or expect
me to have a lot of detailed knowledge about Linux and its toolset...
Marc Chamberlin
Attached is the stack walkback from the crash when I tried to open the
Session Manger found in Personal Settings -> KDE Components -> Session
Manager Something that caught my eye in this walkback is that there
are references to the ATI fglrx driver. I am using the ATI Radeon x1600
video card with the fglrx driver, could something be amiss with this driver?
[?1034h(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2acdfb1533e0 (LWP 28335)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x00002acdf6984b45 in raise () from /lib64/libc.so.6
#6 0x00002acdf69860e0 in abort () from /lib64/libc.so.6
#7 0x00002acdf697e07f in __assert_fail () from /lib64/libc.so.6
#8 0x00002acdf6362c96 in _XReply () from /usr/lib64/libX11.so.6
#9 0x00002acdfe4e4643 in AtiCallFGLCWDDE () from /usr/lib64/xorg/libGL.so.1
#10 0x00002acdff1d75dc in DRICallFGLCWDDE () from
/usr/lib64/dri/fglrx_dri.so
#11 0x00002acdff2288e8 in lnxioGetDongleInfo ()
from /usr/lib64/dri/fglrx_dri.so
#12 0x00002acdff0b9836 in ioOpen () from /usr/lib64/dri/fglrx_dri.so
#13 0x00002acdff0b09a4 in gslOpen () from /usr/lib64/dri/fglrx_dri.so
#14 0x00002acdfe6f6d2a in gldvOpen () from /usr/lib64/dri/fglrx_dri.so
#15 0x00002acdfed07899 in wsiDisplay::wsiDisplay ()
from /usr/lib64/dri/fglrx_dri.so
#16 0x00002acdfed07b5e in wsiGetDisplay () from /usr/lib64/dri/fglrx_dri.so
#17 0x00002acdff1d9ac7 in __driCreateNewScreen_20050727 ()
from /usr/lib64/dri/fglrx_dri.so
#18 0x00002acdfe4c1531 in ?? () from /usr/lib64/xorg/libGL.so.1
#19 0x00002acdfe4bdd55 in glXQueryExtensionsString ()
from /usr/lib64/xorg/libGL.so.1
#20 0x00002acdfda56d3f in SMServerConfig::load ()
from /opt/kde3/lib64/kde3/kcm_smserver.so
#21 0x00002acdfda570c9 in SMServerConfig::SMServerConfig ()
from /opt/kde3/lib64/kde3/kcm_smserver.so
#22 0x00002acdfda57d7a in KGenericFactory
On Wednesday 27 of August 2008, Marc Chamberlin wrote:
Next I found there is something called a Session Manager and when I tried to open it, it crashes! So I now suspect I should get that working to see if this may be the cause of my GUI unresponsiveness. The KDE Crash reporter gave me a walkback which I have included below. Any one got any ideas on what this means?
The crash looks like a driver problem, yes. No idea about the rest, but it could be caused by the driver too. -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (2)
-
Lubos Lunak
-
Marc Chamberlin