Bug 784292 - [abrt] xfwm4-4.8.3-1.fc16: __GI___libc_malloc: Process /usr/bin/xfwm4 was killed by signal 11 (SIGSEGV)
Summary: [abrt] xfwm4-4.8.3-1.fc16: __GI___libc_malloc: Process /usr/bin/xfwm4 was kil...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libX11
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2cfee4ba0452f1d56729ba80f81...
: 700700 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 13:40 UTC by Nicolas Corrarello
Modified: 2014-06-18 09:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 02:22:24 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (5.20 KB, text/plain)
2012-01-24 13:40 UTC, Nicolas Corrarello
no flags Details
File: maps (27.36 KB, text/plain)
2012-01-24 13:40 UTC, Nicolas Corrarello
no flags Details
File: backtrace (92.09 KB, text/plain)
2012-01-24 13:40 UTC, Nicolas Corrarello
no flags Details

Description Nicolas Corrarello 2012-01-24 13:40:38 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 27bfdc54f-86a6-4197-bdee-8ef68c4b47d8
crash_function: __GI___libc_malloc
executable:     /usr/bin/xfwm4
kernel:         3.1.9-1.fc16.x86_64
pid:            1597
pwd:            /home/sgtpepper
reason:         Process /usr/bin/xfwm4 was killed by signal 11 (SIGSEGV)
time:           Tue 24 Jan 2012 10:28:18 AM ART
uid:            1000
username:       sgtpepper

backtrace:      Text file, 94300 bytes
dso_list:       Text file, 5321 bytes
maps:           Text file, 28013 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:SSH_AGENT_PID=1562
:HOSTNAME=conan.planet-express.com.ar
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GPG_AGENT_INFO=/home/sgtpepper/.gnupg/S.gpg-agent:1583:1
:GLADE_PIXMAP_PATH=:
:XDG_MENU_PREFIX=xfce-
:TERM=dumb
:SHELL=/bin/bash
:HISTSIZE=1000
:XDG_SESSION_COOKIE=6960187c1bf8722bf7dc05a80000000f-1327409083.207362-944994370
:GNOME_KEYRING_CONTROL=/tmp/keyring-E9BlDf
:IMSETTINGS_MODULE=none
:USER=sgtpepper
:GLADE_MODULE_PATH=:
:SSH_AUTH_SOCK=/tmp/ssh-PYEzMCJM1433/agent.1433
:USERNAME=sgtpepper
:XDG_CONFIG_DIRS=/etc/xdg
:MAIL=/var/spool/mail/sgtpepper
:DESKTOP_SESSION=xfce
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/sgtpepper/.local/bin:/home/sgtpepper/bin
:QT_IM_MODULE=xim
:PWD=/home/sgtpepper
:XMODIFIERS=@im=none
:LANG=en_US.UTF-8
:GNOME_KEYRING_PID=1429
:GDMSESSION=xfce
:SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
:HISTCONTROL=ignoredups
:SHLVL=2
:XDG_SEAT=seat0
:HOME=/home/sgtpepper
:LOGNAME=sgtpepper
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-cKbD5WfOPv,guid=9474c181418f0bdf87a3f2150000002b
:XDG_DATA_DIRS=/usr/local/share:/usr/share
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:DISPLAY=:0
:XDG_RUNTIME_DIR=/run/user/sgtpepper
:GLADE_CATALOG_PATH=:
:LIBGLADE_MODULE_PATH=:
:XAUTHORITY=/var/run/gdm/auth-for-sgtpepper-5DtD35/database
:_=/usr/bin/xfce4-session
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1592,unix/unix:/tmp/.ICE-unix/1592

var_log_messages:
:Jan 24 10:28:18 conan kernel: [ 2658.649590] xfwm4[1597]: segfault at ffffffff00000010 ip 000000350287dc11 sp 00007fff808e1840 error 4 in libc-2.14.90.so[3502800000+1ab000]
:Jan 24 10:28:18 conan abrt[2811]: Saved core dump of pid 1597 (/usr/bin/xfwm4) to /var/spool/abrt/ccpp-2012-01-24-10:28:18-1597 (4489216 bytes)

Comment 1 Nicolas Corrarello 2012-01-24 13:40:41 UTC
Created attachment 557238 [details]
File: dso_list

Comment 2 Nicolas Corrarello 2012-01-24 13:40:46 UTC
Created attachment 557239 [details]
File: maps

Comment 3 Nicolas Corrarello 2012-01-24 13:40:51 UTC
Created attachment 557240 [details]
File: backtrace

Comment 4 Kevin Fenzi 2012-01-24 17:55:34 UTC
What were you doing when this happened? 

Can you duplicate it?

Comment 5 abrt-bot 2012-03-20 16:29:15 UTC
Backtrace analysis of bugs across components suggests the actual bug is in component libX11, libxcb or glibc instead of component xfwm4, reassigning to libX11.

Bug #700700 from component totem was found to be similar to this bug.

This comment is automatically generated.

Comment 6 abrt-bot 2012-03-20 16:29:25 UTC
*** Bug 700700 has been marked as a duplicate of this bug. ***

Comment 7 Fedora End Of Life 2013-01-17 00:21:42 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 8 Fedora End Of Life 2013-02-14 02:22:28 UTC
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.