mail-notification crashed with SIGSEGV in strlen()

Bug #267021 reported by Khorne
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mail Notification
Invalid
Undecided
Unassigned
mail-notification (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mail-notification

It always crashes just after login to system after pressing "refresh" button or simply during refreshment.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/mail-notification
Package: mail-notification 5.4.dfsg.1-1
ProcAttrCurrent: unconfined
ProcCmdline: mail-notification
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: mail-notification
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 vfprintf () from /lib/tls/i686/cmov/libc.so.6
 __vasprintf_chk () from /lib/tls/i686/cmov/libc.so.6
 g_vasprintf () from /usr/lib/libglib-2.0.so.0
 g_strdup_vprintf () from /usr/lib/libglib-2.0.so.0
Title: mail-notification crashed with SIGSEGV in strlen()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
Khorne (szczygiel-piotr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strlen () from /lib/tls/i686/cmov/libc.so.6
vfprintf () from /lib/tls/i686/cmov/libc.so.6
__vasprintf_chk () from /lib/tls/i686/cmov/libc.so.6
IA__g_vasprintf (string=0xb6bb7264,
IA__g_strdup_vprintf (format=0xb6bbfcd2 <Address 0xb6bbfcd2 out of bounds>,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in mail-notification:
importance: Undecided → Medium
Revision history for this message
Hew (hew) wrote :

Does the problem still occur if you remove/rename ~/.gnome2/mail-notification so that it creates a fresh config?

Changed in mail-notification:
status: New → Incomplete
Revision history for this message
Khorne (szczygiel-piotr) wrote : Re: [Bug 267021] Re: mail-notification crashed with SIGSEGV in strlen()

Yes, I removed this folder and mail-notification started then Config
window appeared but after adding gmail account it segfaulted.

Please let me know what kind of info do you need, I'll try to provide
it.

Thanks

Revision history for this message
Hew (hew) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as triaged and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in mail-notification:
status: Incomplete → Triaged
Revision history for this message
Marcin Wisnicki (mwisnicki) wrote :

I have a patch for this bug attached to a possibly related upstream bug report:

https://bugs.launchpad.net/mail-notification/+bug/179704/comments/7

Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 267021 and any other logs that are relevant for this particular issue.

Changed in mail-notification (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

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