Mageia forum

I have Chromium installed on both of my systems and they have begun to display messages at launch that the previous session did not close correctly and asks to restore pages, even when all of the previous session's tabs were closed, leaving the home tab in place.

A supposed fix found online technically pertained to Windows, but when applied to the Linux version, it didn't work and that was to go into Settings/Advanced/System and turning off 'Continue running background apps when Chromium is closed'.

https://bugs.chromium.org/p/chromium/is ... ?id=429404 is from 2014 and is still an open bug. Scrolling through the comments, it was confirmed long ago.

I uninstalled Chromium, then removed the profile ('chromium' directory in ~/.config) and reinstalled Chromium. No change in behavior. Is there something else I could try?

Thank you in advance.

Received word from someone I know who uses another distro, but with actual Google Chrome and the same problem occurs, so there must be an issue with the current Chromium version.

Created a new profile (by first deleting the ~/.config/chromium directory) and restarting Chromium, it still crashes.

After removing and reinstalling it, it still crashes.

Although this appears to be an upstream issue, I have removed it from my systems.

I discovered that the uBlock Origin extension was causing the crashes. Once removed and a new profile was created, Chromium was fine, until I reinstalled uBO. I have replaced uBO with Ad Block Plus (ABP) and Chromium continues to be crash-free.

Although Chromium will occasionally display the window at startup that it didn't close correctly. Last night, when I closed Chromium after doing the above and using it for a while (exited via the three-dot menu/Exit to close), there was HDD activity for a good 15 seconds. I was told that Chromium is saving 'context' when it's closing.

FWIW, should be this bug: https://bugs.mageia.org/show_bug.cgi?id=29680
You could have mentioned that you also installed chromium extensions from Mageia repositories in addition to chromium itself.

Apart from that, uBlock Origin works fine here with normal chrome, no crashes at all.

The extensions I installed (and removed) were all installed via the Chrome Web Store site, not from Mageia. I did not mention the extensions originally, because I had no idea what was causing the crashes. It was all trial-and-error.

I didn't even know Mageia had a repository of Chromium extensions. Yes, it appears to be the bug you referenced. I'll add comments to it. As I've had no crashes since removing uBO, I'm inclined to think the problem is with the extension and not Chromium.

epp wrote:I did not mention the extensions originally, because I had no idea what was causing the crashes. It was all trial-and-error.

But you mentioned that it also happens after deleting the profile, which means no user-installed extensions.

Correct. It also had been crashing (past-tense). As I deleted the profile out of ~/.config, I did so with the extensions still 'installed' with Chromium. When I tried to remove any extension in the Settings, either uBO or the other (Send Link via Email), that caused a crash as well. Deleting the profile was the only other method I could think of.

Why it crashed on a new profile previously (and isn't crashing now), no idea.

I am still having issues with Chromium, even without uBlock Origin installed.

If both regular and incognito windows are open and I close the incognito window, the majority of the time, it closes both Chromium windows, exiting the app.

Does anyone know if the new version currently in Testing, fixes this?

TIA.

epp wrote:Does anyone know if the new version currently in Testing, fixes this?

as you have a specific issue, it is unlikely that the QA testing team would be able to replicate your issue.
it may be hardware related or some setting that you have enabled (or disabled)

testing the update requires no "special knowledge, privileges or membership" except that you are willing to improve Mageia.

apart from that, all that is required is that updates testing (core, non-free and tainted, and maybe the 32bit as well) repos are enabled, and then update the package. then, disable the "updates " repos.
check to see if it addresses your issue.
report your findings on the appropriate bug report ( https://bugs.mageia.org/show_bug.cgi?id=29846 )

regards

I just launched Chromium from a terminal window and once I closed the Incognito window, it again closed both and resulted in a segfault:

Code: Select all: ~]$ chromium-browser [42881:42881:0131/194736.739761:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42881:42881:0131/194736.739967:ERROR:gl_surface_egl.cc(782)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42881:42881:0131/194736.740021:ERROR:gl_surface_egl.cc(1382)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED [42881:42881:0131/194736.740080:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed. [42881:42881:0131/194736.764038:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [42924:42924:0131/194737.214290:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42924:42924:0131/194737.214808:ERROR:gl_surface_egl.cc(782)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42924:42924:0131/194737.215181:ERROR:gl_surface_egl.cc(1382)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED [42924:42924:0131/194737.215290:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed. [42924:42924:0131/194737.239596:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [42949:42949:0131/194737.564626:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42949:42949:0131/194737.565378:ERROR:gl_surface_egl.cc(782)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42949:42949:0131/194737.565535:ERROR:gl_surface_egl.cc(1382)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED [42949:42949:0131/194737.566061:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed. [42949:42949:0131/194737.575927:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [42980:42980:0131/194737.812613:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42980:42980:0131/194737.816503:ERROR:gl_surface_egl.cc(782)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1048. [42980:42980:0131/194737.816699:ERROR:gl_surface_egl.cc(1382)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED [42980:42980:0131/194737.816808:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed. [42980:42980:0131/194737.854299:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [42999:42999:0131/194737.929226:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is [42845:42864:0131/194740.597252:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends. [42845:42864:0131/194740.597290:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended. [42845:42864:0131/194740.597300:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends. [42845:42864:0131/194741.606828:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status ended. [42845:42875:0131/194859.011698:ERROR:database.cc(1774)] History SQLite error: code 1555 errno 0: UNIQUE constraint failed: context_annotations.visit_id sql: INSERT INTO context_annotations( visit_id,context_annotation_flags,duration_since_last_visit,page_end_reason,total_foreground_duration )VALUES(?,?,?,?,?) Received signal 11 SEGV_MAPERR 000000000000 #0 0x561a877e6619 base::debug::CollectStackTrace() #1 0x561a877303b6 base::debug::StackTrace::StackTrace() #2 0x561a877e5bab base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7f093f6cb180 (/usr/lib64/libpthread-2.32.so+0x1317f) r8: 00007fffbee99904 r9: 0000000000000023 r10: 00000000000002ff r11: 00007fffbee99940 r12: 00007f09083013d0 r13: 0000561a9409f720 r14: 0000561a9409f820 r15: 0000561a8a69c5c0 di: 0000561a94f2d110 si: 00007fffbee99ab0 bp: 00007fffbee99b10 bx: 0000561a9409f820 dx: 0000000000000001 ax: 0000000000000000 cx: 0000000000000000 sp: 00007fffbee99ae8 ip: 0000000000000000 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000014 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Segmentation fault (core dumped)

in this case,

I would recommend that you file a bug report and link it back to here, so that others may benefit.

if not familiar with creating a bug report, have a look here => https://wiki.mageia.org/en/How_to_report_a_bug_properly

Could you please test if you still have the same problem when you disable hardware acceleration in Chromium settings? Either disable it via Chromium advanced settings or start Chromium with

Code: Select all: chromium --disable-gpu

sturmvogel wrote:Could you please test if you still have the same problem when you disable hardware acceleration in Chromium settings? Either disable it via Chromium advanced settings or start Chromium with
Code: Select all
chromium --disable-gpu

It was originally disabled. It segfaults regardless of that setting.

https://bugs.mageia.org/show_bug.cgi?id=29983

a google search for this string (initialize error 0: Internal Vulkan error (-3)) returns this => https://forum.manjaro.org/t/chromium-ch ... tion/97043

with a link to here => https://wiki.archlinux.org/title/chromi ... ecific_GPU.

are either of these helpful?

Unfortunately, no. A few people tried to duplicate this with the current and testing versions, without success.

The bug report now has the info from the inxi -MSG command. There is only one GPU in the system.

chrome://gpu displays:

Graphics Feature Status for Hardware GPU

Problems Detected for Hardware GPU

Log Messages

it seems all of the hardware acceleration is disabled.
did you do this intentionally?
have you turned hardware acceleration off in your bios?

does the chromium appimage also display the issue?

this will help to determine if it is a Mageia specific build issue or a chromium issue.

in your opening post, you remarked that you have 2 systems affected. is this still the case?.
if so, attach

Code: Select all: lspcidrake-v

from both, and also

Code: Select all: lscpu

TIA

this may be of interest => https://bugs.chromium.org/p/chromium/is ... ?id=828462

Yes. Because the computers aren't quite new, I disabled hardware acceleration on both, because the web browsers used with previous distros caused some issues (but no actual crashes) unless it was disabled. I have not updated the other computer in a couple of weeks, it's due for updating, but it also occurred on that system as well, which is two years older than the system I'm on now. That system has a PCI-Express video card installed (with an AMD Radeon (Cedar)), this system is using its on-board GPU.

I'm not familiar with Chromium 'appimage', I have no idea what that is. The BIOS' on both systems do not have a setting for hardware acceleration that I know of.

The bug report has since been updated, as someone was able to duplicate the crashes.

Code: Select all: ~]$ lspcidrake -v ohci_pci : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0 USB OHCI1 Controller [SERIAL_USB] (vendor:1002 device:4398 subv:103c subd:2ab7) i2c_piix4 : Advanced Micro Devices, Inc. [AMD/ATI]|SBx00 SMBus Controller [SERIAL_SMBUS] (vendor:1002 device:4385 subv:103c subd:2ab7) (rev: 3c) unknown : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:1002 device:4391 subv:103c subd:2ab7) snd_hda_intel : Advanced Micro Devices, Inc. [AMD/ATI]|SBx00 Azalia (Intel HDA) [MULTIMEDIA_AUDIO_DEV] (vendor:1002 device:4383 subv:103c subd:2ab7) Card : ATI Radeon HD 4870 and earlier: Advanced Micro Devices, Inc. [AMD/ATI]|RS780L [Radeon 3000] [DISPLAY_VGA] (vendor:1002 device:9616 subv:103c subd:2ab7) unknown : Advanced Micro Devices, Inc. [AMD/ATI]|SBx00 PCI to PCI Bridge [BRIDGE_PCI] (vendor:1002 device:4384) unknown : Advanced Micro Devices, Inc. [AMD]|Family 10h Processor HyperTransport Configuration [BRIDGE_HOST] (vendor:1022 device:1200) ohci_pci : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0 USB OHCI1 Controller [SERIAL_USB] (vendor:1002 device:4398 subv:103c subd:2ab7) unknown : Advanced Micro Devices, Inc. [AMD]|Family 10h Processor DRAM Controller [BRIDGE_HOST] (vendor:1022 device:1202) ohci_pci : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [SERIAL_USB] (vendor:1002 device:4397 subv:103c subd:2ab7) unknown : Advanced Micro Devices, Inc. [AMD]|Family 10h Processor Link Control [BRIDGE_HOST] (vendor:1022 device:1204) unknown : Advanced Micro Devices, Inc. [AMD]|RS780 Host Bridge [BRIDGE_HOST] (vendor:1022 device:9600 subv:103c subd:2ab7) ehci_pci : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0/SB8x0/SB9x0 USB EHCI Controller [SERIAL_USB] (vendor:1002 device:4396 subv:103c subd:2ab7) unknown : Advanced Micro Devices, Inc. [AMD]|RS780/RS880 PCI to PCI bridge (PCIE port 3) [BRIDGE_PCI] (vendor:1022 device:9607) unknown : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0/SB8x0/SB9x0 LPC host controller [BRIDGE_ISA] (vendor:1002 device:439d subv:103c subd:2ab7) ohci_pci : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [SERIAL_USB] (vendor:1002 device:4397 subv:103c subd:2ab7) unknown : Advanced Micro Devices, Inc. [AMD]|RS780/RS880 PCI to PCI bridge (int gfx) [BRIDGE_PCI] (vendor:1022 device:9602) r8169 : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:7470 subd:3468) (rev: 06) unknown : Advanced Micro Devices, Inc. [AMD]|Family 10h Processor Address Map [BRIDGE_HOST] (vendor:1022 device:1201) ehci_pci : Advanced Micro Devices, Inc. [AMD/ATI]|SB7x0/SB8x0/SB9x0 USB EHCI Controller [SERIAL_USB] (vendor:1002 device:4396 subv:103c subd:2ab7) k10temp : Advanced Micro Devices, Inc. [AMD]|Family 10h Processor Miscellaneous Control [BRIDGE_HOST] (vendor:1022 device:1203) hub : Linux 5.15.18-desktop-2.mga8 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) hub : Alcor Micro Corp.|USB Hub [Hub|Unused|Full speed (or root) hub] (vendor:058f device:6254) btusb : Broadcom Corp|BCM20702A0 (vendor:0a5c device:21e8) usbhid : Unknown|USB OPTICAL MOUSE [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:30fa device:0300) hub : Linux 5.15.18-desktop-2.mga8 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) usb_storage : Generic|Mass Storage Device [Mass Storage|SCSI|Bulk-Only] (vendor:058f device:6366) hub : Linux 5.15.18-desktop-2.mga8 ohci_hcd|OHCI PCI host controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001) usbhid : SONiX|USB DEVICE [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:0c45 device:8517) hub : Linux 5.15.18-desktop-2.mga8 ohci_hcd|OHCI PCI host controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001) hub : Linux 5.15.18-desktop-2.mga8 ohci_hcd|OHCI PCI host controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001) hub : Linux 5.15.18-desktop-2.mga8 ohci_hcd|OHCI PCI host controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001) hid_generic : SONiX USB DEVICE hid_generic : USB OPTICAL MOUSE hid_generic : SONiX USB DEVICE ~]$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 16 Model: 6 Model name: AMD Athlon(tm) II X2 260 Processor Stepping: 3 CPU MHz: 800.000 CPU max MHz: 3200.0000 CPU min MHz: 800.0000 BogoMIPS: 6399.98 Virtualization: AMD-V L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 2 MiB NUMA node0 CPU(s): 0,1 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Not affected Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user poin ter sanitization Vulnerability Spectre v2: Mitigation; Full AMD retpoline, STIBP disabled, RSB filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht sys call nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3 dnow constant_tsc rep_good nopl nonstop_tsc cpuid ex td_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowp refetch osvw ibs skinit wdt hw_pstate vmmcall npt lb rv svm_lock nrip_save

epp wrote: 'appimage', I have no idea what that is.

https://wiki.mageia.org/en/Ways_to_inst ... s#Appimage
https://apprepo.de/appimage/chromium

Thank you for the link to the AppImage.

It downloaded version 100.0.4866.0 (Developer Build) and in using it, it has not crashed. I'm not able to replicate the crashes with the Mageia-provided Chromium package.

The setting to use hardware acceleration was off by default. With the setting turned on, Chromium closed, but did not automatically relaunch. Upon relaunch, the setting remained on, but still no crashes.

When launching it from the terminal, this is the resulting output:

Code: Select all: ]$ ./Chromium.AppImage Gtk-Message: 12:39:37.505: Failed to load module "canberra-gtk-module" [13197:13197:0202/123942.174242:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [13160:13185:0202/124102.822511:ERROR:database.cc(1777)] History SQLite error: code 1555 errno 0: UNIQUE constraint failed: context_annotations.visit_id sql: INSERT INTO context_annotations( visit_id,context_annotation_flags,duration_since_last_visit,page_end_reason,total_foreground_duration )VALUES(?,?,?,?,?) [13160:13948:0202/124133.782491:ERROR:database.cc(1777)] History SQLite error: code 1555 errno 0: UNIQUE constraint failed: context_annotations.visit_id sql: INSERT INTO context_annotations( visit_id,context_annotation_flags,duration_since_last_visit,page_end_reason,total_foreground_duration )VALUES(?,?,?,?,?) Gtk-Message: 12:42:24.494: Failed to load module "canberra-gtk-module"

epp wrote:It downloaded version 100.0.4866.0 (Developer Build) and in using it, it has not crashed

ok, so you have a choice as to continue with the appimage, or wait until the Mageia packaged one is fixed.

As you have noted, your issue was replicated by QA, so it *may* get re-packaged.

best test would be wait until Mageia has the above version in testing, and then compare them.

note that the appimage will likely check for newer releases and prompt to update. being a developer build, this is likely to occur regularly, ie daily.

I noticed Mageia's package is also a Developer Build per About Chromium.

I'm marking this thread SOLVED, since subsequent versions of Chromium have not had this issue.

Mageia forum

[SOLVED] Chromium not closing correctly

[SOLVED] Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly (upstream)

Re: Chromium not closing correctly (upstream)

Re: Chromium not closing correctly (upstream)

Re: Chromium not closing correctly (upstream)

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly

Re: Chromium not closing correctly