Bug 446287 - Restarting Plasma causes job progress to be shown in a separate window rather than as Plasma notifications
Summary: Restarting Plasma causes job progress to be shown in a separate window rather...
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.23.3
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-30 17:07 UTC by paninomaninodesu
Modified: 2024-02-22 20:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Dolphin showing file copy status the wrong way (196.51 KB, image/jpeg)
2021-11-30 17:07 UTC, paninomaninodesu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description paninomaninodesu 2021-11-30 17:07:41 UTC
Created attachment 144089 [details]
Dolphin showing file copy status the wrong way

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Execute command "kquitapp5 plasmashell && kstart5 plasmashell" from KDE Connect
2. Wait for the Shell to refresh and continues using normally
3. Eventually notice some minor things that appear to not be working or showing as intended

OBSERVED RESULT
Example, use Dolphin to navigate to any folder, open a compressed file and extract it's content to some folder. In the panel a second Dolphin icon appears, a small windows it's opened showing the file being copied.

EXPECTED RESULT
Normally instead of a second Dolphin icon appearing it should only appear above the icon a number indicating how many files are being copied, and the icon should be colored to work as a progress bar. In the notification widget it should appear a small circle icon showing the percentage of the file copied until it's finished. When the task begins and end it should appear a notification informing the status of the task, that it started and that it finished.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon User - Plasma 25th Anniversary Edition x86_64 
(available in About System)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
This is probably an old problem that I had not realized until now, because maybe don't always happen?
This "bug" with Dolphin is just an example, there may be others that are not easy to notice. But even so, even if it's something that you may not even notice it's still a problem.
Yesterday I noticed the described bug, waited until today to test again to confirm.
Yesterday I had refreshed Plasma using that command via KDE Connect (that I used KDE Connect makes no difference, it's just more convenient to use the phone than using terminal or krunner), today I still didn't... until now. Now I refreshed Plasma and tried to extract other file again to see if the "bug" appears. Yes, it happened. Refreshing Plasma is breaking functionality. This should be "a bug", right?
Comment 1 Nate Graham 2021-12-01 22:47:34 UTC
We'll need separate bug reports for each issue. This particular one would seem to indicate that the notification system disn't get started properly. if you open the Notifications applet in your System Tray, what does it show?
Comment 2 paninomaninodesu 2021-12-01 23:19:51 UTC
"If you open the Notifications applet in your System Tray, what does it show?"

As far as I can tell it's shows normally, there's no apparent change there, that's why I hand't noticed before and had not associated that change in behavior when copying files on Dolphin with the refresh.
It's not that everything stops working because of the refresh, it's just that thing that it's affected (or so it seems).
Comment 3 Nate Graham 2021-12-03 16:19:03 UTC
OK, thanks for the info.
Comment 4 Nate Graham 2024-02-22 20:47:02 UTC
Anyway, this happens when an app launches before Plasma does, and hence it finds no notification server to send jobs to. The app could periodically poll for a new one, but that would be up to each app, and it's a very rare circumstance and hence probably not going to happen everywhere, or even anywhere.

So unfortunately I'm not sure there's much if anything we can do about this, sorry.