https://bugs.kde.org/show_bug.cgi?id=512448

--- Comment #4 from Brent Spillner <[email protected]> ---
I avoid systemd so I don't have coredumpctl, and my coredumpsize ulimit in that
session was zero anyway.  However, plasmashell just crashed again, so I've
restarted it under GDB (although my system package has debugging symbols
stripped) and will share the dump from the next crash.

The stderr output from this crash is pasted below; it looks like the "invalid
global kde_output_device_v2" message is still the common denominator, with the
crash sequence always unfolding the same way from that point on, although there
may be several different preceding trigger paths:

[21023:21197:1126/062516.386730:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:526]
SharedImageManager::ProduceMemory: Trying to Produce a Memory representation
from a non-existent mailbox.
[21023:21197:1126/062516.386791:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:526]
SharedImageManager::ProduceMemory: Trying to Produce a Memory representation
from a non-existent mailbox.
[21023:21197:1126/062516.386818:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:526]
SharedImageManager::ProduceMemory: Trying to Produce a Memory representation
from a non-existent mailbox.
[21023:21197:1126/062516.386872:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:526]
SharedImageManager::ProduceMemory: Trying to Produce a Memory representation
from a non-existent mailbox.
[21023:21197:1126/062516.386895:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:526]
SharedImageManager::ProduceMemory: Trying to Produce a Memory representation
from a non-existent mailbox.
[21023:21197:1126/062516.386914:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:526]
SharedImageManager::ProduceMemory: Trying to Produce a Memory representation
from a non-existent mailbox.
wl_registry#51: error 0: invalid global kde_output_device_v2 (208)
warning: queue "mesa egl surface queue" 0x7f9a2cb1ef00 destroyed while proxies
still attached:
  wp_presentation#43 still attached
qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)

The Wayland connection experienced a fatal error: Protocol error

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to