You are not logged in.
Hi guys. New arch user here, but not necessarily a new linux user. (Been running ubuntu variants for about a year) Naturally, the first thing I try to do is get steam going, after installing the proprietary catalyst drivers and getting cinnamon going. But of course, pacman gives me this output:
[root@localhost ~]# pacman -S steam
resolving dependencies...
:: There are 3 providers available for lib32-libgl:
:: Repository multilib
1) lib32-mesa-libgl 2) lib32-nvidia-304xx-utils 3) lib32-nvidia-libgl
Enter a number (default=1): 1
looking for inter-conflicts...
Packages (27): lib32-bzip2-1.0.6-1 lib32-dbus-1.6.14-1 lib32-elfutils-0.156-1
lib32-expat-2.1.0-1 lib32-gcc-libs-4.8.1-3
lib32-glib2-2.36.4-1 lib32-libdrm-2.4.46-1
lib32-libffi-3.0.13-1 lib32-libgcrypt-1.5.3-1
lib32-libgpg-error-1.12-1 lib32-libpciaccess-0.13.2-1
lib32-libx11-1.6.2-1 lib32-libxau-1.0.8-1 lib32-libxcb-1.9.1-1
lib32-libxdamage-1.1.4-1 lib32-libxdmcp-1.1.1-1
lib32-libxext-1.3.2-1 lib32-libxfixes-5.0.1-1
lib32-libxxf86vm-1.1.3-1 lib32-llvm-libs-3.3-1
lib32-mesa-9.2.0-1 lib32-mesa-libgl-9.2.0-1 lib32-pcre-8.33-1
lib32-systemd-207-1 lib32-xz-5.0.5-1 lib32-zlib-1.2.8-1
steam-1.0.0.42-1
Total Installed Size: 69.87 MiB
:: Proceed with installation? [Y/n] y
(27/27) checking keys in keyring [######################] 100%
(27/27) checking package integrity [######################] 100%
(27/27) loading package files [######################] 100%
(27/27) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
lib32-mesa-libgl: /usr/lib32/libGL.so exists in filesystem
lib32-mesa-libgl: /usr/lib32/libGL.so.1 exists in filesystem
Errors occurred, no packages were upgraded.
Any help on this one? I did install the open-source driver before installing cinnamon because installing the catalyst drivers from ATI is easier with a GUI, but I made sure to uninstall the open-source version before installing the catalyst. Also probably irrelevant but I feel is worth noting, I made sure to enable the 32-bit repositories because of experiences with Ubuntu where direct rendering for steam doesn't work unless 32-bit libraries are installed before the catalyst driver.
I'm tempted to just delete /usr/lib32/libGL.so and its '.1' brother just to see what happens, but that's a scary, scary thought.
Offline
If you're using catalyst drivers, you don't want mesa libgl. How did you install the catalyst drivers? Please tell me you didn't install them outside of pacman
Online
I did install them outside of pacman. I'm used to going strait for AMD's own binary file. Is this something where I can exit out of x, uninstall the catalyst driver and reinstall using pacman, allowing pacman to automatically resolve dependencies?
I guess that also leads me to wonder whether or not I can get my hands on the most recent beta if I install in pacman. It may be worthwhile to stay with the stable release, but seeing as AMD drivers are lagging so badly, I like to have the latest thing I can possibly have.
Last edited by tomsloan (2013-09-30 04:32:10)
Offline
https://wiki.archlinux.org/index.php/Catalyst
Anything that goes in /usr (except /usr/local/) needs to be put there by pacman. As it stands, you have lib32-libgl installed, but pacman has no idea it's there.
Last edited by Scimmia (2013-09-30 04:33:27)
Online
Ok, so here's what I've done: removed the proprietary driver, exited x, removed Mesa-libgl as well as all its dependencies and those which depend on it, then I installed the proprietary driver using the unnofficial repo, had another go at installing steam, and now I get the same error except it says "/usr/lib32/dri exists in file system".
Is this the point at which I start over with a fresh install of arch? I've only been running this one for two days, so I'm really thinking it'd be a big deal to start over, but if there's a legit fix for this, I'd like to do that.
Offline
it says "/usr/lib32/dri exists in file system".
Read https://bbs.archlinux.org/viewtopic.php?id=130138
Last edited by karol (2013-09-30 15:21:46)
Offline
We need more information. Is it still trying to install mesa-libgl?
Online
No, no more issues with mesa-libgl. I used the information in Karol's link to fix the issue with /usr/lib32/dri, which allowed steam to install. But after that, I couldn't get x to start. So, I decided to start all over and create another arch install. Of course, I'm still having issues with x on the new install, but that's an issue for a different subforum (in fact, I'm not entirely conviced this thread belongs in this subforum) so I'll happily mark this thread as resolved.
Thanks for the help!
Offline
If you can't figure out how to mark this thread as solved, read https://bbs.archlinux.org/viewtopic.php?id=130309 :-)
Offline