kopete crashed with SIGSEGV

Bug #560442 reported by vDub2000
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdenetwork

I'm using Kubuntu 10.04 Beta 2. Every time I try to add a new IM account, Kopete crashes.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: kopete 4:4.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 10 22:44:08 2010
Disassembly: => 0x8a7a5d: Cannot access memory at address 0x8a7a5d
ExecutablePath: /usr/bin/kopete
ProcCmdline: /usr/bin/kopete -caption Kopete
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdenetwork
Stacktrace:
 #0 0x008a7a5d in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfc0bff8
StacktraceTop: ?? ()
Title: kopete crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x8a7a5d: Cannot access memory at address 0x8a7a5d
 PC (0x008a7a5d) ok
 SP (0xbfc0bff8) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
vDub2000 (vdub2000) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x008a7a5d in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfc0c06c
StacktraceTop: ?? ()
ThreadStacktrace:

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you please install kdenetwork-dbg and get a backtrace from the KDE crash handler? Thanks in advance.

visibility: private → public
Changed in kdenetwork (Ubuntu):
status: New → Incomplete
Kees Cook (kees)
description: updated
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in kdenetwork (Ubuntu):
status: Incomplete → Invalid
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.