On Tuesday, October 14, 2025 7:04:54 AM Mountain Standard Time Andy Wood wrote: > Replying to my own thread ... > > I think this relates to a serious problem with QtWebEngine. > > Installing the (forky) falkon browser (lightweight web browser based on Qt > WebEngine) and running it from the command line gives the following: > > $ falkon > GBM is not supported with the current configuration. Fallback to Vulkan > rendering in Chromium. > Library plugin "KDEFrameworksIntegration.so" not found > Falkon: 1 extensions loaded > Segmentation fault (core dumped) falkon > > Andy. > > On Monday, 13 October 2025 17:03 Andy Wood wrote: > > After working for many years, today I cannot re-authenticate to a Corporate > > O365 system. The pop-up that normally prompts for password and OTP crashes. > > > > Up to date Debian forky system. > > > > Don't really know how to debug this, but tried: > > /usr/bin/akonadi_ews_resource --identifier akonadi_ews_resource_4 > > > > and the final message is: > > KCrash: Application 'akonadi_ews_resource' crashing... crashRecursionCounter > > = 2 > > Segmentation fault (core dumped). > > > > Is this part of kdepim-addons? When I run Falkon from the command line I get this: $ falkon ProfileManager: Updated UserAgent per domain settings Library plugin "KDEFrameworksIntegration.so" not found Falkon: 1 extensions loaded Falkon starts and runs as expected. This means that the `Library plugin "KDEFrameworksIntegration.so" not found` message is not a critical failure. I am running Wayland if that end up being important. My guess is that whatever is causing `GBM is not supported with the current configuration` is the core of your issue with Falkon (and possibly with O365). -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.