LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-15-2009, 11:30 AM   #1
hemp4fuel
Member
 
Registered: Jun 2003
Location: Topeka, KS
Distribution: Slackware
Posts: 192

Rep: Reputation: 45
kde 4.2 from -current plasma crash


I tried to check out the new kde 4.2 in -current but when I try to login it starts to load then the screen goes black and a box pops up that says "A Fatal Error Occurred The application Plasma Workspace(plasma) crashed and caused the signal 11 (SIGSEGV)." It goes on to say it is unable to create a valid backtrace because debugging isn't built into the package.

When this happened after an upgrade I decided to try starting it as a new user in case something in my ~/ was messing it up. I got the same results. I then decided to do a fresh install of -current to see if there was just something with my particular install that was causing it. I still get the same result.

I haven't seen any other reports of such a problem. Does anybody have any tips on how I might get this to work, or on steps to take to debug it.

Thanks
 
Old 03-15-2009, 12:34 PM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,661

Rep: Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236Reputation: 1236
I don't have this problem (fresh -current in a VM is Slackware 12.2). Anything interesting in /var/log/messages ? /var/log/Xorg.0.log ? find ~/.kde -name "*log" ?

I would try reinstall all kde packages, just in case.
 
Old 03-15-2009, 12:50 PM   #3
hemp4fuel
Member
 
Registered: Jun 2003
Location: Topeka, KS
Distribution: Slackware
Posts: 192

Original Poster
Rep: Reputation: 45
There is nothing interesting in /var/log/Xorg.0.log but in /var/log/messages there is a lot of:

Code:
Mar 15 10:58:01 pod1 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.12" (uid=1000 pid=3336 comm="kdeinit4: kio_trash [kdeinit] trash local:/tmp/kso") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=2794 comm="/usr/sbin/hald --daemon=yes "))
I don't know if that is related.
 
Old 03-15-2009, 07:06 PM   #4
grissiom
Member
 
Registered: Apr 2008
Location: China, Beijing
Distribution: Slackware
Posts: 423

Rep: Reputation: 45
Maybe you should make sure to have all your configuration files up-to-date. Run "slackpkg new-config" will do all the tricks for you. If it does not work, try "rm -rf ~/.kde" and start up kde again, maybe you would like to backup ~/.kde/share/config/plasma-applets.
 
Old 03-15-2009, 07:14 PM   #5
hemp4fuel
Member
 
Registered: Jun 2003
Location: Topeka, KS
Distribution: Slackware
Posts: 192

Original Poster
Rep: Reputation: 45
Thanks for the tips, I did a fresh install of the latest -current so all my conf files should be good. I have tried removing ~/.kde for my normal user as well as with a new user with a blank ~/ and still get the same results. I tried re-installing all the kde packages from a different mirror and that didn't work either. It really has me scratching my head. I am going to try it on another computer and see what kind of results I get there.
 
Old 03-16-2009, 12:18 AM   #6
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Which video card and Xorg driver are you using? If your card has issues with 3d rendering this can cause issues with Plasma. I had issues starting KDE 4 in Virtual Box until I installed the VBox video driver from guest additions.
 
Old 03-16-2009, 12:53 AM   #7
neeza
LQ Newbie
 
Registered: Mar 2009
Posts: 3

Rep: Reputation: 0
try to install -current in directory l/, i try this and solved
 
Old 03-16-2009, 01:07 AM   #8
hemp4fuel
Member
 
Registered: Jun 2003
Location: Topeka, KS
Distribution: Slackware
Posts: 192

Original Poster
Rep: Reputation: 45
My card is an ATI HD3850 with fglrx, I also tried radeonhd with the same results. I haven't had any trouble out of the card otherwise. I am not sure what is meant by installing -current in directory l/. Thanks again for everyone's help.
 
Old 03-17-2009, 04:03 AM   #9
tomcik
LQ Newbie
 
Registered: Mar 2009
Posts: 1

Rep: Reputation: 0
I have a similar problem. I upgraded my Slackware to the current version and I encountered problems with dbus as well. In my case dbus can't connect to dbus-server. I received message:

Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-ZsYjdqRJIg: Connection refuse.

When I try to start dbus manually I can reproduce this error:

First I start dbus-launcher:

eval `dbus-launch --sh-syntax --exit-with-session`

Then I try to invoke qdbus command and I'm receiving the same error: Could not connect to D-Bus server...

Does anyone know what can be wrong with dbus? I upgraded all packages from all directories in slackware-current.

Thanks for help in advance...
 
Old 03-18-2009, 08:44 PM   #10
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware, WinXP, Windows 7
Posts: 1,253

Rep: Reputation: 55
Hi - running a fresh install (today) of -current on a Dell E1505 with a Radeon X1400 video card. I'm using radeonhd and an xorg.conf created by xorgsetup.

Things seem to be running smooth now, but I did have some d-bus related issues at first. I don't know how you are starting KDE, but I found that running as a non-root user and starting from KDM (as opposed to issuing a startx command from the CLI) seemed to clear up the d-bus related errors. These were not the same errors you're seeing, but still d-bus errors.

Reminded me of how freerock gnome would behave if you didn't start it from GDM - error messages about d-bus/messagebus and no icons on the desktop.

Totally guessing of course.

HTH

Last edited by Franklin; 03-18-2009 at 08:46 PM.
 
Old 03-18-2009, 09:42 PM   #11
mbvo
Member
 
Registered: May 2006
Location: the land of confusion
Distribution: slackware-current
Posts: 220

Rep: Reputation: 31
I got the same error when i downloaded from slackware-current on ftp.slackware.com. its running fine now that i redownloaded everything from ftp://slackware.cs.utah.edu/pub/slac...kware-current/
 
Old 03-19-2009, 10:26 AM   #12
hemp4fuel
Member
 
Registered: Jun 2003
Location: Topeka, KS
Distribution: Slackware
Posts: 192

Original Poster
Rep: Reputation: 45
Thanks for the tips. I tried starting from KDM and it did get further along before it crashed, but it crashed just the same. I did try installing the kde packages from a different mirror than I originally got them from but I got the same results. I talked with someone else with the same issue as me after upgrading to -current, so I believe there to be a problem with certain setups.
 
Old 03-30-2009, 08:21 AM   #13
davidsrsb
Member
 
Registered: Oct 2003
Location: Kuala Lumpur, Malaysia
Distribution: Slackware 13.37 current
Posts: 770

Rep: Reputation: 33
I have the same plasma signal 11 with no backtrace. My machine has VIA Chrome on board graphics

Last edited by davidsrsb; 03-30-2009 at 11:44 AM.
 
Old 04-02-2009, 08:33 AM   #14
davidsrsb
Member
 
Registered: Oct 2003
Location: Kuala Lumpur, Malaysia
Distribution: Slackware 13.37 current
Posts: 770

Rep: Reputation: 33
I managed to get the following from messages:
Apr 2 20:22:01 slackbox kernel: agpgart-via 0000:00:00.0: AGP 3.5 bridge
Apr 2 20:22:01 slackbox kernel: agpgart-via 0000:00:00.0: bridge is in legacy mode, falling back to 2.x
Apr 2 20:22:01 slackbox kernel: agpgart-via 0000:00:00.0: putting AGP V2 device into 4x mode
Apr 2 20:22:01 slackbox kernel: pci 0000:01:00.0: putting AGP V2 device into 4x mode
Apr 2 20:22:24 slackbox kernel: plasma[8886]: segfault at 18 ip a9dc64c4 sp a9975840 error 6 in libjpeg.so.62[a9db8000+23000]
 
Old 04-09-2009, 08:44 AM   #15
davidsrsb
Member
 
Registered: Oct 2003
Location: Kuala Lumpur, Malaysia
Distribution: Slackware 13.37 current
Posts: 770

Rep: Reputation: 33
Still breaks in the same way with KDE4.2.2 updates
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
plasma workspace crash kurquhart1 Linux - Newbie 7 06-01-2009 01:29 AM
does kde 4.2 still have the plasma desktop icons? rabbit2345 Linux - Software 3 02-11-2009 05:03 AM
KDE Plasma plasmoid using 100% resources; cannot remove peteyperson Linux - Newbie 12 02-07-2009 07:42 AM
LXer: KDE 4.0.2 Brings New Plasma Features LXer Syndicated Linux News 0 03-06-2008 05:40 AM
LXer: Plasma: The Next-Generation KDE Environment LXer Syndicated Linux News 0 09-18-2006 10:54 AM


All times are GMT -5. The time now is 02:55 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration