adding Bug 79301 - crash in extension manager deleting an extension after upgrading it

I add Bug 79761 - autocorrect slow-down got worse

working with large autocorrect lists in 4.4 master causes long freezes while you type.

I add Bug 81517 - FILEOPEN: pictures in .xls spreadsheets no longer displayed
very evident regression. may affect lot of users and files.

Hereby I nominate "Bug 81756 - Crasher in Format:Page... menu item". Mac OSX only so far.

Adding bug 81496 "Crash in Format Page"

Should add Bug 54342 : seems not to be frequent, but it is awfull when one lose many formulaes in a text without any solution !

@jmg74
this list is reserved to bugs that are specific to the 4.4.x branch
the bug you added is already present in older branches so it does not belong to this list and I'll remove it.

if you think that it qualifies as a MAB you should file it to the proper list which is currently mab4.2 (see the link under See Also)

Added bug 83379 - regression
Data corruption with relatively simple draw objects

Added bug 83174 - regression + crasher
Something is going on with the interaction with sections and the table of contents where if an entry in the TOC is removed and then you try to export as PDF you get a crash. Native ODF file

Adding bug 83633 "FILESAVE: Crash when save in ODF 1.0/1.1".  It is aa
crash and a regression (introduced around 2014-07-02).

added Bug 84678 - FILEOPEN: .DOCX textbox margins incorrectly set in 4.4.x

interoperability regression in 4.4.x (works fine in 4.3.2.2)

Added bug 84854 - critical regression.

Spreadsheet is not drawing correctly when it loads - resulting in massive black areas on the sheet and inability to use it at all. So far only confirmed with:
TinderBox: Win-x86@42.

Does not affect: TinderBox: Win-x86@39

I add Bug 85076 - F11 "Styles and Formatting" not working when sidebar hidden

probably a side effect of sidebar incorporation of that floating panel in 4.4.x
see: https://wiki.documentfoundation.org/ReleaseNotes/4.4#Sidebar_changes

adding Bug 83798 - Chapter numbers (Outline numbering) not included in Table of Contents (TOC)

Adding Bug 86552 - Segmentation fault when I press Ctrl-Z

Regression introduced between 4.4.0.0 alpha2 -> beta1 that causes a crash in Draw, Writer, and probably other components if you try to undo changes w/Ctrl-Z when editing macros.

Add bug 86572: Critical regression automatic recalculation formulas and graphics

Nominating bug 86578 for loss of formatting style--area fill and transparency--of coincident image frames and text frames occurring when an .ODT document is saved and reopened. Causes image in an image frame visible during a Writer edit session to become invisible on reopen.

This bug is present in 4.2, 4.3 and 4.4 versions ( https://www.libreoffice.org/bugzilla/show_bug.cgi?id=79641 )

@shunesburg69, *,
(In reply to shunesburg69 from comment #18)
> This bug is present in 4.2, 4.3 and 4.4 versions (
> https://www.libreoffice.org/bugzilla/show_bug.cgi?id=79641 )

Assume you are referring to bug 81876 -- FORMATTING: Fontwork-formatted text is duplicated. That has been added to mab4.3 (bug 75025). Won't be listed in both mab lists.

Added bug 86904 - crasher regression in calc.
Insert -> Diagram results in crash.

Added bug 85806 - regression
Looks like Hebrew language is completely broken on master - might affect other RTL languages as well.

I add Bug 86678 - TOOLBAR: Underlined letters in new drop downs not working

affects new 4.4.x toolbar drop downs like the new color picker, line spacing, and insert table

Added bug 87119. Bibisected + Regression + Apparent Data Loss

Complex sheet shows empty with 4.4 but shows appropriate data in 4.3. Bibisected

adding Bug 86984 - UI:Line Numbering. Include header or footer not preserved and has no effect on counting

Added bug 87872 - regression

Inability to save basic .doc as odt, worked fine in 4.3, broken on 4.4.

Adding Bug 88056 - [FILE OPEN/SAVE] field Insert ▸ Field ▸ Page Title not saved / reloaded

Adding Bug 87663 - CRASH when attempting to add ToC to document

Promote bug 88111
Math object cannot be seen during slide show

Added bug 88194 - regression + crash

Pasting a cell that has a comment into a lot of other cells causes a hard freeze. Works fine in 4.3.5, broken in 4.4 beta 2 (and master).

Added bug 86636

Some users are experiencing completely black menus in 4.4

adding Bug 88295 - FILEOPEN: White Background Appears in Impress Text Boxes

very nasty Impress regression IMHO.

adding Bug 88276 - Please add UI for new LO 4.4. feature "Text Background Color in Draw"
(for now, I think best is to change the feature info on the wiki..)

grouped formulas lose listeners when split, recalculation broken

Add bug #76825: The style drop-down in Writer is too narrow, causing the edit style button to overlap the style text. This has been introduced in 4.0.

Adding bug 86159: “TOOLBAR: drop downs not having sufficient space on the right and bottom”. It looks horrible under Windows!

Added https://bugs.documentfoundation.org/show_bug.cgi?id=88786

Sign result with a rest between a number and an array is changed.

Adding bug 88792 Calc crashes when applying subtotals

Adding bug 87876: the View page in Settings is crushed because of an overly long checkbox label related to OpenGL, which doesn’t wrap in multiple lines.

Added https://bugs.documentfoundation.org/show_bug.cgi?id=89012

LibreOffice hangs "Create Report in Design View" in base.

When opening on Mac OS X the Finnish version of LibreOffice 4.4., in it's eneral section of Preferences the fourth part "User Interface" and "Graphic Output" collapse partially. In English version these are OK.

(In reply to Julehti from comment #40)
> When opening on Mac OS X the Finnish version of LibreOffice 4.4., in it's
> eneral section of Preferences the fourth part "User Interface" and "Graphic
> Output" collapse partially. In English version these are OK.

That is bug 87876 already on this MAB listing.

Added bug 88935 - linked images read error, flickering, freeze

Evident to some degree in all OS, various hardware.

Promote bug 86624
Position of legend is lost in chart if it is manually placed

adding (reopened) Bug 60910 FILESAVE loses Fontwork/shape objects

I nominate bug 82661 because this regression makes paragraphs with background looking very ugly.

Best regards. JBF

Added bug 63230
"Calc: Date decreased by 1 depending on Timezone"

Same bug  recurrence in 4.4.0.
And this bug has been fixed in the master.
Please adopt this fix in the next release.

Added bug #83159: Textboxes in charts are not preserving their font size when file is reopened after inital creation. This issue can be worked around by changing the font size and then restoring it back to 12, But very annoying having to do this each time I make a chart for my physics lab reports.

Nominated  bug 72007 -- Sidebar: incorrect conflicting widget attachment causing graphic artifacts when the sidebar is docked on the left.

http://cgit.freedesktop.org/libreoffice/core/commit/?id=8965bfda9753568a038303d9935f7a451282a857 seems somehow incomplete.

adding Bug 89780 - Any text placed on a slide is NOT shown when starting the slideshow from that slide
Embarrassing problem for people running presentations on Windows

Added bug 90010 - regression + bisected

Images embedded in password protected document are lost on save

I nominate bug 88941 which breaks PDF export on MacOS-X.

Best regards. JBF

Adding bug 89245 - FORMATTING, FILESAVE: Header and footer background images are not saved

There have been multiple duplicates of this, so clearly it's causing some pain

Adding https://bugs.documentfoundation.org/show_bug.cgi?id=37223 Target for paste cells from column in Calc into TABLE will be single cell instead of column
As its a usual operation that people shouldn't put much thought into and works in MSO (https://youtu.be/4zMfuzoWLv8?t=108).

Note that MSO also has more user friendly options to paste from Excel to Word that enables on right click and gives features like this extension does http://extensions.services.openoffice.org/en/project/pasteasvalue (thankfully an extension works so far even though it can be slow and its been out ages ago) only in more appealing way with preview of what will happen once you choose a paste method. But those are additions currently a bug fix that will enable an easy way to paste from Calc to Writer's table will do way more that those UI changes you're making.

Add BUG #87373: This bug causes significant readability issues due to broken kerning depending on window size introduced in 4.4 for OS X users.

Apparently our window management of color dialogs doesn't play nice with Elementary OS - already a few dupes marked.

Developer from i3 posted some findings that seem on point in comment 3

Added bug 90809 - crasher with simple Thai document. Regression, gtbtrace log attached and bibisected.

Added bug 90808 - crasher, regression, simple highlight/copy causes crash. Bisected

Added bug 90757 - crasher on sort. Regression in 4.4. Bisected

Outline numbering bug in Word docs after re-opening the doc: bug #76817

This bug is very, very, very, very, very, very, very, annoying because chapter numbering is one of the most used features of a Word Processor. And the .doc(x) format is one of the most used in the world. Basically you can NOT use LibO to edit a Word doc in which the chapters are automatically numbered, which is EVERY document ever produced by mankind. Please fix asap if you can.

(In reply to meneerjansen00 from comment #59)
> Basically you can
> NOT use LibO to edit a Word doc in which the chapters are automatically
> numbered, 

Did you do some good tests, before writing that? I cannot confirm the problem as a general issue. (Would have been unlikely, that such an issue would have gone unnoticed for years.)

(In reply to meneerjansen00 from comment #59)
removed bug 76817 from mab4.4 -- assigned to bug 88137

Adding Bug 91242 - Saving as .docx adds the outline number, which is not applied, before the header after reopening

(In reply to V Stuart Foote from comment #61)
> (In reply to meneerjansen00 from comment #59)
> removed bug 76817 from mab4.4 -- assigned to bug 88137

s/ bug 88137/ bug 88173/

Added bug 91293 - regression + bibisected

Saving a presentation file as pptx strips all hyperlinks from the presentation. It's been around for awhile but seems pretty nasty.

Bug #57989: formulas in Writer do not update when adding/deleting last row

See comment 12 for succinct description.

adding Bug 86675 - Bad-quality antialiasing for PNG images, looks terribly ugly ..

Created attachment 116892 [details]
Outline numbering gets restarted every time doc is opened

Outline numbering gets restarted every time doc is opened

(In reply to Cor Nouws from comment #60)
> (In reply to meneerjansen00 from comment #59)
> > Basically you can
> > NOT use LibO to edit a Word doc in which the chapters are automatically
> > numbered, 
> 
> Did you do some good tests, before writing that? I cannot confirm the
> problem as a general issue. (Would have been unlikely, that such an issue
> would have gone unnoticed for years.)
Yes this is a general issue. 

See bug 50774 (https://bugs.documentfoundation.org/show_bug.cgi?id=50774). That bug report was opened 2012-06-06. In comment number 8 there the user named Rainer Bielefeld Retired says: "Same effect with AOOo 3.4.1, so seems inherited from OOo.". He also said: "If this is a general problem that is very serious [...]".

Reproduce this bug by making a fresh Writer document. Apply outline numbering to Heading 1. Save as .doc or .docx, exit. Reopen. Apply Heading 1 to some text in the middle of doc. Added chapter gets no outline number. After reapplying outline numbering to 'Heading 1' numbering is wrong (i.e. the headings formatted in this "session" get numbers starting from 1). See uploaded example doc.

Comment on attachment 116892 [details]
Outline numbering gets restarted every time doc is opened

Attached file contains a doc w/ outline numbering applied to Heading 1. Every time the doc is reopened (which I call a "session") and style 'Heading 1' is applied to some text in the middle of the doc, then that heading gets no number. If one reapplies outline numbering to 'Heading 1' then the outline numbering of the text to which 'Heading 1' was applied in this session restarts at 1.

(In reply to meneerjansen00 from comment #69)
> Comment on attachment 116892 [details]
> Outline numbering gets restarted every time doc is opened

bug 76817 -- "Outline Numbering for DOCX not working when new headings inserted in between", and related bug 50774 -- "FILEOPEN DOC/DOCX: automatic numbering in numbered lists different from Word numbering" are both long present import/export filter issues.

Native ODF format of outline numbers are not affected when kept in that format, so while annoying the bugs are not really new nor are they MAB candidates.

Also, no need to attach issue specific files to the Metabugs--attachements belong with the individual issues.

(In reply to V Stuart Foote from comment #70)
> (In reply to meneerjansen00 from comment #69)
> > Comment on attachment 116892 [details]
> > Outline numbering gets restarted every time doc is opened
> 
> bug 76817 -- "Outline Numbering for DOCX not working when new headings
> inserted in between", and related bug 50774 -- "FILEOPEN DOC/DOCX: automatic
> numbering in numbered lists different from Word numbering" are both long
> present import/export filter issues.
> 
> Native ODF format of outline numbers are not affected when kept in that
> format, so while annoying the bugs are not really new nor are they MAB
> candidates.
> 
> Also, no need to attach issue specific files to the Metabugs--attachements
> belong with the individual issues.

I take it then that we do not have to count on (work starting on) a fix for this bug to come anytime soon? That will be quite disappointing for a lot of LO users I'm afraid...

(In reply to meneerjansen00 from comment #71)
> I take it then that we do not have to count on (work starting on) a fix for
> this bug to come anytime soon? That will be quite disappointing for a lot of
> LO users I'm afraid...

Not at all, work on the WW8 import/export filters is continual. For example, if you follow the samples and discussion of bug 50774 there has been noted improvement. 

Otherwise, concise test cases with annotated comparisons in the XML of OOXML and ODF rendering of the sample documents will provide needed incentive to devs for correcting the filters. That as opposed to general statements that it is "not working".

In general, differences in XML structure--in describing styles and direct formatting--is what goes awry with the filter conversion process. Microsoft handles things "differently" in OOXML to the XML LO composes in ODF.  The filters have to resolve the difference--an ongoing development task.  The MS .DOC formats are more robust (and less dynamic), but do also have round trip filter issues--just fewer of them.

Filing useful bug reports aside, a user can put the onus back on Microsoft and export from there as ODF (e.g. .odt), rather than OOXML (e.g. .docx). Or in a more parochial sense work only in LibreOffice rendered ODF--that is what LibreOffice as a project is obliged to support.

(In reply to V Stuart Foote from comment #72)
> (In reply to meneerjansen00 from comment #71)
> > I take it then that we do not have to count on (work starting on) a fix for
> > this bug to come anytime soon? That will be quite disappointing for a lot of
> > LO users I'm afraid...
> 
> Not at all, work on the WW8 import/export filters is continual. For example,
> if you follow the samples and discussion of bug 50774 there has been noted
> improvement. 
> 
I'm afraid I do not see a lot of improvement in that bub. I do see some discussions. But no patch or suggested solution. I'm sorry

> Otherwise, concise test cases with annotated comparisons in the XML of OOXML
> and ODF rendering of the sample documents will provide needed incentive to
> devs for correcting the filters. That as opposed to general statements that
> it is "not working".
> 
I'm afraid you lost me there. I'm willing to do anything youy want me to. But I do not understand what y'all would like me to give. Is the example doc not good enough? Can you not reproduce the bug? Please help me to provide you with the proper testing documents. On a side note, the description in bug 76817 comment #3 is crystal clear to me. And very reproducable. I'm afraid I do not know waht the devs would like more. If I would, I'd provide y'all with what you want in the bug report you want. I'd like to help or provide input, but I really do not know how anymore. Bug 76817 commnent #3 is so clear already...


> Filing useful bug reports aside, a user can put the onus back on Microsoft
> and export from there as ODF (e.g. .odt), rather than OOXML (e.g. .docx). Or
> in a more parochial sense work only in LibreOffice rendered ODF--that is
> what LibreOffice as a project is obliged to support.

In this hard dog eat dog worl I'm afraid the smaller fish has to accept that the bigger fish is boss. Same thing goed for LaTeX (www.latex-project.org) and  any other way to produce documents.

Best regards, Jansen

@V Stuart Foote 

I'm gonna have to read up on the Office Open XML (OOXML) format/file type (which, confusingly to me, is called .docx in LO), the native Word 2007 (and higher Word versions) file format (also called .docx) and ye 'ol .doc format. This is not to be confused w/ the 'open document file' (ODF) format which, I believe, has been used by Libre- and OpenOffice since a long time. Documents in the ODT format have the extension .odT (with the T from Text, not the D for document) which is also confusing to me (I thought that native LO and 'ye 'ol OOo documents ndend in .odF).  

I found a nice article about this: https://brattahlid.wordpress.com/2012/05/08/is-docx-really-an-open-standard/

Sorry for all this off topic stuff by me that really belongs in a chat or support forum. I'm getting old. Back in the days there was only M$ Word (i.e. .doc) and OpenOffice (which I thought saved in the .odf extension).

As for now, what I did to create a document that my Word loving friends can read, edit and save is:
 
1. Open Libre Office.
2. Create new Writer document.
3. Write some text.
4. Choose: File > Save as > Microsoft Word 97/2000/XP/2003 (.doc).
   FYI: I used to choose .doc because I thought that .docx was less 
   well supported in OOo/LO... 
5. Or I choose: File > Save as > Microsoft Word 2007/2010/2013 XML (.docx)

I never even noticed that in LO there's also an option way down at the bottom called "Office Open XML (.docx)". Until today I've never heard of this format. Until today I really couldn't give a rats *ss 'bout M$'s fiddling w/ .doc and .docx format. I just don't care. If people want to use proprietary software and 
operating systems that's their problem, not mine. Boy was I wrong! 

I'll try to create an .docx LO (that is Office Open XML, not Microsoft .docx!) document and I'll test if the outline numbering probelm is also there.

As for me the question remains how MS Word 2007+ handles OOXML .docx files that were created by LO. Does it leave LO's .docx format intact or not? And how does LO handle M$ created .docx files, does the outline numbering bug appear of doesn't it? 

To be continued. Hope y'all will forgive me all the confusion I might have created and the overly long comments that posted here. One is never to old to learn. :-)

1. Reading the blog that I mentioned earlier is highly recommended for all people who have ever used MS Office '97 to 2003! See: https://brattahlid.wordpress.com/2012/05/08/is-docx-really-an-open-standard
It clarifies why there are two ways of saving a document as .docX!

2. Tried to reproduce the bug by making a document in LO and saving it in Office Open OOXML format (i.e. NOT MS's version of OOXML/docX!).

3. Bug still there.

4. When one saves the document in LO's native open document format (ODF, confusingly ending in .odT) bug is not there.

Conclusion: the bug does not have anything to do with Microsoft's crappy implementation of the OOXML standard. The bug has to do w/ the way Libre Office generates a document in the the OPEN document standard OOXML (confusingly also called .docx, not LO's fault, see aforementioned blog).

This bug, strangely enough, probably has nothing to do w/. Microsoft!

Created attachment 116900 [details]
Two documets made w/ LO in OOXML format and re-saved as...

Two test documents. Both made in LO. One is saved as OOXML (LO's version of OOXML, not MS's version!). The other was made in LO, saved as OOXML (it had the bug) and after that saved as .odT which only made the bug disappear after reapplying ALL outline numbered styles. So using .odt as an intermediate when ou receice a Word doc will not work.

(In reply to meneerjansen00 from comment #74)

> To be continued. Hope y'all will forgive me all the confusion I might have
> created and the overly long comments that posted here. One is never to old
> to learn. :-)

No worries, only request is that comments be moved to the affected bug 76817, or bug 50774, and not continue on this meta issue tracker :)

Its just noise here...

Darn it! Posted my last few comments in this MAB instead of the bug report itself! Sorry, sorry, sorry!

(In reply to V Stuart Foote from comment #77)
> (In reply to meneerjansen00 from comment #74)
> 
> > To be continued. Hope y'all will forgive me all the confusion I might have
> > created and the overly long comments that posted here. One is never to old
> > to learn. :-)
> 
> No worries, only request is that comments be moved to the affected bug
> 76817, or bug 50774, and not continue on this meta issue tracker :)
> 
> Its just noise here...

Copied my last few comments to bug 76817. Awfully sorry for all the mixes up and the confusion. A moderator might delete my last few comments here, if possible...

Added Bug 89818 - Long image inserted at the end of page goes beyond margin and over footer

This bug effects NOT ONLY "long" images, but _all images_ embedded in paragraphs near the end of a page.

"Overlapping" images (over footers and/or below pagemargins) make LO completly useless if you plan to put some images in paragraphs. And using images is not an advanced way to style documents, right?!

(Sorry, added this @ MAB4.3 too :/)

Hi all,

The MAB docs on the wiki have been updated to reflect the new
Priority-based system for categorizing bugs:
https://wiki.documentfoundation.org/QA/Most_Annoying_Bugs

The old MAB tracker bugs (mab4.3, mab4.4, etc.) will remain in
Bugzilla for historical reference, but should be ignored for current
work. 

......................

FINAL mab4.4 STATS
......................

fixed bugs -> 52
open bugs  -> 7

......................

for the record, here is the list of the residual open bugs that I'm going to remove from the "Depends on" field: 

Bug 37223: Target for paste cells from column in Calc into TABLE will be single cell instead of column
Bug 57989: EDITING: Writer TABLE does not update sum when adding or deleting row
Bug 83159: DATALOSS: default font size not saved in chart textbox
Bug 84678: FILEOPEN: .DOCX textbox margins incorrectly set in 4.4.x
Bug 86675: Bad-quality antialiasing for PNG images, looks terribly ugly
Bug 86678: TOOLBAR: Underlined letters in new drop downs not working
Bug 88182: Sidebar: Undocked sidebar is an unusable size without resizing, doesn't expand automatically 

I set status to RESOLVED MOVED to reflect the new way to handle Most Annoying Bugs.