I too have seen a lot of these problems during the f7 to f8 upgrade - many
scriptlets failing (requiring rpm -e --noscripts to erase) and generated cache
invalid messages.  This may explain why, when I add the "running green man"
logout button to the gnome panel I just get a shaded grey square icon instead.

Scriptlets mass-failing (that's where the "invalid cache" messages come from)
are typically selinux-issues, there's nothing rpm itself can do about it.
SELinux relabeling strongly recommended...

SELinux is disabled on the systems I'm using.

I simply do not believe SELinux is the problem because:

* SELinux is disabled on runtime
* SELinux is disabled with kernel-param

Ok... all the above errors are caused by package scriptlets running
gtk-update-icon-cache being and failing for whatever reason, thus causing rpm
not to erase the old package. 

This is not an rpm bug but something else:
a) those packages shouldn't let scriptlets terminate with error codes to begin with
b) what the root issue behind gtk icon cache failures is I don't know

Reassigning to gtk2 maintainer who probably has a better clue what b) is.
Summary also updated...

Im not sure that this is only a gtk2-problem
On this machine vncviewer does not work and if i logout xserver is killed and a
"startx" says the is no font "fixed"

Trying to remove "vnc" fails, removing with "rpm -e --noscripts" rmeoves the
package, and installing again brings "scriptlet failed"

vncviewer exists with "Failed to load any font", i dont know really about the
background of the problem but it seems for me that is triggered....

Hope there will be soon a solution
The upgraded machine works just fine in most cases, but dupes after updates can
be a problem if packages are replaced from other ones, so you do not find them
but they are here :-(

----------------------------

(1/2): vnc-4.1.2-23.fc8.i 100% |=========================|  91 kB    00:01
(2/2): vnc-libs-4.1.2-23. 100% |=========================| 167 kB    00:02
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: vnc-libs                     ######################### [1/2]
  Installing: vnc                          ######################### [2/2]
The generated cache was invalid.
error: %post(vnc-4.1.2-23.fc8.i386) scriptlet failed, exit status 1

Installed: vnc.i386 0:4.1.2-23.fc8
Dependency Installed: vnc-libs.i386 0:4.1.2-23.fc8
Complete!
[harry@nb scripts]$ vncviewer

VNC Viewer Free Edition 4.1.2 for X - built Oct 23 2007 13:57:25
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Failed to load any font

Hi,

I also had this problem. I discovered that there is a file in the GTK icon
folder called: 

/usr/share/icons/hicolor/autopackage-installer.png

This file does not belong to any RPM package, according to the RPM DB on my
Fedora 8 system. I removed this file and /usr/bin/gtk-update-icon-cache stopped
throwing the "The generated cache was invalid." mesages. Further attempts to
remove the affected package by "rpm -e <packagename>" worked flawlessly.

Hope this helps.

Ciao, Thomas

Thanks Thomas.

I can confirm that removing this file fixes the scriptlet problems I've been
having.  The file actually occured in 4 places on my system:

/usr/share/icons/
/usr/share/icons/hicolor/
/usr/share/pixmaps/
/usr/share/pixmaps/hicolor/

I don't know if it is required anywhere, but removing it from the
pixmaps/hicolor folder seems to have been recommended as well.

Yes it seems to fix the problem
But how can it be that the reason for package-dupes is a fucking image too much
in an folder? OK, a warning i would understand, but so this is very bad...

__

[harry@nb ~]$ locate autopackage-installer.png
/usr/share/icons/autopackage-installer.png
/usr/share/icons/hicolor/autopackage-installer.png
/usr/share/pixmaps/autopackage-installer.png
/usr/share/pixmaps/hicolor/autopackage-installer.png
[harry@nb ~]$ sudo rm -f /usr/share/icons/autopackage-installer.png
Passwort:
[harry@nb ~]$ sudo rm -f /usr/share/icons/hicolor/autopackage-installer.png
[harry@nb ~]$ sudo rm -f /usr/share/pixmaps/autopackage-installer.png
[harry@nb ~]$ sudo rm -f /usr/share/pixmaps/hicolor/autopackage-installer.png
[harry@nb ~]$ sudo rpm -e system-config-display
Fehler: Fehlgeschlagende Abhängigkeiten:
        system-config-display wird benötigt von (installiert)
livna-config-display-0.0.19-1.lvn8.noarch
[harry@nb ~]$ sudo rpm -e --nodeps system-config-display
Fehler: Aufruf von stat für /mnt/arrakis nicht möglich: Keine Berechtigung
[harry@nb ~]$ sudo yum -y install system-config-display
Loading "skip-broken" plugin
Loading "kernel-module" plugin
Loading "presto" plugin
Loading "fedorakmod" plugin
Loading "fastestmirror" plugin
Setting up and reading Presto delta metadata
No Presto metadata available for rhsoft-java
No Presto metadata available for rhsoft-generic
No Presto metadata available for livna
No Presto metadata available for fedora
No Presto metadata available for kde-redhat-all
No Presto metadata available for kde-redhat
No Presto metadata available for adobe-linux-i386
No Presto metadata available for rhsoft-fedora
No Presto metadata available for updates
No Presto metadata available for freshrpms
No Presto metadata available for remi
Loading mirror speeds from cached hostfile
Excluding Packages from Fedora 8 - i386
Finished
Excluding Packages from Fedora 8 - i386 - Updates
Finished
Reducing Freshrpms - Fedora 8 to included packages only
Finished
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package system-config-display.noarch 0:1.0.51-4.fc8 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 system-config-display   noarch     1.0.51-4.fc8     fedora            186 k

Transaction Summary
=============================================================================
Install      1 Package(s)
Update       0 Package(s)
Remove       0 Package(s)

Total download size: 186 k
Downloading Packages:
Downloading DeltaRPMs:
Rebuilding rpms from deltarpms
(1/1): system-config-disp 100% |=========================| 186 kB    00:01
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: system-config-display        ######################### [1/1]
error: failed to stat /mnt/arrakis: Permission denied

Installed: system-config-display.noarch 0:1.0.51-4.fc8
Complete!
[harry@nb ~]$  

Whatever program prints "The generated cache was invalid" should print its name
in the beginning.  I assume it's /usr/bin/gtk-update-icon-cache, since the
"strings" command finds that message inside the executable.  If possible, the
offending file should be named too.

I have always assumed it was an rpm error, I rebuilt the rpm database many times
and I was even thinking of reinstalling Fedora when I decided to search for the
message and found this bug.

I don't even remember that I have ever played with autopackage.  The timestamp
of autopackage-installer.png is October 5, 2005 - more than two years ago.  It's
my main development system, and I need to try a lot of software on it.

Please increase severity of the bug.  It pins old versions of packages and
causes conflicts in updates down the road.

Are you still experiencing the reported issue in F-9 or rawhide?

Thanks!

No further problems with updated F-9

djwood1: thanks, this bug appears to be isolated to F-8.

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.