I'm looking for ideas or a check list how TDM might block or ignore desktop notifications. Notifications appear as expected when using a different DM.
I am not using the kdbusnotification package. R14.1.2.
Thanks.
Darrell Anderson via tde-users wrote:
I'm looking for ideas or a check list how TDM might block or ignore desktop notifications. Notifications appear as expected when using a different DM.
There is knotify as part of tdelibs. I saw recently an option to enable/disable the notifications but I do not recall where exactly I saw it. It was not a trivial place. May be you can check k/dcop interface.
Check if you have knotify running.
TDE uses dcop incl. the notifications so it is not really comparable with other DE as they use dbus.
I am not using the kdbusnotification package. R14.1.2.
If you want to see notifications from non TDE applications you need kdbusnotification package (I am using my version which utilizes dbus-1-tqt)
https://mirror.git.trinitydesktop.org/gitea/TDE/kdbusnotification.git
branch feat/with_dbus-1-tqt
It is working fine with all kind of modern apps (Signal, Skype etc.) however you need the notification daemon and knotify running
$ ps faxuww | grep notif ... S Jan04 0:01 notification-daemon-tde ... S Jan04 0:00 knotify [tdeinit]
On 1/5/25 12:32 PM, deloptes via tde-users wrote:
There is knotify as part of tdelibs. I saw recently an option to enable/disable the notifications but I do not recall where exactly I saw it. It was not a trivial place. May be you can check k/dcop interface.
Check if you have knotify running.
I have been doing that all afternoon across several different systems. Some user accounts launch knotify and some do not. I have been unable to find anything unique to cause the differences. I even diffed the $TDEHOME directories.
I get the vague feeling the problem is related to whatever knotify depends for backend packages, if any.
If you want to see notifications from non TDE applications you need kdbusnotification package (I am using my version which utilizes dbus-1-tqt)
I have had issues with the kdbusnotification package. We had a discussion here many months ago. The notable issue for me is the daemon ignores the notify-send expire-time parameter and seems fixed at 6 seconds or so. I use the expire-time parameter.
On 1/5/25 5:53 PM, Darrell Anderson via tde-users wrote:
On 1/5/25 12:32 PM, deloptes via tde-users wrote:
There is knotify as part of tdelibs. I saw recently an option to enable/disable the notifications but I do not recall where exactly I saw it. It was not a trivial place. May be you can check k/dcop interface.
Check if you have knotify running.
I have been doing that all afternoon across several different systems. Some user accounts launch knotify and some do not. I have been unable to find anything unique to cause the differences. I even diffed the $TDEHOME directories.
I get the vague feeling the problem is related to whatever knotify depends for backend packages, if any.
If you want to see notifications from non TDE applications you need kdbusnotification package (I am using my version which utilizes dbus-1-tqt)
I have had issues with the kdbusnotification package. We had a discussion here many months ago. The notable issue for me is the daemon ignores the notify-send expire-time parameter and seems fixed at 6 seconds or so. I use the expire-time parameter.
Looks like this specific TDM issue might be a red herring. I have been tweaking rc files and now popups are showing. I don't know which specific rc file changes made the difference. One way or another, seems the core problem is whether knotify loads automatically. I don't know the root cause why knotify was not loading on some systems yet loading on others.
On 1/5/25 12:32 PM, deloptes via tde-users wrote:
There is knotify as part of tdelibs. I saw recently an option to enable/disable the notifications but I do not recall where exactly I saw it. It was not a trivial place. May be you can check k/dcop interface.
Please share anything related. Other than ensuring knotify is compiled, I have yet to find any useful information.
Darrell Anderson via tde-users wrote:
Please share anything related. Other than ensuring knotify is compiled, I have yet to find any useful information.
it is not about if it is compiled, but if it is running.
I found it in kcontrol - sorry but too lazy to start a VM with english locale - I hope you can identify it by the icon. It says something like feedback on the left side in the menu.
On 1/6/25 11:39 AM, deloptes via tde-users wrote:
Please share anything related. Other than ensuring knotify is compiled, I have yet to find any useful information.
it is not about if it is compiled, but if it is running.
I found it in kcontrol - sorry but too lazy to start a VM with english locale - I hope you can identify it by the icon. It says something like feedback on the left side in the menu.
I know knotify is compiled because there are related lib files. Also knotify sometimes loads, but I haven't found why knotify does not load consistently on all systems. I need to resolve that issue before I can look into the size of the popups.
I don't see anything related in kcontrol other than sounds, which is internal to TDE. My focus is creating notification popups externally with notify-send. My guess is notify-send requires a dbus dependent notification daemon. Because the kdbusnotifcation package is buggy I am using the xfce4 notification daemon.
The only kcontrol items I see about feedback are related to launching tools or the mouse cursor.
Darrell Anderson via tde-users wrote:
I know knotify is compiled because there are related lib files. Also knotify sometimes loads, but I haven't found why knotify does not load consistently on all systems. I need to resolve that issue before I can look into the size of the popups.
I don't see anything related in kcontrol other than sounds, which is internal to TDE. My focus is creating notification popups externally with notify-send. My guess is notify-send requires a dbus dependent notification daemon. Because the kdbusnotifcation package is buggy I am using the xfce4 notification daemon.
Don't remember what was notify-send, but I think it was gnome application and yes it needs dbus and yes you need kdbusnotifcation and yes it was outdated and this is why I added a pull request based on dbus-1-tqt, which works much better. You can compile install and enjoy it.
The only kcontrol items I see about feedback are related to launching tools or the mouse cursor.
Did you see the screenshot - knotify is part of TCC (the kdbusnotifcation is not integrated there)
On 1/6/25 2:58 PM, deloptes via tde-users wrote:
I know knotify is compiled because there are related lib files. Also knotify sometimes loads, but I haven't found why knotify does not load consistently on all systems. I need to resolve that issue before I can look into the size of the popups.
I don't see anything related in kcontrol other than sounds, which is internal to TDE. My focus is creating notification popups externally with notify-send. My guess is notify-send requires a dbus dependent notification daemon. Because the kdbusnotifcation package is buggy I am using the xfce4 notification daemon.
Don't remember what was notify-send, but I think it was gnome application and yes it needs dbus and yes you need kdbusnotifcation and yes it was outdated and this is why I added a pull request based on dbus-1-tqt, which works much better. You can compile install and enjoy it.
The notify-send command is part of the libnotify package. I am reasonably certain recent versions require dbus. Any notification daemon can be used. Multiple daemons can be installed, but there is no specification about which daemon gets called on request. I looked into that oddity not long ago.
The xfce4 notification daemon is fine to interact with notify-send, regardless of the desktop environment.
There are issues with the kdbusnotification package. Notably, in TDE notifications ignore the notify-send 'expire-time' parameter. Related notification durations seem fixed at about 6 seconds. We had a discussion about this about a year and a half ago or so. I think I filed a bug report but I don't remember. Yesterday I again tried using kdbusnotification and saw the same shortfall. I have both of the TDE dbus-tqt packages installed.
The only kcontrol items I see about feedback are related to launching tools or the mouse cursor.
Did you see the screenshot - knotify is part of TCC (the kdbusnotifcation is not integrated there)
Yes, I saw. I don't think those options are related to system system notification popups.
I am tinkering with rebuilding the user TDE profile from scratch. A huge time consuming inconvenience and I still cannot get the TDE knotify process to launch consistently with each login. System notification popups with notify-send seem to be functional though so perhaps that oddity is a should shrug. That does not resolve the size of the system notification popups. In that respect I'm still at square one.
I don't know what knotify is supposed to do. I haven't tried to browse the code to see what the purpose of knotify might be. My original focus hasn't changed though -- the size of the system notification popups are too small.
Darrell Anderson via tde-users wrote:
There are issues with the kdbusnotification package. Notably, in TDE notifications ignore the notify-send 'expire-time' parameter. Related notification durations seem fixed at about 6 seconds. We had a discussion about this about a year and a half ago or so. I think I filed a bug report but I don't remember. Yesterday I again tried using kdbusnotification and saw the same shortfall. I have both of the TDE dbus-tqt packages installed.
you should have only one process listening on the dbus to handle the notification (IMO). It makes things much simpler. Why? 1. Because it registers a unique name, that is used by the calling party 2. Because it also replies to the calling party.
see attached image
Perhaps xfce works because it is started first and thus takes the name first.
Look here - I put some examples how you can test it
https://mirror.git.trinitydesktop.org/gitea/TDE/kdbusnotification/src/branch...
You can pass the expiration time as last argument.
Also note that there are different versions of the interface (more recent version supports more features)
BR
-
Darrell Anderson -
deloptes