kmail crashed with SIGSEGV in __kernel_vsyscall()

Bug #426264 reported by Xosé
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdepim

karmic alpha 5, on launching kmail.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Sep 8 14:39:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmail
NonfreeKernelModules: nvidia
Package: kmail 4:4.3.1-0ubuntu1
ProcCmdline: kmail -session 10b2d5d36e000125232641900000036980024_1252363875_342860
ProcCwd: /home/xose/Documentos
ProcEnviron:
 PATH=(custom, user)
 LANG=gl_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x148422 <__kernel_vsyscall+2>: ret
 PC (0x00148422) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdepim
Stacktrace: #0 0x00148422 in __kernel_vsyscall ()
StacktraceTop: __kernel_vsyscall ()
Title: kmail crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Xosé (ubuntu-galizaweb) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdepim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this crash reproducible? If so, could you install kdepim-dbg and try to obtain a backtrace as described at https://wiki.kubuntu.org/Backtrace please? Thanks in advance.

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