Recent Posts

Pages: [1] 2 3 ... 10

Tutorials / Linux Lite Studio

« Last post by Şerban S. on Today at 09:29:22 AM »

Linux Lite Studio (1)

Low latency kernel

Hi, everyone!
I started this thread hoping that there are people here interested in audio production on Linux, specifically, on Linux Lite. I know there are targeted distros, but I am interested as said above, in a “Linux Lite Studio" flavor.
Thus, the title “Linux Lite Studio”.
Maybe they can help (or get help!).
Since the beginning is a kernel mattter, and then lots of specific applications, I suppose there are many here who can help find solutions and improvements.
From this perspective, a basic requirement is a lowlatency kernel.
Searching in Linux Lite’s kernel list (Lite Tweaks —>Kernel Install), I found only generic kernels.
Since nothing else is specified, the only alternative left, was Synaptic.
On a standard installation, the System Info App, reports “Linux 5.15.0.89-generic”.
So, I figured out I need to find its counter-part, “Linux 5.15.0.89-lowlatency”.
I found the kernel, installed it, and now (after reboot) is loaded.
The System Info App, reports “Linux 5.15.0.89-lowlatency”.
While in theory a “generic” kernel should be usable, in fact, there are specific settings at kernel level that need to be active, such as “threadirqs”.
While this is relative simple to solve, for the “-generic” kernel, there are specific settings that are unavailable in this type of kernel. That makes things go sideways when speaking of latency and DSP (Digital Signal Processing) long chains: DAW setup, many tracks, many plugins.
In order to make JACK work properly, I ndeed to have those kernel options.
Here is a common message issued by JACK:
“Cannot create RT messagebuffer thread: Operation not permitted (1)”.
There are others also.
Although JACK runs, the problem is that I got xruns (frame droppings) with the “-generic” kernel.
Main problem here, is the latency. Since latency is a huge story, I’ll skip the details and say that each and every piece of “something”, where “something” means both hardware and software, has a specific latency. The bad thing is that this is additive so the longer the DSP chain, the greater the lateny hence, the more xruns.
The lower the latency, the better are the results in the audio process (recording, playing, mastering).
The kernel options needed, i.e., are the following:
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LATENCYTOP=y
This is possible only with the said type of kernel.
Those settings, are needed to use a latency monitoring tool, called “LatencyTOP”, which is very similar with “Top” and “Htop”, except it is specifically designed for pro-audio use.

Updates / Re: Chrome NO_PUBKEY E88979FB9B30ACF2

« Last post by stevef on Today at 08:26:52 AM »

It's working ok for my system so possibly a problem at the server end on the repository you are being directed to.
Have you really had this problem for 10 or more days, or just got it now ?

If you follow the instructions in reply 1, you should be able to update/upgrade by skipping the Chrome for the short term.

To check you have the correct key, please can you open a terminal - by pressing Ctrl Alt and T together.
In the terminal window type or paste in this command followed by Enter.

Code: [Select]

apt-key listThis will show what keys apt can find to check software is signed - the chrome section is the one we need to see..
Copy the output and paste it back here.

Chrome has been the included browser for Linux Lite since the release of LL6.0 in June 2022 when Firefox went snap so it has not just happened.
For those that still want Firefox, it is offered in Lite Software, but this will install Snap.
As an alternative, check the 6.0 release notes which give a method to install without Snap.

Updates / Re: Chrome NO_PUBKEY E88979FB9B30ACF2

« Last post by Dan Brown on Today at 07:59:01 AM »

I have the same problem. I thought I had a perfect install for me but after timeshifting back through 10 days I realised that from the beginning I was getting these errors. I don't even want Chrome anyway as everything is in Firefox. Clean install and LL won't do the first update of 443 Updates.

I have fast reliable Fibre and good local repos and and just when I thought my distro hopping days were over LL changes to Chrome.

Here's a log before I do anything except run TimeShift and Clonezilla to Back up this Virgin install

============ Log ===========

Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:2 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Hit:3 http://archive.canonical.com/ubuntu jammy InRelease
Hit:4 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:2 https://dl.google.com/linux/chrome/deb stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:7 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Hit:8 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists...
W: GPG error: https://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
E: The repository 'https://dl.google.com/linux/chrome/deb stable InRelease' is not signed.

DB

Other / Re: Help NEWBIE Screwed up repositories

« Last post by stevef on Today at 03:44:16 AM »

Timeshift (with default settings) will include the system files which update/grade uses.
So if you have a snapshot from when the repositories were still good deploying it should restore the relevant files as it will revert your system to the point the snapshot was taken.

Other / Help NEWBIE Screwed up repositories

« Last post by Dan Brown on Today at 03:14:46 AM »

Hi Steve

Thanks for responding.
I did try that, but It didn't work. I don't know if TimeShift willl do it as I kept snapshots everytime I got something working.

My Needs are simple

1. Keepass2 via Google Drive or Samba for my Passwords
2. Samba to my Windows server
3. TOR Browser (Testing for Customers Dodgy links etc)
4. Firefox in Sync with Windows system
5. Teamviewer 12 (Later)
6. Thunderbird (Later)

I still have to keep my Windows 11 box for customer support and Server 2019 for Customer backups,
so I got the Separate Lenovo to start working on Linux and learning.

I am going to try Timeshift hoping it's like Windows system Restore. I do have a Clonezilla Image
to fall back on as well.

DB

Updates / Re: Chrome NO_PUBKEY E88979FB9B30ACF2

« Last post by DesertWinds on April 26, 2024, 08:51:13 AM »

Thanks Stevef it works

Quote from: stevef on April 25, 2024, 11:00:33 AM

There may be a problem with the source repository - it is giving a 404 error which is odd..
I expect they will resolve it in due course.

In the short term - if you need to allow the updates to run, try this.

Click Menu and begin typing 'Software & Updates' in the search box
When you see 'Software & Updates' click on it.
In the Window that opens select 'Other Software' tab

Uncheck the entry for Chrome and enter your password to authenticate the change if asked.
Click Close on the 'Software & Updates' window and then 'Reload' to refresh the cache.

Then try update/upgrade again. This should now skip the Chrome update.

Once done, I'd leave it 24 hours or so, then go through the above again but re-enable the Chrome repository.

If it isn't working then let us know.

Other / Re: Help NEWBIE Screwed up repositories

« Last post by stevef on April 26, 2024, 04:56:47 AM »

There's an inbuilt utility which is a quick fix attempt but it may not be able to undone what you've done.
It is rated with caution as it involves changing system files.

Click Menu and begin typing 'Lite Tweaks' into the search box.
When you see 'Lite Tweaks' offered, click on it.

In the window that opens scroll down to find and check 'Package System Repair' then click begin and follow the instructions.

If that doesn't work, we could try to debug, but starting from scratch may be quickest.

Other / Help NEWBIE Screwed up repositories

« Last post by Dan Brown on April 26, 2024, 03:33:49 AM »

Hi There

I have been distro hopping for a long time but finally settled on LL.

I keep using timeshift to make restore points but I think I screwed up my Repositories
and need to fix it or start from scratch again. I have googled and searched but never
certain I won't make it worse. I am hoping for a quick fix.

Here's the problem when I try and run updates

===========================
Install Updates Error log
===========================
Install Updates could not fetch the package cache information lists.
Go to https://www.linuxliteos.com/forums/ and paste the log below into the Software - Support - Updates section for assistance.

============ Log ===========

Hit:1 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:1 http://repo.linuxliteos.com/linuxlite fluorite InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 22AAEA0A86A02625
Get:2 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.canonical.com jammy InRelease [11.4 kB]
Err:3 http://archive.canonical.com jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Hit:4 https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease
Err:4 https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD5F235DF639B041
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Err:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9BDB3D89CE49EC21
Err:2 http://archive.ubuntu.com/ubuntu jammy-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Hit:6 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Err:6 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B5B116B72D0F61F0
Hit:8 https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease
Err:8 https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B90E9186F0E836FB
Err:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:9 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Err:9 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Err:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.linuxliteos.com/linuxlite fluorite InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 22AAEA0A86A02625
W: GPG error: http://archive.canonical.com jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.canonical.com jammy InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD5F235DF639B041
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9BDB3D89CE49EC21
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B5B116B72D0F61F0
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B90E9186F0E836FB
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.

Lenovo M73 Thinkcentre mini - i5-4690K Intel CPU - Onboard Intel GPU - 256Gb SSD - 16Gb DDR3 RAM

Other / Re: re-Touchscreen

« Last post by keiaa on April 25, 2024, 07:21:25 PM »

Good day! Please refer to the following documentation for your instance. Cheers!

https://wiki.ubuntu.com/Touchscreen

Other / re-Touchscreen on Chromebook

« Last post by Jesse Bassett on April 25, 2024, 11:11:36 AM »

So I successfully installed LL on a lenovo flex 5i chromebook. Everything works right out-of-the-box EXCEPT the touchscreen. Are there any commands I can try to enable the touchscreen on my laptop?

Pages: [1] 2 3 ... 10