What freezes? Everything? Just the panel and the desktop? Windows too? Can you drag windows? What do you mean by "Freezes"? Can you still move the cursor? Do things still happen when you click on them?

What widget are you talking about that has a lightning bolt icon which changes to a battery icon?

That kind of phone are you connecting?

Created attachment 145692 [details]
status bar

freezes KDE Plasma, but other open applications continue to work. That is, the launcher and the status bar becomes completely unresponsive to actions.
Widget: battery and brightness
Telephone: Apple iphone 7, Unfortunately, I don’t have another phone, I can’t check it for example on android.

Thanks. Cannot reproduce with an old iPhone I dug up.

Strange. I tried to record a video from the screen so that you could see the actions. But when the phone is disconnected, the plasma process is restarted and everything works fine again. And without recording the screen hangs. Although I had a suspicion, perhaps the problem is not so much with the plasma itself, but with manjaro. Because to install the beta plasma, I had to climb over to an unstable branch. Is there an opportunity to try it on an unstable branch too?

Sure, go ahead.

Created attachment 145876 [details]
battery and brightness

(In reply to Nate Graham from comment #5)
> Sure, go ahead.

So. Yesterday I rolled back from the unstable manjaro branch and the kde beta to the previous version. And today, manjaro updates are already stable. 
I installed the beta kde plasma 5.24. And I no longer observe problems with hanging. But two others appeared: 
1) The battery widget icon and brightness do not change when the device is turned on or off.
2) After disconnecting the device, kde plasma restarts on its own, which, although sad, is not as critical as it used to be at first.

Can you check out before and after the crash (hang/restart) if there's anything useful in dmesg (kernel log) and plasmashell output (run it from a terminal like konsole)?

Also take a look at recent coredumpctl entries. The most interesting is `coredumpctl gdb <PID>` and in gdb type in `bt<Enter>` (without backticks, stands for "backtrace"). Note that in some cases coredumpctl needs to be run as sudo.

(In reply to ratijas from comment #8)
> Can you check out before and after the crash (hang/restart) if there's
> anything useful in dmesg (kernel log) and plasmashell output (run it from a
> terminal like konsole)?
> 
> Also take a look at recent coredumpctl entries. The most interesting is
> `coredumpctl gdb <PID>` and in gdb type in `bt<Enter>` (without backticks,
> stands for "backtrace"). Note that in some cases coredumpctl needs to be run
> as sudo.

I recorded two files before the crash: output file begin and after failure: outputfile_end. And by 'coredumpctl gdb <PID>` I don't quite understand what kind of process is needed. Specifically, I don't see a separate widget..

Created attachment 145930 [details]
output file begin

Created attachment 145931 [details]
output file end

> And by 'coredumpctl gdb <PID>` I don't quite understand what kind of process is needed. Specifically, I don't see a separate widget..

All applets normally live within the a plasmashell process. You can restart Plasma yourself in a terminal via either «plasmashell --replace» or (preferably, due to bugs in --replace) «killall plasmashell && plasmashell». Don't be scared just because it prints out a loooot of [[mostly harmless]] warnings.

Either way, just running «coredumpctl» lists all recent crashes top-to-bottom. Scroll down, and you'll likely recognize what you need. If there's more than one entry at a time, that's also an interesting info, since they are probably related.

The problem is no longer reproducible. The task can be closed. Thx

Ok, thanks!