Announcement

Collapse
No announcement yet.

Upgrade to Noble (24.04 LTS) disabled Google Chrome updates

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Upgrade to Noble (24.04 LTS) disabled Google Chrome updates

    While upgrading from 22.04 to 24.04 I got this message:

    "Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager."

    Several weeks after the upgrade I have noticed that some applications are not getting updates, they do not show up in KDE Discover.

    If a take a look at the folder /etc/apt/sources.list.d/ :



    I can see a google-chrome.list.distUpgrade with the following contents:

    Code:
    ### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
# deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main # disabled on upgrade to noble​
​
    There is also the file ubuntu.sources:

    Code:
    Types: deb
URIs: http://es.archive.ubuntu.com/ubuntu/
Suites: noble noble-updates noble-backports
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Types: deb
URIs: http://security.ubuntu.com/ubuntu
Suites: noble-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
​
    And the file third-party.sources with the following lines:

    Code:
    Enabled: no
Types: deb
URIs: cdrom:[Kubuntu 22.04.2 LTS _Jammy Jellyfish_ - Release amd64 (20230223)]/
Suites: jammy
Components: main restricted universe multiverse
    I have removed the "#" from the beginning of the "deb" line in google-chrome.list.distUpgrade​, saved the file and tried a "sudo apt update" which does not detect the latest Google Chrome version. Also tried to update via Discover with the same result (it displays "Up do date"). These are my current settings in Discover:


    What is happening here? How do I re-enable SW updates?

    Thanks in advance
    Tags: None
    • Top
    • Bottom
    #2
    The correct file will be google-chrome.sources.
    What are the contents of that file?

    I believe that if both files exist, the .sources one takes precedence, so even uncommenting the old one won't have an effect on things.

    The *.sources files replace the old style *.list ones due to changes and updates from Debian for the format of source files.

    An unfortunate side effect of the updated source file format is that it breaks their display in Discover, at least until whoever maintains the packagekit/Discover Apt plugin fixes this.

    You can still use the Software Sources tool iirc, but that too might not show all of them, either.
    (hint- you can get to that from the Driver Manager in System Settings.)
    Last edited by claydoh; Oct 26, 2024, 03:30 AM.
    • Top
    • Bottom

    Comment

      #3
      Originally posted by claydoh View Post
      The correct file will be google-chrome.sources.
      What are the contents of that file?
      Code:
      Enabled: no
Types: deb
URIs: https://dl.google.com/linux/chrome/deb/
Suites: stable
Components: main
Signed-By:
-----BEGIN PGP PUBLIC KEY BLOCK-----
.
mQINBFcMjNMBEAC6Wr5QuLIFgz1V1EFPlg8ty2TsjQEl4VWftU AqWlMevJFWvYEx
BOsOZ6kNFfBfjAxgJNWTkxZrHzDl74R7KW/nUx6X57bpFjUyRaB8F3/NpWKSeIGS
pJT+0m2SgUNhLAn1WY/iNJGNaMl7lgUnaP+/ZsSNT9hyTBiH3Ev5VvAtMGhVI/u8
P0EtTjXp4o2U+VqFTBGmZ6PJVhCFjZUeRByloHw8dGOshfXKgr iebpioHvU8iQ2U
GV3WNIirB2Rq1wkKxXJ/9Iw+4l5m4GmXMs7n3XaYQoBj28H86YA1cYWSm5LR5iU2
.
.
.
.
      • Top
      • Bottom

      Comment

        #4
        So enable it and see if that works.
        • Top
        • Bottom

        Comment

          #5
          Yes, it worked. Thank you!

          One more thing. When I execute sudo apt update I get these messages:

          N:​ Missing Signed-By in the sources.list(5) entry for 'http://miktex.org/download/ubuntu'
          N: Missing Signed-By in the sources.list(5) entry for 'https://download.mono-project.com/repo/ubuntu'
          ​
          Taking a look at the /etc/apt/sources.list.d/ folder I believe that they are related to the contents of the files miktex.sources and mono-official-stable.sources:



          miktex.sources:

          Enabled: yes
          Types: deb
          URIs: http://miktex.org/download/ubuntu
          Suites: noble
          Components: universe

          mono-official-stable.sources:​

          Enabled: yes
          Types: deb
          URIs: https://download.mono-project.com/repo/ubuntu
          Suites: stable-focal
          Components: main

          From what I've read it seems that a line starting with Signed-By is missing ​below Components. Do you know where and/or how to inform its value?

          Regards
          • Top
          • Bottom

          Comment

            #6
            Solved!

            Reinstalled both miktex and mono-devel packages and added arch=amd64 to both miktex.list and mono-official-stable.list files:



            miktex.list​:

            deb [arch=amd64 signed-by=/usr/share/keyrings/miktex-keyring.asc] https://miktex.org/download/ubuntu noble universe

            mono-official-stable.list​:

            deb [arch=amd64 signed-by=/usr/share/keyrings/mono-official-archive-keyring.gpg] https://download.mono-project.com/repo/ubuntu stable-focal main

            Regards
            ​
            • Top
            • Bottom

            Comment

            Previous template Next
            Working...
            X