Version: Unbekannt (using KDE 3.4.0 Level "a" , SUSE 9.2 UNSUPPORTED)
Compiler: gcc version 3.3.4 (pre 3.3.5 20040809)
OS: Linux (i686) release 2.6.8-24.11-smp
It's there for a long time now and did not "vanish" with the updates: When I log into my KDE session, I have no system notifications. Only after executing the command "kdeinit knotify", I get the sound. What can I do to have it right from the start?
I created a patch to fix it.
Because when arts crashed it changed knotifyrc value.
But we can't restore value after.
So I reactivate it into kdebase/kcontrol/arts/
see my patch.
Created attachment 9862 [details]
Fix for arts knotifyrc config
> But we can't restore value after.
Mhm? kcontrol/knotify/knotify.cpp PlayerSettingsDialog::save()
Ok in kde3.3.2 I didn't see it.
But I think that it will be a very good idea to reactivate it
when we select arts sound.
Because it's not easy to find it.
SuSE 9.2 KDE 3.4rc1 rpms
gcc version 3.3.4 (pre 3.3.5 20040809)
Linux (i686) 2.6.8-24.11-default
Same problem here. System notifications won't play until 'kdeinit knotify'. I think it has something to do with the aRts packages Suse provides (for some reason they also prevent k3b from compiling).
Use external player=false
kdeinit: Shutting down running client.
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/user/.DCOPserver_AthlonXP1800__0
and start dcopserver again.
KDE Daemon (kded) already running.
Reusing existing ksycoca
kbuildsycoca: WARNING: Property 'X-KDE-Weight' is defined multiple times (KOfficeFilter)
Well, I've compiled arts from source and what shall I say - now it works. So my problem is definitely a SuSE package problem...
*** Bug 100499 has been marked as a duplicate of this bug. ***
This problem is still present in KDE 3.4.1 - basically, once you've turned off arts, turning it on again won't re-enable knotify, since in knotifyrc "Arts Init" and "Use Arts" remain false. The patch previously posted by Laurent Montel works well to allow use of knotify (with arts) when arts is re-enabled.
The patch doesn't seem to have been applied to SVN, though, and I was wondering if there were any reasons why this was the case. The patch does seem to work well enough, though I realize it's not a complete solution - for instance, if arts crashed, and then the user logged out and then in, knotify would still be broken until the user manually stopped/started arts. But nevertheless, it's a help for users, who should not have to edit a config file to get knotify working.
This problem is still present in KDE 3.5.5.
Manually editing knotifyrc:
fixes the sound notify problem for kmail. If there is a patch, multiple reports and it's not committed, should we stop reporting these problems then?
Please, less eyecandy, more bug fixes.
KDE4 will use Phonon instead of artsd