Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

13.37 Can't start KDE in VMware workstation or Virtualbox

1,400 views
Skip to first unread message

Mr. B-o-B

unread,
Apr 28, 2011, 1:28:07 PM4/28/11
to
I installed 13.37 (32bit) on my work pc as a VMWare workstation guest,
and on my laptop as a Virtual Box guest. On both I am unable to start
KDE on either install. It starts to load, and then bombs. I tried XFCE,
and that loaded fine.

Here is a snip from the xorg log:

[ 5638.699] Segmentation fault at address (nil)
[ 5638.699]
Fatal server error:
[ 5638.699] Caught signal 11 (Segmentation fault). Server aborting
[ 5638.699]
[ 5638.699]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 5638.699] Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 5638.699]
[ 5638.700] (II) Power Button: Close
[ 5638.700] (II) UnloadModule: "evdev"
[ 5638.700] (II) Sleep Button: Close
[ 5638.700] (II) UnloadModule: "evdev"
[ 5638.700] (II) VirtualBox USB Tablet: Close
[ 5638.700] (II) UnloadModule: "evdev"
[ 5638.700] (II) AT Translated Set 2 keyboard: Close
[ 5638.700] (II) UnloadModule: "evdev"
[ 5638.700] (II) ImExPS/2 Generic Explorer Mouse: Close
[ 5638.700] (II) UnloadModule: "evdev"
[ 5638.701] (II) Speakup: Close
[ 5638.701] (II) UnloadModule: "evdev"
[ 5638.701] (II) (unnamed): Off.
[ 5638.701] (II) (unnamed): Close
[ 5638.701] (II) UnloadModule: "vboxmouse"

Any idea's what I might be doing wrong, or need to do for KDE?

Thanks!

Mr. B-o-B


Mr. B-o-B

unread,
Apr 28, 2011, 1:37:48 PM4/28/11
to

Forgive me, I forgot to include the message from the screen when it bombs:
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.

<unknown program name>(1949)/: Communication problem with
"plasma-desktop" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.Disconnected" : "
"Connection is closed" "

kdeinit4: Fatal IO error: client killed
kded4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
kcminit_startup: Fatal IO error: client killed
Qt-subapplication: Fatal IO error: client killed
kwin: Fatal IO error: client killed
xinit: connection to X server lost
Hangup
GOT SIGHUP
knotify4: cannot connect to X server :0
plasma-desktop: cannot connect to X server :0
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
Fatal Error: Accessed global static 'KGlobalPrivate *globalData()' after
destruction. Defined at /tmp/kdelibs-4.5.5/kdecore/kernel/kglobal.cpp:116
KCrash: Application 'ksmserver' crashing...
Fatal Error: Accessed global static 'KGlobalPrivate *globalData()' after
destruction. Defined at /tmp/kdelibs-4.5.5/kdecore/kernel/kglobal.cpp:116
Unable to start Dr. Konqi
bob@spaceship1:~$ Could not connect to D-Bus server:
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket
/tmp/dbus-shcUph5DHu: Connection refused
startkde: Shutting down...
kdeinit4_wrapper: Warning:
connect(/home/bob/.kde/socket-spaceship1/kdeinit4__0) failed: : No such
file or directory
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
xprop: unable to open display ':0'
xprop: unable to open display ':0'
startkde: Done.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.

Any thought on this would be great.

Thanks!

mi...@proteotien.ld

unread,
Apr 28, 2011, 4:41:01 PM4/28/11
to
Il Thu, 28 Apr 2011 12:37:48 -0500, Mr. B-o-B ha scritto:

> On 04/28/2011 12:28 PM, Mr. B-o-B wrote:
>> I installed 13.37 (32bit) on my work pc as a VMWare workstation guest,
>> and on my laptop as a Virtual Box guest. On both I am unable to start
>> KDE on either install. It starts to load, and then bombs. I tried XFCE,
>> and that loaded fine.

Months ago, same symptoms in my RealWorld--current64 (not virtualized
one).
Reinstalled "kdelibs" package, everything went (and actually is) fine.
;)

Your mileage my vary ( Cit.) but you can try it....

ming

--
"Ladies and Gentlemen: Elvis has just left the building."

Mr. B-o-B

unread,
Apr 28, 2011, 7:27:02 PM4/28/11
to
mi...@ProteoTien.ld cried from the depths of the abyss...

> Months ago, same symptoms in my RealWorld--current64 (not virtualized
> one).
> Reinstalled "kdelibs" package, everything went (and actually is) fine.
> ;)
>
> Your mileage my vary ( Cit.) but you can try it....
>

Thanks Ming! I reinstalled kdelib, and I still had the error. I
reinstalled all the kde packages, and still have the issue.

I will keep pluggin away at this.


Message has been deleted

Aragorn

unread,
Apr 29, 2011, 7:27:24 AM4/29/11
to
On Thursday 28 April 2011 23:50 in alt.os.linux.slackware, somebody
identifying as Frank Boehm wrote...

> Mr. B-o-B <mr.che...@gmail.com> wrote:
>
>> > Any idea's what I might be doing wrong, or need to do for KDE?
>

>> Caught signal 11 (Segmentation fault). Server aborting
>

> got the same error in VirtualBox-4.0.6 with Slackware-13.37 32bit
>
> kde-4 doesn't work, xfce or any other wm is ok
>
> but I can see plasma is not working in kde4 for me in my vm,
> do I need special hardware for plasma?

I'm not "there" yet - i.e. I'm still using KDE 3.5.10 on this box - but
it is my understanding that Plasma uses hardware-acceleration. If you
have recent hardware, see if you can enable the virtualization
extensions - i.e. AMD's SVM or Intel's VT - in the BIOS. Without that,
VirtualBox will need to emulate (among other things) the graphics
adapter.

> I can use startx with blackbox and call startkde in xterm afterwards

Odd. That would suggest that the problem may be related to a display
manager. Were you trying to use "kdm" by any chance?

--
*Aragorn*
(registered GNU/Linux user #223157)

Mr. B-o-B

unread,
Apr 29, 2011, 8:27:41 AM4/29/11
to
Aragorn cried from the depths of the abyss...

I have not been using kdm.

Message has been deleted
Message has been deleted

Pawlasty

unread,
May 1, 2011, 12:21:34 AM5/1/11
to
W dniu 2011-04-28 19:28, Mr. B-o-B pisze:

> I installed 13.37 (32bit) on my work pc as a VMWare workstation guest,
> and on my laptop as a Virtual Box guest. On both I am unable to start
> KDE on either install. It starts to load, and then bombs. I tried XFCE,
> and that loaded fine.
>
>

CHANGES_AND_HINTS.TXT was very helpful:

Regardless of your chipset (though it seems more common with intel), if KDE
crashes on startup, try disabling the Composite extension (which will
also
disable all of the fancy desktop effects). Place the following
content in
a file at /etc/X11/xorg.conf.d/disable-composite.conf:
Section "Extensions"
Option "Composite" "Disable"
EndSection

Dan C

unread,
May 1, 2011, 12:44:10 PM5/1/11
to

The CHANGES_AND_HINTS.TXT file is always helpful. It's baffling to me
why more people can't be bothered to read it, especially the n00bs and
dimwits who seem to have 90% of the problems... :)


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he found Piglet in bed with Eeyore.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg

Doug713705

unread,
May 1, 2011, 12:48:01 PM5/1/11
to
Le 01-05-2011, Dan C nous expliquait dans
alt.os.linux.slackware :

>
> The CHANGES_AND_HINTS.TXT file is always helpful. It's baffling to me
> why more people can't be bothered to read it, especially the n00bs and
> dimwits who seem to have 90% of the problems... :)

Because if they read it, they will immediatly loose their n00bs status
;-)

--
@+ Doug - Linux user #307925 - Slackware64 roulaize ;-)
http://usenet-fr.dougwise.org
http://newsportal.dougwise.org/
http://news.dougwise.org

herman...@gmail.com

unread,
Jun 11, 2012, 10:58:25 PM6/11/12
to paw...@o2.pl
Pawlasty, you're right! I had the same problem with KDE in Slackware 13.37 and your solution works. Thank you :D
0 new messages