[krita] [Bug 458083] Custom Canvas Input Profile is not remembered upon program restart
https://bugs.kde.org/show_bug.cgi?id=458083 --- Comment #1 from Jennifer Reuter --- UPDATE: I reset the settings via Settings > Reset All Settings. Whatever conflict was happening was cleared up. It now loads the files in the /input (and /shortcuts) folder just fine! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458083] New: Custom Canvas Input Profile is not remembered upon program restart
https://bugs.kde.org/show_bug.cgi?id=458083 Bug ID: 458083 Summary: Custom Canvas Input Profile is not remembered upon program restart Product: krita Version: 5.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jarodragon@gmail.com Target Milestone: --- Created attachment 151439 --> https://bugs.kde.org/attachment.cgi?id=151439=edit 'My Defaults' Input Profile SUMMARY *** When creating a new Input Profile for Canvas Input, Krita doesn't save the Input Profile (or any edits made to "Krita Default") upon closing and restarting the program. *** STEPS TO REPRODUCE 1. Navigate to Settings > Configure Krita > Edit Profiles. 2. Click 'Reset All' for a fresh start. In the krita/input folder, all default '.profile' files exist. 3. Duplicate "Krita Default", rename it to "My Defaults". Close the dialogue. 4. The setting entries get reversed in order. E.g. Activate Line Tool is at the top of the list instead of the bottom in 'Tool Invocation'. 5. Make a change to the input settings while 'My Defaults' is active, e.g. set Activate Line Tool to "` + Left Button". 6. Click Ok in the Configure Input dialogue box. 7. mydefaults.profile appears in the krita/input folder. 8. Use the program with the new invocation: it works. 9. Close the program. 10. Re-open the program and re-navigate to Configure Krita > Canvas Input. OBSERVED RESULT The Input Profile dropdown does not show the 'My Defaults' profile, despite still being visible in the krita/input folder. EXPECTED RESULT Krita loads the mydefaults.profile in the dropdown for selection, or automatic detection. SOFTWARE/OS VERSIONS Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19044 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Qt Version: Version (compiled): 5.12.12 Version (loaded): 5.12.12 ADDITIONAL INFORMATION I've attached the 'mydefaults.profile' file, because I noticed that the custom shortcuts reverse the order of entries within a category, but I do not know if this is expected behaviour. This is not an issue new to 5.1.0, I've had it for quite a while now and don't know where in the program there might be a hiccup preventing me from saving inputs. In a similar way, the Shortcut Scheme, when I import one, shows it as 'Default' when selected in the drop-down at the bottom of the Shortcuts settings, but at least they are remembered between sessions. Here's the Krita Usage Log from the above test session: SESSION: 20 Aug 2022 14:39:56 +1000. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.1.0, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 3856 -- -- -- -- -- -- -- -- 20 Aug 2022 14:39:56 +1000: Style: fusion. Available styles: windowsvista, Windows, Fusion 20 Aug 2022 14:40:08 +1000: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Fri Aug 19 13:30:01 2022 20 Aug 2022 14:40:12 +1000: Could not load resource patterns/krita_EK4500.pat 20 Aug 2022 14:40:12 +1000: Could not load resource patterns/krita_Xj4500.pat 20 Aug 2022 14:40:12 +1000: Could not load resource patterns/krita_Xm4500.pat 20 Aug 2022 14:40:12 +1000: Non-store package - creating updater 20 Aug 2022 14:43:43 +1000: Created image "Unnamed", 3840 * 2160 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 1 20 Aug 2022 14:44:53 +1000: CLOSING SESSION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447628] New: The .profile and .shortcut files aren't being read when there's an alternative Resource Folder location
https://bugs.kde.org/show_bug.cgi?id=447628 Bug ID: 447628 Summary: The .profile and .shortcut files aren't being read when there's an alternative Resource Folder location Product: krita Version: 5.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: jarodragon@gmail.com Target Milestone: --- SUMMARY The .profile and .shortcut files in the custom allocated Resource folder aren't being read by Canvas Input Settings or Keyboard Shortcuts, despite newly created files being saved there correctly. STEPS TO REPRODUCE 1. Allocate a different Resource Folder in General -> Resources configure options. (In my example, instead of on C:/ drive, it's: D:/UserFiles/AppData/Roaming/Krita.) 2. Duplicate "Krita Default" Canvas Input Settings in the 'Edit Profiles' popup. Rename to something else (e.g. "My Default"). 3. In 'D:/UserFiles/AppData/Roaming/Krita/input', a 'mydefault.profile' gets created. (Can confirm the settings are different to Krita Default when opened in a text editor) 4. During the current session, settings are remembered. 5. Upon closing Krita, and re-opening it, the profile isn't visible within settings as an option; Krita Default gets picked again. 6. The file 'mydefault.profile' is still visible in the file explorer at the D:/ location. The above process is equally applicable to .shortcuts files. OBSERVED RESULT The program does not remember, or read, the .profile or .shortcuts files in the 'input' and 'shortcuts' folders of my custom allocated Resource folder location. EXPECTED RESULT Upon creating my custom Input and Shortcut settings, they should save in the right resource folder AND be read from it. SOFTWARE/OS VERSIONS - Windows: 10, Build 19042 - C:/ is located on an SSD, D:/ is located on an HDD. ADDITIONAL INFORMATION I've currently gone around the problem by copying my preferred .profile and .shortcuts files into the original C: Resource location. It seems to read them fine there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447454] Resource-related crash (?) on startup
https://bugs.kde.org/show_bug.cgi?id=447454 --- Comment #8 from Jennifer Reuter --- Will confirm here too that it worked for me also, thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash
https://bugs.kde.org/show_bug.cgi?id=447450 --- Comment #7 from Jennifer Reuter --- Wow, I had ONE file with a capitalised file extension and once I removed it, runs just fine. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash
https://bugs.kde.org/show_bug.cgi?id=447450 --- Comment #3 from Jennifer Reuter --- Certainly! Here's the DrMingW backtrace: krita.exe caused an Access Violation at location 7FF89BB999D6 in module libkritaresources.dll Reading from location 0008. AddrPC Params 7FF89BB999D6 7FF89852A330 005FEF10 005FEF60 libkritaresources.dll!0x499d6 KisStoragePlugin::timestamp+0x6 7FF89BB78A24 151F9778 6D9C5716 005FEEC0 libkritaresources.dll!0x28a24 KisResourceStorage::timestamp+0x14 7FF89BB66444 005FF1B0 005FF170 libkritaresources.dll!0x16444 KisResourceCacheDb::addStorage+0x5c4 7FF89BB67D12 005FF290 0001 153A1B30 libkritaresources.dll!0x17d12 KisResourceCacheDb::synchronizeStorage+0xa12 7FF89BB76C91 005FF390 005FF390 0030 libkritaresources.dll!0x26c91 KisResourceLocator::synchronizeDb+0x231 7FF89BB7765F 005FF548 005FF540 7FF8A744A870 libkritaresources.dll!0x2765f KisResourceLocator::initialize+0x1bf 7FF8992D176E 005FFB80 005FF7A0 009E libkritaui.dll!0x38176e KisApplication::registerResources+0xede 7FF8992D47FB 7FF898399970 7FF88EC21D30 000C libkritaui.dll!0x3847fb KisApplication::start+0x36b 7FF899E3546F 0001 02821AD0 000140007970 krita.dll!0x546f krita_main+0x25bf 0001400013C7 krita.exe!0x13c7 __tmainCRTStartup+0x247 0001400014CB krita.exe!0x14cb WinMainCRTStartup+0x1b 7FF8D57A7034 KERNEL32.DLL!0x17034 BaseThreadInitThunk+0x14 7FF8D6CE2651 ntdll.dll!0x52651 RtlUserThreadStart+0x21 00014000-000140047000 krita.exe 5.0.0.52 7FF8D6C9-7FF8D6E85000 ntdll.dll 6.2.19041.1288 7FF8D579-7FF8D584E000 KERNEL32.DLL 6.2.19041.1348 7FF8D47D-7FF8D4A98000 KERNELBASE.dll6.2.19041.1348 7FF8D19F-7FF8D1A8 apphelp.dll 6.2.19041.1320 7FF8A851-7FF8A857 AcGenral.DLL 6.2.19041.546 7FF8D692-7FF8D69BE000 msvcrt.dll7.0.19041.546 7FF8D680-7FF8D689B000 sechost.dll 6.2.19041.906 7FF8D5B6-7FF8D5C8A000 RPCRT4.dll6.2.19041.1288 7FF8D4EB-7FF8D4F05000 SHLWAPI.dll 6.2.19041.1023 7FF8D58F-7FF8D5A91000 USER32.dll6.2.19041.1202 7FF8D47A-7FF8D47C2000 win32u.dll6.2.19041.1320 7FF8D4CE-7FF8D4D0B000 GDI32.dll 6.2.19041.1202 7FF8D456-7FF8D466B000 gdi32full.dll 6.2.19041.1110 7FF8D467-7FF8D470D000 msvcp_win.dll 6.2.19041.789 7FF8D440-7FF8D450 ucrtbase.dll 6.2.19041.789 7FF8D66D-7FF8D67FA000 ole32.dll 6.2.19041.1202 7FF8D618-7FF8D64D5000 combase.dll 6.2.19041.1348 7FF8D4F9-7FF8D56CF000 SHELL32.dll 6.2.19041.1320 7FF8D4D1-7FF8D4DBC000 ADVAPI32.dll 6.2.19041.1052 7FF8D42B-7FF8D42DE000 USERENV.dll 6.2.19041.572 7FF8CF64-7FF8CF65D000 MPR.dll 6.2.19041.546 7FF8D427-7FF8D42A1000 SspiCli.dll 6.2.19041.1266 7FF8D4E2-7FF8D4E5 IMM32.DLL 6.2.19041.546 7FF899E3-7FF89A4CF000 krita.dll 7FF89CC3-7FF89CCF2000 libkritaglobal.dll 7FF89BB5-7FF89BC41000 libkritaresources.dll 6144-6145A000 libgcc_s_seh-1.dll 7FF89982-7FF899E2D000 libkritaimage.dll 6FC4-6FDA5000 libstdc++-6.dll 7FF8A743-7FF8A7493000 libKF5ConfigCore.dll 7FF89E78-7FF89E7D7000 libKF5I18n.dll 7FF898F5-7FF89981F000 libkritaui.dll 7FF8BE1E-7FF8BE1EE000 libkritaversion.dll 7FF89892-7FF898F43000 Qt5Gui.dll5.12.12.0 7FF8982F-7FF89891E000 Qt5Core.dll 5.12.12.0 7FF8D5C9-7FF8D5CFB000 WS2_32.dll6.2.19041.546 7FF897D8-7FF8982EE000 Qt5Widgets.dll5.12.12.0 7FF8A84E-7FF8A8505000 libkritaplugin.dll 7FF89E8A-7FF89E8DB000 Qt5Xml.dll5.12.12.0 7FF8BE16-7FF8BE17D000 libkritastore.dll 7FF89E74-7FF89E773000 libquazip5.dll 7FF89DE0-7FF89DE48000 Qt5Sql.dll5.12.12.0 7FF89DAA-7FF89DB36000 libKF5CoreAddons.dll 6494-64955000 libwinpthread-1.dll 1.0.0.0 7FF8BD02-7FF8BD03F000 libkritacommand.dll 7FF89D47-7FF89D4A8000 libkritametadata.dll 7FF897D1-7FF897D73000 libkritapsd.dll 7FF89CBE-7FF89CC2E000 libHalf-2_5.dll 7FF897BB-7FF897D0D000 libkritawidgetutils.dll 7FF89787-7FF897BA2000 libkritapigment.dll 7FF8976D-7FF897867000 libfftw3.dll 7FF8976B-7FF8976CF000 intl.dll 0.19.0.0
