Red Hat Bugzilla – Bug 759143
[abrt] gnome-shell-3.2.1-2.fc16: _int_memalign: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Last modified: 2013-02-13 15:09:06 EST
libreport version: 2.0.7
reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
time: Thu 01 Dec 2011 03:06:14 PM CET
backtrace: Text file, 121622 bytes
dso_list: Text file, 19980 bytes
maps: Text file, 50126 bytes
smolt_data: Text file, 2695 bytes
var_log_messages: Text file, 15329 bytes
:(gnome-shell:1548): folks-DEBUG: individual-aggregator.vala:305: Setting primary store IDs to defaults.
:(gnome-shell:1548): folks-DEBUG: individual-aggregator.vala:333: Primary store IDs are 'eds' and 'system'.
:gnome-shell-calendar-server: Got HUP on stdin - exiting
:gnome-session: WARNING: Application 'gnome-shell.desktop' killed by signal
:(gnome-shell:1817): folks-DEBUG: individual-aggregator.vala:305: Setting primary store IDs to defaults.
:(gnome-shell:1817): folks-DEBUG: individual-aggregator.vala:333: Primary store IDs are 'eds' and 'system'.
Created attachment 539212 [details]
Created attachment 539213 [details]
Created attachment 539214 [details]
Created attachment 539215 [details]
Created attachment 539216 [details]
Backtrace analysis of bugs across components suggests the actual bug might be in component glib2 instead of component gnome-shell. You might want to inspect the backtraces from the bugs listed below to find out the correct component.
Bugs which were found to be similar to this bug:
DeviceKit-disks: bug #579968
claws-mail: bug #696680, bug #749177, bug #789636
evince: bug #615380
evolution: bug #744469
evolution-data-server: bug #607960, bug #799718
evolution-exchange: bug #669649
gnome-shell: bug #781780
gvfs: bug #571349
pcmanfm: bug #789628
rhythmbox: bug #681163, bug #709834, bug #748661
xfce4-sensors-plugin: bug #772409
This comment is automatically generated.
*** Bug 799718 has been marked as a duplicate of this bug. ***
*** Bug 696680 has been marked as a duplicate of this bug. ***
*** Bug 709834 has been marked as a duplicate of this bug. ***
*** Bug 748661 has been marked as a duplicate of this bug. ***
*** Bug 781780 has been marked as a duplicate of this bug. ***
*** Bug 681163 has been marked as a duplicate of this bug. ***
*** Bug 789628 has been marked as a duplicate of this bug. ***
*** Bug 789636 has been marked as a duplicate of this bug. ***
*** Bug 772409 has been marked as a duplicate of this bug. ***
*** Bug 749177 has been marked as a duplicate of this bug. ***
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:
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.