Description of problem: I switched my Gtk3 theme in the GNOME tweak tool when BLueman Applet crashed and I think took half my GNOME session with it. Version-Release number of selected component: blueman-2.0-6.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: python /usr/bin/blueman-applet crash_function: _gtk_css_value_equal executable: /usr/bin/python2.7 global_pid: 3189 kernel: 4.0.4-303.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Sat 2015-05-30 12:28:15 CEST, end at Sun 2015-06-14 12:38:11 CEST. -- Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_css_value_equal at gtkcssvalue.c:118 #1 gtk_css_style_get_difference at gtkcssstyle.c:89 #2 _gtk_style_context_validate at gtkstylecontext.c:3076 #3 gtk_container_idle_sizer at gtkcontainer.c:1856 #4 _g_closure_invoke_va at gclosure.c:831 #6 g_signal_emit_by_name at gsignal.c:3401 #7 gdk_frame_clock_paint_idle at gdkframeclockidle.c:408 #14 gtk_main at gtkmain.c:1219 #15 ffi_call_unix64 at ../src/x86/unix64.S:76 #16 ffi_call at ../src/x86/ffi64.c:525
Created attachment 1038497 [details] File: backtrace
Created attachment 1038498 [details] File: cgroup
Created attachment 1038499 [details] File: core_backtrace
Created attachment 1038500 [details] File: dso_list
Created attachment 1038501 [details] File: environ
Created attachment 1038502 [details] File: limits
Created attachment 1038503 [details] File: maps
Created attachment 1038504 [details] File: mountinfo
Created attachment 1038505 [details] File: namespaces
Created attachment 1038506 [details] File: open_fds
Created attachment 1038507 [details] File: proc_pid_status
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.