cgmailservice crashed with SIGSEGV

Bug #451971 reported by rvanrookhuizen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cgmail (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cgmail

bug

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 15 10:09:15 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/cGmail/cgmailservice
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: cgmail 0.6-1
PackageArchitecture: all
ProcCmdline: python /usr/bin/cgmailservice
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
SegvAnalysis:
 Segfault happened at: 0x7f784d0051e0: mov 0x34(%rdi),%eax
 PC (0x7f784d0051e0) ok
 source "0x34(%rdi)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cgmail
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /lib/libglib-2.0.so.0
Title: cgmailservice crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
rvanrookhuizen (r-vanrookhuizen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_dbus_hash_table_get_n_entries (table=0x0) at dbus-hash.c:1702
_dbus_connection_get_dispatch_status_unlocked (
reply_handler_timeout (data=0x2368810)
timeout_handler_dispatch (
?? () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in cgmail (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in cgmail (Ubuntu):
status: New → 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.