Package file invalid when installing on Motorola Razr i
I have tried several times to install the app on my Razr i but it always says that the package file is invalid
Hi Ignacio!
Same problem, on same phone!
The Motorola Razr I has Intel Medfield X86 architecture. Different architecture of ARM Processor
Motorola Razr i - XT-890 (Android 4.0.4 or 4.1.2) is sold on Europe and Latam
Thanks,
Thiago
Similar Messages
-
Error message: Package contains invalid characters installing patchlevel 6
Dear experts:
I have successfullly installed SAP GUI 7.20 compilation 2, using SAP installation server (40 machines, Windows XP sp3 32 bits, latest updates).
I have successfully installed patchlevel 6 in the SAP installation server. (gui720_6-10007878.exe, downloaded from SAP Portal)
SAP GUI is configured to search for updates after 5 double-clicks on desktop icon. I forced the 5 double-clicks on a test machine and the patch begins to install; then informs me that there is a pending reboot.
When I reboot the machine a SAP Netweaver Front-end installer window appears with the error: "/Package contains invalid characters like /*?"<>\" - "Your system has a pending reboot". If I reboot again the message is displayed again.
If I click on the "Cancel" button of this window, Windows XP continues booting and SAP GUI works fine.
Two questions:
How can I avoid the installation of this patch on all the machines?
What can be wrong?
Thank you very much.
Mr.Clinker
Uruguay - South America.1.) To avoid the installation on all clients simply go to "Services -> Configure Automatic Workstation Update Service" in the SAP Installation Server Administration Tool and disbale the service. If this doesnt work you can delete the package on the installation server an create a new one with the same name. You can than patch the package to the patchlevel you want.
2.) Try to apply patch 6 Hotfix 2 and see if the problem remains. -
N97 file corrupted when installing files
My N97 was working well untill yesterday when I tried to download something from ovi store. It asked if I wanted to install the newest version of the store which I tried to do but it keeps saying 'file corrupted' and cancels the installation.
This message is coming up with every file I try installing now, either by downloading it from the older version of ovi store, or by installing through ovi suite.
I've also noticed Ovi Maps no longer loads if you try starting it up. It does nothing!
I tried installing the newest version of Ovi Suite, but its asking to install sms ds plugin 1.14 to my phone which then says file corrupted.
Anyone have a solution, or have I got to do a full reset of the phone? (Hopefully I can still get a backup with ovi suite)i have the same problem and it's been bothering me for a while now, how can i solve it ?
-
Conflicting files problem when installing wine
Hi,
I'm trying to install wine, but get the following errors.
# pacman -S wine
resolving dependencies...
:: There are 3 providers available for lib32-libgl:
:: Repository multilib
1) lib32-mesa-libgl 2) lib32-nvidia-304xx-libgl 3) lib32-nvidia-libgl
Enter a number (default=1):
warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2 dependency
looking for inter-conflicts...
Packages (46): lib32-acl-2.2.52-2 lib32-attr-2.4.47-1 lib32-bzip2-1.0.6-2 lib32-elfutils-0.159-1 lib32-expat-2.1.0-2 lib32-fontconfig-2.11.1-1 lib32-freetype2-2.5.3-1 lib32-gcc-libs-4.9.1-1
lib32-gettext-0.19.2-1 lib32-glib2-2.40.0-1 lib32-glibc-2.19-5 lib32-glu-9.0.0-2 lib32-harfbuzz-0.9.32-1 lib32-icu-53.1-1 lib32-libdbus-1.8.6-1 lib32-libdrm-2.4.56-1
lib32-libffi-3.1-1 lib32-libgcrypt-1.6.1-1 lib32-libgpg-error-1.13-1 lib32-libice-1.0.9-1 lib32-libpciaccess-0.13.2-1 lib32-libpng-1.6.12-1 lib32-libsm-1.2.2-1 lib32-libx11-1.6.2-1
lib32-libxau-1.0.8-1 lib32-libxcb-1.11-1 lib32-libxcursor-1.1.14-1 lib32-libxdamage-1.1.4-2 lib32-libxdmcp-1.1.1-2 lib32-libxext-1.3.3-1 lib32-libxfixes-5.0.1-1 lib32-libxi-1.7.4-1
lib32-libxrandr-1.4.2-1 lib32-libxrender-0.9.8-1 lib32-libxshmfence-1.1-1 lib32-libxxf86vm-1.1.3-1 lib32-llvm-libs-3.4.2-1 lib32-mesa-10.2.5-1 lib32-mesa-libgl-10.2.5-1
lib32-pcre-8.35-1 lib32-systemd-215-1 lib32-util-linux-2.25-1 lib32-wayland-1.5.0-1 lib32-xz-5.0.5-1 lib32-zlib-1.2.8-1 wine-1.7.24-1
Total Installed Size: 387.40 MiB
:: Proceed with installation? [Y/n]
(46/46) checking keys in keyring [###########################################################################] 100%
(46/46) checking package integrity [###########################################################################] 100%
(46/46) loading package files [###########################################################################] 100%
(46/46) checking for file conflicts [###########################################################################] 100%
error: failed to commit transaction (conflicting files)
lib32-glibc: /usr/lib/Mcrt1.o exists in filesystem
lib32-glibc: /usr/lib/Scrt1.o exists in filesystem
lib32-glibc: /usr/lib/audit/sotruss-lib.so exists in filesystem
lib32-glibc: /usr/lib/crt1.o exists in filesystem
lib32-glibc: /usr/lib/crti.o exists in filesystem
lib32-glibc: /usr/lib/crtn.o exists in filesystem
lib32-glibc: /usr/lib/gconv/ANSI_X3.110.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ARMSCII-8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ASMO_449.so exists in filesystem
lib32-glibc: /usr/lib/gconv/BIG5.so exists in filesystem
lib32-glibc: /usr/lib/gconv/BIG5HKSCS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/BRF.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP10007.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1125.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1250.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1251.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1252.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1253.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1254.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1255.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1256.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1257.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP1258.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP737.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP770.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP771.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP772.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP773.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP774.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP775.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CP932.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CSN_369103.so exists in filesystem
lib32-glibc: /usr/lib/gconv/CWI.so exists in filesystem
lib32-glibc: /usr/lib/gconv/DEC-MCS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-AT-DE-A.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-AT-DE.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-CA-FR.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-DK-NO-A.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-DK-NO.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-ES-A.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-ES-S.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-ES.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-FI-SE-A.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-FI-SE.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-FR.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-IS-FRISS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-IT.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-PT.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-UK.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EBCDIC-US.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ECMA-CYRILLIC.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EUC-CN.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EUC-JISX0213.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EUC-JP-MS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EUC-JP.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EUC-KR.so exists in filesystem
lib32-glibc: /usr/lib/gconv/EUC-TW.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GB18030.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GBBIG5.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GBGBK.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GBK.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GEORGIAN-ACADEMY.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GEORGIAN-PS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GOST_19768-74.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GREEK-CCITT.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GREEK7-OLD.so exists in filesystem
lib32-glibc: /usr/lib/gconv/GREEK7.so exists in filesystem
lib32-glibc: /usr/lib/gconv/HP-GREEK8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/HP-ROMAN8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/HP-ROMAN9.so exists in filesystem
lib32-glibc: /usr/lib/gconv/HP-THAI8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/HP-TURKISH8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM037.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM038.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1004.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1008.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1008_420.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1025.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1026.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1046.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1047.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1097.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1112.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1122.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1123.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1124.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1129.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1130.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1132.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1133.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1137.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1140.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1141.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1142.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1143.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1144.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1145.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1146.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1147.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1148.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1149.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1153.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1154.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1155.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1156.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1157.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1158.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1160.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1161.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1162.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1163.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1164.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1166.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1167.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM12712.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1364.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1371.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1388.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1390.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM1399.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM16804.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM256.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM273.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM274.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM275.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM277.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM278.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM280.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM281.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM284.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM285.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM290.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM297.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM420.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM423.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM424.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM437.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM4517.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM4899.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM4909.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM4971.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM500.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM5347.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM803.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM850.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM851.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM852.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM855.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM856.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM857.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM860.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM861.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM862.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM863.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM864.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM865.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM866.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM866NAV.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM868.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM869.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM870.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM871.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM874.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM875.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM880.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM891.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM901.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM902.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM903.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM9030.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM904.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM905.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM9066.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM918.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM921.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM922.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM930.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM932.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM933.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM935.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM937.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM939.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM943.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IBM9448.so exists in filesystem
lib32-glibc: /usr/lib/gconv/IEC_P27-1.so exists in filesystem
lib32-glibc: /usr/lib/gconv/INIS-8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/INIS-CYRILLIC.so exists in filesystem
lib32-glibc: /usr/lib/gconv/INIS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISIRI-3342.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-2022-CN-EXT.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-2022-CN.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-2022-JP-3.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-2022-JP.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-2022-KR.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-IR-197.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO-IR-209.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO646.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-1.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-10.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-11.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-13.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-14.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-15.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-16.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-2.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-3.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-4.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-5.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-6.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-7.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-9.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO8859-9E.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_10367-BOX.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_11548-1.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_2033.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_5427-EXT.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_5427.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_5428.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_6937-2.so exists in filesystem
lib32-glibc: /usr/lib/gconv/ISO_6937.so exists in filesystem
lib32-glibc: /usr/lib/gconv/JOHAB.so exists in filesystem
lib32-glibc: /usr/lib/gconv/KOI-8.so exists in filesystem
lib32-glibc: /usr/lib/gconv/KOI8-R.so exists in filesystem
lib32-glibc: /usr/lib/gconv/KOI8-RU.so exists in filesystem
lib32-glibc: /usr/lib/gconv/KOI8-T.so exists in filesystem
lib32-glibc: /usr/lib/gconv/KOI8-U.so exists in filesystem
lib32-glibc: /usr/lib/gconv/LATIN-GREEK-1.so exists in filesystem
lib32-glibc: /usr/lib/gconv/LATIN-GREEK.so exists in filesystem
lib32-glibc: /usr/lib/gconv/MAC-CENTRALEUROPE.so exists in filesystem
lib32-glibc: /usr/lib/gconv/MAC-IS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/MAC-SAMI.so exists in filesystem
lib32-glibc: /usr/lib/gconv/MAC-UK.so exists in filesystem
lib32-glibc: /usr/lib/gconv/MACINTOSH.so exists in filesystem
lib32-glibc: /usr/lib/gconv/MIK.so exists in filesystem
lib32-glibc: /usr/lib/gconv/NATS-DANO.so exists in filesystem
lib32-glibc: /usr/lib/gconv/NATS-SEFI.so exists in filesystem
lib32-glibc: /usr/lib/gconv/PT154.so exists in filesystem
lib32-glibc: /usr/lib/gconv/RK1048.so exists in filesystem
lib32-glibc: /usr/lib/gconv/SAMI-WS2.so exists in filesystem
lib32-glibc: /usr/lib/gconv/SHIFT_JISX0213.so exists in filesystem
lib32-glibc: /usr/lib/gconv/SJIS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/T.61.so exists in filesystem
lib32-glibc: /usr/lib/gconv/TCVN5712-1.so exists in filesystem
lib32-glibc: /usr/lib/gconv/TIS-620.so exists in filesystem
lib32-glibc: /usr/lib/gconv/TSCII.so exists in filesystem
lib32-glibc: /usr/lib/gconv/UHC.so exists in filesystem
lib32-glibc: /usr/lib/gconv/UNICODE.so exists in filesystem
lib32-glibc: /usr/lib/gconv/UTF-16.so exists in filesystem
lib32-glibc: /usr/lib/gconv/UTF-32.so exists in filesystem
lib32-glibc: /usr/lib/gconv/UTF-7.so exists in filesystem
lib32-glibc: /usr/lib/gconv/VISCII.so exists in filesystem
lib32-glibc: /usr/lib/gconv/gconv-modules exists in filesystem
lib32-glibc: /usr/lib/gconv/libCNS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/libGB.so exists in filesystem
lib32-glibc: /usr/lib/gconv/libISOIR165.so exists in filesystem
lib32-glibc: /usr/lib/gconv/libJIS.so exists in filesystem
lib32-glibc: /usr/lib/gconv/libJISX0213.so exists in filesystem
lib32-glibc: /usr/lib/gconv/libKSC.so exists in filesystem
lib32-glibc: /usr/lib/gcrt1.o exists in filesystem
lib32-glibc: /usr/lib/ld-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libBrokenLocale-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libBrokenLocale.so exists in filesystem
lib32-glibc: /usr/lib/libBrokenLocale.so.1 exists in filesystem
lib32-glibc: /usr/lib/libSegFault.so exists in filesystem
lib32-glibc: /usr/lib/libanl-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libanl.so exists in filesystem
lib32-glibc: /usr/lib/libanl.so.1 exists in filesystem
lib32-glibc: /usr/lib/libc-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libc.a exists in filesystem
lib32-glibc: /usr/lib/libc.so exists in filesystem
lib32-glibc: /usr/lib/libc.so.6 exists in filesystem
lib32-glibc: /usr/lib/libc_nonshared.a exists in filesystem
lib32-glibc: /usr/lib/libcidn-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libcidn.so exists in filesystem
lib32-glibc: /usr/lib/libcidn.so.1 exists in filesystem
lib32-glibc: /usr/lib/libcrypt-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libcrypt.a exists in filesystem
lib32-glibc: /usr/lib/libcrypt.so exists in filesystem
lib32-glibc: /usr/lib/libcrypt.so.1 exists in filesystem
lib32-glibc: /usr/lib/libdl-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libdl.a exists in filesystem
lib32-glibc: /usr/lib/libdl.so exists in filesystem
lib32-glibc: /usr/lib/libdl.so.2 exists in filesystem
lib32-glibc: /usr/lib/libg.a exists in filesystem
lib32-glibc: /usr/lib/libieee.a exists in filesystem
lib32-glibc: /usr/lib/libm-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libm.a exists in filesystem
lib32-glibc: /usr/lib/libm.so exists in filesystem
lib32-glibc: /usr/lib/libm.so.6 exists in filesystem
lib32-glibc: /usr/lib/libmcheck.a exists in filesystem
lib32-glibc: /usr/lib/libmemusage.so exists in filesystem
lib32-glibc: /usr/lib/libnsl-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnsl.so exists in filesystem
lib32-glibc: /usr/lib/libnsl.so.1 exists in filesystem
lib32-glibc: /usr/lib/libnss_compat-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_compat.so exists in filesystem
lib32-glibc: /usr/lib/libnss_compat.so.2 exists in filesystem
lib32-glibc: /usr/lib/libnss_db-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_db.so exists in filesystem
lib32-glibc: /usr/lib/libnss_db.so.2 exists in filesystem
lib32-glibc: /usr/lib/libnss_dns-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_dns.so exists in filesystem
lib32-glibc: /usr/lib/libnss_dns.so.2 exists in filesystem
lib32-glibc: /usr/lib/libnss_files-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_files.so exists in filesystem
lib32-glibc: /usr/lib/libnss_files.so.2 exists in filesystem
lib32-glibc: /usr/lib/libnss_hesiod-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_hesiod.so exists in filesystem
lib32-glibc: /usr/lib/libnss_hesiod.so.2 exists in filesystem
lib32-glibc: /usr/lib/libnss_nis-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_nis.so exists in filesystem
lib32-glibc: /usr/lib/libnss_nis.so.2 exists in filesystem
lib32-glibc: /usr/lib/libnss_nisplus-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libnss_nisplus.so exists in filesystem
lib32-glibc: /usr/lib/libnss_nisplus.so.2 exists in filesystem
lib32-glibc: /usr/lib/libpcprofile.so exists in filesystem
lib32-glibc: /usr/lib/libpthread-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libpthread.a exists in filesystem
lib32-glibc: /usr/lib/libpthread.so exists in filesystem
lib32-glibc: /usr/lib/libpthread.so.0 exists in filesystem
lib32-glibc: /usr/lib/libpthread_nonshared.a exists in filesystem
lib32-glibc: /usr/lib/libresolv-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libresolv.so exists in filesystem
lib32-glibc: /usr/lib/libresolv.so.2 exists in filesystem
lib32-glibc: /usr/lib/librpcsvc.a exists in filesystem
lib32-glibc: /usr/lib/librt-2.19.so exists in filesystem
lib32-glibc: /usr/lib/librt.so exists in filesystem
lib32-glibc: /usr/lib/librt.so.1 exists in filesystem
lib32-glibc: /usr/lib/libthread_db-1.0.so exists in filesystem
lib32-glibc: /usr/lib/libthread_db.so exists in filesystem
lib32-glibc: /usr/lib/libthread_db.so.1 exists in filesystem
lib32-glibc: /usr/lib/libutil-2.19.so exists in filesystem
lib32-glibc: /usr/lib/libutil.so exists in filesystem
lib32-glibc: /usr/lib/libutil.so.1 exists in filesystem
lib32-glibc: /usr/lib/locale exists in filesystem
lib32-expat: /usr/lib/libexpat.so exists in filesystem
lib32-expat: /usr/lib/libexpat.so.1 exists in filesystem
lib32-expat: /usr/lib/libexpat.so.1.6.0 exists in filesystem
lib32-expat: /usr/lib/pkgconfig/expat.pc exists in filesystem
lib32-zlib: /usr/lib/libz.a exists in filesystem
lib32-zlib: /usr/lib/libz.so exists in filesystem
lib32-zlib: /usr/lib/libz.so.1 exists in filesystem
lib32-zlib: /usr/lib/libz.so.1.2.8 exists in filesystem
lib32-zlib: /usr/lib/pkgconfig/zlib.pc exists in filesystem
lib32-bzip2: /usr/lib/libbz2.so exists in filesystem
lib32-bzip2: /usr/lib/libbz2.so.1 exists in filesystem
lib32-bzip2: /usr/lib/libbz2.so.1.0 exists in filesystem
lib32-bzip2: /usr/lib/libbz2.so.1.0.6 exists in filesystem
lib32-libpng: /usr/lib/libpng.so exists in filesystem
lib32-libpng: /usr/lib/libpng16.so exists in filesystem
lib32-libpng: /usr/lib/libpng16.so.16 exists in filesystem
lib32-libpng: /usr/lib/pkgconfig/libpng.pc exists in filesystem
lib32-libpng: /usr/lib/pkgconfig/libpng16.pc exists in filesystem
lib32-gcc-libs: /usr/lib/libasan.so exists in filesystem
lib32-gcc-libs: /usr/lib/libasan.so.1 exists in filesystem
lib32-gcc-libs: /usr/lib/libasan.so.1.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libatomic.so exists in filesystem
lib32-gcc-libs: /usr/lib/libatomic.so.1 exists in filesystem
lib32-gcc-libs: /usr/lib/libatomic.so.1.1.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libcilkrts.so exists in filesystem
lib32-gcc-libs: /usr/lib/libcilkrts.so.5 exists in filesystem
lib32-gcc-libs: /usr/lib/libcilkrts.so.5.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libgcc_s.so exists in filesystem
lib32-gcc-libs: /usr/lib/libgcc_s.so.1 exists in filesystem
lib32-gcc-libs: /usr/lib/libgfortran.so exists in filesystem
lib32-gcc-libs: /usr/lib/libgfortran.so.3 exists in filesystem
lib32-gcc-libs: /usr/lib/libgfortran.so.3.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libgomp.so exists in filesystem
lib32-gcc-libs: /usr/lib/libgomp.so.1 exists in filesystem
lib32-gcc-libs: /usr/lib/libgomp.so.1.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libitm.so exists in filesystem
lib32-gcc-libs: /usr/lib/libitm.so.1 exists in filesystem
lib32-gcc-libs: /usr/lib/libitm.so.1.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libobjc.so exists in filesystem
lib32-gcc-libs: /usr/lib/libobjc.so.4 exists in filesystem
lib32-gcc-libs: /usr/lib/libobjc.so.4.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libquadmath.so exists in filesystem
lib32-gcc-libs: /usr/lib/libquadmath.so.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libquadmath.so.0.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libstdc++.so exists in filesystem
lib32-gcc-libs: /usr/lib/libstdc++.so.6 exists in filesystem
lib32-gcc-libs: /usr/lib/libstdc++.so.6.0.20 exists in filesystem
lib32-gcc-libs: /usr/lib/libubsan.so exists in filesystem
lib32-gcc-libs: /usr/lib/libubsan.so.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libubsan.so.0.0.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libvtv.so exists in filesystem
lib32-gcc-libs: /usr/lib/libvtv.so.0 exists in filesystem
lib32-gcc-libs: /usr/lib/libvtv.so.0.0.0 exists in filesystem
lib32-icu: /usr/lib/icu/53.1/Makefile.inc exists in filesystem
lib32-icu: /usr/lib/icu/53.1/pkgdata.inc exists in filesystem
lib32-icu: /usr/lib/icu/Makefile.inc exists in filesystem
lib32-icu: /usr/lib/icu/current exists in filesystem
lib32-icu: /usr/lib/icu/pkgdata.inc exists in filesystem
lib32-icu: /usr/lib/libicudata.so exists in filesystem
lib32-icu: /usr/lib/libicudata.so.53 exists in filesystem
lib32-icu: /usr/lib/libicudata.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libicui18n.so exists in filesystem
lib32-icu: /usr/lib/libicui18n.so.53 exists in filesystem
lib32-icu: /usr/lib/libicui18n.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libicuio.so exists in filesystem
lib32-icu: /usr/lib/libicuio.so.53 exists in filesystem
lib32-icu: /usr/lib/libicuio.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libicule.so exists in filesystem
lib32-icu: /usr/lib/libicule.so.53 exists in filesystem
lib32-icu: /usr/lib/libicule.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libiculx.so exists in filesystem
lib32-icu: /usr/lib/libiculx.so.53 exists in filesystem
lib32-icu: /usr/lib/libiculx.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libicutest.so exists in filesystem
lib32-icu: /usr/lib/libicutest.so.53 exists in filesystem
lib32-icu: /usr/lib/libicutest.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libicutu.so exists in filesystem
lib32-icu: /usr/lib/libicutu.so.53 exists in filesystem
lib32-icu: /usr/lib/libicutu.so.53.1 exists in filesystem
lib32-icu: /usr/lib/libicuuc.so exists in filesystem
lib32-icu: /usr/lib/libicuuc.so.53 exists in filesystem
lib32-icu: /usr/lib/libicuuc.so.53.1 exists in filesystem
lib32-icu: /usr/lib/pkgconfig/icu-i18n.pc exists in filesystem
lib32-icu: /usr/lib/pkgconfig/icu-io.pc exists in filesystem
lib32-icu: /usr/lib/pkgconfig/icu-le.pc exists in filesystem
lib32-icu: /usr/lib/pkgconfig/icu-lx.pc exists in filesystem
lib32-icu: /usr/lib/pkgconfig/icu-uc.pc exists in filesystem
lib32-pcre: /usr/lib/libpcre.so exists in filesystem
lib32-pcre: /usr/lib/libpcre.so.1 exists in filesystem
lib32-pcre: /usr/lib/libpcre.so.1.2.3 exists in filesystem
lib32-pcre: /usr/lib/libpcre16.so exists in filesystem
lib32-pcre: /usr/lib/libpcre16.so.0 exists in filesystem
lib32-pcre: /usr/lib/libpcre16.so.0.2.3 exists in filesystem
lib32-pcre: /usr/lib/libpcre32.so exists in filesystem
lib32-pcre: /usr/lib/libpcre32.so.0 exists in filesystem
lib32-pcre: /usr/lib/libpcre32.so.0.0.3 exists in filesystem
lib32-pcre: /usr/lib/libpcrecpp.so exists in filesystem
lib32-pcre: /usr/lib/libpcrecpp.so.0 exists in filesystem
lib32-pcre: /usr/lib/libpcrecpp.so.0.0.0 exists in filesystem
lib32-pcre: /usr/lib/libpcreposix.so exists in filesystem
lib32-pcre: /usr/lib/libpcreposix.so.0 exists in filesystem
lib32-pcre: /usr/lib/libpcreposix.so.0.0.2 exists in filesystem
lib32-pcre: /usr/lib/pkgconfig/libpcre.pc exists in filesystem
lib32-pcre: /usr/lib/pkgconfig/libpcre16.pc exists in filesystem
lib32-pcre: /usr/lib/pkgconfig/libpcre32.pc exists in filesystem
lib32-pcre: /usr/lib/pkgconfig/libpcrecpp.pc exists in filesystem
lib32-pcre: /usr/lib/pkgconfig/libpcreposix.pc exists in filesystem
lib32-libdbus: /usr/lib/dbus-1.0/include/dbus/dbus-arch-deps.h exists in filesystem
lib32-libdbus: /usr/lib/libdbus-1.so exists in filesystem
lib32-libdbus: /usr/lib/libdbus-1.so.3 exists in filesystem
lib32-libdbus: /usr/lib/pkgconfig/dbus-1.pc exists in filesystem
lib32-libffi: /usr/lib/libffi-3.1/include/ffi.h exists in filesystem
lib32-libffi: /usr/lib/libffi-3.1/include/ffitarget.h exists in filesystem
lib32-libffi: /usr/lib/libffi.so exists in filesystem
lib32-libffi: /usr/lib/libffi.so.6 exists in filesystem
lib32-libffi: /usr/lib/libffi.so.6.0.2 exists in filesystem
lib32-libffi: /usr/lib/pkgconfig/libffi.pc exists in filesystem
lib32-glib2: /usr/lib/glib-2.0/include/glibconfig.h exists in filesystem
lib32-glib2: /usr/lib/libgio-2.0.so exists in filesystem
lib32-glib2: /usr/lib/libgio-2.0.so.0 exists in filesystem
lib32-glib2: /usr/lib/libgio-2.0.so.0.4000.0 exists in filesystem
lib32-glib2: /usr/lib/libglib-2.0.so exists in filesystem
lib32-glib2: /usr/lib/libglib-2.0.so.0 exists in filesystem
lib32-glib2: /usr/lib/libglib-2.0.so.0.4000.0 exists in filesystem
lib32-glib2: /usr/lib/libgmodule-2.0.so exists in filesystem
lib32-glib2: /usr/lib/libgmodule-2.0.so.0 exists in filesystem
lib32-glib2: /usr/lib/libgmodule-2.0.so.0.4000.0 exists in filesystem
lib32-glib2: /usr/lib/libgobject-2.0.so exists in filesystem
lib32-glib2: /usr/lib/libgobject-2.0.so.0 exists in filesystem
lib32-glib2: /usr/lib/libgobject-2.0.so.0.4000.0 exists in filesystem
lib32-glib2: /usr/lib/libgthread-2.0.so exists in filesystem
lib32-glib2: /usr/lib/libgthread-2.0.so.0 exists in filesystem
lib32-glib2: /usr/lib/libgthread-2.0.so.0.4000.0 exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gio-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gio-unix-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/glib-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gmodule-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gmodule-export-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gmodule-no-export-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gobject-2.0.pc exists in filesystem
lib32-glib2: /usr/lib/pkgconfig/gthread-2.0.pc exists in filesystem
lib32-harfbuzz: /usr/lib/libharfbuzz-icu.so exists in filesystem
lib32-harfbuzz: /usr/lib/libharfbuzz-icu.so.0 exists in filesystem
lib32-harfbuzz: /usr/lib/libharfbuzz.so exists in filesystem
lib32-harfbuzz: /usr/lib/libharfbuzz.so.0 exists in filesystem
lib32-harfbuzz: /usr/lib/pkgconfig/harfbuzz-icu.pc exists in filesystem
lib32-harfbuzz: /usr/lib/pkgconfig/harfbuzz.pc exists in filesystem
lib32-freetype2: /usr/lib/libfreetype.so exists in filesystem
lib32-freetype2: /usr/lib/libfreetype.so.6 exists in filesystem
lib32-freetype2: /usr/lib/libfreetype.so.6.11.2 exists in filesystem
lib32-freetype2: /usr/lib/pkgconfig/freetype2.pc exists in filesystem
lib32-fontconfig: /usr/lib/libfontconfig.so exists in filesystem
lib32-fontconfig: /usr/lib/libfontconfig.so.1 exists in filesystem
lib32-fontconfig: /usr/lib/libfontconfig.so.1.8.0 exists in filesystem
lib32-fontconfig: /usr/lib/pkgconfig/fontconfig.pc exists in filesystem
lib32-libxdmcp: /usr/lib/libXdmcp.so exists in filesystem
lib32-libxdmcp: /usr/lib/libXdmcp.so.6 exists in filesystem
lib32-libxdmcp: /usr/lib/libXdmcp.so.6.0.0 exists in filesystem
lib32-libxdmcp: /usr/lib/pkgconfig/xdmcp.pc exists in filesystem
lib32-libxau: /usr/lib/libXau.so exists in filesystem
lib32-libxau: /usr/lib/libXau.so.6 exists in filesystem
lib32-libxau: /usr/lib/libXau.so.6.0.0 exists in filesystem
lib32-libxau: /usr/lib/pkgconfig/xau.pc exists in filesystem
lib32-libxcb: /usr/lib/libxcb-composite.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-composite.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-composite.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-damage.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-damage.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-damage.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dpms.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dpms.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dpms.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dri2.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dri2.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dri2.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dri3.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dri3.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-dri3.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-glx.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-glx.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-glx.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-present.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-present.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-present.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-randr.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-randr.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-randr.so.0.1.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-record.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-record.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-record.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-render.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-render.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-render.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-res.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-res.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-res.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-screensaver.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-screensaver.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-screensaver.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-shape.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-shape.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-shape.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-shm.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-shm.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-shm.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-sync.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-sync.so.1 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-sync.so.1.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xevie.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xevie.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xevie.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xf86dri.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xf86dri.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xf86dri.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xfixes.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xfixes.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xfixes.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xinerama.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xinerama.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xinerama.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xinput.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xinput.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xinput.so.0.1.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xkb.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xkb.so.1 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xkb.so.1.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xprint.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xprint.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xprint.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xtest.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xtest.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xtest.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xv.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xv.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xv.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xvmc.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xvmc.so.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb-xvmc.so.0.0.0 exists in filesystem
lib32-libxcb: /usr/lib/libxcb.so exists in filesystem
lib32-libxcb: /usr/lib/libxcb.so.1 exists in filesystem
lib32-libxcb: /usr/lib/libxcb.so.1.1.0 exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-composite.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-damage.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-dpms.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-dri2.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-dri3.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-glx.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-present.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-randr.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-record.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-render.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-res.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-screensaver.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-shape.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-shm.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-sync.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xevie.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xf86dri.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xfixes.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xinerama.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xinput.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xkb.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xprint.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xtest.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xv.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb-xvmc.pc exists in filesystem
lib32-libxcb: /usr/lib/pkgconfig/xcb.pc exists in filesystem
lib32-libx11: /usr/lib/libX11-xcb.so exists in filesystem
lib32-libx11: /usr/lib/libX11-xcb.so.1 exists in filesystem
lib32-libx11: /usr/lib/libX11-xcb.so.1.0.0 exists in filesystem
lib32-libx11: /usr/lib/libX11.so exists in filesystem
lib32-libx11: /usr/lib/libX11.so.6 exists in filesystem
lib32-libx11: /usr/lib/libX11.so.6.3.0 exists in filesystem
lib32-libx11: /usr/lib/pkgconfig/x11-xcb.pc exists in filesystem
lib32-libx11: /usr/lib/pkgconfig/x11.pc exists in filesystem
lib32-libxfixes: /usr/lib/libXfixes.so exists in filesystem
lib32-libxfixes: /usr/lib/libXfixes.so.3 exists in filesystem
lib32-libxfixes: /usr/lib/libXfixes.so.3.1.0 exists in filesystem
lib32-libxfixes: /usr/lib/pkgconfig/xfixes.pc exists in filesystem
lib32-libxrender: /usr/lib/libXrender.so exists in filesystem
lib32-libxrender: /usr/lib/libXrender.so.1 exists in filesystem
lib32-libxrender: /usr/lib/libXrender.so.1.3.0 exists in filesystem
lib32-libxrender: /usr/lib/pkgconfig/xrender.pc exists in filesystem
lib32-libxcursor: /usr/lib/libXcursor.so exists in filesystem
lib32-libxcursor: /usr/lib/libXcursor.so.1 exists in filesystem
lib32-libxcursor: /usr/lib/libXcursor.so.1.0.2 exists in filesystem
lib32-libxcursor: /usr/lib/pkgconfig/xcursor.pc exists in filesystem
lib32-libxext: /usr/lib/libXext.so exists in filesystem
lib32-libxext: /usr/lib/libXext.so.6 exists in filesystem
lib32-libxext: /usr/lib/libXext.so.6.4.0 exists in filesystem
lib32-libxext: /usr/lib/pkgconfig/xext.pc exists in filesystem
lib32-libxrandr: /usr/lib/libXrandr.so exists in filesystem
lib32-libxrandr: /usr/lib/libXrandr.so.2 exists in filesystem
lib32-libxrandr: /usr/lib/libXrandr.so.2.2.0 exists in filesystem
lib32-libxrandr: /usr/lib/pkgconfig/xrandr.pc exists in filesystem
lib32-libxdamage: /usr/lib/libXdamage.so exists in filesystem
lib32-libxdamage: /usr/lib/libXdamage.so.1 exists in filesystem
lib32-libxdamage: /usr/lib/libXdamage.so.1.1.0 exists in filesystem
lib32-libxdamage: /usr/lib/pkgconfig/xdamage.pc exists in filesystem
lib32-libxi: /usr/lib/libXi.so exists in filesystem
lib32-libxi: /usr/lib/libXi.so.6 exists in filesystem
lib32-libxi: /usr/lib/libXi.so.6.1.0 exists in filesystem
lib32-libxi: /usr/lib/pkgconfig/xi.pc exists in filesystem
lib32-attr: /usr/lib/libattr.so exists in filesystem
lib32-attr: /usr/lib/libattr.so.1 exists in filesystem
lib32-attr: /usr/lib/libattr.so.1.1.0 exists in filesystem
lib32-acl: /usr/lib/libacl.so exists in filesystem
lib32-acl: /usr/lib/libacl.so.1 exists in filesystem
lib32-acl: /usr/lib/libacl.so.1.1.0 exists in filesystem
lib32-gettext: /usr/lib/gettext/hostname exists in filesystem
lib32-gettext: /usr/lib/gettext/project-id exists in filesystem
lib32-gettext: /usr/lib/gettext/urlget exists in filesystem
lib32-gettext: /usr/lib/gettext/user-email exists in filesystem
lib32-gettext: /usr/lib/libasprintf.so exists in filesystem
lib32-gettext: /usr/lib/libasprintf.so.0 exists in filesystem
lib32-gettext: /usr/lib/libasprintf.so.0.0.0 exists in filesystem
lib32-gettext: /usr/lib/libgettextlib.so exists in filesystem
lib32-gettext: /usr/lib/libgettextpo.so exists in filesystem
lib32-gettext: /usr/lib/libgettextpo.so.0 exists in filesystem
lib32-gettext: /usr/lib/libgettextpo.so.0.5.2 exists in filesystem
lib32-gettext: /usr/lib/libgettextsrc.so exists in filesystem
lib32-gettext: /usr/lib/preloadable_libintl.so exists in filesystem
lib32-libpciaccess: /usr/lib/libpciaccess.so exists in filesystem
lib32-libpciaccess: /usr/lib/libpciaccess.so.0 exists in filesystem
lib32-libpciaccess: /usr/lib/libpciaccess.so.0.11.1 exists in filesystem
lib32-libpciaccess: /usr/lib/pkgconfig/pciaccess.pc exists in filesystem
lib32-libdrm: /usr/lib/libdrm.so exists in filesystem
lib32-libdrm: /usr/lib/libdrm.so.2 exists in filesystem
lib32-libdrm: /usr/lib/libdrm.so.2.4.0 exists in filesystem
lib32-libdrm: /usr/lib/libdrm_intel.so exists in filesystem
lib32-libdrm: /usr/lib/libdrm_intel.so.1 exists in filesystem
lib32-libdrm: /usr/lib/libdrm_intel.so.1.0.0 exists in filesystem
lib32-libdrm: /usr/lib/libdrm_nouveau.so exists in filesystem
lib32-libdrm: /usr/lib/libdrm_nouveau.so.2 exists in filesystem
lib32-libdrm: /usr/lib/libdrm_nouveau.so.2.0.0 exists in filesystem
lib32-libdrm: /usr/lib/libdrm_radeon.so exists in filesystem
lib32-libdrm: /usr/lib/libdrm_radeon.so.1 exists in filesystem
lib32-libdrm: /usr/lib/libdrm_radeon.so.1.0.1 exists in filesystem
lib32-libdrm: /usr/lib/libkms.so exists in filesystem
lib32-libdrm: /usr/lib/libkms.so.1 exists in filesystem
lib32-libdrm: /usr/lib/libkms.so.1.0.0 exists in filesystem
lib32-libdrm: /usr/lib/pkgconfig/libdrm.pc exists in filesystem
lib32-libdrm: /usr/lib/pkgconfig/libdrm_intel.pc exists in filesystem
lib32-libdrm: /usr/lib/pkgconfig/libdrm_nouveau.pc exists in filesystem
lib32-libdrm: /usr/lib/pkgconfig/libdrm_radeon.pc exists in filesystem
lib32-libdrm: /usr/lib/pkgconfig/libkms.pc exists in filesystem
lib32-libxxf86vm: /usr/lib/libXxf86vm.so exists in filesystem
lib32-libxxf86vm: /usr/lib/libXxf86vm.so.1 exists in filesystem
lib32-libxxf86vm: /usr/lib/libXxf86vm.so.1.0.0 exists in filesystem
lib32-libxxf86vm: /usr/lib/pkgconfig/xxf86vm.pc exists in filesystem
lib32-libxshmfence: /usr/lib/libxshmfence.so exists in filesystem
lib32-libxshmfence: /usr/lib/libxshmfence.so.1 exists in filesystem
lib32-libxshmfence: /usr/lib/libxshmfence.so.1.0.0 exists in filesystem
lib32-libxshmfence: /usr/lib/pkgconfig/xshmfence.pc exists in filesystem
lib32-libgpg-error: /usr/lib/libgpg-error.so exists in filesystem
lib32-libgpg-error: /usr/lib/libgpg-error.so.0 exists in filesystem
lib32-libgpg-error: /usr/lib/libgpg-error.so.0.11.0 exists in filesystem
lib32-libgcrypt: /usr/lib/libgcrypt.so exists in filesystem
lib32-libgcrypt: /usr/lib/libgcrypt.so.20 exists in filesystem
lib32-libgcrypt: /usr/lib/libgcrypt.so.20.0.1 exists in filesystem
lib32-xz: /usr/lib/liblzma.so exists in filesystem
lib32-xz: /usr/lib/liblzma.so.5 exists in filesystem
lib32-xz: /usr/lib/liblzma.so.5.0.5 exists in filesystem
lib32-xz: /usr/lib/pkgconfig/liblzma.pc exists in filesystem
lib32-systemd: /usr/lib/libgudev-1.0.so exists in filesystem
lib32-systemd: /usr/lib/libgudev-1.0.so.0 exists in filesystem
lib32-systemd: /usr/lib/libgudev-1.0.so.0.2.0 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-daemon.so exists in filesystem
lib32-systemd: /usr/lib/libsystemd-daemon.so.0 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-daemon.so.0.0.12 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-id128.so exists in filesystem
lib32-systemd: /usr/lib/libsystemd-id128.so.0 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-id128.so.0.0.28 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-journal.so exists in filesystem
lib32-systemd: /usr/lib/libsystemd-journal.so.0 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-journal.so.0.11.5 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-login.so exists in filesystem
lib32-systemd: /usr/lib/libsystemd-login.so.0 exists in filesystem
lib32-systemd: /usr/lib/libsystemd-login.so.0.9.3 exists in filesystem
lib32-systemd: /usr/lib/libsystemd.so exists in filesystem
lib32-systemd: /usr/lib/libsystemd.so.0 exists in filesystem
lib32-systemd: /usr/lib/libudev.so exists in filesystem
lib32-systemd: /usr/lib/libudev.so.1 exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/gudev-1.0.pc exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/libsystemd-daemon.pc exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/libsystemd-id128.pc exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/libsystemd-journal.pc exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/libsystemd-login.pc exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/libsystemd.pc exists in filesystem
lib32-systemd: /usr/lib/pkgconfig/libudev.pc exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_aarch64.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_alpha.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_arm.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_i386.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_ia64.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_ppc.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_ppc64.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_s390.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_sh.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_sparc.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_tilegx.so exists in filesystem
lib32-elfutils: /usr/lib/elfutils/libebl_x86_64.so exists in filesystem
lib32-elfutils: /usr/lib/libasm.so exists in filesystem
lib32-elfutils: /usr/lib/libasm.so.1 exists in filesystem
lib32-elfutils: /usr/lib/libdw.so exists in filesystem
lib32-elfutils: /usr/lib/libdw.so.1 exists in filesystem
lib32-elfutils: /usr/lib/libelf.so exists in filesystem
lib32-elfutils: /usr/lib/libelf.so.1 exists in filesystem
lib32-llvm-libs: /usr/lib/libLLVM-3.4.2.so exists in filesystem
lib32-llvm-libs: /usr/lib/libLLVM-3.4.so exists in filesystem
lib32-wayland: /usr/lib/libwayland-client.so exists in filesystem
lib32-wayland: /usr/lib/libwayland-client.so.0 exists in filesystem
lib32-wayland: /usr/lib/libwayland-client.so.0.2.0 exists in filesystem
lib32-wayland: /usr/lib/libwayland-cursor.so exists in filesystem
lib32-wayland: /usr/lib/libwayland-cursor.so.0 exists in filesystem
lib32-wayland: /usr/lib/libwayland-cursor.so.0.0.0 exists in filesystem
lib32-wayland: /usr/lib/libwayland-server.so exists in filesystem
lib32-wayland: /usr/lib/libwayland-server.so.0 exists in filesystem
lib32-wayland: /usr/lib/libwayland-server.so.0.1.0 exists in filesystem
lib32-wayland: /usr/lib/pkgconfig/wayland-client.pc exists in filesystem
lib32-wayland: /usr/lib/pkgconfig/wayland-cursor.pc exists in filesystem
lib32-wayland: /usr/lib/pkgconfig/wayland-scanner.pc exists in filesystem
lib32-wayland: /usr/lib/pkgconfig/wayland-server.pc exists in filesystem
lib32-mesa: /usr/lib/libOSMesa.so exists in filesystem
lib32-mesa: /usr/lib/libOSMesa.so.8 exists in filesystem
lib32-mesa: /usr/lib/libOSMesa.so.8.0.0 exists in filesystem
lib32-mesa: /usr/lib/libgbm.so exists in filesystem
lib32-mesa: /usr/lib/libgbm.so.1 exists in filesystem
lib32-mesa: /usr/lib/libgbm.so.1.0.0 exists in filesystem
lib32-mesa: /usr/lib/libglapi.so exists in filesystem
lib32-mesa: /usr/lib/libglapi.so.0 exists in filesystem
lib32-mesa: /usr/lib/libglapi.so.0.0.0 exists in filesystem
lib32-mesa: /usr/lib/libwayland-egl.so exists in filesystem
lib32-mesa: /usr/lib/libwayland-egl.so.1 exists in filesystem
lib32-mesa: /usr/lib/libwayland-egl.so.1.0.0 exists in filesystem
lib32-mesa: /usr/lib/mesa/libEGL.so exists in filesystem
lib32-mesa: /usr/lib/mesa/libEGL.so.1 exists in filesystem
lib32-mesa: /usr/lib/mesa/libEGL.so.1.0.0 exists in filesystem
lib32-mesa: /usr/lib/mesa/libGL.so exists in filesystem
lib32-mesa: /usr/lib/mesa/libGL.so.1 exists in filesystem
lib32-mesa: /usr/lib/mesa/libGL.so.1.2.0 exists in filesystem
lib32-mesa: /usr/lib/mesa/libGLESv1_CM.so exists in filesystem
lib32-mesa: /usr/lib/mesa/libGLESv1_CM.so.1 exists in filesystem
lib32-mesa: /usr/lib/mesa/libGLESv1_CM.so.1.1.0 exists in filesystem
lib32-mesa: /usr/lib/mesa/libGLESv2.so exists in filesystem
lib32-mesa: /usr/lib/mesa/libGLESv2.so.2 exists in filesystem
lib32-mesa: /usr/lib/mesa/libGLESv2.so.2.0.0 exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/dri.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/egl.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/gbm.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/gl.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/glesv1_cm.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/glesv2.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/osmesa.pc exists in filesystem
lib32-mesa: /usr/lib/pkgconfig/wayland-egl.pc exists in filesystem
lib32-mesa: /usr/lib/xorg/modules/dri/swrast_dri.so exists in filesystem
lib32-mesa-libgl: /usr/lib/libEGL.so exists in filesystem
lib32-mesa-libgl: /usr/lib/libEGL.so.1 exists in filesystem
lib32-mesa-libgl: /usr/lib/libEGL.so.1.0.0 exists in filesystem
lib32-mesa-libgl: /usr/lib/libGL.so exists in filesystem
lib32-mesa-libgl: /usr/lib/libGL.so.1 exists in filesystem
lib32-mesa-libgl: /usr/lib/libGL.so.1.2.0 exists in filesystem
lib32-mesa-libgl: /usr/lib/libGLESv1_CM.so exists in filesystem
lib32-mesa-libgl: /usr/lib/libGLESv1_CM.so.1 exists in filesystem
lib32-mesa-libgl: /usr/lib/libGLESv1_CM.so.1.1.0 exists in filesystem
lib32-mesa-libgl: /usr/lib/libGLESv2.so exists in filesystem
lib32-mesa-libgl: /usr/lib/libGLESv2.so.2 exists in filesystem
lib32-mesa-libgl: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
lib32-glu: /usr/lib/libGLU.so exists in filesystem
lib32-glu: /usr/lib/libGLU.so.1 exists in filesystem
lib32-glu: /usr/lib/libGLU.so.1.3.1 exists in filesystem
lib32-glu: /usr/lib/pkgconfig/glu.pc exists in filesystem
lib32-libice: /usr/lib/libICE.so exists in filesystem
lib32-libice: /usr/lib/libICE.so.6 exists in filesystem
lib32-libice: /usr/lib/libICE.so.6.3.0 exists in filesystem
lib32-libice: /usr/lib/pkgconfig/ice.pc exists in filesystem
lib32-util-linux: /usr/lib/libblkid.so exists in filesystem
lib32-util-linux: /usr/lib/libblkid.so.1 exists in filesystem
lib32-util-linux: /usr/lib/libblkid.so.1.1.0 exists in filesystem
lib32-util-linux: /usr/lib/libmount.so exists in filesystem
lib32-util-linux: /usr/lib/libmount.so.1 exists in filesystem
lib32-util-linux: /usr/lib/libmount.so.1.1.0 exists in filesystem
lib32-util-linux: /usr/lib/libuuid.so exists in filesystem
lib32-util-linux: /usr/lib/libuuid.so.1 exists in filesystem
lib32-util-linux: /usr/lib/libuuid.so.1.3.0 exists in filesystem
lib32-util-linux: /usr/lib/pkgconfig/blkid.pc exists in filesystem
lib32-util-linux: /usr/lib/pkgconfig/mount.pc exists in filesystem
lib32-util-linux: /usr/lib/pkgconfig/uuid.pc exists in filesystem
lib32-libsm: /usr/lib/libSM.so exists in filesystem
lib32-libsm: /usr/lib/libSM.so.6 exists in filesystem
lib32-libsm: /usr/lib/libSM.so.6.0.1 exists in filesystem
lib32-libsm: /usr/lib/pkgconfig/sm.pc exists in filesystem
Errors occurred, no packages were upgraded.
Lots of conflicting files...
This is what happens if I try to force it.
# pacman -S --force wine
resolving dependencies...
:: There are 3 providers available for lib32-libgl:
:: Repository multilib
1) lib32-mesa-libgl 2) lib32-nvidia-304xx-libgl 3) lib32-nvidia-libgl
Enter a number (default=1):
warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2 dependency
looking for inter-conflicts...
Packages (46): lib32-acl-2.2.52-2 lib32-attr-2.4.47-1 lib32-bzip2-1.0.6-2 lib32-elfutils-0.159-1 lib32-expat-2.1.0-2 lib32-fontconfig-2.11.1-1 lib32-freetype2-2.5.3-1 lib32-gcc-libs-4.9.1-1
lib32-gettext-0.19.2-1 lib32-glib2-2.40.0-1 lib32-glibc-2.19-5 lib32-glu-9.0.0-2 lib32-harfbuzz-0.9.32-1 lib32-icu-53.1-1 lib32-libdbus-1.8.6-1 lib32-libdrm-2.4.56-1
lib32-libffi-3.1-1 lib32-libgcrypt-1.6.1-1 lib32-libgpg-error-1.13-1 lib32-libice-1.0.9-1 lib32-libpciaccess-0.13.2-1 lib32-libpng-1.6.12-1 lib32-libsm-1.2.2-1 lib32-libx11-1.6.2-1
lib32-libxau-1.0.8-1 lib32-libxcb-1.11-1 lib32-libxcursor-1.1.14-1 lib32-libxdamage-1.1.4-2 lib32-libxdmcp-1.1.1-2 lib32-libxext-1.3.3-1 lib32-libxfixes-5.0.1-1 lib32-libxi-1.7.4-1
lib32-libxrandr-1.4.2-1 lib32-libxrender-0.9.8-1 lib32-libxshmfence-1.1-1 lib32-libxxf86vm-1.1.3-1 lib32-llvm-libs-3.4.2-1 lib32-mesa-10.2.5-1 lib32-mesa-libgl-10.2.5-1
lib32-pcre-8.35-1 lib32-systemd-215-1 lib32-util-linux-2.25-1 lib32-wayland-1.5.0-1 lib32-xz-5.0.5-1 lib32-zlib-1.2.8-1 wine-1.7.24-1
Total Installed Size: 387.40 MiB
:: Proceed with installation? [Y/n]
(46/46) checking keys in keyring [###########################################################################] 100%
(46/46) checking package integrity [###########################################################################] 100%
(46/46) loading package files [###########################################################################] 100%
(46/46) checking for file conflicts [###########################################################################] 100%
error: failed to commit transaction (conflicting files)
unable to --force directory-file conflicts
lib32-glibc: /usr/lib/locale exists in filesystem
Errors occurred, no packages were upgraded.
I have no idea what could be the problem. My Arch is up to date.
Please help me.
Thanks3mb3r4 wrote:This is what happens if I try to force it
If you don't understand what happens to your installation, DON'T DO THAT AGAIN.
You should use '--force' only if you are sure nothing bad will result from that.
In this case, you are happy that pacman refuses to force the installation of the lib32 packages in place of the already installed x86_64 libraries.
The lib32 libraries should be installed in '/usr/lib32' not '/usr/lib'.
What is the result of 'ls -l /usr/lib32' ?
There is something not good here with your system... -
Missing file error when installing SAP Front End
When installing SAP front end, i am receiving following file missing error, please assist:
I am using Windows XP Professional
The SAP Front-End Setup has not successfully installed all selected components on your computer, either because a component could not be installed or the process has been aborted.
Click Finish to exit the wizard.
The following program files are missing on the installation source:
c:\sapexport34567\others\sapgui620\gui\windows\win32\sapgui\filc\odbc\mscreate.dir
c:\sapexport34567\others\sapgui620\gui\windows\win32\sapgui\xxl\saplotgr.gid
c:\sapexport34567\others\sapgui620\gui\windows\win32\sapgui\xxl\saplotuk.gid
The installed applications may not function correctly until all program files are successfully installed. For detailed error descriptions, please open file://C:\SAPEXP1\Others\SAPGUI1\GUI\WINDOWS\WIN32\setup\saplogvw.exe .Hi Anand,
I would not care about those files, because they are unneccessary. mscreate.dir is a 0 byte file which just tells that microsoft has created this directory. The *.gid files are winhelp files that get created when you first use the help function.
Regards,
Pascal -
Address book files corrupt when transfered to motorola phone
when syncing via bluetooth from addressbook using "send this card", the file arrives at my motorola Pebl phone but when I tried to save it, I get the message file corrupt. Any suggestions
Motorola pebl phone Mac OS X (10.4.5) via bluetoothMotorola phone and Address Book might not agree of what a correct VCard is.
I would say that the main problem is the encoding.
Does your card contain special characters?
Go in Address Book preferences -> VCard and change encoding to UTF8 or change VCard version down to 2.1. -
File transfer between IMAC and Motorola RAZR V3c
I recently replaced my defective Verizon RAZR phone with a new RAZR v3c. Previously, I was able to exchange music, video and pic files readily by dragging and dropping via bluetooth. The new phone pairs up w/ bluetooth but an error message appears stating the device "does not have the necessary services". Is there a way to transfer these files even w/o bluetooth if necessary? I've been reading for hours and haven't found a solution. Please HELP!! Thanks
Bad news... Verizon disabled that "feature" of your phone. I guess they did it to try to force subscribers to buy more ringtones and use more data transfers. It might depend on the exact firmware version. There's some info on it here:
http://blog.wired.com/music/2006/07/verizonrazrca.html
And a (somewhat daunting) wiki tutorial on how to replace the Verizon $oftware with the original phone software from Alltel:
http://wiki.howardforums.com/index.php/MotorolaV3c_Tutorial:_Flashing_to_Alltel_UserInterface
Oh wait, just found this... apparently you can take it to a Verizon store and have them update the firmware:
http://www.gizmodo.com/gadgets/cellphones/verizon-finally-enables-file-transfer- bluetooth-on-motorola-razr-v3c-168533.php -
Valid packages goes invalid when executing application
Friends of pl/sql
When we execute our application we find that 2 of our main packiages go invalid for no reason. The packages compiles just fine when we then compile them. So, no syntax errors. But it stops our application with a lovely "existing state of packages have been discarded......." type error. Not too nice.
What are some of the things to check on for why the package goes invalid ?
We are using TOAD and sql*monitor to trace the process at the moment...........
Any solutions out there ?
Environment : Oracle Enterprise Linux 5 on Oracle 11.1.0.6 (latest patch available). Oracle 11 client as well.
Edited by: ow001294 on Apr 15, 2009 9:24 AMOne of my older standard responses (haven't use this in a while)..
Packages tend to fail because of their "package state". A package has a "state" when it contains package level variables/constants etc. and the package is called. Upon first calling the package, the "state" is created in memory to hold the values of those variables etc. If an object that the package depends upon e.g. a table is altered in some way e.g. dropped and recreated, then because of the database dependencies, the package takes on an INVALID status. When you next make a call to the package, Oracle looks at the status and sees that it is invalid, then determines that the package has a "state". Because something has altered that the package depended upon, the state is taken as being out of date and is discarded, thus causing the "Package state has been discarded" error message.
If a package does not have package level variables etc. i.e. the "state" then, taking the same example above, the package takes on an INVALID status, but when you next make a call to the package, Oracle sees it as Invalid, but knows that there is no "state" attached to it, and so is able to recompile the package automatically and then carry on execution without causing any error messages. The only exception here is if the thing that the package was dependant on has changes in such a way that the package cannot compile, in which case you'll get an Invalid package type of error.
And if you want to know how to prevent discarded package states....
Move all constants and variables into a stand-alone package spec and reference those from your initial package. Thus when the status of your original package is invlidated for whatever reason, it has no package state and can be recompiled automatically, however the package containing the vars/const will not become invalidated as it has no dependencies, so the state that is in memory for that package will remain and can continue to be used.
As for having package level cursors, you'll need to make these local to the procedures/functions using them as you won't be able to reference cursors across packages like that (not sure about using REF CURSORS though.... there's one for me to investigate!)
This first example shows the package state being invalided by the addition of a new column on the table, and causing it to give a "Package state discarded" error...
SQL> set serveroutput on
SQL>
SQL> create table dependonme (x number)
2 /
Table created.
SQL>
SQL> insert into dependonme values (5)
2 /
1 row created.
SQL>
SQL> create or replace package mypkg is
2 procedure myproc;
3 end mypkg;
4 /
Package created.
SQL>
SQL> create or replace package body mypkg is
2 v_statevar number := 5; -- this means my package has a state
3
4 procedure myproc is
5 myval number;
6 begin
7 select x
8 into myval
9 from dependonme;
10
11 myval := myval * v_statevar;
12 DBMS_OUTPUT.PUT_LINE('My Result is: '||myval);
13 end;
14 end mypkg;
15 /
Package body created.
SQL>
SQL> exec mypkg.myproc
My Result is: 25
PL/SQL procedure successfully completed.
SQL>
SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
2 /
OBJECT_NAME
OBJECT_TYPE STATUS
MYPKG
PACKAGE VALID
MYPKG
PACKAGE BODY VALID
SQL>
SQL>
SQL> alter table dependonme add (y number)
2 /
Table altered.
SQL>
SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
2 /
OBJECT_NAME
OBJECT_TYPE STATUS
MYPKG
PACKAGE VALID
MYPKG
PACKAGE BODY INVALID
SQL>
SQL> exec mypkg.myproc
BEGIN mypkg.myproc; END;
ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package body "SCOTT.MYPKG" has been invalidated
ORA-06508: PL/SQL: could not find program unit being called: "SCOTT.MYPKG"
ORA-06512: at line 1
SQL>
SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
2 /
OBJECT_NAME
OBJECT_TYPE STATUS
MYPKG
PACKAGE VALID
MYPKG
PACKAGE BODY INVALID
SQL>
SQL> exec mypkg.myproc
PL/SQL procedure successfully completed.
SQL>
SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
2 /
OBJECT_NAME
OBJECT_TYPE STATUS
MYPKG
PACKAGE VALID
MYPKG
PACKAGE BODY VALIDAnd this next example shows how having the package variables in their own package spec, allows the package to automatically recompile when it is called even though it became invalidated by the action of adding a column to the table.
SQL> drop table dependonme
2 /
Table dropped.
SQL>
SQL> drop package mypkg
2 /
Package dropped.
SQL>
SQL> set serveroutput on
SQL>
SQL> create table dependonme (x number)
2 /
Table created.
SQL>
SQL> insert into dependonme values (5)
2 /
1 row created.
SQL>
SQL> create or replace package mypkg is
2 procedure myproc;
3 end mypkg;
4 /
Package created.
SQL>
SQL> create or replace package mypkg_state is
2 v_statevar number := 5; -- package state in seperate package spec
3 end mypkg_state;
4 /
Package created.
SQL>
SQL> create or replace package body mypkg is
2 -- this package has no state area
3
4 procedure myproc is
5 myval number;
6 begin
7 select x
8 into myval
9 from dependonme;
10
11 myval := myval * mypkg_state.v_statevar; -- note: references the mypkg_state package
12 DBMS_OUTPUT.PUT_LINE('My Result is: '||myval);
13 end;
14 end mypkg;
15 /
Package body created.
SQL>
SQL> exec mypkg.myproc
My Result is: 25
PL/SQL procedure successfully completed.
SQL>
SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
2 /
OBJECT_NAME
OBJECT_TYPE STATUS
MYPKG
PACKAGE VALID
MYPKG
PACKAGE BODY VALID
SQL>
SQL> alter table dependonme add (y number)
2 /
Table altered.
SQL>
SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
2 /
OBJECT_NAME
OBJECT_TYPE STATUS
MYPKG
PACKAGE VALID
MYPKG
PACKAGE BODY INVALID
SQL>
SQL> exec mypkg.myproc
My Result is: 25
PL/SQL procedure successfully completed. -
Adobe Acrobat losing file association when installing Adobe Reader X or XI (Using Cust. Wizard)
Hello Adobe Forums,
I'm an IT professionnal in a large company, and we've been dealing with an issue using this software.
Using the "Adobe Customization Wizard 9", prior to version X and XI, the following option was available:
Adobe Acrobat 9:
Adobe Reader 9:
As you see, the customization wizard of both software allowed you to leave Adobe Acrobat as the default PDF handler.
Now, let's look at the Customization Wizard X
Adobe Acrobat X: (XI has the same options)
Adobe Reader X: (XI has the same options)
Now here, we can see that in Adobe Reader X, we only have "Make Reader the default" or "Installer will decide which will be the default"
I want to keep Adobe Acrobat as the default, so I choose "Installer will decide which product will be the default"
Guess which software becomes the default? Adobe Reader....
So what is happening here is that Adobe Customization Wizard X and XI will NOT let you keep Acrobat as the default, unless you execute a repair or reinstall Acrobat after installing Adobe Reader.
Adobe Reader X and XI forces itself to become the default handler, in every option scenario we can find. Adobe Customization Wizard 9 would let you choose to keep Acrobat as the handler. Why was this removed in X and XI?
This is very annoying and causing a lot of grief inside the company. Is there a solution for this?Sup guys
My colleague did some research and found the answer in this thread: http://forums.adobe.com/message/4457755#4457755
Use "LEAVE_PDFOWNERSHIP=YES" in the command line when installing Adobe Reader to preserve PDF Ownership! -
[SOLVED] Files corrupted when installing packages
I've been using arch for about six months now, I like it very much but I've run into a problem. I suspect it could be that coming from Ubuntu, I'm not used to Arch's "rolling release" approach and I've let things get out of date, but I'd like to have that confirmed before I update my whole system.
I am having trouble installing the apache web server, specifically the download seems to go OK but then pacman says the files are corrupt :
root> pacman -S apache
warning: apache-2.4.12-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) apache-2.4.12-2
Total Download Size: 1.28 MiB
Total Installed Size: 7.13 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] Y
:: Retrieving packages ...
apache-2.4.12-2-x86_64 1309.1 KiB 2.01M/s 00:01 [############################################################] 100%
(1/1) checking keys in keyring [############################################################] 100%
(1/1) checking package integrity [############################################################] 100%
error: apache: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/apache-2.4.12-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
I got a similar result a couple of days ago when trying to install 'gdb'. I tried making http://mirror.rit.edu/archlinux/$repo/os/$arch the first server in my mirrorlist file, but no change. I'm wondering if maybe my version of arch is just outdated and I need to upgrade with 'pacman -Syu' ? Currently uname -a shows "Linux bigsalad 3.18.5-1-ARCH #1 SMP PREEMPT Fri Jan 30 07:31:50 CET 2015 x86_64 GNU/Linux". As far as I can see, it's either that I'm out of date, or for some random reason the two packages I've happened to try in the last few days have issues. If it's the latter, I'd rather not over react with "pacman -Syu".
Anyone have any thoughts? This is my first post here so apologies in advance if it isn't quite right.
Thanks,
Niles.
Last edited by nilesOien (2015-05-09 04:55:36)OK, now I'm super confused.
I tried both "pacman-key --refresh-keys", and after that failed, "pacman -Syu". Neither worked. The full output from refreshing the keys is below :
root> pacman-key --refresh-keys
gpg: refreshing 77 keys from hkp://pool.sks-keyservers.net
gpg: connecting dirmngr at '/root/.gnupg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver refresh failed: No dirmngr
==> ERROR: A specified local key could not be updated from a keyserver.
Not being very experienced with keys, I didn't pursue that further.
And pacman -Syu failed - it seemed to download everything, but then convince itself that the keys were invalid (see below). I'm not at all experienced with keys, so that may be the problem. Please help!!! My arch systems have been running fine, but I don't seem to be able to upgrade, which seems to be a requisite for installing new packages? I'm lost!!
(361/361) checking keys in keyring [################################] 100%
(361/361) checking package integrity [################################] 100%
error: lzo: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/lzo-2.09-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: alsa-lib: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/alsa-lib-1.0.29-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: alsa-plugins: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/alsa-plugins-1.0.29-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: alsa-utils: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/alsa-utils-1.0.29-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: apr: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/apr-1.5.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: v4l-utils: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/v4l-utils-1.6.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: dhcpcd: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/dhcpcd-6.8.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: dhclient: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/dhclient-4.3.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: talloc: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/talloc-2.1.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: syslinux: signature from "Anatol Pomozov <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/syslinux-6.03-3-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
Last edited by nilesOien (2015-05-09 04:31:41) -
CRC missing file error when installing windows
When trying to instal windows on my Mac Pro desktop I keep getting the same error message. I must have tried it 6 times and always get the same message whether I am trying to my main disk partitioned, or to my secondary disk. It tells me to check my disk and I have, and cleaned it, plus I have ued the same disk to instal windows on my laptop Mac Pro without problems.
The message follows...
Error:
SXS.dll: syntax error in manifest or policy file "f:\i386\asms\6000\msft\windows\common\controls\controls.man" on line 4
xxx
error:
installation failed f:\i386\asms. Error message: Data error (cycle redundancy check)
xxx
fatal error:
one of the components that windows needs to continue setup could not be installed.
Data error (cycle redundancy check)
If you are installing from a CD there might be a problem with the disk; try cleaning the disk or using another disk.
Please help!
DougIt should be "Cyclic Redundancy Check" I believe. If I were you I would check the disc for scratches...etc., and even if you can't detect any that are very visible, it would still be a good idea to go out and purchase some stuff designed for fixing scratches/blemishes on CD's so you can use them again. If that doesn't work, I'm at a loss.
-
Error on file m293 when installing Crystal Reports Enterprise XI sp4
I am trying up upgrade Crystal Reports Enterprise XI from sp2 to sp4. When I run the crsxir2win_sp4.exe it runs for awhile and then an error is return indicating that it can not find the file m293.cab. I looked in the temporary folder when the install program exploded the files and I see a lot of mXXX.cab files but I do not see m293. Is there a problem with the file I downloaded.
Thanks
AdamI have the same problem.
-
N8 "File corrupted" when installing apps
I recently made a reset on my Nokia N8, using *#7370# command.
After the reset I'm not able to install any application to the phone. When I start the installation (e.g.: Ovi Store), the "File corrupted" error message appears on the screen. I tried different applications but the same happens.
I tried re-installing the firmware, and doing Factory reset, but none of these helped.
Anybody having the same issue?if i understand well you have install the firmware via pc 2 times and did not help
then try one more time with out hard reset, if still nothing you may need go at nokia care
dont know more detailed infos cos never involved so deep but seems the installing part or qt files or applicationswhich helps to install has been damage or missing (after hard reset) and updating the software not help because phone after update is restoring back (something like back up) the previous setting -
Has anyone gotten a missing file error when installing 10.5 on windows 7
I have tried to install iTunes 10.5 on my windows 7 64 bit laptop and keep getting a "missing file error" but it doesn't say what file is missing and I haven't been able to find any info to help resolve the issue. Any help would be appreciated!
Ok, if you get this message I've read a bit further and found that you must uninstal everything that has something to do with apple. this includes the device driver. this link may help you with that. http://support.apple.com/kb/ht1925 Once I went through the list and deleted everything (device support is a *****). I installed it again and it came up with the same error. I then clicked ok and it rolled back but automatically started installing again and it worked. I know have itunes 10.5. but know my iphone 4 wont connect to it, lol. it says i have to reinstal because the driver didn't take or something. I really want the OS update for my phone but gd this is a bit much.
-
N85 says file corrupted when installing whatsapp
Hey all i really need some help here!!
I tried to install whatsapp from http://www.whatsapp.com/nokia/ but failed -"file corrupted".
i don't know what happened because the website clearly states that the app supports N85.
Another thing, Nokia Suite made me download the service controllers (no idea what that is) but i couldn't install that either, ágain, "file corrupted".
Is there something wrong with my phone?
THANKS IN ADVANCE!!! )))
Device:
Software Version 31.002
4-11-09
Custom Version 31.002.208.4
24-12-09Hi Crumpetgirl,
Welcome to Nokia Support Discussions!
Have you tried downloading Whatsapp directly from Nokia Store, you can find it here. You can download it directly on your mobile using the Store application or connect your phone to Nokia Suite and download it through there.
If the problem persists, try to re-install your phone software by selecting Tools > Software update on Nokia Suite.
Hope this helps!
Puigchild
If you find this post helpful, a click upon the white star at bottom would always be appreciated.
If it also solves your problem, clicking ACCEPT AS SOLUTION below it will benefit other users!
Maybe you are looking for
-
How do i move photos from one mac to another
I just purchased a MacBook Pro, and would like to move the photos on my old iMac to it. How do I do that? Thanks.
-
How can I find ringtones for sale in iTunes? I don't see it as a category anywhere.
how can I find ringtones for sale in iTunes? I don't see it as a category anywhere.
-
Move photos to trash from Bridge and can't find them in trash
Help! When I was doing the selection from Bridge, I delete some of the photos by selecting them then clicked 'move to trash', but I can't find them in trash,I am using Bridge CC, When I was using the previous edition there's no problem, but things ch
-
Fix blurry images downloaded from Safari (The semi-easy way)
Hi, I've noticed a couple of people around here have had problems with image quality (blurry images) whenever an image was saved to the camera roll from Safari. Turns out, there is a simple fix for this! This fix requires a drawing app such as Brushe
-
How to send SMS Our Database Record
Hi, I need when some one send message (DET *11952*) to my No (Which is connect with my server) then it will send sms the sum of qty of design no *11952* from the table detail I Am using Developer 6I with oracle XE edition Regards Shahzaib ismail