Bug 768597 - [abrt] xboard-4.5.2a-1.fc16: LayoutChild: Process /usr/bin/xboard was killed by signal 11 (SIGSEGV)
Summary: [abrt] xboard-4.5.2a-1.fc16: LayoutChild: Process /usr/bin/xboard was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xboard
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Denise Dumas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2167da3418a73e63acfd812ea6f...
: 757222 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-17 10:44 UTC by Francesco Bonomi
Modified: 2014-02-05 11:52 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 11:52:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: event_log (4.23 KB, text/plain)
2011-12-17 10:44 UTC, Francesco Bonomi
no flags Details
File: backtrace (20.89 KB, text/plain)
2011-12-17 10:44 UTC, Francesco Bonomi
no flags Details
File: smolt_data (2.64 KB, text/plain)
2011-12-17 10:44 UTC, Francesco Bonomi
no flags Details
File: coredump (4.05 MB, text/plain)
2011-12-17 10:46 UTC, Francesco Bonomi
no flags Details
File: maps (3.92 KB, text/plain)
2011-12-17 10:46 UTC, Francesco Bonomi
no flags Details
File: dso_list (2.02 KB, text/plain)
2011-12-17 10:46 UTC, Francesco Bonomi
no flags Details
File: backtrace (20.61 KB, text/plain)
2012-04-02 12:01 UTC, Dmitri Skok
no flags Details
File: backtrace (20.69 KB, text/plain)
2012-04-02 22:57 UTC, Miloslav Trmač
no flags Details
File: backtrace (20.09 KB, text/plain)
2012-04-15 12:38 UTC, Graham Chapman
no flags Details
File: backtrace (20.04 KB, text/plain)
2012-04-27 19:43 UTC, Graham Chapman
no flags Details

Description Francesco Bonomi 2011-12-17 10:44:20 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        xboard
crash_function: LayoutChild
executable:     /usr/bin/xboard
kernel:         3.1.1-2.fc16.i686
pid:            1836
pwd:            /home/francesco.bonomi
reason:         Process /usr/bin/xboard was killed by signal 11 (SIGSEGV)
time:           mar 13 dic 2011 21:50:04 CET
uid:            1000
username:       francesco.bonomi
xsession_errors: 

backtrace:      Text file, 21392 bytes
dso_list:       Text file, 2070 bytes
event_log:      Text file, 4334 bytes
maps:           Text file, 4013 bytes
smolt_data:     Text file, 2699 bytes

build_ids:
:9d63dc2ec7319f8f859631fe02b108b896da5450
:e86c829bf8553d6b593dbd8c4df0957268dc8328
:96b666a7f6d7a80ea6f9aef54f0cdd0f6190c058
:55433495aa80cf9e1f994ea7e7ae278422ef1ede
:12cd53b71fd05ffbfe068dc898a902381f370f51
:bf0a36dd7bb8edf9bdb86ebcf5c1cf12543a78ca
:798697a352bae4178953ba502fb04f33dd0ed987
:40e3e5b910a2762887fba4cecdb950ad85cc7359
:eff0bea7fcdeae774d6e13c220ceda926377d0d6
:6fdbfcd9e4f3f1a2e5346a39cc05ed4104315ccf
:80bb58221fa63654070c0d920ae81ecd3c28acc6
:7e645e46542edda59c493361a82e3b992a26e1c2
:15bab279752ad8e30f901abae77bcb1ed1f38977
:12da4d1dc9764d3990ab6a2def5a88c4687d4550
:a0b366e13cecd6a811ac0afa3481d443b583aa4c
:faa844e460702359079f4f15f1f881e87777abb6
:21d0a4a7a50fccfd28494f22a8c0c17644fca991
:92a9033bbedc303317346dc414914fec5643bd7b
:030b651bfa42f57fde8249f7c6d3ece6d1f57343
:d7cd016536dcce05ea28a1219c92eb9507121fa3
:10cec21724c13b95ec03f00985b0405412817a49
:82674b49345364df4c158e8258b93fd4d8fdbae0

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=1
:HOSTNAME=francesco.bonomi
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=083bd8b0b99e79685057b66200000013-1323808523.363344-1988158174
:IMSETTINGS_MODULE=none
:USER=francesco.bonomi
:USERNAME=francesco.bonomi
:MAIL=/var/spool/mail/francesco.bonomi
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/francesco.bonomi/.local/bin:/home/francesco.bonomi/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/francesco.bonomi
:XMODIFIERS=@im=none
:LANG=en_US.utf8
:GDM_LANG=en_US.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/francesco.bonomi
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=francesco.bonomi
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-RwGuVAkjrB,guid=7728d01dca97d2ca84c00a7a00000021
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/francesco.bonomi
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-francesco.bonomi-dOeoBf/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1073,unix/unix:/tmp/.ICE-unix/1073
:GNOME_KEYRING_CONTROL=/tmp/keyring-40f1K9
:SSH_AUTH_SOCK=/tmp/keyring-40f1K9/ssh
:GPG_AGENT_INFO=/tmp/keyring-40f1K9/gpg:0:1
:LC_TIME=it_IT.utf8
:LC_NUMERIC=it_IT.utf8
:LC_MONETARY=it_IT.utf8
:LC_MEASUREMENT=it_IT.utf8
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/xboard.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=1836

var_log_messages:
:Dec 13 21:50:04 francesco kernel: [  914.044068] xboard[1836]: segfault at 2c ip 4101afd8 sp bff8cf50 error 4 in libXaw7.so.7.0.0[41000000+5d000]
:Dec 13 21:50:04 francesco abrt[1878]: Saved core dump of pid 1836 (/usr/bin/xboard) to /var/spool/abrt/ccpp-2011-12-13-21:50:04-1836 (4251648 bytes)

Comment 1 Francesco Bonomi 2011-12-17 10:44:23 UTC
Created attachment 548125 [details]
File: event_log

Comment 2 Francesco Bonomi 2011-12-17 10:44:26 UTC
Created attachment 548126 [details]
File: backtrace

Comment 3 Francesco Bonomi 2011-12-17 10:44:28 UTC
Created attachment 548127 [details]
File: smolt_data

Comment 4 Francesco Bonomi 2011-12-17 10:46:28 UTC
Created attachment 548128 [details]
File: coredump

Comment 5 Francesco Bonomi 2011-12-17 10:46:31 UTC
Created attachment 548129 [details]
File: maps

Comment 6 Francesco Bonomi 2011-12-17 10:46:33 UTC
Created attachment 548130 [details]
File: dso_list

Comment 8 abrt-bot 2012-03-21 17:19:19 UTC
*** Bug 757222 has been marked as a duplicate of this bug. ***

Comment 9 Dmitri Skok 2012-04-02 12:01:19 UTC
Engine->Engine #1 settings during game

backtrace_rating: 4
Package: xboard-4.5.2a-1.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment 10 Dmitri Skok 2012-04-02 12:01:24 UTC
Created attachment 574482 [details]
File: backtrace

Comment 11 Miloslav Trmač 2012-04-02 22:57:35 UTC
Clicked on Engine/Engine #1 settings

backtrace_rating: 4
Package: xboard-4.5.2a-1.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment 12 Miloslav Trmač 2012-04-02 22:57:39 UTC
Created attachment 574669 [details]
File: backtrace

Comment 13 Graham Chapman 2012-04-15 12:38:15 UTC
Click on 'Engine 1' in menu of xboard / gnuchess

backtrace_rating: 4
Package: xboard-4.5.2a-1.fc16
OS Release: Fedora release 16 (Verne)

Comment 14 Graham Chapman 2012-04-15 12:38:21 UTC
Created attachment 577535 [details]
File: backtrace

Comment 15 Graham Chapman 2012-04-27 19:43:40 UTC
Selected 'Engine' -> 'Engine #1 settings . . .'

backtrace_rating: 4
Package: xboard-4.5.2a-1.fc16
OS Release: Fedora release 16 (Verne)

Comment 16 Graham Chapman 2012-04-27 19:43:45 UTC
Created attachment 580848 [details]
File: backtrace

Comment 17 William Bader 2012-10-31 01:14:29 UTC
clicked on the menu

backtrace_rating: 4
Package: xboard-4.5.2a-2.fc17
Architecture: x86_64
OS Release: Fedora release 17 (Beefy Miracle)

Comment 18 Fedora End Of Life 2013-01-16 14:12:18 UTC
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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 19 Miloslav Trmač 2013-01-16 15:58:51 UTC
Still seeing this in F17 xboard-4.5.2a-2.fc17.x86_64.

Comment 20 Scott Isaacman 2013-01-26 02:56:23 UTC
I was trying to configure Xboard and it suddenly disappeared (followed by crash message).  I was not on command line, just using drop down menu.  My computer is an old compaq with an AMD sempron processor.

backtrace_rating: 4
Package: xboard-4.5.2a-3.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 21 Wilbert Isaac Cortés González 2013-02-06 00:40:58 UTC
I had the firefox open, running in gnome-shell, transmission-gtk, hotot and gnome-terminal, I clicked over the menu item "Engine" and BAM! it closed/crashed.

backtrace_rating: 4
Package: xboard-4.5.2a-3.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 23 Fedora End Of Life 2013-07-03 22:07:10 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 24 Fedora End Of Life 2013-12-21 08:31:33 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 25 Fedora End Of Life 2014-02-05 11:52:55 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.