Bug 460831

root@celsius ~ $ cgrep /etc/X11/xorg.conf
Section "ServerLayout"
    Identifier     "single head configuration"
    Screen      0  "Screen0" 1280 0
    Screen      1  "Screen1" LeftOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
    ModulePath      "/usr/lib64/xorg/modules/extensions/nvidia"
    ModulePath      "/usr/lib64/xorg/modules"
EndSection
Section "ServerFlags"
    Option         "AIGLX" "on"
    Option         "Xinerama" "0"
EndSection
Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "XkbModel" "pc105"
    Option         "XkbLayout" "ch"
    Option         "XkbVariant" "de_nodeadkeys"
EndSection
Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Samsung SyncMaster"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "dpms"
EndSection
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "EIZO S2431W"
    HorizSync       31.0 - 76.0
    VertRefresh     59.0 - 61.0
EndSection
Section "Device"
    Identifier     "Videocard0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
    Option         "AddARGBGLXVisuals" "True"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection
Section "Device"
    Identifier     "Videocard1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection
Section "Screen"
    Identifier     "Screen0"
    Device         "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
Section "Screen"
    Identifier     "Screen1"
    Device         "Videocard1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "CRT: nvidia-auto-select +0+0"
EndSection
Section "Extensions"
    Option         "Composite" "Enable"
EndSection

I found out some regularity: It seems to work every third and fourth login, what should not mean, that every first login attempt results in this bug... The Bug always occurs two times in a row, then its gonna work for the next two logins... odd isn't it?

when it happens, what's the output of

ps -ef | grep notification-area-applet

?

if its NOT working:

# ps -ef | grep notification-area-applet
myuser    28942     1  0 20:42 ?        00:00:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=65

if it IS working:

# ps -ef | grep notification-area-applet
myuser     3949     1  0 18:35 ?        00:00:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=54

The problem still persists, even after upgrading gnome and pidgin... now it anyhow does only happen at about every fifth login...this problem is not related to pidgin as e.g. bittorent (version see below) shows the same minimization problem... I really would be happy if this issue could be solved as it is really annoying and forcing me to relogin over and over again... TIA 

$ rpm -qa gnome*
gnome-user-share-0.31-1.fc9.x86_64
gnome-speech-0.4.18-3.fc9.x86_64
gnome-vfs2-obexftp-0.4-6.fc9.x86_64
gnome-python2-desktop-2.22.0-4.fc9.x86_64
gnome-desktop-2.22.3-1.fc9.x86_64
gnome-settings-daemon-2.22.2.1-2.fc9.x86_64
gnome-system-monitor-2.22.4-1.fc9.x86_64
gnome-panel-2.22.2-3.fc9.x86_64
gnome-themes-2.22.0-1.fc9.noarch
gnome-vfs2-2.22.0-1.fc9.x86_64
gnome-pilot-2.0.16-2.fc9.x86_64
gnome-spell-1.0.8-5.fc9.x86_64
gnome-python2-2.22.1-2.fc9.x86_64
gnome-python2-gconf-2.22.1-2.fc9.x86_64
gnome-keyring-pam-2.22.3-1.fc9.x86_64
gnome-python2-gnomekeyring-2.22.0-4.fc9.x86_64
gnome-packagekit-0.2.5-2.fc9.x86_64
gnome-applet-netspeed-0.15.2-1.fc9.x86_64
gnome-media-2.22.0-2.fc9.x86_64
gnome-mag-0.15.0-2.fc9.x86_64
gnome-python2-gnomevfs-2.22.1-2.fc9.x86_64
gnome-vfs2-2.22.0-1.fc9.i386
gnome-applets-2.22.3-1.fc9.x86_64
gnome-mime-data-2.18.0-2.fc7.noarch
gnome-netstatus-2.12.1-4.fc9.x86_64
gnome-utils-2.20.0.1-5.fc9.x86_64
gnome-session-2.22.3-1.fc9.x86_64
gnome-audio-2.22.2-1.noarch
gnome-icon-theme-2.22.0-6.fc9.noarch
gnome-power-manager-2.22.1-1.fc9.x86_64
gnome-vfs2-smb-2.22.0-1.fc9.x86_64
gnome-terminal-2.22.2-1.fc9.x86_64
gnome-user-docs-2.22.1-1.fc9.noarch
gnome-python2-bonobo-2.22.1-2.fc9.x86_64
gnome-panel-libs-2.22.2-3.fc9.x86_64
gnome-python2-libegg-2.19.1-21.fc9.x86_64
gnome-doc-utils-stylesheets-0.12.2-1.fc9.noarch
gnome-screensaver-2.22.1-1.fc9.x86_64
gnome-sharp-2.16.1-1.fc9.x86_64
gnome-applet-sensors-1.8.2-2.fc9.x86_64
gnome-python2-applet-2.22.0-4.fc9.x86_64
gnome-keyring-2.22.3-1.fc9.x86_64
gnome-python2-extras-2.19.1-21.fc9.x86_64
gnome-python2-gtkhtml2-2.19.1-21.fc9.x86_64
gnome-backgrounds-2.22.0-1.fc9.noarch
gnome-mount-0.8-1.fc9.x86_64
gnome-menus-2.22.2-1.fc9.x86_64
gnome-python2-canvas-2.22.1-2.fc9.x86_64
gnome-keyring-2.22.3-1.fc9.i386
gnome-applet-music-2.4.2-1.fc9.x86_64

$ rpm -qa pidgin
pidgin-2.5.2-1.fc9.x86_64

$ rpm -qa *torrent*
bittorrent-4.4.0-7.fc9.noarch

$ ps -ef | grep notification-area-applet
sp4rc     5105     1  0 12:09 ?        00:00:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=42

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I have the same problem with a similar setup (but running fedora 9). I found a workaround, kind of. At least I don't have to logout/in.

Punish the misbehaving /usr/libexec/notification-area-applet by killing it ('kill 28942' - Refer to comment #4).

It will soon try to re-incarnate. Allow it to do so and most of the icons (NetworkManager, pidgin, liferea, ...) are in the notification area again. The one icon I use that don't work is moztrayicon, restarting thunderbird solves that problem.

I hope this helps someone. It's still annoying though.

I can confirm the same behavior. Thanks for the workaround, it was getting annoying.

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.