Started off with just being an issue with steam; of course my PC doesn't want to be nice to mutliarch does it.
Linux - GamesThis forum is for all discussion relating to gaming in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Started off with just being an issue with steam; of course my PC doesn't want to be nice to mutliarch does it.
Alright, so I am just installing steam. A while ago, I thought I fixed everything; I forgot what the issue was, but I solved it by finding a package with "i386" in the name.. It was the same package of what I needed but in 32bit so steam wouldn't wine (pun intended.. though I'm not using wine) to me. Anyways, I you know go to open it. I havn't really opened it up yet, just have been using windows. Anyways, it tells me
Code:
You are missing the following 32-bit libraries, and Steam may not run:
libGL.so.1
Press enter to continue:
Okay, so I manage to figure out that I need some various stuffs -
libgl1-mesa-dri:i386
libgl-mesa-glx:i386
or as someone on the Internet said libgl1-nvidia-glx:i386. Though for now, those details aren't too important - I hope.. So, back to other stuffs. I goto install those - and all these packages "have no installation canidate".. Yay! Next - lets see, make sure we got multiarch up correct? Okie dokies
Code:
// Yeah I work in root. I know it "is a bad habit". Oh well, I for some reason every time I add myself
//to sudoers file it opts to go "no-no this doesn't work. I presume you have had the usual lecture. blah
//blah.. system admin .. boils down. blah blah .. this incident will be reported" Anyways, help with
//that would be nice, but in the end I can just google it later.
~# dpkg --add-architecture i386
~# dpkg --add-architecture i368
// I can never recall which one 32bit is.. So I just did both. I am pretty sure 368. Anyways, I just did // both for everything.
~# apt-get update
Okie dokies - no troubles right? Running out of ideas? Googlable fixes? Nonsense! I'll just add ubuntu repos to my debian system right? No, that didn't work out. It just gave me some error I don't care for right now. So, this is where I am currently at - clueless as to why all my packages only support AMD64 except like 2. (Seriously, if I do "apt search lib | grep i386" I get two results. Two. 2. dos.).
First, I am in middle school - Not a sysadmin. Just a kid trying to weave through the outdated mess of packages debian calls stable.
Second, I am sure there is an XKCD comic that perfectly explains how I am feeling rn. I am confident there is.
32-bit is 386. However you shouldn't normally have to add it as an architecture as it will be automatically handled as a foreign architecture.
However, to be honest, you are completely correct when you say that running as root is a bad idea. It will not only get you into trouble but it will also instil you with bad habits (it's important to be able to distinguish between user-land and root-land).
So I'd prefer, if I could, to do the following:
. get your user/sudoer problem sorted out.
. get the architecture problem sorted out and make sure your packages are up to date and in good shape.
. solve the Steam problem.
If you're up for it, please let me know which distro (and version) you're running (always an important piece of information!).
Oh sorry, I completely neglected to do that.. I kinda got lost in my frustration. Anyways, I am running Debian Jessie or 8.6 to be a little more exact. (My Internet is horrible. I have "apt-get --dist-upgrade" (or the correct command if that isn't. I just know what I tossed in cron is..) so I hardly upgrade as sometimes I am on windows the first.
No problem. I'm using Mint 18.1 so you'll need to forgive me if I'm not aware of any Debian-specific issues. However, most things should be the same with the two systems.
Firstly, I'm assuming that you're actually logging on to the system as a user, not as root. Please let me know if that isn't the case.
Can you please run and paste the output from:
whoami
followed by
sudo bash (you will be asked for your user password)
So, I guess that is sorted out. I don't know whether I call it luck that these things spontaneously start working for me, or just make me look plain out stupid.
The fact that you're running Linux shows you're not stupid.
That's good. So, from now on, if you want to do something as root on the command line, use sudo command.
If you want to run a GUI program from the command line as root, use gksudo program (it would be kdesudo program if you were running KDE).
In addition, I would recommend that if you want to do some extended root work, that you either use sudo bash, as you did above, and/or on a GUI-level, start up your file manager with gksudo (in my case, gksudo caja). Other people would recommend other ways of working in root, but I personally tend to use sudo unless I have extended work to do, in which case I use these methods.
Ok, to the packages. Can you please paste the output from:
(Don't ask how I got asprin@Murica. Also, while you're at it, take a look at my background image. I took it after borrowing a camera that I presume with the lense costed a few thousand.. Quality has been reduced. The camera is still a few years old.)
Last edited by TheLinuxCake; 03-11-2017 at 08:53 AM.
(Don't ask how I got asprin@Murica. Also, while you're at it, take a look at my background image. I took it after borrowing a camera that I presume with the lense costed a few thousand..)
Nice picture.
Ok, let's delete that extraneous foreign architecture (it shouldn't cause any harm being there but we may as well make things tidy).
sudo dpkg --remove-architecture i368 (please make sure that it is the '68' version that you remove here).
Then let's check to see which repositories you have:
# jessie
deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb http://mirrors.kernel.org/debian/ jessie main contrib non-free
deb-src http://mirrors.kernel.org/debian/ jessie main contrib non-free
# jessie/updates
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
deb http://mirrors.kernel.org/debian/ jessie-updates main contrib non-free
deb-src http://mirrors.kernel.org/debian/ jessie-updates main contrib non-free
#Multimedia non-free
#deb ftp://ftp.deb-multimedia.org jessie main non-free
#deb ftp://ftp.deb-multimedia.org jessie main
#
deb http://repository.spotify.com stable non-free
deb [arch=amd64,i386] http://repo.steampowered.com/steam/ precise steam
deb-src [arch=amd64,i386] http://repo.steampowered.com/steam/ precise steam
You should remove the deb and deb-src lines that refer to http://mirrors.kernel.org..., both here and further down where the same thing happens again for jessie-updates, unless this is some strange Debian thing that I don't know about.
I think you should also comment out the steam and spotify repos for the moment, by putting a # before the relevant lines - we can re-enable them afterwards.
To edit these files, use e.g. gksudo gedit /etc/apt/sources.list (this assumes that gedit is your editor of choice - replace it with another editor if necessary). I'm not sure whether Debian keeps all the sources in the one /etc/apt/sources.list file or also in fragment files in the sources.list.d directory, but you can determine that.
First of all, for sources I use nano because.. I guess I don't like having terminal be a log to something - I just like using it. Anyways, steam & spotify are in sources.d.
Okie dokie, so instead of removing those lines, I commented then out because I am really lazy; shouldn't matter. Anyways, here is my current lists:
"Really lazy" can lead to confusion in the future. By all means comment out stuff if you want to see if the change works first or you may uncomment then again in the future, but if you don't need something, you should get rid of it. Keeping things tidy and organised makes maintaining your system so much easier. In my opinion.
So, let's update:
sudo apt-get update
followed by
sudo apt-get upgrade
Only go through with the latter command to do the actual updates if there are no warnings from both commands.
Okay. That was.. odd.. It needed to get 0 bytes / 73mb of archives.. Downloads nothing. Anyways, that is all up-to-date. Edit: I have no clue what was going on; my PC thought it was connected to the Internet and thought it was down all at the same time. Mmmm. Okie dokie, replug that ethernet.. seems to be all good, Internet is fully up again. I repeat process, and no updates so I guess it is all good?
Edit:
Wow! I think it is going through! Maybe it was the false arch being removed (I doubt it), who knows maybe repos? I doubt it.. Most likely upgraded packages. Anyways, I am able to intsall the i386 version of the libGL1 packages I need. Hopefully this will resolve my issues, but who knows with my "insanely good" luck.
Last edited by TheLinuxCake; 03-11-2017 at 02:53 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
