sometimes this also happens after invoking the editor, but File/Save gives this bug reliably. even if a verb only has 3 conjugations stored, in the next practice after File/Save the test page asks for 15 conjugations, and only a few of them actually have labels. Makes the entire test page almost unreadable, as the text boxes lower their height to fit them all in. Reproducible: Always Steps to Reproduce: 1. load dummy.kvtml 2. start conjugation practice 3. stop practice 4. File/Save 5. Practice Again Actual Results: Test page has 15 question text boxes Expected Results: Should only show as many text boxes as there are conjugations for this specific verb most of the time, though not reliably, this can also be remedied by invoking Editor, then Edit/Languages... , selecting the dummy language, selecting the "Personal Pronouns" tab and clicking OK. My guess is that saving the document (a kdelib function) actually modifies the in-memory representation. Here are debug lines from validPersonalPronouns from 2 Practice invocations, with a File/Save action between them: parley(11758) Practice::ConjugationBackendMode::validPersonalPronouns: PP: 3 ("s1", "s3", "p3") parley(11758) Practice::ConjugationBackendMode::validPersonalPronouns: PP: 15 ("s1", "s2", "", "", "s3", "", "", "", "", "", "p1", "p2", "", "", "p3")
Created attachment 75275 [details] make sure conjugation exists before adding pronoun flag this is only a workaround: add defensive check for conjugation existence before adding a KEduVocWordFlags combination to m_pronounFlags. Strangely, all possible (num|pers|gender) combinations are found in every m_conjugation in a practice session, but only after File/Save. Before File/Save, everything looked ok.
Created attachment 75276 [details] demo vocabulary to demonstrate the bug
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
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!
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!
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!