Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
the console kept giving an error , something about trying sudo apt-get -f install (without a package)
I gave up in the end but on restarting Mint wont load any more (just get a flashing cursor on black screen). I can get the grub and I tried all the repair options in the recovery menu but dpkg is showing that same error and i have no idea what to do anymore
I keep trying and trying to replace windows with linux but soooo many problems i spent months trying to get everything to work as i would expect/need and i was almost getting somewhere.
That shouldn't break anything. Have you done a recent "apt-get update && apt-get upgrade"? Maybe your system was working off of an old package listing.
You should really pay more attention to the error messages. We need to know exactly what it said in order to help (you'll also need to know exactly what it said in order to search the web for solutions).
nop that was the only command i used , it showed an error , i searched it to no avail then rebooted.
well i did search the error at the time (before rebooting) but i cant get back into mint to see what the exact error was now , i shall boot the repair and pen&paper the error from there as its very similar. brb
When is the last time you did an apt-get update and upgrade?
Sometimes when you install a piece of software using the central package manager (apt-get in your case) it breaks other functionality by bringing in newer, conflicting versions of libraries. For that reason on Linux you should always make sure your system is up to date before using the package manager to install any new software.
Last edited by suicidaleggroll; 08-25-2015 at 02:34 PM.
From your first post it sounds like your command didn't actually do anything, it just immediately threw an error and stopped. That tells me that the problem already existed and that was simply the first time you saw any symptoms of it. Had you done anything else on the system before that, especially related to libgl?
What happens if you run "sudo apt-get update && sudo apt-get upgrade" from the console? What happens if you try to install one of those packages that it's complaining about?
Well something definitely got borked in whatever else you were doing on the system. I highly doubt any of this is related to the python installation command you ran...it has to be from something earlier.
Maybe look back through /var/log/apt/history.log or /var/log/dpkg.log to see if something there jogs your memory.
As for how to fix it...I would start by just installing all of these packages that it's complaining about, though I'm not sure why apt-get's dependency resolution isn't picking them up automatically. I don't use deb based distributions often and don't have much experience with apt-get.
its all just a bit much for me , i did not do anything other than follow simple installation instructions and bam :-/ . I tried putting in the installation disk to see if i could do a re-install but of course i then remember that live boot DVD's dont work on my comp because of UEFI (it was one of the major problems i spent ages on resolving, then the screen tearing problem took ages too then ... ahh well you get the idea) , i may create a usb stick later , we shall see.
Is this a brand new machine? It shouldn't be this big of an issue to get things running, unless this machine uses bleeding edge or otherwise abnormal hardware. If so, you may want to try a distro with more up-to-date support, at least until the hardware has been out for a while and the LTS distros catch up.
As for UEFI, you should be able to just disable secure boot in the BIOS, unless Windows is forcing you to keep it around.
Last edited by suicidaleggroll; 08-25-2015 at 04:48 PM.
well its quite new and the Nvidia card is pretty new too.
well i suppose all this knowledge is ok in retrospect but we all start out somewhere :-/
I ill prob do a new install , at least i know most of the things i have to do to get around most of the problems but its just the way it dies from nothing really. Im desperately trying to get away from windows but at least everything just works (video cards , printers, boot sectors, web cams etc (even the shutdown button stopped working on mint17.1 at one point, i found it was a common problem, jess)).