Description of problem: This happened after I closed Glade. I had been editing a UI file. Version-Release number of selected component: glade-3.15.0-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: glade /home/mcatanzaro/jhbuild/src/gnome-chess/data/gnome-chess.ui crash_function: glade_project_model_get_iter_for_object executable: /usr/bin/glade kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 glade_project_model_get_iter_for_object at glade-project.c:4294 #6 glade_project_notify_row_has_child at glade-project.c:2721 #7 glade_project_remove_object at glade-project.c:3014 #8 glade_project_dispose at glade-project.c:329 #10 glade_design_view_set_project at glade-design-view.c:241 #11 glade_design_view_finalize at glade-design-view.c:399 #13 do_close at glade-window.c:1447 #14 on_quit_action_activate at glade-window.c:2964 #19 _gtk_action_emit_activate at gtkaction.c:801 #20 gtk_action_activate at gtkaction.c:832
Created attachment 769685 [details] File: backtrace
Created attachment 769686 [details] File: cgroup
Created attachment 769687 [details] File: core_backtrace
Created attachment 769688 [details] File: dso_list
Created attachment 769689 [details] File: environ
Created attachment 769690 [details] File: limits
Created attachment 769691 [details] File: maps
Created attachment 769692 [details] File: open_fds
Created attachment 769693 [details] File: proc_pid_status
Created attachment 769694 [details] File: var_log_messages
Created attachment 769695 [details] UI file Just happened again. Here's the UI I was working on, though I don't know it's relevant.
Glade crashes every time I close it, no matter what I'm editing. This seems to be 100% reproducible. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: glade crash_function: glade_project_model_get_iter_for_object executable: /usr/bin/glade kernel: 3.9.9-302.fc19.x86_64 package: glade-3.15.0-1.fc19 reason: Process /usr/bin/glade was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
glade flightdeck.ui (from http://gna.org/projects/vfrnav) then quit reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: glade flightdeck.ui crash_function: glade_project_model_get_iter_for_object executable: /usr/bin/glade kernel: 3.10.5-201.fc19.x86_64 package: glade-3.15.0-1.fc19 reason: Process /usr/bin/glade was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1591
I opened the devassistant.glade file and made some modifications. Afterwards I saved it. Till now all works properly and devassistant.glade file was saved successfully. When I have tried to close glade application then glade crashed with SIGABRT. Problem is reproducible. You can download devassistant.glade file from repo: https://github.com/bkabrda/devassistant/blob/master/devassistant/gui/devel-assistant.glade reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: glade crash_function: glade_project_model_get_iter_for_object executable: /usr/bin/glade kernel: 3.11.1-200.fc19.x86_64 package: glade-3.15.0-1.fc19 reason: Process /usr/bin/glade was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
While I were editing two documents, I closed one of them (the tab) which caused glade to crash. Unfortunately It is not reproducible every time. Maybe there is something special about my documents. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: glade crash_function: glade_project_model_get_iter_for_object executable: /usr/bin/glade kernel: 3.11.6-200.fc19.x86_64 package: glade-3.15.0-1.fc19 reason: Process /usr/bin/glade was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 19270
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.
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.