libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: rhythmbox crash_function: gtk_text_view_accessible_update_cursor executable: /usr/bin/rhythmbox kernel: 3.3.5-2.fc16.x86_64 pid: 1999 pwd: /home/mihkel reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) time: P 20 mai 2012 22:13:53 EEST uid: 1000 username: mihkel backtrace: Text file, 106790 bytes dso_list: Text file, 26614 bytes maps: Text file, 112003 bytes environ: :XDG_VTNR=1 :XDG_SESSION_ID=2 :HOSTNAME=gigabyte :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :XDG_SESSION_COOKIE=5116faf45411aa5ccce25fd20000000b-1337549358.344421-1027212914 :GNOME_KEYRING_CONTROL=/tmp/keyring-dWUv6o :'IMSETTINGS_MODULE=User Specific' :USER=mihkel :USERNAME=mihkel :MAIL=/var/spool/mail/mihkel :PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/mihkel/bin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/mihkel :XMODIFIERS=@im=ibus :EDITOR=emc :GNOME_KEYRING_PID=1215 :LANG=et_EE.UTF-8 :GDMSESSION=gnome :CLUTTER_PAINT=disable-clipped-redraws:disable-culling :HISTCONTROL=ignoredups :HOME=/home/mihkel :XDG_SEAT=seat0 :SHLVL=1 :LOGNAME=mihkel :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-GyR9nz8qAV,guid=5bcc2d3b3b25cda94e233e1000000034 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=1 :XDG_RUNTIME_DIR=/run/user/mihkel :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-mihkel-xh6lNV/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1219,unix/unix:/tmp/.ICE-unix/1219 :SSH_AUTH_SOCK=/tmp/keyring-dWUv6o/ssh :GPG_AGENT_INFO=/tmp/keyring-dWUv6o/gpg:0:1 :GJS_DEBUG_OUTPUT=stderr :'GJS_DEBUG_TOPICS=JS ERROR;JS LOG' :DESKTOP_STARTUP_ID=gnome-shell-1390-gigabyte-rhythmbox-1_TIME73994 :GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/rhythmbox.desktop :GIO_LAUNCHED_DESKTOP_FILE_PID=1999 var_log_messages: :May 20 22:13:49 gigabyte abrt: detected unhandled Python exception in 'rhythmbox' :May 20 22:13:53 gigabyte kernel: [ 926.813650] rhythmbox[1999]: segfault at 64 ip 00007fc4836a37b3 sp 00007fffe9a0d800 error 4 in libgtk-3.so.0.200.4[7fc4833d0000+43b000] :May 20 22:13:55 gigabyte abrt[3708]: Saved core dump of pid 1999 (/usr/bin/rhythmbox) to /var/spool/abrt/ccpp-2012-05-20-22:13:53-1999 (175239168 bytes)
Created attachment 585671 [details] File: dso_list
Created attachment 585672 [details] File: maps
Created attachment 585673 [details] File: backtrace
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
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.