After every installation ldconfig runs (or something similar) [Solved]

Primoz · 2013-10-15 09:13:20

Sorry for a vague title, but I have no idea what's going on. Only thing I know is, that after I install, or remove any package, this is what I get at the end of it:

ldconfig: File /usr/lib/libnm-glib-vpn.so.1 is empty, not checked.
ldconfig: File /usr/lib/libpq.so is empty, not checked.
ldconfig: File /usr/lib/libv4lconvert.so.0 is empty, not checked.
ldconfig: File /usr/lib/libv4lconvert.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libnm-glib.so.4 is empty, not checked.
ldconfig: File /usr/lib/libv4l1.so.0 is empty, not checked.
ldconfig: File /usr/lib/libv4l2rds.so is empty, not checked.
ldconfig: File /usr/lib/libpq.so.5.6 is empty, not checked.
ldconfig: File /usr/lib/libpgtypes.so.3.4 is empty, not checked.
ldconfig: File /usr/lib/libnm-glib.so is empty, not checked.
ldconfig: File /usr/lib/libv4l2.so.0 is empty, not checked.
ldconfig: File /usr/lib/libnm-glib-vpn.so.1.1.0 is empty, not checked.
ldconfig: File /usr/lib/libecpg.so.6 is empty, not checked.
ldconfig: File /usr/lib/libv4l1.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libpgtypes.so.3 is empty, not checked.
ldconfig: File /usr/lib/libecpg_compat.so is empty, not checked.
ldconfig: File /usr/lib/libv4l2rds.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libnm-util.so is empty, not checked.
ldconfig: File /usr/lib/libnm-glib.so.4.6.0 is empty, not checked.
ldconfig: File /usr/lib/libpgtypes.so is empty, not checked.
ldconfig: File /usr/lib/libv4l2.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libv4l2rds.so.0 is empty, not checked.
ldconfig: File /usr/lib/libecpg.so.6.5 is empty, not checked.
ldconfig: File /usr/lib/libv4l2.so is empty, not checked.
ldconfig: File /usr/lib/libv4l1.so is empty, not checked.
ldconfig: File /usr/lib/libv4lconvert.so is empty, not checked.
ldconfig: File /usr/lib/libpq.so.5 is empty, not checked.
ldconfig: File /usr/lib/libecpg_compat.so.3 is empty, not checked.
ldconfig: File /usr/lib/libnm-glib-vpn.so is empty, not checked.
ldconfig: File /usr/lib/libecpg_compat.so.3.5 is empty, not checked.
ldconfig: File /usr/lib/libecpg.so is empty, not checked.
ldconfig: File /usr/lib/libnm-util.so.2.4.0 is empty, not checked.
ldconfig: File /usr/lib/libnm-util.so.2 is empty, not checked.
ldconfig: File /usr/lib32/libv4lconvert.so.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4lconvert.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l1.so.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l2rds.so is empty, not checked.
ldconfig: File /usr/lib32/libv4l2.so.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l1.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l2rds.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l2.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l2rds.so.0 is empty, not checked.
ldconfig: File /usr/lib32/libv4l2.so is empty, not checked.
ldconfig: File /usr/lib32/libv4l1.so is empty, not checked.
ldconfig: File /usr/lib32/libv4lconvert.so is empty, not checked.

Why am I getting this and how do I stop it?

Last edited by Primoz (2013-10-15 15:11:49)

falconindy · 2013-10-15 12:53:49

Primoz wrote:

Why am I getting this and how do I stop it?

Because of exactly what the error says -- those files are empty. You should be concerned about this and reinstall the packages those files belong to.

Primoz · 2013-10-15 14:44:25

I have no idea to which they belong to...
Well I found few of them, I think:

libnm-qt
libpqxx
v4l-utils
lib32-v4l-utils

The problem now being that after I installed libnm-qt and libpqxx I still get both of them on the list of missing libs.
But if I try to install v4l-utils and lib32-v4l-utils, I first get notification, that they're already installed and then this:

napaka: izvedba prenosa je spodletela(conflicting files)
v4l-utils: /usr/bin/cx18-ctl obstaja v podatkovnem sistemu (meaning: exsists in filesystetm)
v4l-utils: /usr/bin/decode_tm6000 obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/dvb-fe-tool obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/dvb-format-convert obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/dvbv5-scan obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/dvbv5-zap obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/ir-keytable obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/qv4l2 obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/rds-ctl obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/v4l2-compliance obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/v4l2-ctl obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/v4l2-dbg obstaja v podatkovnem sistemu
v4l-utils: /usr/bin/v4l2-sysfs-path obstaja v podatkovnem sistemu
v4l-utils: /usr/include/libv4l-plugin.h obstaja v podatkovnem sistemu
v4l-utils: /usr/include/libv4l1-videodev.h obstaja v podatkovnem sistemu
v4l-utils: /usr/include/libv4l1.h obstaja v podatkovnem sistemu
v4l-utils: /usr/include/libv4l2.h obstaja v podatkovnem sistemu
v4l-utils: /usr/include/libv4l2rds.h obstaja v podatkovnem sistemu
v4l-utils: /usr/include/libv4lconvert.h obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l/ov511-decomp obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l/ov518-decomp obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l/plugins/libv4l-mplane.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l/v4l1compat.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l/v4l2convert.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l1.a obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l1.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l1.so.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l1.so.0.0.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2.a obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2.so.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2.so.0.0.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2rds.a obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2rds.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2rds.so.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4l2rds.so.0.0.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4lconvert.a obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4lconvert.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4lconvert.so.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/libv4lconvert.so.0.0.0 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/pkgconfig/libv4l1.pc obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/pkgconfig/libv4l2.pc obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/pkgconfig/libv4l2rds.pc obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/pkgconfig/libv4lconvert.pc obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/a800 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/adstech_dvb_t_pci obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/af9005 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/alink_dtu_m obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/anysee obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/apac_viewcomp obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/asus_pc39 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/asus_ps3_100 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/ati_tv_wonder_hd_600 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/ati_x10 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia_a16d obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia_cardbus obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia_dvbt obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia_m135a obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia_m733a_rm_k6 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avermedia_rm_ks obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/avertv_303 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/azurewave_ad_tu700 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/behold obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/behold_columbus obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/budget_ci_old obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/cinergy obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/cinergy_1400 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/cinergyt2 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/d680_dmb obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/delock_61959 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dib0700_nec obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dib0700_rc5 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dibusb obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/digitalnow_tinytwin obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/digittrade obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/digitv obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dm1105_nec obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dntv_live_dvb_t obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dntv_live_dvbt_pro obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dtt200u obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dvico_mce obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dvico_portable obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/dw210x obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/em_terratec obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/encore_enltv obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/encore_enltv2 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/encore_enltv_fm53 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/evga_indtube obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/eztv obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/flydvb obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/flyvideo obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/fusionhdtv_mce obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/gadmei_rm008z obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/genius_tvgo_a11mce obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/gotview7135 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/haupp obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/hauppauge obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/imon_mce obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/imon_pad obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/iodata_bctv7e obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/it913x_v1 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/it913x_v2 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/kaiomy obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/kworld_315u obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/kworld_pc150u obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/kworld_plus_tv_analog obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/leadtek_y04g0051 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/lme2510 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/manli obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/medion_x10 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/medion_x10_digitainer obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/medion_x10_or2x obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/megasky obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/msi_digivox_ii obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/msi_digivox_iii obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/msi_tvanywhere obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/msi_tvanywhere_plus obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/nebula obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/nec_terratec_cinergy_xs obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/norwood obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/npgtech obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/opera1 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pctv_sedna obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pinnacle310e obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pinnacle_color obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pinnacle_grey obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pinnacle_pctv_hd obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pixelview obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pixelview_002t obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pixelview_mk12 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pixelview_new obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/powercolor_real_angel obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/proteus_2309 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/purpletv obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/pv951 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/rc6_mce obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/real_audio_220_32_keys obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/reddo obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/snapstream_firefly obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/streamzap obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/su3000 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tbs obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tbs_nec obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/technisat_usb2 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/terratec_cinergy_xs obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/terratec_slim obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/terratec_slim_2 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tevii obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tevii_nec obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tivo obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/total_media_in_hand obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/total_media_in_hand_02 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/trekstor obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tt_1500 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/tvwalkertwin obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/twinhan_vp1027_dvbs obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/videomate_k100 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/videomate_s350 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/videomate_tv_pvr obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/vp702x obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/vp7045 obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/winfast obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rc_keymaps/winfast_usbii_deluxe obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/udev/rules.d/70-infrared.rules obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/v4l1compat.so obstaja v podatkovnem sistemu
v4l-utils: /usr/lib/v4l2convert.so obstaja v podatkovnem sistemu
v4l-utils: /usr/share/applications/qv4l2.desktop obstaja v podatkovnem sistemu
v4l-utils: /usr/share/icons/hicolor/16x16/apps/qv4l2.png obstaja v podatkovnem sistemu
v4l-utils: /usr/share/icons/hicolor/24x24/apps/qv4l2.png obstaja v podatkovnem sistemu
v4l-utils: /usr/share/icons/hicolor/32x32/apps/qv4l2.png obstaja v podatkovnem sistemu
v4l-utils: /usr/share/icons/hicolor/64x64/apps/qv4l2.png obstaja v podatkovnem sistemu
v4l-utils: /usr/share/icons/hicolor/scalable/apps/qv4l2.svg obstaja v podatkovnem sistemu
v4l-utils: /usr/share/man/man1/ir-keytable.1.gz obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l/ov511-decomp obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l/ov518-decomp obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l/plugins/libv4l-mplane.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l/v4l1compat.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l/v4l2convert.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l1.a obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l1.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l1.so.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l1.so.0.0.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2.a obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2.so.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2.so.0.0.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2rds.a obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2rds.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2rds.so.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4l2rds.so.0.0.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4lconvert.a obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4lconvert.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4lconvert.so.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/libv4lconvert.so.0.0.0 obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/pkgconfig/libv4l1.pc obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/pkgconfig/libv4l2.pc obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/pkgconfig/libv4l2rds.pc obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/pkgconfig/libv4lconvert.pc obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/v4l1compat.so obstaja v podatkovnem sistemu
lib32-v4l-utils: /usr/lib32/v4l2convert.so obstaja v podatkovnem sistemu

falconindy · 2013-10-15 14:46:28

And obstaja v podatkovnem sistemu to you, too.

https://bbs.archlinux.org/viewtopic.php?id=130138

karol · 2013-10-15 14:47:53

Primoz. run

LC_ALL=C <command>

to get the output in English.

Primoz · 2013-10-15 15:16:27

Okay I found out which packages had those libs by first searching for libs in /usr/lib, where I found out, that all missing libs were last used 12.10.13, so I went to check pacman log and see which packages were installed that date and that time.
Those were: v4l-utils lib32-v4l-utils (as predicted), networkmanager and postgresql-libs

As I said before I got file existing in the filesystem. I knew that forcing to reinstall would do the trick, but I tried to do it with sudo pacman -Sf instead of sudo pacman -S --force, apparently -f option was removed.
Anyway now I don't get the error any more.

But to tell you the truth I have no idea why this happened in the first place. I probably used badly synced mirror or something.

Allan · 2013-10-15 15:23:43

Nope - probably a power down without the files being synced. Did you lose power during an upgrade?

Primoz · 2013-10-15 17:00:47

Allan wrote:

Nope - probably a power down without the files being synced. Did you lose power during an upgrade?

No, I didn't. But my computer is on a switch, and I do recall that I turned the switch off before it actually shut down (it was in process of shutting down). It was probably this.

Arch Linux

#1 2013-10-15 09:13:20

After every installation ldconfig runs (or something similar) [Solved]

#2 2013-10-15 12:53:49

Re: After every installation ldconfig runs (or something similar) [Solved]

#3 2013-10-15 14:44:25

Re: After every installation ldconfig runs (or something similar) [Solved]

#4 2013-10-15 14:46:28

Re: After every installation ldconfig runs (or something similar) [Solved]

#5 2013-10-15 14:47:53

Re: After every installation ldconfig runs (or something similar) [Solved]

#6 2013-10-15 15:16:27

Re: After every installation ldconfig runs (or something similar) [Solved]

#7 2013-10-15 15:23:43

Re: After every installation ldconfig runs (or something similar) [Solved]

#8 2013-10-15 17:00:47

Re: After every installation ldconfig runs (or something similar) [Solved]

Board footer