Version-Release number of selected component: xfce4-panel-4.12.2-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libxfce4-sensors-plugin.so 29 10485811 xfce4-sensors-plugin crash_function: strlen executable: /usr/lib64/xfce4/panel/wrapper-2.0 journald_cursor: s=05c2c8f68daa4abfa38de83c84b87720;i=14b1;b=4478c85d05ac49e99f942237a1b92a9a;m=2d09f1d1;t=5765d655b1c49;x=b08d992b3626bb0f kernel: 4.18.7-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1485431 [details] File: backtrace
Created attachment 1485432 [details] File: cgroup
Created attachment 1485433 [details] File: core_backtrace
Created attachment 1485434 [details] File: cpuinfo
Created attachment 1485435 [details] File: dso_list
Created attachment 1485436 [details] File: environ
Created attachment 1485437 [details] File: limits
Created attachment 1485438 [details] File: maps
Created attachment 1485439 [details] File: mountinfo
Created attachment 1485440 [details] File: open_fds
Created attachment 1485441 [details] File: proc_pid_status
Created attachment 1485442 [details] File: exploitable
Similar problem has been detected: The system was recently rebooted after applying all available F28 updates. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libxfce4-sensors-plugin.so 17 10485795 xfce4-sensors-plugin Sensor plugin Show sensor values. crash_function: strlen executable: /usr/lib64/xfce4/panel/wrapper-2.0 journald_cursor: s=b3cc44defd384508874f769deacd18b5;i=12227d;b=0bfaf5682a0142fcbbff79545a3c6ac3;m=29701d49;t=57adca314426d;x=4be301868abdaca6 kernel: 4.18.18-200.fc28.x86_64 package: xfce4-panel-4.12.2-2.fc28 reason: wrapper-2.0 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I also have this problem. I upgraded to Fedora 28 last night.
Similar problem has been detected: It happened spontaneously a few minutes after system start-up. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libxfce4-sensors-plugin.so 16 10485800 xfce4-sensors-plugin Sensor plugin Show sensor values. crash_function: strlen executable: /usr/lib64/xfce4/panel/wrapper-2.0 journald_cursor: s=fa059d3b789b42c9b9bb38041cfde23d;i=21841d;b=66dab441b985428a81bfe3762a207c5e;m=248b00a9;t=5879fe99792a9;x=513cba70f23e467a kernel: 5.0.9-100.fc28.x86_64 package: xfce4-panel-4.12.2-2.fc28 reason: wrapper-2.0 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.