kdeinit4 crashed with SIGSEGV in <signal handler called>()

Bug #451783 reported by MAKAPOH
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
New
Undecided
Unassigned

Bug Description

..

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Oct 14 17:10:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
NonfreeKernelModules: nvidia
Package: kdelibs-bin 4:4.3.2-0ubuntu4
ProcCmdline: kdeinit4:\ ksmserver\ [kdeinit]
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x9e3846 <_ZN21QDBusAdaptorConnector9relaySlotEPPv+22>: mov 0x4(%edx),%ecx
 PC (0x009e3846) ok
 source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 ?? () from /usr/lib/libkdeinit4_ksmserver.so
 <signal handler called>
 __kernel_vsyscall ()
 select () from /lib/tls/i686/cmov/libc.so.6
 QProcessManager::run (this=0x8850108)
Title: kdeinit4 crashed with SIGSEGV in <signal handler called>()
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
MAKAPOH (makapoh) wrote :
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.