Browsers are broken

Started by sites, 2023/11/19, 16:10:25

Previous topic - Next topic

sites

Ran updates this morning. Chrome and Brave will not load pages properly. Firefox does, but some pages crash. Typing from a different pc now.

edlin

Sorry, but hardly anyone here will be able to do anything with your description of the problem.
1. neither Chrome nor Brave are part of the official Debian/Siduction repos. Which versions do you have installed?
2. is your system up to date (apt update && apt dist-upgrade)?
3. KDE/Plasma, Wayland or X11, ...?
4. what do you mean by a page not loading properly?
5. example pages and the concrete problems (screenshots) would be helpful.
6. have you tested Chromium instead of Chrome?
7. which pages crash under Firefox?
8. ...

edlin
,,Ein kluger Mann macht nicht alle Fehler selber. Er lässt auch anderen eine Chance."

Winston Churchill

towo

For Chromium, i can confirm the Issue, Chromium does not render any site since todays upgrade.
For Google-Chrome and Firefox i can't see any problem here.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

edlin

I have just installed Chromium as a test and cannot see any problems.
apt policy chromium
chromium:
  Installed: 119.0.6045.159-1
  Installationskandidat: 119.0.6045.159-1
  Version table:
*** 119.0.6045.159-1 500
        500 https://deb.debian.org/debian testing/main amd64 packages
        500 http://ftp.de.debian.org/debian unstable/main amd64 packages
        500 http://debian.intergenia.de/debian trixie/main amd64 packages
        100 /var/lib/dpkg/status
     119.0.6045.123-1 500
        500 http://ftp.hosteurope.de/mirror/ftp.debian.org/debian trixie/main amd64 Packages


KDE/Plasma, X11

edlin
,,Ein kluger Mann macht nicht alle Fehler selber. Er lässt auch anderen eine Chance."

Winston Churchill

towo

I'm on Plasma Wayland.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

towo

After removing ~/.cache/chromium and ~/.config/chromium, Chromium is working again.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

edlin

A virgin Wayland session works fine with Chromium.

edlin@Devil:~$ inxi -G
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: amdgpu v: kernel
  Device-2: Aveo USB2.0 UVC PC Camera driver: uvcvideo type: USB
  Display: wayland server: X.Org v: 23.2.2 with: Xwayland v: 23.2.2
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1200~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 vendor: amd mesa v: 23.2.1-1 renderer: AMD Radeon
    Graphics (renoir LLVM 16.0.6 DRM 3.54 6.5.11-1-siduction-amd64)


Perhaps it is the legacy files (cache, config) that are causing problems. The problem should then disappear with a new user created as a test.

edlin
,,Ein kluger Mann macht nicht alle Fehler selber. Er lässt auch anderen eine Chance."

Winston Churchill

samoht

#7
Recently Google Chrome and Vivaldi, as the browsers based on the Chromium machine, have been updated. And only these versions are working again on my siduction.

[Interestingly, the standalone desktop version of the Bitwarden client as an Electron-based programme still does not work.

UPDATE:
Bitwarden works again after deleting the current
~/.config/Bitwarden]

Camelot

I now had the same problem, the solution is to delete only the GPUCache folder.
Tested with the following browsers: Chromium, Vivaldi, Opera

Before deleting, you can test by starting the browser without GPU:
chromium --disable-gpu --disable-accelerated-video-encode

If this works, simply delete the GPU cache folder:
~/.config/chromium/Default/GPUCache

The complete browser profile therefore does not have to be deleted.