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 18 25165858 power-manager-plugin 'Plugin del gestore di energia' 'Mostra il livello di carica dei dispositivi e controlla la luminosit\xc3\xa0 dello schermo' '' crash_function: strlen executable: /usr/lib64/xfce4/panel/wrapper-2.0 global_pid: 1749 kernel: 4.2.6-301.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:68 #1 get_device_description at xfpm-power-common.c:267 #2 power_manager_button_update_device_icon_and_details at ../power-manager-button.c:454 #8 g_object_notify_by_spec_internal at gobject.c:1154 #9 g_object_notify at gobject.c:1202 #15 g_object_notify_by_spec_internal at gobject.c:1154 #16 g_object_notify at gobject.c:1202 #17 up_device_glue_proxy_g_properties_changed at up-device-glue.c:2706 #18 ffi_call_unix64 at ../src/x86/unix64.S:76 #19 ffi_call at ../src/x86/ffi64.c:525 Potential duplicate: bug 1227082
Created attachment 1104450 [details] File: backtrace
Created attachment 1104451 [details] File: cgroup
Created attachment 1104452 [details] File: core_backtrace
Created attachment 1104453 [details] File: dso_list
Created attachment 1104454 [details] File: environ
Created attachment 1104455 [details] File: exploitable
Created attachment 1104456 [details] File: limits
Created attachment 1104457 [details] File: maps
Created attachment 1104458 [details] File: mountinfo
Created attachment 1104459 [details] File: namespaces
Created attachment 1104460 [details] File: open_fds
Created attachment 1104461 [details] File: proc_pid_status
What were you doing when this happened? Can you duplicate it?
*** Bug 1309708 has been marked as a duplicate of this bug. ***
I might be a duplicate of BZ1283347.
Indeed it does look like a dupe. ;) Thanks! Do upgrade to the latest xfce4-power-manager and if you still see this, please file a new bug. *** This bug has been marked as a duplicate of bug 1283347 ***