Where is the notification popup timeout stored?
I have several cron jobs that have been running for years with notify-send --expire-time=0. The popups remain active until explicitly acknowledged, but in TDE the popups timeout at about 6 to 7 seconds and close.
Does TDE ignore notify-send timeout parameters?
Is there a preferred way to create persistent notifications in TDE?
Thanks again.
On Tuesday 28 February 2023 06:28:57 pm Darrell Anderson via tde-users wrote:
Where is the notification popup timeout stored?
I have several cron jobs that have been running for years with notify-send --expire-time=0. The popups remain active until explicitly acknowledged, but in TDE the popups timeout at about 6 to 7 seconds and close.
Does TDE ignore notify-send timeout parameters?
Is there a preferred way to create persistent notifications in TDE?
I'm not sure TDE has a notify-send? Or at least mine is installed form Debian...
michael@local [~]# which notify-send /usr/bin/notify-send michael@local [~]# ll /opt/trinity/bin/not* ls: cannot access '/opt/trinity/bin/not*': No such file or directory michael@local [~]# aptitude show notify-send E: Unable to locate package notify-send michael@local [~]# dpkg -S /usr/bin/notify-send libnotify-bin: /usr/bin/notify-send michael@local [~]# aptitude show libnotify-bin Package: libnotify-bin Version: 0.7.7-4 State: installed Automatically installed: yes Priority: optional Section: utils Maintainer: Debian GNOME Maintainers pkg-gnome-maintainers@lists.alioth.debian.org Architecture: amd64 Uncompressed Size: 46.1 k Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.26), libnotify4 (>= 0.7.3) Conflicts: libnotify-bin:i386 Description: sends desktop notifications to a notification daemon (Utilities) A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way.
This package contains the binary which sends the notification. Tags: interface::commandline, role::program, scope::utility
On 2/28/23 6:49 PM, Michael via tde-users wrote:
On Tuesday 28 February 2023 06:28:57 pm Darrell Anderson via tde-users wrote:
Where is the notification popup timeout stored?
I have several cron jobs that have been running for years with notify-send --expire-time=0. The popups remain active until explicitly acknowledged, but in TDE the popups timeout at about 6 to 7 seconds and close.
Does TDE ignore notify-send timeout parameters?
Is there a preferred way to create persistent notifications in TDE?
I'm not sure TDE has a notify-send? Or at least mine is installed form Debian...
The point is TDE is closing the popup despite the --expire-time=0 parameter. I never had this happen in other DEs. Is there a way to get TDE to honor expire-time=0 and not close the popup?
Bug?
On Tuesday 28 February 2023 07:07:45 pm Darrell Anderson via tde-users wrote:
On 2/28/23 6:49 PM, Michael via tde-users wrote:
On Tuesday 28 February 2023 06:28:57 pm Darrell Anderson via tde-users
wrote:
Where is the notification popup timeout stored?
I have several cron jobs that have been running for years with notify-send --expire-time=0. The popups remain active until explicitly acknowledged, but in TDE the popups timeout at about 6 to 7 seconds and close.
Does TDE ignore notify-send timeout parameters?
Is there a preferred way to create persistent notifications in TDE?
I'm not sure TDE has a notify-send? Or at least mine is installed form Debian...
The point is TDE is closing the popup despite the --expire-time=0 parameter. I never had this happen in other DEs. Is there a way to get TDE to honor expire-time=0 and not close the popup?
Bug?
Don't know ;0 Please copy/paste the command you're using and I'll run it here to see if it's doing the same thing.
Best, Michael
On 2/28/23 7:25 PM, Michael via tde-users wrote:
Don't know ;0 Please copy/paste the command you're using and I'll run it here to see if it's doing the same thing.
notify-send --expire-time=0 "Test" "This is a test"
Looks like the source of the problem is the dbus-notification package.
Without the notification-daemon-tde running the notify-send command hangs.
Trying different expire-time timeouts makes no difference here. The popup always closes at about 6 to 7 seconds.
On Tuesday 28 February 2023 08:04:06 pm Darrell Anderson via tde-users wrote:
On 2/28/23 7:25 PM, Michael via tde-users wrote:
Don't know ;0 Please copy/paste the command you're using and I'll run it here to see if it's doing the same thing.
notify-send --expire-time=0 "Test" "This is a test"
Looks like the source of the problem is the dbus-notification package.
Without the notification-daemon-tde running the notify-send command hangs.
Trying different expire-time timeouts makes no difference here. The popup always closes at about 6 to 7 seconds.
Hmmm, working here. e.g. It's been open for the last couple minutes. From a Konsole shell and different durations work as well. Guessing the bug is specific to what distribution you're running?
Here's mine for reference.
PRETTY_NAME="Debian GNU/Linux 10 (buster)" Kernel: 4.19.0-22-amd64 x86_64 bits: 64 Desktop: Trinity R14.0.13 Distro: MX-19.4_x64 patito feo May 31 2020
Or, what shell are you using? From man:
-t, --expire-time=TIME The duration, in milliseconds, for the notification to appear on screen. (Ubuntu's Notify OSD and GNOME Shell both ignore this parameter.)
Since you said it's running from cron, maybe try adding this to the line above the command?
SHELL="/bin/bash"
Well, that's what gets auto-added to my CentOS servers, might work?
# # #
That's it for my knowledge, if the above doesn't help, then do open a bug report (as it should be working).
Best, Michael
On 2/28/23 8:42 PM, Michael via tde-users wrote:
Hmmm, working here. e.g. It's been open for the last couple minutes. From a Konsole shell and different durations work as well. Guessing the bug is specific to what distribution you're running?
Do you have any other desktop environments installed?
On Tue February 28 2023 18:04:06 Darrell Anderson via tde-users wrote:
notify-send --expire-time=0 "Test" "This is a test"
I tried this with --expire-time=0 and also with --expire-time=100000 and with other values. dbus-monitor shows the integer in the message but the time on screen always seems to be around six seconds.
TDE version: R14.0.13 Distribution: Debian GNU/Linux 11.6 (bullseye) Hardware: amd64
I don't know whether TDE is intended to ignore the timeout as Gnome does or whether this is a bug.
--Mike
On 3/1/23 12:44 AM, Mike Bird via tde-users wrote:
On Tue February 28 2023 18:04:06 Darrell Anderson via tde-users wrote:
notify-send --expire-time=0 "Test" "This is a test"
I tried this with --expire-time=0 and also with --expire-time=100000 and with other values. dbus-monitor shows the integer in the message but the time on screen always seems to be around six seconds.
TDE version: R14.0.13 Distribution: Debian GNU/Linux 11.6 (bullseye) Hardware: amd64I don't know whether TDE is intended to ignore the timeout as Gnome does or whether this is a bug.
Thank you for testing. I am not a coder but I walked through the kdbusnotification cpp file and looks like this daemon contacts the TDE notify client. My guess is the notify client is timing out at 6-7 seconds.
I do not know if kdbusnotification is passing the expire-time information on to knotify client.
On 2023/03/01 04:02 PM, Darrell Anderson via tde-users wrote:
On 3/1/23 12:44 AM, Mike Bird via tde-users wrote:
On Tue February 28 2023 18:04:06 Darrell Anderson via tde-users wrote:
notify-send --expire-time=0 "Test" "This is a test"
I tried this with --expire-time=0 and also with --expire-time=100000 and with other values. dbus-monitor shows the integer in the message but the time on screen always seems to be around six seconds.
TDE version: R14.0.13 Distribution: Debian GNU/Linux 11.6 (bullseye) Hardware: amd64
I don't know whether TDE is intended to ignore the timeout as Gnome does or whether this is a bug.
Thank you for testing. I am not a coder but I walked through the kdbusnotification cpp file and looks like this daemon contacts the TDE notify client. My guess is the notify client is timing out at 6-7 seconds.
I do not know if kdbusnotification is passing the expire-time information on to knotify client.
This sounds like a bug that we should look at. notify-send is not part of TDE, but even a notification sent directly using d-feet displays the same behavior.
Darrell, can you file a bug report for this? If it is an easy fix, I will make it for R14.1.0, but I will need to investigate first.
Cheers Michele
On 3/1/23 8:29 AM, Michele Calgaro via tde-users wrote:
This sounds like a bug that we should look at. notify-send is not part of TDE, but even a notification sent directly using d-feet displays the same behavior.
Darrell, can you file a bug report for this? If it is an easy fix, I will make it for R14.1.0, but I will need to investigate first.
Bug report 193 filed:
https://mirror.git.trinitydesktop.org/gitea/TDE/tdelibs/issues/193
The reason I asked if other DEs are installed is dbus does not seem designed to be particular about which notification daemon to launch. Even if kdbusnotification is not installed, another DE notification daemon will suffice as far as dbus is concerned.
I get persistent popups when launched through one of the other DE notification daemons and kdbusnotification removed.
Right now that is my work-around.
-
Darrell Anderson -
Michael -
Michele Calgaro -
Mike Bird