Bug 383793

Summary:	[broken configuration from corona] - applets with same id in the configuration file
Product:	[Frameworks and Libraries] libplasma	Reporter:	Michail Vourlakos <mvourlakos>
Component:	libplasma	Assignee:	Marco Martin <notmart>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	5.37.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Michail Vourlakos 2017-08-21 14:46:25 UTC

In Latte 0.7 we have added a check for the config files in order to check that the applets have unique ids. This was done because we wanted to be sure that the config files are clean at all cases and they do not create crashes.

There are some users informing us, that this warning that shouldnt appear if everything was ok, that some of their layouts are broken. We tracked it down in the following situation e.g.:

- The user has a systray that contains an applet with id:303 this is the maximum applet id and in that case it is assigned to :org.kde.plasma.mediacontroller

- The user adds a new applet and that new applet isnt at the systray, that new applet even though it shouldnt has also id:303


this case we consider it broken because different applets with same ids they can create instability and crashes. Isnt that the case?

Comment 1 Justin Zobel 2022-11-08 06:49:58 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 2 Bug Janitor Service 2022-11-23 05:14:57 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2022-12-08 05:14:31 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!