Bug 756857

Summary: [abrt] rhythmbox-2.90.1-17.git20110927.fc16: g_type_check_instance_cast: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Talha Khan <talha.khan1>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:56bda9e56cb0b7ececaffb6e75a5e44fdeb0ffeb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 11:57:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dso_list
none
File: smolt_data
none
File: xsession_errors
none
File: backtrace
none
File: maps none

Description Talha Khan 2011-11-24 20:59:53 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        rhythmbox
comment:        I closed Rhtyhmbox from the bottom notification panel
crash_function: g_type_check_instance_cast
executable:     /usr/bin/rhythmbox
kernel:         3.1.1-2.fc16.i686
pid:            4920
pwd:            /home/talha
reason:         Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
time:           Thu 24 Nov 2011 03:48:37 PM EST
uid:            1000
username:       talha

backtrace:      Text file, 50131 bytes
dso_list:       Text file, 23196 bytes
maps:           Text file, 58149 bytes
smolt_data:     Text file, 3263 bytes
xsession_errors: Text file, 15248 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=talha-laptop
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=7e7c4cd26413be07d19985c300000010-1322153485.415955-2098784664
:QTDIR=/usr/lib/qt-3.3
:GNOME_KEYRING_CONTROL=/tmp/keyring-VBEzVw
:QTINC=/usr/lib/qt-3.3/include
:IMSETTINGS_MODULE=none
:USER=talha
:USERNAME=talha
:MAIL=/var/spool/mail/talha
:PATH=/usr/lib/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/talha/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/talha
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1430
:LANG=en_US.UTF-8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/talha
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=talha
:QTLIB=/usr/lib/qt-3.3/lib
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-rSYaIMMZgT,guid=38538f9c23bbfa79ab11663900000044
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/talha
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-talha-i0tF1G/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1434,unix/unix:/tmp/.ICE-unix/1434
:SSH_AUTH_SOCK=/tmp/keyring-VBEzVw/ssh
:GPG_AGENT_INFO=/tmp/keyring-VBEzVw/gpg:0:1
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:DESKTOP_STARTUP_ID=gnome-shell-1632-talha-laptop-rhythmbox-7_TIME9504291
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/rhythmbox.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=4920

var_log_messages:
:Nov 21 14:18:47 talha-laptop rhythmbox: abrt: detected unhandled Python exception in rhythmbox
:Nov 21 14:25:20 talha-laptop kernel: [ 4788.481848] rhythmbox-metad[17002]: segfault at 5 ip 0804e6f9 sp bfb4b780 error 4 in rhythmbox-metadata[8048000+11000]
:Nov 21 14:25:20 talha-laptop abrt[17013]: saved core dump of pid 17002 (/usr/libexec/rhythmbox-metadata) to /var/spool/abrt/ccpp-2011-11-21-14:25:20-17002 (36753408 bytes)
:Nov 23 23:41:45 talha-laptop abrt: detected unhandled Python exception in 'rhythmbox'
:Nov 24 15:48:37 talha-laptop kernel: [10594.971592] rhythmbox[4920]: segfault at 3e66 ip 44e39d9f sp bfb26b20 error 4 in libgobject-2.0.so.0.3000.1[44e08000+4c000]
:Nov 24 15:48:38 talha-laptop abrt[5162]: Saved core dump of pid 4920 (/usr/bin/rhythmbox) to /var/spool/abrt/ccpp-2011-11-24-15:48:37-4920 (135585792 bytes)

Comment 1 Talha Khan 2011-11-24 20:59:55 UTC
Created attachment 536051 [details]
File: dso_list

Comment 2 Talha Khan 2011-11-24 20:59:57 UTC
Created attachment 536052 [details]
File: smolt_data

Comment 3 Talha Khan 2011-11-24 20:59:58 UTC
Created attachment 536053 [details]
File: xsession_errors

Comment 4 Talha Khan 2011-11-24 21:00:00 UTC
Created attachment 536054 [details]
File: backtrace

Comment 5 Talha Khan 2011-11-24 21:00:02 UTC
Created attachment 536055 [details]
File: maps

Comment 6 Fedora End Of Life 2013-01-16 12:05:07 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 7 Fedora End Of Life 2013-02-13 11:57:06 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.