Is there a way to disable the animation for system/application notifications?

I have a program that spams up to 100 notifications at once when I first log in, causing my system to freeze with one core pegged at 100% (because of the animation) until I reboot.

I can disable notifications (System Tray Settings > Notifications), but that's not an acceptable solution. I simply want the message banner to pop out and disappear without the gliding animation (which is causing the freeze-up).

BTW, the process that hangs is /usr/bin/plasma-desktop.
Also, Linux Mint 17, KDE 4.13.3.

Thanks.

run "kcmshell4 kwincompositing"
in the second tab disable the "Slide" (not! "slide back") animation - but
a) the window will be caught by the "normal" animations next
b) that won't help you for something that spams 100 windows anyway
You may try to disable the compositor altogether to lower VRAM demand, but the proper fix it to stop the client from spamming messages (or a more efficient notification system that can deal with such amount of messages)

Thanks.

I'll try that out this evening.

Turns our I already had that effect disabled. Ran the command as root user and disabled it under that account as well, but the slide animation still persists.

Thanks for the suggestion, though.

The window might perform an "internal" slide (ie. not relying on the WM feature but just really move the window around - likely required for uncomposited case anyway) - in that case the window effect (if compositing is enabled) would rather be a relief.

Altering this for another user (inc. root) has no effect.

If by "100" notifications you *mean* "100" notifications, this is however probably pointless.

Just run

Code: Select all

while ((i=0;i<100;++i)); do xterm & done

and see your system stall.

You really want to have the client message less/differently.

I think you could propably write a simple Python script that could capture all libnotify events and filter them out.

luebking wrote:You really want to have the client message less/differently.

Tell me how, please

It's Kopete. Every time I boot up from sleep, while it's waiting for my WiFi to connect, it spams the hell out of me with "waiting|failed to connect." One CPU core gets pegged at 100% and everything just freezes. The only work-around I've found is to disable Notifications in the System Tray Settings menu.

Same thing happens when joining a chat room. With notifications disabled, all Kopete does is cause a dozen small windows to stack one on top of the other, but without freezing mdm.

The guides I've found online for Kopete are pretty outdated, with links to 404 pages.

Is there a way to make Kopete be less noisy with non-chatroom notifications?

---

Actually, after typing my post, I checked Kopete's own notifications menu and disabled all non-chatroom messages. Fingers crossed that does the trick.

dkeska wrote:I think you could propably write a simple Python script that could capture all libnotify events and filter them out.

Thanks for the suggestion. I wish I were good enough with Python to do that, but I've yet to learn that language, so would likely just make things worse.

jacqu wrote:Tell me how, please

Code: Select all

kcmshell4 notify

Select kopete and deaactivate notifications for each and every sh** (I don't irc, but geeez... that must be a *very* spammy client)

You can log the *really* important stuff to a file and have the less important things make a "pinggg" and use notifications where it *really* makes sense.

m(

jacqu wrote:Actually, after typing my post, I checked Kopete's own notifications menu and disabled all non-chatroom messages. Fingers crossed that does the trick.

Ah, yes - that will probably do it.

It btw. severely doubt that you could intercept and redirect notifications (let alone via a python script...) the protocol is bilateral between the client and the notification server. You'd have to manipulate the dbus stack (ie. the dbus server) to intercept there "somehow".