Bug 184116 - sigsegv on nepomuk server when log off
Summary: sigsegv on nepomuk server when log off
Status: RESOLVED UNMAINTAINED
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-12 08:59 UTC by dick thompson
Modified: 2018-09-04 15:22 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dick thompson 2009-02-12 08:59:13 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Slackware Packages

When I log out to restart I get the sigsegv error.


(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 0x2b7b80b887d0 (LWP 3228)]
[New Thread 0x40800950 (LWP 3229)]
(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)
[KCrash handler]
#5  0x00002b7b7a3d4ec0 in QObject::thread () from /usr/lib/libQtCore.so.4
#6  0x00002b7b7a3c77cf in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#7  0x00002b7b799e1958 in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#8  0x00002b7b799e3903 in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#9  0x00002b7b799de08b in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#10 0x00002b7b799de1e0 in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#11 0x00002b7b799dcc5c in ?? () from /usr/lib/libkdeinit4_nepomukserver.so
#12 0x00002b7b7a3d53b0 in QObjectPrivate::deleteChildren ()
   from /usr/lib/libQtCore.so.4
#13 0x00002b7b7a3daae3 in QObject::~QObject () from /usr/lib/libQtCore.so.4
#14 0x00002b7b7bbebd27 in QApplication::~QApplication ()
   from /usr/lib/libQtGui.so.4
#15 0x00002b7b799e4f4b in kdemain ()
   from /usr/lib/libkdeinit4_nepomukserver.so
#16 0x00002b7b7ef37164 in __libc_start_main () from /lib/libc.so.6
#17 0x00000000004007a9 in _start ()
#0  0x00002b7b7efb63f1 in nanosleep () from /lib/libc.so.6
Comment 1 John Schmidt 2009-03-10 02:14:22 UTC
I had a similar crash when I logged out immediately after installing Kubuntu 8.10 and installing all the updates.     The error message began "Fatal Error" and said Nepomuk serverwas involved.     The "details" section of the message said no valid back trace could be done because either the packages were built in a way that did not allow it or the stack was so corrupted in the crash that a back trace was impossible.

The following information was also provided:

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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb643ba00 (LWP 5528)]
[New Thread 0xb4d88b90 (LWP 5530)]
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f08430 in __kernel_vsyscall ()
[Current thread is 0 (LWP 5528)]

Thread 2 (Thread 0xb4d88b90 (LWP 5530)):
#0  0xb7f08430 in __kernel_vsyscall ()
#1  0xb7e42c01 in getdtablesize () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7b4cff4 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb79786ae in ?? () from /usr/lib/libQtCore.so.4
#4  0xb67f750f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb7e4a7ee in ?? () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb643ba00 (LWP 5528)):
#0  0xb7f08430 in __kernel_vsyscall ()
#1  0xb7e05de6 in sleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6e81042 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#3  0x00000000 in ?? ()
#0  0xb7f08430 in __kernel_vsyscall ()

Something similar also happened the first time I installed Kubuntu 8.10 and updated it and logged out.

I hope this helps correct this bug.     Thank you.


Sincerely,
John Schmidt
Comment 2 Sebastian Trueg 2009-04-28 10:27:28 UTC
does this still happen in kde 4.2
Comment 3 Dario Andres 2009-07-22 23:19:31 UTC
Marking as NEEDSINFO
Comment 4 Andrew Crouthamel 2018-09-04 15:22:37 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Development has moved to Baloo, please try again using the latest version and applications, and submit a new ticket for frameworks-baloo if you still have an issue. Thank you!