update problems after upgrading to 21.2 Victoria

[Papa-26]

After upgrading to Mint 21.2 Victoria via the upgrade manager, I have problems when I run sudo apt-get update. It provides a slew of error messages (see below) I found that /etc/apt/sources.list and sources.list.d still point to Vera.

System: Kernel: 6.1.0-1019-oem x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: Mobo: ASUSTeK model: PRIME Z690-P D4 v: Rev 1.xx serial: UEFI: American Megatrends v: 2404 date: 03/30/2023 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: charge: 55% (should be ignored) status: Discharging CPU: Info: 6-core model: 12th Gen Intel Core i5-12600 bits: 64 type: MT MCP arch: Alder Lake rev: 5 cache: L1: 480 KiB L2: 7.5 MiB L3: 18 MiB Speed (MHz): avg: 3075 high: 3300 min/max: 800/6100 cores: 1: 600 2: 3300 3: 3300 4: 3300 5: 3300 6: 3300 7: 3300 8: 3300 9: 3300 10: 3300 11: 3300 12: 3300 bogomips: 79257 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: eVga.com. driver: nvidia v: 525.125.06 pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: DP-1,HDMI-A-1 empty: DP-2 bus-ID: 01:00.0 chip-ID: 10de:1f82 Device-2: Creative Live! Cam Socialize HD 1080 [VF0680] type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-9.6:8 chip-ID: 041e:4087 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x1080 s-dpi: 101 Monitor-1: DP-1 pos: primary,left res: 1920x1080 dpi: 102 diag: 551mm (21.7") Monitor-2: HDMI-0 pos: right res: 1920x1080 dpi: 102 diag: 551mm (21.7") OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 525.125.06 direct render: Yes Audio: Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:7ad0 Device-2: NVIDIA vendor: eVga.com. driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10fa Device-3: Creative Live! Cam Socialize HD 1080 [VF0680] type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-9.6:8 chip-ID: 041e:4087 Sound Server-1: ALSA v: k6.1.0-1019-oem running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 5 GT/s lanes: 1 port: 4000 bus-ID: 06:00.0 chip-ID: 10ec:8125 IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: Bluetooth: Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 chip-ID: 0a5c:21e8 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 2.1 lmp-v: 4.0 sub-v: 220e RAID: Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 bus-ID: 00:0e.0 chip-ID: 8086:467f Drives: Local Storage: total: 4.55 TiB used: 598.54 GiB (12.9%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 24.9 C ID-2: /dev/sda vendor: Western Digital model: WD20EZAZ-00L9GB0 size: 1.82 TiB speed: 6.0 Gb/s serial: ID-3: /dev/sdb vendor: Western Digital model: WD20EZAZ-00L9GB0 size: 1.82 TiB speed: 6.0 Gb/s serial: Partition: ID-1: / size: 762.2 GiB used: 278.41 GiB (36.5%) fs: ext4 dev: /dev/sdb5 ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 33 C Fan Speeds (RPM): N/A gpu: nvidia fan: 0% Repos: Packages: 2705 apt: 2676 flatpak: 24 snap: 5 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 1: deb https: //adoptopenjdk.jfrog.io/adoptopenjdk/deb/ jammy main 2: deb https: //cloud.r-project.org/bin/linux/ubuntu focal-cran40/ 3: deb https: //cloud.r-project.org/bin/linux/ubuntu vera-cran40/ Active apt repos in: /etc/apt/sources.list.d/adoptium.list 1: deb https: //packages.adoptium.net/artifactory/deb vera main Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main No active apt repos in: /etc/apt/sources.list.d/docker.list Active apt repos in: /etc/apt/sources.list.d/focal-security.list 1: deb http: //security.ubuntu.com/ubuntu focal-security main Active apt repos in: /etc/apt/sources.list.d/github_git-lfs.list 1: deb [signed-by=/etc/apt/keyrings/github_git-lfs-archive-keyring.gpg] https: //packagecloud.io/github/git-lfs/ubuntu/ jammy main 2: deb-src [signed-by=/etc/apt/keyrings/github_git-lfs-archive-keyring.gpg] https: //packagecloud.io/github/git-lfs/ubuntu/ jammy main Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/obsproject-obs-studio-jammy.list 1: deb [arch=amd64 signed-by=/etc/apt/keyrings/obsproject-obs-studio-jammy.gpg] https: //ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy main 2: deb-src [arch=amd64 signed-by=/etc/apt/keyrings/obsproject-obs-studio-jammy.gpg] https: //ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb https: //mirror.csclub.uwaterloo.ca/linuxmint-packages victoria main upstream import backport 2: deb http: //mirror.ca-tr.kamatera.com/ubuntu jammy main restricted universe multiverse 3: deb http: //mirror.ca-tr.kamatera.com/ubuntu jammy-updates main restricted universe multiverse 4: deb http: //mirror.ca-tr.kamatera.com/ubuntu jammy-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse Active apt repos in: /etc/apt/sources.list.d/vscode.list 1: deb [arch=amd64,arm64,armhf] http: //packages.microsoft.com/repos/code stable main Info: Processes: 342 Uptime: 4h 2m Memory: 15.36 GiB used: 2.46 GiB (16.0%) Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 5.8.4 inxi: 3.3.13

Screenshots

[danostg]

I had similar problems in 21.2 cinnamon, I found a fix for this, it is below, I use several apps that are "flatpak" so I ran in terminal: sudo flatpak repair flatpak repair --user flatpak update Do not interrupt this, it takes lots of time, approximately half an hour.

I also run every month the following: sudo apt-get update sudo apt-get autoclean sudo apt-get autoremove

I hope this helps you dan

[Papa-26]

Thank you for your suggestion. I ran it, you are right, It gave me enough time to prepare a tasty rágu di finocchio. But at the end, the sudo apt-get update still gave me the same error messages.

[anaximeno]

The problem doesn't seem to be with Mint or its source concretely.

I found that /etc/apt/sources.list and sources.list.d still point to Vera.

From what I saw on my computer it seems to be commented on, so it isn't being used:

Also in the system info you sent above, there was a line stating:

No active apt repos in: /etc/apt/sources.list

But from what I saw in the image with the result of the apt update command, the problem is with the additional sources of software you installed, some are pointing to the wrong release info, and other seems to not be supported yet. Please send the result of the following command:

apt update > output.txt

It will store the output of the command on the file named 'output.txt' you'll just have to send it in the comment.

Open the update manager click on the edit option in the top nav, then click software sources and send a screenshot of the following section:

[Papa-26]

nope, doesn't help. When I try maintenance on the Software Sources, this is, what I get:

E:The repository 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb jammy Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'https://cloud.r-project.org/bin/linux/ubuntu vera-cran40/ Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386', E:The repository 'https://packages.adoptium.net/artifactory/deb vera Release' does not have a Release file.

[anaximeno]

No, my last message wasn't the solution, I just want more data to see what's the best course of action for you to take right now.

[danostg]

The update manager could be uninstalled reinstalled via Synaptic.

On Mon, Aug 28, 2023, 10:28 PM Ralph Bloch @.***> wrote:

nope, doesn't help. When I try maintenance on the Software Sources, this is, what I get:

E:The repository 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb jammy Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'https://cloud.r-project.org/bin/linux/ubuntu vera-cran40/ Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386', E:The repository ' https://packages.adoptium.net/artifactory/deb vera Release' does not have a Release file.

— Reply to this email directly, view it on GitHub https://github.com/linuxmint/mintupdate/issues/839#issuecomment-1696253577, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIISBFHCE3UCUKSSA46POY3XXTWMZANCNFSM6AAAAAA35DTUBA . You are receiving this because you commented.Message ID: @.***>

[anaximeno]

From what I know the structure to define a software source repository for a specific OS is the following:

\<url> \<os version codename> \<Release channel (or something like that)>

If you look right, in some of your sources you have codenames such as vera-cran40 or vera, but they aren't valid codenames for the distributions represented in their respective URLs (Ubuntu, and Debian respectively), as vera is a codename for Mint but not for the other distributions.

[anaximeno]

The update manager could be uninstalled reinstalled via Synaptic. … On Mon, Aug 28, 2023, 10:28 PM Ralph Bloch @.> wrote: nope, doesn't help. When I try maintenance on the Software Sources, this is, what I get: E:The repository 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb jammy Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'https://cloud.r-project.org/bin/linux/ubuntu vera-cran40/ Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386', E:The repository ' https://packages.adoptium.net/artifactory/deb vera Release' does not have a Release file. — Reply to this email directly, view it on GitHub <#839 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIISBFHCE3UCUKSSA46POY3XXTWMZANCNFSM6AAAAAA35DTUBA . You are receiving this because you commented.Message ID: @.>

The problem doesn't seem to be with the software manager itself.

[anaximeno]

Mr. Ralph (@Papa-26), try to open the source section I showed above and change where you have vera-cran40/ and vera to jammy save a run the update command again.

[anaximeno]

You can disable the source 'https://adoptopenjdk.jfrog.io/adoptopenjdk/deb because it is deprecated, meaning it is not being used anymore:

You won't need it since you already have the new source (please note the difference between the sources) which is https://packages.adoptium.net/artifactory/deb.

[anaximeno]

You might still have this problem:

Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com/ stable InRelease' doesn't support architecture 'i386'

Because it seems that you are requesting software for the i386 (32bit) architecture but the repository doesn't support that version. I am not sure what's the best course of action for you in this case.

[anaximeno]

I gave a quick look at the brave repository and it seems that it does not support the 32bit architecture, so brave might not be installable on your computer (if it is in fact, a 32bit computer):

So you might want to disable (or remove) the source for brave https://brave-browser-apt-release.s3.brave.com/ and install another browser.

After this, you might not have more problems at least for now.

[Papa-26]

Brave works fine, and my computer isAMD64; I did all the psiible updates on the Update Manager, under Software Sources, and it made no differences. All the sources that raised errors had pointed to either Vanessa or Vera, where the current keyring code doesn't work. What I need is a way to get the sources appropriate for Victoria!

[anaximeno]

Brave works fine, and my computer isAMD64;

Oh, ok, I don't know why it is requesting for 32bits then.

I did all the psiible updates on the Update Manager, under Software Sources, and it made no differences. All the sources that raised errors had pointed to either Vanessa or Vera, where the current keyring code doesn't work. What I need is a way to get the sources appropriate for Victoria!

Did you change those sources to jammy (the ones I recommend above)? Linux Mint is based on Ubuntu, so in this case you'll have to use Ubuntu sources. If possible, send the screenshot of the apt update command to confirm you made it right.