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
Add "Bug 48368 - CRASH closing IDE"
Bug 48377 [EDITING] Indicator when dragging a row has changed
Bug 48333 Path changed to <home> (as defined in the users options) with File > Save As, File>Template>Edit, ...
Add bug 48946: Current master build can't find JRE on Windows.
Add "Bug 49291 - CRASH at menu Tools - Macros"
add Bug 49340 - CRASH closing window Edit > Changes > Accept or Reject with ESC
Add "Bug 49808 - FILEOPEN MSO2007 .pptx background missing or wrong color", what makes LibO more or less unusable fro MSO2007.pptx
Add "Bug 50035 - CONFIGURATION: During initialization of Extensions several CRASHes until first launch will be successful"
CC'ing dev list as it seems to be missing
* bug 49806 as it is a pptx import regression in windows
* bug 48243 as it is a regression - sdext/ extensions not work in windows
Add "Bug 50221 - FILESAVE particular .xls (MSO97) will CRASH". Currently only reproducible with 1 document, but might be serious.
Add "Bug 50344 - Basic Macro will not run because of missing Java", it seems that Macro execution is completely broken
Adding bug 50137, LibO close after creating user profile. A recent regression on Windows.
Add "Bug 50679 - EDITING Copying cell(s) with conditional CRASH when paste" - but Markus is already involved, no panic ;-)
Add bug 50783: Can't create database or access table in Base. It makes Base almost unusable.
Add "Bug 50910 - Impossible to access particular spreadsheet based database table"
Add "Bug 50911 - FILEOPEN impossible for any existing.ods"
Add Bug 51040 - Calc crashes if zoom to "Page Width" is used under "Page Preview"
Can you please explain the relation between this bug and Bug 37361 - LibreOffice 3.5 most annoying bugs?
Should unresolved bugs from Bug 37361 at some point (which?) be added here?
This is no place for discussions. If you have a question concerning proceeding ask on <firstname.lastname@example.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!
Add #40907 : concurrent access to AFP shared files impossible - total lock on file
Add "Bug 51231 - UI: Slide thumbnail overlay "start presentation, disable slide, copy slide" position depends on slides pane scroll slider position and mouse way", makes slide pane more or less unusable.
Add "Bug 51278 - Opening Report fails with Error Message", limits usability of Database very much.
Add "Bug 51326 - CRASH when FILESAVE particular document with CHART"
Add "Bug 34467 - FORMATTING Fit to Frame for text boxes is broken" due 2 duplicates
Add "Bug 51368 - EDITING: CRASH when Merge Cells with "move contents" and first of merged Cells is involved in calculation"
Bug 40907 : the bug is very annoying for corporate use on mac network
(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!)
Adding 51324 as it is:
a) a crasher
b) although it is a heisenbug, we have a decent reproduction scenario
c) it disturbs all forms of automated testing
Adding bug 51179 - cannot save as ppt. Because it's a regression, and I think we can't live with this bug.
Bug 51239: very slow base / jdbc / embedded HSQLDB
Add "Bug 51507 - FILEOPEN 3.5 document: conditional formatting of type "Formula is" not recognized correctly, lost after saved", serious problem affecting many users.
Add bug 51547 : make Presenter screen unusable.
Add bug 51143: crash if online update not installed, that may hinder corporate deployments.
Add: "Bug 51555 - FORMATTING Not possible to add Conditional formatting"; basic function, affecting many users
Add <a href="https://bugs.freedesktop.org/show_bug.cgi?id=51554">Bug 51554</a> - linking to external slides in Impress, which can lead to data loss.
Ass "Bug 51582 - EDITING: BACKSPACE in cell with hyphenation will CRASH", crash in plausible scenario.
add bug#51685 - startup component registration / profile compatibility issue.
Add "Bug 45355 - CRASH if characters in text of BENGALI, TIBETAN, MALAYALAM, MARATHI, NEPALI, ORIYA, TAMIL, TELUGU, KHMER", what reappeared from 3.4
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.
bug 51976: Base embedded HSQLDB horribly slow
move 51554 back to 3.5
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.
Added bug 51859, regression in LO 3.6 : in Calc comments are not displayed in the Navigator.
add bug#52152 broken display switching regression.
add bug#52205 apparent CSV import regression.
add bug#51252 - can't start on Windows - missing VS2010 run-time (?)
add bug#51772 - general I/O error loading RTF file, apparently a regression
Add "Bug 49441 - FILEOPEN for multiple documents fails from new File Dialog": Very visible and very annoying for "power users"
Add "Bug 52340 - EDITING: CRASH when Copy+Paste row with conditional formatting to other sheet and back to inserted row"; Crash with often used operation.
Add 51659: Letter Wizard leaves LO in a strange semi-crashed state.
(In reply to comment #48)
> Add "Bug 52340 - EDITING: CRASH when Copy+Paste row with conditional formatting
> to other sheet and back to inserted row"; Crash with often used operation.
Really added :-)
Add "Bug 52399 - EDITING: Report-Builder does not show any properties". Not a blocker, but really annoying for someone who uses Base intensively
nominate bug 52433 : memory leak, crash under XP.
Add "Bug 52447 - FILEOPEN particular .xls: EDITING PIVOTTABLE will CRASH": Regression Crash
Bug 34467 - "FORMATTING Fit to Frame for text boxes is broken" removed here and added to "LibreOffice 3.5 most annoying bugs" (bug 37361) instead, because this bug goes back to LibreOffice 3.3.0.
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.
Add "Bug 52393 - FILEOPEN 3.5.x spreadsheet with wrong row height": Makes CALC nearby completely unusable
Add "Bug 51832 - EDITING: CRASH in special case when 'Edit > Changes > Accept or reject > Reject'"
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)
Add Bug 52612 - FILESAVE [DOCX] Loss of footnotes's text when exporting to DOCX-files (https://bugs.freedesktop.org/show_bug.cgi?id=52612)
Nominating Bug 51620 - Toolbars aspect not consistent, depends on docking place.
OK, it's only cosmetic, but it gives a very bad impression to users.
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!
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.
Add "Bug 53012 - FILEOPEN .csv will CRASH if "fixed width" is preselected", might affect many users.
(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.
Bug 53006 - "Autocorrection TWo INitial CApitals does not work because of bundled extensions problem" added by Rainer Bielefeld.
Added Bug 52639 - "ReportBuilder: Creating a new report destroys .odb" (reproducible according to comment no. 10 there; urgent regresssion).
Added bug 52022 ("My macro's" and imported macro libraries are lost after update from 3.5.5) as this will give a lot of extra work when upgrading a company from 3.5 to 3.6
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 ?
"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.
Ok so I remove 30571
Add "Bug 53252 - UI: CRASH when edit LibO File Dialog Path Pane"
Added bug 52078 - "shlxthdl_x64.dll/shlxthdl.dll causes Windows Explorer to CRASH
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).
Add: "Bug 43489 - [Task] Incorrect behavior using existing User Profile for upgrade" Due to results ESC call 2012-08-09
Please add this long standing bug
Bug 40421 - PRINTING shapes with transparent(?) Bitmap background loses bezier curves
(In reply to comment #75)
> Please add this long standing bug
> Bug 40421 - PRINTING shapes with transparent(?) Bitmap background loses bezier
This bug is already listed as 3.5 MAB => we need not mention it here at these stage.
Nominate bug 53089 : Numbers from external URL are always interpreted as text
It is a regression from LO 3.5 that make Calc unusable to analyze linked external data.
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 #78)
> Nominate bug 53113 (DOCX filter loses shape containing text) and bug 53175
> (Error reading “Content (TOC)” from a DOCX).
You added them to 3.5 MABs, no need to add these bugs here.
Bug 46716 (Some formulas are lost by "DOCX" import filter) reopened as a blocker:
- LibreOffice is frozen now.
added bug 53325 as it appears to be a regression related to calc CSV import improvements in 3.6 series
Added bug 52240 since it's more then annoying. If this is intentional "feature" from LO team, I'm not upgrading any of my 300 users from 3.5.x to 3.6. Also, you can find my comment in connected bug: https://bugs.freedesktop.org/show_bug.cgi?id=52288#c4
added 53325 regression problem: layout of created label/mail-merge documents broken.
(In reply to comment #83)
> added 53325 regression problem: layout of created label/mail-merge documents
for 53325 read 53673...
Add fdo#53399, word count inconsistent and wrong with non-breaking space
1. Since LibO 3.6, live word count statistics are prominently shown in the status line. Showing wrong numbers on the simplest documents makes for a very poor user experience.
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.
(In reply to comment #85)
> Add fdo#53399, word count inconsistent and wrong with non-breaking space
That is bug 53399.
(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).
Adding bug #51550. DATALOSS of embedded OLE objects when saving as .docx, ie. charts, spreadsheets,...
Arrg, depending on bug #51550, not blocking it. Sorry
Can't use Pivot Tables at all since the results are icorrect, so 3.6 is unusable. https://bugs.freedesktop.org/show_bug.cgi?id=53640
(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.
Add: "Bug 54018 - EDITING: CRASH sorting sheet with Comments"
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!
Adding bug 53839 as a dependency. With 3.6 I can't edit a spreadsheet I was able to edit with 3.5--there are crashes when inserting a row and other operations.
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
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).
Add "Bug 53872 - CRASH - opening database report" - Regression
bug 53557, base crasher on any calculated field
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.
Add bug 40594 – Charts embedded in docx are completely absent. It is critical bug for many people.
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
(In reply to comment #103)
> Add bug 40594 – Charts embedded in docx are completely absent. It is critical
> bug for many people.
A good nomination! However, this bug is not new in LibO 3.6.x, therefore I have moved it to our "LibreOffice 3.5 most annyoing bugs" list (bug 37361), where it belongs -- please see http://wiki.documentfoundation.org/Most_Annoying_Bugs
Added bug 53588 : explorer extension causes very annoying freeze on MS-Windows version.
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.
Bug 46271 : Scrollbar unusable on large documents on Mac OS.
Add "Bug 54695 - 188.8.131.52+ FILEOPEN shows all charts anchored to page moved at the top left corner of the sheet", destroys document view. But I doubt that that is critical.
Added fdo#54719 : crash in LO 184.108.40.206 and LO 220.127.116.11+ when deleting a row in a spreadsheet with conditional formatting
Add "54733 - EDITING: CRASH when deleting cell content (of sheet with conditional formatting?)"
Add "Bug 54621 - EDITING: CRASH in .ods documents with lots of (conditional) formatting", we urgently need Markus' arising fix in 3.6.2
Adding 48569 - crash when saving odt as docx under certain circumstances. Document and bt provided.
54827 - FILEOPEN: File open from NTFS Filesystem- crashes Write -version 3.6 ,3..6.1
Really, really, really annoying bug!
Crash upon deleting a particular row results in data loss, plus...just really annoying
Added back bug 54498, which was probably accidentally removed by its original nominator.
Calc is unusable with conditional formats (this concerns numerous files and users)
Still present in version 18.104.22.168
Add "Bug 55043 - No WINDOWS daily builds available for QA". Without daily builds we can not verify fixes.
Windows 7 home premium 32bit on AMD &3Gb RAM
Just installed LO 22.214.171.124 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?
Terry: This bugtracker is a metabug (it's a kind of wrap for other bugs).
Could you file a brand new bug here: https://www.libreoffice.org/get-help/bug/
(help here: http://wiki.documentfoundation.org/BugReport)
(In reply to comment #122)
> Windows 7 home premium 32bit on AMD &3Gb RAM
> Just installed LO 126.96.36.199 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?
I had major problems with this issue, but it is fixed in 3.6.2 RC1
Nominating Calc Bug 55059. Regression.
Nominating bug# 54862: Broken formatting for .DOC files after some on some libreoffice version > 3.5.2 (found on 188.8.131.52)
Affects installations where documents are stored in Word format.
Add "Bug 55379 - FILEOPEN CRASH for particular .ods", at least for me with 3.6.2 loss of access to hundreds of documents.
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.
Add "Bug 55633 - CRASH when FILEOPEN particular .ODS"
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 !
Add bug 55369 Entering fractions results in dates. This feature works fine in 3.5.x but got broken in transition to 3.6.x
I add possible DUPS of Bug 55379:
"Bug 55710 - CRASH FILEOPEN particular .ods with Conditional Formatting"
"Bug 55711 - CRASH FILEOPEN particular .ods with Conditional Formatting"
Adding minor bug 54514 Old icons in Print Preview. Not critical but not beautiful
Add minor bug 55367 wrong convertion factor for "tspm" in function CONVERT_ADD.
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.
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 Bug 50774 with autonumeration (problems in TOC) https://bugs.freedesktop.org/show_bug.cgi?id=50774
(In reply to comment #137)
> Nominating Bug 50774 with autonumeration (problems in TOC)
Agree: really annoying, a killer for academic etc. usage. However, this bug was already in LibO 3.5, so I add it to the “3.5 most annoying bugs” instead (bug 37361). Cf. http://wiki.documentfoundation.org/Most_Annoying_Bugs
Nominating 53924, which is a regression over 3.5.6 in printed output on Mac OSX, also present in master.
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"
may I ask you to follow Romans hints (he created for the 3.7 MAB tracking bugs) on
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.
I add "Bug 53482 - UI: Option 'Range contains column headings' ignored" makes sort useless for many users.
I add "Bug 54748 - EDITING: CONDITIONAL FORMATTING not included in copy-paste cell". Very basic function what does not work
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 :-))
Nominate fdo#53474 [Accessibility] Java Accessibility Bridge not mapping UNO Accessibility roles -- no functional Java based Assistive Technology for Windows builds.
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 56070 - EDITING: Copy / Paste only pastes plain text contents", what makes WRITER more or less unusable (unfortunately currently difficult to reproduce)
Shift from 3.5 MAB to here because 3.5 lifecycle has ended: "Bug 51023 - EDITING: Drag-and-drop slide always moves slide to first position, leading to data corruption and sometimes CRASH"; dataloss risk for Linux and Mac users
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.
I add "Bug 56316 - EDITING: CONDITIONAL FORMATTING not included in copy-paste cell", Dataloss with a very basic editing function,
Add the bug #53070: freeze /hang when FILEOPEN MS Access 2007 or Access '.mdb'
It seems that we somehow screwed up the support for MS Access database. The bug is getting more and more duplicates. It seems to be regression against LO-3.5, see https://bugs.freedesktop.org/show_bug.cgi?id=54454
Add bug #52640: FORMATTING : tabstops malfunction in Draw and Impress
It's a regression from 3.5.x and breaks documents. Has several duplicates. Some users can't use LO-3.6 because of this.
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 would like to add Bug 56325 . It's a regression in 3.6.3 rc1 from 3.6.2.
Added bug 55939 - “FILESAVE RTF export faulty file when text has footnotes”.
This is an important regression introduced in LibreOffice 184.108.40.206 (not present until 220.127.116.11), 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. ;-))
Add bug 56205 "FORMATTING fractions displayed misleading and calculated wrong"
Fractions are mis formatted and therfore misleading.
Add bug 56209 "FILEOPEN: opening a .ods file saved in Excel damages all formula".
Excel files saved as .ods are broken in CALC all formulas show "msoxl=[formula]".
Worked in 3.5.x.
(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.
Nomiting: Bug 42899 - Macro changes not saved on document Close/Save
Huge problem for people who frequently use macros and save document as xls. I have personally lost hours of work due to this one.
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 nominate bug 39066 (Hyperlinks are missing after closing): in Draw, hyperlinks set on image are lost after reopening the file.
adding bug 56278
EDITING: Calculate formula: DEl or BS to empty a cell with a formula, does not result in updating a formula referencing that cell
maybe should have done that earlier. sorry
Added Bug 55032 - FORMATTING: Conditional formatting lost when sheets are copied
As this prevents copying any sheets with conditional formatting and prevents me from upgrading.
Add 50430: Can't Open/Save in UOP format
The UOP file format import/export seems to be completely broken. We should either fix it or disable it at all.
Add 57203 :
LibO 18.104.22.168 is a great release but cannot be automated by Automation compatible script languages (VBScript, Ruby, ...) as the OLE bridge is broken.
I nominate bug 57311 : LO 22.214.171.124 is named LOdev instead of LibreOffice on Linux / Deb x86
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.
Nominating bug 48039: Cross-references disrupted in Master Document. It destroys cross references in subdocuments.
(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
* 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 ...)
57698 is a REALLY ANNOYING bug that makes it infuriating to edit two documents at the same time.
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.
Added 56939, where LibreOffice doesn't remember the last folder opened, making it really hard to edit all the files in a folder one by one.
Added 35669, which has been around for 8 years, and incorrectly marked fixed. Cross references in chaptered documents don't work.
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.
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 126.96.36.199
I add "Bug 57176 - EDITING: CONDITIONAL FORMATTING not restored by UNDO" because of dataloss
Nominating Bug 58278 - FORMATTING: Crash applying AutoCorrect. Crash and Retrogression in common functionality.
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.
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 188.8.131.52.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).
Please, look at the bug 47838, https://bugs.freedesktop.org/show_bug.cgi?id=47838
It's one of the oldest bugs (from early releases of the OO.org). Can anybody fix it? It is really annoying - all new releases of the LO with it stops many people from using LobreOffice and Writer in particular.
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.
May I suggest to add bug 58893 ?
[crash] filopen master document with linked template modified
because libo crash and it is a regression from libo 3.5.7
as "silent give consent", I've raised this bug
[crash] filopen master document with linked template modified
it's a regression against 3.5.7
the only workaround is to let libreoffice crash and restart libo (one time on loop)
Added - missing jump-list in Windows 7 - apparently a rather annoying regression.
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
Nominating Bug 52159 https://bugs.freedesktop.org/show_bug.cgi?id=52159
Error bars of charts, when copied from Calc and pasted into Writer, loses the correct values for error bars, and become the same as Y-values.
This bug appeared only in 3.6. Was not present in 3.5.
Nominate bug 33281, vertical text not exported properly in PDF. Filed in 2011.
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.
I apologize. Is there a way to withdraw it, then?
I nominate "Bug 60549 - Pictures not saved to .pptx" to this list because it's critical to save/don't lose a picture in a presentation.
This bug causes data loss (notices of entire tabsheets get lost) and is extremely annoying as the damage is only noted when reopening the calc document.
Added Bug 61186 as our printer settings (file - printer settings) are essentially a useless set of options until this is fixed
I add "Bug 61339 - FILEOPEN LibO 3572 .ods: CONDITIONAL FORMATTING type 'if cell value' without style type, UI Localization related", serious Version Interoperability issue
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.
I nominate "Bug 55715 - FILESAVE: Writer creates corrupt docx when a chart is copied from calc" because this is a common used function and results in data loss.
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).
(In reply to comment #208)
> 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).
RESOLVED NOTABUG. Autocorrect feature defaults have 1/4, 1/2 and 3/4 replacements with corresponding fraction character from fontset. Autocorrect is immediately reverted with <Ctl>-Z
Alternative entry using correct date format of 03/04/13 avoids autocorrect. Or, autocorrect replacement can be eliminated by deletion of 1/4, 1/2, 3/4 entries in the Replace tab.
Possible UX enhancement to change Autocorrect function for date formatted fields, but not a MAB.
Adding Bug 38619 - Picture of type wmf is not printed correctly because it's really old, from 3.4.1, and, while not maybe common case because limited to printing WMF from Windows, still annoying.
I nominate "Bug 46553" Update embedded manifest on win32 builds to declare dpiAware
"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.
As discussed on IRC with jmadero adding #49853 to MAB. It affects many people, have several duplicates and 27 subscribers.
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.
Added 62073 - copy/paste of a line in impress results in a change in size for bullets, ctrl + z doesn't undo the changed bullet size -- common feature, prevents high quality work
Adding back bug 62073 which was accidentally removed right after nomination.
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.
scaling of images no longer working in 3.6 - appears to have been introduced either in 3.5.7 or 3.6.0.
Makes pdf export with scaled images useless
Adding back bug 55345 which was accidentally removed right after nomination.
Added Bug 63647
Really simple test case provided - export as a pdf and the document is useless (calc table is zoomed way into the corner, probably 1000% plus).
Bug 49840 - XLSX FILEOPEN Text in cells is lost
Renders spreadsheet documents completely useless.
(In reply to comment #221)
> Bug 49840 - XLSX FILEOPEN Text in cells is lost
> Renders spreadsheet documents completely useless.
The document is invalid according to the OOXML spec.
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.
Nominated 64753 - document/sheet protection is completely lost with .xlsx format which seems to be quite bad. Works fine for xls and of course ods formats
I move here Bug 46060 - Writer corrupts DOCX file containing TOC, recovery not possible with Office 2010 - from MAB 4.0.
I would like to nominate Bug #34957 - "table in Writer behaves strange when set option Keep with next paragraph" because it is a long standing bug and makes some of my documents look ugly!
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
I nominate "Bug 49708 - EDITING FILESAVE Setting primary key was silently ignored" because :
- the possibility to add a primary key via UI is indeed broken
- there's no error message
- it's quite an old bug
If it's too much broken perhaps it would be better to remove this option completely.
propose remove: bug#58819 it looks like a reasonably normal interop. problem - arguably data-loss, but export to OOXML has plenty of similar issues; pending Miklos' input.
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?
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
I'm adding Bug 58577 because it caused my text frame lost when I save as OOXML (*.docx). It is a BLOCKER!
For Bug 56960, patch is out for LibreOffice 4.1, but not in LibreOffice 3.6 list.
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!
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?
(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:
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:
> 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.
outdated install instructions: website
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.
All still open 3.6 MABs have been moved to the 4.0 MAB list since the 3.6 branch reached is end of life (EOL).
changing status to CLOSED FIXED.
INCREDIBLE WORK Tommy - really we can all learn from your commitment to this project. I hate to speak for everyone but from all of QA and I'm sure all of us contributors outside of QA, THANK YOU
The MAB docs on the wiki have been updated to reflect the new
Priority-based system for categorizing bugs:
The old MAB tracker bugs (mab4.3, mab4.4, etc.) will remain in
Bugzilla for historical reference, but should be ignored for current
FINAL mab3.6 STATS
fixed bugs -> 157
open bugs -> 0