Bug 986681

Summary: [abrt] Gtk:ERROR:gtkrbtree.c:465:_gtk_rbtree_insert_after: assertion failed: (_gtk_rbtree_is_nil (tree->root))
Product: [Fedora] Fedora Reporter: Alex <alex334599>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bugs.michael, ccecchi, malkodan, mclasen, moez.roy, vonsch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8d0282110bc0bd5a6a354aab3dfede851b231799
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:17:09 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
File: xsession_errors none

Description Alex 2013-07-21 15:10:30 UTC 
Description of problem:
I was going to add a file and opened the file manager (Caja) by pressing [F]
After the FM was opened I remembered that I needed to edit a playlist file (m3u).
This file was located in the directory the FM was currently in.

I edited the file and (upon saving, I think) audacious crashed.

---
Instructions for repeating:
Open audacious
Press f
Open emacs
Edit a file in the directory the FM is currently in.
Save file
Should result in a crash of audacious.

Version-Release number of selected component:
audacious-3.4-1.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        audacious
crash_function: _gtk_rbtree_insert_after
executable:     /usr/bin/audacious
kernel:         3.9.9-302.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jul 19 08:00:16 localhost abrt[23458]: Saved core dump of pid 2469 (/usr/bin/audacious) to /var/tmp/abrt/ccpp-2013-07-19-08:00:15-2469 (106729472 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:8866
 #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_task_return_now at gtask.c:1105
Comment 1 Alex 2013-07-21 15:10:35 UTC 
Created attachment 776458 [details]
File: backtrace
Comment 2 Alex 2013-07-21 15:10:38 UTC 
Created attachment 776459 [details]
File: cgroup
Comment 3 Alex 2013-07-21 15:10:43 UTC 
Created attachment 776460 [details]
File: core_backtrace
Comment 4 Alex 2013-07-21 15:10:46 UTC 
Created attachment 776461 [details]
File: dso_list
Comment 5 Alex 2013-07-21 15:10:49 UTC 
Created attachment 776462 [details]
File: environ
Comment 6 Alex 2013-07-21 15:10:53 UTC 
Created attachment 776463 [details]
File: limits
Comment 7 Alex 2013-07-21 15:10:57 UTC 
Created attachment 776464 [details]
File: maps
Comment 8 Alex 2013-07-21 15:11:00 UTC 
Created attachment 776465 [details]
File: open_fds
Comment 9 Alex 2013-07-21 15:11:04 UTC 
Created attachment 776466 [details]
File: proc_pid_status
Comment 10 Alex 2013-07-21 15:11:07 UTC 
Created attachment 776467 [details]
File: xsession_errors
Comment 11 Michael Schwendt 2013-07-21 15:42:38 UTC 
Are you sure it's the MATE Desktop file manager "Caja"? I think it's GTK+'s file manager.

Similar to bug 895044 (Fedora 18).

Dunno a safe way to reproduce it yet, but indeed, keeping the file manager open while creating/editing/removing files in the open directory, can crash it. Whether it crashes may depend on what other files are located in the dir.
Comment 12 Moez Roy 2014-06-13 05:33:05 UTC 
(In reply to Michael Schwendt from comment #11)
> Dunno a safe way to reproduce it yet, but indeed, keeping the file manager
> open while creating/editing/removing files in the open directory, can crash
> it. Whether it crashes may depend on what other files are located in the dir.

Very similar, except in my case I had Gnome Tweak Tool open to change the desktop background and was creating some pictures using LO Draw.
Comment 13 Fedora End Of Life 2015-01-09 19:01:54 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 14 Fedora End Of Life 2015-02-17 16:17:09 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.