Hide Forgot
Description of problem: Sorry, no clue, just ran the tool. Version-Release number of selected component: lxappearance-0.5.2-6.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: lxappearance crash_function: install_icon_theme_package executable: /usr/bin/lxappearance kernel: 3.11.6-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 install_icon_theme_package at utils.c:195 #3 install_icon_theme at utils.c:234 #4 _g_closure_invoke_va at gclosure.c:840 #7 gtk_real_button_released at gtkbutton.c:1712 #8 _g_closure_invoke_va at gclosure.c:840 #11 gtk_button_button_release at gtkbutton.c:1604 #12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #17 gtk_widget_event_internal at gtkwidget.c:5017 #18 gtk_widget_event at gtkwidget.c:4814 #19 gtk_propagate_event at gtkmain.c:2490 Potential duplicate: bug 962152
Created attachment 830987 [details] File: backtrace
Created attachment 830988 [details] File: cgroup
Created attachment 830989 [details] File: core_backtrace
Created attachment 830990 [details] File: dso_list
Created attachment 830991 [details] File: environ
Created attachment 830992 [details] File: exploitable
Created attachment 830993 [details] File: limits
Created attachment 830994 [details] File: maps
Created attachment 830995 [details] File: open_fds
Created attachment 830996 [details] File: proc_pid_status
Created attachment 830997 [details] File: var_log_messages
Another user experienced a similar problem: It happened when I clicked the 'Apply' button to apply a new cursor theme. Oddly enough though, it didn't occur when I clicked 'Apply' again to revert back to the original cursor theme. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: lxappearance crash_function: install_icon_theme_package executable: /usr/bin/lxappearance kernel: 3.13.5-202.fc20.x86_64 package: lxappearance-0.5.2-6.fc20 reason: lxappearance 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.