Linux Lite Forums
Software - Support => Installing Software => Topic started by: gaas on April 06, 2024, 10:07:33 AM
-
Every time i try to install something i get this error : E: Dipendenze non soddisfatte. Provare "apt --fix-broken install" senza pacchetti (o specificare una soluzione)
how do i fix it?
-
The error message is indicating that the package manager (apt) cannot work because it has detected a conflict in package dependencies.
For example, one package may require a certain version of a library package while another package requires a different version of the same library.
Running the suggested command with the --dry-run option should show what apt will try to do the attempt the fix.
sudo apt --fix-broken install --dry-runIf you post back with the results it may show us the problem.
If it is more complex (o specificare una soluzione) it will be necessary to try to fully understand how the conflict has been caused.
Once that is understood, it may need low-level commands to try to resolve the conflict.
This can get complicated.
Do you have a System Restore point (aka timeshift) made before the conflict ?
-
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze... Fatto
Lettura informazioni sullo stato... Fatto
Correzione delle dipendenze... Fatto
I seguenti pacchetti aggiuntivi saranno inoltre installati:
linux-tools-common
1) I seguenti pacchetti NUOVI saranno installati:
linux-tools-common
0 aggiornati, 1 installati, 0 da rimuovere e 255 non aggiornati.
2 non completamente installati o rimossi.
Inst linux-tools-common (5.15.0-101.111 Ubuntu:22.04/jammy-updates, Ubuntu:22.04/jammy-security [all])
Conf linux-tools-common (5.15.0-101.111 Ubuntu:22.04/jammy-updates, Ubuntu:22.04/jammy-security [all])
Conf linux-tools-5.15.0-82-generic (5.15.0-82.91 Ubuntu:22.04/jammy-updates, Ubuntu:22.04/jammy-security [amd64])
Conf linux-tools-5.15.0-82 (5.15.0-82.91 Ubuntu:22.04/jammy-updates, Ubuntu:22.04/jammy-security [amd64])
2) no i didn't made a restore point.
-
What package are you trying to install from the command line ?
-
I'm trying to install obs studio, but this error happens with every package that i try to install.
-
https://itsfoss.com/install-obs-ubuntu/ (https://itsfoss.com/install-obs-ubuntu/)
It's a Debian package.
TC
-
Problem happens also with debian packages
-
I've used OBS Studio for a long time on Linux Lite 6.x. I installed it from Lite Software though.
Can you give me the syntax you are using so I can try installing it on a test set up in the same way as you.
-
I used this command
sudo apt install obs-studio (i get the error with every program that i try to install)
and got this error
E: Dipendenze non soddisfatte. Provare "apt --fix-broken install" senza pacchetti (o specificare una soluzione).
-
OBS-studio installs fine for me on a test system using the command line.
linux-tools-common isn't a dependency for obs-studio
When did your problem start ?
Can you recall what triggered it ?
Have you installed or tried to install any performance tools ?
If this is a fairly new set up you may want to consider starting again.
-
Yes i installed a software called "powerctrl" to get performance, maybe this is why i get the error? And if it is, how do i delete the software?
-
my problem started yesterday
-
Yes i installed a software called "powerctrl" to get performance, maybe this is why i get the error? And if it is, how do i delete the software?
linux-tools-common is associated with system monitoring applications so it is possible. We need to know what you did.
I'm not familiar with powerctl. Do you have any links to the method you used to install ?
Any reputable software should give instructions on how to uninstall and also show what packages it needs (dependencires)
my problem started yesterday
Did your problems start after the powerctl installation ?
If you can directly attribute the problem to the powerctl install AND confirm powerctl uses linux-tools-common then either
1) try the command 'sudo apt --fix-broken install' as we did before without the '--dry-run' option.
2) uninstall powerctl
-
Yes i installed a software called "powerctrl" to get performance, maybe this is why i get the error? And if it is, how do i delete the software?
linux-tools-common is associated with system monitoring applications so it is possible. We need to know what you did.
I'm not familiar with powerctl. Do you have any links to the method you used to install ?
Any reputable software should give instructions on how to uninstall and also show what packages it needs (dependencires)
my problem started yesterday
Did your problems start after the powerctl installation ?
If you can directly attribute the problem to the powerctl install AND confirm powerctl uses linux-tools-common then either
1) try the command 'sudo apt --fix-broken install' as we did before without the '--dry-run' option.
2) uninstall powerctl
1) I installed it by a youtube tutorial i don't remember what video
2) i can't really tell if powerctrl caused the problem, but i will try to delete it and see if the problem persists
-
I tried to run the command but it gave me an error :
dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/linux-tools-commo
n_5.15.0-101.111_all.deb (--unpack):
tentata sovrascrittura di "/usr/bin/acpidbg" presente anche nel pacchetto linux
-intel-iotg-tools-common 5.15.0-1051.57
dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Broken p
ipe)
Si sono verificati degli errori nell'elaborazione:
/var/cache/apt/archives/linux-tools-common_5.15.0-101.111_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
maybe i should reinstall linux :( ?
-
It looks like the (o specificare una soluzione) is required.
The powerctl install is a possible suspect but we need the timeline or more details about powerctl to be sure.
You could check your cli history to see what commands were run to install.
There is a danger in trying to resolve without knowing the problem will make things worse.
Unless someone else has insight then re-installing may be the best choice and the quickest way of getting to a stable system
Consider using 'System Restore Utility' and 'Backups' when building a new system to save time if things go wrong.
-
It looks like the (o specificare una soluzione) is required.
The powerctl install is a possible suspect but we need the timeline or more details about powerctl to be sure.
You could check your cli history to see what commands were run to install.
There is a danger in trying to resolve without knowing the problem will make things worse.
Unless someone else has insight then re-installing may be the best choice and the quickest way of getting to a stable system
Consider using 'System Restore Utility' and 'Backups' when building a new system to save time if things go wrong.
And how do i do that?
-
And how do i do that?
Not sure which bit of the post you are asking about.
o specificare una soluzione
Is a reference to the fact that the command that apt suggested can't resolve the problem.
That means we have to work out what is wrong and specify a solution to get apt or dpkg to correct the situation.
This is proving difficult.
You could check your cli history to see what commands were run to install.
This assumes you used the command line to install powerctl.
If you did, open a terminal by pressing 'Ctrl' Alt' and 'T' together
In the window that opens enter the command
historyfollowed by enter. This will list the most recent commands entered on CLI.
Scrolling back through the list may show the command(s) used to install the powerctl software - provided you haven't used too many commands since installing or cleared the history.
-
And how do i do that?
Not sure which bit of the post you are asking about.
o specificare una soluzione
Is a reference to the fact that the command that apt suggested can't resolve the problem.
That means we have to work out what is wrong and specify a solution to get apt or dpkg to correct the situation.
This is proving difficult.
You could check your cli history to see what commands were run to install.
This assumes you used the command line to install powerctl.
If you did, open a terminal by pressing 'Ctrl' Alt' and 'T' together
In the window that opens enter the command
historyfollowed by enter. This will list the most recent commands entered on CLI.
Scrolling back through the list may show the command(s) used to install the powerctl software - provided you haven't used too many commands since installing or cleared the history.
I found out that after i installed "cpufrequtils" i couldn't install apps, is there a way to delete this?
this is the commands that i used :
171 apt-get install cpufrequtils
172 apk add cpufrequtils
173 sudo apt install cpufrequtils
then i got the error, and tried to fix it
174 apt --fix-broken install
-
If running the install for cpufrequtils was the first installation that gave you the error, then it is likely that something you did before actually caused the problem.
So cpufrequtils may not be the problem - I think it only installs one other package called libcpufreq0.
If you don't want it and can't find other instructions to remove it, this may work.
sudo apt remove cpufrequtils
-
If running the install for cpufrequtils was the first installation that gave you the error, then it is likely that something you did before actually caused the problem.
So cpufrequtils may not be the problem - I think it only installs one other package called libcpufreq0.
If you don't want it and can't find other instructions to remove it, this may work.
sudo apt remove cpufrequtils
sudo apt remove cpufrequtils
[sudo] password for gaas:
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze... Fatto
Lettura informazioni sullo stato... Fatto
Il pacchetto "cpufrequtils" non è installato e quindi non è stato rimosso
È utile eseguire "apt --fix-broken install" per correggere ciò.
I seguenti pacchetti hanno dipendenze non soddisfatte:
linux-tools-5.15.0-82 : Dipende: linux-tools-common ma non sta per essere installato
E: Dipendenze non soddisfatte. Provare "apt --fix-broken install" senza pacchetti (o specificare una soluzione).
:60:
-
I may just reinstall linux at this point :'(
-
Hi!
I've been watching the development of this thread. (Sorry for using English, my primary language is Română and my Italian is way below requirements...)
Now, there are some facts I'm familiar with:
1. The cpufrequtils utility.
This is easy to replace, since it does little to help you. It's main goal is to show the CPU load. Forget about overclocking. It's about a lot of things that usually go sideways, and you might even get your CPU/Video fried out if you overclock. You can do CPU monitoring using other programs. I recommend you use the "System Monitor" app (Menu> System> System Monitor.) The App has been tweaked by Jerry and it works fine on lots of machines, has a nice GUI and offers enough information regarding the CPU load, Video, Memory, etc.
Alternately, you can install "htop". It's a tiny CLI utility that gives you a bunch of information regarding the system.
You can use the following to install it:
sudo apt install htop
Post - installation, you can then type in Terminal htop and it displays you a semi-graphic interface (like Midnight Commander, ncurses) with lots of dynamically updated info.
You can close it by pressing the F10 key, or clicking on the F10 button on the interface.
2. The libcpufreq0 library.
I did this and here is what I got:
apt search libcpufreq0
Sorting... Done
Full Text Search... Done
libcpufreq0/jammy 008-2build1 amd64
shared library to deal with the cpufreq Linux kernel feature
Are you shure you have the full expertise to tinker with the Linux Kernel?
I doubt I have it, after more than 12 years of using Linux on a daily basis and more than 29 years of computer practice.
But... Wo am I to say what is wrong or what is right?
I just say I want a peaceful life with my computer, so I stay away from things that are way above "my paygrade". ;)
And so far, I could manage to do so!
3. Fixing broken packages.
I usually go like that:
Lite Tweaks (Menu> Search "Lite tw...", click on the menu item "Lite Tweaks").
In the Lite Tweaks window, select the checkbox beside the item "Package System Repair". I had some trouble over the years so I used it a few times and it did a great job, spearing me of a full install job. I've done installations maybe thousands of times, but still... it takes at least 100 minutes from start to end. So, why would I go on this path, instead of a two minutes or less job?
I discovered that after issuing the "fix-broken" option, you need to issue the:
sudo apt update
It seems that sometimes, after cleaning the system with that, some residual files still point to the old packages configuration and I presume that this leads to some new error messages during "apt upgrade".
Anyway, applying this workaround, never got me into trouble again.
I hope that will help you get things done!
Best regards, Șerban.
-
Hi!
I've been watching the development of this thread. (Sorry for using English, my primary language is Română and my Italian is way below requirements...)
Now, there are some facts I'm familiar with:
1. The cpufrequtils utility.
This is easy to replace, since it does little to help you. It's main goal is to show the CPU load. Forget about overclocking. It's about a lot of things that usually go sideways, and you might even get your CPU/Video fried out if you overclock. You can do CPU monitoring using other programs. I recommend you use the "System Monitor" app (Menu> System> System Monitor.) The App has been tweaked by Jerry and it works fine on lots of machines, has a nice GUI and offers enough information regarding the CPU load, Video, Memory, etc.
Alternately, you can install "htop". It's a tiny CLI utility that gives you a bunch of information regarding the system.
You can use the following to install it:
sudo apt install htop
Post - installation, you can then type in Terminal htop and it displays you a semi-graphic interface (like Midnight Commander, ncurses) with lots of dynamically updated info.
You can close it by pressing the F10 key, or clicking on the F10 button on the interface.
2. The libcpufreq0 library.
I did this and here is what I got:
apt search libcpufreq0
Sorting... Done
Full Text Search... Done
libcpufreq0/jammy 008-2build1 amd64
shared library to deal with the cpufreq Linux kernel feature
Are you shure you have the full expertise to tinker with the Linux Kernel?
I doubt I have it, after more than 12 years of using Linux on a daily basis and more than 29 years of computer practice.
But... Wo am I to say what is wrong or what is right?
I just say I want a peaceful life with my computer, so I stay away from things that are way above "my paygrade". ;)
And so far, I could manage to do so!
3. Fixing broken packages.
I usually go like that:
Lite Tweaks (Menu> Search "Lite tw...", click on the menu item "Lite Tweaks").
In the Lite Tweaks window, select the checkbox beside the item "Package System Repair". I had some trouble over the years so I used it a few times and it did a great job, spearing me of a full install job. I've done installations maybe thousands of times, but still... it takes at least 100 minutes from start to end. So, why would I go on this path, instead of a two minutes or less job?
I discovered that after issuing the "fix-broken" option, you need to issue the:
sudo apt update
It seems that sometimes, after cleaning the system with that, some residual files still point to the old packages configuration and I presume that this leads to some new error messages during "apt upgrade".
Anyway, applying this workaround, never got me into trouble again.
I hope that will help you get things done!
Best regards, Șerban.
Can you explain in simpler terms please? I'm pretty new to Linux.
-
[...]
Can you explain in simpler terms please? I'm pretty new to Linux.
OK. I got it. I'll see what I can do. Now, I'm pretty tired and it's late here.
I need to (re)think it differently, and it takes some time.
Best regards!
-
[...]
Can you explain in simpler terms please? I'm pretty new to Linux.
OK. I got it. I'll see what I can do. Now, I'm pretty tired and it's late here.
I need to (re)think it differently, and it takes some time.
Best regards!
Ok, take your time. :)
-
Hi!
First question you need to answer:
What is the goal you are aiming at with cpufrequtils?
In other words: What do you expect to get from it? What real problem you want to solve using this program?
Defining very clearly what you want to get, increases the available choices to do it.
There are lots of programs that do basically the same thing (serve the same purpose).
Choosing the best, bolis down to what do you know to do with it.
Making it simple:
It is unlikely that you will be able to comb your hair, using your shoes. You need a comb to do that.
As a final touch:
Knowing what to do with whatever piece of software, means:
- How do I install it?
- How do I uninstall it?
- How can I use it?
- What kind of trouble can I get into using it?
- How do I fix the system in case it breaks down?
Still! Nobody knows everything about everything.
It applies to me, to you, to anybody on this Forum, including Jerry.
Yet, each one might have an idea.
In order to gather info, you need a starting point.
This is usually the answer to the initial question:
What is the goal I am aiming at with ... [package name, or program]
In this case, cpufrequtils.
Here is what it does:
https://packages.debian.org/sid/cpufrequtils (https://packages.debian.org/sid/cpufrequtils)
So, this is why I asked you in the previous message if you know enough to tinker with the Linux Kernel.
If you belive that overclocking your CPU will solve anything, you are on a very dangerous path.
It usually leads to frying either the CPU, the RAM or the mainboard. Sometimes, all three.
Unless you are an expert in hardware testing beyond the factory specifications boundaries. Are you?
Best regards, Șerban!
-
Hi!
First question you need to answer:
What is the goal you are aiming at with cpufrequtils?
In other words: What do you expect to get from it? What real problem you want to solve using this program?
Defining very clearly what you want to get, increases the available choices to do it.
There are lots of programs that do basically the same thing (serve the same purpose).
Choosing the best, bolis down to what do you know to do with it.
Making it simple:
It is unlikely that you will be able to comb your hair, using your shoes. You need a comb to do that.
As a final touch:
Knowing what to do with whatever piece of software, means:
- How do I install it?
- How do I uninstall it?
- How can I use it?
- What kind of trouble can I get into using it?
- How do I fix the system in case it breaks down?
Still! Nobody knows everything about everything.
It applies to me, to you, to anybody on this Forum, including Jerry.
Yet, each one might have an idea.
In order to gather info, you need a starting point.
This is usually the answer to the initial question:
What is the goal I am aiming at with ... [package name, or program]
In this case, cpufrequtils.
Here is what it does:
https://packages.debian.org/sid/cpufrequtils (https://packages.debian.org/sid/cpufrequtils)
So, this is why I asked you in the previous message if you know enough to tinker with the Linux Kernel.
If you belive that overclocking your CPU will solve anything, you are on a very dangerous path.
It usually leads to frying either the CPU, the RAM or the mainboard. Sometimes, all three.
Unless you are an expert in hardware testing beyond the factory specifications boundaries. Are you?
Best regards, Șerban!
I was trying to boost my clock speed because my cpu, was running at 1.6ghz, only made things worst :(
-
You may be getting distracted by cpufrequtils.
From what I've read here, it seems the problem relates to dependencies associated with linux-tools-common.
cpufrequtils doesn't have any link (as far as I can see) to linux-tools-common
I don't think that cpufrequtils got installed - the uninstall command couldn't find it.
Il pacchetto "cpufrequtils" non è installato e quindi non è stato rimosso
Trying to install cpufrequtils may have been the first time you noted apt reporting a problem.
The inference I make is that something installed *before* cpufrequtils has caused the dependency issue.
If you search the command line history before cpufrequtils, you may find something.
Or if you were using the GUI, we may need to look into other logs.
Unless we find the root cause, we can't try to fix it.
It may be more efficient to re-install.
-
I was trying to boost my clock speed because my cpu, was running at 1.6ghz, only made things worst :(
Sadly ,the things goes worst when you tried to speed up your cpu...
Yes, reinstall is better but perhaps gaas installed other programs without the terminal, and those packages could be found in your BROWSING HISTORY of your web browser
Well ,that's too personal info but if it's possible you should share the info only about programs, tips you tried and that video of youtube..
-
You may be getting distracted by cpufrequtils.
From what I've read here, it seems the problem relates to dependencies associated with linux-tools-common.
cpufrequtils doesn't have any link (as far as I can see) to linux-tools-common
I don't think that cpufrequtils got installed - the uninstall command couldn't find it.
Il pacchetto "cpufrequtils" non è installato e quindi non è stato rimosso
Trying to install cpufrequtils may have been the first time you noted apt reporting a problem.
The inference I make is that something installed *before* cpufrequtils has caused the dependency issue.
If you search the command line history before cpufrequtils, you may find something.
Or if you were using the GUI, we may need to look into other logs.
Unless we find the root cause, we can't try to fix it.
It may be more efficient to re-install.
I reinstalled linux, didn't have any important files anyway