Description: 1) some extensions seem to to keep crashing and cause a 'restart in safe mode' loop > not sure which exactly: i removed BaseReporter, CADLO, and Japanese Education Tool 2)the restart/crash loop (which eventually resolves and was same in 6.3 really): restart in safe/restart in normal / send-crash-report / restart in safe / restart in normal / send-crash report/recover or discard document / restart in safe / restart in normal ... 3) on finally making into my .odb I find some forms (quite complex) are FUBAR. Some with very similar set up and same macros (open-close/show-hide sections)seem ok - but one (based on same 'macro-template')in particular is so completely f*~@ed up it is almost funny :/ I have no idea why - that form is so broken i dont know where to begin. Will be going straight back to 6.3 (so i can get so work done:) - however as a note: Base on 7.0 did not have this problem (at least on LO.7(dev) from c.1 week ago) - there where some other issues (all fonts on button-names reverts to default:/) - but otherwise the form works fine in 7.0 - and is utterly screwed in 6.4 ... (will add any info if i come across it, but heading straight back to 6.3 for now) (Love you Libre!) Steps to Reproduce: 1.unclear - only effects some of my forms 2. 3. Actual Results: form layout, sections and controls are scattered around like confetti :) Expected Results: ... Reproducible: Always User Profile Reset: No Additional Info: ...
Ok - so it may not be 6.4.4.2 exactly... The problematic forms are fine in edit mode, but glitched in normal view - resizing the window manually with mouse resolves the glitches - can actually see something similar in 6.3 also for those same forms ...
IDK :/... forms seem to sort themselves out once they have been resized, after which they can be are ratio or full screen no problem > but on first opening new install of Base the window seems to default to a 'non-maximised-but-full-screen-fit', and when this is scrolled multiple glitches appear .. [this is scrolling down a form with multiple sections with 'MultiformMacro' to jump between sections when they are hidden (currently they are all shown on first opening the form for development purposes)] Changing the size/position of the open form window (does not seem to matter where/how much)resolves the glitches, which do not reappear when the form is next opened. A bad explanation i know > in short, is there some kind of initial/default window scaling that causes visual glitches that do not persist after user-defined window scaling is applied ?
pretty sure now that this is related to opening forms (at least my forms with sections) for first time AFTER A NEW INSTALL of 6.3/6.4 LO - after steps above, forms open (and re-open) properly on subsequent LO instances.
(In reply to trowelandmattock from comment #3) > pretty sure now that this is related to opening forms (at least my forms > with sections) for first time AFTER A NEW INSTALL of 6.3/6.4 LO - after > steps above, forms open (and re-open) properly on subsequent LO instances. This sounds like you should be able to reproduce the problem always in Safe mode. Help - Restart in safe mode and then Continue in safe mode. Is this the case? Regarding what you say in the description, is the problem gone even in Safe mode? A minimal example file would be nice. Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear trowelandmattock, 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: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
Dear trowelandmattock, 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 Warm Regards, QA Team MassPing-NeedInfo-FollowUp