Bug 604431 - [abrt] crash in compiz-0.8.6-1.fc13: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in compiz-0.8.6-1.fc13: Process /usr/bin/compiz was killed by si...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1fb35c49d36c2bfd32a85e25910...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-15 21:11 UTC by tiagoalmeida
Modified: 2011-06-27 18:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 18:19:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.12 KB, text/plain)
2010-06-15 21:11 UTC, tiagoalmeida
no flags Details

Description tiagoalmeida 2010-06-15 21:11:50 UTC
abrt 1.1.1 detected a crash.

architecture: i686
component: compiz
executable: /usr/bin/compiz
global_uuid: 1fb35c49d36c2bfd32a85e25910f85c9e2c8d463
kernel: 2.6.33.5-112.fc13.i686.PAE
package: compiz-0.8.6-1.fc13
rating: 4
reason: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

backtrace
-----
BFD: Warning: /var/cache/abrt/ccpp-1276635889-2030/coredump is truncated: expected core file size >= 39788544, found: 61440.
[New Thread 2030]
Failed to read a valid object file image from memory.
Core was generated by `compiz --ignore-desktop-hints glib gconf gnomecompat'.
Program terminated with signal 11, Segmentation fault.
#0  0x080549cc in ?? ()

Thread 1 (Thread 2030):
Cannot access memory at address 0xbf89863c
From        To          Syms Read   Shared Object Library
0x004e4830  0x004fc37f  Yes         /lib/ld-linux.so.2
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
eax            0x92e5178	154030456
ecx            0x0	0
edx            0x9232468	153298024
ebx            0x2c0b41c5	738935237
esp            0xbf898610	0xbf898610
ebp            0xbf898638	0xbf898638
esi            0xffffffe8	-24
edi            0x1	1
eip            0x80549cc	0x80549cc
eflags         0x10246	[ PF ZF IF RF ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
No function contains program counter for selected frame.

Comment 1 tiagoalmeida 2010-06-15 21:11:52 UTC
Created attachment 424302 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-02 10:41:30 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 3 Bug Zapper 2011-06-27 18:19:43 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.