Ubuntu
notify-osd package

Misplaced notification balloons

Bug #457973 reported by markpaterson on 2009-10-22

This bug report is a duplicate of: Bug #438536: Notifications should show up closer to top right. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	notify-osd (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: rhythmbox

In Karmic, some of the dark gray notification balloons are displayed in the wrong place (screenshot attached). The light yellow notification balloons for the same apps don't seem to have this problem, and it doesn't occur with all applications.

Example applications with misplaced gray notifications:
Rhythmbox
Network manager
Power ("battery discharging" notification)

Example applications with correctly placed notifications:
Volume
Display brightness

ProblemType: Bug
Architecture: amd64
Date: Thu Oct 22 02:56:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.5-0ubuntu4
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: rhythmbox
Uname: Linux 2.6.31-14-generic x86_64

Tags:

Revision history for this message

markpaterson (markpaters) wrote on 2009-10-22:

misplacedballoon.png Edit (37.7 KiB, image/png)
Dependencies.txt Edit (6.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (88.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (782 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (3.0 KiB, text/plain; charset="utf-8")

Sebastien Bacher (seb128) on 2009-10-22

affects:

rhythmbox (Ubuntu) → notify-osd (Ubuntu)

Revision history for this message

Waldir Leoncio (wleoncio) wrote on 2009-10-22:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #438536, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.