Bug 171647 - nepomuk server crash at shutdown, logoff
Summary: nepomuk server crash at shutdown, logoff
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 174197 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-25 13:12 UTC by Rick Andrade
Modified: 2009-02-07 10:26 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
nepomukserver kcrash file (2.95 KB, text/plain)
2008-10-24 18:35 UTC, Michael Kühn
Details
emerge --info output (3.94 KB, text/plain)
2008-10-24 18:37 UTC, Michael Kühn
Details
emerge --info output (3.60 KB, application/octet-stream)
2008-10-24 23:17 UTC, Michael Kühn
Details
Upon shutdown the screen went white and gave me this error. (3.28 KB, text/plain)
2009-02-07 04:05 UTC, MartinBurschka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Andrade 2008-09-25 13:12:59 UTC
Version:            (using KDE 4.1.0)
OS:                Linux
Installed from:    SuSE RPMs

Application: Nepomuk Server (nepomukserver), signal SIGSEGV
[?1034h(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 0xb686d9d0 (LWP 4390)]
[New Thread 0xb5064b90 (LWP 4401)]
(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)
[KCrash handler]
#6  0xb7c78457 in QObject::thread () from /usr/lib/libQtCore.so.4
#7  0xb7f3df23 in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#8  0xb7f3f3e5 in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#9  0xb7f3b1ed in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#10 0xb7f3b34e in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#11 0xb7f39ead in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#12 0xb7c788bf in QObjectPrivate::deleteChildren ()
   from /usr/lib/libQtCore.so.4
#13 0xb7c807e4 in QObject::~QObject () from /usr/lib/libQtCore.so.4
#14 0xb7c6d2ef in QCoreApplication::~QCoreApplication ()
   from /usr/lib/libQtCore.so.4
#15 0xb737d986 in QApplication::~QApplication () from /usr/lib/libQtGui.so.4
#16 0xb6f7637e in KApplication::~KApplication () from /usr/lib/libkdeui.so.5
#17 0xb6f7d108 in KUniqueApplication::~KUniqueApplication ()
   from /usr/lib/libkdeui.so.5
#18 0xb7f40d86 in kdemain () from /usr/lib/libkdeinit4_nepomukserver.so
#19 0x08048772 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()
Comment 1 George Goldberg 2008-09-25 13:23:35 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 Michael Kühn 2008-10-24 18:35:44 UTC
Created attachment 28113 [details]
nepomukserver kcrash file
Comment 3 Michael Kühn 2008-10-24 18:37:54 UTC
Created attachment 28114 [details]
emerge --info output
Comment 4 Michael Kühn 2008-10-24 18:38:03 UTC
Hi,

same problem here. I installed kde from the gentoo-portage. i attached my emerge --info output.
Comment 5 Michael Kühn 2008-10-24 23:17:47 UTC
Created attachment 28121 [details]
emerge --info output

sorry.. previous is the wrong emerge --info file
Comment 6 Sebastian Trueg 2008-10-27 14:27:14 UTC
fixed in 4.1.something. Cannot remember which exactly
Comment 7 Sebastian Trueg 2008-11-04 08:54:06 UTC
*** Bug 174197 has been marked as a duplicate of this bug. ***
Comment 8 MartinBurschka 2009-02-07 04:05:35 UTC
Created attachment 31064 [details]
Upon shutdown the screen went white and gave me this error.

A Fatal Error Occurred
The application Nepomuk Server (nepomukserver) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.

Using Nvidia twindisplay GForce 7025 with 2 SyncMaster 225UW and 12 point fonts at 120DPI.
I have had a lot of crashed during install from CD/DVD - even on a new drive.
Install worked only when I avoided any CD/DVD-burning and reading.
Comment 9 Sebastian Trueg 2009-02-07 10:26:44 UTC
Martin: which kde version?