Version-Release number of selected component: emerald-0.8.8-5.fc18 Additional info: backtrace_rating: 4 cmdline: emerald-theme-manager crash_function: is_visible executable: /usr/bin/emerald-theme-manager kernel: 3.8.4-202.fc18.i686 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 is_visible at main.c:1222 #1 gtk_tree_model_filter_visible at gtktreemodelfilter.c:764 #2 gtk_tree_model_filter_row_inserted at gtktreemodelfilter.c:1460 #3 _gtk_marshal_VOID__BOXED_BOXED at gtkmarshalers.c:1311 #8 gtk_tree_model_row_inserted at gtktreemodel.c:1525 #9 gtk_list_store_insert at gtkliststore.c:1039 #10 gtk_list_store_append at gtkliststore.c:1144 #11 theme_list_append at main.c:53 #12 theme_scan_dir at main.c:203 #13 refresh_theme_list at main.c:235 Potential duplicate: bug 711014
Created attachment 718295 [details] File: backtrace
Created attachment 718296 [details] File: build_ids
Created attachment 718297 [details] File: cgroup
Created attachment 718298 [details] File: core_backtrace
Created attachment 718299 [details] File: dso_list
Created attachment 718300 [details] File: environ
Created attachment 718301 [details] File: limits
Created attachment 718302 [details] File: maps
Created attachment 718303 [details] File: open_fds
Created attachment 718304 [details] File: proc_pid_status
It would be very nice if you could give more info? What did you do exactly for trigger this report? Does it happend all the time if you're using emerald? You don't have to write a book, but only clicking on the send button in abrt-gui isn't a solution.
While importing theme backtrace_rating: 4 cmdline: emerald-theme-manager '/home/bohyn/.cache/.fr-Xg0l5b/Kore - Default.emerald' crash_function: is_visible executable: /usr/bin/emerald-theme-manager kernel: 3.8.11-200.fc18.x86_64 package: emerald-0.8.8-6.fc18 reason: Process /usr/bin/emerald-theme-manager was killed by signal 11 (SIGSEGV) uid: 1001 ureports_counter: 1
MATE: This is caused on first load of compiz, and choosing an emerald theme. mate-panel --reset fixes me up.
Does the issue occurs every time if you use the theme manager? Does the theme manager crash or only triger a abrt alarm?