Bootcamp problem when booting win vista

hello guys
i have one small problem while booting with windows vist. i make a clean install with vista.
first i created bootcamp partition and then i boot with vista dvd and i formated the ''bootcamp'' partition and install vista. after restart and pressing the option key to select the vista boot the booting started with some errors. because is not possible to make screen shots on bootime i record a video and i uploaded to youtube so u can watch the errors.
does this happen on all macbooks with bootcamp/vista installation or the problem is on my macbook or the vista installation...?
http://www.youtube.com/watch?v=J7PrnQw-T_A
thanks

If Vista installed, and did an automatic restart after expanding and copying files to your hard drive, it should restart on its own into Vista until all the updates are applied. No need to use the Option key.
I didn't visit YouTube to try to see, other than what you have described.
As long as you formatted to NTFS and Vista accepted the partition (20-50GB is good number).
I would install Boot Camp from your OEM DVD from Apple either before doing any auto updates from Microsoft, or when it is all done. Either works. And add AV software like Norton AV 2009 (and yes, it is fine, unlike 2008 and before, and no need for any of the "Suites" with Vista, most get in the way and take over).
I have had trouble with Vista SP1 DVD though.

Similar Messages

  • I deal with a itunes update problem when i try to update i get coneection has timed out error! i had the same problem when i had vista.. yesterday i formated my pc but i still have the same prommblem. i dont deal with such problems on direct downloads.

    i deal with a itunes update problem when i try to update i get coneection has timed out error! i had the same problem when i had vista.. yesterday i formated my pc but i still have the same prommblem. i dont deal with such problems on direct downloads.i have this problem only with tunes. maybe my conection freezes for a sec idk

    Sorry I gave this a 'this helped me' but after a long struggle I found some ticked box somewhere from some unauthorised chrome extension blaaa....... the link you gave was great, not only did it confirm all the bad things google is supposed to be up to it provided a better browser. Cheers man.
    Anyone who find this; I disabled all extension in chrome. I then searched the word proxy in the settings section. A button came up, "change proxy settings" I clicked on it. Earlier it was greyed out as an extension was interefering.. It brought up a box with my own settings from my computer. Then I clicked LAN settings, then unchecked the 'Use a proxy server' button.
    P.S. If you're using chrome, bail, and dowload Komodo Dragon. It's virtually identical, but you're not tracked, and you can use chrome extensions, and you can quickily transfer your chrome preferences into it.

  • Audio problem when running Win XP Pro SP3

    I have a problem when running Windows XP SP3 on my MacBook. Every minute or so, and this happens consistently, the music would be played in a slow-motion mode, and after a few seconds return to normal speed. I have exchanged for another MacBook, and I am having the exact same problem. I have all the drivers installed properly, and have tried both iTunes and WMP. This even happens when I am gaming or watching YouTube.
    The problem does not exist when I'm running Mac OS X.
    Any help would be greatly appreciated. Thanks.

    After spending a few hours googling around I finally found the solution to the problem. At first I thought it was something wrong with my Windows XP Pro, but apparently people running Vista were having the same problem.
    I installed Vista myself and indeed was having the same problem.
    The problem apparently is a clash between the sound card and the WiFi card on the MacBook. If you turn off your WiFi, you would not get the occasional adio/video slowdown.
    The solution was actually quite simple, force-install the 5.x Broadcom 802.11n driver, and voila, problem taken care of.
    Message was edited by: docomo661

  • Qosmio G30 problems when booting up

    Hi - I hope someone can help.
    My G30 has developed problems on boot up. When I switch on I hear the 'tune' and the drive light flashes but the screen stays black.
    I've tried leaving it for up to 10 minutes but still nothing happens. If I hold 'FN' and press f5 it bursts into life and I then scroll the various screen options and it works fine. I am not too technically gifted so be gentle with me if you have any suggestions.
    I only found out about the F5 because I thought it was a screen problem so I hooked up a separate screen to try to get some access to the drives.
    Any thoughts - anyone?
    Ron
    Message was edited by: rocketronr6

    Hi,
    just a question: do you have a picture on your external screen? I couldnt in your posting figure out if yes or not.
    You can try to remove memorymodules if possible, to test if its a memory issue. (Its often the problem that one module is faulty and the reason for no-boot)
    Otherwise you should bring your lovely paperweight ;) to a local service partner for hardware checkup.
    Would appreciate some feedback of your diagnosis progress :)
    Greets

  • Problems when Booting my Mac/ Partitioning for Windows 7

    Hello Community,
    3 months ago, i bought a MacBook Pro mid 2012-model. I was very satisfied until a really big problem occured.
    The first time I recognized a boot-problem was when I restarted my Mac, a screen with the "forbidden-symbol" came up, after the Apple Logo. So I read some articles on the web and tried to restore my mac. After some trys, this was successfull after about 5h (got slow internet connection). I could also start my mac successfully, and in the boot menu, when hitting alt on the keyboard, a normal Mac partition, and a recovery partition could be seen (Before it only a Mac partition was there, no Windows and no recovery). So I started OS X successfully and looked into hard drive diagnostics and let the computer check the Hard Drive. It said that it was successfully, but after booting the second time (after successfull restore), I had the same problem again (and there was only one partition showing in the boot menu).
    Finally, after 4 days of problem-solving, I managed to install windows 7 on my mac, without installing mac. Now I want to make a Mac recovery disk on windows, and use it for restoring.
    So my question is:
    1. What is causing the boot-problem and how can I solve that? I am sooooo desperated and just want to go back to Windows computers .
    2. If there is no chance I can repair my mac, how can I create a recovery diskon Windows? (This question is less important, but i'd be REALLY thankful for any hints)
    Thank you in advance!
    With best regards,
    David Al

    Got it. Thanks for the help.  Isn't there any boot disk thing that I can just stick in there that will jerk the OS sideways and give me the Mac login screen, or did the Bootcamp/partition attack just wreck everything?  I don't see why I have to do an entire scrape of my totally updated and formerly working OSX just to retry a routine Bootcamp partition, which the girl at the Mac Store in Seattle here assured me has worked for them all the time.   It really is a crock. Maybe I shouldn't bother trying to put Windows 7 on there at all if all these latest versions are so flimsy. I wouldn't want to have to do it all again. But it looks like I'll have to at least once. And send Apple the bill for my wasted time. I ain't feelin' the glamour.

  • Problems dual booting Windows Vista with Oracle Enterprise Linux 4

    I tried dual booting my sony laptop which came pre installed with windows Vista,After a successful installation,windows Vista boots fine,but Oracle enterprise linux just stops booting at this point " Starting Udev...................................................(OK)
    Initializing hardware....Storage network"
    It's posibly a hardware compatibility problem but I dont know why I get stuck at this point.Can anyone help please?

    hi,
    r u getting this error while installing oel or after installation?
    which version of oel u r installing?
    u may get this error probably due to hard disk (usually sata) compatility with linux.
    --Regards
    Xaheer

  • Problem when booting - Invalid Node Structure

    Hey!
    I decided to put my MacBook G4 up to date. So I installed several updates of my software. So far so good. Then I tried to check with Disk Utility wether there were any problems on the file system. I ran "repair Disk Permissions" and some errors where found and corrected. I tried "Verify Disk" and it announced there where some errors namely "Invalid Node Structure". As I couldn't repair the disk as it was the current boot disk I decided to run Disk Utility from a CD. Unfortunately I didn't have my original cd so I asked a friend to use his. He gave me his "MacBook Pro - Mac OS X Install Disc"s (Mac OS X 10.5) and I ran it on my PowerBook G4 (Mac OS X 10.4 installed). It gave the same result like when I ran it from my hard drive. When I tried to repair it, it started and stopped after some seconds (between 20 and 40 seconds) saying it was unable to repair it.
    After that the computer does not mount from hard drive (10.4 installed) anymore, only from cd. I tried booting in single user mode and executing /sbin/fsck -fy but I had the same result ("disk0s10: I/O error. Invalid node structure (4, 7698) **Volume check failed.").
    I think I can resolve the problem by starting my mac in firewire mode, backing up my data and reinstalling Mac OS X (would a repair from 10.4 Disk Utility work?) but I would be happy if there were any faster / more elegant way to do so as I cant use my install cds for 10.4 right now as I am in an other country for some time.
    Any help?

    Hi Ja!, and a warm welcome to the forums!
    Unfortunately DU & fsck can't fix all that much, your best bet is DiskWarrior, you need the CD though.
    http://www.alsoft.com/DiskWarrior/
    If DW can't fix it, you might try Data Rescue II...
    http://www.prosofteng.com/products/data_rescue.php
    (Has a Free Demo to see if it could or not, but you'll need another drive to recover to).
    Or FileSalvage...
    http://www.subrosasoft.com/OSXSoftware/index.php?%20mainpage=product_info&productsid=1
    to recover what you can.
    PS. Don't use Leopard Install Disk to work on Tiger Hard disks, it's always messed up my Tiger Disks ehen I did.
    Also, not a good idea to even Repair Permissions if there are Disk problems like you have, you don't want to write anything to a disk that has problems, that means even trying to boot off it until you fix it.

  • Problem when booting from PATA drive on IDE-3 with SATA RAID on ICH5R

    Hello,
    I have a PATA drive installed as Master on IDE-3 (Promise Controller), using Windows XP as the operating system. I also have an aditional drive as Slave on IDE-3.
    I recently bought 2 SATA drives which I would like to use as a RAID array, so I connected them to SER-1 and SER-2, on the ICH5R controller.
    I set the On-Chip IDE Configuration as follows:
    Native Mode
    SATA Only
    Keep PATA Active - Yes
    PATA Channel selection - Both
    Configure SATA as Raid - Yes
    I have my PATA Master IDE-3 drive as the firts boot device...unfortunatly now my system does not boot up.
    It goes through the Intel Raid Bios screen, then the Promise Controller screen, and then when it was supposed to start loading windows, the screen remains black for about 2 minutes and after it I receive an error message warning me that Windows has detected a hardware configuration problem.
    I went back to BIOS and changed the "Configure SATA as Raid" to NO, and now everything works fine, except for the fact that I have no RAID array installed.
    Can anyone help me with this?
    Thanks,
    Mihalis

    The PATA IDE channel associated with the Promise controller is exclusively designed to be used as a RAID solution. It seems you have an invalid hardware installation of your 2 EIDE drives. Although you succesfully installed WinXP using that configuration, you're destined to have unpredictable behavior because of it.
    WinXP looks to the BIOS first to identify hard drives. Then it does something that no other OS has done before (except maybe Win2K), it attempts to detect the hard drive directly through the wires itself. If it finds something, it installs resources to get it to work right. In your case, WinXP has bypassed the BIOS and detected the drives but doesn't really know where they are. WinXP just knows they are there so it supplied the necessary resources to complete the installation.
    That drives that are connected to the Promise controller must use the Promise RAID drivers supplied with your motherboard so that the Promise controller can properly report to the OS. You could have conected the same two drives on the same controller, but they needed to be configured as RAID drives within the Promise controller utility.
    To have them recognized as separate drives, you need to define each drive as a stripe, except you would have a 1 + 0 stripe instead of a 1 + 1 stripe. The drives are still connected the same way (Master/Slave) as you have them now. This congiguration would allow you to take advantage of the Ultra ATA 133 feature of that channel as long as you attached hard drives which support that standard.
    Finally, you would set the "Onboard Promise IDE" menu as "RAID" to have the drives properly recognized through the BIOS. Currently, you have that set as "S-ATA" but you have no S-ATA drives installed on that controller.
    I realize this does not resolve your original problem, but at this point, I would recommend that you back-up data at your earliest convenience and start over.
    If you do decide to start over, you may want to consider attaching your S-ATA drives to the promise controller instead of on the Intel controller. Aside from getting better performance, it makes for a much simpler install through the Promise controller utility and then everything is manageable through the PAM utility at the desktop.

  • Lines appears when boot win xp

    Hi friends
    I have macbook pro 17 inch with intel core duo2, when i start my computer in Win Xp a lines satured in blue appears horizontally in the displays, and its more critical when i use a background turned gray or clear color.
    Please anyone knows how repare
    it it will be very kind of you.

    same problem, no solution:
    http://discussions.apple.com/thread.jspa?threadID=1284396&tstart=15

  • Mkinitcpio problem when booting (plymouth not found) [SOLVED]

    I installed Arch very recently, but I'm having a bit of a problem with mkinitcpio. I cannot fully boot into my system.
    It's looking for Plymouth. I looked up Plymouth on the wiki, and it appears to be a graphical splash screen manager. The thing is I don't have this package installed or in my hooks/modules in my mkinitcpio.conf file, so there's no reason why systemd should even be looking for it.
    So I've done some searching for this issue, but I haven't found any threads that could solve my problem. The issue is systemd keeps looking for a binary that I don't have or specified, so I'm wondering what's going on.
    Is this a bug?
    Output of journalctl | tail -n 80:
    Nov 08 09:03:00 pc-main systemd[1]: Dependency failed for D-Bus System Message Bus.
    Nov 08 09:03:00 pc-main systemd[1]: Job dbus.service/start failed with result 'dependency'.
    Nov 08 09:03:00 pc-main systemd[1]: Dependency failed for Provides automatic netcfg wireless connection.
    Nov 08 09:03:00 pc-main systemd[1]: Job net-auto-wireless.service/start failed with result 'dependency'.
    Nov 08 09:03:00 pc-main systemd[1]: Job basic.target/start failed with result 'dependency'.
    Nov 08 09:03:00 pc-main systemd[1]: Dependency failed for Daily Cleanup of Temporary Directories.
    Nov 08 09:03:00 pc-main systemd[1]: Job systemd-tmpfiles-clean.timer/start failed with result 'dependency'.
    Nov 08 09:03:00 pc-main systemd[1]: Dependency failed for D-Bus System Message Bus Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Job dbus.socket/start failed with result 'dependency'.
    Nov 08 09:03:00 pc-main systemd[1]: Job boot.mount/start failed with result 'dependency'.
    Nov 08 09:03:00 pc-main systemd[1]: Job dev-disk-by\x2dlabel-pc\x2dmain\x2dboot.device/start failed with result 'timeout'.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped File System Check on /dev/disk/by-label/pc-main-boot.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Local File Systems (Pre).
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Local File Systems (Pre).
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Network.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Update UTMP about System Runlevel Changes.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Remount Root and Kernel File Systems...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Remount Root and Kernel File Systems.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Graphical Interface.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Multi-User.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Provides automatic netcfg wireless connection.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped D-Bus System Message Bus.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Login Service.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Login Prompts.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Getty on tty1.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Permit User Sessions.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Trigger Flushing of Journal to Persistent Storage.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Remote File Systems.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Remote File Systems.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Basic System.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping udev Kernel Device Manager...
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping LVM activation...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped LVM activation.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping udev Wait for Complete Device Initialization...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped udev Wait for Complete Device Initialization.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping udev Coldplug all Devices...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped udev Coldplug all Devices.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Sockets.
    Nov 08 09:03:00 pc-main systemd-journal[134]: Journal stopped
    Nov 08 09:03:00 pc-main systemd-journal[234]: Allowing runtime journal files to grow to 175.4M.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Delayed Shutdown Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Closed Delayed Shutdown Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping /dev/initctl Compatibility Named Pipe.
    Nov 08 09:03:00 pc-main systemd[1]: Closed /dev/initctl Compatibility Named Pipe.
    Nov 08 09:03:00 pc-main systemd[1]: Closed D-Bus System Message Bus Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target System Initialization.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Recreate Volatile Files and Directories.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Encrypted Volumes.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Encrypted Volumes.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Apply Kernel Variables...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Apply Kernel Variables.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Load Kernel Modules...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Load Kernel Modules.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Setup Virtual Console...
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Setup Virtual Console.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Swap.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped target Swap.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping Journal Service...
    Nov 08 09:03:00 pc-main systemd-journald[134]: Received SIGTERM
    Nov 08 09:03:00 pc-main systemd[1]: Starting Emergency Shell...
    Nov 08 09:03:00 pc-main systemd[1]: Started Emergency Shell.
    Nov 08 09:03:00 pc-main systemd[1]: Starting Emergency Mode.
    Nov 08 09:03:00 pc-main systemd[1]: Reached target Emergency Mode.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped udev Kernel Device Manager.
    Nov 08 09:03:00 pc-main systemd[1]: Stopped Journal Service.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping udev Kernel Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Closed udev Kernel Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Stopping udev Control Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Closed udev Control Socket.
    Nov 08 09:03:00 pc-main systemd[1]: Startup finished in 1s 243ms 842us (kernel) + 1min 30s 53ms 238us (userspace) = 1min 31s 297ms 80us.
    Nov 08 09:03:00 pc-main systemd[1]: Starting Journal Service...
    Nov 08 09:03:00 pc-main systemd[1]: Started Journal Service.
    Nov 08 09:03:00 pc-main systemd-journal[234]: Journal started
    Nov 08 09:03:00 pc-main systemd[231]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
    Nov 08 09:04:19 pc-main kernel: EXT4-fs (sdh1): mounted filesystem with ordered data mode. Opts: (null)
    Output of cat /etc/fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/mapper/pc--main--vg-pc--main--root UUID=fc3574ca-c8ea-4fbc-a6cb-9a36d145e6df
    /dev/mapper/pc--main--vg-pc--main--root / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 UUID=7f511c15-a179-46ec-9a4a-87018c958e5c
    LABEL=pc-main-boot /boot ext2 rw,relatime 0 2
    # /dev/mapper/pc--main--vg-pc--main--home UUID=1dd6085f-d42a-4b8d-8007-4958507893c2
    /dev/mapper/pc--main--vg-pc--main--home /home ext4 rw,relatime,nodev,nosuid,data=ordered 0 2
    # /dev/mapper/pc--main--vg-pc--main--tmp UUID=2cc1d3f6-a5d6-4566-9d4e-1fae76aa8bfa
    /dev/mapper/pc--main--vg-pc--main--tmp /tmp ext2 rw,relatime,nodev,nosuid 0 0
    # /dev/mapper/pc--main--vg-pc--main--var UUID=a5452d9f-4f94-4d93-b996-c7e3fdb20056
    /dev/mapper/pc--main--vg-pc--main--var /var ext2 rw,relatime,nodev,nosuid 0 2
    I am running Arch x86_64 with kernel 3.6.6-1.
    Last edited by mrrhq (2012-11-10 03:02:54)

    WonderWoofy wrote:
    I just masked the things that I don't use.  I think that included some kind of plymouth-wait, plymouth, and auditd.
    Edit: This has nothing to do with your question, but I noticed you have a /tmp partition.  Do yu actually need a persistent /tmp?  Or did you just do this because it is what you are used to doing?  Systemd includes a tmp.mount file that automatically puts it on a tmpfs.  I actually think it may even override what is in your fstab... though I have not tested this.  If you want to keep your persistent /tmp, you should disable tmp.mount or mask it as well.
    I don't know what you mean... because systemd shouldn't be looking for it. I'll scrounge around in my config files for systemctl/systemd and see if I can find anything.
    Yes, eventually I'm going to use dm-crypt+LUKS, so that the /tmp directory will be encrypted with random data (and possibly tmpfs). Since I wasn't comfortable trying to install Arch the first time, I wanted to make sure I would get it working with GRUB2, GPT and LVM first, so I'm going to do encryption after I get bootup working.
    Sorry to ask but how do I disable "tmp.mount"?
    I am new to systemd, but I've only gotten familiar with Debian's sysvinit.
    I just looked in the systemd page of the Wiki and didn't find anything.

  • 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.
    Thanks

    3mb3r4 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...

  • Problem when booting up PC- Adobe issue?

    Every time I boot up my laptop a get an error message (several actually) which, I believe is caused by Adobe. The message reads:
    "Runtime Error!
    Program: C:\Program Files(x86)\Adob........
    R6034
    An application has made an attempt tp load the C runtime library incorrectly. Please contact the application's support team for more information."
    I have deleted Adobe Reader and downloaded again but the problem still exists. Also I have had a couple crashes since this started.
    Any ideas??
    Not sure if this is the right place to raise this, as I tried contacting customer support and got sent here!?
    Thanks for any help

    I think that some of this "clean-up" may have solved the Adobe problems. I
    ran the CCleaner and found the following in the Registry
    HKCU:Run CAHeadless Adobe Systems Incorporated C:\Program Files
    (x86)\Adobe\Elements 10 Organizer\CAHeadless\ElementsAutoAnalyzer.exe
    I then disabled this line and haven't got the error message-   "C\Program
    Files (x86)\Adob...." (there is still one message left but doesn't have the
    "Adob..." bit, so probably a different file)
    I also had deleted Adobe Reader and Flash Player but will reload soon
    Thanks for your help
    will this be shown on the forum?I've had an email from Em-and-m about
    having the same problem
    Regards
    Peter

  • Help: IPOD service problem when installing in Vista

    Message reads something like Ipod Service did not start make sure you have sufficient permissions. It then gives the option to retry or cancel. This happens at some point in the installation process.
    I have among other things tried out all the steps outlined on the apple website, ensured I have admin access, created another admin account, msconfig, deleted completely all traces of Apple products even tried installing an earlier version all to no avail. I have contacted apple as well who though responsive were not much help either pointing me in the direction of well web links to manuals on the apple website. I also have SP1 installed. So My MS side of life is sorted.
    I am fed up and might just have to return my IPOD touch if no joy. This is probably my last chance to make this work. Unfortunate that what is presumably a lovely piece of kit is a nightmare simply because I don't use an apple machine.
    Alternatively can anyone suggest other ways to get this IPOD touch working other than Itunes. GGRRRRRRRRRRRRRRRRRRRRRH

    New developments:
    1) At the point in the installation where it tries to start services, I get an error message saying that IPOD Service did not start. Ensure you have enough permissions.
    2) I have done this using administrator account and even turned off Vista UAC all to no avail.
    3) I have also uninstalled with Windows install clean up like for the 20th time.
    4) Even when I do a clean uninstall and delete every trace of files and folders in other parts of the C:\ I stll find that IPOD service is listed and stopped. How is that possible?
    5) Any time I attempt to start IPOD service in task manager I get an error message saying Windows could not start the IPOD Service on Local Computer Error 2: The system cannot find the file specified.
    6) There are only two options available when it stalls in no.4 above ie. either to retry or to cancel. When you cancel it rolls back the installation.
    7) When I went to C:\Program Files folder there was no IPOD\bin folder and hence no IPOD Service folder.
    8) Yesterday I decided to circumvent the installation procedure by opening folder rather than opening the file. I was able to save a few IPOD and ITunes files which would not have been possible if I had selected cancel because when rolling back it deletes most of the vital folders and files.
    9) When I click on the Ipod service icon at this stage, nothing still happens. Also when I click on Itunes icon at this stage I get an error message saying some vital files are missing please reinstall.
    Is there a registry hack to resolve this issue? I am convinced that it is the only way to get me out of the doldrums. I must also mention that I have Vista service pack 1 intalled.

  • Problem when booting up

    Sometimes when my Macbook boots up it can't seem to target my internal hardrive. It just goes to a gray screen and not OS X. It's done this twice. Last time I was able to fix it by putting in my OS disk and reinstalling a couple programs. After doing this my mac was able to target the disk when I restarted. This time when I try and do the same thing not even the Mac OS X installer can find my internal hard drive. What the ****? Holding down command-x, d, during boot helps. I'm about to throw my macbook out the window, someone please help.

    Back up all your data first and boot up from the Mac OS X install disk. Launch Disk Utility and see if you can find the internal drive there. If you can, you might have to reformat and erase the disk. After that, restore all your files back.

  • Problems when use win 8.1 serial in win 10

    Hello.
    Today I did a clean install of windows 10.
    But when trying to activate using the key windows 8, originally from my machine, I could not.
    I called Microsoft who informed me that the clean copy is not possible. And I have to install the original version coming in the machine. But I do not have the CD / DVD this windows.
    I tried to restore using F11 to start the computer, but nothing happens.
    I wonder where can the original windows 8 of my machine to download.
    Grateful.

    What you don't know, and MS isn't really telling folks, is that the Upgrade version of Win10 will not accept any Win7/8/8.1 product keys for activation; instead, you have to do an in-place Upgrade first.  That Upgrade actually performs the activation so that after that, you can perform a clean reinstall to get rid of all the crud that carried over from the earlier OS. As to Recovery, you have to order a Recovery Media set from HP.  My laptop got trashed from the Win10 upgrade and I had to do that.  It cost me around $30 USD, and yours will probably be about the same.  But be advised, the Recovery Media reformats the entire drive, removing everything that is there -- data, settings, apps.  So, be sure to save off anything you want to keep before doing the Recovery.

Maybe you are looking for

  • ITunes Sharing between Accounts

    I have 2 accounts on my iBook and would like to be able to combine the libraries (so that when I'm in my account I can access music in the other account's iTunes library). Basically, I don't want to have to import all music twice and take up twice th

  • Adding a client to a collection is slow

    Or "Help me like SCCM 2012"! I like it in principle, but it seems awfully fragile. For instance, we had it deploying an OS image just fine. The consultant who put this functionality in place included a VB script to place newly imaged machines in to t

  • Xcode on OSX server

    I want to run xcode on one of my network accounts that is linked to OSX server.  When I ran a project on the network account it would not run the iphone simulator.   Not sure if this is a permissions issue. What is the best solution for this? Regards

  • Looking for LabVIEW & TestStand work in the Dallas/Fort Worth area.

    I am currently working in the Arlington, Tx. My contract will be up in mid September. I am wanting to stay either in the Dallas/Fort Worth area or in the southern U.S. Please view my resume if you are interested. Thank you Warren Arnold Attachments:

  • Nano wont get out of disk mode or show up in itunes

    i just got a replacement 2gb nano yesterday and it worked fine... this morning i turned on itunes and it didnt show up... also it seems to be stuck in disk mode... i tried resetting, it didnt work... i cant restore it cuz the updater says it wont mou