Bug 332731 - auto-spellcheck state is inconsistent upon startup
Summary: auto-spellcheck state is inconsistent upon startup
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: inputline (show other bugs)
Version: 1.5
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-28 11:31 UTC by cluebat
Modified: 2023-02-09 03:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cluebat 2014-03-28 11:31:54 UTC
After enabling auto-spellcheck for the inputline, the option remains checked across restarts of Konversation. However, the internal state is inconsistent with the indicated state. After restarting, more often than not, spellchecking is not actually enabled but the option appears as checked. Toggling the state actually enabled auto-spellcheck for real.

Reproducible: Always

Steps to Reproduce:
1. Turn on auto-spell check
2. Exist and restart Konversation
3. Type gibberish and observe no marked spelling errors
4. Toggle auto-spellcheck state
5. Observe that nonsense words are now marked as misspellings

Actual Results:  
With steps 1-3, misspelling go unnoticed. performing step 4 corrects this.

Expected Results:  
Step 4 should not be necessary and step5 should be step 3.

spelling language is US English, nothing strange that should cause any trouble enabling spellcheck
Comment 1 Andrew Crouthamel 2018-11-11 04:33:24 UTC
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!
Comment 2 Andrew Crouthamel 2018-11-21 04:37:50 UTC
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!
Comment 3 Justin Zobel 2023-01-10 01:52:21 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 4 Bug Janitor Service 2023-01-25 05:06:08 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 2023-02-09 03:54:15 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!