Arch Linux

kris|~/ies4linux-2.0beta6$ sudo pacman -Syu
:: Synchronizing package databases...
:: current is up to date
error: anonymous login failed
:: extra is up to date
error: anonymous login failed
:: unstable is up to date
:: community is up to date
shadowhand [################] 100% 4K 8.0K/s 00:00:00
:: testing is up to date
:: gvim: local (7.0-1) appears to be newer than repo (current/6.4-3)
:: hawknl: local (168-1) appears to be newer than repo (community/1.68-1)
:: nvidia: local (1.0.8762-1) appears to be newer than repo (extra/1.0.8178-16)
:: opera-devel: local (20060502.6-1) appears to be newer than repo (shadowhand/9.0b2-1)
:: vim: local (7.0-1) appears to be newer than repo (current/6.4-2)
:: Above packages will be skipped. To manually upgrade use 'pacman -S <pkg>'

Targets: gnome-common-2.12.0-4 gstreamer0.10-bad-0.10.3-1
gstreamer0.10-swfdec-0.10.3-1 libxfce4util-4.2.3.2-3

Total Package Size: 0.4 MB

Proceed with upgrade? [Y/n]

checking package integrity... done.
loading package data... load_pkg: missing package name in /var/cache/pacman/pkg/gnome-common-2.12.0-4.pkg.tar.gz.

this happened first with wine btw(sudo pacman -S wine), after i had removed .wine and winetools directories aswell as pacman -R wine, pacman -R winetools

maybe that means something...

sudo pacman -Scc doesn't work either..

After a reboot it worked? looks like you have filesystem corruption or so. About the suspicious processes you couldn't kill: those are kernel processes you can't kill.

yeah i'd think so too. The reason i knew it worked after a reebot is because iv'e had the problem once before. Hovewer if it was a fs corruption i would have seen it "fixing it" on bootup no? That means i should have seen it in dmesg; but i'm not.

kris|~$ dmesg|grep -4 XFS
hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 < hda5 hda6 hda7 >
ide-floppy driver 0.99.newide
SGI XFS with ACLs, security attributes, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem hda6
Ending clean XFS mount for filesystem: hda6
Freeing unused kernel memory: 244k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.3

If that were the case it also means atleast 1, probably 2 and possibly everyone of the above thread people also should have had such a corruption.

The reason I listed the [pdflush] entries is because i usually never have them, if I remember correctly then I had them the last time I had this problem as well.

Status in the latest Pacman3 RC?

It appears the original bug is related to filesystem corruption

EDIT: Ignore that - package validation is on -A/-U operations. Still, pacman does validate with md5sums, but there's really nothing we can do about filesystem corruption.

I think this is closable.