[blfs-dev] libnotify-0.7.6 in Seamonkey, Thunderbird and Firefox

Fernando de Oliveira famobr at yahoo.com.br
Wed Sep 30 15:46:47 PDT 2015

Em 30-09-2015 14:58, Bruce Dubbs escreveu:
> Fernando de Oliveira wrote:
>> This is bothering me for years, perhaps. Have asked long ago, no reply.
>> It is always there in the pages and scripts. It does nothing, for me, at
>> runtime. Or does it?
> I really don't know what it does here.

Many things: when it worked, it notified when a restart was needed due
to an extension update, when a download had finished, and with the right
extensions, when a ne mail arrived. It was done with the same
notification system that tels you if a connection is up or down, with
Network Manager. And the notifications were kept one below the other
until libnotify changed and the notifications were ket as an ivon in the
panel notification area.

Just discovered that there is an extension that makes it work back with
libnotify, but have not tested and don't know if works with latest firefox:


I am finally building firefox-41.0 (got courage, today) building new FF
(several days without building anything), last update was on September
13th, 2015.

> In SM, grepping through my build
> directory I see:
> mailnews/base/src/nsMessengerUnixIntegration.cpp:
> // determine if we should use libnotify or the built-in alert system
> Reading more comments there indicate that there should be an indication
> of new mail in the system tray.  I don't know if it is used in FF or not.
>> I don't know enough to completely understand this code, worse yet the
>> entire file, but it seems to me this is a left over code.
> Me either.  AFAIK, the build doesn't complain if
> ac_add_options --disable-libnotify
> is in mozconfig, so I would prefer to leave it.
>> These results seem to demonstrate that from the three mozconfigs
>> libnotify can be removed.
>> I am not 100% sure if it can be remove from the dependencies.
>> Please, some opinions? Should it be completely removed?
> Not before release, but have you tried to build SM without
> --disable-libnotify and with libnotifyso removed?
>   -- Bruce

I was almost sure that libnotify could be removed from all of the three:


> William Chen [:wchen] 2013-03-27 17:28:24 PDT
> (In reply to Alex Keybl [:akeybl] from comment #5)
>> wchen - can you confirm comment 4, and move this into the TB product
>> if we can't make core changes to support them in FF22?
> I can confirm that removing libnotify was intentional. It is important
> that notifications work on all platforms, not just the ones that had
> libnotify installed. In addition, not all libnotify implementations
> support necessary features to implement the updated alerts service API
> (being able to click and close them).
> (In reply to Alex Keybl [:akeybl] from comment #7)
>> I'm trying to understand whether bug 782211 was landed assuming
>> resolution of bug 852648 and bug 852917 in FF22, or whether
>> engineering was hoping TB would make a comm-specific backout and
>> diverge from Firefox.
> The idea was to use the XUL notifications and add back support for
> native notifications if they could support the updated alerts service
> API. There was no intent for a comm backout.

But this long thread


Reported: 	2013-04-06 05:53 PDT by Stephan Sokolow
Modified: 	2015-07-20 15:27 PDT

made me confuse again.

Fernando, aka Sísifo

More information about the blfs-dev mailing list