Created attachment 92498 [details]
screenshot with example
When entering a string of alpha or numerical or alphanumerical characters into a Calc cell the default font is not displayed even after after striking the "Enter" key or clicking into another cell.
Only after operations like:
- double clicking the cell again.
- changing the cell size (hight, width)
- doing some other operations on the same sheet but different cells the correct font is suddenly displayed> However, which other operations triggered the font correction is unclear.
- copy and paste of a cell with wrong font shows the correct font after paste operation but original cell still stays with the wrong font.
1- I could not verify it the font type is wrong or only the size. Thus above wrong or correct "font" could only mean "wrong font size" or "correct font size"
2- The font windows in the tool bar always show the correct font name and size, even when the font appear as wrong.
3-Used default font is Arial 10
4- I did not observe this behavior in 4.0 versions which I used up to 4.0.6
5- I tested 4.1.3 portable and did not observe this faulty behavior
Steps to reproduce:
1. Open a spread sheet
2. Type any character string
3. Do any of above mentioned operations - recommendation: copy and paste the content below the cell used to enter the original text.
Entering a string into a cell and striking "Enter" key or clicking into another cell does nor display the correct font/font size
Already during the entering of a string into a cell the correct font/font size should be displayed.
Operating System: Windows XP
Version: 220.127.116.11 release
LibO 18.104.22.168 rc with Win7 : not reproduced.
Just to be sure : what you called "default font" is the font for "default" cell style ?
Cannot comment on 4.2 version yet
"default font" is the font
- which is automatically used when I open Calc and start typing in a cell
- which is to be seen when I open Cell Styles, tab Font and look for Western font
Hope this clarifies.
OK, it clarifies. Nevertheless, let me propose this rewording:
- when opening Calc, all cells initialy wear the "Default" cell style,
- so typing in a cell applies the font specified by the "Default" cell style font,
- styles are visible in the stylist (F11). Within "Cell styles" panel, right-click on "Default" (which is selected in light grey), then "Modify>Font" to check it.
Bubsequent change of this font affect all cells where:
- no font superseding has been applied by a direct formating command ("Format cell" or formating toolbar), and:
- no other styles has been applied (except style derived from "Default" with no font change).
Bug is still to be seen in 22.214.171.124 on XP/SP3
I can not reproduce with LO 4.3.2, win7. Font Liberation Sans, size 10. Please, could you test with version 4.3.x? Thank you
I still see the bug in
Version: 126.96.36.199 (portable)
Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d
Version: 188.8.131.52 (normal)
Build ID: 933c0aa564ec4f8883ed5732c866db48dca4dac5
all on XP/SP3
Win 7 64-bit Version: 184.108.40.206.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Upgraded to Version: 220.127.116.11
Build ID: bc356b2f991740509f321d70e4512a6a54c5f243 and still see the bug.
(In reply to raal from comment #5)
> I can not reproduce with LO 4.3.2, win7
(In reply to Beluga from comment #7)
> Can't repro.
> Win 7 64-bit Version: 18.104.22.168.alpha2+
(In reply to bugquestcontri from comment #6)
> I still see the bug in
> Version: 22.214.171.124 (portable)
> Version: 126.96.36.199 (normal)
> all on XP/SP3
Okay, looks like we need WinXP to test this bug
Whiteboard -> needsWindowsXP
I can confirm the bug on my XP machine for LibO 188.8.131.52
Hoewver, on my kubuntu 14.04 LTS machine I do not see the bug for LibO. 184.108.40.206 and 220.127.116.11.
I can confirm the bug on my XP machine for LibO 18.104.22.168
However, on my kubuntu 14.04 LTS machine I do not see the bug for LibO. 22.214.171.124 and 126.96.36.199.
(In reply to bugquestcontri from comment #11)
> I can confirm the bug on my XP machine for LibO 188.8.131.52
> However, on my kubuntu 14.04 LTS machine I do not see the bug for LibO.
> 184.108.40.206 and 220.127.116.11.
Sorry to keep asking, but as this seems like such a hard bug to reproduce, could you test with 4.4 on WinXP? Or even 4.4.1 release candidate.
Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
I see the bug in 18.104.22.168 at the XP machine. As my XP machine is my production (or machine needed to make my libing) I cannot yet install 4.4. and will change on this machine only at 4.4.4 to be on the safe side.
I will have a look for this bug then and report here.
(In reply to bugquestcontri from comment #13)
> I see the bug in 22.214.171.124 at the XP machine. As my XP machine is my
> production (or machine needed to make my libing) I cannot yet install 4.4.
> and will change on this machine only at 4.4.4 to be on the safe side.
> I will have a look for this bug then and report here.
You have two options that enable you to test right now.
A master build of 4.5, which installs separately:
Separate install GUI, which lets you install any version separately:
None of those will affect your 4.3.6.
Thanks for your hint of adding additional versions. Once I have my new production machine (kubuntu with XP virtual machines inside) fully running I will be more brave in installing more and newer versions.
For another test I used portable versions:
126.96.36.199 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7
188.8.131.52 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d
184.108.40.206 Build ID: bc356b2f991740509f321d70e4512a6a54c5f243
I don't see the bug in the portable versions. I am seeing this bug in the normal XP version since I reported it for 4.1.4 x.y.4 is my typical step-up version.
The test with portable versions doesn't really contribute to the solution. When I get the impression that 4.4.1 is a bit more stable than the 4.4.0, I will change a bit earlier. Maybe 4.4.2.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
This NEEDINFO message was generated on: 2015-09-03
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-10-14