Bug 667580 - [abrt] mail-notification-5.4-25.fc14: g_return_if_fail_warning: Process /usr/bin/mail-notification was killed by signal 6 (SIGABRT)
Summary: [abrt] mail-notification-5.4-25.fc14: g_return_if_fail_warning: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 654826
Alias: None
Product: Fedora
Classification: Fedora
Component: mail-notification
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Dmitry Butskoy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e9a4e54682c7d33b46128bc14d4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-06 04:46 UTC by David
Modified: 2011-01-06 16:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-06 13:29:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (62.20 KB, text/plain)
2011-01-06 04:46 UTC, David 		no flags Details
File: reproduce (2.98 KB, text/plain)
2011-01-06 04:46 UTC, David 		no flags Details
View All

Description David 2011-01-06 04:46:07 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: mail-notification -p
comment: I did not have evolution installed when I got this error, as it is not a depencency.  Installing evolution solved the problem, perhaps making it a dependency would fix this.
component: mail-notification
crash_function: g_return_if_fail_warning
executable: /usr/bin/mail-notification
kernel: 2.6.35.10-74.fc14.i686
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)
Attached file: reproduce
time: 1294286409
uid: 500
Comment 1 David 2011-01-06 04:46:11 UTC 
Created attachment 471983 [details]
File: backtrace
Comment 2 David 2011-01-06 04:46:13 UTC 
Created attachment 471984 [details]
File: reproduce
Comment 3 Dmitry Butskoy 2011-01-06 13:29:26 UTC 

*** This bug has been marked as a duplicate of bug 654826 ***
Comment 4 David 2011-01-06 16:26:00 UTC 
It is not a total duplicate since that bug is on x86_64 and this is i686, but I would be surprised if the solutions are different.
Note You need to log in before you can comment on or make changes to this bug.