No apparent way to change the color and location of the popups

[Brian J. Murrell]

The new libnotify behavior in Karmic is just not working for me. The prompts are too far out of my primary focus and too dark (in color, not what they are saying :-).

I can't seem to find any way to configure where the bubble's pop up nor a way to change their color.

The gconf /apps/notification-daemon/ settings seem to be getting ignored as are the "tooltips" color settings from the theme editor.

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[Brian J. Murrell (brian-interlinx)]

On Thu, 2010-07-01 at 12:28 +0000, Sebastien Bacher wrote:
> Thanks for the bug report. This particular bug has already been
> reported,

And the already reported bug number is what?

> but feel free to report any other bugs you find.
>
> ** Package changed: libnotify (Ubuntu) => notify-osd (Ubuntu)
>
> ** Changed in: notify-osd (Ubuntu)
> Importance: Undecided => Wishlist
>
> ** Changed in: notify-osd (Ubuntu)
> Status: New => Invalid

Wouldn't it be much more useful (to me and anyone else that comes across
this bug) to close this as a duplicate of another bug rather than
Invalid?

[Sebastien Bacher (seb128)]

> And the already reported bug number is what?

finding notify-osd requests for customization shouldn't be harder, there has been quite some of those

> Wouldn't it be much more useful (to me and anyone else that comes across this bug) to close this as a duplicate of another bug rather than Invalid?

It could but it would require spending times searching for numbers

[Brian J. Murrell (brian-interlinx)]

On Mon, 2010-07-05 at 08:38 +0000, Sebastien Bacher wrote:
> > And the already reported bug number is what?
>
> finding notify-osd requests for customization shouldn't be harder, there
> has been quite some of those

I am sure you are much more adept at searching issues in LP than I am.
If it's not so difficult, could you oblige me?

> It could but it would require spending times searching for numbers

Well, that's kinda part-and-parcel with closing bugs as "already filed".
Surely the person closing a bug as a duplicate must have a duplicate bug
in hand and not just "some idea" that some other similar bug must exist.

Put another way, surely the person responsible for a given package or
aspect of the distro must be very familiar with all of the open issues,
or have the ability to find all open issues related to his
responsibilities very quickly and easily -- much more so than a user
reporting a bug.

[Sebastien Bacher (seb128)]

> Well, that's kinda part-and-parcel with closing bugs as "already filed". Surely the person closing a bug as a duplicate must have a duplicate bug in hand and not just "some idea" that some other similar bug must exist.

Not especially no, I've read regular discussions and requests for such options over years but I didn't keep note of each bug numbers

> Put another way, surely the person responsible for a given package or aspect of the distro must be very familiar with all of the open issues, or have the ability to find all open issues related to his responsibilities very quickly and easily -- much more so than a user reporting a bug.

Right, it might take a short time search for one duplicate, but hundred of duplicates are opened every day and it quickly counts in hours of time a day, time which could be used to work on the issue or search for numbers.
Reopening this bug since I was just trying to keep the buglist usable by closing known duplicates, I don't want to spend my days searching for duplicates, some other triager might pick it up or the bug will just be a bit less easy to work on.

[David D Lowe (flimm)]

As far as I can tell, this is the combination of three separate bugs:
Bug #420583: "Notify-osd looks are not customizable"
Bug #420514: "Position of notification bubbles could be configurable"
Bug #346095: "Regression: bubble location setting from notification-daemon is not migrated to notify-osd"