Bug 186874 - dolphin crashed at startup with SIGSEGV
Summary: dolphin crashed at startup with SIGSEGV
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
: 188685 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-03-11 16:30 UTC by sebastien
Modified: 2018-04-09 16:31 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sebastien 2009-03-11 16:30:29 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Fedora RPMs

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fcd770 (LWP 3195)]
[New Thread 0xb669fb90 (LWP 3198)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00681416 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xb7fcd770 (LWP 3195))]

Thread 2 (Thread 0xb669fb90 (LWP 3198)):
#0  0x00681416 in __kernel_vsyscall ()
#1  0x00571456 in nanosleep () from /lib/libc.so.6
#2  0x0057126e in sleep () from /lib/libc.so.6
#3  0x05dd039a in ?? () from /usr/lib/libkdeui.so.5
#4  0x05dd0dcc in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0x0306e3dd in QMutex::lock () from /usr/lib/libQtCore.so.4
#7  0x0573aa00 in ?? () from /usr/lib/libQtNetwork.so.4
#8  0x05747c37 in QAbstractSocket::setSocketDescriptor () from /usr/lib/libQtNetwork.so.4
#9  0x05754f79 in ?? () from /usr/lib/libQtNetwork.so.4
#10 0x05755966 in QLocalSocket::connectToServer () from /usr/lib/libQtNetwork.so.4
#11 0x07f3925e in Soprano::Client::LocalSocketClientConnection::newConnection () from /usr/lib/libsopranoclient.so.1
#12 0x07f3a563 in Soprano::Client::ClientConnection::socket () from /usr/lib/libsopranoclient.so.1
#13 0x07f3a6e2 in Soprano::Client::ClientConnection::iteratorClose () from /usr/lib/libsopranoclient.so.1
#14 0x07f3d859 in Soprano::Client::ClientModel::closeIterator () from /usr/lib/libsopranoclient.so.1
#15 0x07f3e4a6 in Soprano::Client::ClientStatementIteratorBackend::close () from /usr/lib/libsopranoclient.so.1
#16 0x07e7e083 in Soprano::Iterator<Soprano::Statement>::next () from /usr/lib/libsoprano.so.4
#17 0x07edd62b in Soprano::Util::MutexStatementIteratorBackend::next () from /usr/lib/libsoprano.so.4
#18 0x07fa1385 in ?? () from /usr/lib/libnepomuk.so.4
#19 0x07f9bd08 in ?? () from /usr/lib/libnepomuk.so.4
#20 0x07f9c558 in ?? () from /usr/lib/libnepomuk.so.4
#21 0x07fb7b07 in Nepomuk::Resource::property () from /usr/lib/libnepomuk.so.4
#22 0x07fb8e21 in Nepomuk::Resource::rating () from /usr/lib/libnepomuk.so.4
#23 0x08083f55 in _start ()

Thread 1 (Thread 0xb7fcd770 (LWP 3195)):
#0  0x00681416 in __kernel_vsyscall ()
#1  0x005ae3d1 in select () from /lib/libc.so.6
#2  0x05751857 in ?? () from /usr/lib/libQtNetwork.so.4
#3  0x0573c520 in ?? () from /usr/lib/libQtNetwork.so.4
#4  0x0574b662 in QAbstractSocket::waitForReadyRead () from /usr/lib/libQtNetwork.so.4
#5  0x0575360d in QLocalSocket::waitForReadyRead () from /usr/lib/libQtNetwork.so.4
#6  0x07f3a728 in Soprano::Client::ClientConnection::iteratorClose () from /usr/lib/libsopranoclient.so.1
#7  0x07f3d293 in Soprano::Client::ClientModel::~ClientModel () from /usr/lib/libsopranoclient.so.1
#8  0x07fa4332 in ?? () from /usr/lib/libnepomuk.so.4
#9  0x00500949 in exit () from /lib/libc.so.6
#10 0x004e86ed in __libc_start_main () from /lib/libc.so.6
#11 0x08060031 in _start ()
Comment 1 Dario Andres 2009-03-11 23:25:06 UTC
What were you doing when the application crashed? Do you experience this crash all the times? Are your KDE packages updated?
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You may need to install "libqt4-debuginfo" (Not sure if there is a debuginfo package for soprano/nepomuk, as this seems to be related to them)
Thanks :)
Comment 2 Dario Andres 2009-04-02 23:01:54 UTC
*** Bug 188685 has been marked as a duplicate of this bug. ***
Comment 3 Dario Andres 2009-04-26 16:16:27 UTC
Marking as NEEDSINFO
Comment 4 kingsimpson 2009-08-05 16:13:06 UTC
Dolphin crashed when Browsing shared drives on a windows XP machine in the same subnet
Comment 5 Dario Andres 2009-08-07 22:45:25 UTC
@kingsimpson@gmail.com: your crash is a different one. If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? Thanks
Comment 6 Julian Steinmann 2018-03-22 17:28:06 UTC
Closing because a lot of information is missing. If you can still reproduce this behavior with the newest version of Dolphin, please reopen this bug & attach a proper backtrace.
Comment 7 Julian Steinmann 2018-04-09 16:31:47 UTC
No response -> closing. Please reopen this bug if you still encounter this crash in newer versions of Dolphin.