Version-Release number of selected component: audacious-3.2.4-1.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: audacious crash_function: standard_free kernel: 3.5.3-1.fc17.i686 truncated backtrace: :Thread no. 1 (10 frames) : #6 standard_free at gmem.c : #8 g_slice_free1 at gslice.c : #9 gtk_file_system_model_finalize at gtkfilesystemmodel.c : #11 stop_loading_and_clear_list_model at gtkfilechooserdefault.c : #12 gtk_file_chooser_default_finalize at gtkfilechooserdefault.c : #14 g_value_object_free_value at gobject.c : #15 g_value_unset at gvalue.c : #17 g_signal_emit_by_name at gsignal.c : #18 list_row_activated at gtkfilechooserdefault.c : #19 _gtk_marshal_VOID__BOXED_OBJECT at gtkmarshalers.c
Created attachment 617731 [details] File: core_backtrace
Created attachment 617732 [details] File: environ
Created attachment 617733 [details] File: backtrace
Created attachment 617734 [details] File: limits
Created attachment 617735 [details] File: cgroup
Created attachment 617736 [details] File: maps
Created attachment 617737 [details] File: dso_list
Created attachment 617738 [details] File: open_fds
Created attachment 617739 [details] File: var_log_messages
Could you give a little bit of context/background, please? At least try. The backtrace is about glibc detecting malloc "double free or corruption (out)" and aborting the application. The code path leads into internal GTK+ filechooser code.
Audacious produced this error after installing a big bunch of updates and giving the PC a restart. I couldn't really dig deeper, because I'm still a noob in Linux. I was unable to fix it so I finally removed audacious. With this the investigation of the problem walked out the door I believe, but I'll try to re-install audacious to see if the problem persists.
*** Bug 863709 has been marked as a duplicate of this bug. ***
*** Bug 891958 has been marked as a duplicate of this bug. ***
*** Bug 868539 has been marked as a duplicate of this bug. ***
*** Bug 858100 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.