libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: rhythmbox crash_function: __GI___libc_malloc executable: /usr/bin/rhythmbox kernel: 3.3.5-2.fc16.i686.PAE pid: 26369 pwd: /home/sk reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) time: Пн. 21 мая 2012 12:24:17 uid: 1000 username: sk backtrace: Text file, 109673 bytes build_ids: Text file, 7872 bytes dso_list: Text file, 20544 bytes maps: Text file, 52309 bytes environ: :XDG_VTNR=1 :XDG_SESSION_ID=2 :HOSTNAME=sk :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :XDG_SESSION_COOKIE=693055fce9243295571c24fc00000008-1337436729.705704-2056051228 :QTDIR=/usr/lib/qt-3.3 :GNOME_KEYRING_CONTROL=/tmp/keyring-7v1rqP :QTINC=/usr/lib/qt-3.3/include :'IMSETTINGS_MODULE=X compose table' :USER=sk :USERNAME=sk :MAIL=/var/spool/mail/sk :PATH=/usr/lib/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/sk/.local/bin:/home/sk/bin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/sk :XMODIFIERS=@im=none :GNOME_KEYRING_PID=2374 :LANG=ru_RU.utf8 :GDM_LANG=ru_RU.utf8 :GDMSESSION=gnome :HISTCONTROL=ignoredups :HOME=/home/sk :XDG_SEAT=seat0 :SHLVL=1 :LOGNAME=sk :QTLIB=/usr/lib/qt-3.3/lib :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-5EmGDWIYZD,guid=b6a466cf48d18a70d73ff2f100000016 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=1 :XDG_RUNTIME_DIR=/run/user/sk :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-sk-j9lHKx/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2379,unix/unix:/tmp/.ICE-unix/2379 :SSH_AUTH_SOCK=/tmp/keyring-7v1rqP/ssh :GPG_AGENT_INFO=/tmp/keyring-7v1rqP/gpg:0:1 :GJS_DEBUG_OUTPUT=stderr :'GJS_DEBUG_TOPICS=JS ERROR;JS LOG' :DESKTOP_STARTUP_ID=gnome-shell-3018-sk-rhythmbox-17_TIME137548246 :GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/rhythmbox.desktop :GIO_LAUNCHED_DESKTOP_FILE_PID=26369 var_log_messages: :May 20 11:23:49 sk abrt: detected unhandled Python exception in 'rhythmbox' :May 21 12:24:17 sk kernel: [137550.119069] rhythmbox[26381]: segfault at 3a726f74 ip 4184b6bd sp b04a8ba0 error 4 in libc-2.14.90.so[417d3000+1a7000] :May 21 12:24:17 sk abrt[26382]: Saved core dump of pid 26369 (/usr/bin/rhythmbox) to /var/spool/abrt/ccpp-2012-05-21-12:24:17-26369 (50749440 bytes)
Created attachment 585822 [details] File: build_ids
Created attachment 585823 [details] File: dso_list
Created attachment 585824 [details] File: backtrace
Created attachment 585825 [details] File: maps
next track backtrace_rating: 4 Package: rhythmbox-2.90.1-17.git20110927.fc16 OS Release: Fedora release 16 (Verne)
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.