Screenshosts of the notification you're talking about would be nice. At the
moment I can only guess what you're seeing. Next would be to file this bug
against seahorse (and not notify-osd), because it is not within notify-osd's
scope to control what gets send to it. Some advice for enhancing sea
This needs to be filed against seahorse upstream
(http://projects.gnome.org/seahorse)
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
--
notifikation with seahorse
https://bugs.launchpad.net/bugs/375370
You received this bug notification because you are a member of Ubuntu
Bugs,
The theme in question needs to inherit from gnome or Human icon-theme.
Furthermore we provide fallback-icons as part of the notify-osd package.
You can find the installed icons here /usr/share/notify-
osd/icons/hicolor/scalable/status/*.svg
--
Most icon themes don't have icons for notify-osd
http
kwwii knows the mechanisms of icon-theme inheritance much better then I
do. This is actually something that needs to be fixed in icon-themes.
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Kenneth Wimer (kwwii)
-
That looks like HP Device Manager is not using notifications following
the galago spec (http://www.galago-
project.org/specs/notification/0.9/index.html) at all. According to you
remark it seems to be a Qt application using it's own notification
bubble rendering system. This bug is therefore invali
not a notify-osd issue, rather compiz-related (to be really exact it's
an issue of DRI2 missing)
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Inkscape in fullscreen f
not an inkscape-related issue, see my comment for explanation of the
issue: https://bugs.edge.launchpad.net/ubuntu/+source/notify-
osd/+bug/372789/comments/1
** Changed in: inkscape (Ubuntu)
Status: New => Invalid
** Changed in: inkscape (Ubuntu)
Assignee: (unassigned) =>
That's not a notify-osd specific bug, but a compiz-related issue. For
example you can trigger the same kind of flashing by simply starting
totem playing back some video, switching totem to fullscreen-mode and
then in fullscreen-mode move the mouse (to that the on-screen UI-
elements appear). That c
*** This bug is a duplicate of bug 372789 ***
https://bugs.launchpad.net/bugs/372789
** This bug has been marked a duplicate of bug 372789
Inkscape in fullscreen flashes when using NotifyOSD
--
notify-osd interferes with full screen video playback in mplayer
https://bugs.launchpad.net/bug
** Changed in: notify-osd (Ubuntu)
Status: New => Confirmed
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Matthew Paul Thomas (mpt)
--
[wishlist] Click to dismiss
https://bugs.launchpad.net/bugs/371093
You received this bug notification because you are a member of Ubun
nee: (unassigned) => Mirco Müller (macslow)
--
Notification bubble that does not disappear
https://bugs.launchpad.net/bugs/369915
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.ubuntu.com
How long did you wait for the initial "Volume Muted" bubble to disappear
before you considered it to be faulty (more than 3 seconds)?
With your "system booting" you actually mean the GNOME-desktop starting
after login (autologin)?
When you mute your volume on desktop-startup the "Volume Muted" bu
The blur-cache is missing still in notify-osd. Once that implemented
this lag will no longer occur.
** Changed in: notify-osd (Ubuntu)
Status: New => Confirmed
--
notify-osd is very, very slow
https://bugs.launchpad.net/bugs/367049
You received this bug notification because you are a memb
This is not correctly filed. The correct packages is gnome-settings-
daemon. That's the application triggering the volume-notifications based
upon the keyboard multimedia-keys.
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
--
Sound notification and Mixer applet disagree on cor
Pi Boy, does mannheim's advice fix the issue for you? BTW, notify-osd
only displays what gets send to it. Thus it is not correctly filed. The
correct packages in this case would be gnome-settings-daemon. That's the
application triggering the volume-notifications based upon the keyboard
multimedia-k
Are you talking about the summary-text (title) or the body-text? With
regards to links placed in a bubble's body-text, we provide guidlines
for apps to not do that
(https://wiki.ubuntu.com/NotificationDevelopmentGuidelines,
https://wiki.ubuntu.com/NotificationDesignGuidelines), since a user
cannot
** Changed in: notify-osd (Ubuntu)
Status: New => Confirmed
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Notifications appear in non-visible area of multi-head desktop
https://bugs.launchpad.net/bugs/367947
You received this bug notifi
ification-audio-volume-medium -h int:value:75 -h
string:x-canonical-private-synchronous:
Also make screenshots of these and attach them to this bug-report.
Thanks in advance.
** Changed in: notify-osd (Ubuntu)
Status: New => Incomplete
** Changed in: notify-osd (Ubuntu)
Assignee: (
** Also affects: hplip
Importance: Undecided
Status: New
--
hplip notifications do not integrate
https://bugs.launchpad.net/bugs/373773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Bug https://bugs.edge.launchpad.net/hplip/+bug/354451 filed against
HPLIP indicates HPLIP not using a libnotify-based notification-system
correctly. Thus notifications are no passed via DBus according to the
specs (https://wiki.ubuntu.com/NotifyOSD, http://www.galago-
project.org/specs/notification
*** This bug is a duplicate of bug 345251 ***
https://bugs.launchpad.net/bugs/345251
I've not been able to reproduce this yet myself, but it appears to be
another instance of notify-osd being started (probably by root) and
displaying notification-bubbles. This is very likely a duplicate of
345
** Changed in: notify-osd
Status: In Progress => Fix Committed
** Changed in: notify-osd (Ubuntu)
Status: In Progress => Fix Committed
--
Meter for brightness/volume is too flat
https://bugs.launchpad.net/bugs/338215
You received this bug notification because you are a member of Ub
** Changed in: pidgin-libnotify (Ubuntu)
Status: New => Fix Committed
** Changed in: pidgin-libnotify (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
** Changed in: notify-osd (Ubuntu)
Status: New => Fix Committed
** Changed in: notify-osd (Ubuntu)
** Changed in: notify-osd
Importance: Undecided => Low
** Changed in: notify-osd
Status: New => Invalid
** Changed in: notify-osd
Assignee: (unassigned) => Mirco Müller (macslow)
--
Banshee album art is blurred in notification bubbles
https://bugs.launchpad.net/bugs/3
** Changed in: notify-osd
Importance: Undecided => Low
** Changed in: notify-osd
Status: New => Triaged
** Changed in: notify-osd
Assignee: (unassigned) => Mirco Müller (macslow)
--
Tango icon theme does not have the notifiy osd icons
https://bugs.launchpad.net/bugs/3
The /usr/share/icons/Tango/index.theme:3 needs to change from
Inherits=gnome,crystalsvg
to
Inherits=gnome,crystalsvg,Human
so the missing notification-icons are picked up by the Tango icon-theme. Since
tango-icon-theme is using quilt as a patch-system I'm afaid I can't provide a
patch right now.
signee: (unassigned) => Mirco Müller (macslow)
--
Still shows up and flickers the screen when watching in full screen via VLC
Media Player
https://bugs.launchpad.net/bugs/365003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu (via b
This image (-size/quality) passed to notify-osd for display is outside
of the control of notify-osd.
** Changed in: notify-osd
Importance: Undecided => Low
** Changed in: notify-osd
Status: New => Invalid
** Changed in: notify-osd
Assignee: (unassigned) => Mirco Müller
Do you press and hold the VolumeUp/Down key or press it only once?
--
notify-osd is infinitly called
https://bugs.launchpad.net/bugs/376554
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.ub
Pedro, regarding Ara's request... copy $HOME/.cache/notify-osd.log right
after the bug hits. Preferably from a remote system you logged into to
your Toshiba U300 if you can. This is needed since notify-osd.log is
recreated each time notify-osd is started (e.g. when you log into your
desktop-session
Hm... that looks like some odd misbehaving of NetworkManager there. On
the other hand-side throttling/"spam-protection" in notify-osd isn't in
place yet to. Does it somehow look like in the screencast I attached?
** Attachment added: "screencast example of simulated behaviour"
http://launchpadl
Via which means did you aquire this number?
--
notify-osd heavy memory usage
https://bugs.launchpad.net/bugs/334141
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.ubuntu.com
https://lists.u
BTW, on my system notify-osd is reported to be using 8.3 MBytes by
gnome-system-monitor. top reports for notify-osd 17 MBytes (RES) and 174
MBytes (VIRT).
--
notify-osd heavy memory usage
https://bugs.launchpad.net/bugs/334141
You received this bug notification because you are a member of Ubuntu
Do you have a screenshot of the notification you're talking about. I've
never seen something like that yet. From NetworkManager I only get
"connected" and "disconnected" notifications.
--
networkmanager + libnotify + available wireless networks = bad usability
https://bugs.launchpad.net/bugs/3834
. For Karmic+1 that will be a different story and we'll revisit this.
But let's focus on Karmic for now.
** Changed in: notify-osd (Ubuntu)
Status: New => Triaged
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Notifications not v
*** This bug is a duplicate of bug 344978 ***
https://bugs.launchpad.net/bugs/344978
** This bug has been marked a duplicate of bug 344978
notify-osd takes you out of the fullscreen flashplayer
--
System volume up/down notifications exit full screen flash, whereas other
system notificati
*** This bug is a duplicate of bug 344978 ***
https://bugs.launchpad.net/bugs/344978
** This bug is no longer a duplicate of bug 387650
System volume up/down notifications exit full screen flash, whereas other
system notifications do not.
** This bug has been marked a duplicate of bug 344
What Mark describes there is is possible with notify-osd right now. Ted
I don't think it's too much to ask of a application developer to watch
one notification. It's easy to implement. Have a look at the attached
screencast were I simulate Mark's music-player example with a simple
python script fee
Well is it banshee or rhythmbox? :)
--
design problem? infinite wait for long queue
https://bugs.launchpad.net/bugs/334809
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.ubuntu.com
https://
The design team wants the indicator to "throb" when the user hits
volume/brightness up (down) but the systems state-value for that is
already at its maximum (minimum). The only way to communicate this to
notify-osd by using these special values 101 (-1), because notify-osd
has no (and should not ha
I fixed several things in the pixels-per-em calculation (there should be
no more rounding errors) and I set the factors for title- and body-text
back to 1.0 and 0.8. With that this (see attachment) is what I get from
your example.
I'm not sure what I should regard for text-height there. The l, i o
Because there once was a discussion between using 1.2 EMs (title), 1.0
EMs (body) and 1.0 EMs (title), 0.8 (body) I provide a side-by-side
comparison of both settings with the recently fixed EM- and font-height
calculation code of notify-osd trunk. I just want to avoid coming back
to this later, sh
I let the screenshot speak for itself :)
** Attachment added: "screenshot of fixed notify-osd trunk"
http://launchpadlibrarian.net/28301043/resolved.png
--
Font size is too large by default
https://bugs.launchpad.net/bugs/391190
You received this bug notification because you are a member of U
** Changed in: notify-osd (Ubuntu)
Importance: Undecided => Medium
** Changed in: notify-osd (Ubuntu)
Status: New => Fix Committed
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Font size is too large by default
https://bugs.laun
: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
networkmanager + libnotify + available wireless networks = bad usability
https://bugs.launchpad.net/bugs/383404
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
dredpapercuts
Assignee: (unassigned) => Mirco Müller (macslow)
--
volume control by hotkeys - notification sluggish
https://bugs.launchpad.net/bugs/389072
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 367049 ***
https://bugs.launchpad.net/bugs/367049
** This bug has been marked a duplicate of bug 367049
notify-osd is very, very slow
--
notify-osd runs at 100% of CPU locking up X
https://bugs.launchpad.net/bugs/367069
You received this bug notification
manzur, thanks for the video. It confirms my assumption. With the blur
/surface-cache, meant to land in notify-osd by the time Karmic hits,
this should be solved. Apart form that, "spam-protection" in the queue-
handling of notify-osd will also help ease the flood of these feedback-
notifications (
*** This bug is a duplicate of bug 367049 ***
https://bugs.launchpad.net/bugs/367049
** This bug has been marked a duplicate of bug 367049
notify-osd is very, very slow
--
volume control by hotkeys - notification sluggish
https://bugs.launchpad.net/bugs/389072
You received this bug notifi
*** This bug is a duplicate of bug 367049 ***
https://bugs.launchpad.net/bugs/367049
** This bug has been marked a duplicate of bug 367049
notify-osd is very, very slow
--
Volume notification pops up and never go off using 100% cpu
https://bugs.launchpad.net/bugs/376840
You received this
There's nothing we can do about the "unfullscreen-ing" of the Adobe's
flash-plugin. In notify-osd trunk I'm using...
gtk_window_set_focus_on_map (GTK_WINDOW (window), FALSE);
gtk_window_set_accept_focus (GTK_WINDOW (window), FALSE);
... to make sure a notification-bubble is really not focused whe
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Queued statuses from pidgin-microblog using CPU/RAM and freezing pidgin
https://bugs.launchpad.net/bugs/386880
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 271706 ***
https://bugs.launchpad.net/bugs/271706
In my opinion you're suffering form the missing blur- and surface-
caching in the currently shipping version of notify-osd. The continuous
triggering of notify-osd via the volume-wheel of your laptop might ver
I can't reproduce this on Jaunty (Ubuntu 9.04) with i945- and i965-based
GPUs running compiz.
--
Freeze when pressing alt-space after scaling out (super-E)
https://bugs.launchpad.net/bugs/129398
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have notify-osd exception rules in the open- and close-sections for
the animation-plugin. Furthermore I have the same exception also in the
fade-plugin. With both plugins enabled only occasionally I see the
flicker on fading-in.
It makes sense that you'll see some flickering becaue both plugins
It is on our radar for the default compiz-settings in karmic.
--
OSD notifications sometimes flicker when fading in
https://bugs.launchpad.net/bugs/331564
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
I tried it on nvidia- and intel-based GPUs. Both under
metacity+compositor and compiz. For the intel-based GPUs I used the new
UXA/DRI2 architecture and the old EXA one. The flickering was only
present for under the combination intel-GPU with EXA. All other settings
worked without flickering. Thus
I've to state that I'm on kernel 2.6.30 on the intel-based machine I
tested with. BTW, if someone can do me a favour and remove the wrongly
added link to the affected project. Thanks in advance!
** Changed in: notify-osd (Ubuntu)
Importance: Undecided => Medium
** Changed in: notify-osd (Ubunt
A general note here. notify-osd only dispalys what it gets told by an
application via DBus (libnotify). In the case of brightness
notifications the app responsible for sending out those notifications is
gnome-power-manager. This bug should better be filed against gnome-
power-manager.
** Also aff
To be more precise, the patch against gnome-power-manager to use
libnotify (thus notify-osd) is a Ubuntu-specific patch still.
--
brightness notification moves in wrong direction when increasing after a
decrease or vice versa
https://bugs.launchpad.net/bugs/344626
You received this bug notificat
I'm not 100% sure what it looks like. Could you provide a screencast
(e.g. recorded with GtkRecordMyDesktop)? Do you think it's a rendering-
bug of notify-osd or a wrong use of network-manager? A screencast would
help me guess that better.
--
When a CDMA connection is established, the notify-osd
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Width of notifications seem arbitrarily small
https://bugs.launchpad.net/bugs/336110
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
In notify-osd trunk proximity-fade has been implemented
(http://bazaar.launchpad.net/%7Enotify-osd-developers/notify-
osd/main/revision/327) as part of the feature-list for the karmic cycle.
** Changed in: notify-osd (Ubuntu)
Status: Confirmed => Fix Committed
--
fade when mouse cursor in
; Won't Fix
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Changed in: notify-osd (Ubuntu)
Importance: Undecided => Medium
--
no blurring is present
https://bugs.launchpad.net/bugs/344896
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.ubuntu.
libnotify-dev does not have any effect on the bug you describe. What
made you (which report-tool) choose to add this information? Only
notify-osd and compiz are of relevance here. It's actually something I
fixed with a patch for the compiz plugin-settings several months ago.
I'm surprised you still
For a better explanation of the issues involved with this bug, please
read the last two paragraphs of
https://bugs.edge.launchpad.net/ubuntu/+source/notify-
osd/+bug/372789/comments/1
--
Screen blinks to desktop when OSD message appears over fullscreen window or
even when you move the mouse
http
Did anybody happen to try notify-osd trunk?! Just a question.
--
Title text is smaller than user's default, and body's even smaller
https://bugs.launchpad.net/bugs/339026
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Changed in: notify-osd
Status: Fix Committed => Fix Released
--
"Overshoot" animation on volume/brightness bubbles is triggered every time it's
at 100%
https://bugs.launchpad.net/bugs/337820
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Your last comment verified my described observation. This is certainly
more precise than your initial comment on the bug-entry.
--
Notifications steal focus from Widget Layer
https://bugs.launchpad.net/bugs/346467
You received this bug notification because you are a member of Ubuntu
Bugs, which i
That's something to patch in the volume-indicator-applet then.
--
No volume change indication on volume change using trackpad or mouse scroll
wheel
https://bugs.launchpad.net/bugs/363304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Assignee: (unassigned) => Mirco Müller (macslow)
--
Brightness/Volume notifications use the same bubble
https://bugs.launchpad.net/bugs/364099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
I'm not sure this particular case should use a notification.
Notifications can be missed and the message someone leaves for a user on
their session should be guaranteed to by read.
--
[jaunty] leave message does not use new notify system
https://bugs.launchpad.net/bugs/333269
You received this bu
I updated the examples for C, Python and C# at
https://wiki.ubuntu.com/NotificationDevelopmentGuidelines to state this
as "best practices".
--
New osd-notify notifications should not have an empty title
https://bugs.launchpad.net/bugs/334292
You received this bug notification because you are a me
The needed fix is to monitor the panel strut. The current implementation
does read this strut only upon daemon startup (which is usually too
early or at least before gnome-panel updated its strut). The current
workaround of restarting notify-osd manually or doing some session-
startup order-magic w
Uff... TCL well :) For the sake of completeness have a look at the
jaunty notification development guidelines here
http://wiki.ubuntu.com/NotificationDevelopmentGuidelines you at least
find example code in C, Python and C#. That's the best I can provide
right now. I'm just about to extend that docu
There's not much one can do to improve the look of notifications for the
non-composite case without redesigning the way the bubble-background is
rendered (that black rounded rectangle thing). The non-composited case
never has been a priority. Therefore no design-thought went into this
case. The onl
If all goes well tomorrow I'll provide a new packages of "notify-osd"
that wraps a summary/title in up to three lines of text.
--
Notification truncated: "System restart req..."
https://bugs.launchpad.net/bugs/331367
You received this bug notification because you are a member of Ubuntu
Bugs, whic
/booting up?
** Changed in: notify-osd (Ubuntu)
Status: New => Incomplete
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
notify-osd is very, very slow
https://bugs.launchpad.net/bugs/367049
You received this bug notification because you are a
Could you try the attached scripts with your system running 9.04 from
the live CD. Do both/just one/none max out too?
** Attachment added: "non-throbbing test"
http://launchpadlibrarian.net/26020587/test-volume-no-throb.sh
--
notify-osd runs at 100% of CPU locking up X
https://bugs.launchpad
** Attachment added: "throbbing test"
http://launchpadlibrarian.net/26020592/test-volume-throb.sh
--
notify-osd runs at 100% of CPU locking up X
https://bugs.launchpad.net/bugs/367069
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
This is not notify-osd running, but a plugin from awn.
** Changed in: notify-osd (Ubuntu)
Status: New => Invalid
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Notify is no longer black
https://bugs.launchpad.net/bugs/364334
You receive
Please note that these two test-scripts will not change the systems
volume at all. They just trigger the pure notifications.
** Changed in: notify-osd (Ubuntu)
Status: New => Incomplete
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
Just to be on the save side ... run the attached script to make sure no
"stale" remains of awn are still on your fathers sytem. After that do:
DEBUG=1 ./notify-osd >/tmp/debug.log
... in a terminal. Then issue the command:
sudo apt-get install libnotify-bin
notify-send "Testing" "This is a test"
Ok, with the two scripts I wanted to make sure it's not the actual
rendering-code of notify-osd. So this looks like it's happening
"outside" of notify-osd. I'm guessing some quirky issue in gnome-
settings-daemon, which triggers the notification, could be the cause. Or
some dbus-related issue.
--
** Changed in: notify-osd (Ubuntu)
Status: New => Confirmed
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
--
should consider vertical elements to position bubbles
https://bugs.launchpad.net/bugs/365088
You received this bug notification b
** Changed in: notify-osd
Status: Confirmed => In Progress
** Changed in: notify-osd
Assignee: Cody Russell (bratsche) => Mirco Müller (macslow)
** Changed in: notify-osd (Ubuntu)
Status: Confirmed => In Progress
--
"Overshoot" animation on volume/br
** Changed in: notify-osd
Status: Triaged => In Progress
** Changed in: notify-osd (Ubuntu)
Status: Confirmed => In Progress
--
Meter for brightness/volume is too flat
https://bugs.launchpad.net/bugs/338215
You received this bug notification because you are a member of Ubuntu
Bugs,
Examples for how to use the new/correct trigger-values (-1, 101) take a
look at the icon-value example (C, Python, C#) in the notify-
osd/examples. This is mainly of concern to the patch for gnome-settings-
daemon.
** Changed in: notify-osd
Status: In Progress => Fix Committed
** Changed i
I switched to "AccelMethod" "UXA" now. Using UXA acceleration on my
lenovo X61 tablet is _much_ faster than EXA. The only issue I see is
with some windows (using compiz) having the wrong alpha-channel
(multiplied alpha), which is mentioned in
https://bugs.edge.launchpad.net/ubuntu/+source/xorg-serv
/NotificationDevelopmentGuidelines
https://wiki.ubuntu.com/NotificationDesignGuidelines.
** Changed in: notify-osd (Ubuntu Jaunty)
Assignee: (unassigned) => Mirco Müller (macslow)
Status: New => Invalid
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.ne
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
Status: New => Confirmed
--
Doesn't adhere to specification
https://bugs.launchpad.net/bugs/340817
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I can confirm that on my lenovo X61 tablet, which is also driven by an
intel i965 ("Mesa DRI Intel(R) 965GM GEM 20090114"). Intrepid was
_a_lot_ faster and snappier with compiz running. I mostly see this when
texture-fetches are being preformed (e.g. when triggering the expo-
plugin, cube-rotation
by gnome-power-manager (the patch to it) in order to
normalize the value passed to notify-osd.
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
Status: New => Invalid
--
Bad number of steps in brightness OSD
https://bugs.launchpad.net/bugs/3396
There's a design-shortcoming in the way notify-osd handles the fallback-
dialog. It does not pass additional widgets from a notification to the
fallback dialog. That's the first thing I'll fix. After that I'll write
a patch to kerneloops upstream to use a nice gtk+-dialog, if notify-osd
is found to
The fix in notify-osd is pushed. It was actually only a typo that
prevented the actions to be passed to the fallback dialog.
** Changed in: notify-osd (Ubuntu Jaunty)
Status: New => Fix Committed
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
Yo
I'm trying to reproduce this with epiphany now and work on a fix for it.
** Changed in: notify-osd (Ubuntu Jaunty)
Status: Triaged => In Progress
--
notify-osd crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
https://bugs.launchpad.net/bugs/332042
You received this bug notification b
** Changed in: notify-osd (Ubuntu Jaunty)
Status: In Progress => Fix Committed
--
notify-osd crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
https://bugs.launchpad.net/bugs/332042
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
ser I don't know the exact package names by heart. It could also
be part of kdebase.
** Changed in: notify-osd (Ubuntu Jaunty)
Assignee: (unassigned) => Mirco Müller (macslow)
Status: Confirmed => Invalid
--
notifications visible through the screensaver
https://bugs.launchpad
Depending how fast the official repo exposes Michaels uploaded libgksu,
you can give it a try grabbing it from my PPA (here:
https://edge.launchpad.net/~macslow/+archive), if you're very impatient.
While I never was able to reproduce the crash on any of my systems, I
found a minor rendering glitch
1 - 100 of 1406 matches
Mail list logo
