Bug 501866

Summary: Breaks official Minecraft Launcher
Product: [Plasma] plasma-browser-integration Reporter: Phillip Schichtel <phillip>
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: CONFIRMED ---    
Severity: normal CC: brokencanoe, yurii.kolesnykov
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Phillip Schichtel 2025-03-22 15:45:23 UTC 
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY

The plasma browser extension, when installed as a system-wide chromium extension as done by Arch's "plasma-browser-integration" package, then Minecraft's official launcher, which indirectly uses CEF, picks up the extension and fails to properly start after an initial successful start. A workaround has been to remove CEF's "Preferences", which resolves the issue for the next start.

The launcher shows a very unspecific "Whoops!" page. Logs:

```
sh: line 1: orca: command not found
Created browser window for reuse: 0x3600004
[80097:80097:0322/163825.278925:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[80097:80145:0322/163825.333215:ERROR:cert_verify_proc_builtin.cc(1063)] CertVerifyProcBuiltin for mojang failed:
----- Certificate i=0 (CN=Kubernetes Ingress Controller Fake Certificate,O=Acme Co) -----
ERROR: No matching issuer found


[80156:80190:0322/163825.333360:ERROR:ssl_client_socket_impl.cc(883)] handshake failed; returned -1, SSL error code 1, net_error -202
[80097:80138:0322/163825.333502:ERROR:cert_verify_proc_builtin.cc(1063)] CertVerifyProcBuiltin for mojang failed:
----- Certificate i=0 (CN=Kubernetes Ingress Controller Fake Certificate,O=Acme Co) -----
ERROR: No matching issuer found


[80156:80190:0322/163825.333552:ERROR:ssl_client_socket_impl.cc(883)] handshake failed; returned -1, SSL error code 1, net_error -202
[80156:80190:0322/163825.441120:ERROR:ssl_client_socket_impl.cc(883)] handshake failed; returned -1, SSL error code 1, net_error -202
[80097:80141:0322/163825.756005:ERROR:mime_util_xdg.cc(137)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44
[80154:80154:0322/163829.357329:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[80154:80154:0322/163829.358467:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[80154:80154:0322/163836.930804:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
```

The first report of the issue on minecraft-launcher's AUR page was this comment https://aur.archlinux.org/packages/minecraft-launcher?O=10#comment-1014382 from the 5th of march, however it didn't start happening for everyone at the same time I think, because at least for me it wasn't reproducible at that time.

STEPS TO REPRODUCE
(assume archlinux)

1. install "plasma-browser-integration"
2. start minecraft launcher (downloaded from https://www.minecraft.net/en-us/download or via packages)
3. stop the launcher and start it again

OBSERVED RESULT

Launcher presents a "Whoops!" page.

EXPECTED RESULT

Launcher starts up normally.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 Phillip Schichtel 2025-03-22 15:56:17 UTC 
Bug report over at Mojang: https://report.bugs.mojang.com/servicedesk/customer/portal/2/MC-295726
Comment 2 Canoe 2025-03-23 14:01:55 UTC 
Confirmed : 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 3 Kai Uwe Broulik 2025-03-23 14:40:27 UTC 
wtf. Can confirm. Why is it even picking up browser extensions?! We install (depending on distro) a policy file that instructs Chrome/Chromium to auto-install the extension. It makes no sense for non-browser apps to honor this. Tell them to fix their launcher, please.

Unfortunately, developer tools are not accessible form this app, so I cannot debug or investigate.
Comment 4 Phillip Schichtel 2025-03-23 19:24:09 UTC 
(In reply to Kai Uwe Broulik from comment #3)
> wtf. Can confirm. Why is it even picking up browser extensions?! We install
> (depending on distro) a policy file that instructs Chrome/Chromium to
> auto-install the extension. It makes no sense for non-browser apps to honor
> this. Tell them to fix their launcher, please.
> 
> Unfortunately, developer tools are not accessible form this app, so I cannot
> debug or investigate.

Do you have any rough pointers for them to go about preventing it from picking up the extensions? Also: Would there be anything on the packaging side that I could do?
Comment 5 Kai Uwe Broulik 2025-03-24 14:28:23 UTC 
We install a policy file [1] for Chrome and Chromium [2] that instructs Chromium to auto-install the extension. Sadly I cannot find the recent documentation for this, the one I had bookmarked is gone [3].

[1] https://invent.kde.org/plasma/plasma-browser-integration/-/blob/master/chrome_install_from_store_policy?ref_type=heads

[2] https://invent.kde.org/plasma/plasma-browser-integration/-/blob/master/CMakeLists.txt?ref_type=heads#L117

[3] https://www.chromium.org/administrators/policy-list-3/#ExtensionInstallForcelist