Bug 759792 - [abrt] gnome-shell-3.2.1-2.fc16: g_type_check_instance_is_a: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-shell-3.2.1-2.fc16: g_type_check_instance_is_a: Process /usr/bin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8bd554316078c88ebbddc939c79...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-03 20:45 UTC by msrocks
Modified: 2013-02-13 20:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 20:10:26 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (20.17 KB, text/plain)
2011-12-03 20:45 UTC, msrocks
no flags Details
File: maps (76.87 KB, text/plain)
2011-12-03 20:46 UTC, msrocks
no flags Details
File: xsession_errors (3.20 KB, text/plain)
2011-12-03 20:46 UTC, msrocks
no flags Details
File: backtrace (31.42 KB, text/plain)
2011-12-03 20:46 UTC, msrocks
no flags Details

Description msrocks 2011-12-03 20:45:54 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: g_type_check_instance_is_a
executable:     /usr/bin/gnome-shell
kernel:         3.1.2-1.fc16.x86_64
pid:            14959
pwd:            /home/maroun
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
time:           Sat 03 Dec 2011 03:37:07 PM EST
uid:            1000
username:       maroun

backtrace:      Text file, 32172 bytes
dso_list:       Text file, 20649 bytes
maps:           Text file, 78713 bytes
xsession_errors: Text file, 3280 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=FedoraCM
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=4c0954cdb65602407791c6830000000c-1322941814.975390-528442280
:GNOME_KEYRING_CONTROL=/tmp/keyring-xNLV99
:IMSETTINGS_MODULE=none
:USER=maroun
:USERNAME=maroun
:MAIL=/var/spool/mail/maroun
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/maroun/.local/bin:/home/maroun/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/maroun
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1445
:LANG=en_US.UTF-8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/maroun
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=maroun
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-P6ASNrAdwS,guid=4ab306b45e77798b557381a600000025
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/maroun
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-maroun-LoctHA/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1449,unix/unix:/tmp/.ICE-unix/1449
:GPG_AGENT_INFO=/tmp/keyring-xNLV99/gpg:0:1
:SSH_AUTH_SOCK=/tmp/keyring-xNLV99/ssh
:DESKTOP_AUTOSTART_ID=107bbcd4ff4612a847132294181577922400000014490000

var_log_messages:
:Dec  3 15:18:50 FedoraCM kernel: [ 1747.766901] gnome-shell[14038]: segfault at 3a445d008 ip 0000003be625ff28 sp 00007fff0cfd5ed0 error 4 in libglib-2.0.so.0.3000.1[3be6200000+11e000]
:Dec  3 15:18:51 FedoraCM abrt[14941]: Saved core dump of pid 14038 (/usr/bin/gnome-shell) to /var/spool/abrt/ccpp-2011-12-03-15:18:50-14038 (135778304 bytes)
:Dec  3 15:18:51 FedoraCM gnome-session[1449]: WARNING: Application 'gnome-shell.desktop' killed by signal
:Dec  3 15:37:07 FedoraCM kernel: [ 2841.567116] gnome-shell[14959]: segfault at e64f5016 ip 0000003be72329e0 sp 00007ffff7157428 error 4 in libgobject-2.0.so.0.3000.1[3be7200000+4c000]
:Dec  3 15:37:08 FedoraCM abrt[21570]: Saved core dump of pid 14959 (/usr/bin/gnome-shell) to /var/spool/abrt/ccpp-2011-12-03-15:37:07-14959 (136519680 bytes)
:Dec  3 15:37:08 FedoraCM gnome-session[1449]: WARNING: Application 'gnome-shell.desktop' killed by signal

Comment 1 msrocks 2011-12-03 20:45:58 UTC
Created attachment 540144 [details]
File: dso_list

Comment 2 msrocks 2011-12-03 20:46:00 UTC
Created attachment 540145 [details]
File: maps

Comment 3 msrocks 2011-12-03 20:46:01 UTC
Created attachment 540146 [details]
File: xsession_errors

Comment 4 msrocks 2011-12-03 20:46:03 UTC
Created attachment 540147 [details]
File: backtrace

Comment 5 Fedora End Of Life 2013-01-16 16:27:43 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 6 Fedora End Of Life 2013-02-13 20:10:30 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.