Description of problem: I opened exaile and it instantly crashed. Version-Release number of selected component: exaile-3.4.3-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python2 /usr/share/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui crash_function: miUnionNonO executable: /usr/bin/python2.7 kernel: 3.18.7-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 miUnionNonO at gdkregion-generic.c:1123 #5 miRegionOp at gdkregion-generic.c:942 #6 gdk_region_union at gdkregion-generic.c:1266 #7 gdk_window_invalidate_maybe_recurse_full at gdkwindow.c:6000 #8 gtk_widget_invalidate_widget_windows at gtkwidget.c:4004 #9 gtk_widget_size_allocate at gtkwidget.c:4146 #10 gtk_notebook_page_allocate at gtknotebook.c:5992 #11 gtk_notebook_pages_allocate at gtknotebook.c:5886 #12 gtk_notebook_size_allocate at gtknotebook.c:2311 #13 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1160 Potential duplicate: bug 1079471
Created attachment 994123 [details] File: backtrace
Created attachment 994124 [details] File: cgroup
Created attachment 994125 [details] File: core_backtrace
Created attachment 994128 [details] File: dso_list
Created attachment 994129 [details] File: environ
Created attachment 994131 [details] File: limits
Created attachment 994134 [details] File: maps
Created attachment 994136 [details] File: open_fds
Created attachment 994138 [details] File: proc_pid_status
Created attachment 994139 [details] File: var_log_messages
*** Bug 1194972 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: I was starting Exaile for the first time of my session, and it instantly crashed. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python2 /usr/share/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui crash_function: miUnionNonO executable: /usr/bin/python2.7 kernel: 3.18.7-200.fc21.x86_64 package: exaile-3.4.3-1.fc21 reason: python2.7 killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Sorry for the last comment: I thought this was a different kind of crash and thus I used ABRt to report it.
*** Bug 1208781 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.