Bug 162317

Summary:	Changes to config files are not recognized
Product:	[Unmaintained] kdelibs	Reporter:	Dennis Nienhüser <nienhueser>
Component:	knotify	Assignee:	Olivier Goffart <ogoffart>
Status:	RESOLVED FIXED
Severity:	normal	CC:	amantia, andresbajotierra, renda.krell, torquil
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dennis Nienhüser 2008-05-19 17:27:32 UTC

Version:            (using KDE 4.0.4)
Installed from:    Ubuntu Packages
OS:                Linux

Changes to config files are not recognized by the knotify4 daemon, therefore changing a notification setting only takes effect after restarting knotify4. A quick way to reproduce this is to open konsole, configure the visible bell notification, trigger it, change the notification configuration and trigger the event again. The configuration changes won't be applied unless knotify4 is restarted.

This happens for both KDE 4.0.4 and SVN trunk and is likely due to commit 798565 and 798568. See bug 156346.

Comment 1 Olivier Goffart 2008-06-02 21:53:18 UTC

*** Bug 162976 has been marked as a duplicate of this bug. ***

Comment 2 Olivier Goffart 2008-06-03 08:13:45 UTC

SVN commit 816038 by ogoffart:

Clear the config cache on the reconfigure dbus method
CCBUG: 162317



 M  +1 -0      knotify.cpp  
 M  +9 -1      knotifyconfig.cpp  
 M  +2 -0      knotifyconfig.h  
 M  +1 -1      main.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=816038

Comment 3 Dennis Nienhüser 2008-06-05 15:46:13 UTC

*** Bug 163190 has been marked as a duplicate of this bug. ***

Comment 4 Dennis Nienhüser 2008-06-10 00:27:44 UTC

*** Bug 163348 has been marked as a duplicate of this bug. ***

Comment 5 Olivier Goffart 2008-06-13 18:46:22 UTC

SVN commit 820250 by ogoffart:

Ask the knotify deamon to reload the config when we change it.

CCBUG: 162317



 M  +9 -0      knotifyconfigwidget.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=820250

Comment 6 Dario Andres 2008-12-26 19:23:25 UTC

Can anyone still reproduce this bug with a recent KDE version? (4.1.3 / 4.2beta2 / 4.2svn) even after the last commit in comment 5?  Thanks :)

Comment 7 Dennis Nienhüser 2008-12-27 16:03:43 UTC

No, it works now (tested with 4.2svn).