Bug 443717

Summary:	[workspace] Saving a new workspace doesn't appear in "Workspaces list", but in 'Windows layout" list.
Product:	[Applications] krita	Reporter:	David REVOY <info>
Component:	Resource Management	Assignee:	Tiar <tamtamy.tymona>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dragonheart2497, tamtamy.tymona, tomtomtomreportingin
Priority:	NOR	Keywords:	regression
Version First Reported In:	5.0.0-beta2
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David REVOY 2021-10-14 14:59:23 UTC

Hi,
Something I noticed today while trying to save a new workspace, after clicking the "Save" button; it doesn't appear in the "Workspaces" list, but in "Windows layout" list.

STEPS TO REPRODUCE
1. Click the top-right icon of the toolbar (Tooltip: Choose workspaces)
2. Under the list "Workspaces", Insert a name then press Save button. 

OBSERVED RESULT
The name inserted appears on the list under named "Windows layout". Only closing and relaunching Krita will make the workspace to join its real list.

EXPECTED RESULT
After clicking on "Save" the workspace appears among the list of "Workspaces".

SOFTWARE/OS VERSIONS
Kubuntu 20.04 LTS

Comment 1 tomtomtomreportingin 2021-10-14 16:53:16 UTC

Yep, noticed this a couple days ago but haven't gotten around to reporting it. Does NOT happen in Krita 5 beta 1, so it is a regression as of beta 2. Also occurs in 5.1.0-prealpha (git 6a41c43).

Comment 2 tomtomtomreportingin 2021-10-14 23:15:12 UTC

Additional problem that might be related: Workspaces that share names with deleted workspaces aren't shown in either list until Krita is restarted.

Comment 3 Tiar 2021-10-21 14:48:59 UTC

I can't reproduce on current master (7032c652ff). I've found some issues to fix (and fixed them) in the workspace chooser but even after I came back to master, the bug was not there. Can you please reconfirm?

(I can reproduce it in beta2 appimage, btw, but I cannot in the latest stable (25c11c1f42) or master (7032c652ff)). I guess maybe it was resolved in the meantime?

Comment 4 Bug Janitor Service 2021-11-05 04:36:00 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 5 Bug Janitor Service 2021-11-20 04:38:42 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!

Comment 6 David REVOY 2021-11-20 16:20:53 UTC

Thank you Bug Janitor for the reminder, good bot.

Good news: I confirm this bug doesn't affect  current 5.0beta/Krita Plus, I just tested.

Comment 7 Tiar 2021-11-30 00:36:43 UTC

*** Bug 446261 has been marked as a duplicate of this bug. ***