Version-Release number of selected component: xfce4-panel-4.12.0-4.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libxfce4powermanager.so 11 25249992 power-manager-plugin '\xe7\x94\xb5\xe9\x87\x8f\xe7\xae\xa1\xe7\x90\x86\xe6\x8f\x92\xe4\xbb\xb6' '\xe6\x98\xbe\xe7\xa4\xba\xe8\xae\xbe\xe5\xa4\x87\xe7\x94\xb5\xe9\x87\x8f\xe5\xb9\xb6\xe6\x8e\xa7\xe5\x88\xb6\xe5\xb1\x8f\xe5\xb9\x95\xe4\xba\xae\xe5\xba\xa6' '' crash_function: _gtk_widget_run_controllers executable: /usr/lib64/xfce4/panel/wrapper-2.0 global_pid: 10241 kernel: 4.2.6-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_widget_run_controllers at gtkwidget.c:7304 #1 scale_menu_item_grab_broken at ../scalemenuitem.c:324 #2 scale_menu_item_button_release_event at ../scalemenuitem.c:281 #3 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:131 #4 _g_closure_invoke_va at gclosure.c:864 #7 gtk_widget_event_internal at gtkwidget.c:7692 #8 propagate_event_up at gtkmain.c:2517 #9 propagate_event at gtkmain.c:2619 #10 gtk_main_do_event at gtkmain.c:1850 #16 gtk_main at gtkmain.c:1241
Created attachment 1099173 [details] File: backtrace
Created attachment 1099174 [details] File: cgroup
Created attachment 1099175 [details] File: core_backtrace
Created attachment 1099176 [details] File: dso_list
Created attachment 1099177 [details] File: environ
Created attachment 1099178 [details] File: limits
Created attachment 1099179 [details] File: maps
Created attachment 1099180 [details] File: mountinfo
Created attachment 1099181 [details] File: namespaces
Created attachment 1099182 [details] File: open_fds
Created attachment 1099183 [details] File: proc_pid_status
Created attachment 1099184 [details] File: exploitable
Reassigning to xfpm4 as cmdline implicates. Can you reproduce this crash? What do you do therefore?
It happened When I use xfce4-panel power management plugin to adjust brightness。
Thinkpad T430 with nvs 5400m... Or need any other information?
*** This bug has been marked as a duplicate of bug 1226858 ***