Bug 895044

Summary: [abrt] Gtk:ERROR:gtkrbtree.c:465:_gtk_rbtree_insert_after: assertion failed: (_gtk_rbtree_is_nil (tree->root))
Product: [Fedora] Fedora Reporter: Ivan Mironov <ivan.mironov>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: actionless.loveless, asmolin84, braden, bugs.michael, cfergeau, dustin, emmanuel.pacaud, marwalk, mclasen, moez.roy, ovasik, scorpy_sk, w_pirker
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: abrt_hash:8d0282110bc0bd5a6a354aab3dfede851b231799
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:36:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Ivan Mironov 2013-01-14 11:12:16 UTC 
Description of problem:
Audacious was just open on different workspace. It even don't play anything when crashed.

Version-Release number of selected component:
audacious-3.3.3-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        audacious
crash_function: _gtk_rbtree_insert_after
executable:     /usr/bin/audacious
kernel:         3.6.11-3.fc18.x86_64
remote_result:  831444
uid:            1000
var_log_messages: Jan 14 16:51:56 localhost abrt[4493]: Saved core dump of pid 10615 (/usr/bin/audacious) to /var/spool/abrt/ccpp-2013-01-14-16:51:55-10615 (120102912 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 _gtk_rbtree_insert_after at gtkrbtree.c:465
 #5 gtk_tree_view_row_inserted at gtktreeview.c:8868
 #10 gtk_tree_model_row_inserted at gtktreemodel.c:1820
 #11 emit_row_inserted_for_node at gtkfilesystemmodel.c:309
 #12 node_set_visible_and_filtered_out at gtkfilesystemmodel.c:359
 #13 node_compute_visibility_and_filters at gtkfilesystemmodel.c:481
 #14 add_file at gtkfilesystemmodel.c:1867
 #15 _gtk_file_system_model_update_file at gtkfilesystemmodel.c:1941
 #16 gtk_file_system_model_query_done at gtkfilesystemmodel.c:1226
 #17 g_simple_async_result_complete at gsimpleasyncresult.c:775
Comment 1 Ivan Mironov 2013-01-14 11:12:20 UTC 
Created attachment 678178 [details]
File: backtrace
Comment 2 Ivan Mironov 2013-01-14 11:12:26 UTC 
Created attachment 678179 [details]
File: cgroup
Comment 3 Ivan Mironov 2013-01-14 11:12:28 UTC 
Created attachment 678180 [details]
File: core_backtrace
Comment 4 Ivan Mironov 2013-01-14 11:12:31 UTC 
Created attachment 678181 [details]
File: dso_list
Comment 5 Ivan Mironov 2013-01-14 11:12:33 UTC 
Created attachment 678182 [details]
File: environ
Comment 6 Ivan Mironov 2013-01-14 11:12:35 UTC 
Created attachment 678183 [details]
File: limits
Comment 7 Ivan Mironov 2013-01-14 11:12:38 UTC 
Created attachment 678184 [details]
File: maps
Comment 8 Ivan Mironov 2013-01-14 11:12:40 UTC 
Created attachment 678185 [details]
File: open_fds
Comment 9 Ivan Mironov 2013-01-14 11:12:42 UTC 
Created attachment 678186 [details]
File: proc_pid_status
Comment 10 Ivan Mironov 2013-01-25 08:43:35 UTC 
No more crashes. Seems fixed in one of the latest updates.
Comment 11 Ivan Mironov 2013-01-29 05:23:08 UTC 
No, it crashed again =(.

I think that this happens only when "Search Tool" is open.
Comment 12 Christophe Fergeau 2013-03-11 09:51:21 UTC 
*** Bug 880791 has been marked as a duplicate of this bug. ***
Comment 13 Christophe Fergeau 2013-03-11 09:52:54 UTC 
*** Bug 886132 has been marked as a duplicate of this bug. ***
Comment 14 Christophe Fergeau 2013-03-11 09:53:42 UTC 
*** Bug 892333 has been marked as a duplicate of this bug. ***
Comment 15 Christophe Fergeau 2013-03-11 09:54:14 UTC 
*** Bug 902058 has been marked as a duplicate of this bug. ***
Comment 16 Christophe Fergeau 2013-03-11 09:55:57 UTC 
*** Bug 879850 has been marked as a duplicate of this bug. ***
Comment 17 Christophe Fergeau 2013-03-11 09:58:52 UTC 
*** Bug 902650 has been marked as a duplicate of this bug. ***
Comment 18 Christophe Fergeau 2013-03-11 10:03:38 UTC 
This seems to be reported upstream as https://bugzilla.gnome.org/show_bug.cgi?id=692546
Comment 19 Fedora End Of Life 2013-12-21 15:17:32 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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.
Comment 20 Fedora End Of Life 2014-02-05 22:57:45 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 21 Moez Roy 2014-06-13 05:18:27 UTC 
problem still exists in F20
Comment 22 Fedora End Of Life 2015-05-29 08:50:59 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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.
Comment 23 Fedora End Of Life 2015-06-30 00:36:56 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.