Bug 536697 - [abrt] crash detected in glib/gobject functions
Summary: [abrt] crash detected in glib/gobject functions
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glib2
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:81d56e5f91dea04c3d20485c0e9...
: 536699 536700 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-11 00:13 UTC by Adam Williamson
Modified: 2010-11-05 22:18 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-05 22:18:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (41.45 KB, text/plain)
2009-11-11 00:13 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2009-11-11 00:13:10 UTC
abrt detected a crash.

Comment: Nothing specific. Evo suddenly seems to be crashing quite regularly. Hasn't been doing this throughout F12 cycle.
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
kernel: 2.6.31.5-127.fc12.x86_64
package: evolution-2.28.0-2.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Adam Williamson 2009-11-11 00:13:12 UTC
Created attachment 368972 [details]
File: backtrace

Comment 2 Milan Crha 2009-11-12 11:58:15 UTC
*** Bug 536700 has been marked as a duplicate of this bug. ***

Comment 3 Milan Crha 2009-11-12 12:00:04 UTC
*** Bug 536699 has been marked as a duplicate of this bug. ***

Comment 4 Milan Crha 2009-11-12 12:03:58 UTC
Thanks for a bug report. This bug and the duplicates are crashing in glib code. What is your glib2 version, and is this somehow reproducible, please?
  $ rpm -q glib2

I'm assigning it to glib for now, as there is not much evolution code involved in the crashing thread itself.

Comment 5 Adam Williamson 2009-11-12 19:51:08 UTC
I haven't found a way to predictably reproduce it yet, no. As I said in one of the dupes, I've tried doing the exact same operation I was doing when it crashed, and that doesn't reproduce it. So obviously there's something deeper than that happening.

As for the dupes, I am intentionally being 'stupid' about abrt reports: I'm just sending 'em all in, on the basis that this is what users will do anyway. If it leads to dupe floods like this, that is your trigger to ask the abrt folks to kindly include some better duplicate-detection smarts :)

glib2: glib2-2.22.2-2.fc12.x86_64 . latest in f12.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Bug Zapper 2010-11-04 06:34:24 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 7 Adam Williamson 2010-11-05 22:18:27 UTC
can't investigate this any more.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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