mail-notification crashed with SIGSEGV in mn_mail_icon_set_tip()

[Jens Kehne]

I believe this is the same as #924647. It said there to open a new bug if this happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: mail-notification 5.4.dfsg.1-8
Uname: Linux 3.11.6-zen+ x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 27 12:04:27 2013
ExecutablePath: /usr/bin/mail-notification
InstallationDate: Installed on 2012-06-05 (508 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: mail-notification
ProcEnviron:
 SHELL=/usr/bin/fish
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:en
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x41b150 <mn_mail_icon_set_tip>: mov 0x98(%rdi),%rax
 PC (0x0041b150) ok
 source "0x98(%rdi)" (0x00000098) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mail-notification
StacktraceTop:
 mn_mail_icon_set_tip ()
 ?? ()
 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
 g_signal_emitv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mail-notification crashed with SIGSEGV in mn_mail_icon_set_tip()
UpgradeStatus: Upgraded to saucy on 2013-10-26 (0 days ago)
UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark

[Apport retracing service (apport)]

StacktraceTop:
 mn_mail_icon_set_tip (self=0x0, tip=0x7f165868c71c <Address 0x7f165868c71c out of bounds>) at src/mn-mail-icon.gob:286
 mn_shell_update_tooltip (self=0x13022e0) at src/mn-shell.gob:716
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!