This is the Meta issue to track most annoying bugs for the release of
LibreOffice 3.6.x releases. It helps developers to concentrate on bugs that are important for users. Also it helps users to be aware of potential problems.
If anyone wants to raise an Bug for the release, please add the Bug ID as
dependent Bug here to the Meta Bug in field "Depends on". Additionally please
leave a comment here why you think that the bug should be privileged.
See also http://wiki.documentfoundation.org/Release_Criteria
and http://wiki.documentfoundation.org/ReleasePlan

@Timur:
This is no place for discussions. If you have a question concerning proceeding ask on <libreoffice-qa@lists.freedesktop.org>!
Short answer here: This is for MAB what can't be fixed in 3.5, but please shift NO bug between these tracking Bugs. Anything else in Mailing list!

(In reply to comment #26)
> Bug 40907 : the bug is very annoying for corporate use on mac network
I agree completely. However, bug 40907 is already included in our "LibreOffice 3.5 most annoying bugs" list (bug 37361), and this is sufficient and adaequate. At the moment, the present (3.6) bugs list should contain only bugs which are *new* in LibreOffice 3.6. If bug 40907 will not be resolved during the 3.5 maintenance phase, we will move it, just like all remaining (open) 3.5 bugs, to this (3.6) bug list, so there really is no need to include a bug in both lists.
(No offence -- this is just an attempt to explain our current practice for anybody who does not know it yet!)

Add "Bug 51943 - text color setting is broken". A wonderful regression which would make all users (and especially our friends at Microsoft and AOO) laugh about LibreOffice -- so this needs to be fixed before 3.6 goes final.
At the moment only documented for MacOS X; could someone else please test on Linux and Windows? But even if this bug occurs only on MacOS X, it is very important to fix it, just because it is so simple and ridiculous.

Add bug 52028 - "Writer 3.6 creates and applies empty automatic styles everywhere, leading to needless file complexity and size".
I don't know why nobody tries to confirm (or disprove) this bug, maybe my explanation is just too lengthy ;-), but if this bug is reproducible (even if it is just partially reproducible), this is an important regression which needs to get fixed soon.

Bug 52433 -- "writer memory eater file leading to crash (images related)" -- is alreay reproducible in LibreOffice 3.5.x and also listed on the "LibreOffice 3.5 most annoying bugs" list (bug 37361). Therefore removed it from the present list, which is about 3.6; a bug should be included only in one of our "most annoying bugs" lists, that is to say, in the best fitting one.

Adding bug 52615; component database; the ADO driver is inactive. This is especially annoying since that's how we "automagically" connect to MS Access databases -> a non-expert user cannot connect to an MS Access database (connecting through ODBC works, but this takes expert setup, while connecting through ADO is setup automatically by LibreOffice).

(In reply to comment #58)
> Add Bug 52610 - FILESAVE [DOCX] File.docx, created LibO Writer, can't be opened
> in other programs (https://bugs.freedesktop.org/show_bug.cgi?id=52610)
(In reply to comment #59)
> Add Bug 52612 - FILESAVE [DOCX] Loss of footnotes's text when exporting to
> DOCX-files (https://bugs.freedesktop.org/show_bug.cgi?id=52612)
Both bugs have been nominated, but not acutally added to the "Depends on" list, and this is good so -- because none of the two bugs is new in LibO 3.6.x, and for now only bugs new in 3.6.x should be added to the present list. So, if someone still considers one or both of these bugs as "most annoying", he/she should please add it to our "LibO 3.5 most annoying bugs" list, but not here. Thanks!

(In reply to comment #63)
> Nominating bug 52998 and bug 52999: Saving file as XLS/XLSX lost comments.
> These are regressions in 3.6 version, and IMHO we need public caution for these
> bugs if we release 3.6.0 with them. Thanks.
IMHO good nominations (regressions with data loss), therefore actually added.

Added bug 30571 ("Some items in vertical toolbar unusable")
It's a very old bug and this one must be quite annoying for those who prefer vertical toolbars.
devs: any hint where to begin to chase this one ?

Comment 70Don't use this account, use tml@iki.fi
2012-08-07 05:00:50 UTC

"must be quite annoying for those"? So you don't find it annoying yourself, and haven't heard explicitly from anybody finding it very annoying? I am not sure if it is a good idea to start guessing here. Surely one could say that *all* bugs are annoying for somebody if they bothered to report a bug? If a bug in some non-default user interface configuration behaviour is very old, surely people have learned to live with it by now, and/or not even bother trying to use that configuration? Just shows once more that too any options is bad.

Added bug 52078 - "shlxthdl_x64.dll/shlxthdl.dll causes Windows Explorer to CRASH
repeatedly".
This bug is especially annoying, because it causes *repeated* Windows Explorer crashes -- under certain circumstances, you can get into a nice crash loop which can get stopped only by complicated actions (see e.g. comment no. 15 in that bug report and the description in the dupliacte bug 52276).

Nominate bug 53113 (DOCX filter loses shape containing text) and bug 53175 (Error reading “Content (TOC)” from a DOCX).
These bugs are not regression but they make unusable re-import OOXML text documents (DOCX, ISO) by Writer. As result we need to use Microsoft Office for this purpose.

(In reply to comment #85)
> 2. Educational users (students etc.) might have to obey hard limits on the
> number of words in documents they write. LibreOffice's wrong numbers might get
> trustful users into inconvenient situations.
I ought to support this. At the first glance, correct or incorrect word count seems to be a minor issue. But in the academic (and probably also in the journalistic?!) world word count is an extremely important entity, sometimes of vital importance ("Yes, your essay was very very good, but it was three words too long, so you can only get a C grade ..."). So, bug 53399 is really important.

Supplement: bfoman has added bug 49102 -- "Writer: Incorrect numbering when cells are merged in the table", still waiting for confirmation. This is a LibO 3.5.x bug which went wrong in LibO 3.6.x (maybe it would be better if there were two separate bug reports, one for the 3.5.x problem and one for the additional 3.6.x regression).

(In reply to comment #88)
> Supplement: bfoman has added bug 49102 -- "Writer: Incorrect numbering when
> cells are merged in the table", still waiting for confirmation. This is a LibO
> 3.5.x bug which went wrong in LibO 3.6.x ...
Obviously the weather is too hot in these days, it has totally evaporated my knowledge of English grammar; sorry! Please read:
This is a LibO 3.5. bug which _went_ _worse_ in LibO 3.6.x ...
And bug 49102 is confirmed now, of course.

Added bug 54023 -- CRASH on launch when loading local libiconv.2.dylib ("liblangtag.0.dylib requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0")
I can’t confirm this bug at the moment (download problems), but if it is reproducible (and there is little doubt that it will be), this is a blocker, because it makes testing the master build impossible.
Does somebody know which developer knows best about liblangtag, and therefore should be CC’ed about this bug?

(In reply to comment #94)
> Added bug 54023 -- CRASH on launch when loading local libiconv.2.dylib
> ("liblangtag.0.dylib requires version 8.0.0 or later, but libiconv.2.dylib
> provides version 7.0")
Oh no -- sorry -- how stupid by me! From the first bugs on this list, I am still used to the expectation that also bugs from the newest master builds should be added to this list. But now that 3.6 is released, the master is 3.7alpha0, and therefore bugs in the master builds like bug 54023 should _not_ be added anymore to this list ...
Remove bug 54023 again. Sorry again!

I would like to nominate the nasty Bug 51023. It is already a 3.5 most annoying bug, but should be a 3.6 most annoying bug:
Bug 51023 EDITING: Drag-and-drop slide always moves slide to first position, leading to data corruption and sometimes CRASH

(In reply to comment #97)
> I would like to nominate the nasty Bug 51023. It is already a 3.5 most annoying
> bug, but should be a 3.6 most annoying bug:
Sorry, but you don’t need to add that bug to the this list if the bug is already a “LibreOffice 3.5 most annoying bugs”. As long as LibreOffice 3.5 is maintained actively, only bugs new in LibreOffice 3.6 should be added to this (3.6) list; but all bugs which have been inherited from previous versions (3.3, 3.4, 3.5) should be added only to the “LibreOffice 3.5 most annoying bugs” list -- see
https://wiki.documentfoundation.org/Most_Annoying_Bugs
Entering a bug into both lists does not help fixing it, it just makes it more difficult to keep track of the most annoying bugs.
Thank you very much for your understanding!

As already mentioned in 53341, adding it because it makes the dpkg status database invalid, which other Debian utilities (rightfully) complain about, and the fix is likely somewhat trivial (though potentially not uninvasive).

Bug 45893 CHART printing directly is amissing feature which is included in Excel and in Lotus 123 for around 20 years. The workaround to export the chart to PDF and then print from there is working but a total mess and waste of time to get it right ( changing page properties, changing chart window and alot trial and error).

(In reply to comment #104)
> Bug 45893 CHART printing directly is amissing feature which is included in
> Excel and in Lotus 123 for around 20 years. The workaround to export the chart
> to PDF and then print from there is working but a total mess and waste of time
> to get it right ( changing page properties, changing chart window and alot
> trial and error).
Sorry, but this report is already on the "LibreOffice 3.5 most annoying bugs" list (bug 37361), therefore it should not be added here -- see
http://wiki.documentfoundation.org/Most_Annoying_Bugs

Added bug 54398 - DOC files created in LO lose drawings after field update in MS Word 2007.
This bug causes a lot problems in common work with MS Office users, because all drawings are deleted from such .doc files.

I added Bug 54259 - FILESAVE: When saving in MSWord doc format, some table cells unmerged so data not shown properly. It seems that this started in 3.6. We are affected also on our memo, so it's highly visible.

Windows 7 home premium 32bit on AMD &3Gb RAM
Just installed LO 3.6.1.2 and ALWAYS get a crash just pointing at a .ODF file on my desktop.
Cannot delete as crash is too quick!
Had 3.5 before with no problems.
Not good for LO!
update. Deleted 3.6 & re-installed 3.5, problem gone. So no 3.6 for me or my company then?
Regards
Terry

(In reply to comment #122)
> Windows 7 home premium 32bit on AMD &3Gb RAM
>
> Just installed LO 3.6.1.2 and ALWAYS get a crash just pointing at a .ODF file
> on my desktop.
> Cannot delete as crash is too quick!
> Had 3.5 before with no problems.
> Not good for LO!
>
> update. Deleted 3.6 & re-installed 3.5, problem gone. So no 3.6 for me or my
> company then?
>
> Regards
>
> Terry
I had major problems with this issue, but it is fixed in 3.6.2 RC1
Dave

Is there a chance to consider :
"Bug 47662 - EDITING: Inconsistent / unintuitive reference link handling for check boxes and other form fields when Copying Sheets" for 3.6 ?
and "Bug 51756 - scrollbars display differently when editing vs "print preview" vs when actually printed" as there is no workaround to have a correct print of srollbar.
thanks

Add "bug 54552 EDITING: Cell used in a formula is considered non-empty"
This bug could seem minor in the interface (user's keystroke <Ctrl><End>
and the cursor can go "further" than the last input cell) but IMHO it is
very inconvenient for applications : many (most) of them use
the gotoEndOfUsedArea method whose result is not the same !

nominating fdo#49277
https://bugs.freedesktop.org/show_bug.cgi?id=49277
Could potentially cause a huge headache for a user trying to make a professional quality presentation. Error only shows when you close a document and reopen it -- making chance of accidentally showing poor quality work quite high.

Looking here, I see a load of not-really-most-annoying bugs diluting the impact of this issue - in particular the dependencies of:
> bug 48741 – container issue for Page styles/formatting header and footer
> These bugs cause wrong import of documents with simplest formatting and
> seems to be easy to fix.
cf. https://bugs.freedesktop.org/showdependencytree.cgi?id=44446&hide_resolved=1
Are often unsuitable; eg. bug#44941, bug#33304, bug#47838 etc. On the other hand some of those tracked issues are MABs. To encourage people to re-nominate the MABs out of that list, I'll drop bug#48741 and ask people to re-add a few suitably critical / blocker / really-most-annoying issues back. Hope that's ok.
Really missing Petr's editorial role here :-)

Nominating fdo#54898 as MAB since:
- it's a regression from 3.5
- it has been reproduced at least twice (fdo#54898 + its dup 55625)
- it's stealth (no error message or something) and we can't trust results of Data Pilot for the moment

Really added Bug 54898
for the records, latest "nominations" were
"Bug 54898 - : sum error with hours in Pivot Table (AKA Data Pilot)"
"Bug 53924 - FORMATTING: PRINTING changes text (space get's removed) on OS X 10.7/10.8"
@all:
may I ask you to follow Romans hints (he created for the 3.7 MAB tracking bugs) on
<http://wiki.documentfoundation.org/Most_Annoying_Bugs>,
what would help to use these tracking Bugs more effective?
That especially means:
Please always Copy / Paste the complete summary of the "nominated" bug to your comment in the MAB tracking bug. So aAll in CC, especially Developers and QA staff on lists, see immediately concerning what that problem that bug is. Some "fdo#xyz" is not useful because in the Bugzilla Daemon mails nobody can see Concerning what problem the new bug is, he has to visit the bug, and that's some work, because neither in mail nor in comment a link will be created.
Thank you!

nominating bug 48056.
Reasoning, as per http://wiki.documentfoundation.org/Release_Criteria:
- The bug renders a function completely unusable, namely reports with charts.
- bug is certainly reproducible by a lot of users, seeing the confirmations
in the bug itself, and the duplicates
- The bug is a regression to the 3.4.x series
- There is no workaroundd at all: If you want to use your reports, you need
to revert to an older version of LO.

(In reply to comment #144)
> nominating bug 48056.
> - The bug is a regression to the 3.4.x series
> - There is no workaroundd at all: If you want to use your reports, you need
> to revert to an older version of LO.
Can I put a big like on this ? Hi Frank, good to see you around :-))
Alex

Add "Bug 56068 - EDITING: Paste Special for copy of cell with formula unavailable, only plain text pasted", what makes creation of new spreadsheets very annoying. Currently unfortuntately difficult to reproduce!

Add Bug 47838 - Writer causes extra page-crossing (text flow to next page) in some MS Office documents - related with header/footer and page formatting.
It is very annoying bug: Writer adds footers or headers on pages that do not have it => length of the document changes.

Added bug 55939 - “FILESAVE RTF export faulty file when text has footnotes”.
This is an important regression introduced in LibreOffice 3.5.6.1 (not present until 3.5.5.3), and also affecting all 3.6.x and Master builds. It makes it *impossible* to save any Writer file containing any footnotes in RTF format, because the RTF file will be corrupted (non-matching braces).
I add the bug to this (3.6 MAB) list, and not to the 3.5 MAB list (bug 37361), because AFAIK the 3.5 MAB list is more or less closed now. (No more 3.5.x releases are planned officially, even if it is possible that there will be a 3.5.8 release. IMHO this bug, being a regression *during* the 3.5.x release cycle,
would be one more good reason to actually release a 3.5.8 version, just to fix such late regressions. ;-))

(In reply to comment #154)
> I would like to nominate Bug #42134 "FORMATTING: Autofit doesn't work
> properly on long texts" as a most annoying bug, it has been around since
> version 3.3 and I would not think it is too hard to fix?
I agree that it is annoying but I do not thing that it belongs here. It is a very old bug and I do not see other duplicates. I think that it is because many other users do not use so long texts. Note that long texts are not ideal for presentations anyway.

I nominate bug 46410 (EDITING: Alphabetical index with concordance file) : creating a lexical index with concordance file does not work anymore. There is several duplicates of this bug.Very annoying for scientific writing.

I add "Bug 55618 - LOCALHELP: obsolete for CALC Conditional Formatting": new CF features cause a lot of trouble on mailing lists and also Bugzilla, it's too difficult to understand how it works with obsolete Help.

(In reply to comment #169)
> Nominating bug 48039: Cross-references disrupted in Master Document. It
> destroys cross references in subdocuments.
A good nomination, however -- this is already a “Most Annoying Bug”: it is included in the “LibreOffice 3.5 Most Annoying Bugs” list (bug 37361). We include a bug only in the oldest applicable (and open) most annoying bugs list, plese see http://wiki.documentfoundation.org/Most_Annoying_Bugs for details ...

(In reply to comment #170)
> (In reply to comment #169)
> > Nominating bug 48039: Cross-references disrupted in Master Document. It
> > destroys cross references in subdocuments.
>
> A good nomination, however -- this is already a “Most Annoying Bug”: it is
> included in the “LibreOffice 3.5 Most Annoying Bugs” list (bug 37361). We
> include a bug only in the oldest applicable (and open) most annoying bugs
> list, plese see http://wiki.documentfoundation.org/Most_Annoying_Bugs for
> details ...
Oops, I'm sorry, I checked first also 3.5 bugtracker, but I did it wrong :-/ and I didnt see that 48039 was blocking 37361.

For the record: Norbert Scheibner has added
* Bug 56742 - “conditional formatings got lost in copyed spreadsheet
after fileclose”
* Bug 40788 - “FORMATTING - Calc ignores manual breaks when ‘fit to number
of pages’ is chosen”
I have removed bug 40788 here again, because it is already included in the “LibreOffice 3.5 most annyoing bugs” list. Of course, we will close the 3.5 MAB soon, but nevertheless a bug should never be included in more than one MAB list, see http://wiki.documentfoundation.org/Most_Annoying_Bugs ...
@ Norber Scheibner:
Thank you for nominations, but please *always* add a comment citing the bug summaries when you add bugs to a MAB list.

For the record: Steve Kelem has added
Bug 50057 - “EDITING: Replication of frames when record changes (redlining) is on”
Definitely a good nomination. (Should be in the 3.5 MAB bugs list, of course,
but at least it is not duplicated = in both MAB lists, as the previous entries where, so let it stay here, because we will finally close the 3.5 list ...)

Added 40465, to fix zoom so that it stays on the same page when multiple pages are shown at the same time. Currently, zoom out to two pages jumps to something like the current page number divided by 2 instead of showing the current page and the preceding or following page. Zoom into page #/2 is not where the user wants to go.

57710 is one that's had me frustrated for years! I have to write PDFs for chapters in a document I'm working on many times a week. The option mentioned, when turned off because, reading the text of the option, it might make sense to do so, results in the wrong pages being output with no idea of why it's happening.

Hi Steve; please hold off adding more bugs (added six in one day) until we can get some independent assessment of the ones you have already added - being annoying to you is bad of course; but I'd like some independent review of these. Bloating this bug's dependencies does no-one any favours and can obscure the most severe issues (which yours may be - I don't know - they need review). Thanks for your work in bugzilla !

Sorry to overwhelm you. I happened across the MAB for the first time and thought "What a great way to get some old issues resolved and some long-standing ones that I need to generate a test case for, else no one would believe me!" So, I spent time to create test cases for the bugs that are annoying because they're keeping me from being productive.
By the way, I saw some of the entries here removing bugs from 3.6.x MAB because they are in the 3.5.x MAB. If 3.5.x is "old" and an annoying bug for 3.5 is still a problem in 3.6, what's the procedure for making sure the outstanding bugs, especially the MABs, are still addressed?

3.5 MAB are still being addressed, the procedure is that these bugs are highlighted for the developers but with the vast amount of bugs, enhancements, etc... being done all the time, some MAB get "brought over" to the new version (for instance some 3.5 bugs may come over to 3.6 bugs but that isn't happening yet). Furthermore, it is at the discretion of the developers which MAB comes first -- how old a bug is isn't the main criteria in most cases, it's really how annoying the bug is for the most amount of people coupled with what developer(s) know that part of the code enough to tackle the issue.
The other issue is that some MAB are not in fact MAB and were put there without independent review (this is a requirement for MAB's amongst other requirements). These bugs may be taken off the MAB list at some point but our developers are working hard on fixing bugs that have already been independently verified to be a MAB for many users. Most of the times this means a major feature of LibO isn't working properly, and can often include crashes, memory leaks, etc....
If you want to get more involved with how policies are made and help us continue to make LibO better, please join us over at QA, we always welcome a fresh opinion.

Added
https://bugs.freedesktop.org/show_bug.cgi?id=55842
no focus on frame outside of page margins for editing
Choosing of frames in letters, for example address in a frame outside the content of the letter, is impossible with the mouse since LO 3.6.2.2

Nominate Bug 48409 - Impossible to use Writer OLE object due to unstable placement (Impress, Calc, Draw)
This _regression_ bug began from 3.4.* and it completely blocks the possibility of editing Writer OLE objects and inserting new one. Completely means I have to use LO 3.3.4 to edit them.

Hello,
LibreOffice 3.5.7 has been released and announced as the possible last revision of 3.5.x branch.
Since there will be no more correction of bugs in 3.5.x branch, it is time to move LibreOffice 3.5 most annoying bugs and to add them to this list, at least those which have been tested and reported to be still present with 3.6.x releases.
I would specially nominate bug 52433, "Writer memory leak crash", which has been present since 3.5.0 to 3.6.4 and prevents the use of LibreOffice as soon as you add images to a writer file.

(In reply to comment #186)
> Since there will be no more correction of bugs in 3.5.x branch, it is time
> to move LibreOffice 3.5 most annoying bugs and to add them to this list, at
> least those which have been tested and reported to be still present with
> 3.6.x releases.
Thank you for your hint! But AFAIK this movement of all remaining important bugs from the 3.5 MAB list to the 3.6 MAB list is already on its way; especially Rainer Bielefeld has already judged and moved many bugs, and others (including myself) have done similar things. It will just take some time to complete this task, because (a) it should be done carefully, (b) probably by experienced bug wranglers, and (c) most of our QA volunteers are occupied with testing the upcoming version 4.0.0; which is a much more urgent task right now ...

Added 54275: this bug prevents Ubuntu Linux users (not confirmed for other distros) to be able to save documents to mounted gvfs samba shares (when navigating via nautilus sidebar menu).
Seems very critical for a network situation. 3.5.x does not have this issue. Workaround to manually navigate to mountpoint will not be known to many users.

(In reply to comment #188)
> Added 54275: this bug prevents Ubuntu Linux users (not confirmed for other
> distros) to be able to save documents to mounted gvfs samba shares (when
> navigating via nautilus sidebar menu).
>
Confirmed bug 54275 still present in Linux 64 bit Version 4.0.0.0.beta2 (Build ID: 4104d660979c57e1160b5135634f732918460a0).
Again, problem is that a user is unable to save a NEW document to a samba share in Linux (am able to open and modify and save existing documents).

I add "Bug 54264 - FILEOPEN: LO cannot open more than one file at a time from Mac Finder" because of the regression with 3.5 branch. It's quite annoying when you need to open all files one by one, when you try to open multiple documents at once.

Nominating bug 58283 (LibO descriptions untranslated in application menu), as it means that many Linux users get LibO app descriptions (plus Unity's "New Document/Spreadsheet/...") in their menu in English, even if they use localized desktop.

Add "Bug 37960 - Shift click to select multiple drawings does not work if picture there" because:
- Not in mab3.5
- Has been around since 3.4.0 release
- Importance: "high - major"
- Very basic editing action is broken

Also nominate bug 55946, LO cannot properly read .docx cover pages. A good number of Word documents out there use cover pages, and LibreOffice needs to be able to display Word documents correctly to be at its best.

(In reply to comment #199)
> Also nominate bug 55946, LO cannot properly read .docx cover pages. A good
> number of Word documents out there use cover pages, and LibreOffice needs to
> be able to display Word documents correctly to be at its best.
It is one of more features that are missing in the import/export filters. Only one person is currently interested into this bug. SO, I would prefer to leave it out of MABs. Instread, I added Writer developers into CC, so they are aware of it.

Nominating bug 55814: condition for hidden section gets lost
This is an often used functionality in templates, which should be available in the actual LibO version for productive use. Therefore I ask for fixing this in LibO 3.6.x.

Bug 61903 - FORMATTING: entering 3/4/13 into a date formatted cell is changed to fraction 3/4 and /13
This bug prevents typing in a date as 3/4/13 changes to ¾/13 (three-quarters sign then /13 - happens as soon as the second forward slash is entered).

I nominate "Bug 46553" Update embedded manifest on win32 builds to declare dpiAware
and
"Bug 46817" Screen font anti-aliasing does not work (Windows)
They are causing inferior rendering quality of GUI and user content on Windows.

[Bug 44621] With MacOSX 10.7 and later, dragging an image from the desktop to LO Writer is not possible
This is a bug so prominent that probably every single LO on Mac OS >= 10.7 user has come across and been annoyed by it. And remember that Mac folks tend to be less technical, so the fraction of Mac users creating a bugzilla account when bothered by a bug is going to be smaller than the corresponding fraction of Windows and Linux users.

Bug 44617 causes irreversible problems (undo doesn't work) when resizing a group of shapes that use the "resize shape to fit text" option. While Drawing is not the most used function in LibreOffice, a bug causing irreversible damage to a document should be corrected in a stable version.

I would like to nominate bug 40489 "PRINTING: Option Buttons and Check Boxes not printed correctly" because documents with check boxes are common in a business context and it is important that the user can TRUST LibreOffice to print documents as displayed (and not printing only half of the check boxes).
The bug exists since 2011 and (compared to OpenOffice) it is a regression.

There are many bug reports for images in .docx. I move here Bug 52226 from MAB 4.0. I'd like also to add Bug 43641 - Image in .docx file not shown reported in 2011. Some may be duplicate, but hopefully this will at least be resolved.

external links to another sheet seem to be changing to a default folder with xls files.
Nominated: 57738 - at least 3 bugs reported against this issue, sum, indirect and another function affected. Results in unusable sheets

LibreCalc Bug 39936 - it has always been unnecessarily cumbersome to move rows around. Excel has a context menu option called "Insert cut cells", which I miss dearly in LibreCalc.
PS: is 3.6 still being developed? Should these bugs move to 4.x?

@Dan Dascalescu
it's not time yet to change the mab3.6 status to FIXED, so I'm REOPENING.
LibO 3.6.x is still under development, though is close to the end of life.
see here the release plan: https://wiki.documentfoundation.org/ReleasePlan/3.6#3.6.7_release
the last 3.6.7 release will come out in a few weeks, then after that, all the remaining 3.6.x MABs which are still reproducible on 4.0.x versions will be moved by the QA guys to the mab4.0 page

Bug 51453: "Equation Frame size linked to caption frame size" should be added to the list. If you have a caption that's wider than your "formula", either the caption is wrapped (possibly over several lines) to match the width of the formula or the formula is scaled to match the width of the frame containing the formula and the caption. Both of those options look horrible and there is no good workaround!
http://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=7949 shows an example of this bug.
This bug was filed in 2005!

(In reply to comment #235)
> About my last post about 51453...it's an annoying bug, but it's listed
> against OpenOffice at the Apache site:
> https://issues.apache.org/ooo/show_bug.cgi?id=51453
Happens to all of us who follow both projects ;-)
>
> It still applies to LibreOffice. What's the right way to get this fixed?
Just did a search, it has not been raised as an issue on the LibreOffice side.
So for starters, need a substantive write-up of the issue. The AOO issue #i51453# is a start, but you'll note it has had no substantive attention since 2005. As to being/becomming a Most Annoying Bug--that will depend on your write up and justification on use of a caption with an inserted formula object. Actually seems more a UX issue to me.
Anyhow, please make you steps to reproduce the observed behavior simple but complete.

(In reply to comment #235)
> About my last post about 51453...it's an annoying bug, but it's listed
> against OpenOffice at the Apache site:
> https://issues.apache.org/ooo/show_bug.cgi?id=51453
>
> It still applies to LibreOffice. What's the right way to get this fixed?
First, thanks for bringing up this problem. Please, open bug against LibreOffice in the FreeDesktop bugzilla and mention there links to original bug report. A simple link would be enough but it might speed up the things if you provide a test document and simple steps how to reproduce it.
Otherwise, I would prefer to handle this problem as a normal but. I understand that it is annoying for certain people but there are many other bugs that affect more people and are even more annoying. I think that this one does not qualify for the top priority queue.

LibO 3.6.7 is out and will be the last release of the 3.6.x branch.
all the unfixed mab3.6 are actually under review before being moved to the mab4.0 page.
so, please don't add new bugs to the current meta-bug.

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 mab3.6 STATS
......................
fixed bugs -> 157
open bugs -> 0
......................