This forum has been archived. All content is frozen. Please use KDE Discuss instead.

krusader crashing on Fedora 17

Tags: None
(comma "," separated)
cmiranda
Registered Member
Posts
14
Karma
0

krusader crashing on Fedora 17

Sat Sep 08, 2012 11:21 pm
Hi, I use Fedora 17 KDE spin, 32 bits,

I am a happy krusader (file manager) user. However this week I updated to the latest packages (no testing repo), and suddenly krusader crash (segfault) when I open the Setting window.

krusader is launched and used, but opening the Setting window, it crashes.

Any help on how to fix it ?

Information about the package
Code: Select all
$ rpm -qi krusader
Name        : krusader
Version     : 2.4.0
Release     : 0.4.beta1.fc17
Architecture: i686
Install Date: Sat Sep  8 19:33:07 2012
Group       : Applications/File
Size        : 9639315
License     : GPLv2+
Signature   : RSA/SHA256, Thu Jan 19 08:10:39 2012, Key ID 50e94c991aca3465
Source RPM  : krusader-2.4.0-0.4.beta1.fc17.src.rpm
Build Date  : Mon Jan 16 06:00:18 2012
Build Host  : x86-01.phx2.fedoraproject.org


KDE is 4.8.5

crash information, when launched from command line
Code: Select all
KCrash: Application 'krusader' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/home/claudio/.kde/socket-zhukov/kdeinit4__0


Backtrace information
Code: Select all
Application: Krusader (krusader), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb770ca00 (LWP 11579))]

Thread 2 (Thread 0xb65e7b40 (LWP 11580)):
#0  0x4875fdcd in clock_gettime () from /lib/librt.so.1
#1  0x4a3c9966 in ?? () from /lib/libQtCore.so.4
#2  0x4a4b16af in ?? () from /lib/libQtCore.so.4
#3  0xb5c004e0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xb770ca00 (LWP 11579)):
[KCrash Handler]
#6  0x4249182d in KSycocaEntry::name() const () from /lib/libkdecore.so.5
#7  0x0815d500 in ?? ()
#8  0x09066e40 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: krusader crashing on Fedora 17

Sun Sep 23, 2012 12:58 am
Please run "kbuildsycoca4 --noincremental".
That backtrace indicates that severe memory corruption has occurred, which may be linked to the Sycoca (which if it is the cause, would be surprising as most of KDE shouldn't be working if that is true).


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell