** Changed in: network-manager-applet
Importance: Unknown => Medium
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Branch linked: lp:ubuntu/network-manager-applet
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: hundredpapercuts
Status: Triaged => Fix Released
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
This bug was fixed in the package network-manager-applet - 0.8-0ubuntu3
---
network-manager-applet (0.8-0ubuntu3) lucid; urgency=low
[ Mirco Müller (MacSlow) ]
* Make nm-applet correctly update a notification, if the connection-status
has changed. This avoids displaying obsol
** Branch linked: lp:~network-manager/network-manager-applet/ubuntu.head
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Branch linked: lp:~chrisccoulson/network-manager-applet/lp460144
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Branch linked: lp:ubuntu/notify-osd
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
This bug was fixed in the package notify-osd - 0.9.27-0ubuntu1
---
notify-osd (0.9.27-0ubuntu1) lucid; urgency=low
* New upstream version:
- Small maintainance release to fix LP: #525546, so appending works
correctly. This release is also a prerequisite for fixing nm-apple
almost done... here are the fixes (nm-applet, notify-osd) at work ->
http://macslow.net/clips/nm-applet-correctly-updates.ogv
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bu
Adding papercut task and assign Tony from duplicate
** Changed in: hundredpapercuts
Importance: Undecided => Medium
** Changed in: hundredpapercuts
Status: New => Triaged
** Changed in: hundredpapercuts
Milestone: None => lucid-round-8
** Changed in: hundredpapercuts
Assignee
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Here is a stand-alone example in ANSI C of how to correctly
update/replace the content of a notification/bubble. The simulated use-
case is that of NetworkManager disconnecting and reconnecting after a
resume from suspend. Be sure to check the top of the source-file about
how to compile and run it.
@rfugger :
Merging is text a + text b .
But here we cant do that.
The text a needs to be _replaced_ with text b ...
--
nm applet doesn't close notification when it is obsolete
https://bugs.launchpad.net/bugs/460144
You received this bug notification because you are a member of Ubuntu
Bugs, w
As detailed in bug #460964, network manager can merge asynchronous
notifications when a new one should supercede an old one by giving them
the same title. This is in keeping with then notify-osd guidelines:
https://wiki.ubuntu.com/NotifyOSD#Merging%20notifications
Assuming notify-osd is implemen
** Changed in: notify-osd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: notify-osd (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager-applet (Ubuntu)
Status: Confirmed => Triaged
** Changed in: network-manager-applet (Ubuntu)
Importance: Undecided =>
I'v earlier asked Mirco regarding this issue , and if network manager can send
the notifications as sync notifications.
He mentioned that the network-manager is _not_ supposed to send sync
notifications as they are specifically reserved for direct "hardware-feedback"
type of notifications.
And
This is a problem because , network manager use asynchronous
notifications, which are under notify-osd's queue control, hence the
difference in notification reception and notification display.
Whereas the volume/brightness/eject notifications are synchronous (or
feedback) notifications... they get
17 matches
Mail list logo
