https://bugs.kde.org/show_bug.cgi?id=507691
--- Comment #18 from Brent Spillner <[email protected]> --- Interesting that your crash also seems to be initiated within libfontconfig; this was the stderr output immediately preceding my latest crash during screen wakeup/unlock: Fontconfig error: Cannot load default config file: No such file: (null) [25997:25997:0207/180917.317811:ERROR:mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:732] Message 5 rejected by interface blink.mojom.WidgetHost [26064:26064:0207/180917.318153:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. [26064:26064:0207/180917.322915:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. [26064:26064:0207/180917.327087:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. [26064:26064:0207/180917.328715:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. Fontconfig error: Cannot load default config file: No such file: (null) QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap wl_registry#61: error 0: invalid global kde_output_device_v2 (184) QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread interface_endpoint_client.cc, shared_image_manager.cc, ssl_client_socket_impl.cc, and the blink.mojom.WidgetHost interface are all part of Chromium, which I had running in the background (as I usually do) at the time of the crash. I'm not sure that's directly the culprit, as Chromium itself never crashes when plasmashell does, and as noted in #512448, I have had plasmashell crashes even when Chromium wasn't running. However, it seems suspicious that in both Russell's traces and mine, FcConfigParse() makes a failed call to FcConfigFileExists(), which apparently returns NULL in my cases and triggers a fault within access(2) in his. FWIW, I do have both an /etc/fonts/fonts.conf and ~/.config/fontconfig/fonts.conf, and both files are readable and well-formed. Obviously, fontconfig has nothing directly to do with Wayland protocol calls, but it appears these errors may be setting up some kind of inconsistent or incomplete client state (e.g. Chromium continuing to try to render a pixmap after ProduceSkia() failed to actually produce it). Of course, in an ideal world plasmashell would not be so fragile in the face of client/helper application crashes, even kioworker. -- You are receiving this mail because: You are watching all bug changes.
