Ubuntu
nepomuk-core package

nepomukserver crashed with SIGSEGV in close()

Bug #1163632 reported by Starbetrayer on 2013-04-03

74

This bug affects 10 people

Affects		Status	Importance	Assigned to	Milestone
	nepomuk-core (Ubuntu)	Invalid	Low	Unassigned

Bug Description

crash after startup

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nepomuk-core 4:4.10.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Tue Apr 2 19:27:29 2013
ExecutablePath: /usr/bin/nepomukserver
InstallationDate: Installed on 2011-07-15 (627 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
MarkForUpload: True
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6c51e258cc <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+236>: mov (%rax,%rdx,8),%rbx
PC (0x7f6c51e258cc) ok
source "(%rax,%rdx,8)" (0x00000141) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
StacktraceTop:
close () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: nepomukserver crashed with SIGSEGV in close()
UpgradeStatus: Upgraded to raring on 2012-01-09 (449 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Starbetrayer (starbetrayer) wrote on 2013-04-03:

#1

CoreDump.gz Edit (426.2 KiB, application/x-gzip)
Dependencies.txt Edit (7.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (841 bytes, text/plain; charset="utf-8")
Registers.txt Edit (832 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.0 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Harald Sitter (apachelogger) wrote on 2013-04-04:

#2

What is the output of

kreadconfig --file nepomukserverrc --group "Basic Settings" --key "Start Nepomuk"

Changed in nepomuk-core (Ubuntu):
status:	New → Incomplete

Revision history for this message

RussianNeuroMancer (russianneuromancer) wrote on 2013-04-07:

#3

I have same issue. In my case output of this command is "true".

Changed in nepomuk-core (Ubuntu):
status:	Incomplete → New

Revision history for this message

Starbetrayer (starbetrayer) wrote on 2013-04-07:

#4

In my case, I have no output, it just goes back to the normal console.

Revision history for this message

Harald Sitter (apachelogger) wrote on 2013-04-07:

#5

it's caused by signals landing while the qapplication is already cleaning up, thus making the signal handler work on a partially destructed object tree. solution would be to prevent signal handling after the qapplication mainloop returned. talked to upstream and hope it gets resolved soonishy. meanwhile it's not an issue, supposedly this happens on logout when it is shutting down already but takes too long such that it gets a TERM or QUIT signal to tell it to hurry up, so only a theoretical problem.

Changed in nepomuk-core (Ubuntu):
importance:	Undecided → Low
status:	New → Triaged

Revision history for this message

Apport retracing service (apport) wrote on 2013-05-07:

#6

Stacktrace:
#0 0x00007f6c51e258cc in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
StacktraceTop:
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2013-05-07: ThreadStacktrace.txt

#7

ThreadStacktrace.txt Edit (151 bytes, text/plain)

tags:	added: apport-failed-retrace
tags:	removed: need-amd64-retrace

Revision history for this message

Rohan Garg (rohangarg) wrote on 2014-02-12:

#8

Thanks for taking the time to report this bug. 13.04 reached EOL on January 27, 2014.
Please see this document for currently supported Kubuntu releases:
https://wiki.kubuntu.org/Releases

Unfortunately this means that there will be no more bugfixes for 13.04. It is also recommended that you upgrade, if you have not already.

Please feel free to report any other bugs you may find, and thanks for your understanding.

Changed in nepomuk-core (Ubuntu):
status:	Triaged → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.