Bug 388214 - Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...
Summary: Zombie notifications in plasmashell. There must be way to inspect/debug what ...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.11.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
: 383932 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-12-25 13:49 UTC by David Tonhofer
Modified: 2020-11-23 15:15 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Zombie notifications in action (93.84 KB, image/png)
2017-12-25 13:49 UTC, David Tonhofer
Details
There seems to be no processes corresponding to the notifications (74.58 KB, image/png)
2017-12-25 13:50 UTC, David Tonhofer
Details
demonstration on Arch Linux, Plasma 5.12.3, Dolphin 17.12.3 (544.98 KB, image/gif)
2018-03-16 17:10 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Tonhofer 2017-12-25 13:49:24 UTC
Created attachment 109509 [details]
Zombie notifications in action

In Fedora 27 KDE, which uses 

plasma-workspace-5.11.3-2.fc27.x86_64

I encounter the following:

I am doing some heavy rearrangement/copying operations in Dolphin, in parallel.

This seems to succeed (how do I into "I'm sure it succeeded?", ah, transactions and Unix filesystems, a problem since 1969 ;-) 

However, the plasmashell notification widget seems to remain in the "not sure" state (see attachment). 9 jobs are marked as "in progress" and display the "Zylon Moving Eye". 

However these notifications never go away. No processes seem to correspond to thos (see attachment) There is neither a title, nor a log, nor any explanation about what these are (basically, "zombie notifications", innit?) 

There needs to be a way to debug these. PID number, thread number. What caused the notification to appear, command line, anything. And indications about what happens if I press "pause" or "stop".
Comment 1 David Tonhofer 2017-12-25 13:50:02 UTC
Created attachment 109510 [details]
There seems to be no processes corresponding to the notifications
Comment 2 David Edmundson 2017-12-28 23:49:39 UTC
If you want to actually debug this stuff, check out kuiserver in dbus.
Comment 3 David Tonhofer 2017-12-30 14:00:55 UTC
kuiserver5, right?

Is there actually a documentation on that? Nothing at KDE docs.

I have found a blogpost: https://pindablog.wordpress.com/2008/07/24/more-on-kuiserver-and-extenders/
Comment 4 David Tonhofer 2018-01-27 18:11:27 UTC
Ok, it happened again.

It happens when you copy the contents of large directories (1000's of files) using Dolphin. 

At which point the world stops (even the clock gets stuck for 10 minutes...) 

And then you are plagued by 30 by thirty ghost notifications (maybe they are created whenever dolphin asks for overwrite confirmation?)
Comment 5 Nate Graham 2018-01-27 18:28:41 UTC
FWIW, we are actively working on improving the user case of copying thousands of files. E.g. see https://phabricator.kde.org/D10124 and https://phabricator.kde.org/D10085
Comment 6 Patrick Silva 2018-03-16 17:10:32 UTC
Created attachment 111446 [details]
demonstration on Arch Linux, Plasma 5.12.3, Dolphin 17.12.3

It just happened on my Arch Linux (Plasma 5.12.3, Dolphin 17.12.3) after I moved hundreds of jpg files to another partition.
Comment 7 Patrick Silva 2018-05-22 22:12:47 UTC
*** Bug 383932 has been marked as a duplicate of this bug. ***
Comment 8 Alexander Mentyu 2018-09-28 13:54:43 UTC
Possibly duplicate of this bug https://bugs.kde.org/show_bug.cgi?id=363357 + cannot reproduce it currently
Comment 9 Justin Zobel 2020-11-08 09:23:33 UTC
Thanks for the report David.

Now that both differentials have been merged can this be retested to confirm if the issue is resolved or needs further work, thanks.
Comment 10 Bug Janitor Service 2020-11-23 04:34:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Germano Massullo 2020-11-23 08:59:10 UTC
My personal experience is that I am no longer experiencing this bug
Comment 12 Nate Graham 2020-11-23 15:15:42 UTC
Thanks.

This isn't a super-actionable bug so let's call it fixed and re-open or file a new one if it happens again.