Created attachment 93154 [details] Screen shot of the problem dialog box. When I create a form and try to edit a field, the "Position and Size" pop-up box does not display correctly. It draws the box outline, but the contents are what is underneath, not the tabs and options that should be displayed. If I click on the box and happen to find one of the Width or Height Increase/Decrease buttons, then the contents display but I can not change them. Clicking on the Rotation or Slant & Corner Radius tabs does not display their contents. The only buttons that work are the OK and Cancel buttons at the bottom. Other pop-up boxes, such as the Control and Form pop-up work correctly. This makes it impossible to use any of the options in this pop-up. This problem was present in 4.1 and not fixed in 4.2.
I thought i saw something similar, both with "size & position" and "Area.." dialog boxes, but after an application restart and a fresh base document, the dialogs respond normally. Are you certain you can reproduce the problem? Can you provide a series of steps for it? my installation can function normally (LO Version: 4.1.4.2 Build ID: 410m0(Build:2) OS: Opensuse 12.2 86x64
Well, this is weird... SOME fields show this behaviour and some don't. Same goes for field labels, as well as Drawing toolbar objects. If one nudges the field a bit, then tries again the problem goes away If one cuts & pastes the label in adifferent document and back in, all ok. Maybe a graphics update issue?? LO Version: 4.1.4.2 Build ID: 410m0(Build:2) OS: Opensuse 12.2 86x64, Nvidia with proprietary drivers
Created attachment 93155 [details] screenshot of transparent, unresponsive "size & position" dialog box Further digging around revealed that a) changing the anchoring of the item from Page to Paragraph and vice versa may "permit" the dialogbox to show up properly b) de-activating Web-laout MAY have the same effect c)saving and re-opening does NOT reproducibly solve the problem On a clean, fresh document, i cannot reproduce it On a busy form with Labels, backgrounds, drawing objects, a table component it happens on an intermittent basis, and NOT on the same objects. still NEEDINFO... anyway, attached a screenshot of the situation.. LO Version: 4.1.4.2 Build ID: 410m0(Build:2) OS: Opensuse 12.2 86x64, Nvidia with proprietary drivers
(In reply to comment #0) > > This problem was present in 4.1 and not fixed in 4.2. You have recognized the problem in LO 4.1. ... The version in theis report has to show the first version the bug appeared. Please set it to the first version where you recognized it. I can't confirm this bug with any version here (have about 40 versions installed for testing). My system: OpenSUSE 12.3 64bit rpm, KDE, LO up to 4.2.0.4 (tested with this before answering to this report) and Intel-onboard-graphic.
(In reply to comment #0) can you specify which graphics adapter & driver you are using? just tested with Nouveau instead of Nvidia and the problems seem not to appear.. could very well be wrong though...
I'm new to Base, converting from Alpha 5. I can reproduce this at will by opening a database converted from an Alpha 5 dbf, creating the very first form using the Form Wizard, selecting all the fields (there are about 50 fields, a mix of text, dates, and boolean), choosing one of the columnar layouts and clicking finish. Then I edit the form, pick one of the of the fields, right click on it and choose the Position and Size... option. I've tried it on many of the fields, text, date, and boolean and gotten the same results. I've ungrouped the field, separating the field and label and tried just the label or just the field. Same failure. I've reproduced the issue with a new DB that I created from scratch in Base also. I do New->Database, Create a new Database (HSQLEmbedded), Next, Finish, Save. Create new table using wizard, Personal, Addresses, select all fields, Finish. Close database window. Click Forms, Use Wizard to Create Form..., select all fields, Next, Next, choose one of the columnar layouts, and Finish. Edit the form. Right click on a field, choose position and size and ... failure to display.... If I create a form in the above new database that only has the first three fields I still have the problem. Nudging a field did not get it to display. Changing the anchor from paragraph to page and back to paragraph did not help. Changing from Web Layout to Print Layout did not help either. Computer is a desktop running Windows 7 Pro 64 bit, fully patched, 16GB RAM, Nvidia GeForce GTX 560 Ti display adapter with latest version of Nvidia drivers, currently 332.21.
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: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO 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! Warm Regards, QA Team
I'm Sorry for the delay in replying. I'm running the native Nvidia latest driver for my MSI GTX 560 Ti adapter. It's currently the GeForce 340.52 driver. I've also updated to 4.3.0.4 and the problem is still present. Let me know if there is anything else I can supply. I'll try to be more timely in responding :-)
Can't reproduce on Version: 4.3.2.2 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d OSX Yosemite 10.10 Graphics : Jeu de composants : NVIDIA GeForce 320M Type : Processeur graphique (GPU) Bus : PCI VRAM (totale) : 256 Mo Fournisseur : NVIDIA (0x10de) Identifiant du périphérique : 0x08a4 Identifiant de révision : 0x00a2 Révision de la ROM : 3546
Could well be a graphics driver issue I followed your instructions from comment 6, i.e. complete new database using default Assets table via database wizard, the directly on to creating form with corresponding wizard. Open form for editing (form design mode), select a field with mouse, right mouse button click, choose Position & Size.
Do you still see this with latest production release 4322 ?
The problem is not fixed. For me it's 100% reproducible. I have an MSI GeForce GTX 560 Ti card with the latest Nvidia driver, 344.11. I upgraded to LibreOffice Version: 4.3.2.2 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d, installing it on top of the 4.3.1.x version that I had. I opened Base and then the database. The database is a simple Alpha 5 DB used for my contact information. It has about 46 fields that are all basic fields like FNAME, LNAME, STREET, AGE, BDATE and some boolean fields. There are no forms defined in Base for this DB. I used the Wizard to create a new form. I selected the first two field, FNAME and LNAME. I clicked Next twice. I selected Columnar - Labels Left and clicked finish. I closed the window that opened. I then right clicked on the newly create form and selected Edit. I right clicked on the first field and selected Position and Size... The window that popped up is just the contents of the screen under where the window popped up. It displays no controls, tabs, or any other program features. If I mouse around left clicking as I do, I eventually hit a field or control. At that point all the appropriate contents appear with the original image vanishing. I can then use the controls normally. One difference from previous versions is that clicking on the Rotation or Slant & Corner Radius tabs causes their controls to display correctly. In previous versions they also displayed nothing but the image under the window. If I right click the field and select any other option, like Description..., Name..., Control..., or Form..., those windows open with the correct contents. It's just the Position and Size... window that does not display correctly. What else can I do to help resolve this issue? I'm not a windows programmer, but I used to program in C and Assembly and am otherwise very computer literate.
(In reply to Jus from comment #12) > What else can I do to help resolve this issue? I'm not a windows programmer, > but I used to program in C and Assembly and am otherwise very computer > literate. You could hop on the quality assurance channel: http://webchat.freenode.net/?channel=libreoffice-qa You can try a daily Windows build: http://dev-builds.libreoffice.org/daily/master/Win-x86@39/ It installs alongside your regular LibO. You could try reproducing the problem using a live USB stick with Ubuntu: http://releases.ubuntu.com/14.10/ If you want to get into development: https://wiki.documentfoundation.org/Development
Thank you for the suggestions. I tried installing 4.3.3.2 on another system, an HP laptop using the built-in Intel video chip/drivers. I get the same failure. The "Position and Size" dialog box appears with only the background of the screen in the box, none of the controls. I also tried installing libreoffice-4-4~2014-11-24_13.14.58_LibreOfficeDev_4.4.0.0.beta1_Win_x86_en-US_de_ar_ja_ru_qtz and master~2014-11-21_00.01.14_LibreOfficeDev_4.5.0.0.alpha0_Win_x86 both had this problem resolved. The "Position and Size" window appears correctly with all the controls visible and usable. So this problem in 4.3.3.2 release is fixed in the 4.4 and 4.5 trains. There are other issues in both 4.4 and 4.5, notably the form the wizard created was "permanent" in that even if I deleted it, when I used the Wizard to create a different form, after I saved the new one the form that I then opened was the original one created with the wizard and not the new one.
(In reply to Jus from comment #14) > So this problem in 4.3.3.2 release is fixed in the 4.4 and 4.5 trains. > > There are other issues in both 4.4 and 4.5, notably the form the wizard > created was "permanent" in that even if I deleted it, when I used the Wizard > to create a different form, after I saved the new one the form that I then > opened was the original one created with the wizard and not the new one. Thanks for testing. I will mark this as WORKSFORME then. You can open separate bug reports for any other issues.
(In reply to Beluga from comment #15) > (In reply to Jus from comment #14) > > So this problem in 4.3.3.2 release is fixed in the 4.4 and 4.5 trains. > > > > There are other issues in both 4.4 and 4.5, notably the form the wizard > > created was "permanent" in that even if I deleted it, when I used the Wizard > > to create a different form, after I saved the new one the form that I then > > opened was the original one created with the wizard and not the new one. > > Thanks for testing. I will mark this as WORKSFORME then. > You can open separate bug reports for any other issues. How could you set this to "RESOLVED" and "WORKSFORME"? It seems to be a bug in 4.3.3.2 - and 4.3 will have some more bugfixes. I will repopen this bug.
(In reply to robert from comment #16) > How could you set this to "RESOLVED" and "WORKSFORME"? It seems to be a bug > in 4.3.3.2 - and 4.3 will have some more bugfixes. > I will repopen this bug. I brought this up in the QA meeting today. It was decided that the best way to act in cases like this is to: - set to WORKSFORME - notify the reporter that they can perform a bibisect to find out the specific commit that fixed the issue If the commit is found, it is up to the dev(s) to backport it, if they wish. The reporter should be aware that if no one else has reproduced the issue, it is possible that the backport repositories do not have the issue. More: https://wiki.documentfoundation.org/QA/Meetings/2014/December_03#backport Setting this back to WFM.
(In reply to Beluga from comment #17) > (In reply to robert from comment #16) > > How could you set this to "RESOLVED" and "WORKSFORME"? It seems to be a bug > > in 4.3.3.2 - and 4.3 will have some more bugfixes. > > I will repopen this bug. > > I brought this up in the QA meeting today. It was decided that the best way > to act in cases like this is to: > - set to WORKSFORME > - notify the reporter that they can perform a bibisect to find out the > specific commit that fixed the issue Looks a little bit funny for me: How could someone bibisect a buggy behavior, which appears in Windows only? Isn't my bug. Doesn't appear here. But when I had a look here: https://wiki.documentfoundation.org/QA/HowToBibisect I only see the possibility to bibisect with an Ubuntu-installation.
(In reply to robert from comment #18) > Looks a little bit funny for me: How could someone bibisect a buggy > behavior, which appears in Windows only? > Isn't my bug. Doesn't appear here. But when I had a look here: > https://wiki.documentfoundation.org/QA/HowToBibisect > I only see the possibility to bibisect with an Ubuntu-installation. Yep, that's the limitation. Still, the fact is that developers are not going to start doing backports for things they don't know exist. Even if the commit that fixed this issue was discovered, backporting might be skipped as not needed.
I'm sorry, but I don't understand how this can be "worksforme" when I'm not the only one able to cause the issue (see the second screen shot by gagrilli) and I've reproduced it on two completely different PCs? I'd be happy to try to find the version that fixes it, but I'm a windows user and, as noted in the Wiki, it appears that only Ubuntu is supported for this exercise. When is V4.4 going to released? If it's soon, I'll just wait for that.
(In reply to Jus from comment #20) > I'm sorry, but I don't understand how this can be "worksforme" when I'm not > the only one able to cause the issue (see the second screen shot by > gagrilli) and I've reproduced it on two completely different PCs? > > I'd be happy to try to find the version that fixes it, but I'm a windows > user and, as noted in the Wiki, it appears that only Ubuntu is supported for > this exercise. > > When is V4.4 going to released? If it's soon, I'll just wait for that. Please don't change the status without any reason or new discoveries. 4.4 is going to be released Feb 1 2015, but I don't see 4.4 beta as particularly unstable (it's going to release candidate status in under two weeks). Beta2 is coming soon. https://wiki.documentfoundation.org/ReleasePlan/4.4 You can use a parallel install of 4.4 beta: https://wiki.documentfoundation.org/Installing_in_parallel#Windows