Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Upgrading packages that plasmashell depended on.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Downgrading the packages.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Output from when attempting to run plasmashell now:

$ plasmashell
Invalid Context= "places" line for icon theme:  "/usr/share/icons/DarkPurpy/48x48/places/"
org.kde.plasmaquick: Applet preload policy set to 1
Empty filename passed to function
last screen is < 0 so putting containment on screen  0
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/bin/plasmashell directly
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 21165
KCrash: Arguments: /usr/bin/plasmashell
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi directly
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
"Message recipient disconnected from message bus without replying"
QSystemTrayIcon::setVisible: No Icon set

[1]+  Stopped                 plasmashell

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Logging onto KDE after being locked out using <Meta>-L (lockscreen manually)
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   Sometimes I need to restart plasma shell which can be done from the crash
program. Cores occur frequently.  Apparently I cannot send cores because they
are too big.
   * What was the outcome of this action?
   Plasma shell is restarted as you would expect.
   * What outcome did you expect instead?
   I would prefer plasma shell did not dump core.


  Message: Process 536551 (plasmashell) of user 1040 dumped core.

                Module libsystemd.so.0 from deb systemd-252.36-1~deb12u1.amd64
                Module libudev.so.1 from deb systemd-252.36-1~deb12u1.amd64
                Stack trace of thread 536551:
                #0  0x00007f860faa9eec n/a (libc.so.6 + 0x8aeec)
                #1  0x00007f860fa5afb2 raise (libc.so.6 + 0x3bfb2)
                #2  0x00007f861206c83d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x583d)
                #3  0x00007f860fa5b050 n/a (libc.so.6 + 0x3c050)
                #4  0x0000561604fac370 n/a (plasmashell + 0x38370)
                #5  0x0000561604fc74c0 n/a (plasmashell + 0x534c0)
                #6  0x00007f860fee8f8f n/a (libQt5Core.so.5 + 0x2e8f8f)
                #7  0x00007f860feecdaa _ZN6QTimer7timeoutENS_14QPrivateSignalE
(libQt5Core.so.5 + 0x2ecdaa)
                #8  0x00007f860fedd54d _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x2dd54d)
                #9  0x00007f8610b62fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
                #10 0x00007f860feb1738
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b1738)
                #11 0x00007f860ff08c71 _ZN14QTimerInfoList14activateTimersEv
(libQt5Core.so.5 + 0x308c71)
                #12 0x00007f860ff0953c n/a (libQt5Core.so.5 + 0x30953c)
                #13 0x00007f860e8737a9 g_main_context_dispatch
(libglib-2.0.so.0 + 0x547a9)
                #14 0x00007f860e873a38 n/a (libglib-2.0.so.0 + 0x54a38)
                #15 0x00007f860e873acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
                #16 0x00007f860ff09876
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309876)
                #17 0x00007f860feb01bb
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b01bb)
                #18 0x00007f860feb8316 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2b8316)
                #19 0x0000561604f9adc3 n/a (plasmashell + 0x26dc3)
                #20 0x00007f860fa4624a n/a (libc.so.6 + 0x2724a)
                #21 0x00007f860fa46305 __libc_start_main (libc.so.6 + 0x27305)
                #22 0x0000561604f9aee1 n/a (plasmashell + 0x26ee1)

*** End of the template - remove these template lines ***

The crash tool that allows the crash to restart is called "The KDE
Crash Handler".  Because the KDE Crash handler allows restarting of
plasma shell in the event that it is no longer running causes this
problem to easily be worked around.  But the problem happens very
frequently, though not always reproducible.

Sorry about my misunderstanding on how exactly to fill out the bug report form.