** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965772
Title:
mutt-org crashed with SIGSEGV
To manage notifications about this bug go to:
I suspect this may also be a dup of open bug #666286 and open bug
#861056
I found these after I had this same crash today. I can force Mutt to
crash via a different mechanism though, via a notmuch-mutt call and
doing a search for a popular word.
--
You received this bug notification because
Given that there is still debate about the patch, I'm not sure there is
anything for ubuntu-sponsors to do at this point. Perhaps upstream
should be involved before we upload something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Agreed; unsubscribing sponsors for now. Resubscribe once there's
consensus on a solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965772
Title:
mutt-org crashed with SIGSEGV
To manage
There is a setting to override the obsolete package check:
# check obsolete packages
if report['ProblemType'] == 'Crash' and \
'APPORT_IGNORE_OBSOLETE_PACKAGES' not in os.environ:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On Wed, Jun 20, 2012 at 05:46:28PM -, Brian Murray wrote:
There is a setting to override the obsolete package check:
# check obsolete packages
if report['ProblemType'] == 'Crash' and \
'APPORT_IGNORE_OBSOLETE_PACKAGES' not in os.environ:
Yes, and I tried to use it, but
I just got a similar looking crash while running with the patch from
comment #8. :-/
apport won't report it because it's an obsolete package, but based on
the user-visible symptoms I think it's a similar problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
On Mon, Jun 04, 2012 at 03:06:38PM -, Sebastien Bacher wrote:
@Matt: is there any chance you could try to debdiff there and see if
that fixes the issue for you,sponsor the update if it does?
I am running with the patch from comment #8 now. I don't have a reproducer,
but will watch for a
@Matt: is there any chance you could try to debdiff there and see if
that fixes the issue for you,sponsor the update if it does?
@Brian: right, that patch is applied so it seems not enough, the
upstream bug points to http://dev.mutt.org/trac/changeset/0e4f1782ea2e
which is what the debdiff seems
The upstream mutt bug reporter contains a comment regarding the
following Debian bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537694
That bug in Debian is fixed by the patch, debian/patches/upstream/537694
-segv-imap-headers.patch, which is included in the Ubuntu package.
Oh, I
I've reopened the debian bug regarding this issue as it would be good to
have upstream fix their patch.
@Vibhav - your don't see to have used quilt properly in your debdiff as
imap/message.c is still showing as being modified and your patch hasn't
been added to the series file
Actually, there is a patch in debian that does cover this bug (well at
least the upstream one like this) and its in version 1.5.21-5:
+ 584138-mx_update_context-segfault.patch: fix a segfault due to holes in
IMAP headers, 537694-segv-imap-headers.patch is removed as part of this
** Patch added: mutt_1.5.21-5ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/mutt/+bug/965772/+attachment/3132767/+files/mutt_1.5.21-5ubuntu3.debdiff
** Changed in: mutt (Ubuntu)
Assignee: (unassigned) = Vibhav Pant (vibhavp)
--
You received this bug notification because you
The attachment mutt_1.5.21-5ubuntu3.debdiff of this bug report has
been identified as being a patch in the form of a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. In the event that this is in
fact not a patch
Thanks for the patch! I see this crash pretty regularly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965772
Title:
mutt-org crashed with SIGSEGV
To manage notifications about this bug go to:
** Bug watch added: Mutt Trac #3288
http://dev.mutt.org/trac/ticket/3288
** Also affects: mutt via
http://dev.mutt.org/trac/ticket/3288
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: mutt
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965772
Title:
mutt-org crashed with SIGSEGV
To manage notifications about this bug go to:
What's needed is the more recent patch from the upstream bug. I linked a
bzr branch wherein I applied the newer patch. I've never submitted a
patch to lp before, not sure if I'm doing this right.
** Branch linked: lp:~benw/mutt/mutt
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965772
Title:
** Description changed:
I've been seeing this for a while, and it's still happening on current
- Precise
+ Precise.
+
+ It seems to happen when I'm reading mail in one mailbox, and mutt
+ notifies me there is new mail in another mailbox. When I try to switch
+ to the mailbox with new mail, I
mx.c:1650 in the (patched) source seems to refer to the comment
preceding the declaration of mx_update_context. It's pretty safe to say
the crash didn't actually occur on that line. ;-)
When this happens, relaunching mutt and opening the same mailbox always
works fine. It's only after the
21 matches
Mail list logo
