Bug 500508

Summary: Nullpointer exceptions: plasma-desktop-6.3.0/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:79: TypeError: Cannot read property 'status' of null
Product: [Plasma] plasmashell Reporter: Robert <elles.robert>
Component: Task Manager and Icons-Only Task Manager widgetsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: cwo.kde, nate, qydwhotmail
Priority: NOR Keywords: regression
Version First Reported In: 6.3.0   
Target Milestone: 1.0   
Platform: NixOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 6.3.1
Sentry Crash Report:

Description Robert 2025-02-21 07:52:04 UTC 
Hello,

In the plasmashell log I see a lot of Nullpointer error messages:

plasma-desktop-6.3.0/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:79: TypeError: Cannot read property 'status' of null

So in line 79 of the file Task.qml of plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui the code tries to read a 'status' property of something that is null.

Looking in this file I see line 79 is the following:
active: !inPopup && !tasksRoot.groupDialog && contextMenu.status !== PlasmaExtras.Menu.Open

It is trying to read status from contextMenu. So contextMenu musst be null.

I think in line 79 one there should be an extra null check before the 'status' property is accessed.
Comment 1 Nate Graham 2025-02-21 21:51:48 UTC 
Introduced by me in https://invent.kde.org/plasma/plasma-desktop/-/commit/3b6d394c0f3336b6ab81a3dc0d770a4c08a0ed4b, and already fixed by Christoph Wolk in https://invent.kde.org/plasma/plasma-desktop/-/commit/f463cdfcfc2cc474b695b5629450dd96a4170039 for Plasma 6.4.

Until then, it's harmless and you can ignore it, but I'll look into backporting it anyway.
Comment 2 cwo 2025-02-22 00:47:43 UTC 
(In reply to Nate Graham from comment #1)
> Until then, it's harmless and you can ignore it, but I'll look into
> backporting it anyway.

You already did in https://invent.kde.org/plasma/plasma-desktop/-/commit/0ed639e4f99ecfb4e3f46512f205f123ba71b244; it barely missed the 6.3.0 window, so already fixed in 6.3.1.

*** This bug has been marked as a duplicate of bug 500227 ***
Comment 3 Nate Graham 2025-02-22 01:25:22 UTC 
So I did!