Bug 675843 - [abrt] evolution-data-server-2.32.1-1.fc14: append_value_to_blob: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.1-1.fc14: append_value_to_blob: Process /us...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glib2
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d0560ad1d8afff2c860d738f531...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-07 22:22 UTC by David
Modified: 2012-08-16 14:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:22:02 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (53.11 KB, text/plain)
2011-02-07 22:22 UTC, David
no flags Details

Description David 2011-02-07 22:22:46 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
crash_function: append_value_to_blob
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.10-74.fc14.i686
package: evolution-data-server-2.32.1-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297111629
uid: 500

How to reproduce
-----
1.
2.
3.
This issue came up after logging in and tring to switch between monitors on the docked laptop.

Comment 1 David 2011-02-07 22:22:48 UTC
Created attachment 477507 [details]
File: backtrace

Comment 2 Milan Crha 2011-02-08 11:16:34 UTC
Thanks for a bug report. This doesn't seem to be a use-after-free on evolution/evolution-data-server side, thus I'm moving this to gio, for further investigation, if they can think of anything.

Could you paste here your glib2 version, please?

Comment 3 David 2011-02-08 22:22:12 UTC
(In reply to comment #2)
> Thanks for a bug report. This doesn't seem to be a use-after-free on
> evolution/evolution-data-server side, thus I'm moving this to gio, for further
> investigation, if they can think of anything.
> 
> Could you paste here your glib2 version, please?

I looked in the lib directory but I'm now sure what to look under to find the glib2 version.

Comment 4 Milan Crha 2011-02-09 07:24:49 UTC
Oh, I'm sorry, I meant the package version, so result of:
   $ rpm -q glib2

Comment 5 David 2011-02-09 18:15:53 UTC
(In reply to comment #4)
> Oh, I'm sorry, I meant the package version, so result of:
>    $ rpm -q glib2

glib2-2.26.0-2.fc14.i686

Comment 6 Fedora End Of Life 2012-08-16 14:22:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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