LinuxQuestions.org - Latest update wont allow KDE to run... (in VirtualBox)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Latest update wont allow KDE to run... (in VirtualBox) (https://www.linuxquestions.org/questions/slackware-14/latest-update-wont-allow-kde-to-run-in-virtualbox-844673/)

Latest update wont allow KDE to run... (in VirtualBox)

Hello, have similar issues with Slackware, since the latest Xorg updates I cant run KDE anymore. I am using VBox 3.2.10, so thats not the issue, i suppose.

Here is the error from kdm.log:

Code:

KCrash: Application 'kdmgreet' crashing...

KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly

QThread::wait: Thread tried to wait on itself

QThread: Destroyed while thread is still running

error setting MTRR (base = 0xe0000000, size = 0x04000000, type = 1) Invalid argument (22)

drkonqi: cannot connect to X server :0.0

Parse error on line 87 of section Files in file /etc/X11/xorg.conf

        Ignoring obsolete keyword "RgbPath".

error setting MTRR (base = 0xe0000000, size = 0x04000000, type = 1) Invalid argument (22)

Parse error on line 87 of section Files in file /etc/X11/xorg.conf

        Ignoring obsolete keyword "RgbPath".



Backtrace:

0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e6cfb]

1: /usr/bin/X (0x8048000+0x5daf5) [0x80a5af5]

2: (vdso) (__kernel_rt_sigreturn+0x0) [0x18140c]

3: /usr/lib/xorg/modules/libfb.so (fbBlt+0xca) [0x25a94a]

4: /usr/lib/xorg/modules/libfb.so (fbBltStip+0x73) [0x25b703]

5: /usr/lib/xorg/modules/libfb.so (fbGetImage+0x199) [0x260a59]

6: /usr/lib/xorg/modules/libshadow.so (0x160000+0xf4c) [0x160f4c]

7: /usr/bin/X (0x8048000+0x15e7af) [0x81a67af]

8: /usr/lib/xorg/modules/extensions/libglx.so (0x1f8000+0x37e8b) [0x22fe8b]

9: /usr/lib/xorg/modules/dri/swrast_dri.so (0xfda000+0xf4bd) [0xfe94bd]

10: /usr/lib/xorg/modules/dri/swrast_dri.so (0xfda000+0xf507) [0xfe9507]

11: /usr/lib/xorg/modules/extensions/libglx.so (0x1f8000+0x37ded) [0x22fded]

12: /usr/lib/xorg/modules/extensions/libglx.so (0x1f8000+0x34542) [0x22c542]

13: /usr/lib/xorg/modules/extensions/libglx.so (0x1f8000+0x353ba) [0x22d3ba]

14: /usr/lib/xorg/modules/extensions/libglx.so (0x1f8000+0x373af) [0x22f3af]

15: /usr/bin/X (0x8048000+0x27e97) [0x806fe97]

16: /usr/bin/X (0x8048000+0x1aec5) [0x8062ec5]

17: /lib/libc.so.6 (__libc_start_main+0xe6) [0xe5bc66]

18: /usr/bin/X (0x8048000+0x1aaa1) [0x8062aa1]

Segmentation fault at address (nil)



Fatal server error:

Caught signal 11 (Segmentation fault). Server aborting

Also when the system is booting I get a warning like this:

Code:

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.

Same here in a "real" machine. I start at runlevel 3 and when I "startx" => KDE I get the same backtrace (but in Xorg.0.log, not in kdm.log, obvioulsy)

But :
- at first X seems to start, I can see the KDE greeting screen for some seconds,
- X starts fine => fluxbox

I append Xorg.0.log.

I get the same issue... kind of :)

@Didier_Spaier - I have been comparing your Xorg.0.log file with mine from my Slackware 32 bit setup running the nouveau driver where all is OK.
I see this

Quote:

[ 921.670] (**) Option "AIGLX" "false"

I do not have this in my xorg.conf.

Also I note this

Quote:

[ 921.675] (--) using VT number 8

whereas I see

Quote:

[ 54.075] (--) using VT number 7

I had a problem which showed this switch in VT numbers. I found it was due to an old static libGL.a file in /usr/lib. After deleting the old file, all was OK.

Well I don't have libGL.a, so thats not the issue!

@allend

I have been using the option "AIGLX" "false" for months to avoid a (non hurting, I admit) AIGLX error in Xorg.0.log, see http://nouveau.freedesktop.org/wiki/...8AIGLXerror.29.

About the VT number, all I can tell is I don't have libGL.a either.

In fact I have no old files as I made a fresh install of current (not an upgrade).

Thanks anyway.

Downgrade mesa -
http://www.linuxquestions.org/questi...ml#post4159752

Had the same issue with VMware, and this solved it. I'm building KDE 4.5.3 now, against the new mesa to see if that also works.

But I have mesa 7.9 on my Slackware-13.1 as well and no issue in that case :scratch:

Downgrade to which version, I dont know which version was before...

OK, downgraded Mesa to version 7.8.2 and everything works. Well thanks for the the help... and those who wanna fix their issue with X+KDE then downgrade Mesa to version 7.8.2

It's still crashing, but X and KDE work:

Code:

[142158.002] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event3)

[142158.002] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"

[142158.002] (**) ImExPS/2 Generic Explorer Mouse: always reports core events

[142158.002] (**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event3"

[142158.006] (--) ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons

[142158.006] (--) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)

[142158.007] (--) ImExPS/2 Generic Explorer Mouse: Found relative axes

[142158.007] (--) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes

[142158.007] (II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse

[142158.007] (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5

[142158.007] (**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200

[142158.007] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE)

[142158.007] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1

[142158.007] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0

[142158.007] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000

[142158.007] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4

[142158.007] (II) ImExPS/2 Generic Explorer Mouse: initialized for relative axes.

[142158.008] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)

[142158.008] (II) No input driver/identifier specified (ignoring)

[142206.396] 

Backtrace:

[142206.397] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e6cfb]

[142206.397] 1: /usr/bin/X (0x8048000+0x5daf5) [0x80a5af5]

[142206.397] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xd7140c]

[142206.397] 3: /usr/bin/X (FreeClientResources+0xdf) [0x808e68f]

[142206.397] 4: /usr/bin/X (FreeAllResources+0x56) [0x808e746]

[142206.397] 5: /usr/bin/X (0x8048000+0x1aef1) [0x8062ef1]

[142206.397] 6: /lib/libc.so.6 (__libc_start_main+0xe6) [0x21bc66]

[142206.397] 7: /usr/bin/X (0x8048000+0x1aaa1) [0x8062aa1]

[142206.398] Segmentation fault at address 0x5e9

[142206.398] 

Fatal server error:

[142206.398] Caught signal 11 (Segmentation fault). Server aborting

[142206.399] 

[142206.399] 

Please consult the The X.Org Foundation support 

        at http://wiki.x.org

 for help. 

[142206.399] Please also check the log file at "/var/log/Xorg.0.log" for additional information.

[142206.399] 

[142206.418] (II) Power Button: Close

[142206.418] (II) UnloadModule: "evdev"

[142206.426] (II) Sleep Button: Close

[142206.426] (II) UnloadModule: "evdev"

[142206.434] (II) AT Translated Set 2 keyboard: Close

[142206.434] (II) UnloadModule: "evdev"

[142206.450] (II) ImExPS/2 Generic Explorer Mouse: Close

[142206.482] (II) UnloadModule: "evdev"

Quote:

Originally Posted by robertjinx (Post 4162953)

OK, downgraded Mesa to version 7.8.2 and everything works. Well thanks for the the help... and those who wanna fix their issue with X+KDE then downgrade Mesa to version 7.8.2

Or stay with Mesa 7.9 and disable compositing:

Quote:

Originally Posted by Slackware-current's Changelog

If X crashes at start, try disabling compositing. Create a file named
/etc/X11/xorg.conf.d/disable-composite.conf with this in it:
Section "Extensions"
Option "Composite" "Disable"
EndSection

This works here, so I will keep Mesa 7.9

I have a nVidia Corporation Quadro NVS 140M (rev a1) and don't use the blob.

SIGTERM to children
/home/user/.kde/socket-user/kdeinit4_0: No such file or directory
FAILED to connect to socket /tmp/dbus-62mVzAerCW

any ideas on that problem?

You're right, disabling composite works with Mesa 7.9.

Quote:

Originally Posted by robertjinx (Post 4162953)

OK, downgraded Mesa to version 7.8.2 and everything works. Well thanks for the the help... and those who wanna fix their issue with X+KDE then downgrade Mesa to version 7.8.2

If you would have bothered to read the link I posted, it does not get any clearer than that --- gives you a direct link to the package, reasons why Pat uploaded the package and in that thread even the disable composite bits ;)

I have this issue too, the segmentation fault thing. But when at runlevel 4, I can start KDE though.

KDE Compositing problem - update

I installed (again!) a fresh Slackware-current (32 bit), the last entry in Changelog dated Tue Nov 30 23:39:25 UTC 2010.

OK there has been an update of KDE since then and I will check it ASAP but first let me report about what I have found so far ;)

I have a Nvidia graphical card, lspci|grep VGA says:

Code:

01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)

I installed everything but the Nouveau X driver. Using the huge kernel when I "startx" from runlevel 3 :

Every WM/desktop but KDE is launched fine with either nv ou vesa X driver (I did put a minimal vesa.conf file in /etc/X11/xorg.conf.d to check with vesa, as when the nouveau module is not installed X use nv by default)
KDE crashes at startup using either nv or vesa
But KDE is launched fine if I upgradepkg to the nouveau X driver provided in /extra. This was not the case a while ago, but may be due to the fact that the X server has been patched recently to try nouveau before nv (another solution being to choose explicitly the nouveau X driver in a configuration file)

The same problem occur with KDE if I set the default runlevel to 4 in /etc/inittab.

Workarounds I know of:

Don't use KDE (just kidding - well, mostly)
Do what's suggested in the changelog entry dated Sun Nov 14 23:58:42 UTC 2010

Code:

Create a file named /etc/X11/xorg.conf.d/disable-composite.conf with this in it: Section "Extensions" Option "Composite" "Disable" EndSection
Edit the file ~.kde/share/config/kwinrc which is created at first KDE startup, replacing "OpenGLIsUnsafe=false" by "OpenGLIsUnsafe=true"

PS I couldn't find which program write ~.kde/share/config/kwinrc. Anyhow you will hardly convince me that it's an X or mesa problem unless you expose good reasons. IMHO it's really a KDE problem, may be only with the 4.5.1 version.

Stay tuned, I will provide an update as soon as I can try with KDE-4.5.4

Update after slackpkg update && slackpkg upgrade-all including KDE-4.5.4 && rm -rf ~/.kde : nothing changed, alas.

The /etc/X11/xorg.conf.d/disable-composite.conf solved my problem with KDE. Just updated last night and today there's another patch. Have yo update once again :D

@Didier - Have you tried blacklisting the Blur effect and Lancoz filter? http://www.linuxquestions.org/questi...ml#post4167103

Here is another blog post that provides more information on KDE 4.5 and graphics drivers. http://blog.martin-graesslin.com/blo...orkspaces-4-5/

Quote:

Originally Posted by allend (Post 4184151)

@Didier - Have you tried blacklisting the Blur effect and Lancoz filter? http://www.linuxquestions.org/questi...ml#post4167103

Thanks for the suggestion allend but I didn't yet - I promise to try in the sake of completion but honestly I do not plan to use KDE any time soon anyhow, thus my only concern is not to have new slackers disappointed by a crash at the first launch of their shiny new slackware-13.2.

In fact my advise to nVidia GPU owners is to either use "nouveau" or (if they post-install it) the proprietary drivers, aka "the blob", as "nv" is really dead now and "vesa" a last resort if nothing else works.

But as "nouveau" is still in "extra" they should be able to use "nv" or "vesa" at first and if they use KDE (most will do, I guess), they will be disappointed unless this issue be fixed by a member of the Slackware Team in concern - EH or PV or P++V++ aka RW I guess ;)

About the link you provided I am not sure I understood everything - in fact I am sure I didn't, let's excuse my bad English on that ;)

<off topic>@dc_eros there is a typo in your signature my friend, should read omelette au fromage</off topic>

Quote:

Originally Posted by Didier Spaier (Post 4185181)

<off topic>@dc_eros there is a typo in your signature my friend, should read omelette au fromage</off topic>

<off topic>Someone hasn't seen Dexter's Lab</off topic>

@T3slider: You're right of course, thank you for having provided me a good occasion to enhance my American culture.

I have eventually found it here http://jimerryan.multiply.com/video/...The_Big_Cheese

So I should have complained to Genndy Tartakovsky, sorry about thet dc_eros :confused:

Killed my KDE again:
Tried to switch back from fglrx to radeon driver, so I uninstalled flgrx, removed xorg.conf, rebooted. Bang, KDE crash. Started from cli: crashes because of lack of libatiuki.so.1, which is a part of fglrx. Reinstalled kde, still the same. WTF - why kde becomes dependant on driver provided by fglrx driver?