Bug 654125 - [abrt] evolution-2.32.0-2.fc14: (SIGSEGV) content_info_to_db, g_string_new
Summary: [abrt] evolution-2.32.0-2.fc14: (SIGSEGV) content_info_to_db, g_string_new
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6593fe6a1b840c8c9914b56e5e8...
: 743138 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-16 22:52 UTC by PRABIN KUMAR DATTA
Modified: 2011-10-06 17:33 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-18 10:02:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (57.44 KB, text/plain)
2010-11-16 22:52 UTC, PRABIN KUMAR DATTA
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 635161 0 None None None Never

Description PRABIN KUMAR DATTA 2010-11-16 22:52:55 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289945650
uid: 500

How to reproduce
-----
1. I logged-in to gmail.
2. Open terminal, then login as root using su command.
3. Suddenly, I saw a pop-up at the top of screen saying this package crashed.

Comment 1 PRABIN KUMAR DATTA 2010-11-16 22:52:59 UTC
Created attachment 460947 [details]
File: backtrace

Comment 2 Milan Crha 2010-11-18 10:02:04 UTC
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=635161

Comment 3 Milan Crha 2011-10-06 17:33:42 UTC
*** Bug 743138 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.