kded4 crashed with SIGSEGV in ntrack_monitor_get()

[sirjeppe]

Got this crash immediately after startup.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: kdelibs-bin 4:4.7.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
Architecture: i386
Date: Wed Aug 17 11:27:26 2011
ExecutablePath: /usr/bin/kded4
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803)
ProcCmdline: /usr/bin/kded4 --nocrashhandler
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x298cdf4: mov (%eax),%edx
 PC (0x0298cdf4) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 ?? () from /usr/lib/libntrack.so.0
 ntrack_monitor_get () from /usr/lib/libntrack.so.0
 QNtrack::QNtrack() () from /usr/lib/libntrack-qt4.so.1
 QNtrack::instance() () from /usr/lib/libntrack-qt4.so.1
 ?? () from /usr/lib/kde4/kded_networkstatus.so
Title: kded4 crashed with SIGSEGV in ntrack_monitor_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ntrack_arch_new (callback=0x298d630 <process_monitor_arch_event>, user_data=0x0) at ntrack.c:119
 __new () at ntrackmonitor.c:212
 ntrack_monitor_get () at ntrackmonitor.c:49
 QNtrack::QNtrack (this=0x9dfb688) at QNtrack.cpp:47
 QNtrack::instance () at QNtrack.cpp:39

[Alexander Sack (asac)]

should be fixed by upstream in 016-1. please reopen and add ntrack _project_ target if you still see this.

if you dont run precise, packages for all active ubuntu versions are available here https://launchpad.net/~asac/+archive/ntrack ppa

[Gabriel Diosan (gabsd84)]

I just got a similar crash on startup today but the description is "nepomukservicestub crashed with SIGSEGV"

Should I open a new bug report for this or is it related?

[Jonathan Thomas (echidnaman)]

That would be a totally different issue altogether. (SIGSEGV is a fancy way of saying, "it crashed trying to access an invalid area of memory.")