| Summary: | When notifications appear plasma freezes for 10-15 seconds | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | temporary987 |
| Component: | Notifications | Assignee: | Martin Klapetek <mklapetek> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | plasma-bugs |
| Priority: | NOR | ||
| Version: | 5.3.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| URL: | https://vid.me/tR8v | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
bustle log
and in pdf |
||
|
Description
temporary987
2015-04-27 05:21:44 UTC
Interesting. Does this also happen with simple notify-send? Also, what distro/package version and what graphics driver do you use? Nvidia proprietary, 346, ubuntu vivid. I have no possibility to test notifysend now (will check later), but kdialog passivepopup doesnt cause this problem. No problems with kdialog --passivepopup and notify-send. Thanks. Can you identify particular notifications with which it does freeze? You've mentioned network manager, any other applications/applets that would freeze plasma? If there are updates available, Muon will show notification - freeze. If I change output audio device, there is a notification about device switch - freeze. If I connect my smartphone using KDE Connect, it will show pairing request as a notification - freeze. Policykit authentication also spawns notification - freeze. Seems like it doesn't matter, which program spawns notification, the problem is in the notification system. Ok so I was hoping this would be just one component which would make it very likely to be that component's fault rather than the notification system. It's not strictly in the notification system as otherwise kdialog and/or notify-send would have the very same problem, which they don't. Can you install and run bustle, start recording a log and then try to trigger just one freeze, stop bustle logging and attach the log here please? Created attachment 92276 [details]
bustle log
Here it is. First 4 entries in a log appeared immediately after I triggered notification (by sending KDEConnect request), the fifth appeared after notification disappeared, plasma unfreezed.
Created attachment 92277 [details]
and in pdf
Ok that doesn't say much. Can you try turning compositing mode off and see if that still freezes? Alt+shift+f12. Reproduces without compositing. Ok, so the last thing to try is to see where exactly is plasma stuck when it's stuck. So make it freeze and attach gdb to it. In case you have no experience with gdb, just follow these steps: 0/ open konsole and send the kdeconnect notification that will make it freeze 1/ run "gdb --pid `pidof plasmashell`" in konsole (without those double quotes) 1.5/ if you get some error about permissions and ptrace, repeat with sudo (or run "sudo !!") 2/ wait for gdb to settle 3/ type "bt" <enter> 4/ copy that bt (full) in here You might want to install qt5 debug symbols first (qtbase, qtquick and qtdeclarative) and also plasma-framework aaand knotifications-framework if you don't have already. Please forgive me, I have deleted my Kubuntu partition by accident, and when I reinstalled it I didn't manage to reproduce this bug O_o Sorry to hear. If you're able to reproduce again, please follow the instructions in comment #11 and reopen this bug. Thanks |