Hello Sarah, I am sorry, but the given information might not be enough for the maintainers to solve the crash.
Usually when a segfault happens in 'dmesg' output should appear two lines about this event. Maybe you could forward these to the report too. If it is possible to install systemd-coredump a backtrace would be automatically added to the journal, which could be viewed by 'journalctl --no-pager'. 'coredumpctl gdb' could also show these information and if the package gdb is also installed a '(gdb)' prompt should appear, where the command 'thread apply all bt full' should provide detailed information where the crash happened. This information would be much better if the package plasma-workspace-dbgsym and maybe some for shared libraries get installed from the repository described here [1]. (If output gets too much pages, maybe attach as file.) Kind regards Bernhard [1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols