[Dx-packages] [Bug 1851154] Re: libindicator ftbfs: G_ADD_PRIVATE
I note this is the same problem indicator-messages had in bug 1843740. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1851154 Title: libindicator ftbfs: G_ADD_PRIVATE Status in libindicator package in Ubuntu: New Bug description: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1851154/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1851154] [NEW] libindicator ftbfs: G_ADD_PRIVATE
Public bug reported: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. ** Affects: libindicator (Ubuntu) Importance: Undecided Status: New ** Attachment added: "build log from makechrootpkg" https://bugs.launchpad.net/bugs/1851154/+attachment/5302542/+files/libindicator-buildlog -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1851154 Title: libindicator ftbfs: G_ADD_PRIVATE Status in libindicator package in Ubuntu: New Bug description: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1851154/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 754065] Re: Minimized windows are invisible but present; minimize COMPLETELY BROKEN
*** This bug is a duplicate of bug 1574136 *** https://bugs.launchpad.net/bugs/1574136 ** This bug is no longer a duplicate of bug 758253 unity-compiz develops focus problems and sends input to minimized windows when 'Keep previews of minimized windows' is enabled ** This bug has been marked a duplicate of bug 1574136 Minimized window not loosing focus -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/754065 Title: Minimized windows are invisible but present; minimize COMPLETELY BROKEN Status in Unity: Confirmed Status in compiz-plugins-main package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Binary package hint: unity Minimize is completely broken in both unity 3.8.2 and 3.8.4 on a fully updated Ubuntu 11.04 using ubuntu-daily, fglrx, amd64. Here are the problems: 1) When you try to minimize windows, they become invisible, but you can still interact with them in whatever way you like, click any button, type anywhere, whatever you like. You can also use the global menu in the panel above, and the panel still claims the app is focused. You cannot interact with windows behind where the "minimized" window was/is, even if you focus them. 2) Clicking on the launcher does not raise "minimized" windows, probably because they aren't really minimized, just invisible. You also don't get them by clicking the launcher to get scale when multiple instances are open. Alt-tab is the only way to get them visible again. 3) After "unminimizing" "minimized" windows, the windows are totally broken. They are always on top no matter which window is focused. Windows behind them can be focused, but they cannot be seen or interacted with because the "unminimized" window is always above them. You can still interact with "unminimized" windows, but they are not seen by alt-tab or scale. They respond incorrectly to resize, mazimize, and shade, but move normally. For a long time I thought there was no way to restore an "unminimized" window to sanity, but it turns out that for whatever reason, if you shade a window and double-click on its titlebar to maximize it, then it will remain invisible for several seconds, at the end of which time it becomes visible. Once it is visible again it becomes once more a normal window. They also appear to become normal again if compiz crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/754065/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1415964] Re: Transparent background in gnome-system-monitor 3.14
*** This bug is a duplicate of bug 1167079 *** https://bugs.launchpad.net/bugs/1167079 ** This bug has been marked a duplicate of bug 1167079 GtkScrolledWindow widgets (GTK3) have black or transparent backgrounds with Ayatana overlay-scrollbar -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1415964 Title: Transparent background in gnome-system-monitor 3.14 Status in overlay-scrollbar: New Status in overlay-scrollbar package in Ubuntu: Fix Released Bug description: gnome-system-monitor 3.14 has a transparent background with overlay scrollbars enabled. Switch to and from the resources tab to see. To manage notifications about this bug go to: https://bugs.launchpad.net/overlay-scrollbar/+bug/1415964/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 420583] Re: Notify-osd looks are not customizable
I don't understand this code really:
indicator-applet-developers/notify-osd/trunk/src/defaults.c
gint
defaults_get_on_screen_timeout (Defaults* self)
{
gint on_screen_timeout;
if (!self || !IS_DEFAULTS (self))
return 0;
g_object_get (self, "on-screen-timeout", _screen_timeout, NULL);
return on_screen_timeout;
}
x time for n characters?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/420583
Title:
Notify-osd looks are not customizable
Status in notify-osd package in Ubuntu:
Confirmed
Bug description:
Binary package hint: notify-osd
At the moment the notify-osd looks are not configurable (not with a
GUI, and as far as I can see not with gconf and/or a configuration
file).
THis should be possible to do: in the first place with gconf (or
configuration file) and in the longer term a GUI (maybe not all
aspects, but at least some of them).
Rationale:
Color settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all
(Mirco has confirmed the problem and seems to work on a solution)
Presentation settings: If notifications should be visible in fullscreen or
not (and what priority should be shown)
(https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962)
Font settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already
being worked on...)
Also things like blur and fade out settings should be configurable
Timeout settings: the time notifications stay should also be
configurable: some people read faster than others, so the very-
sensible default (of x time per n characters) can be good, but some
people maybe like y time per n characters.
Placement settings (which is the real cause of the bug report: center-right
is in my option very bad UI design (maybe it is just an experiment): Probably
it is more noticeable than top-right but it is also more probable that it is in
your way:
While reading (a big text) the part I'm reading is often more or less in the
center, so I can do 2 things when such a notification happens: Scroll down so I
can read the text again, or move my mouse so it appears above the notification
so I can read the text under it...
It thought notify-osd was about "passive" notifications that didn't take your
attention so you were not obliged to do anything, with the new (non-)sensible
non-configurable default setting I have to react (sometimes) to a
notification...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 420583] Re: Notify-osd looks are not customizable
Just digging around indicator-applet-developers/notify-
osd/trunk/src/display.c
/* if there is already one bubble on display
we don't have room for another one */
if (bubble_is_visible (bubble))
return NULL;
not great, but off topic.
on topic:
if (bubble_is_urgent (bubble))
{
/* pick-up the /first/ urgent bubble
in the queue (FIFO) */
return bubble;
}
We replace this, and excuse my bashism, with something like
bubble_is_"$URGENCY" (and have no specification == urgent for your
default behavior) and let it be set by an environment variable; then the
hook is customizable like any other freedesktop feature.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/420583
Title:
Notify-osd looks are not customizable
Status in notify-osd package in Ubuntu:
Confirmed
Bug description:
Binary package hint: notify-osd
At the moment the notify-osd looks are not configurable (not with a
GUI, and as far as I can see not with gconf and/or a configuration
file).
THis should be possible to do: in the first place with gconf (or
configuration file) and in the longer term a GUI (maybe not all
aspects, but at least some of them).
Rationale:
Color settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all
(Mirco has confirmed the problem and seems to work on a solution)
Presentation settings: If notifications should be visible in fullscreen or
not (and what priority should be shown)
(https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962)
Font settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already
being worked on...)
Also things like blur and fade out settings should be configurable
Timeout settings: the time notifications stay should also be
configurable: some people read faster than others, so the very-
sensible default (of x time per n characters) can be good, but some
people maybe like y time per n characters.
Placement settings (which is the real cause of the bug report: center-right
is in my option very bad UI design (maybe it is just an experiment): Probably
it is more noticeable than top-right but it is also more probable that it is in
your way:
While reading (a big text) the part I'm reading is often more or less in the
center, so I can do 2 things when such a notification happens: Scroll down so I
can read the text again, or move my mouse so it appears above the notification
so I can read the text under it...
It thought notify-osd was about "passive" notifications that didn't take your
attention so you were not obliged to do anything, with the new (non-)sensible
non-configurable default setting I have to react (sometimes) to a
notification...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 420583] Re: Notify-osd looks are not customizable
Use case: Ubuntu derivative/rebranding diversity. Derivatives might have different interest in notifications; ie some kind of kiosk distro could intentionally favor full screen, urgency=normal, as a default behavior while a multimedia desktop may want something like elementary's wingpanel-indicator-notifications-bzr (status notifier notification log) and no bubbles. An adoptable notify-osd would win brownie points for Ayatana Design. A lot of non-Unity derivatives have already opted for their own ad-hoc notification method. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/420583 Title: Notify-osd looks are not customizable Status in notify-osd package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd At the moment the notify-osd looks are not configurable (not with a GUI, and as far as I can see not with gconf and/or a configuration file). THis should be possible to do: in the first place with gconf (or configuration file) and in the longer term a GUI (maybe not all aspects, but at least some of them). Rationale: Color settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all (Mirco has confirmed the problem and seems to work on a solution) Presentation settings: If notifications should be visible in fullscreen or not (and what priority should be shown) (https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962) Font settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already being worked on...) Also things like blur and fade out settings should be configurable Timeout settings: the time notifications stay should also be configurable: some people read faster than others, so the very- sensible default (of x time per n characters) can be good, but some people maybe like y time per n characters. Placement settings (which is the real cause of the bug report: center-right is in my option very bad UI design (maybe it is just an experiment): Probably it is more noticeable than top-right but it is also more probable that it is in your way: While reading (a big text) the part I'm reading is often more or less in the center, so I can do 2 things when such a notification happens: Scroll down so I can read the text again, or move my mouse so it appears above the notification so I can read the text under it... It thought notify-osd was about "passive" notifications that didn't take your attention so you were not obliged to do anything, with the new (non-)sensible non-configurable default setting I have to react (sometimes) to a notification... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
>mpt
Glad to see this bug is still bothering you, because it still bothers
us.
bug 420583's proposal great, and it's been sitting there for seven
years.
Seven years ago there was an idea that could probably have avoided all
this trouble.
Did the x time per n characters algorithm ever really get implemented?
Where is the proposed settings dialog (aside from leolik's fork, which
has one)?
How much progress has been made toward making the hooks customizable?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in Ayatana Design:
New
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 420583] Re: Notify-osd looks are not customizable
>Timeout settings: the time notifications stay should also be configurable: some people read faster than others, so the very-sensible default (of x time per n characters) can be good, but some people maybe like y time per n characters. That would be wonderful. Implement that; put a high priority on it. Make it happen. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/420583 Title: Notify-osd looks are not customizable Status in notify-osd package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd At the moment the notify-osd looks are not configurable (not with a GUI, and as far as I can see not with gconf and/or a configuration file). THis should be possible to do: in the first place with gconf (or configuration file) and in the longer term a GUI (maybe not all aspects, but at least some of them). Rationale: Color settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all (Mirco has confirmed the problem and seems to work on a solution) Presentation settings: If notifications should be visible in fullscreen or not (and what priority should be shown) (https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962) Font settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already being worked on...) Also things like blur and fade out settings should be configurable Timeout settings: the time notifications stay should also be configurable: some people read faster than others, so the very- sensible default (of x time per n characters) can be good, but some people maybe like y time per n characters. Placement settings (which is the real cause of the bug report: center-right is in my option very bad UI design (maybe it is just an experiment): Probably it is more noticeable than top-right but it is also more probable that it is in your way: While reading (a big text) the part I'm reading is often more or less in the center, so I can do 2 things when such a notification happens: Scroll down so I can read the text again, or move my mouse so it appears above the notification so I can read the text under it... It thought notify-osd was about "passive" notifications that didn't take your attention so you were not obliged to do anything, with the new (non-)sensible non-configurable default setting I have to react (sometimes) to a notification... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
However, it's the people *not* represented on launchpad that you're
*even more* wrong about.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in Ayatana Design:
New
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
>>mpt
Just because I don't agree with you doesn't mean I don't understand your
lexicon.
I just think you're wrong. The group disproportionately represented on
launchpad is not who you think it is.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in Ayatana Design:
New
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
** Also affects: ayatana-design
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in Ayatana Design:
New
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
>People who look for, find, and comment in bug reports are
disproportionately those who notice and are annoyed by software's
current behavior. People who don't notice, don't care about, or agree
with, current behavior don't go looking for bug reports about it.
I strongly disagree.
You aren't taking into account people who notice and are annoyed, but
don't know anything about bug reports--or even what to call "the
annoying bubble thingies that won't ever go away".
Before discovering launchpad, or the forums, or making an account,
they'll get frustrated, give up and think this, Ubuntu, and/or Linux are
[insert expletive here]--and use something else.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
defaria I think you may have encountered what I was getting at in #32 GNOME has tied hotkey support into gnome-shell, such that hotkeys no longer work without gnome-shell in any gnome-derivative desktops (like Unity). The GNOME team has provided a utility to restore hotkey support without gnome-shell: gnome-fallback-media-keys-helper At the moment, the only Ubuntu package available is in the Zorion OS PPA: https://launchpad.net/~zorin-os/+archive/ubuntu/packages Rather than add the whole PPA, it's probably a better idea to download the one package and install it with dpkg. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
or has that change not hit Ubuntu yet? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
How does unity work around gnome-settings-daemon dropping support for media keys? Does unity handle these keys itself now? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
** Changed in: ayatana-design Status: Fix Committed = Opinion ** Changed in: ayatana-design Status: Opinion = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: In Progress Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in unity source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) - Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
duncan bayne
The bug isn't in notify-send; this is part of libnotify which properly
implements the timeout specification (you can send the timeout
parameter).
The problem is in notify-osd (Canonical's notification front-end) which
does not properly implement the timeout specification (it will not
receive the timeout parameter) for no justifiable reason as I have
pointed out with quotations from Canonical's notification specs, the
freedesktop specs, and specific real-world use cases.
franglais.125
Welcome to the fold.
Everyone
Let me at this time express my appreciation for pantheon-notify, a
notification front-end from that does everything right. The
notifications do honor the timeout parameter and feature a close button
as well for when you want them to just go away. It does nothing less
than notify-osd can do and everything more.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
Have I mentioned before that I think this is a layering problem? I was reading the old xscreensaver (one of many things unity appears on top of) faq and came a across this: __ Every few minutes, xscreensaver will raise itself above any other windows that have popped up, but it can't prevent other programs from popping up their windows in the first place. So they will appear for a little while, and then be hidden. If this is happening and it bothers you, switching to a different window manager may fix it. You might consider this a bug in your window manager (though some consider it a feature.) If you think it's a bug, then the magic incantation to repeat to the author of your window manager is as follows: you should be mapping windows with XRestackWindows instead of XRaiseWindow, to ensure that managed windows always appear below override-redirect windows. It is also possible that the application that is popping up the window is doing so using an override-redirect window of its own. (This is currently the case with GTK_WINDOW_POPUP style dialogs.) In that case, it is impossible for either xscreensaver or the window manager to prevent those windows from popping up, since override-redirect windows, by definition, bypass the window manager. __ Is Unity drawn using override-redirect? Is it mapped with XRaiseWindow? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Confirmed Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) - Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
there's also the fact that lacking support for the timeout parameter
allows for notifications that do not reliably disappear, ever.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Besides, the documentation contradicting Ubuntu's implementation at
freedesktop.org isn't outdated.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
The people trying to figure out why notifications linger at the top of
the screen for way too long and cause new notifications to come in late
and pile up in a chain that can go on for several minutes are not
reading outdated documentation; they are trying to figure out what is
wrong with this implementation.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon
Townsend First, thank you for doing the right thing. I haven't tried this feature yet, since I'm still not using Unity (or even Ubuntu anymore) and I have a question: does this feature distinguish between focused (to be minimized) and unfocused (to be focused) state? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/733349 Title: Minimize Application's Windows upon clicking its Launcher Icon Status in Ayatana Design: Won't Fix Status in Obsolete project please ignore: Invalid Status in Unity: Fix Committed Status in Unity Tweak Tool: Won't Fix Status in “unity” package in Ubuntu: Fix Released Bug description: What I do miss in Unity is the possibility to click on the app. icon on the Unity launcher bar to minimize all windows of that application, not only to launch/restore it. mlaverdiere's futher addition: https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2 My suggestion would be to modify the interaction-design/process like this (*=my modification proposal/2 cents!): 1) start it, if it hasn't been started yet; *2) restore it, if it is minimized; *3) focus the app, if it's started, not minimized and has not the focus yet; 4) spread windows (of app), if app is focused and has multiple windows open; *5) minimize it if it is in spread-mode (see 4). Note that this bug has over 300 comments and several working but rejected patches. This means that this feature probably will never land in official Unity! So if you want it, you have to use a patched version of Unity. There is a working patch for 13.04 ( from comment #322, https://bugs.launchpad.net/ayatana- design/+bug/733349/+attachment/3573380/+files/minimize.patch ). Somebody should set up a PPA (and note it here) to make it easy to install the patched version. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/733349/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon
This is the code I asked about:
=== modified file 'launcher/ApplicationLauncherIcon.cpp'
--- launcher/ApplicationLauncherIcon.cpp2014-03-12 23:46:10 +
+++ launcher/ApplicationLauncherIcon.cpp2014-03-17 20:58:25 +
@@ -399,7 +399,16 @@
{
if (arg.source != ActionArg::Source::SWITCHER)
{
-Spread(true, 0, false);
+WindowList windows = GetWindows(WindowFilter::ON_CURRENT_DESKTOP);
+
+if (windows.size() == 1 minimize_window_on_click)
+{
+wm.Minimize(windows[0]-window_id());
+}
+else
+{
+Spread(true, 0, false);
+}
}
}
}
Looks like it checks how many windows are in the group (windows.size()
== 1) and if the setting is enabled (minimize_window_on_click); and the
function is limited to windows on the current desktop
(WindowFilter::ON_CURRENT_DESKTOP); but I don't see anything about
focused/unfocused state.
Most of the time it will be fine as-is, especially for users who don't
clutter a single workspace with lots of windows, but there may be
occasions when a single window on the current desktop may be under
another window or a group of windows and clicking on the icon will
minimize it behind them (Aunt Suzy). Since there's a minimize
animation to see, most users will probably realize what happened and
click the icon one more time to get the desired window out and on top.
Adding an additional if statement to cover this case would be a nice
improvement. Please excuse my ignorance of the proper names of the
functions and variables involved; consider this a blueprint for actual
code:
if (windows.size() == 1 minimize_window_on_click)
{
+if ( windows[0]-window_state() == unfocused )
+{
+wm.Raise(windows[0]-window_id());
+}
+else
+{
wm.Minimize(windows[0]-window_id());
}
I know how hard it was to get this feature in even as-is with no more
tweaks or enhancements, and I'm happy to see it happen at all, so I
won't hold it against anyone if this behavior is never updated; just a
suggestion (and reiteration of the same from several comments in this
report).
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/733349
Title:
Minimize Application's Windows upon clicking its Launcher Icon
Status in Ayatana Design:
Won't Fix
Status in Obsolete project please ignore:
Invalid
Status in Unity:
Fix Committed
Status in Unity Tweak Tool:
Won't Fix
Status in “unity” package in Ubuntu:
Fix Released
Bug description:
What I do miss in Unity is the possibility to click on the app. icon on the
Unity launcher bar to minimize all windows of that application, not only to
launch/restore it.
mlaverdiere's futher addition:
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2
My suggestion would be to modify the interaction-design/process like
this (*=my modification proposal/2 cents!):
1) start it, if it hasn't been started yet;
*2) restore it, if it is minimized;
*3) focus the app, if it's started, not minimized and has not the focus yet;
4) spread windows (of app), if app is focused and has multiple windows open;
*5) minimize it if it is in spread-mode (see 4).
Note that this bug has over 300 comments and several working but
rejected patches. This means that this feature probably will never
land in official Unity! So if you want it, you have to use a patched
version of Unity.
There is a working patch for 13.04 ( from comment #322,
https://bugs.launchpad.net/ayatana-
design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
Somebody should set up a PPA (and note it here) to make it easy to
install the patched version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/733349/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
No longer affects notify-osd?
When is someone with the authority and the ability going to wake up and
realize that this bug needs to be fixed, and the way to fix it is to
implement the expire_timeout parameter as specified.
There are plenty of specific cases pointed out in this report of users
and developers who require support for the expire_timeout parameter.
Failing to recognize their need is insulting; it sends the message that
Cannonical doesn't care.
For every one person who goes to the trouble of creating a launchpad
account and posting a comment on a bug report, how many give up and
assume nothing can be done? How many stop using Ubuntu? How many stop
using Linux?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228360] Re: No clock in menu bar and can't edit Clock settings
Alberto Salvia Novella Do not change bug status without verification. This bug has not been fixed anywhere. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228360 Title: No clock in menu bar and can't edit Clock settings Status in One Hundred Papercuts: Fix Released Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The latest update broke the clock in several ways: * No clock shows up in the menu bar. * Open Time Date settings. You cannot edit anything in the Clock tab. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu38 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 15:51:55 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-07-12 (800 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MarkForUpload: True SourcePackage: gnome-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1228360/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228360] Re: No clock in menu bar and can't edit Clock settings
What happened to /usr/lib/indicators3/7/libdatetime.so et al? These libraries are missing from several of saucy's indicator-* packages. Take a look: http://packages.ubuntu.com/raring/amd64/indicator-datetime/filelist http://packages.ubuntu.com/saucy/amd64/indicator-datetime/filelist http://packages.ubuntu.com/raring/amd64/indicator-sound/filelist http://packages.ubuntu.com/saucy/amd64/indicator-sound/filelist Perhaps they are not needed for unity, but these were used to load indicators for other panels. Without these libraries the indicators can't be used outside of unity. I hate unity, but I like indicators. Can I have them back please? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228360 Title: No clock in menu bar and can't edit Clock settings Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: The latest update broke the clock in several ways: * No clock shows up in the menu bar. * Open Time Date settings. You cannot edit anything in the Clock tab. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu38 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 15:51:55 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-07-12 (800 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MarkForUpload: True SourcePackage: gnome-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1228360/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
mpt
No, it doesn't.
http://www.galago-project.org/specs/notification/0.9/x408.html#command-
close-notification
In section 9, notifaction D-BUS protocol specification, it clearly
states:
The following messages must be supported by all implementations.
Following that is section 9.1, which lists several messages that are
required to be implemented.
Among them, in subsection 9.1.2:
expire_timeout INT32 The timeout time in milliseconds since the
display of the notification at which the notification should
automatically close.If -1, the notification's expiration time is
dependent on the notification server's settings, and may vary for the
type of notification. If 0, never expire.
Perhaps this is where design decisions for NotifyOSD began to go wrong:
If 0, never expire.
This specification presents a problem for Ubuntu's NotifyOSD design,
which renders notifications with no means of closing the notifications
manually. In fact, NotifyOSD renders notifications that don't accept any
interaction at all:
http://developer.ubuntu.com/resources/technologies/notification/#Notification_actions
Notify OSD bubbles cannot be clicked on themselves, nor can they
contain buttons that can be clicked: in the terminology of the Desktop
Notifications Specification, they do not accept actions.
Therefore, a timeout is the only means of closing NotifyOSD
notifications, however a notification with expire_timeout 0 would never
disappear, which is actually a problem with the freedesktop.org
specification in that it allows non-interactive notifications with an
expire_timeout of 0.
However, there is already logic in NotifyOSD to handle this specific
situation:
http://developer.ubuntu.com/resources/technologies/notification/#Non-
expiring_notifications
Some programs specify an expire_timeout of 0 to produce notifications
that never close by themselves, assuming that they can be closed
manually as they can in notification-daemon. Because this is usually
done for a message that requires response or acknowledgement, Notify OSD
presents it as an alert box rather than as a bubble.
Furthermore if a notification does not actually need response or
acknowledgement, you can avoid it appearing as an alert box by setting
the expire_timeout to the default value of -1. So NotifyOSD has to
support expire_timeout by design after all.
There are no conflicts between fredesktop.org's specification and
NotifyOSD's design that prevent a notification from dissapearing on a
timer set by the program or script sending a notification. As there is
no need to resolve the already resolved issue of non-expiring
notifications, and no other conflict with the specification related to
expire_timeout, and the design includes a use case for the parameter,
there is no logic to support removing expire_timeout support from
NotifyOSD or it's documentation.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in Notify OSD:
Won't Fix
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon
eZFlow Unfortunately, I don't have any authority whatsoever to implement policy here or elsewhere. Even more unfortunate is that I lack the programming skill to fork Unity and implement this on my own. We'll have to wait and see if someone with both the authority and the skill to resolve this issue comes along. Until then, I've completely given up on Unity as a desktop environment. I've switched to Pantheon, because the people working on it seem to think usability is among the primary virtues of a good interface. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/733349 Title: Minimize Application's Windows upon clicking its Launcher Icon Status in Ayatana Design: Won't Fix Status in Obsolete project please ignore: Confirmed Status in Unity: Won't Fix Status in Unity Tweak Tool: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: What I do miss in Unity is the possibility to click on the app. icon on the Unity launcher bar to minimize all windows of that application, not only to launch/restore it. mlaverdiere's futher addition: https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2 My suggestion would be to modify the interaction-design/process like this (*=my modification proposal/2 cents!): 1) start it, if it hasn't been started yet; *2) restore it, if it is minimized; *3) focus the app, if it's started, not minimized and has not the focus yet; 4) spread windows (of app), if app is focused and has multiple windows open; *5) minimize it if it is in spread-mode (see 4). Note that this bug has over 300 comments and several working but rejected patches. This means that this feature probably will never land in official Unity! So if you want it, you have to use a patched version of Unity. There is a working patch for 13.04 ( from comment #322, https://bugs.launchpad.net/ayatana- design/+bug/733349/+attachment/3573380/+files/minimize.patch ). Somebody should set up a PPA (and note it here) to make it easy to install the patched version. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/733349/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon
Following the overwhelming trend of comments in this report an elsewhere, the design needs to be changed. I don't see how anything less will ever end this controversy or this discussion. ** Changed in: canonical-design Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/733349 Title: Minimize Application's Windows upon clicking its Launcher Icon Status in Ayatana Design: Won't Fix Status in Canonical Design: Confirmed Status in Unity: Won't Fix Status in Unity Tweak Tool: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: What I do miss in Unity is the possibility to click on the app. icon on the Unity launcher bar to minimize all windows of that application, not only to launch/restore it. mlaverdiere's futher addition: https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2 My suggestion would be to modify the interaction-design/process like this (*=my modification proposal/2 cents!): 1) start it, if it hasn't been started yet; *2) restore it, if it is minimized; *3) focus the app, if it's started, not minimized and has not the focus yet; 4) spread windows (of app), if app is focused and has multiple windows open; *5) minimize it if it is in spread-mode (see 4). Note that this bug has over 300 comments and several working but rejected patches. This means that this feature probably will never land in official Unity! So if you want it, you have to use a patched version of Unity. There is a working patch for 13.04 ( from comment #322, https://bugs.launchpad.net/ayatana- design/+bug/733349/+attachment/3573380/+files/minimize.patch ). Somebody should set up a PPA (and note it here) to make it easy to install the patched version. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/733349/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
Last year I did some work in unityshell.cpp to make it actually honour the window order and pretend that its input windows were real ones. Do you recall a specific release version in which those changes were working? I'd like to try it out, since I have never seen unity /not/ having this problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Confirmed Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) - Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Well, it looks like the tide has turned toward sweeping this under the
rug by changing the man page...
Allow me to reiterate that this is the wrong way to fix this bug.
The correct way would be to support the timeout parameter.
That would also follow the freedesktop spec, if it still means anything
to anybody.
Case in point:
Similar to adryoman5, I'm use a script that controls a television card
and uses notify-osd to provide information much like the OSD on an
actual television. Some of the messages are relatively important, others
are unimportant. The --urgency parameter is not what I'm looking for
as it only controls which messages a user will actually see (and users
have no idea how to control which messages they will actually see). The
best way to do this is to specify all the messages as --
urgency=critical to be certain they will actually make it onto the
screen; but some of them don't need to stay there long.
For example, when channel surfing, if I leave each CH+/- on the screen
for five seconds, by the time I've switched five channels I might still
be looking at the number of the first one, or possibly five numbers for
five different channels. That would be dumb. The numbers need to be
displayed, but they don't need to be displayed for five seconds each.
Less than a second each would be acceptable. This is not possible with
the current design.
You might ask why I just don't replace each old notification with the
next one, but then I'd have to redirect you to bug 257135
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in Notify OSD:
Won't Fix
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
