Software - Support > Installing Software
Error while trying to install something on the terminal
gaas:
--- Quote from: Şerban S. on April 07, 2024, 05:09:27 PM ---
--- Quote from: gaas on April 07, 2024, 04:02:25 PM ---[...]
Can you explain in simpler terms please? I'm pretty new to Linux.
--- End quote ---
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!
--- End quote ---
Ok, take your time. :)
Şerban S.:
--- Quote from: gaas on April 07, 2024, 04:02:25 PM ---[...]
Can you explain in simpler terms please? I'm pretty new to Linux.
--- End quote ---
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!
gaas:
--- Quote from: Şerban S. on April 07, 2024, 03:34:29 PM ---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:
--- Code: ---sudo apt install htop
--- End code ---
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:
--- Code: ---apt search libcpufreq0
Sorting... Done
Full Text Search... Done
libcpufreq0/jammy 008-2build1 amd64
shared library to deal with the cpufreq Linux kernel feature
--- End code ---
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:
--- Code: ---sudo apt update
--- End code ---
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.
--- End quote ---
Can you explain in simpler terms please? I'm pretty new to Linux.
Şerban S.:
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:
--- Code: ---sudo apt install htop
--- End code ---
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:
--- Code: ---apt search libcpufreq0
Sorting... Done
Full Text Search... Done
libcpufreq0/jammy 008-2build1 amd64
shared library to deal with the cpufreq Linux kernel feature
--- End code ---
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:
--- Code: ---sudo apt update
--- End code ---
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.
gaas:
I may just reinstall linux at this point :'(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version