Bug 655380

Summary: [abrt] mail-notification-5.4-25.fc14: g_logv: Process /usr/bin/mail-notification was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Gary Myers <gary>
Component: mail-notificationAssignee: Dmitry Butskoy <dmitry>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: dmitry, erik-fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b57b466b1673a0f962903c7fd9b4f5da2130056e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-22 16:40:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Gary Myers 2010-11-20 18:44:11 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: mail-notification -p
comment: Removed mail-notification and re-installed via Yum. Deleted locally stored config to attempt a fresh configuration. Still crashing.
component: mail-notification
crash_function: g_logv
executable: /usr/bin/mail-notification
kernel: 2.6.35.6-48.fc14.x86_64
package: mail-notification-5.4-25.fc14
rating: 4
reason: Process /usr/bin/mail-notification was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1290278433
uid: 501

How to reproduce
-----
1. Just updated server to F14 - new dovecot; might be co-incidence.
2. Attempted to modify/add/remove mailboxes - crash occurs.
3.

Comment 1 Gary Myers 2010-11-20 18:44:15 UTC
Created attachment 461752 [details]
File: backtrace

Comment 2 Gary Myers 2010-11-20 19:39:28 UTC
Fixed dovecot error: New config defaults to disable plaintext auth. Re-configured and Thunderbird happy again. mail-notification still failing.

Comment 3 Dmitry Butskoy 2010-11-22 16:40:54 UTC

*** This bug has been marked as a duplicate of bug 649606 ***