Bug 494694

Summary:	Bluetooth notifier from systray shows an error after Plasma started.
Product:	[KDE Neon] neon	Reporter:	Piotr Mierzwinski <piotr.mierzwinski>
Component:	Packages Testing Edition	Assignee:	Neon Bugs <neon-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	jr, kde, nate, neon-bugs, nicolas.fella, piotr.mierzwinski
Priority:	NOR	Keywords:	qt6, wayland-only
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	bluetooth error

Description Piotr Mierzwinski 2024-10-13 19:53:33 UTC

SUMMARY
Today I made update (Neon Unstable) and after I restarted my PC and logged in to Plasma I clicked into Bluetooth icon placed in systray and found error coming from Bluetooth like below:

"file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/main.qml:87:14: Cannot assign to non-existent property "onSecondaryActivated"



STEPS TO REPRODUCE
1. Login to Plasma
2. Click in to Bluetooth icon placed in systray
3. 

OBSERVED RESULT
Appears error like:
"file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/main.qml:87:14: Cannot assign to non-existent property "onSecondaryActivated"

EXPECTED RESULT
should not appears any error

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.2.80
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Neon Unstable Edition
System updated today (2024/10/13) evening.

Comment 1 Piotr Mierzwinski 2024-10-17 21:42:00 UTC

Created attachment 174967 [details]
bluetooth error

Comment 2 Piotr Mierzwinski 2024-10-23 22:10:25 UTC

Passed 10 days, no any response.
I'm not sure if this error happens only for me or this is normal because I use "Neon Unstable Edition", or this is bug only present in my system instance  :/

Comment 3 Nicolas Fella 2024-10-25 15:10:17 UTC

This looks like Neon is in an inconsistent state. Does it still happen with latest updates?

Comment 4 Piotr Mierzwinski 2024-11-03 01:13:12 UTC

(In reply to Nicolas Fella from comment #3)
> This looks like Neon is in an inconsistent state. Does it still happen with
> latest updates?

Thank you for your reply.
Unfortunately today issue still persists. 
BTW.
This is another time that issue I reported was caused by problem in distribution. I'm not sure if Neon is credible system to test and reporting bugs. I think alternative is build from source :/.

Comment 5 Nate Graham 2024-11-05 21:43:56 UTC

Yes, this is a Neon-specific packaging bug. Moving there.

Comment 6 Piotr Mierzwinski 2024-11-06 23:51:18 UTC

(In reply to Nate Graham from comment #5)
> Yes, this is a Neon-specific packaging bug. Moving there.
Today I found that issue disappeared.