Ubuntu
mail-notification package

mail-notification crashed with SIGSEGV in mn_mail_icon_set_tip_widget()

Bug #924647 reported by Scott Lewin
208
This bug affects 59 people
Affects Status Importance Assigned to Milestone
mail-notification (Debian)
Fix Released
Unknown
mail-notification (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Recieved this error during shutdown.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mail-notification 5.4.dfsg.1-2.4ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Jan 31 23:13:08 2012
ExecutablePath: /usr/bin/mail-notification
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: mail-notification --sm-disable
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41a100 <mn_mail_icon_set_tip_widget>: mov 0x170(%rdi),%rax
 PC (0x0041a100) ok
 source "0x170(%rdi)" (0x00000170) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mail-notification
StacktraceTop:
 mn_mail_icon_set_tip_widget ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: mail-notification crashed with SIGSEGV in mn_mail_icon_set_tip_widget()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Scott Lewin (sclewin) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mn_mail_icon_set_tip_widget ()
 ?? ()
 g_closure_invoke (closure=0x1d78bd0, return_value=0x0, n_param_values=1, param_values=0x7fff6751fa30, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.12/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0x7fff6751fa30) at /build/buildd/glib2.0-2.31.12/./gobject/gsignal.c:3302
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mail-notification (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mail-notification (Ubuntu):
status: New → Confirmed
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

I reported the bug upstream: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666407

no longer affects: mail-notification
Bug Watch Updater (bug-watch-updater)
Changed in mail-notification (Debian):
status: Unknown → New
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

I haven't seen this bug for months, now running Ubuntu 12.10 updated, so I'm closing it. If anybody is still affected please open a new bug with his or her system information.

Changed in mail-notification (Ubuntu):
status: Confirmed → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in mail-notification (Debian):
status: New → Fix Released
Revision history for this message
chris pollock (cpollock) wrote :

I keep getting this crash report periodically. According to the comment on 2012-10-04 a fix was released. Why then may I ask am I still getting this crash?

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

@cpollok , maybe you should open a new bug report with the information of your system if this is still an issue for you.

Revision history for this message
chris pollock (cpollock) wrote :

Good idea, I'll do that the next time it occurs and see what happens.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.