This bug was fixed in the package libnotify - 0.7.11-1
---
libnotify (0.7.11-1) unstable; urgency=medium
* New upstream release:
- notify-send: Support for replacing an existing notification (LP: #257135,
Closes: #559544)
- notify-send: Support commas in icon filenames
** Changed in: libnotify (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage
** Changed in: libnotify (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage noti
btw, I created a PR upstream. still waiting for merging though
https://gitlab.gnome.org/GNOME/libnotify/-/merge_requests/17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1)
When could we expect this patch to be deployed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage notifications about this
I ended up using the answer in Ask Ubuntu:
https://askubuntu.com/a/871207/307523
The basic concept is you link your message to the last message you sent
with an extra line:
-h string:x-canonical-private-synchronous:anything
Where 'anything' is the string/text grouping your spamming bubbles
It would be nice to have the patch applied both the standard call from
bash as well as the python libraries (2.7.12 and 3.x).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(
Yes, please deploy the patch if it works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage notifications about this bug go
I would find this incredibly helpful, but would also love to be able to
also dismiss something by ID. That way a "Processing..." notification
could be displayed indefinitely, then removed when the process behind
completed.
As someone seems to have already patched this it would be fantastic to
see
** Changed in: libnotify (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage notificat
** Bug watch added: Debian Bug tracker #559544
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544
** Also affects: libnotify (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Ok, I figured it out, copy the patch text, save as "patch". download
source, https://launchpad.net/ubuntu/+source/libnotify , un-archive the
source, put "patch" in the source folder, patch with `patch -p1 <
patch` in terminal in the folder, then
`./configure`
`make`
`sudo make install`
If that
It would be nice to know how to use the patch, where notify-send.c is to
be placed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notificatio
The attachment "notify-send.c: add --print-id and --replace-id switches"
of this bug report has been identified as being a patch. The ubuntu-
reviewers team has been subscribed to the bug report so that they can
review the patch. In the event that this is in fact not a patch you can
resolve this
Hi Ralph,
Actually, I don't know if that can happen. And even if the ID is 0, we
should print it anyway, because, as I discovered when I was updating my
scripts, we can then safely write
id=0
while ...; do
...
id=$(notify-send -p -r $id ...)
...
done
which is nice and simple.
Attach
Thanks Paul. Why might there not be an id to print?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage notifications about
Here's v2 of the patch, which now terminates the argument list to
g_object_set correctly.
** Patch added: "notify-send.c: add --print-id and --replace-id switches,
version 2"
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+attachment/3157323/+files/print-and-replace-id-v2.pat
Here's a patch to notify-send.c that adds --print-id and --replace-id
switches.
I've tested it lightly here and it seems to do what I expect.
** Patch added: "notify-send.c: add --print-id and --replace-id switches"
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+attachment/
>>Sander
How can you know what that number is?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
--
ubuntu-bugs mailing list
ubuntu
Workaround:
hack something together in
ruby/python/.
As I have done here:
https://github.com/marvinthepa/cake/blob/master/bin/notify
(probably not idiomatic Ruby, I know much more Python and Perl..). Maybe I will
add the missing stuff so that it is fully backward-compatible to notify-send
and c
@ Sebastien Bacher
I want to disclose up front that I really don't know the details of how
bug importance is assigned, or what it really means for this to be "Low"
importance.
That said, it does look like you have looked at bug #390508 (I see that
you responded there), which many people have been
** Changed in: libnotify (Ubuntu)
Importance: Undecided => Low
--
notify-send(1) can't replace an existing notification
https://bugs.launchpad.net/bugs/257135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
It would be really nice to have command line access to this parameter.
There are nearly as many use-cases for this as there are for using notify-send
at all.
.
This would enable easily scripted messages to update status quickly. As it is,
to get messages at the speed of channel surfing, temperat
I consider it a bug that the underlying mechanism returns an ID and
allows for its replacement yet the userspace command doesn't. It's
restricting the usefulness of the mechanism.
--
notify-send(1) can't replace an existing notification
https://bugs.launchpad.net/bugs/257135
You received this bu
This would me wildly useful. Something for the wish list?
** Changed in: libnotify (Ubuntu)
Status: New => Confirmed
--
notify-send(1) can't replace an existing notification
https://bugs.launchpad.net/bugs/257135
You received this bug notification because you are a member of Ubuntu
Bugs,
25 matches
Mail list logo
