Arch Linux

nu_kru

Member

Registered: 2009-12-14

Posts: 8

Crash X when kde istarts

Hi.

I installed arch with kde in a P4, VIA Technologies, Inc. CN896/VN896/P4M900. I've installed xf86-openchrome and I didn't create any xorg.conf
When I try login, X crashes and go to kdm.

when I Iaunch kde it give me this error trace

X.Org X Server 1.9.2
Release Date: 2010-10-30
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.35-ARCH i686 
Current Operating System: Linux **** 2.6.36-ARCH #1 SMP PREEMPT Wed Nov 24 06:44:11 UTC 2010 i686
Kernel command line: root=/dev/sda3 ro
Build Date: 01 November 2010  10:35:30PM

Current version of pixman: 0.20.0
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
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: Wed Dec  1 14:30:50 2010
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) [drm] drmOpen failed.
(EE) CHROME(0): [dri] DRIScreenInit failed.  Disabling DRI.
Freed 20976640 (pool 1)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kbuildsycoca4 running...
Fetched layout groups from X server:    layouts: ("es")    variants: ("") 
Fetched layout groups from X server:    layouts: ("es")    variants: ("") 
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kded(1884)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.5'
kwin(1894) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "Mesa Project" 
kwin(1894) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "Software Rasterizer" 
kwin(1894) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "1.4 (2.1 Mesa 7.9)" 
kwin(1894) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "software" , version "7.9.)" 
kwin(1894): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed" 
kwin(1894): glCheckFramebufferStatus failed:  "GL_NO_ERROR" 

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e5ebb]
1: /usr/bin/X (0x8048000+0x5cd65) [0x80a4d65]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb778440c]
3: /usr/lib/xorg/modules/libfb.so (fbBltStip+0x73) [0xb70ec3f3]
4: /usr/lib/xorg/modules/libfb.so (fbGetImage+0x199) [0xb70f1679]
5: /usr/lib/xorg/modules/libxaa.so (0xb7080000+0x661c) [0xb708661c]
6: /usr/lib/xorg/modules/libxaa.so (0xb7080000+0x553ad) [0xb70d53ad]
7: /usr/bin/X (0x8048000+0x15f59f) [0x81a759f]
8: /usr/lib/xorg/modules/extensions/libglx.so (0xb7377000+0x3814b) [0xb73af14b]
9: /usr/lib/xorg/modules/dri/swrast_dri.so (0xaedda000+0xf76d) [0xaede976d]
10: /usr/lib/xorg/modules/dri/swrast_dri.so (0xaedda000+0xf7b7) [0xaede97b7]
11: /usr/lib/xorg/modules/extensions/libglx.so (0xb7377000+0x380ad) [0xb73af0ad]
12: /usr/lib/xorg/modules/extensions/libglx.so (0xb7377000+0x34802) [0xb73ab802]
13: /usr/lib/xorg/modules/extensions/libglx.so (0xb7377000+0x3567a) [0xb73ac67a]
14: /usr/lib/xorg/modules/extensions/libglx.so (0xb7377000+0x3766f) [0xb73ae66f]
15: /usr/bin/X (0x8048000+0x27187) [0x806f187]
16: /usr/bin/X (0x8048000+0x1a1b5) [0x80621b5]
17: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb74bac76]
18: /usr/bin/X (0x8048000+0x19d91) [0x8061d91]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support 
    at http://wiki.x.org
for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

kded4: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
QProcess: Destroyed while process is still running.
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
Colgar (hangup)
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-ttJLH0oqb5: Conexión rehusada
startkde: Shutting down...
kdeinit4_wrapper: Warning: connect(/home/***/.kde4/socket-****/kdeinit4__0) failed: : No such file or directory
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
Qt-subapplication: Fatal IO error: client killed
xprop:  unable to open display ':0'
xprop:  unable to open display ':0'
startkde: Done.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.

this is the results in errors.log.

Dec  1 17:02:56 localhost kdm[3633]: X server for display :1 terminated unexpectedly
Dec  1 17:02:58 localhost kdm_greet[5314]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory

When I login in failsafe session it works well.

thanks.

vladthedog

Member

Registered: 2010-12-03

Posts: 45

Re: Crash X when kde istarts

This is happening to me as well.  I was messing around with the desktop effects, and read to remove kwinrc from my home folder configs to fix my mistakes, and it wouldn't let me log in at all (i.e. it would crash like above).  If I moved the kwinrc back, it would work fine again.  I decided to create a new user on my system for trouble-shooting, and i started having the same error where X would crash.  Mind you this was with a brand new user on the system, never logged in before.  I decided to edit kwinrc on my new user and noticed this line:

OpenGLIsUnsafe=false

when I was messing around with the desktop effects earlier i was trying to get openGL working and thats where I was having issues.  I changed that line to:

OpenGLIsUnsafe=true

and now I can login with my new user.  It seems like default settings is to try to use OpenGL (not sure if this is something I did or a default setting elsewhere) and it causes my X to crash.  go to:

~/.kde4/share/config

edit kwinrc as i mentioned above and see if you can login now.

joshdmiller

Member

From: California

Registered: 2010-04-25

Posts: 51

Website

Re: Crash X when kde istarts

I had the same issue on a clean install this morning using the Nouveau driver, which does not support 3d. Fixing the value in kwinrc solved this for me as well.

But is this the correct fix? This was never an issue in earlier releases.

---

Website | GitHub | Twitter | Google+ | LinkedIn

vladthedog

Member

Registered: 2010-12-03

Posts: 45

Re: Crash X when kde istarts

No, I don't think its the "correct" fix.  I just posted what I found hoping someone smarter and more knowledgeable than I would know more about what I stumbled across

Cows

Member

From: Brooklyn, NY

Registered: 2007-05-20

Posts: 101

Re: Crash X when kde istarts

Thanks this worked

nu_kru

Member

Registered: 2009-12-14

Posts: 8

Re: Crash X when kde istarts

Hi,

I was looking for information and it was in fact a bug in the Unichome DRI Driver of Mesa.

There are more solutions:
This can be avoided by xorg.conf config:

Section "ServerFlags"
        Option          "AIGLX"                 "off"
EndSection

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562585

Or to apply a patch to the sources

https://bugs.freedesktop.org/show_bug.cgi?id=26999

I think this last solution is the best

devius

Member

Registered: 2010-11-11

Posts: 22

Re: Crash X when kde istarts

No, I don't think its the "correct" fix.  I just posted what I found hoping someone smarter and more knowledgeable than I would know more about what I stumbled across

Kwin changes so much between releases that there is no "correct fix". Having said that, the OpenGLIsUnsafe setting is usually what it takes to solve any issues like this one that you were having. It just disables OpenGL 3D acceleration for kwin in case it's marked as true. Luckily 2D performance in kwin is usually pretty good.
I also experienced some issues with the latest update. My system which has been working very well with desktop effects suddenly started to suffer from massive slowdowns when it tried displaying window miniatures. It seems that with the latest 4.5.4 they implemented a new filter but didn't test it in enough hardware to know exactly which gpu supported it.