Bug 6: Renderer task manager bug

Description:
Known Chromium bug still present:

ERROR:fallback_task_provider.cc:126 Every renderer should have at least one task
  provided by a primary task provider.

Reference: crbug.com/739782

Touch extension throws unhandled errors

Description:
Built-in touch communication extension throws errors on startup:

ERROR:CONSOLE:503 "Uncaught (in promise) Error"
  source: chrome-extension://ebongfbmlegepmkkdjlnlmdcmckedlal/touch_communication.js

Appears twice during each launch.

Bug 4: GCM push notifications use deprecated endpoint

Description:
Repeated 4+ times on every session:

ERROR:registration_request.cc:290 Registration response error message: DEPRECATED_ENDPOINT

Google Cloud Messaging registration endpoint is deprecated.

Bug 3: Built-in extensions fail content verification

Description:
Fresh install, no user extensions. Multiple Opera-bundled extensions fail content verification:

ERROR:content_hash.cc:267 Fetching verified_contents.json failed
  for extension ddfjocfgcmcbeejfjefghoegecamfbof version 2.0 (error -300)
ERROR:content_hash.cc:267 Fetching verified_contents.json failed
  for extension eaahgnceaiheanheajmiojafolhdfbih version 1.5 (error -300)
ERROR:content_hash.cc:267 Fetching verified_contents.json failed
  for extension fbjgnhgkjlcbbmdflhhegadcjmmlnlfp version 1.0.6 (error -300)

Followed by multiple verification failures for files in extension ddfjocfgcmcbeejfjefghoegecamfbof (GX wallpaper/modding):

Content verify job failed at path: webmodding/opera.css
Content verify job failed at path: wallpaper/My Movie 48.webm

Error -300 indicates a fetch/network failure for Opera's own bundled extensions.

Bug 2: Wayland sRGB color space initialization fails

Description:
On every startup, sRGB color space fails to initialize on Wayland:

ERROR:wayland_wp_color_manager.cc:277 Unable to set image transfer function.
ERROR:wayland_wp_color_manager.cc:195 Failed to populate image description for
  color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}

Appears twice during each launch.

Environment:

• Opera GX: opera-gx-stable 129.0.5823.26 (amd64)
• OS: Arch Linux (rolling)
• Kernel: 6.19.9-arch1-1
• Desktop: KDE Plasma / Wayland (wayland-0)
• Shell: fish
• CPU: AMD Ryzen 7 7800X3D 8-Core Processor
• GPU: AMD Radeon RX 7900 XTX (RDNA3, navi31)
• GPU driver: Mesa 26.0.3 (radeonsi, ACO)
• Locale: fr_FR.UTF-8

System libraries:

• glibc 2.43
• Mesa 26.0.3 / vulkan-radeon 26.0.3
• Qt6 6.10.2 (qt6-base + qt6-wayland + qt6-tools)
• NSS 3.122

Logs collected with: opera-gx --enable-logging --v=1

Bug 1: "Set as default browser" banner cannot be dismissed

Description:
Opera GX shows the "Set as default browser" banner on every launch, even when it IS the system default browser. The banner reappears after every restart.

Verified with:

$ xdg-settings get default-web-browser
opera-gx.desktop

Tested workarounds (none work):

• Setting Opera GX as default via xdg-settings set default-web-browser opera-gx.desktop
• Creating opera-gx-stable.desktop and setting it as default
• Setting "check_default_browser":false in ~/.config/opera-gx/Default/Preferences (overwritten on launch)
• Dismissing with X button (reappears on restart)
• Installing qtpaths symlink in /usr/bin/

Possibly related log entry:

/usr/bin/xdg-mime: ligne 885: qtpaths: commande introuvable

Opera GX internally calls xdg-mime which requires qtpaths. On Arch Linux, qtpaths is installed at /usr/lib/qt6/bin/ but not in the default PATH. Even after adding a symlink in /usr/bin/, the banner persists.

Note: Opera Stable 129.0.5823.22 does NOT show this banner on the same system.

Update: Fixed in version 129.0.5823.26. Opera GX now launches correctly on the same system. The crash was specific to version 128.0.5807.97.

Environment:

• Opera GX: opera-gx-stable 128.0.5807.97 (amd64)
• OS: Arch Linux (rolling)
• Kernel: 6.19.9-arch1-1
• Desktop: KDE Plasma / Wayland (wayland-0)
• Shell: fish
• CPU: AMD Ryzen 7 7800X3D 8-Core Processor
• GPU: AMD Radeon RX 7900 XTX (RDNA3, navi31)
• GPU driver: Mesa 26.0.3 (radeonsi, ACO)
• Locale: fr_FR.UTF-8

System libraries:

• glibc 2.43
• Mesa 26.0.3 / vulkan-radeon 26.0.3
• Qt6 6.10.2 (qt6-base + qt6-wayland)
• NSS 3.122

Pre-checks:

• No missing shared libraries (ldd reports all found)
• No existing config directory (fresh install, no corrupted profile)
• No SELinux/AppArmor restrictions
• Binary SHA256: 69ebb502188db6fa2b0f2ba9e296105d5cfcb1ea47a6fa22aaacde1798fadce3
• Package source: official .deb from deb.opera.com, unmodified

Description:
Opera GX crashes immediately on startup with Signal 11 (SEGV) before any window appears. The crash is 100% reproducible and always occurs at the same offset (opera + 0x9780767). This is a fresh install with no prior configuration.

Comparison with other browsers on same system:

• Opera Stable 129.0.5823.22: works perfectly
• Brave 1.88.136 (Chromium 146): works perfectly
• Opera GX 128.0.5807.97: SEGV on startup

All three are Chromium-based. Only Opera GX crashes. This confirms the issue is 100% Opera GX-specific, not related to GPU drivers, Mesa, kernel, Wayland, or system libraries.

Tested workarounds (all crash identically at the same offset):

• opera-gx (default, Wayland)
• opera-gx --ozone-platform=x11
• opera-gx --no-sandbox
• opera-gx --disable-gpu
• opera-gx --no-sandbox --ozone-platform=x11
• opera-gx --disable-gpu --ozone-platform=x11

Crash stack trace (offsets from opera binary):

Signal: 11 (SEGV)
#0  0x9780767
#1  0xa5fbea3
#2  0xa5fbe2e
#3  0x87ec0bb
#4  0x87ebed0
#5  0x87eae23
#6  0x87e4517
#7  0x7bedb9b
#8  0x2f8de7b
#9  0x892646c
#10 0x8e6512e
#11 0x8925539
#12 0x90659b1
#13 0x9063084
#14 0x4ed2708
#15 0x4ed1c88
#16 0x7a9008c
#17 0x7a8e12c
#18 0x4ef43dc
#19 0x4b565b9
#20 0x4b563e5
#21 0x6e58ef6
#22 0x6e55a77
#23 0x8fc5458
#24 0x8fc511a
#25 0x8fc28a3
#26 0x4a9b73d  ChromeMain

Notes:

• Crash offset 0x9780767 is identical across all attempts, regardless of flags or display server
• Crash occurs during early initialization, before any UI renders
• Opera Stable works fine on the exact same system, proving this is not a driver/system issue
• The crash may be related to GX-specific initialization code (gaming features, GX Control, etc.)