Bug 801984 - [abrt] gnome-settings-daemon-3.2.2-1.fc16: _int_free: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
[abrt] gnome-settings-daemon-3.2.2-1.fc16: _int_free: Process /usr/libexec/gn...
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-09 21:58 EST by ccc2007chaos
Modified: 2013-02-13 07:29 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 07:28:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: dso_list (4.31 KB, text/plain)
2012-03-09 21:58 EST, ccc2007chaos
no flags Details
File: maps (11.96 KB, text/plain)
2012-03-09 21:58 EST, ccc2007chaos
no flags Details
File: var_log_messages (13.26 KB, text/plain)
2012-03-09 21:58 EST, ccc2007chaos
no flags Details
File: backtrace (39.10 KB, text/plain)
2012-03-09 21:58 EST, ccc2007chaos
no flags Details

  None (edit)
Description ccc2007chaos 2012-03-09 21:58:10 EST
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: _int_free
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.2.9-1.fc16.i686
pid:            2036
pwd:            /home/marios
reason:         Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
time:           Sat 10 Mar 2012 04:27:52 AM EET
uid:            1000
username:       marios

backtrace:      Text file, 40035 bytes
dso_list:       Text file, 4414 bytes
maps:           Text file, 12246 bytes
var_log_messages: Text file, 13576 bytes


:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
Comment 1 ccc2007chaos 2012-03-09 21:58:15 EST
Created attachment 569033 [details]
File: dso_list
Comment 2 ccc2007chaos 2012-03-09 21:58:17 EST
Created attachment 569034 [details]
File: maps
Comment 3 ccc2007chaos 2012-03-09 21:58:24 EST
Created attachment 569035 [details]
File: var_log_messages
Comment 4 ccc2007chaos 2012-03-09 21:58:27 EST
Created attachment 569036 [details]
File: backtrace
Comment 5 Fedora End Of Life 2013-01-16 07:16:07 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" 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: 
Comment 6 Fedora End Of Life 2013-02-13 07:29:01 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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