Chromium error recently appeared (under 19.3)

Forum Forums General Software Chromium error recently appeared (under 19.3)

  • This topic has 5 replies, 3 voices, and was last updated Sep 19-12:14 pm by ModdIt.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #88987
    Member
    roland

      I’m not sure where to report this fault, if it is an antiX fault at all, I’m having this trouble under Chromium running under 19.3 but it may be unrelated to the release number of antiX. I am unsure how to report faults relating to individual packages.

      My online banking login screen for Barclays UK requires the members surname to be typed in a screen box followed by a membership number in the next box down.

      The dialog then requires the member to confirm his authenticity by one of 3 methods, the middle one entailing the use of the members credit or debit card inserted into a calculator-sized machine called a Pinsentry.

      On inserting the card into the Pinsentry and entering the cards pin number, an 8 digit code is printed on the Pinsentry lcd screen.

      First the user enters the last 4 digits of his card number into a dialog screen box.

      This 8-digit Pinsentry code is then entered as 2 groups of 4 digits into 2 consecutive boxes on the dialog screen.

      If the code checks out by the bank dialog the user is passed forwards to online banking processes.

      A recent change has occurred to Chromium in that the screen appears corrupted and one of the 2 consecutive boxes in which to enter the Pinsentry code is missing from the screen, and the code cannot be entered, only the 1st 4 characters.

      Firefox ESR works as the bank intended, and the screen appears normally, and login is achieved.

      The changes to Chromium that I describe have occurred during the last 7 days at most, maybe less.

      I attach the corrupted Chromium screenshot and the correct FirefoxESR screenshots for comparison.

      My system is kept fully up to date on a weekly basis or more frequently using apt-update and apt-dist-upgrade as necessary, and all changed packages are applied. I am only using an old 15″ glass monitor on this PC.

      • This topic was modified 7 months, 3 weeks ago by roland.
      #88992
      Member
      ModdIt
        Helpful
        Up
        1
        ::

        According to Google Blog

        Stable Channel Update for Desktop
        Wednesday, September 14, 2022

        The Stable channel has been updated to 105.0.5195.125 for Mac and Linux, 105.0.5195.125/126/127
        which will roll out over the coming days/weeks. A full list of changes in this build is available
        in the log.

        Do you already have te latest release, should you do so best to purge then remove config, the
        hidden directory in home then reinstall. It may fix your problem.

        Should reinstall not fix you can file a bug report against chrome.

        Personaly I would not recommend chrome for banking, or anything else for that matter.
        Everything you do google is with you.

        Ungoogled Chromium far better. If you have a 64 bit OS.

        If you really are fixed on chrome based maybe Vivaldi would be a reasonable alternative.

        #89027
        Member
        olsztyn
          Helpful
          Up
          0
          ::

          I’m having this trouble under Chromium running under 19.3 but it may be unrelated to the release number of antiX.

          For identifying what is causing this issue I would first suggest:
          – What desktop WM are you using on antiX?
          – If you are using Fluxbox or IceWM to run this, then the test I am suggesting is: Switch desktop WM from Fluxbox (or IceWM) to JWM by selecting from the menu ‘Other Desktops’, etc.
          – Start Chromium and proceed to this banking service as usual.
          – See if you experience the same issue.

          It takes a minute to perform this test so worth trying…
          I am curious if your problem gets resolved… If it happens so that it will work then switch back to your original IceWM (or Fluxbox) and it should continue to work in such your preferred desktop…

          • This reply was modified 7 months, 3 weeks ago by olsztyn.

          Live antiX Boot Options (Previously posted by Xecure):
          https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

          #89151
          Member
          roland
            Helpful
            Up
            0
            ::

            I have tried several times on 2 or 3 different 64-bit pcs to install ungoogled chromium, without success. The process runs apt-update then fails immediately but I can never see what with.

            I have read the post above by Moddit, and a later one describing how to deal with the sandbox, it’s all a bit over my head I’m ashamed to say.

            But should I purge chromium first before attempting to install ungoogled chromium? What are the minimal things I need to do to achieve an install?

            ps I am using iceWM (or space-iceWM?) and spaceFM, I have never used anything else and am wary of a sudden change to JWM in case it leads me too far away from the immediate problem. The fact that Firefox works and Chromium doesn’t in this instance tells me not to diverge too much, so I wish to either install ungoogled chromium or change to another browser. I like chromium but am prepared to abandon it as I suspect it is also the cause of the workspace freezing problem I posted a few weeks ago, although that does not occur with this current 193. installation, but does with the latest 21 install.

            • This reply was modified 7 months, 3 weeks ago by roland. Reason: more information
            #89157
            Member
            ModdIt
              Helpful
              Up
              1
              ::

              Hopefully helpful, please do not despair, problems with browsers can be bothersome to fix, and sometimes
              troubles are only fixable by a system upgrade. That has to do with the Librarys the browser depends on, biggest
              issue is often GLIBC. A very important system component.

              to rule out a corrupted config or cache please regenerate both.
              Config is to be found at /home/yourusername/.config/chromium
              Eazy, delete with rox or filemanager of your choice.
              please also remove chromium cache as it might cause problems
              easy from the terminal rm -rf ~/.cache/chromium
              Or use filemanager.

              If that does not help then:
              I suggest to purge/remove chromium as the config has the same name for both chromium and UngoogledChromium

              If you use the package installer you should get a fitting install and not need to touch the sandbox or do anything
              to get a menu entry.

              If you are still stuck best choice is use firefox for banking until a fix or way round the problem can be found, or you
              decide to stay with the fox. You could also try LibreWolf. It works ok for my bank.

              The problem may be coming from updated chrome but could be a bank site issue, hard to separate without using an older
              and insecure chrome version to see if the issue dissapears. Not recommended for banking.

              For Info and Understanding/ try if you wish but following will need as a minimum Bullseye for sure.

              I want the latest and greatest version so i am not using the package installer. I am also running antiX with sid repos.
              What might happen is that a download from below source needs a much newer GLIBC than is on your system.
              ………………………………………………………………………………………………………………………
              I use a universal package of UngoogledChromium. That is similar to the way firefox comes if you download from mozilla.
              I download from https://ungoogled-software.github.io/ungoogled-chromium-binaries/
              Check the sha256 sum of the zip file before unpacking.
              In the package is a README, after unpacking and opening the resulting folder it is readable.
              Important part for testing if Installing as I do will work on your system.
              How to set up the SUID sandbox:
              1. Rename “chrome_sandbox” to “chrome-sandbox” so you rename as demanded, easy peasy in ICEWM. Right mouse click use rename option
              2. Set the file mode to 4755. Easy to understand way when you use the rename option use the path to the downloaded folder and file.
              Which would look like: chmod 4755 /home/yourusername/Downloads/ungoogled-chromium_105.0.5195.127-1.1_linux/chrome-sandbox

              3. Set the group to root
              chown :root /home/yourusername/Downloads/ungoogled-chromium_105.0.5195.127-1.1_linux/chrome-sandbox

              4 make chrome-wrapper executable, easy, right click on the file, you have a right click menu item for that.

              Then left click on chrome wrapper and see if UngoogledChromium will start.

              If working correctly easy to move the browser files to a saner place, I use /opt then make a personal menu
              entry with the control center tool.

              I hope understandable, need help with understanding please ask.

              #89315
              Member
              ModdIt
                Helpful
                Up
                0
                ::

                Note: For chrome based browsers

                Users please do take a look through chrome://flags
                at least in latest UngoogledChromium you can set,
                among many other things.
                Clear data on exit to enabled

                But it does not clean everything so I will keep
                my cache to temp diversion active.

                UngoogledChromium makes many choices available, due to lack of usage
                I am unable to confirm whether all are same in other chrome based
                browsers. Read Chromium Vivaldi Edge etc.

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.