Arch Linux

djidji

Member

Registered: 2007-02-26

Posts: 57

[solved] problems with pacman after upgrading to 2.6.27-ARCH

i'm not sure if my problem is related with the new version of software or the fact that i ran out of space during the upgrade. but once i restarted after the upgrade i was not able to boot into the system and the error i would get was:

ERROR: Failed to parse block device name for '/dev/sda3'
unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.

i followed what some other people did and i booted with livecd, chrooted and regenerated mkinitcpio. since i saw some other people having the same problems here is what i used:
http://wiki.archlinux.org/index.php/Boo … omplicated
http://wiki.archlinux.org/index.php/Mki … ng_presets

and just for good measure i decided to run fsck:
http://wiki.archlinux.org/index.php/Fsck

i was still seeing some segmentation faults so i decided to re-install all of the packages installed:
http://wiki.archlinux.org/index.php/Pac … re_Restore

now everything seems to work OK except when i run pacman. here is what i get:

/sbin/ldconfig: /usr/lib/libgettextpo.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libwiretap.so.0.0.1 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libasprintf.so.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libasprintf.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libsigc-2.0.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libasprintf.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libwiretap.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libgettextpo.so.0.4.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libgettextsrc.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libsigc-2.0.so.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libgettextsrc-0.17.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libgettextpo.so.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libgettextlib-0.17.so is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libsigc-2.0.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libwiretap.so.0 is not an ELF file - it has the wrong magic bytes at the start.

/sbin/ldconfig: /usr/lib/libgettextlib.so is not an ELF file - it has the wrong magic bytes at the start.

packages are still installed but i would like to get to the bottom of this and get it fixed. any ideas what went wrong (well... besides me running out of disk space!) and how to get it fixed?

Last edited by djidji (2008-10-24 17:49:14)

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: [solved] problems with pacman after upgrading to 2.6.27-ARCH

Well, to cut it short: watch out not to run out of space... I know your pain -> http://bugs.archlinux.org/task/11639

Do this:
- paste the last part of /var/log/pacman.log, from the time when you started the upgrade
- run 'find /var/lib/pacman/local/ -name files -size 0' and paste the list

More to follow after that, this should be fixable.

Edit: oops, I read too fast -- you reinstalled? Ok, then all you have to do is to identify the packages those broken files belong to (pacman -Qo) and reinstall those.

Last edited by byte (2008-10-22 21:51:03)

---

1000

djidji

Member

Registered: 2007-02-26

Posts: 57

Re: [solved] problems with pacman after upgrading to 2.6.27-ARCH

thanks for the reply. i tried finding out what packages these libraries beling to but for every single one of these listed i get an error saying that "No packages owns...". could it be something with ldconfig?

EDIT:

so i figured out that one of the files was related to wireshark. i tried re-installing wireshark and here is what i got:

: sudo pacman -Sy wireshark                                                                                                                            
:: Synchronizing package databases...
 core                      31.4K  229.6K/s 00:00:00 [#############################################################################################] 100%
 extra                    413.1K  508.9K/s 00:00:01 [#############################################################################################] 100%
 community                356.3K  298.9K/s 00:00:01 [#############################################################################################] 100%
resolving dependencies...
looking for inter-conflicts...

Targets (1): wireshark-1.0.4-1  

Total Download Size:    11.89 MB
Total Installed Size:   51.80 MB

Proceed with installation? [Y/n] 
:: Retrieving packages from extra...
 wireshark-1.0.4-1-i686    11.9M  455.5K/s 00:00:27 [#############################################################################################] 100%
checking package integrity...
(1/1) checking for file conflicts                   [#############################################################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
wireshark: /usr/bin/capinfos exists in filesystem
wireshark: /usr/bin/dftest exists in filesystem
wireshark: /usr/bin/dumpcap exists in filesystem
wireshark: /usr/bin/editcap exists in filesystem
wireshark: /usr/bin/idl2wrs exists in filesystem
wireshark: /usr/bin/mergecap exists in filesystem
wireshark: /usr/bin/randpkt exists in filesystem
wireshark: /usr/bin/rawshark exists in filesystem
wireshark: /usr/bin/text2pcap exists in filesystem
wireshark: /usr/bin/tshark exists in filesystem
wireshark: /usr/bin/wireshark exists in filesystem
wireshark: /usr/lib/libwireshark.so exists in filesystem
wireshark: /usr/lib/libwireshark.so.0 exists in filesystem
wireshark: /usr/lib/libwireshark.so.0.0.1 exists in filesystem
wireshark: /usr/lib/libwiretap.so exists in filesystem
wireshark: /usr/lib/libwiretap.so.0 exists in filesystem
wireshark: /usr/lib/libwiretap.so.0.0.1 exists in filesystem
wireshark: /usr/share/man/man1/capinfos.1 exists in filesystem
wireshark: /usr/share/man/man1/dumpcap.1 exists in filesystem
wireshark: /usr/share/man/man1/editcap.1 exists in filesystem
wireshark: /usr/share/man/man1/idl2wrs.1 exists in filesystem
wireshark: /usr/share/man/man1/mergecap.1 exists in filesystem
wireshark: /usr/share/man/man1/rawshark.1 exists in filesystem
wireshark: /usr/share/man/man1/text2pcap.1 exists in filesystem
wireshark: /usr/share/man/man1/tshark.1 exists in filesystem
wireshark: /usr/share/man/man1/wireshark.1 exists in filesystem
wireshark: /usr/share/man/man4/wireshark-filter.4 exists in filesystem
wireshark: /usr/share/wireshark/AUTHORS-SHORT exists in filesystem
wireshark: /usr/share/wireshark/COPYING exists in filesystem
wireshark: /usr/share/wireshark/capinfos.html exists in filesystem
wireshark: /usr/share/wireshark/cfilters exists in filesystem
wireshark: /usr/share/wireshark/colorfilters exists in filesystem
wireshark: /usr/share/wireshark/dfilters exists in filesystem
wireshark: /usr/share/wireshark/diameter/Ericsson.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/TGPPGmb.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/TGPPSh.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/chargecontrol.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/dictionary.dtd exists in filesystem
wireshark: /usr/share/wireshark/diameter/dictionary.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/etsie2e4.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/gqpolicy.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/imscxdx.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/mobileipv4.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/nasreq.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/sip.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/sunping.xml exists in filesystem
wireshark: /usr/share/wireshark/dtds/dc.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/itunes.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/mscml.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/pocsettings.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/presence.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/reginfo.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/rlmi.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/rss.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/smil.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/watcherinfo.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/xcap-caps.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/xcap-error.dtd exists in filesystem
wireshark: /usr/share/wireshark/dumpcap.html exists in filesystem
wireshark: /usr/share/wireshark/editcap.html exists in filesystem
wireshark: /usr/share/wireshark/help/capture_filters.txt exists in filesystem
wireshark: /usr/share/wireshark/help/capturing.txt exists in filesystem
wireshark: /usr/share/wireshark/help/display_filters.txt exists in filesystem
wireshark: /usr/share/wireshark/help/faq.txt exists in filesystem
wireshark: /usr/share/wireshark/help/getting_started.txt exists in filesystem
wireshark: /usr/share/wireshark/help/overview.txt exists in filesystem
wireshark: /usr/share/wireshark/help/toc exists in filesystem
wireshark: /usr/share/wireshark/idl2wrs.html exists in filesystem
wireshark: /usr/share/wireshark/manuf exists in filesystem
wireshark: /usr/share/wireshark/mergecap.html exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.3com exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.3gpp exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.3gpp2 exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.acc exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.alcatel exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.alteon exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.altiga exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.aptis exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.ascend exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.bay exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.bintec exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.bristol exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cablelabs exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cabletron exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco.bbsm exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco.vpn3000 exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco.vpn5000 exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.colubris exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.columbia_university exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.compat exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cosine exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.ericsson exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.erx exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.extreme exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.foundry exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.freeradius exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.gandalf exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.garderos exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.gemtek exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.itk exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.juniper exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.karlnet exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.livingston exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.localweb exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.merit exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.microsoft exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.mikrotik exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.navini exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.netscreen exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.nokia exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.nomadix exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.propel exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.quintum exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.redback exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.redcreek exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.shasta exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.shiva exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.sonicwall exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.springtide exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.t_systems_nova exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.telebit exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.trapeze exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.tunnel exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.unisphere exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.unix exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.usr exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.valemount exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.versanet exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.wispr exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.xedia exists in filesystem
wireshark: /usr/share/wireshark/rawshark.html exists in filesystem
wireshark: /usr/share/wireshark/services exists in filesystem
wireshark: /usr/share/wireshark/smi_modules exists in filesystem
wireshark: /usr/share/wireshark/text2pcap.html exists in filesystem
wireshark: /usr/share/wireshark/tpncp/tpncp.dat exists in filesystem
wireshark: /usr/share/wireshark/tshark.html exists in filesystem
wireshark: /usr/share/wireshark/wimaxasncp/dictionary.dtd exists in filesystem
wireshark: /usr/share/wireshark/wimaxasncp/dictionary.xml exists in filesystem
wireshark: /usr/share/wireshark/wireshark-filter.html exists in filesystem
wireshark: /usr/share/wireshark/wireshark.html exists in filesystem
wireshark: /usr/share/wireshark/ws.css exists in filesystem
Errors occurred, no packages were upgraded.

i'm hoping there is a way to sort this out. i'm loving the way my laptop is set up and would have re-install everything...

Last edited by djidji (2008-10-24 01:27:00)

djidji

Member

Registered: 2007-02-26

Posts: 57

Re: [solved] problems with pacman after upgrading to 2.6.27-ARCH

Ok... last update... i forced install of wireshark, gettext and gtkmm and now i get no errors or warnings. i'm hoping this is the end of this project.... oh yeah, and i moved pacman cache to a different location :-)