This forum has been archived. All content is frozen. Please use KDE Discuss instead.

how to stop KDE from calling KTTSD ?

Tags: None
(comma "," separated)
lechat
Registered Member
Posts
7
Karma
0
OS

how to stop KDE from calling KTTSD ?

Mon May 09, 2011 10:32 pm
Hello, KDE keeps launching an error box from time to time about KTTSD, especially when the update notifier notifies me, and I don't know how to tell KDE that I definitely don't want to run this service at all.

I uninstalled KTTSD purposely, which is why KDE complains.

Can anybody help me on this ? Does anybody have any other ideas to prevent similar non essential features from eating resources ?

[idea=]What would be the keyword to look for in the configuration files ?[/idea]
User avatar
google01103
Manager
Posts
6668
Karma
25
do you have jovie installed? jovie appears to have replaced kttsd, so if installed you should remove it.

could you provide the actual error/warning message


OpenSuse Leap 42.1 x64, Plasma 5.x

pinotree
KDE Developer
Posts
222
Karma
7
OS
Right click on the clock widget -> Clock configuration -> General -> Speak time -> set to "Never" (using the bottom arrow in the selector).


Pino Toscano
lechat
Registered Member
Posts
7
Karma
0
OS
@ pinotree : thank you but it's not related to the clock. I already disabled this. It comes up when the update notifier notifies of updates.

@ google01103 :

jovie is not available on my system. KTTSD is, and I uninstalled it.

Title :
Impossible de trouver le service
(means it cannot find the service)

Message :
Échec du lancement de KTTSD
(means it failed to launch KTTSD, which is normal since I uninstalled it.)

Maybe there is a way to prevent the update notifier from calling KTTSD, and that would be interesting. There should be a way to tell KDE to never try calling it (I hope), and that would be the nicest.
User avatar
google01103
Manager
Posts
6668
Karma
25
if it's an update notifier that's causing the problem then it's not part of KDE SC, what update notifier is being used? synaptic? kpackagekit? other?

is there a setting in the package manager that speaks announcements of updates?


OpenSuse Leap 42.1 x64, Plasma 5.x

lechat
Registered Member
Posts
7
Karma
0
OS
In the KDE system configuration, I look at the service manager, and here is my update notifier. It uses the new KDE notification tray icon.

Such update notifications appear standalone, thanks to this service, as far as I know. The notification is also triggered when Synaptic reloads the package information and updates are available.

Whether Synaptic is running or not does not make any difference.
User avatar
google01103
Manager
Posts
6668
Karma
25
from what I can gather update-manager is a separate package from synaptic http://packages.debian.org/search?keywo ... te-manager


OpenSuse Leap 42.1 x64, Plasma 5.x

lechat
Registered Member
Posts
7
Karma
0
OS
Hmmmm, update-manager is not running.

    The notifier tells it speaks in the name of Update notification daemon.
    The error dialog is /usr/bin/knotify4
    The parent of this process is init

This does not tell me who sent the notification. Is there a way to intercept messages sent to knotify and catch the sender ? Do they travel trough DBUS ?
User avatar
google01103
Manager
Posts
6668
Karma
25
no idea, as those kinda questions are well above my pay grade

if you remove update-manager does the problem go away?


OpenSuse Leap 42.1 x64, Plasma 5.x

lechat
Registered Member
Posts
7
Karma
0
OS
Too complicated for me also. Good answers are simple. I found this in .kde/share/config/kde.notifyrc (and not in the GUI) :

Code: Select all
[Event/messageWarning]
Action=Sound|Execute|Taskbar|KTTS
Execute=olnotify infobeep
KTTS=%e
Logfile=


so I changed these 2 lines to :
Code: Select all
Action=Sound|Execute|Taskbar
KTTS=


Now I restart KDE ... and it's OK ! The only problem was that I could not see this in the GUI notification settings, although I reviewed everything several times.

Thank you for your support, I was a lot easier thanks to our questions/answers.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Note that this could also have been done through System Settings > Application and System Notifications > Manage Notifications. Select the correct event source and ensure "Speak" is disabled.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
lechat
Registered Member
Posts
7
Karma
0
OS
Arghhhh, I spoke too fast : now I'm certain that any accessible/visible setting is not configured with KTTS anywhere (either in the system configuration or directly in the config files), nevertheless the notifier keeps trying to call it.

I begin thinking it's hard coded ... yark !
User avatar
google01103
Manager
Posts
6668
Karma
25
Is the updater the only app that is causing this? What updater app are you using? And it's the updater's tray app that's the cause? If so this probably wouldn't be in ~/.kde (as it'not a KDE SC app) possibly in ~/.config or ~/ (as hidden folder/file). So you'd need to find the updater and the notifier rc files (if separate folder/files) and edit them.


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Please run the following:
Code: Select all
cat $(kde4-config --localprefix)/share/config/*.notifyrc | grep -i KTTS


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
lechat
Registered Member
Posts
7
Karma
0
OS
Very good idea ! I did :

Code: Select all
cd $(kde4-config --localprefix)/share/config)
fgrep -i "KTTS" *

and I found a lot of notify configurations that cannot be seen in the GUI (and that I did not find before with the GUI searching tool), including kingston_update_notifier.notifyrc, so I did :

Code: Select all
for file in $(fgrep -i -l "KTTS" *) ; do sed -i -r -e 's/\|KTTS//g' "$file" ; done

and also
Code: Select all
for file in $(fgrep -i -l "KTTS" *) ; do sed -i -r -e 's/Action=KTTS/Action=/g' "$file"  ; done

to automate the removing of the KTTS action in all notification config files, and now it should be OK. I'll be back if it's not.

Thank you ^-^

Note for other readers : beware of the context before blindly running those commands on your system. It's a quick and dirty job, there certainly is a safe and clean way of doing the same, but I'm not an expert. Backup first.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot]