[SOLVED] Elementary OS Luna/Ubuntu based distro broken graphics after update
UbuntuThis forum is for the discussion of Ubuntu 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.
After rebooting the system it hung at the Elementary Splash Screen.
Rebooting again only gave the same result so we tried Ctrl + Alt + F2 and he signed in. I thought that the update broke the graphics (fglrx)
So in console mode he tried:
Code:
sudo ap-get install fglrx
Get http://us.archive.ubuntu.com/ubuntu/ precise-updates/restricted fglrx amd64 4 2:8 960- 0buntu1.1 [66.6MB
Get 2 http://us.archive.ubuntu.com/ubuntu/ precise-updates/restricted fglrx-amdccle amd64 2:8 960-0ubunt1.1 [5,924 kb]
Fetched 72.5 MB in 2 min 19s [59 kB/s]
Selecting previously unselected package fglrx
Reading database... 175515 files and directories currently installed
Unpacking fglrx (from.../fglrx_2%3a8.
960-0ubuntu1.1_amd64.deb
One or more files have been altered since installation
Uninstall will not be compleated
See /etc/ati/fglrx-uninstall.log for details
dpkg: error processing
/var/cache/apt/archives/fglrx_
2%3a8.960-0ubuntu1.1_amd64.deb
(--)unpack:
subprocess new pre-installation
script returned error exit
status 1
Selecting previously unselected package
fglrx-amdcccle
Unpacking fglrx-amdcccle (from...
/fglrx-amdcccle_2%3a8.960-
0ubuntu1.1_amd64.deb
Errors were encountered while processing:
/var/cache/apt/archives/
fglrx_2%3a8.960-0ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
I looked in the etc/ati/fglrx-uninstall.log
It said that the AMD Catalyst Proprietary Driver file is missing from the system.
To force uninstall, remove all installed file w/o verification, run:
/usr/share/ati/amd-uninstall.sh --force
Forcing uninstall is not reccommended and may cause system corruption.
This is not my computer but I need your help to help my friend.
Please advise as what we should try.
Ok I tried apt-get -f install and after that I tried apt-get upgrade again.
It just returns me to the same thing over and over again:
Code:
apt-get upgrade
Reading package lists... Done
You may want to run 'apt-get -f install' to correct these
The following packages have unment dependencies:
fglrx-amdcccle: Depends: fglrx but it is not installed
E: Unmet dependencies Try using -f
The easiest way to fix that would be to recover from the system backup you surely have made before adding an unsupported third party repository to this system, which is, as I get from the PM you sent me, a system your friend needs for his work.
If for whatever reason you don't have a backup start with running
Yes, TobiSGD that's right this Elementary OS distro is what he uses for his work.
Since the system hangs at the Elementary OS logo splash screen the only thing that worked was console mode only; unfortunately all the research and cmd's (dpkg -- configure -a & ap-get install -f) that I found online that others tried did not help.
I have given thought to locating the corrupt package (gvfs) and remove it along with removing the whole block of information about it and save the changes made in the /var/lib/dpkg/status. I did not do that because I wasn't sure if it was wise.
When class is over I will try dpkg --audit and work from there.
I hope to be able to fix this OS and if not I will have (as a last resort) to re-install it:-
The pressure is on me to fix this and so I'll soldier on-:-
Thank you for your help and advice it means alot to me during this stressful time.
The following have been unpacked but not yet configured
They must be configured using dpkg --configure or the configure menu in dselect for them to work:
fglrx-amdcccle
dpkg --configure
Type dpkg --help about installing and deinstalling packages[*]
Use 'deselect' or 'aptitude' for user friendly package management
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force -help for a list of forcing options
Type dpkg -deb --help for help about manipulating *.deb files
Options marked[*] produce a lot of output -pipe it through 'less' or 'more'
Aside from using the 'dpkg' or "dpkg --install" command what command should I use to fix this system?
These options are creating confusion for me...Is this what I need to do?
You will need to identify what changes YOU made and reverse them.
Start by checking the apt/dpkg logs in /var/log to see what was done.
It might be a good idea to NOT keep installing stuff to see if it works (i.e. if you are in a hole - STOP DIGGING!), rather, try to carefully back out to the working state it was in previously, then reflect on the wisdom of adding a 3rd party repo (for a different OS) to the sources of a "production" machine.
I tried as a super user to get into the /var/log and the apt/dpkg log.
I used cat /var/log to view it. BTW, the Elementary OS is in console mode now, no GUI is present.
Console mode returned no such file or directory.
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
Quote:
Originally Posted by descendant_command
There isn't "a command to fix this system".
You will need to identify what changes YOU made and reverse them.
Start by checking the apt/dpkg logs in /var/log to see what was done.
It might be a good idea to NOT keep installing stuff to see if it works (i.e. if you are in a hole - STOP DIGGING!), rather, try to carefully back out to the working state it was in previously, then reflect on the wisdom of adding a 3rd party repo (for a different OS) to the sources of a "production" machine.
Apt has been complaining that packages have unmet dependencies which is referring to the fglrx-amdcccle which depends on the fglrx-driver.
I (think) that has been the problem from the start.
The owner moved the amd.run (the script for the driver)file into the trash bin.
This was the AMD Catalyst Proprietary Linux Driver from the AMD website.
Which, correct me if I am wrong; is not the same as the fglrx_2%3a8.960-0buntu1.1_amd64.deb that's coming from the /var/cache/apt/archives-:-
Using the 'dpkg --audit" cmd that TobiSGD advised me to use makes it clear that the package is unpacked but not configured. Using "dselect" (unless I misunderstand, is the way to manage this unpacked yet unconfigured pkg) however: this is not an option because for one it (dselect) is not installed and when I attempt to install it doesn't work because the dependency problem is in my vision again.
Code:
The following packages have unmet dependencies:
fglrx-amdcccle: Depends: fglrx but it is not installed
E: Unmet dependency Try using -f
So you have installed the binary driver from AMD's website and the package from the repositories? There you go, now you know why it is recommended to not use the installer, but the driver from the repositories, unless you know what you are doing. In no case ever use both at the same time. Remove that package, remove the binary drivers from the installer (I don't have them installed, but there should be an uninstall script somewhere, maybe in /usr/share/ati or something similar), so that you at least have a working system with the free driver, then proceed from that point on.
So you have installed the binary driver from AMD's website and the package from the repositories? There you go, now you know why it is recommended to not use the installer, but the driver from the repositories, unless you know what you are doing. In no case ever use both at the same time. Remove that package, remove the binary drivers from the installer (I don't have them installed, but there should be an uninstall script somewhere, maybe in /usr/share/ati or something similar), so that you at least have a working system with the free driver, then proceed from that point on.
I wasn't sure if the AMD driver was installed. He is having trouble remembering if he installed the AMD driver or not. So; I checked with nano /usr/share/ati
the file opened in nano and the screen was blank. Nothing was in that file.
Is an empty file an indication that there is not a script & the driver is 'not installed' ?
If I use the Live Elementary OS DVD will it override the current installed fs?
(or) will it restore what he already has?
/usr/share/ati (id that is the correct name, I don't use the proprietary driver) should be a directory, not a file. It seems that nano always shows an empty file when you try to open an existing directory, a quite nonsensical behavior, IMHO.
Please specify what you actually want to do with the Elementary DVD.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.