| Summary: | Spell checker doesn't start automatically on file open. Needs user interaction | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Telesto <telesto> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | VERIFIED FIXED | ||
| Severity: | normal | CC: | dgp-mail, glogow, xiscofauli |
| Priority: | medium | ||
| Version: | 6.2.0.0.alpha0+ | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=116370 https://bugs.documentfoundation.org/show_bug.cgi?id=116872 |
||
| Whiteboard: | target:6.2.0 target:6.1.1 target:6.0.7 | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 96000 | ||
| Attachments: |
Example file
page settings |
||
|
Description
Telesto
2018-08-23 16:28:07 UTC
Created attachment 144399 [details]
Example file
Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ce68889678bca3b51c258452f7bfdd21982e4a0d tdf#119458 always start the SwDocIdle It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. (In reply to Commit Notification from comment #2) > Jan-Marek Glogowski committed a patch related to this issue. Status is still UNCONFIRMED. I think it should be changed. Setting to NEW for now (or should it be assigned). Anyway; thanks for the quick fix :-) cc: Jan-Marek Glogowski The committed fix actually re-introduces bug 116370 :-( Didn't realize and just tested independently. Both bugs should be finally fixed with: https://gerrit.libreoffice.org/#/c/59586/ This turned out to be more tricky then expected, so we need to re-test both after the merge or with a cherry-pick, on all platforms. (In reply to Jan-Marek Glogowski from comment #6) > The committed fix actually re-introduces bug 116370 :-( > > Didn't realize and just tested independently. Out of curiosity; what made you test for bug 116370 again? Eine Eingebung? Or a procedural check? (In reply to Telesto from comment #7) > (In reply to Jan-Marek Glogowski from comment #6) > > The committed fix actually re-introduces bug 116370 :-( > > > > Didn't realize and just tested independently. > > Out of curiosity; what made you test for bug 116370 again? Eine Eingebung? > Or a procedural check? No. If it had been, I wouldn't have pushed the broken fix ;-) The whole SwDoc idle formatting has always been fragile, because the idle document state is very distributed. This results in either no jobs run or busy loops, like the one in the printing problem. This is just a constant problem, if you touch code related to the Scheduler / system event loop integration. I'll recheck, if I can change Windows to behave like the other backends, which just run timers via the main loop and not via an extra thread. Windows has SetTimer for this, but for whatever reason, this function has a minimum timeout > 0, which results in other problems. Abstracting the platform behaviour to be consistent in this regard is the main problem. And I always check some source to see, if a LO uses a whole CPU core. With todays HW you often doesn't realise this, as everything still runs smooth. Since the original Scheduler work started for 5.0 we had a lot of bugs, where Idles starved lower priority events, which also resulted in busy loops. Just see my current painting fix for the floating, dockable toolbars. I did notice that timer are a delicate matter. And changes with the potential for nasty side-effect. So deep respect for touching the timer code; especially with the fallout potential and the clean-up work afterwards. Btw, a small sidenote. Seeing Noels comments at https://gerrit.libreoffice.org/#/c/59586/ This bug report started with some trouble with the spellchecker on MacOS. No spell checking in some cases (when pasting content into a new document). I switched to Windows to check (where I found this bug) However, MacOS pre-dates the changes here. The spell checker stopped working out of the blue for new documents (similar to this report). And will be functioning again a while later (with in the same session, if I remember correctly). Did happen once or twice. I didn't observe it again. It might be that change are likelier plenty of documents open (16 or something like that; relative small document; don't have that at the moment) And not sure if there is some relation with MacOS sleep or the fact that I'm running LibreOffice for multiple days.. So pure speculation. might be no correlation.. Version: 6.2.0.0.alpha0+ Build ID: c958f52b813d34baa9b5236bb34a08a04e6b0aba CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-08-10_05:06:44 Locale: nl-NL (nl_NL.UTF-8); Calc: threaded Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=107f0e6dba57a5b27366a35a5cdb184079546df0 tdf#119458 fix sw background Idle state handling It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=771544544ee13ec98961f93b5313a7d2e29429cd tdf#119458 fix sw background Idle unblocking It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=3bd8316718fdfed454c01a9c4ae6af6beb34437d tdf#119458 just wakeup Scheduler on active Idle It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=20e46a6ca5b62f7177f799eae9e0f26e659fd03b&h=libreoffice-6-1 tdf#119458 reorganize sw background Idle handling It will be available in 6.1.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Created attachment 144572 [details]
page settings
Just now i have this case in a similar situation.
An letter with only one page.
When i open the document on the PC i have written, i see only 1 page.
When i open it on another PC it has 2 pages!
The last line is on the second page.
Why?
Everything is the same: Debian 8, same Libreoffice, same Font is installed, only a different printer is installed, but the margins are so big that it can't make a difference.
There should be no difference when i open a document on another PC!
I MUST use PDF to get identical results on different PC's.
Please delete comment 14 - it is related to https://bugs.documentfoundation.org/show_bug.cgi?id=119584 Jan-Marek, is the work over? If so, can you mark se Fixed? Since there are also other bugs in See Also fixed with this, please comment on backport to 6.0. (In reply to Timur from comment #16) > Jan-Marek, is the work over? If so, can you mark se Fixed? > Since there are also other bugs in See Also fixed with this, please comment > on backport to 6.0. jmux> x1sc0: tdf#116370 is a 6.0 bug. The patch results in tdf#119458. So for 6.0 we need both patches. I'm waiting for https://gerrit.libreoffice.org/#/c/59769/, so I can backport both. Verified in Version: 6.2.0.0.alpha0+ Build ID: 433fce6571d4b9121374047324a7d2d2722ac3e4 CPU threads: 16; OS: Windows 6.3; UI render: default; Locale: en-GB (en_GB); Calc: threaded @Jan-Marek Glogowski, Should it be closed as RESOLVED FIXED ? Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "libreoffice-6-1-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=3abec366a3fdb8657d69e24b69b4338121f80b22&h=libreoffice-6-1-1 tdf#119458 reorganize sw background Idle handling It will be available in 6.1.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Setting to VERIFIED. @Jan-Marek Glogowski, Thanks for fixing this!
> jmux> x1sc0: tdf#116370 is a 6.0 bug. The patch results in tdf#119458. So
> for 6.0 we need both patches. I'm waiting for
> https://gerrit.libreoffice.org/#/c/59769/, so I can backport both.
Do no forget to backport it to 6.0 when you have a moment...
Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=36556f2f2c30c10f34d5495a7f7cc735b9b9417a&h=libreoffice-6-0 tdf#119458 reorganize sw background Idle handling It will be available in 6.0.7. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. |