Announcement

**TheSupremeVizier** · Aug 15, 2025, 05:19 PM

Plasma crashed again. I have included the output of "journalctl -b -0 -r" below. I looked around for a core dump but couldn't find one associated with this event. I was using Chromium and looking at https://compare.porsche.com/en-US?mo...series=cayenne . Allow me to dream a bit, OK? ;-) I did find a core dump in /var/crash/_usr_bin_plasmashell.1000.crash but that is from one week ago. It's also 72 MB, and I've got no clue where to put it for your review. ;-)

Code:

Aug 15 17:46:45 <hostname> sudo[19821]:    <username> : TTY=pts/4 ; PWD=/home/<username> ; USER=root ; COMMAND=/usr/bin/journalctl -b -0 -r
Aug 15 17:46:04 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:04 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:02 <hostname> plasmashell[19721]: file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PrinterItem.qml:22:5: Unable to assign [undefined] to bool
Aug 15 17:46:02 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:02 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:01 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_13_00.6.analog-stereo.monitor"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Aug 15 17:46:00 <hostname> plasmashell[19721]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 15 17:46:00 <hostname> plasmashell[19721]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Aug 15 17:46:00 <hostname> plasmashell[19721]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignmen>
Aug 15 17:46:00 <hostname> plasmashell[19721]: kde.dataengine.mpris: "org.mpris.MediaPlayer2.chromium.instance4114" has an invalid URL for the mpris:artUrl entry of the "Metadata" property
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/main.qml:30:5: Unable to assign [undefined] to bool
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
Aug 15 17:46:00 <hostname> plasmashell[19721]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/pla>
Aug 15 17:46:00 <hostname> plasmashell[19721]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/pla>
Aug 15 17:46:00 <hostname> plasmashell[19721]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/main.qml:30:5: Unable to assign [undefined] to bool
Aug 15 17:45:59 <hostname> plasmashell[19721]: org.kde.plasma.kicker: Kicker.WindowSystem is deprecated and will be removed in Plasma 6. Use KWindowSystem/KX11Extras instead.
Aug 15 17:45:59 <hostname> plasmashell[19721]: org.kde.plasma.kicker: DragHelper is deprecated and will be removed in Plasma 6. Use Qt Quick Drag instead.
Aug 15 17:45:59 <hostname> plasmashell[19721]: org.kde.plasma.kicker: Kicker.WindowSystem is deprecated and will be removed in Plasma 6. Use KWindowSystem/KX11Extras instead.
Aug 15 17:45:59 <hostname> plasmashell[19721]: org.kde.plasma.kicker: DragHelper is deprecated and will be removed in Plasma 6. Use Qt Quick Drag instead.
Aug 15 17:45:59 <hostname> dbus-daemon[3200]: [session uid=1000 pid=3200] Activating service name='org.kde.KSplash' requested by ':1.152' (uid=1000 pid=19721 comm="/usr/bin/plasmashell --no-respawn" label=>
Aug 15 17:45:59 <hostname> plasmashell[19721]: libpng warning: iCCP: known incorrect sRGB profile
Aug 15 17:45:59 <hostname> plasmashell[19721]: kf.plasma.quick: Applet preload policy set to 1
Aug 15 17:45:59 <hostname> systemd[3178]: Started plasma-plasmashell.service - KDE Plasma Workspace.
Aug 15 17:45:59 <hostname> plasmashell[19721]: Checking screens: available: (QScreen(0x5c195602cfe0, name="DP-3"), QScreen(0x5c195602d020, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5c19>
Aug 15 17:45:59 <hostname> plasmashell[19721]: Checking screens: available: (QScreen(0x5c195602cfe0, name="DP-3"), QScreen(0x5c195602d020, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5c19>
Aug 15 17:45:59 <hostname> systemd[3178]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Consumed 25.022s CPU time.
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Failed with result 'core-dump'.
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Aug 15 17:45:57 <hostname> plasmashell[3495]: Re-raising signal for core dump handling.
Aug 15 17:45:57 <hostname> plasmashell[3495]: Unable to start Dr. Konqi
Aug 15 17:45:57 <hostname> plasmashell[3495]: QSocketNotifier: Invalid socket 32 and type 'Read', disabling...
Aug 15 17:45:59 <hostname> plasmashell[19721]: kf.plasma.quick: Applet preload policy set to 1
Aug 15 17:45:59 <hostname> systemd[3178]: Started plasma-plasmashell.service - KDE Plasma Workspace.
Aug 15 17:45:59 <hostname> plasmashell[19721]: Checking screens: available: (QScreen(0x5c195602cfe0, name="DP-3"), QScreen(0x5c195602d020, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5c195602cfe0, name="DP-3"), QScreen(0x5c195602d020, name="DP-1"))
Aug 15 17:45:59 <hostname> plasmashell[19721]: Checking screens: available: (QScreen(0x5c195602cfe0, name="DP-3"), QScreen(0x5c195602d020, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5c195602cfe0, name="DP-3"), QScreen(0x5c195602d020, name="DP-1"))
Aug 15 17:45:59 <hostname> systemd[3178]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Consumed 25.022s CPU time.
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Failed with result 'core-dump'.
Aug 15 17:45:59 <hostname> systemd[3178]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Aug 15 17:45:57 <hostname> plasmashell[3495]: Re-raising signal for core dump handling.
Aug 15 17:45:57 <hostname> plasmashell[3495]: Unable to start Dr. Konqi
Aug 15 17:45:57 <hostname> plasmashell[3495]: QSocketNotifier: Invalid socket 32 and type 'Read', disabling...
Aug 15 17:45:57 <hostname> plasmashell[3495]: QSocketNotifier: Invalid socket 29 and type 'Read', disabling...
Aug 15 17:45:57 <hostname> plasmashell[3495]: QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
Aug 15 17:45:57 <hostname> plasmashell[3495]: QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
Aug 15 17:45:52 <hostname> plasmashell[3495]: KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Aug 15 17:45:52 <hostname> plasmashell[3495]: KCrash: Arguments: /usr/bin/plasmashell --no-respawn
Aug 15 17:45:52 <hostname> plasmashell[3495]: KCrash: Application Name = plasmashell path = /usr/bin pid = 3495
Aug 15 17:45:52 <hostname> plasmashell[3495]: KCrash: crashing... crashRecursionCounter = 2

**deadsplash** · Aug 16, 2025, 02:00 PM

Do you install custom widget or themes?

**TheSupremeVizier** · Aug 17, 2025, 05:43 PM

Hi, deadsplash.

I don't think I've installed any custom widgets or themes, unless your definition of custom differs from mine. Anything I've used to modify my display "theme" was selected inside System Settings -> Appearance -> Global Theme, where I selected Sweet, which contains "desktop layout". Frankly, I don't think I know what the definition of a widget is in the first place. Any widgets that *might* have been added were selected one of two ways: (1) by right-clicking on the desktop and selecting "+ Add Widgets" which then presented "widgets" such as "Calculator", or (2) I left click on the Application Launcher and then find the desired executable...say KCalc...and then I right click on that executable in the GUI and select "+ Add to Desktop". The icon or widget is then found on the desktop and I move it to what I believe is the appropriate location. Interesting to me is that I have a Desktop directory at ~/Desktop which contains only three files: two of those widgets are associated with games obtained through Steam and they have filenames like "<GameName>.desktop. The third widget-associated file is "gkrellm-gkrellm-2.desktop" and it is a link to /usr/share/applications/gkrellm-gkrellm-2.desktop, but there is no such file at that location. (I run three instances of gkrellm on only one monitor so I can monitor all the CPUs, partitions, LAN, temperatures, etc.) Obviously, many of these icons/widgets must be defined somewhere else other than ~/Desktop. I have two monitors and I have duplicated the icons/widgets on each of those monitors. I have 4 desktops and each desktop spans the two monitors. I can right click each of these desktop icons/widgets and view Properties of each of these icons/widgets, such as under the Application tab, where it tells me the Program path. This information must be supplied in a file in a directory somewhere, but I'm not a KDE guru, so I don't know where. (I just did a "find" search and found a lot of files with the "desktop" suffix under the ~/.local subdirectory.)

I have been running KDE a long time, long before I started using Kubuntu, and after I installed Kubuntu, I then loaded my user space, which contains files from my previous system. I did not have any plasma crashes when I first did this into that Kubuntu LTS. I performed the upgrade to 24.04 LTS on that older system and did not experience plasma crashes. That system was over a decade old when the motherboard died. I then built this new system, loaded the same Kubuntu LTS as I had previously upgraded onto the now-dead system, and only then did I start to experience plasma crashes. Again, I did not have this plasma-crashing issue on the now-dead system with my previous Kubuntu installation which was the LTS system that preceded 24.04 and I did not have the plasma-crashing issue on the now-dead system after upgrading to 24.04 LTS. I am having the plasma-crash issues on new hardware with the 24.04 LTS. I am allegedly running the same user space files that were saved off from that previous Kubuntu LTS installation.

I hope I've answered your question adequately.

**skyfishgoo** · Aug 18, 2025, 06:08 AM

create a new user and see if the issues still occur with that acct... that will tell you if its your settings or your system that's borked.

**TheSupremeVizier** · Aug 18, 2025, 05:28 PM

I will try creating a new user, but it might take a lot of time to replicate the issue. There are 29 icons/widgets on each of two monitors. There are three gkrellms running on one monitor. I will need to replicate everything else on the monitors, such as background images. I will need to replicate all Appearance, Workspace, Personalization, Display/Monitor, Audio and other settings inside System Settings. If after all that effort, I have exactly replicated the display and there are no plasma crashes, I will then have to consider what parts of my current "old" account do NOT need to be transferred into the new account. If I eventually get it so that all the functionality of my old account is in my new account, then I will consider closing the old account and keeping the new account. And if plasma crashes somewhere during this "migration", maybe I will have learned something about the cause.

**TheSupremeVizier** · Aug 19, 2025, 06:51 PM

I took a break while creating a new user and filling the desktop with appropriate icons/widgets. One thing I noticed is that the problematic (older) account has specified Desktop layout under Desktop Settings -> Wallpaper, while the new account has defaulted to Folder View. I don't know what this implies with respect to configuration layout. I don't know if this will make a difference or not, and if I were to switch the newer account from Folder View to Desktop, what would happen to all the icons/widgets I have already placed on the two monitors. It would be nice to know this before proceding further.

When I say I took a break, what I really meant is that I placed the desktop into "Sleep" mode at the time I took a break. When I came back from my break and I returned the system to running mode, there was an almost immediate plasma crash. I am providing a truncated output of "journalctl -b -0 -r" below. When I say "truncated", I mean that I have done my best to visually reduce alphanumerically identical statements from the log presented here while also keeping log order intact. (I could have written an awk script to do this, but I thought what I was doing would be quicker for now.) I understand that performing the newuser exercise helps to identify the issue, but I suspect that it does not produce to root cause without substantially more work. The idea is to get the system to a reliable "good enough" state and that might mean that we do not dive all the way to true root cause.

Code:

Aug 19 18:16:37 <hostname> sudo[34708]: pam_unix(sudo:session): session opened for user root(uid=0) by <username>(uid=1000)
Aug 19 18:16:37 <hostname> sudo[34708]:    <username> : TTY=pts/4 ; PWD=/home/<username> ; USER=root ; COMMAND=/usr/bin/journalctl -b -0 -r
Aug 19 18:15:53 <hostname> plasmashell[34611]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 19 18:15:50 <hostname> plasmashell[34611]: file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PrinterItem.qml:22:5: Unable to assign [undefined] to bool
Aug 19 18:15:49 <hostname> plasmashell[34611]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_13_00.6.analog-stereo.monitor"
Aug 19 18:15:49 <hostname> plasmashell[34611]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Aug 19 18:15:49 <hostname> plasmashell[34611]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Aug 19 18:15:49 <hostname> plasmashell[34611]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 19 18:15:48 <hostname> dbus-daemon[3224]: [session uid=1000 pid=3224] Activating service name='org.kde.KSplash' requested by ':1.230' (uid=1000 pid=34611 comm="/usr/bin/plasmashell --no-respawn" label="plasmashell (enforce)")
Aug 19 18:15:48 <hostname> plasmashell[34611]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/main.qml:30:5: Unable to assign [undefined] to bool
Aug 19 18:15:48 <hostname> plasmashell[34611]: file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
Aug 19 18:15:48 <hostname> plasmashell[34611]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
Aug 19 18:15:48 <hostname> plasmashell[34611]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
Aug 19 18:15:48 <hostname> plasmashell[34611]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/main.qml:30:5: Unable to assign [undefined] to bool
Aug 19 18:15:48 <hostname> plasmashell[34611]: org.kde.plasma.kicker: Kicker.WindowSystem is deprecated and will be removed in Plasma 6. Use KWindowSystem/KX11Extras instead.
Aug 19 18:15:48 <hostname> plasmashell[34611]: org.kde.plasma.kicker: DragHelper is deprecated and will be removed in Plasma 6. Use Qt Quick Drag instead.
Aug 19 18:15:48 <hostname> dbus-daemon[3224]: apparmor="DENIED" operation="dbus_signal"  bus="session" path="/com/canonical/unity/launcherentry/366353504" interface="com.canonical.Unity.LauncherEntry" member="Update" mask="send" name="org.freedesktop.DBus" pid=4200 label="snap.chromium.chromium" peer_pid=34611 peer_label="plasmashell"
Aug 19 18:15:48 <hostname> plasmashell[34611]: libpng warning: iCCP: known incorrect sRGB profile
Aug 19 18:15:48 <hostname> plasmashell[34611]: kf.plasma.quick: Applet preload policy set to 1
Aug 19 18:15:48 <hostname> systemd[3201]: Started plasma-plasmashell.service - KDE Plasma Workspace.
Aug 19 18:15:48 <hostname> plasmashell[34611]: Checking screens: available: (QScreen(0x5cd028a14fd0, name="DP-3"), QScreen(0x5cd028a15010, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x5cd028a14fd0, name="DP-3"), QScreen(0x5cd028a15010, name="DP-1"))
Aug 19 18:15:47 <hostname> systemd[3201]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
Aug 19 18:15:47 <hostname> systemd[3201]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Aug 19 18:15:47 <hostname> kded5[3468]: "/var/crash/_usr_bin_plasmashell.1000.crash"
Aug 19 18:15:47 <hostname> systemd[3201]: plasma-plasmashell.service: Consumed 36.054s CPU time.
Aug 19 18:15:47 <hostname> systemd[3201]: plasma-plasmashell.service: Failed with result 'core-dump'.
Aug 19 18:15:47 <hostname> systemd[3201]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Aug 19 18:15:47 <hostname> systemd[1]: whoopsie.service: Deactivated successfully.
Aug 19 18:15:47 <hostname> whoopsie[34608]: [18:15:47] Using lock path: /var/lock/whoopsie/lock
Aug 19 18:15:47 <hostname> systemd[1]: Started whoopsie.service - crash report submission.
Aug 19 18:15:47 <hostname> CRON[34605]: pam_unix(cron:session): session closed for user root
Aug 19 18:15:47 <hostname> CRON[34606]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 19 18:15:47 <hostname> CRON[34605]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 19 18:15:46 <hostname> systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 19 18:15:43 <hostname> kded5[3468]: "/var/crash/_usr_bin_plasmashell.1000.crash"
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: PID 34581 terminated.
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: PID 34580 terminated.
Aug 19 18:15:41 <hostname> kded5[34580]: ERROR: whoopsie is not running
Aug 19 18:15:41 <hostname> kded5[34581]: ERROR: whoopsie is not running
Aug 19 18:15:41 <hostname> kded5[3468]: running "/usr/share/kubuntu-notification-helper/whoopsie-upload-all"
Aug 19 18:15:41 <hostname> kded5[3468]: "/var/crash/_usr_bin_plasmashell.1000.crash"
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: preparing to launch '/usr/share/kubuntu-notification-helper/whoopsie-upload-all'
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: Got EXEC_NEW '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' from launcher.
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: opened connection to :0
Aug 19 18:15:41 <hostname> kded5[34576]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: Launched KLauncher, pid = 34576, result = 0
Aug 19 18:15:41 <hostname> kded5[34575]: kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
Aug 19 18:15:41 <hostname> kded5[3468]: running "/usr/share/kubuntu-notification-helper/whoopsie-upload-all"
Aug 19 18:15:41 <hostname> kded5[3468]: "/var/crash"
Aug 19 18:15:41 <hostname> systemd[1]: whoopsie.service: Deactivated successfully.
Aug 19 18:15:41 <hostname> whoopsie[34559]: [18:15:41] Using lock path: /var/lock/whoopsie/lock
Aug 19 18:15:41 <hostname> systemd[1]: Started whoopsie.service - crash report submission.
Aug 19 18:15:40 <hostname> plasmashell[3521]: Re-raising signal for core dump handling.
Aug 19 18:15:40 <hostname> plasmashell[3521]: Unable to start Dr. Konqi
Aug 19 18:15:40 <hostname> plasmashell[3521]: QSocketNotifier: Invalid socket 32 and type 'Read', disabling...
Aug 19 18:15:40 <hostname> plasmashell[3521]: QSocketNotifier: Invalid socket 29 and type 'Read', disabling...
Aug 19 18:15:40 <hostname> plasmashell[3521]: QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
Aug 19 18:15:40 <hostname> plasmashell[3521]: QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
Aug 19 18:15:40 <hostname> plasmashell[3521]: KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Aug 19 18:15:40 <hostname> plasmashell[3521]: KCrash: Arguments: /usr/bin/plasmashell --no-respawn
Aug 19 18:15:40 <hostname> plasmashell[3521]: KCrash: Application Name = plasmashell path = /usr/bin pid = 3521
Aug 19 18:15:40 <hostname> plasmashell[3521]: KCrash: crashing... crashRecursionCounter = 2
Aug 19 18:15:40 <hostname> plasmashell[3521]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:278:9: QML Image: Cannot open: file:///tmp/.org.chromium.Chromium.bK2n7D
Aug 19 18:15:40 <hostname> plasmashell[3521]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:278:9: QML Image: Cannot open: file:///tmp/.org.chromium.Chromium.bK2n7D
Aug 19 18:15:39 <hostname> avahi-daemon[1910]: Registering new address record for 2603:6000:dd00:ff:6722:522:c349:48a1 on enp15s0.*.
Aug 19 18:15:38 <hostname> plasmashell[34512]: KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Aug 19 18:15:38 <hostname> kwin_x11[3469]: kwin_core: XCB error: 152 (BadDamage), sequence: 40765, resource id: 19608259, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Aug 19 18:15:38 <hostname> plasmashell[33876]: [33876:1:0819/181538.746127:ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:127] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:277): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/explicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:276): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:275): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:274): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:273): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:272): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:271): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:270): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:269): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> kernel: audit: type=1400 audit(1755645338.739:268): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=34512 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:38 <hostname> plasmashell[4200]: [4200:4200:0819/181538.706907:ERROR:content/browser/gpu/gpu_process_host.cc:957] GPU process exited unexpectedly: exit_code=8704
Aug 19 18:15:38 <hostname> plasmashell[7745]: [7745:6:0819/181538.704463:ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:327] GPU state invalid after WaitForGetOffsetInRange.
Aug 19 18:15:38 <hostname> plasmashell[22845]: [22845:22845:0819/181538.695759:ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.
Aug 19 18:15:38 <hostname> plasmashell[22845]: [22845:22845:0819/181538.695634:ERROR:gpu/command_buffer/service/shared_context_state.cc:1372] SharedContextState context lost via EXT_robustness. Reset status = GL_UNKNOWN_CONTEXT_RESET_KHR
Aug 19 18:15:38 <hostname> kwin_x11[3469]: kwin_core: XCB error: 3 (BadWindow), sequence: 40475, resource id: 20971564, major code: 129 (SHAPE), minor code: 6 (Input)
Aug 19 18:15:37 <hostname> dnsmasq[2394]: using nameserver 127.0.0.53#53
Aug 19 18:15:37 <hostname> dnsmasq[2394]: reading /etc/resolv.conf
Aug 19 18:15:37 <hostname> systemd-resolved[1559]: enp15s0: Bus client set search domain list to: search.charter.net
Aug 19 18:15:37 <hostname> systemd-resolved[1559]: enp15s0: Bus client set DNS server list to: 192.168.1.1, fe80::3a94:edff:fec8:200f
Aug 19 18:15:37 <hostname> avahi-daemon[1910]: Withdrawing address record for fe80::d77c:7351:3e75:22b9 on enp15s0.
Aug 19 18:15:37 <hostname> NetworkManager[2017]: <info>  [1755645337.7128] dhcp6 (enp15s0): state changed new lease
Aug 19 18:15:37 <hostname> avahi-daemon[1910]: Registering new address record for 2603:6000:dd00:ff:ea79:156:42d6:b4a6 on enp15s0.*.
Aug 19 18:15:37 <hostname> avahi-daemon[1910]: Joining mDNS multicast group on interface enp15s0.IPv6 with address 2603:6000:dd00:ff:ea79:156:42d6:b4a6.
Aug 19 18:15:37 <hostname> avahi-daemon[1910]: Leaving mDNS multicast group on interface enp15s0.IPv6 with address fe80::d77c:7351:3e75:22b9.
Aug 19 18:15:37 <hostname> NetworkManager[2017]: <info>  [1755645337.7121] policy: set 'Wired connection 1' (enp15s0) as default for IPv6 routing and DNS
Aug 19 18:15:37 <hostname> NetworkManager[2017]: <info>  [1755645337.7117] dhcp6 (enp15s0): activation: beginning transaction (timeout in 45 seconds)
Aug 19 18:15:37 <hostname> ModemManager[2097]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0b.0/0000:10:00.0': not supported by any plugin
Aug 19 18:15:37 <hostname> ModemManager[2097]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0a.0/0000:0f:00.0': not supported by any plugin
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4934] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4933] device (enp15s0): Activation: successful, device activated.
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4932] manager: NetworkManager state is now CONNECTED_SITE
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4931] device (enp15s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4930] device (enp15s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> dbus-daemon[1913]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 19 18:15:36 <hostname> systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4819] device (enp15s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> systemd-resolved[1559]: enp15s0: Bus client set DNS server list to: 192.168.1.1
Aug 19 18:15:36 <hostname> systemd-resolved[1559]: enp15s0: Bus client set default route setting: yes
Aug 19 18:15:36 <hostname> dbus-daemon[1913]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=2017 comm="/usr/sbin/NetworkManager --no-daemon" label="unconfined")
Aug 19 18:15:36 <hostname> avahi-daemon[1910]: Registering new address record for 192.168.1.18 on enp15s0.IPv4.
Aug 19 18:15:36 <hostname> avahi-daemon[1910]: New relevant interface enp15s0.IPv4 for mDNS.
Aug 19 18:15:36 <hostname> avahi-daemon[1910]: Joining mDNS multicast group on interface enp15s0.IPv4 with address 192.168.1.18.
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4690] policy: set 'Wired connection 1' (enp15s0) as default for IPv4 routing and DNS
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.4688] dhcp4 (enp15s0): state changed new lease, address=192.168.1.18
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.3232] dhcp4 (enp15s0): state changed new lease, address=192.168.1.18, acd pending
Aug 19 18:15:36 <hostname> systemd[1]: systemd-rfkill.service: Deactivated successfully.
Aug 19 18:15:36 <hostname> avahi-daemon[1910]: Registering new address record for fe80::d77c:7351:3e75:22b9 on enp15s0.*.
Aug 19 18:15:36 <hostname> avahi-daemon[1910]: New relevant interface enp15s0.IPv6 for mDNS.
Aug 19 18:15:36 <hostname> avahi-daemon[1910]: Joining mDNS multicast group on interface enp15s0.IPv6 with address fe80::d77c:7351:3e75:22b9.
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2636] dhcp4 (enp15s0): activation: beginning transaction (timeout in 45 seconds)
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2634] device (enp15s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2632] device (enp15s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2632] manager: NetworkManager state is now CONNECTING
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2630] device (enp15s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2630] device (enp15s0): Activation: starting connection 'Wired connection 1' (fc12c8ec-dabe-3991-9f9f-0bd3d71e1578)
Aug 19 18:15:36 <hostname> kernel: r8169 0000:0f:00.0 enp15s0: Link is Up - 1Gbps/Full - flow control rx/tx
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2627] policy: auto-activating connection 'Wired connection 1' (fc12c8ec-dabe-3991-9f9f-0bd3d71e1578)
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2625] device (enp15s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 19 18:15:36 <hostname> NetworkManager[2017]: <info>  [1755645336.2623] device (enp15s0): carrier: link connected
Aug 19 18:15:34 <hostname> systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 19 18:15:33 <hostname> plasmashell[3521]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_13_00.6.analog-stereo"
Aug 19 18:15:33 <hostname> plasmashell[3521]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_13_00.6.analog-stereo.monitor"
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2511] device (p2p-dev-wlp16s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2510] device (wlp16s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2509] device (p2p-dev-wlp16s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2509] manager: (p2p-dev-wlp16s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/12)
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2508] Wi-Fi P2P device controlled by interface wlp16s0 created
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2505] device (p2p-dev-wlp16s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2505] device (wlp16s0): supplicant interface state: internal-starting -> disconnected
Aug 19 18:15:33 <hostname> plasmashell[3521]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5e3ea4bedd90) QQmlContext(0x5e3ea345d070) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2329] device (60:81:10:DC:EB:62): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2327] manager: NetworkManager state is now CONNECTED_LOCAL
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2326] device (60:81:10:DC:EB:62): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2325] device (p2p-dev-wlp16s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 19 18:15:33 <hostname> kernel: r8169 0000:0f:00.0 enp15s0: Link is Down
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.2285] device (wlp16s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 19 18:15:33 <hostname> plasmashell[3521]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 19 18:15:33 <hostname> systemd[1]: Finished grub-initrd-fallback.service - GRUB failed boot detection.
Aug 19 18:15:33 <hostname> systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Aug 19 18:15:33 <hostname> systemd[1]: Starting grub-initrd-fallback.service - GRUB failed boot detection...
Aug 19 18:15:33 <hostname> systemd[1]: Finished grub-common.service - Record successful boot for GRUB.
Aug 19 18:15:33 <hostname> systemd[1]: grub-common.service: Deactivated successfully.
Aug 19 18:15:33 <hostname> systemd[1]: Finished nvidia-resume.service - NVIDIA system resume actions.
Aug 19 18:15:33 <hostname> systemd[1]: nvidia-resume.service: Deactivated successfully.
Aug 19 18:15:33 <hostname> logger[34466]: <13>Aug 19 18:15:33 suspend: nvidia-resume.service
Aug 19 18:15:33 <hostname> suspend[34466]: nvidia-resume.service
Aug 19 18:15:33 <hostname> systemd[1]: Stopped target suspend.target - Suspend.
Aug 19 18:15:33 <hostname> systemd[1]: Starting nvidia-resume.service - NVIDIA system resume actions...
Aug 19 18:15:33 <hostname> systemd[1]: Starting grub-common.service - Record successful boot for GRUB...
Aug 19 18:15:33 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-f00:00: attached PHY driver (mii_bus:phy_addr=r8169-0-f00:00, irq=MAC)
Aug 19 18:15:33 <hostname> kdeconnectd[3686]: Error sending UDP packet: QAbstractSocket::NetworkError
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.0493] device (enp15s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 19 18:15:33 <hostname> NetworkManager[2017]: <info>  [1755645333.0492] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Aug 19 18:15:33 <hostname> ModemManager[2097]: <msg> [sleep-monitor-systemd] system is resuming
Aug 19 18:15:33 <hostname> systemd-logind[1948]: Operation 'suspend' finished.
Aug 19 18:15:33 <hostname> systemd[1]: Reached target suspend.target - Suspend.
Aug 19 18:15:33 <hostname> systemd[1]: Stopped target sleep.target - Sleep.
Aug 19 18:15:33 <hostname> systemd[1]: systemd-suspend.service: Consumed 1.354s CPU time.
Aug 19 18:15:33 <hostname> systemd[1]: Finished systemd-suspend.service - System Suspend.
Aug 19 18:15:33 <hostname> systemd[1]: systemd-suspend.service: Deactivated successfully.
Aug 19 18:15:33 <hostname> systemd-sleep[34296]:  APM_level        = 254
Aug 19 18:15:33 <hostname> systemd-sleep[34296]:  setting Advanced Power Management level to 0xfe (254)
Aug 19 18:15:33 <hostname> systemd-sleep[34296]: /dev/sda:
Aug 19 18:15:33 <hostname> kernel: ata3.00: configured for UDMA/133
Aug 19 18:15:33 <hostname> kernel: sd 2:0:0:0: [sda] Starting disk
Aug 19 18:15:32 <hostname> kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 19 18:15:32 <hostname> kded5[34413]: kcm_touchpad: Using X11 backend
Aug 19 18:15:32 <hostname> kded5[34413]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Aug 19 18:15:32 <hostname> kded5[34413]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Aug 19 18:15:32 <hostname> ksmserver[34033]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml:82:9: QML Image: Cannot open: file:///tmp/.org.chromium.Chromium.bK2n7D
Aug 19 18:15:32 <hostname> kwin_x11[3469]: DesktopGridConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: KscreenConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: OverviewConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: SlideConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: SlidingPopupsConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: WindowViewConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: ZoomConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: BlurConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: WobblyWindowsConfig::instance called after the first use - ignoring
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Virtual Machine:                        no
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Texture NPOT support:                   yes
Aug 19 18:15:32 <hostname> kwin_x11[3469]: GLSL shaders:                           yes
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Requires strict binding:                no
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Linux kernel version:                   6.14
Aug 19 18:15:32 <hostname> kwin_x11[3469]: X server version:                       1.21.1
Aug 19 18:15:32 <hostname> kwin_x11[3469]: GLSL version:                           1.40
Aug 19 18:15:32 <hostname> kwin_x11[3469]: OpenGL version:                         3.1
Aug 19 18:15:32 <hostname> kwin_x11[3469]: GPU class:                              Unknown
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Driver version:                         575.64.3
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Driver:                                 NVIDIA
Aug 19 18:15:32 <hostname> kwin_x11[3469]: OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Aug 19 18:15:32 <hostname> kwin_x11[3469]: OpenGL version string:                  3.1.0 NVIDIA 575.64.03
Aug 19 18:15:32 <hostname> kwin_x11[3469]: OpenGL renderer string:                 NVIDIA GeForce RTX 5070/PCIe/SSE2
Aug 19 18:15:32 <hostname> kwin_x11[3469]: OpenGL vendor string:                   NVIDIA Corporation
Aug 19 18:15:32 <hostname> kwin_x11[3469]: Xlib:  extension "NV-GLX" missing on display ":0".
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/opus_05
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSink/opus_05
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/faststream_duplex
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/faststream
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/sbc_xq
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSink/sbc_xq
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/sbc
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSink/sbc
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/aptx
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSink/aptx
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/aptx_hd
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSink/aptx_hd
Aug 19 18:15:31 <hostname> bluetoothd[1911]: Endpoint registered: sender=:1.173 path=/MediaEndpoint/A2DPSource/ldac
Aug 19 18:15:31 <hostname> systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Aug 19 18:15:31 <hostname> systemd[1]: sysstat-collect.service: Deactivated successfully.
Aug 19 18:15:31 <hostname> systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Aug 19 18:15:30 <hostname> NetworkManager[2017]: <info>  [1755645330.8902] manager: (60:81:10:DC:EB:62): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/11)
Aug 19 18:15:30 <hostname> kernel: Bluetooth: MGMT ver 1.23
Aug 19 18:15:30 <hostname> bluetoothd[1911]: sap-server: Operation not permitted (1)
Aug 19 18:15:30 <hostname> bluetoothd[1911]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 19 18:15:30 <hostname> bluetoothd[1911]: Battery Provider Manager created
Aug 19 18:15:30 <hostname> systemd[1]: Finished man-db.service - Daily man-db regeneration.
Aug 19 18:15:30 <hostname> systemd[1]: man-db.service: Deactivated successfully.
Aug 19 18:15:30 <hostname> kernel: audit: type=1400 audit(1755645330.466:267): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=34236 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 19 18:15:30 <hostname> kernel: kauditd_printk_skb: 7 callbacks suppressed
Aug 19 18:15:30 <hostname> systemd[3201]: Reached target bluetooth.target - Bluetooth.
Aug 19 18:15:30 <hostname> systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Aug 19 18:15:30 <hostname> systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Aug 19 18:15:30 <hostname> systemd[1]: Starting man-db.service - Daily man-db regeneration...
Aug 19 18:15:30 <hostname> kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Aug 19 18:15:30 <hostname> systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Aug 19 18:15:30 <hostname> systemd[3201]: Stopped target bluetooth.target - Bluetooth.
Aug 19 18:15:30 <hostname> systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
Aug 19 18:15:30 <hostname> systemd[3201]: Started snap.firmware-updater.firmware-notifier.service - Service for snap application firmware-updater.firmware-notifier.
Aug 19 18:15:30 <hostname> systemd-sleep[34093]: System returned from sleep operation 'suspend'.
Aug 19 18:15:30 <hostname> bluetoothd[1911]: Battery Provider Manager destroyed
Aug 19 18:15:30 <hostname> systemd-resolved[1559]: Clock change detected. Flushing caches.
Aug 19 18:15:30 <hostname> kernel: PM: suspend exit
Aug 19 18:15:30 <hostname> kernel: random: crng reseeded on system resumption
Aug 19 18:15:30 <hostname> kernel: Restarting tasks ... done.
Aug 19 18:15:30 <hostname> kernel: OOM killer enabled.
Aug 19 18:15:30 <hostname> kernel: usb 1-6: reset full-speed USB device number 2 using xhci_hcd
Aug 19 18:15:30 <hostname> kernel: usb 1-6: WARN: invalid context state for evaluate context command.
Aug 19 18:15:30 <hostname> kernel: firewire_core 0000:08:00.0: rediscovered device fw0
Aug 19 18:15:30 <hostname> kernel: usb 1-12: reset full-speed USB device number 3 using xhci_hcd
Aug 19 18:15:30 <hostname> kernel: ata1: SATA link down (SStatus 0 SControl 300)
Aug 19 18:15:30 <hostname> kernel: ata2: SATA link down (SStatus 0 SControl 300)
Aug 19 18:15:30 <hostname> kernel: ata4: SATA link down (SStatus 0 SControl 300)
Aug 19 18:15:30 <hostname> kernel: usb 1-12: WARN: invalid context state for evaluate context command.
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: [drm] Cannot find any crtc or sizes
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: [drm] Cannot find any crtc or sizes
Aug 19 18:15:30 <hostname> kernel: [drm] DMUB hardware initialized: version=0x05000F00
Aug 19 18:15:30 <hostname> kernel: [drm] kiq ring mec 2 pipe 1 q 0
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: SMU is resumed successfully!
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: SMU is resuming...
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: RAP: optional rap ta ucode is not available
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: RAS: optional ras ta ucode is not available
Aug 19 18:15:30 <hostname> kernel: nvme nvme1: 24/0/0 default/read/poll queues
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: reserve 0xa00000 from 0xf41e000000 for PSP TMR
Aug 19 18:15:30 <hostname> kernel: ath12k_pci 0000:10:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
Aug 19 18:15:30 <hostname> kernel: ath12k_pci 0000:10:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
Aug 19 18:15:30 <hostname> kernel: nvme nvme0: 24/0/0 default/read/poll queues
Aug 19 18:15:30 <hostname> kernel: usb usb2: root hub lost power or was reset
Aug 19 18:15:30 <hostname> kernel: usb usb1: root hub lost power or was reset
Aug 19 18:15:30 <hostname> kernel: xhci_hcd 0000:11:00.0: xHC error in resume, USBSTS 0x401, Reinit
Aug 19 18:15:30 <hostname> kernel: amdgpu 0000:13:00.0: amdgpu: PSP is resuming...
Aug 19 18:15:30 <hostname> kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
Aug 19 18:15:30 <hostname> kernel: mhi mhi0: Wait for device to enter SBL or Mission mode
Aug 19 18:15:30 <hostname> kernel: mhi mhi0: Power on setup success
Aug 19 18:15:30 <hostname> kernel: mhi mhi0: Requested to power ON
Aug 19 18:15:30 <hostname> kernel: nvidia 0000:01:00.0: Enabling HDA controller
Aug 19 18:15:30 <hostname> kernel: ACPI: PM: Waking up from system sleep state S3
Aug 19 18:15:30 <hostname> kernel: CPU23 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#23, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 23 APIC 0x1b
Aug 19 18:15:30 <hostname> kernel: CPU22 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#22, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 22 APIC 0x19
Aug 19 18:15:30 <hostname> kernel: CPU21 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#21, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 21 APIC 0x17
Aug 19 18:15:30 <hostname> kernel: CPU20 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#20, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 20 APIC 0x15
Aug 19 18:15:30 <hostname> kernel: CPU19 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#19, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 19 APIC 0x13
Aug 19 18:15:30 <hostname> kernel: CPU18 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#18, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 18 APIC 0x11
Aug 19 18:15:30 <hostname> kernel: CPU17 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#17, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 17 APIC 0xb
Aug 19 18:15:30 <hostname> kernel: CPU16 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#16, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 16 APIC 0x9
Aug 19 18:15:30 <hostname> kernel: CPU15 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#15, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 15 APIC 0x7
Aug 19 18:15:30 <hostname> kernel: CPU14 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#14, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 14 APIC 0x5
Aug 19 18:15:30 <hostname> kernel: CPU13 is up
Aug 19 18:15:30 <hostname> kernel: Spurious APIC interrupt (vector 0xFF) on CPU#13, should never happen.
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 13 APIC 0x3
Aug 19 18:15:30 <hostname> kernel: CPU12 is up
Aug 19 18:15:30 <hostname> kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 12 APIC 0x1
Aug 19 18:15:30 <hostname> kernel: CPU11 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 11 APIC 0x1a
Aug 19 18:15:30 <hostname> kernel: CPU10 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 10 APIC 0x18
Aug 19 18:15:30 <hostname> kernel: CPU9 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 9 APIC 0x16
Aug 19 18:15:30 <hostname> kernel: CPU8 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 8 APIC 0x14
Aug 19 18:15:30 <hostname> kernel: CPU7 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 7 APIC 0x12
Aug 19 18:15:30 <hostname> kernel: CPU6 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 6 APIC 0x10
Aug 19 18:15:30 <hostname> kernel: CPU5 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Aug 19 18:15:30 <hostname> kernel: CPU4 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Aug 19 18:15:30 <hostname> kernel: CPU3 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Aug 19 18:15:30 <hostname> kernel: CPU2 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Aug 19 18:15:30 <hostname> kernel: CPU1 is up
Aug 19 18:15:30 <hostname> kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Aug 19 18:15:30 <hostname> kernel: Enabling non-boot CPUs ...
Aug 19 18:15:30 <hostname> kernel: LVT offset 0 assigned for vector 0x400
Aug 19 18:15:30 <hostname> kernel: AMD-Vi: Virtual APIC enabled
Aug 19 18:15:30 <hostname> kernel: AMD-Vi: Virtual APIC enabled
Aug 19 18:15:30 <hostname> kernel: ACPI: PM: Restoring platform NVS memory
Aug 19 18:15:30 <hostname> kernel: ACPI: PM: Low-level resume complete
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 1 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 2 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 3 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 4 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 5 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 6 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 7 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 8 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 9 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 10 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 11 is now offline
Aug 19 18:15:30 <hostname> kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 12 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 13 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 14 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 15 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 16 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 17 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 18 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 19 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 20 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 21 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 22 is now offline
Aug 19 18:15:30 <hostname> kernel: smpboot: CPU 23 is now offline
Aug 19 18:15:30 <hostname> kernel: Disabling non-boot CPUs ...
Aug 19 18:15:30 <hostname> kernel: ACPI: PM: Saving platform NVS memory
Aug 19 18:15:30 <hostname> kernel: ACPI: PM: Preparing to enter system sleep state S3
Aug 19 18:15:30 <hostname> kernel: ata3.00: Entering standby power mode
Aug 19 18:15:30 <hostname> kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
Aug 19 18:15:30 <hostname> kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Aug 19 18:15:30 <hostname> kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Aug 19 18:15:30 <hostname> kernel: Freezing remaining freezable tasks
Aug 19 18:15:30 <hostname> kernel: OOM killer disabled.
Aug 19 18:15:30 <hostname> kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Aug 19 18:15:30 <hostname> kernel: Freezing user space processes

**TheSupremeVizier** · Aug 19, 2025, 07:10 PM

Ahah! I just leaned something. My older desktop user account is running the "Sweet" theme. I just went to System Settings -> Global Theme on the new account and "Sweet" wasn't offered there, so I clicked on "Get New Global Themes" and the following statement was displayed along with a search window titled "Download New Global Themes". The statement: "The content available here has been uploaded by users like you, and has not been reviewed by your distributor for functionality or stability." Ooooooooh. One more thing to check.

Furthermore, "Sweet" was NOT one of the themes currently offered inside "Download New Global Themes". When searching for "sweet", I found "Utterly Sweet Solid Global for Plasma 5", "Utterly Sweet Global for Plasma 5", "Sweet Ambar Blue" and "Sweet Mars KDE". The apparently simpler "Sweet" isn't even offered now.

**Snowhog** · Aug 19, 2025, 07:32 PM

Then, on your original users account, switch to one of the default Themes and see if your problems go away.

**TheSupremeVizier** · Aug 23, 2025, 04:55 PM

Edited to add: What follows has just been voided. I am removing the [RESOLVED] prepend. The plasma display on my olde account, running the "Breeze Dark" theme, has just crashed. Grrrrr.... What to do...what to do...

Previous post:

I am prepending the topic title with [RESOLVED], but I also want to report my findings and my opinion here.

I have an olde account which I have changed the Global Theme from "Sweet" to "Breeze Dark". I have a new (not to be confused with "gnu" ;-)) account which I have created using all the desktop icons/widgets found in the olde account and changed the Global Theme from whatever the default was to a theme very similar to "Sweet", but the allegedly problematic "Sweet" theme was not available. The similar to "Sweet" theme I used is called "Utterly Sweet Solid Global for Plasma 5". Both the olde and new accounts are now behaving nicely since I have NOT witnessed any plasma crashes since 19 August, and I have exercised the hell out of both accounts.

So what is the root cause of the issue? I can't state that it was entirely caused by the "Sweet" theme, but what I can say is that I've been using the "Sweet" theme for a very long time in the olde account, with the Kubuntu LTS that preceded 24.04 and earlier, and did not see any plasma crashes until 24.04 LTS.

What I suspect has been happening...but cannot prove at this time...is that my olde account is so old that it contains ancient KDE configuration files from Sabayon (which was Gentoo-based) and much earlier (yes, even downloaded through Knoppix!), and that this detritus might have had something to do with it. Either that, or the "Sweet" theme is no longer available for a good reason. (It would be really nice to know why "Sweet" is no longer available.) If I knew more about useless (or zombie) portions of configuration files...or even complete zombie configuration files...I'd clean up this olde account a bit. The only other thing is to tar up everything in the olde account, create a newer account, and somehow avoid untarring the potentially problematic configuration files into the newer account.

So, a very great thank you to deadsplash, skyfishgoo and Snowhog for your generous assistance!

**TheSupremeVizier** · Aug 23, 2025, 07:01 PM

I put my system into "sleep" mode at system time 18:08:09.
I returned the system to a running state at system time 19:14:24.
Here is the what I believe to be the pertinent output from "sudo journalctl -b-0 -r":

Code:

Aug 23 19:31:17 <hostname> systemd[3173]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
Aug 23 19:31:17 <hostname> systemd[3173]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Aug 23 19:31:17 <hostname> systemd[3173]: plasma-plasmashell.service: Consumed 12.444s CPU time.
Aug 23 19:31:17 <hostname> systemd[3173]: plasma-plasmashell.service: Failed with result 'core-dump'.
Aug 23 19:31:17 <hostname> systemd[3173]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Aug 23 19:31:16 <hostname> kded5[3438]: Service  ":1.144" unregistered
Aug 23 19:31:16 <hostname> plasmashell[3487]: Re-raising signal for core dump handling.
Aug 23 19:31:16 <hostname> plasmashell[3487]: Unable to start Dr. Konqi
Aug 23 19:31:16 <hostname> plasmashell[3487]: QSocketNotifier: Invalid socket 32 and type 'Read', disabling...
Aug 23 19:31:16 <hostname> plasmashell[3487]: QSocketNotifier: Invalid socket 29 and type 'Read', disabling...
Aug 23 19:31:16 <hostname> plasmashell[3487]: QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
Aug 23 19:31:16 <hostname> plasmashell[3487]: QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
Aug 23 19:31:16 <hostname> kded5[3438]: Registering ":1.144/StatusNotifierItem" to system tray
Aug 23 19:31:15 <hostname> plasmashell[3487]: KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Aug 23 19:31:15 <hostname> plasmashell[3487]: KCrash: Arguments: /usr/bin/plasmashell --no-respawn
Aug 23 19:31:15 <hostname> plasmashell[3487]: KCrash: Application Name = plasmashell path = /usr/bin pid = 3487
Aug 23 19:31:15 <hostname> plasmashell[3487]: KCrash: crashing... crashRecursionCounter = 2
Aug 23 19:30:40 <hostname> systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Aug 23 19:30:40 <hostname> systemd[1]: sysstat-collect.service: Deactivated successfully.
Aug 23 19:30:40 <hostname> systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
Aug 23 19:30:02 <hostname> CRON[13322]: pam_unix(cron:session): session closed for user root
Aug 23 19:30:02 <hostname> CRON[13323]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Aug 23 19:30:02 <hostname> CRON[13322]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 23 19:29:32 <hostname> smartd[1931]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 29 to 27
Aug 23 19:29:32 <hostname> smartd[1931]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 71 to 73
Aug 23 19:29:19 <hostname> Tor[2804]: Your system clock just jumped 7571 seconds forward; assuming established circuits no longer work.
Aug 23 19:29:13 <hostname> cups.cups-browsed[2585]: + sleep 3600
Aug 23 19:29:13 <hostname> cups.cups-browsed[2585]: + true
Aug 23 19:25:01 <hostname> CRON[13014]: pam_unix(cron:session): session closed for user root
Aug 23 19:25:01 <hostname> CRON[13015]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 23 19:25:01 <hostname> CRON[13014]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Aug 23 19:23:48 <hostname> systemd[1]: fwupd.service: Deactivated successfully.
Aug 23 19:20:10 <hostname> systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Aug 23 19:20:10 <hostname> systemd[1]: sysstat-collect.service: Deactivated successfully.
Aug 23 19:20:10 <hostname> systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
Aug 23 19:19:35 <hostname> systemd[1]: packagekit.service: Consumed 1.981s CPU time.
Aug 23 19:19:35 <hostname> systemd[1]: packagekit.service: Deactivated successfully.
Aug 23 19:19:35 <hostname> PackageKit[9357]: daemon quit
Aug 23 19:18:47 <hostname> systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd.
Aug 23 19:18:47 <hostname> systemd[1]: fwupd-refresh.service: Deactivated successfully.
Aug 23 19:18:47 <hostname> systemd[1]: Started fwupd.service - Firmware update daemon.
Aug 23 19:18:47 <hostname> dbus-daemon[1901]: [system] Successfully activated service 'org.freedesktop.fwupd'
Aug 23 19:18:47 <hostname> fwupd[12162]: 00:18:47.963 FuMain               fwupd 1.9.30 ready for requests (locale en_US.UTF-8)
Aug 23 19:18:47 <hostname> systemd[1]: Starting fwupd.service - Firmware update daemon...
Aug 23 19:18:47 <hostname> dbus-daemon[1901]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.146' (uid=990 pid=12156 comm="/usr/bin/fwupdmgr refresh" label="unconfined")
Aug 23 19:18:47 <hostname> systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd...
Aug 23 19:18:09 <hostname> plasmashell[11700]: Fontconfig error: Cannot load default config file
Aug 23 19:18:03 <hostname> systemd[1]: fwupd.service: Deactivated successfully.
Aug 23 19:17:36 <hostname> plasmashell[10558]: [10558:10558:0823/191736.859704: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.
Aug 23 19:17:01 <hostname> CRON[10924]: pam_unix(cron:session): session closed for user root
Aug 23 19:17:01 <hostname> CRON[10925]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Aug 23 19:17:01 <hostname> CRON[10924]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)

/dev/sda is not mounted.

Any ideas?

**TheSupremeVizier** · 2025-08-29T17:22:38

Can someone provide me a link that describes how I might use apport to debug this issue?
I just had another plasma crash occur.
I have a /var/crash/_usr_bin_plasmashell.1000.crash file I could use to debug.
I will also need to understand what other dependencies for apport are required and how to get them; something like a pointer/link to source code, maybe?

**Cincinnatus** · 2025-08-30T11:03:03

Just a suggestion, but with all this time you're spending on this issue, I would honestly just backup my files and do a fresh install

Announcement

Plasma Crashes

Plasma Crashes

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Users Viewing This Topic