Ubuntu This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
10-11-2011, 09:46 AM
|
#1
|
LQ Newbie
Registered: Sep 2011
Location: Tokyo, Japan (since 1979).
Distribution: Ubuntu
Posts: 15
Rep:
|
How do you fix broken packages when Synaptic is unable to?
Hi, again!
I noticed I had some 866 updates to install from the Update Manager, so I clicked install. It says fix the broken packages first. I go to Synaptic and click the fix button in Edit. Sorry, no can do. My system is holding onto something that's broken, that has to be fixed first. But it can't be fixed because I'm holding onto it. A real Catch-22. What does a sane human being do in this dilemma?
|
|
|
10-11-2011, 10:18 AM
|
#2
|
Senior Member
Registered: Jul 2009
Location: Virginia
Distribution: Debian Stable Testing Sid Slackware CentOS
Posts: 1,055
Rep:
|
You could try a command line:
Second one, -f = fix
|
|
1 members found this post helpful.
|
10-12-2011, 01:07 AM
|
#3
|
LQ Newbie
Registered: Sep 2011
Location: Tokyo, Japan (since 1979).
Distribution: Ubuntu
Posts: 15
Original Poster
Rep:
|
Thanks, man! I'll give it a whirl!
|
|
|
10-18-2011, 02:31 AM
|
#4
|
Member
Registered: Feb 2011
Distribution: Ubuntu 10.04, Debian Squeeze
Posts: 46
Rep:
|
If packages are still broken after the above "apt-get install -f" and you have added additional repositories, there is always the possibility that the repositories contain conflicting packages. This can be a bit of a pain. When I suspect this problem, I typically go in and disable my extra repo's and then run "apt-get update && apt-get upgrade", or something along those lines.
Hope this helps.
|
|
1 members found this post helpful.
|
04-30-2017, 10:23 PM
|
#5
|
Member
Registered: Apr 2017
Location: The Sierra Nevada above Sacramento
Distribution: Kali and AVLinux, seems I lean towards the Debian side of things
Posts: 61
Rep:
|
Quote:
Originally Posted by countach74
If packages are still broken after the above "apt-get install -f" and you have added additional repositories, there is always the possibility that the repositories contain conflicting packages. This can be a bit of a pain. When I suspect this problem, I typically go in and disable my extra repo's and then run "apt-get update && apt-get upgrade", or something along those lines.
Hope this helps.
|
Thank you. I had the same issue as the OP and was set scrap the install and start over, but pointing to the sources.list file led to solving the problem for me. I just turned each repository off one at a time until the issue was no more. So, again, thank you
|
|
|
All times are GMT -5. The time now is 01:44 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.
|
Latest Threads
LQ News
|
|