Created attachment 47665 [details]
An image where you can see the bug.
On A1, when we can write in, jsut when we don't write anything yet, there is a black block (who is center).
It's a very strange and minor bug.
I could not reproduce this bug. Can you please give us more details, e.g. operating system?
I cann see taht on a slow desktop with Windows XP Familial SP3.
It does the smae ting for all the sheets.
Created attachment 49822 [details]
LibreOffice 3.4.2 Calc, on Windows 7 64bit.
I have the same problem with a powerfull PC, on Windows 7 x64, with LibreOffice 3.4.2 (final).
[Reproducible] with "LibreOffice 3.4.4RC2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:402)]"
[Reproducible] with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: d3d1481-3f8994a-2ba0a9f)]" (110909)
Steps to reproduce:
1. Open new spreadsheet document
2. double click 'A1'
You see the same effect:
11. Open new spreadsheet document
12. Click D10
13. Menu 'Window -> Split'
Window becomes splitted
13. Couble click D10 (Or A1), black area will be shown.
I thought that I would already have confirmed that (here or in an other bug), but I can't find any other bug.
Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
Adding Noel to CC. Yes, we were just discussing this weird issue the other day.
*** Bug 38518 has been marked as a duplicate of this bug. ***
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
Build ID: 087a610fcd5c0c354a9ed6bfccd3451b667d62a3
TinderBox: Win-x86@6-debug, Branch:master, Time: 2013-08-04_21:41:24
Windows 8.1 Enterprise Preview 64 bit
Confirmed on OS X 10.8.4, LO 188.8.131.52.
not reproducible with LibO 3.3.3 and 3.3.4 so it has been probably introduced in the 3.4.x branch
still reproducible using 184.108.40.206 and 220.127.116.11.alpha0+
Build ID: 488f31200094d7237d45545ab227014831a1f8e6
TinderBox: Win-x86@39, Branch:master, Time: 2014-06-15_05:02:39
Created attachment 111783 [details]
Capture with black square
Reproduced on openSUSE Tumbleweed with version: 18.104.22.168.0+ .
*** Bug 88243 has been marked as a duplicate of this bug. ***
Migrating Whiteboard tags to Keywords: (preBibisect)
Not reproducible for me with LO 22.214.171.124.0+ (GTK2) and master (GTK3), both built at home under Ubuntu 15.10 x86-64.
Please, test again.
Best regards. JBF
Following Jean-Baptiste's comment, let's put this one to NEEDINFO.
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 INSUFFICIENTDATA
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!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker