Version-Release number of selected component: baobab-3.10.1-1.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: baobab crash_function: _cairo_arc_in_direction executable: /usr/bin/baobab kernel: 3.13.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 _cairo_arc_in_direction at cairo-arc.c:189 #5 _cairo_default_context_arc at cairo-default-context.c:783 #6 cairo_arc at cairo.c:1641 #7 baobab_ringschart_real_draw_item at baobab-ringschart.c:1167 #8 baobab_chart_real_draw at baobab-chart.c:1193 #9 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #10 gtk_widget_draw_marshallerv at gtkwidget.c:1009 #11 _g_closure_invoke_va at gclosure.c:840 #14 _gtk_widget_draw_internal at gtkwidget.c:6441 #16 _gtk_widget_draw_windows at gtkwidget.c:6542
Created attachment 888049 [details] File: backtrace
Created attachment 888050 [details] File: cgroup
Created attachment 888051 [details] File: core_backtrace
Created attachment 888052 [details] File: dso_list
Created attachment 888053 [details] File: environ
Created attachment 888054 [details] File: limits
Created attachment 888055 [details] File: maps
Created attachment 888056 [details] File: open_fds
Created attachment 888057 [details] File: proc_pid_status
Created attachment 888058 [details] File: var_log_messages
Another user experienced a similar problem: 1. had been looking at folders from different mounts. 2. clicked in a small folder 2nd bottom of list. 3. clicked in smallest folder at bottom list (may have double-clicked, or click dragged - not sure how the OS took the mouse action. 4. crash. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: baobab /home/work/2 crash_function: _cairo_arc_in_direction executable: /usr/bin/baobab kernel: 3.18.9-100.fc20.x86_64 package: baobab-3.10.1-1.fc20 reason: baobab killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
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.
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.