| Summary: | Unable to remember workspace last used on program exit | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | lozmacdesigns |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | ghevan, halla |
| Priority: | NOR | ||
| Version First Reported In: | 4.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-1143-0.html
attachment-1472-0.html attachment-1863-0.html attachment-2235-0.html CC47A1509D314FEC93E6AB19E4D9482F.png |
||
|
Description
lozmacdesigns
2019-07-05 19:00:16 UTC
Hi! Krita does remember workspaces, at least on the kritas Im using. So as an idea could you reset your configuration options and see if the problem persists? (how to reset config: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration). It is possible the configuration got corrupted somehow. Awaiting your response Created attachment 121338 [details] attachment-1143-0.html I literally just reinstalled the latest version only backing up my settings for brushes. Would this still be a prudent thing to do under these circumstances? Loz ________________________________ From: vanyossi <bugzilla_noreply@kde.org> Sent: Friday, July 5, 2019 8:06:53 PM To: lozmacdesigns@hotmail.com Subject: [krita] [Bug 409535] Unable to remember workspace last used on program exit https://bugs.kde.org/show_bug.cgi?id=409535 vanyossi <ghevan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC| |ghevan@gmail.com --- Comment #1 from vanyossi <ghevan@gmail.com> --- Hi! Krita does remember workspaces, at least on the kritas Im using. So as an idea could you reset your configuration options and see if the problem persists? (how to reset config: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration). It is possible the configuration got corrupted somehow. Awaiting your response -- You are receiving this mail because: You reported the bug. yes, its prudent since reinstalling will not mess with your krita user's configuration. Krita uses a default configuration if none exists, but if there is one that is the one it will use. Created attachment 121339 [details] attachment-1472-0.html Renamed that arc file to no avail. Same thing. I even made a new profile (same settings but another name) to see if it would help. No. Still resets to something odd on restart and scaling breaks when screen size is changed. Loz ________________________________ From: vanyossi <bugzilla_noreply@kde.org> Sent: Friday, July 5, 2019 8:34:15 PM To: lozmacdesigns@hotmail.com Subject: [krita] [Bug 409535] Unable to remember workspace last used on program exit https://bugs.kde.org/show_bug.cgi?id=409535 --- Comment #3 from vanyossi <ghevan@gmail.com> --- yes, its prudent since reinstalling will not mess with your krita user's configuration. Krita uses a default configuration if none exists, but if there is one that is the one it will use. -- You are receiving this mail because: You reported the bug. Created attachment 121340 [details] attachment-1863-0.html Now did the display file (renamed) as well. The openGL file does not exist. Still no dice. This breaks on resize and cannot remember anything on reboot. Loz ________________________________ From: vanyossi <bugzilla_noreply@kde.org> Sent: Friday, July 5, 2019 8:34:15 PM To: lozmacdesigns@hotmail.com Subject: [krita] [Bug 409535] Unable to remember workspace last used on program exit https://bugs.kde.org/show_bug.cgi?id=409535 --- Comment #3 from vanyossi <ghevan@gmail.com> --- yes, its prudent since reinstalling will not mess with your krita user's configuration. Krita uses a default configuration if none exists, but if there is one that is the one it will use. -- You are receiving this mail because: You reported the bug. Created attachment 121342 [details] attachment-2235-0.html Update. This seems to only affect my workspaces. In particular, the separating boundaries on the elements are affected. Please see attached screenshot to illustrate. Now, even when I reload my own workspaces, as you can see from screenshot the boundaries have moved on both tools and palette. These are supposed to be further down (so that you can see all of the tools without having to scroll up & down constantly. This has to be reset constantly during program usage. On each reboot, and every time the window scaling is touched, even slightly moved. As I’m sure you can imagine, this is really annoying. Loz ________________________________ From: vanyossi <bugzilla_noreply@kde.org> Sent: Friday, July 5, 2019 8:34:15 PM To: lozmacdesigns@hotmail.com Subject: [krita] [Bug 409535] Unable to remember workspace last used on program exit https://bugs.kde.org/show_bug.cgi?id=409535 --- Comment #3 from vanyossi <ghevan@gmail.com> --- yes, its prudent since reinstalling will not mess with your krita user's configuration. Krita uses a default configuration if none exists, but if there is one that is the one it will use. -- You are receiving this mail because: You reported the bug. Created attachment 121343 [details] CC47A1509D314FEC93E6AB19E4D9482F.png [cid:image002.png@01D53379.40722720] Sorry my email ate the screenshot from last email sent... From: vanyossi<mailto:bugzilla_noreply@kde.org> Sent: 05 July 2019 20:34 To: lozmacdesigns@hotmail.com<mailto:lozmacdesigns@hotmail.com> Subject: [krita] [Bug 409535] Unable to remember workspace last used on program exit https://bugs.kde.org/show_bug.cgi?id=409535 --- Comment #3 from vanyossi <ghevan@gmail.com> --- yes, its prudent since reinstalling will not mess with your krita user's configuration. Krita uses a default configuration if none exists, but if there is one that is the one it will use. -- You are receiving this mail because: You reported the bug. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. *** This bug has been marked as a duplicate of bug 408160 *** |
