Hello Chris,

sorry for not responding for such a long time. I'm aware of the issue you
are describing and think due to the messed up world of notification areas
there is no future safe solution. GNOME Shell along with an incompatible
KDE upgrade both killed all cross-desktop environment safe solution.

This is why I decided for 1.11 to significantly simplify the tray icon support.
The idea is to isolate the code into a plugin that will not activate with GNOME
shell and to have a different plugin for GNOME shell. To prevent the problem
you describe hiding was entirely removed (but could be reimplemented in tge
GTK notification area plugin as an option.

As a temporary solution adding "-w shown" to the starter options might help.


On Sat, Mar 29, 2014 at 3:37 AM, Chris Siebenmann <cks@cs.toronto.edu> wrote:
|  My Liferea (compiled from the latest git tip) has started hanging during
| startup (before it brings up the window and so on).

 It turns out that this was not the case; what was actually going on was
that Liferea had decided to start in 'hidden' state (probably due to a
remembered value of the last window state). In my case it was *really*
hidden, since I am not running a modern Gnome environment and I did not
have the tray icon plugin enabled.

 There are two workarounds for this. First, I can start liferea with '-w
shown' to force it to always shown the main window on startup.  Second,
if Liferea hides away trying to start another copy of Liferea will
re-shown the running Liferea.

 It would be nice if there was some way for Liferea to detect that the
hidden state was this invisible and refuse to go into it. Alternately
I'd be happy with a preference that said 'never go to hidden state'.

(My actual solution so far is to hardcode Liferea to default to starting
in shown state regardless of the remembered last state it was in .)

        - cks

Liferea-devel mailing list