KNetAttach crashes on login
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://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-
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/
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/bin/
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:
_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
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.