KNetAttach crashes on login

Bug #980110 reported by Isak Enström
122
This bug affects 28 people
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Unfortunately Apport crashed just after it launched my web browser so I don't know if it were going to provide any further info.

The notification I get after login is that "an application has crashed on your system (now or in the past)". When I click the notification it says that it's KNetAttach that has crashed. It happened 2-3 times just after I installed Kubuntu 12.04 beta2, so I've hardly made any changes at all to the system.

Output of: lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

Output of: apt-cache policy kde-runtime
kde-runtime:
  Installed: 4:4.8.2-0ubuntu1
  Candidate: 4:4.8.2-0ubuntu1
  Version table:
 *** 4:4.8.2-0ubuntu1 0
        500 http://se.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Apr 12 19:25:18 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 ?? ()
 QObject::~QObject() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QObject::~QObject() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 _start ()
Title: nepomukservicestub crashed with SIGSEGV in QObject::~QObject()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Isak Enström (isen) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #913024, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-runtime (Ubuntu):
status: New → Confirmed
Revision history for this message
nockdown (nockdown) wrote :

Output of: lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04

Output of: apt-cache policy kde-runtime
kde-runtime:
 Installed: 4:4.8.2-0ubuntu2
 Candidate: 4:4.8.2-0ubuntu2
 Version table:
 *** 4:4.8.2-0ubuntu2 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

ApportVersion
2.0.1-0ubuntu7
Architecture
amd64
CrashCounter
1
Date
Tue May 8 13:09:28 2012
Disassembly
=> 0x0: Cannot access memory at address 0x0
DistroRelease
Ubuntu 12.04
ExecutablePath
/usr/bin/nepomukservicestub
InstallationMedia
Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
Package
kde-runtime 4:4.8.2-0ubuntu2
PackageArchitecture
amd64
ProblemType
Crash
ProcCmdline
/usr/bin/nepomukservicestub nepomukstorage
ProcEnviron
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcVersionSignature
Ubuntu 3.2.0-23.36-generic 3.2.14
SegvAnalysis
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason
executing NULL VMA
Signal
11
SourcePackage
kde-runtime
Stacktrace
#0 0x0000000000000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffc2e076e8
Tags
 precise
ThreadStacktrace
.
Thread 3 (LWP 1703):
#0 0x00007feb37754b03 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7feb254fdc80
Title
nepomukservicestub crashed with SIGSEGV
Uname
Linux 3.2.0-23-generic x86_64
UpgradeStatus
No upgrade log present (probably fresh install)
UserGroups
adm cdrom dip lpadmin plugdev sambashare sudo

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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