Problem with plasma5-applets-thermal-monitor

After the latest Stable update, the plasmoid from the package plasma5-applets-thermal-monitor from the repos seems to be broken.

Right clicking on the widget and choosing "Configure Thermal Monitor..." causes plasmashell to crash.

journalctl entry
Jul 21 08:22:36 hostname systemd-coredump[102791]: Process 102006 (plasmashell) of user 1000 dumped core.
                                              
     Stack trace of thread 102006:
     #0  0x00007fc3298db355 raise (libc.so.6 + 0x3c355)
     #1  0x00007fc3298db3e0 __restore_rt (libc.so.6 + 0x3c3e0)
     #2  0x00007fc329d512df _ZNK12QMapNodeBase8nextNodeEv (libQt5Core.so.5 + 0x10c2df)
     #3  0x00007fc32bd41f03 _ZN6Plasma13DataContainer14checkForUpdateEv (libKF5Plasma.so.5 + 0x4bf03)
     #4  0x00007fc329f2fa60 n/a (libQt5Core.so.5 + 0x2eaa60)
     #5  0x00007fc329e64449 _ZN8QProcess8finishedEiNS_10ExitStatusE (libQt5Core.so.5 + 0x21f449)
     #6  0x00007fc329e69d96 n/a (libQt5Core.so.5 + 0x224d96)
     #7  0x00007fc329e69ece n/a (libQt5Core.so.5 + 0x224ece)
     #8  0x00007fc329f2fa60 n/a (libQt5Core.so.5 + 0x2eaa60)
     #9  0x00007fc329f32f90 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2edf90)
     #10 0x00007fc329f3379d _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2ee79d)
     #11 0x00007fc32aa1c702 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15c702)
     #12 0x00007fc329ef87ba _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b37ba)
     #13 0x00007fc329f51f46 n/a (libQt5Core.so.5 + 0x30cf46)
     #14 0x00007fc3283a443c g_main_context_dispatch (libglib-2.0.so.0 + 0x5243c)
     #15 0x00007fc3283f21d9 n/a (libglib-2.0.so.0 + 0xa01d9)
     #16 0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #17 0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #18 0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #19 0x00007fc329eff5c4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2ba5c4)
     #20 0x000055ff20784f5d n/a (plasmashell + 0x1df5d)
     #21 0x00007fc3298c6002 __libc_start_main (libc.so.6 + 0x27002)
     #22 0x000055ff2078519e _start (plasmashell + 0x1e19e)
     
     Stack trace of thread 102035:
     #0  0x00007fc3291f1e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfe32)
     #1  0x00007fc329d19e84 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e84)
     #2  0x00007fc32b99ae7b n/a (libQt5Quick.so.5 + 0x1f4e7b)
     #3  0x00007fc32b99d41b n/a (libQt5Quick.so.5 + 0x1f741b)
     #4  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #5  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #6  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102014:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc3283f2168 n/a (libglib-2.0.so.0 + 0xa0168)
     #2  0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #3  0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #4  0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #5  0x00007fc329d12c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
     #6  0x00007fc32b650789 n/a (libQt5Qml.so.5 + 0x30b789)
     #7  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #8  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #9  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102032:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc3283f2168 n/a (libglib-2.0.so.0 + 0xa0168)
     #2  0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #3  0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #4  0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #5  0x00007fc329d12c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
     #6  0x00007fc2e25cbbab _ZN15KCupsConnection3runEv (libkcupslib.so + 0x20bab)
     #7  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #8  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #9  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102013:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc3283f2168 n/a (libglib-2.0.so.0 + 0xa0168)
     #2  0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #3  0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #4  0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #5  0x00007fc329d12c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
     #6  0x00007fc32b003098 n/a (libQt5DBus.so.5 + 0x17098)
     #7  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #8  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #9  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102012:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc32bdc063b n/a (libxcb.so.1 + 0xc63b)
     #2  0x00007fc32bdc237b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
     #3  0x00007fc32557cc51 n/a (libQt5XcbQpa.so.5 + 0x5dc51)
     #4  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #5  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #6  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102056:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc3283f2168 n/a (libglib-2.0.so.0 + 0xa0168)
     #2  0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #3  0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #4  0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #5  0x00007fc329d12c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
     #6  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #7  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #8  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102771:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc3283f2168 n/a (libglib-2.0.so.0 + 0xa0168)
     #2  0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #3  0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #4  0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #5  0x00007fc329d12c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
     #6  0x00007fc32b650789 n/a (libQt5Qml.so.5 + 0x30b789)
     #7  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #8  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #9  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102778:
     #0  0x00007fc3291f2158 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x10158)
     #1  0x00007fc329d19e08 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e08)
     #2  0x00007fc329d18084 n/a (libQt5Core.so.5 + 0xd3084)
     #3  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #4  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #5  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102780:
     #0  0x00007fc3291f2158 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x10158)
     #1  0x00007fc329d19e08 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e08)
     #2  0x00007fc329d18084 n/a (libQt5Core.so.5 + 0xd3084)
     #3  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #4  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #5  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102781:
     #0  0x00007fc3291f2158 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x10158)
     #1  0x00007fc329d19e08 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e08)
     #2  0x00007fc329d18084 n/a (libQt5Core.so.5 + 0xd3084)
     #3  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #4  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #5  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102016:
     #0  0x00007fc3291f1e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfe32)
     #1  0x00007fc329d19e84 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e84)
     #2  0x00007fc32b99ae7b n/a (libQt5Quick.so.5 + 0x1f4e7b)
     #3  0x00007fc32b99d41b n/a (libQt5Quick.so.5 + 0x1f741b)
     #4  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #5  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #6  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102017:
     #0  0x00007fc32999405f __poll (libc.so.6 + 0xf505f)
     #1  0x00007fc3283f2168 n/a (libglib-2.0.so.0 + 0xa0168)
     #2  0x00007fc3283a3221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
     #3  0x00007fc329f51331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
     #4  0x00007fc329ef713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
     #5  0x00007fc329d12c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
     #6  0x00007fc32b8ec18b n/a (libQt5Quick.so.5 + 0x14618b)
     #7  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #8  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #9  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102095:
     #0  0x00007fc3291f1e32 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfe32)
     #1  0x00007fc329d19e84 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e84)
     #2  0x00007fc32b99ae7b n/a (libQt5Quick.so.5 + 0x1f4e7b)
     #3  0x00007fc32b99d41b n/a (libQt5Quick.so.5 + 0x1f741b)
     #4  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #5  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #6  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)
     
     Stack trace of thread 102779:
     #0  0x00007fc3291f2158 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x10158)
     #1  0x00007fc329d19e08 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4e08)
     #2  0x00007fc329d18084 n/a (libQt5Core.so.5 + 0xd3084)
     #3  0x00007fc329d13e0f n/a (libQt5Core.so.5 + 0xcee0f)
     #4  0x00007fc3291eb422 start_thread (libpthread.so.0 + 0x9422)
     #5  0x00007fc32999ebf3 __clone (libc.so.6 + 0xffbf3)

It's probably an upstream issue, but it is a package from the repos, so it seems appropriate to mention it here.

https://bugs.kde.org/show_bug.cgi?id=421392 resp. https://bugs.kde.org/show_bug.cgi?id=422230

it is already fixed, hopefully will make it into one of the next versions ^^

1 Like

Hi!
try this

2 Likes

I've had no luck with this fix. The files mentioned in the readme that have to be overwritten do not exist, and creating them changes nothing.

However, since the next update will probably contain the bug fix, it's not a big issue. Thanks for the help!

Hi!
I make a mistake, I write so fast the files' path that i write them wrong. It's already fixed.
I just uploaded the files 'cause this post and I'm so noob with gitlab that I should've see that comming.
Replay with the outcome if you try again, please. Thanks

Still no luck. You have another mistake in the path:

~/.local/share/plasma/plasmoids/org.kde.thermalMonitor//contents/ui/config/
                                                       ^

but even with that typo fixed, the widget is now gone from the panel and a new one cannot be created.

Hi!
Thanks for the typo!! Fixed!
It's weird that you haven't the same folder tree. Did you find any of the files on your widget folder? even if they're in other path, just out curiosity.
Sorry for all the mishaps!!

Hi!
Are we talking about this one, right?

I think that's the one, but I installed it with pacman from the repos. And no, these directories do not exist on my install.

The config files are strored in /usr/share/plasma/plasmoids/org.kde.thermalMonitor/

Now, there should be no need to change those files, since the files in ~/.local/share/plasma/plasmoids/org.kde.thermalMonitor/ should have precedence, but they do not exist. When I create them, the widget does not work. So, it seems to me there is something wrong in your patched files.

Hi!
Did you find the widget forder? Even if the paths aren't the same, those files have to be somewhere
I installed by "add new" from the right click menu

Fwiw, this bug [which i'd not known, til reading your post] remains present in my Arch. I just tried the right-click "Configure Thermal Monitor..." & sure enough Plasmashell did a whoopsie.

Executable: plasmashell (deleted) PID: 1544 Signal: Segmentation fault (11) Time: 21/07/2020 18:38:16 AEST

My version of plasma5-applets-thermal-monitor is 1.2.9-2 -> 1.2.9-3, updated 12 July.

Bummer, btw.

1 Like

Hi!
Maybe the different installation way is the problem, I'll look into it.
I'm using those files in 2 installations of thermal monitor widget in manjaro kde, both updated to the date (stable), and they work just fine,but like I said, I installed the widget from de "add new" option from the right click menu.

Thanks for confirming it!

So that probably means the next Manjaro Stable update won't fix it, since you a have newer version of Plasma on your Arch machine. That sucks to a minor degree. :frowning_face:

1 Like

I know i'm a wet blanket but yes that's also the conclusion i had assumed. Bummer once more.


Actually, our logic might be 100% wrong. Given Stables are coming with often a fairly protracted lag, it seems feasible that in the meantime the upstream fix might have flowed into Arch, so i'll get it, thence in the usual way into MJ Unstable then Testing, then Stable. So actually afaik the next Stable might well have it, or you could pull it early [unless it has Frameworks dependencies] from Unstable or Testing... ? Maybe...

1 Like

Well, if you notice it on your Arch install, post it here, please :slight_smile:

1 Like

No way, piss off!!

Allegedly.

:crazy_face:

Is this still valid?


I didn't tested it since i use kargos ... i think is the 3rd or 4th topic with this issue :stuck_out_tongue:

1 Like

thx for the temp fix, as I use the plasma5-applets-thermal-monitor package form the community repo

Yeah, the AUR package plasma5-applets-thermal-monitor-git works fine, the package from the repos does not.

Thermal Monitor Fix

Corrected version of Thermal Monitor widget added to kde store.

1 Like

Forum kindly sponsored by