Summary: | notifications don't expire, have to be dismissed manually | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Christian Schubert <mail> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | bengan, finex, hein, jpalecek, plasma-bugs, sven.burmeister |
Priority: | NOR | ||
Version: | 1.2-alpha3 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | screenshot with lots of stacked non-expiring notification popups |
Description
Christian Schubert
2009-06-30 12:54:40 UTC
Created attachment 34936 [details]
screenshot with lots of stacked non-expiring notification popups
Shouldn't this be a bug of Plasma? Anyway on KDE 4.3 notification system has been improved. Probably this shouldn't happen anymore. How would a user tell, whether konversation or plasma was responsible (without digging down in the source)? For me this only seems to happen with konversation, so this is for what I filed the bug. If you seem convinced, that this is not konversation's fault then, of course, you're free to make this a plasma bug. Will retest as soon as kde 4.3 hits debian unstable. I also have the same problem. But it seems to be a problem only when there is lots of notifications. Typical seems to be when I have more than ruffly 100. konversation 1.2.0 kde 4.3.1 opensuse 11.2 I can't reproduce this, notifications expire just fine for me. In any case, Konversation makes no attempts to have the desktop shell show them persistently _or_ to set a timeout, so the behavior is up to the shell regardless. |