Version: (using KDE 4.3.1) Installed from: Gentoo Packages Hello, I had configure "run command" for notification, and after I have remove it, but it continu to execute this command on the event after reboot of the soft (particuliarly with kopete). Please fix it.
Here using: Qt: 4.5.2 (KDE-Qt git commit 0bd84180cd0a6ae5c5eb18c0d3ed74228434608d Date: Mon Aug 24 13:56:57 2009 +0200) KDE: 4.3.68 (KDE 4.3.68 (KDE 4.4 >= 20090907)) kdelibs svn rev. 1022896 / kdebase svn rev. 1022896 on ArchLinux i686 - Kernel 2.6.30.5 I can't reproduce the bug. Unchecking the "Run command" checkbox from the Notification KCM in SystemSettings will stop running the entered command when getting that selected notification. - Does it happens with any type of notifications ? Have you tried with a lot of them ? Which kind command did you setted up previously ? Thanks
Marking as NEEDSINFO
I have set run: kwrite /home/user/file.txt when kopete is offline. It work. After I have remove it from notification of kopete, but it continue to execute it. I have need restart KDE session for it stop to execute the command. Same bug on all my computer in KDE 4.3.2
I'm seeing the same problem on my machine (KDE 4.3.2/Qt 4.5.2). Changing a notification option in either the KCM or the application is not always obeyed immediately - sometimes it is (rarely), but most of the time it requires a session restart for the changes to take full effect. Restarting knotify4, in my experience, also has no effect. This definitely occurs in Kopete and we're getting many (confirmed) reports of it in KMess as well. I've tried with all of the various notification plugin types (popup, sound, etc etc) and they all produce the same result (require a session restart to take effect). It's almost as if the application's .notifyrc config file isn't being properly reloaded when it changes and so knotify4 keeps using the original configuration. Let me know if I can give you any more info. I don't run KDE trunk so I can't test there unfortunately.
I confirm this problem on KDE 4.3.2
I can also confirm this bug with KDE 4.3.2
Sorry for the double post. I forgot to tell that I can also confirm this bug on KDE 4.3.73
I can confirm this bug on KDE 4.3.3) with KMess Version 2.0. Need to log out and then in again before changes are applied. I can see the changes are showing in both KMess settings and in System Settings-Notification, but it will still make notification sounds even though they are turned off What info is needed? This still has NEEDSINFO and seems abandoned. How to reproduce: Install KDE 4.3.3 and KMess Version 2.0 (Mine is installed from Arch repo, (not kdemod)). Launch KMess, login, start a conversation, get annoyed by the constant notification sounds, turn them off in system settings or KMess options, get even more annoyed by the notification sounds, as the changes have no effect whatsoever unless you log out and in again. If this still really NEEDSINFO, then please tell why, and what information is missing.
I'm reopening it until I get some time to double check, thanks for the info
i want to confirm it too. it would be a great thing to work on this bug since it really affects the instant messaging experience (i'm talking about kmess but i read it bugs kopete too).
This annoying bug presents in kde 4.4, opensuse 11.2, kmess 2.0.2 :(
Is this problem still happening?
Options reseted, I can't try because it block my work station. I thinks it's sloved.
It's ok for me. OpenSUSE 11.4, kde 4.6.2, kmess 2.0.6.1