This is the Meta issue to track most annoying bugs for the release of LibreOffice 3.5.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
My be one of next bugs: Bug 34436 - TABLES text in cells behaves wrong when rotated (annoys when opening documents in doc format, there rotated text has no restrictions) Bug 34451 - Appearing docked Toolbars cause document jumping on screen (distorts attention, slows down work) Bug 34559 - Complex Dialogs should be resizable (dialogs takes only small part on contemporary displays, and if dialog contains much information, it seriously slows down work; besides on some locales text not fits in UI of dialogs) Bug 35302 - in Writer in table cursor jump to last cell if press Ctrl-A (user lost cell where last time works, problem if table is big) Bug 35829 - Writer table: can not select rows by mouse (user can not select many rows in table) Bug 35991 - merged cells in tables in DOC files not saved correctly by Writer on Linux 64bit (user can not save to doc format correctly) Bug 36035 - Opening .doc file displays numbering with wrong size VIEWING (some files open incorrectly) None of these bug is serious, but they are annoying
Nominate Bug 39187 - Mouse pointer disappears instead of changing to "move arrows". There are lots of additional conditions causing disappearing mouse pointer, Master is difficult to use
Nominate Bug 39026 - Recent Documents list does not work
Add bug 40392. LO window is on background when starting on MAC.
I nominate bug 40466. Import and Export Excel files in format xlsx crashes immediately. Working with spreadsheets in new Excel format is impossible.
Nominate "Bug 40615 - PDF: Most of contents missing, wrong PDF syntax": Very basic function completely broken, WRITER would be unusable for very many users.
nominate Bug 39313 - XTableRows.removeByIndex and also symply remove Row / Column crashes Libo
(In reply to comment #7) > nominate Bug 39313 - XTableRows.removeByIndex and also symply remove Row / > Column crashes Libo It is a core function => accepted
Nominate "Bug 40449 - SPELLCHECK does not recognize text language", WRITER without any spell check - unimaginable!
Nominate "Bug 39365 - Spell check does not work after copy / paste, modified language not recognized". WRITER without any spell check - unimaginable!
I nominate Bug 35669 it really old but never the less very annoying. For complex Documents and Thesis it is important that the master document feature works again. https://bugs.freedesktop.org/show_bug.cgi?id=35669
Nominate "Bug 40902 - FILEOPEN CRASH with trivial lorem ipsum text document"
Nominate Bug 30467 - required visual studio 2008 redistributable libraries not installed, failed to start. For details please see <https://bugs.freedesktop.org/show_bug.cgi?id=30467#c20>
I would like to nominate bug 40298. Crash when moving cells <https://bugs.freedesktop.org/show_bug.cgi?id=40298>. It happens a lot using KDE interface rendering working with calc quite interesting.
(In reply to comment #13) > Nominate Bug 30467 - required visual studio 2008 redistributable libraries not > installed, failed to start accepted
Nominate "Bug 42178 - CRASH when PRINTING from Page Preview"
I nominate the bug #41888. The import/export of shapes is somehow broken.
Nominate "Bug 42227 - FILEOPEN: rotated objects all in top left slide corner", what makes DRAW unusable
Nominate Bug 32664 (multimedia keys)- this (i hope only a) simple bug which is not solved for years (since OOo 3.0.1).
Nominate Bug 42640 - Impress may shows the wrong image if a RTF file is opened before the ODP document.
Nominate "Bug 42694 - EDITING: Crash when insert Table Control". Potential for 3.4 M.A.B. but within rather long time nobody reclaimmed, so 3.5 might be more appropriate.
I would like to focus on an improvement, not a bug. The possibility to print notes besides text, like in MS Office would be really a big step forward. This feature is missing since the early OOo release. Due this lack I still need MS Office for printing documents with notes, because it is not possible to work with notes printed on the next/last page.
Orwel - it is quite a well known issue that people are trying to find funding to fix; whether it is a 'most annoying' bug, as a non-blocker, non-regression I don't know. Then again we have no tracker for "most important features". Either way, you'd want to file a bug for this I think. Also the feature freeze is in ~2 weeks, so you're a bit late for 3.5 :-)
I want to add 42826 : unopkg.bin runtime error during installation. If we want to make test, we need a version installed without error.
Nominate 43105 because its: - a regression - a very relevant file import (*.doc) File import issues are hard to tracks as is, and regressions are harder to solve the longer they are in the product.
Nominate bug 35669: Incorrect cross-references to illustrations and equations in master documents. It is a quite old bug with many duplicates and votes.
Nominate bug 43154: regression from LibO 3.4, false results in Calc.
Nominating bug 40447: cannot change macro security settings: UI does not open
Nominate Bug 42914 - Terminal (command) window is opened when launching any executable. Such a very visible problem is not acceptable for a release.
Nominate "Bug 42979 - Wrong application icon on the MSVC Master". Such a very visible problem is not acceptable for a release.
Nominate "43384 - FILESAVE: causes lots of messages or even impossible". Blocker if reproducible!
Nominate "Bug 43409 - CRASH wen close document" Blocker if reproducible!
Nominate bug 42470: scripting code in the wild (and example code in SDK) uses --nodefault command-line argument to mean "splash screen shown, but no window opened after that". LibO 3.4 uses it to mean "show welcome screen on startup instead of opening a blank Writer document", which breaks user code. We need to clean that up.
Nominate "Bug 43454 - Break-off with message "Terminate Quick Starter""; 3.5.0 Beta0 Installation fails for me.
Nominate 'Bug 43422 - Spell check: Crash "Runtime Error" with AutoSpellcheck'; not acceptable for a release.
Nominate Bug 43462 – findAll doesn't work This bug would break extensions and macroses that use findAll method in Calc
May I propose to add Bug 36982: "Writer ignores text after Equation in docx" -- or even crashes (see comments about the bug)? I know this is an old bug report from LibreOffice 3.4, but IMHO fixing it for 3.5 is even more important now because our "scratch-pad of notes to build release notes from" at http://wiki.documentfoundation.org/ReleaseNotes/3.5 says: "Support for export and import of math formulas in Office Open XML (docx) documents (Luboš Luňák)." So, if we declare that there is now official support for import/export of math formulas in docx documents, it is strange that opening such a docx document containing some math formulas does not work at all or even crashes LibreOffice ... Just ignore my proposal if I got something wrong, but at least to me fixing this bug seems especially important. It should be not that difficult, BTW, because on MacOS the same docx files containing math formulas already open without major difficulties, so this seems Windows-only problem ... Compare also Bug 43429, which is IMHO a duplicate of Bug 36982 but especially describes the crashes.
Nominate bug 43556: Hidden state in report design, leads to behaviour that is incomprehensible from what is shown in the UI.
Nominate "Bug 43614 - Crash when closing document and several Spreadsheet documents open", makes CALC unusable!
Nominating "Bug 43491 - CONFIGURATION: Using existing User Profile existing WRITER documents open "semi read only"". Currently indications are rather confusing and it's not a crash or similar, but there is a potential to make WRITER unusable after an update.
Nominating bug 43197 : navigator corruption. The problem is mostly with Impress and make the navigator unusable.
Nominate #42656 : Problems during exchange of image from ODP and RTF. Copy an image from an opendocument to an rtf does'nt work
Nominating Bug 41996 - Can't move slides in slide sorter. Tried with LibO 3.5 beta 0. Seems to not affect everyone, though. (Only certain Linux distros? It would be nice to get more people to test it.)
Nominate "Bug 43752 - VIEWING: Rotated flipped shapes in 3.4 drawings loose rotation opened in 3.5".
Nominate "Bug 43749 - EDITING in existing cell content not possible, cursor jumps to line end"
Nominate "Bug 43707 - FILEOPEN PDF brings up (ASCII) filter selector instead of opening document"
Nominate "Bug 43831 - Advanced FILTER incompatible with 3.4.4 documents" - we should not break compatibility
Nominate "Bug 43862 - Page FORMATTING: Margin settings information not compatible with 3.4.4", breaking version interoperability is a potential blocker.
Nominate Bug 43837 - Impress crashes on custom animation of presentation objects Please try it out, it is not confirmed yet.
Propose Bug 43867 - MAILMERGE: Mail Merge with image in header of document, causes crash
propose Bug 43458 - LibreOffice does not start with a second monitor connected
propose Bug 43824 - Crash when starting to enter cell contents with a single quote for the second time
propose Bug 43532 - Renaming and deleting of inserted template categories broken, inserted templates land in wrong category (indexing issue in code)
proposing Bug 43480 - EDITING: cell text *contents* from Calc pasted to Writer is pasted at bottom of document, unless paste special is used
propose Bug 43869 - Paste special from Calc to Writer, causes last paragraph to be removed
Propose bug https://bugs.freedesktop.org/show_bug.cgi?id=35023, base is unusable until this is resolved. While it seems to be a Java bug, we already appear to have had at least one misdiagnosis.
Adding Bug 43837 (as reported by Regina Henschel in comment #49) to the list because the bug has been confirmed now and is a blocker.
Propose to add this: https://bugs.freedesktop.org/show_bug.cgi?id=43738 Two of our bundled extensions don't work on Windows.
(In reply to comment #44) > Nominate "Bug 43752 - VIEWING: Rotated flipped shapes in 3.4 drawings loose > rotation opened in 3.5". Yup, we should fix this.
I propose the following bugs in order of my priorities: Bug 40482 - CONFIGURATION: Formatting aids - displayed nonprinting characters become unchecked during printing and PDF export Reason: Because it is a regression and really annoying to recover the characters. Bug 40489 - PRINTING: Option Buttons and Check Boxes not printed correctly Reason: Because it is a regression and we have many documents with check boxes making it impossible to use LO at the moment. Bug 43765 - FORMCONTROLS: Check Boxes and Option Buttons Become Invisible, when you Click into a Table. Reason: Because it is a regression and image of LO is suffering ("Why do we use LO if that software is not able to display a simple document). Bug 34436 - TABLES text in cells behaves wrong when rotated Reason: Because MS Word compatibility is important for us. Rotated text with more that one line can not be read after import and even the creation of the second line next to (and not under) the rotated text in LO is less than obvious. The behaviour (Ctrl+Enter) is not expected by the users I know.
Proposed bug 44110. "New Math symbols poorly redered in Windows" The bug has the fix already, we just need to cherry-pick the files.
Proposing bug 44078, as UI in Hebrew is broken due to selection of a font without Hebrew support. Since beta2, this font is also part of LibO, which makes the problem to happen on default installation unless the font is manually deleted from the system.
Nominate "Bug 43856 - PRINTING: after leaving Print Page Preview with <esc> particular documents will CRASH", it seems many documents are affected
add Bug 44219 - Text rendered poorly
Writer (beta2) crashes after leaving to another program on Win7 64bit https://bugs.freedesktop.org/show_bug.cgi?id=44260
I nominate the bug #44040. Crash when page preview after <f4> (data sources).
hello, I re-openend https://bugs.freedesktop.org/show_bug.cgi?id=36681. For an average user this bug is very confusing and dissapointing. Should be corrected before releasing a new version. I also did see it in the main-build, 3.6. I discovered it myself working on a 230 pages document, my logbook, which I carry along for 6 years (!). So now this bug suddenly appeared. I am even disappointed my self. From the discription: it showed up suddenly and disappeared suddenly, now it is there again. For me it was consistent during 3 days of editing work on a document, then was gone again in one editing session. Some not of half-way initialised parameter ? Please consider adding this bug to this generic bug report. Luc
(In reply to comment #67) > hello, > > I re-openend https://bugs.freedesktop.org/show_bug.cgi?id=36681. > > For an average user this bug is very confusing and dissapointing. Should > be corrected before releasing a new version. I also did see it in the > main-build, 3.6. I agree that it is quite annoying => adding here. Well, I am not if we will be able to fix it. Random bugs are always hard to cope with.
(In reply to comment #66) > I nominate the bug #44040. Crash when page preview after <f4> (data sources). Yup, that sounds pretty nasty.
Nominate "Bug 41436 - FORMATTING: User style not trans ferred with copy / paste to other document", this bug makes effective work with DRAW impossible (enchains me to OOo 3.1.1)
Nominate 44093: Forms open in printer view. They should open in web-view
Nominate Bug 42073: Writer input fields are not populated using the Java UNO API
As per discussion with Michael Meeks, nominating bug 44075 - mysql connector 1.0.1 extension from Oracle no longer works with 3.5 and throws a UNO shared object/component error. Alex
Nominate Bug 44467 - Deleting sheets can shift images or graphics between next sheets
Nominate 44147: unable to edit embeded Calc table in Writer
Please, verify Bug 44492 - in Arabian text blank squares instead of letters it my be regression if confirmed
Nominate 44322: ODF compatibility; margins saved by Lo-3.5 are not read corrrectly by L0-3.4
Nominate 44498: Even simple odt document is considered as invalid by MS Office 2010.
Nominate "Bug 43989 - After installation first launch terminates after splash screen". Although it seems completely harmless, that's no good first impression of a fresh installed software. We should be sure that that will not happen with RC1.
Nominate "Bug 44518 - EDITING: CRASH for any input in Full Screen Mode"
(In reply to comment #79) > Nominate "Bug 43989 - After installation first launch terminates after splash > screen". Although it seems completely harmless, that's no good first impression > of a fresh installed software. We should be sure that that will not happen with > RC1. I agree that it is annoying => added. On the other hand, you saw it also with 3.4.5 => it is older bug => it is not must to have for rc1.
I am a bit unsure about these, but I'd like to nominate: Bug 38515 - LibreOffice crashes in Bibliography dialog when pressing Enter – Because it's a crash and has been in LibO at least since 3.4 Bug 44602 - Modeless Word Count window hides when user clicks into a note – Because it's a new feature that doesn't always work as advertised
Adding "Bug 40438 - CRASH in OLE object EDITING"
Please, verify Bug 44664 - Calc PRINTING: printer prints Landscape page orientation as Portrait it my be regression if confirmed
Adding bug 44657 - There's no scroller in Calc's scrollbar with RTL UI.
(In reply to comment #84) > Please, verify Bug 44664 - Calc PRINTING: printer prints Landscape page > orientation as Portrait > it my be regression if confirmed Please see prior Bug 38962 as it may be the same or a closely related bug. In Bug 38962 Comment 3, freedesktop isolates the problem he is seeing to the Printer Language Type being set to PDF. Note that this may be affecting primarily Brother brand printers(???). Also note that this may be an issue for 3.4 as well as 3.5.
(In reply to comment #82) > Bug 38515 - LibreOffice crashes in Bibliography dialog when pressing Enter > – Because it's a crash and has been in LibO at least since 3.4 I crashes even when adding TOC, so let's add it > Bug 44602 - Modeless Word Count window hides when user clicks into a note > – Because it's a new feature that doesn't always work as advertised I think that this one is rather funny than annoying. I think that we do not need to prioritize it that much.
Add Bug 37860 - Formula returns #VALUE in 3.4RC2 but works as expected in 3.3 Although the change is intended, it breaks compatibility to earlier versions and to Excel import. There's a common pattern =IF(A1+B1=0;"";A1+B1) which is used to hide zeros, that leads to an error if another formula references this cell when 0/"". Additionally it is already tagged as EasyHack.
Nominate bug 44721: Cannot resize a control with the mouse in Report Builder.
I am still confused about the usage of "nominate" here. http://en.wiktionary.org/wiki/nominate says it has two meanings: 1) To name someone as a candidate for a particular role or position, including that of an office. and 2) (obsolete) To entitle, confer a name upon. So, when people "nominate" a bug for the coveted Most Annoying membership, does that mean they 1) suggest it as a candidate for being Most Annoying, i.e. invite discussion whether it is or not? Or that they 2) directly entitle it, say that it *is* a Most Annoying bug?
@Tor: Because of that confusion I changed my wording to "Adding bug ...". I do not believe we should do long discussions here concerning each bug, IMHO the proceeding should be: - Always add the Bug Number to "Depends on" - Always cite the Bug Subject in a comment with a one sentence reason why it is a "Most Annoying" one, so that we keep overview here. Without objection the Bug remains listed here, or someone objects and deletes it from "Depends on", further discussion in the Bug report itself. A "nominate first, discuss, add" would be too bureaucratic
I understand it the way that all bugs are kind of nominated because they could be added and removed from the dependencies at any time if there are good reasons. I think that the main confusion is whether to update bug dependencies together with the explanation comment or wait for someone to accept it. My suggestion is to update dependencies immediately if you are pretty sure that it is annoying for many users. You could just leave a comment if you are not sure. It is how it works now and I think that it works well. I agree with Rainer that we do not want long discussions about every bug. Most people nominate reasonable bugs. This is why the initial comment suggest to add the dependency immediately. By other words, both approaches are good. You can't do a mistake :-)
Version LOdev 3.5 beta3 S.O. Ubuntu 10.04 and Debian Testing. Leaflet 'writer' with inserted OLE object (Calc). Opens the object Calc to modify the cells. No change is possible because the sheet Calc is protected. Even if 'format cells' eliminates the tick on 'protection' remains the fact that it is impossible to modify any cell. In my similar models very old (made with OOo 2.x in years 2003, 2004 or 2005) the elimination of protection works very well and the cells are modified and saved correctly.
(In reply to comment #93) > Version LOdev 3.5 beta3 > S.O. Ubuntu 10.04 and Debian Testing. > Leaflet 'writer' with inserted OLE object (Calc). > Opens the object Calc to modify the cells. > No change is possible because the sheet Calc is protected. > Even if 'format cells' eliminates the tick on 'protection' remains the fact > that it is impossible to modify any cell. In my similar models very old (made > with OOo 2.x in years 2003, 2004 or 2005) the elimination of protection works > very well and the cells are modified and saved correctly. Felice this must be reported only (!) on Bug 44147 and, in case, changed there the target platforms: not here in 3.5 bugs collection. Ok? Carlo
Hi Kohei Why did you remove that bug from the list? Shouldn't I have it added to 3.4 and 3.5, or what's the reason? Regards Philipp Am 12.01.2012 20:13, schrieb bugzilla-daemon@freedesktop.org: > https://bugs.freedesktop.org/show_bug.cgi?id=37361 > > Kohei Yoshida <kohei.yoshida@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Depends on|37860 | >
Another interesting bug: Bug 44770 - Writer FILESAVE: document, saved by LibO 3.5.0 opens incorrectly in LibO 3.3.4 and 3.4.3
Add bug 44210 : too bad user experience with StartCenter.
(In reply to comment #96) > Another interesting bug: > Bug 44770 - Writer FILESAVE: document, saved by LibO 3.5.0 opens incorrectly in > LibO 3.3.4 and 3.4.3 @sasha: You nominated bug 44770, but bug 44770 is marked as a duplicate of Bug 43862, which is (or should be) fixed now. Is bug 44770 not fixed for you? If this is the case, it is probably not a duplicate of bug 43862, and then bug 44770 should be opened again. Or why did you nominate it? Am I missing something? (Just wanting to help, no offense!)
@Roman I closed bug 44770 (as dup) after it was mentioned here. The fix will be at beta3 while it was reported on beta2.
Possible regression from 3.3.4 if confirmed: Bug 44829 - Impress EDITING: Undo not works when change master page
Suggest bug#44836 - leaking page-breaks in the rendering, makes the new feature look bad.
possible regression, if confirmed: Bug 44856 - Calc: font on screen looks corrupted
possible regression, if confirmed: Bug 44862 - Writer EDITING: LibO crashes when attempt to copy-paste from Calc and undo results
possible regression, if confirmed: Bug 44863 - Calc EDITING: when recovered after crash, impossible to enter into cells
users from opennet.ru very complain on this bug: Bug 40540 - FILESAVE During DOC export drawing is lost
another regression since 3.3.4 version: Bug 40539 - Writer FILESAVE: Text direction in table is not saved into DOC format
Regression from LibO 3.3.4: Bug 37561 Rationale: Duden Korrektor is a commercial extension (ca. 20 Euro) providing various language tools for the German language that in many tests out-performed all other similar contestants. The extension is available for LibreOffice, OpenOffice and Microsoft Office and is important for German professional writers as well as many 'regular' German writers. Not being able to install the extension in LibO 3.4.0 to 3.4.4 makes for a /very/ bad user experience. Guess what users relying on that extension will stay with or switch to? As far as I can see from the discussion in #37561, a fix (adding missing symbols) should be relatively simple. Thanks, Stephan Hennig Note, I've also added this bug to 'LibreOffice 3.4 most annoying bugs', but only after LibO 3.4.5 was released. According to the release plan LibO 3.5.0 will be the next release.
another regression since 3.3.4 version: Bug 44868 - Writer FILEOPEN: document in format DOC with picture opens incorrectly
Suggest add major PPTX performance regression: bug#44719 that may affect other font related performance issues.
https://bugs.freedesktop.org/show_bug.cgi?id=44915 MSI installer does not show localized UI for many languages, for example pt-BR.
Possible regression: In Writer options disappears one option, important for Asian languages. See explanations in last comments of this bug: Bug 33743
I added https://bugs.freedesktop.org/show_bug.cgi?id=36876 which should be, if it that's not clear, OpenOffice bug 13791. Writer FILEOPEN: document in format DOC with table opens incorrectly.
Adding bug 44025 ORowSetCache provides the XResultSet interface. Its isLast() returned true on the last line of the prefetch window, instead of the last line of the data. This has the potential to break a lot of other stuff, and in particular breaks search: the search does not look beyond the prefetch window.
Can I nominate Bug 34531 Not letting the Smartboard ink layer get above an Impress presentation on a second screen makes Impress pretty useless in most schools. XP works fine but Linux doesn't ( As in: Slideshow/Slideshow Settings/Presentation Always On Top doesn't seem to do anything at all )
(In reply to comment #114) > Can I nominate Bug 34531 > > Not letting the Smartboard ink layer get above an Impress presentation on a > second screen makes Impress pretty useless in most schools. > > XP works fine but Linux doesn't ( As in: Slideshow/Slideshow > Settings/Presentation Always On Top doesn't seem to do anything at all ) Updated this bug for RC1... Please read it's very interesting M
Nominate 44143 - formula's that use data from pivot table don't update with the pivot table
nominate Bug 33302 - brackets inverted in rtl text (mac only).
(In reply to comment #117) > nominate Bug 33302 - brackets inverted in rtl text (mac only). sorry for double post but i wanted to add an argument : it is very annoying to see inverted brackets in file you open or create, it makes it very hard to know how the file will look in other programs , and the bug persists while printing . it is probably not hard to fix it is related to fonts (neooffice fixed it a long time ago)!
Nominating Bug 45068 - Update installation from 3.4 fails on most windows systems
> Nominating Bug 45068 - Update installation from 3.4 fails on most windows @Volker: It's as Lionel wrote in the bug, we can't do a Fix for the 3.4.4 and older versions. But we urgently will need a hint in the installations manual that Versions before 3.4.5 will have to be uninstalled on 64 Bit WIN
I think that bug 40289, bug 36742 and bug 45078 are the same one. I just test them with: - LibreOffice 3.4.5 rc2 (= final), linux x86-64 rpm build, on OpenSuSE 12.1, kernel 3.1.0, updated, Gnome, ita GUIed; - LibreOffice 3.5.0 beta3 and rc1, win32 build, on my Windows Vista 64 bit, SP2, updated, ita GUIed; and I obtained always the same result: the bug is still here. Now I try with 3.5.0 RC1, I posti here test results and then I add them to Most Annoying 3.4 and 3.5 ones. I think they may hide a bad table width initialization and tick and color management. This affect quality and people LibreOffice quality ideas. Tables and default table width are too often used to yield many document and their exported PDFs so that people may easily decide because the border bug that LibreOffice is still too young to be adopted and so they may decide to unistall it putting all our efforts trough the window! It's a big pity! So that I add them to most annoying one. Carlo
adding regression Bug 45084 - FILEOPEN: Cannot open HTML Files in Calc
(In reply to comment #117) > nominate Bug 33302 - brackets inverted in rtl text (mac only). It sounds pretty annoying => added to the list.
(In reply to comment #109) > Suggest add major PPTX performance regression: bug#44719 that may affect other > font related performance issues. Added to the list. The reason is quite located. Probably has more duplicates.
(In reply to comment #114) > Can I nominate Bug 34531 Let's leave it outside the list for now. I am not sure how many users are affected. The bug has already got some attention. It works on Windows now...
(In reply to comment #106) > another regression since 3.3.4 version: > Bug 40539 - Writer FILESAVE: Text direction in table is not saved into DOC > format Added to the list 40539. The document is still readable but it looks much worse. The other text direction is pretty useful feature when you do more complex tables.
(In reply to comment #105) > users from opennet.ru very complain on this bug: > Bug 40540 - FILESAVE During DOC export drawing is lost The objects are somehow special. Normal drawing objects are exported correctly. I have added some experts into CC. I am not sure how many users are affected, so let's leave it out of the most annoying bugs for now.
Want to add bug 45067. Pivot table with dates is inusable. Dates are changed in string, so you cannot use Data > Group.
(In reply to comment #104) > possible regression, if confirmed: > Bug 44863 - Calc EDITING: when recovered after crash, impossible to enter into > cells Great catch. Well, let's leave it outside of most annoying bugs for now. It happens only when the document in not saved or autosaved.
(In reply to comment #104) > possible regression, if confirmed: > Bug 44863 - Calc EDITING: when recovered after crash, impossible to enter into > cells Added to the list. Looks well reproducible. Might help to solve more cut&paste related crashes.
(In reply to comment #130) > (In reply to comment #104) > > possible regression, if confirmed: > > Bug 44863 - Calc EDITING: when recovered after crash, impossible to enter into > > cells > > Added to the list. Looks well reproducible. Might help to solve more cut&paste > related crashes. I am sorry, this was meant for the cut&paste crasher bug 44862.
(In reply to comment #102) > possible regression, if confirmed: > Bug 44856 - Calc: font on screen looks corrupted It has been fixed in the meantime.
(In reply to comment #100) > Possible regression from 3.3.4 if confirmed: > Bug 44829 - Impress EDITING: Undo not works when change master page Nice catch. I see it also with 3.4.5. I am not sure how many users are affected. I would leave it as a normal bug.
Bug 45084 is not a regression even though it may seem like one to some users. I gave my reason in that bug report. Please consider removing it from the list.
(In reply to comment #134) > Bug 45084 is not a regression even though it may seem like one to some users. the bug report currenly shows no consensus about it being not a regression ..
(In reply to comment #135) > (In reply to comment #134) > > Bug 45084 is not a regression even though it may seem like one to some users. > > the bug report currenly shows no consensus about it being not a regression .. If we need to ensure the same order in an unordered map container, then all bets are off. I'll leave it at that. No more input from me.
(In reply to comment #136) > If we need to ensure the same order in an unordered map container, then all > bets are off. I'll leave it at that. No more input from me. pls consider to read the comment in the issue en reply there. It's the way to open the file, that you suggest to use, that is not working any more. thanks.
In one bug hard to distinguish regression from new functionality: Bug 35735 - "Save As" defaults to current document format
Added Bug 33393 : images (graphics, pictures) get lost on editing. Gets more duplicates ..
#40907 : Networking for Mac users is strongly affected by this bug. When a user attempts to open a file already open on AFP shared folder, it is not advised of which use this file, but receive an I/O error
Add "Bug 45219 - SLIDESHOW: Transparency gradient effect fade in with wrong VIEWING", that might make Presentation useless fol many users.
(In reply to comment #138) > In one bug hard to distinguish regression from new functionality: > Bug 35735 - "Save As" defaults to current document format It was already in LO-3.4. The current state seems reasonable. Just the description is slightly confusing. People do not complain about LO-3.4 => normal bug.
Heh, I have modified the platform setting by mistake.
Nominate Bug 45248.
Nominate Bug 45248. This is a seemingly minor regression, but it breaks our extension quite badly :(
possible regression since 3.3.4: when import from doc, comments disappears Bug 37794 - Writer, comment (see last comment)
Instead of Bug 37794: Bug 45255 - Writer FILEOPEN: when open doc file, comments disappear
Adding Bug 42543 - Report Designer Wizard missing Label display and editing capability - regression
Add bug #45254: cannot edit data using postgreSQL-SDBC
Add bug 45042: The Document Converter wizard is crashing on Windows OSs with default installation. It depends on binfilters.
Added 37024 as we have now had this bug for the whole of the 3.4 series and it is still not fixed. It is a blocker for all Base users, and a regression over previously established OOo 3.x versions and apparently LibO 3.3.x versions of ODB files. Alex
Add "Bug 45370 - EDITING: Calculated cell contents not updated after copy - paste - delete of source values", what makes calculations unreliable.
Adding bug 34432: Crash on 64 bits when using an ODBC datasource (some drivers).
Regression since 3.3.4 Bug 39415 - Table borders in word 200x .doc are shown incorrect in writer
regression since 3.3.4: Bug 39903 - FORMATTING: Table number format not retained
+ "Bug 45401 - CRASH when XML filter settings XSLTs test", regression crash!
+ "Bug 45409 - FILEOPEN particular .doc: Table of contents broken, internal reference information visible". Makes 3.5 useless for editing WORD documents, dataloss, saved with 3.5 also unsable with more early versions.
Adding bug#45453: on database system with no/poor boolean support, "big" queries/tables completely fail to open in datasheet mode.
regression since 3.3.4: Bug 40320 - Pie charts colors messed up when saving opening Excel (.xls) documents
possible regression, all formulas in doc file disappear: Bug 40768 - LibreOffice Writer doesn't get the right border style of an image or object in .doc files
Added Bug 31624, without the necessary change to the Windows installer (to include XML filters in the default installation), Flat ODF (XML) fails to work on Windows.
regression, doc file opens wrong (see my comment): Bug 40787 - FILEOPEN: Extra footer text when Libreoffice opens a .doc created in Word
Writer hangs on Linux when open docx file, regression: Bug 40900 - FORMATTING: Writer unable to format specific docx/doc correctly
Bug 45584 - presentation view defective
Adding 45607 - really poor performance on Calc macro execution (repeat insertions). Alex
Adding bug 45341, this is a (partial) regression against OOo and the fact the field becomes completely undeletable is a very annoying behavior.
regression since 3.3.4, OLE opject not opens: Bug 41765 - cannot open OLE object when the document is opened in read-only mode
regression since 3.3.4, most information in doc file is lost Bug 41798 - FORMATTING: Opening a .doc file - Regression in Libreoffice 3.4
please look at Bug 45521 - [FILEOPEN] "LibO Writer changes decimal delimiter when opening a sdw file which causes data loss after saving" Maybe specific case, maybe more generic problem ..
Bug 45696 - Importing uno libraries in python my crash python; workaround exists
add Bug 45085 - FORMCONTROLS: Notes/comments are displayed below controls
Add Bug 45049 Non-standard caption number and reference do not appear in the insert cross-reference dialog
It took me far to long to step into this annoyancy: problems with paper size and printing. As fas as I am concerned, all 3.4 versions are affected and the 3.5 line logically too. Bug 34380 - PRINTING - Brochure printing incorrectly changes paper size to 'Legal' Bug 33791 - Print system fails to use or allow user to select correct paper size for printing Bug 44275 - Letter-size landscape 2-column Laser PRINTING bug Please note that in this comment : https://bugs.freedesktop.org/show_bug.cgi?id=34380#c12 I've added two links to discussions on the users list. One with more explanation (in my judgement) / workaround. Highly recommended :-) Would be great to have 3.5.1 cured from those issues. Thanks
Put back 33791. It was evidently removed by mistake, probably when adding a comment at the same time.
Add 45117: Shrinked buttons in the warning when saving documents in non-ODF file formats.
regression since 3.3.4 Writer crashes opening fodt file Bug 42771 - Crash over invalid ODF
Nominating 43567, nasty crash in XML Form document production. Alex
Nominating 40261, see also bug 43567 where there are bt provided by Julien - nasty crash in XML form control Alex
regression since 3.4.5 Bug 43229 - Unable to un-protect password protected MS-Word .doc document
Can't install 3.5 because it says I must quit using another version of libre
(In reply to comment #180) > Can't install 3.5 because it says I must quit using another version of libre It is most likely caused by the bug 45068. The update to LO-.3.5 does not work directly from LO < 3.4.5. The solution is to either install 3.4.5 and then 3.5 or remove the older LO before installation.
Bug 43313 - Writer table: border of merged cell is misplaced (regression since 3.3.4)
Bug 43318 - Draw printing: Bitmap edited object prints incorrectly from Draw (regression since 3.3.4)
No databases in Wisard of mailmerge (regression since 3.4.4) Bug 43399 - Address data source wizard will not allow the definition of a Spreadsheet connection setting
add Bug 45991 Crash when merging cells that have been pasted as Formatted text from copy of spreadsheet cells
Add "Bug 46038 - EDITING: CRASH when copy-paste text from particular WRITER source" because of regression CRASH
Added 44127 - Writer EDITING: LO crash on "Apply Numbering" Undo with Tracked Changes
regression since 3.4: ole object inserted in Calc becomes looking corrupted when resize object or save/reload document: Bug 44838 - FORMATTING: Position, size, word wrap wrong for WRITER OLE Object in CALC
Consider Bug 46144 - "Distributy Columns Evenly" does not work with the selected columns. Also scripting in Java unavailable (regression since 3.4.x) - Bug 46102 - script dispatch java extensions are broken
This happens with LO3.5.0 released version downloaded on 18/Feb/2012 on MSWin7Prof64-bit. LO crashes quite frequently. I have filed a separate bug 46292 about crash when attempting to set proxy. (In reply to comment #81) > (In reply to comment #79) > > Nominate "Bug 43989 - After installation first launch terminates after splash > > screen". Although it seems completely harmless, that's no good first impression > > of a fresh installed software. We should be sure that that will not happen with > > RC1. > > I agree that it is annoying => added. On the other hand, you saw it also with 3.4.5 => it is older bug => it is not must to have for rc1.
mentioned above bug 46144 is regression since version 3.4
@ Orwel, Michael Meeks: There is already a bug for Advanced printing capabilities of comments in Writer [PRINTING] at https://bugs.freedesktop.org/show_bug.cgi?id=36815. It's one of my favorites.
I don't know why https://bugs.freedesktop.org/show_bug.cgi?id=39006 was not here, but now, it is: FILEOPEN: LibreOffice hangs with 100% CPU usage on specific .doc file.
Add "Bug 43932 - PRINTING: Paper tray setting not accepted from "File -> Print..."", broken important basic function.
Regression: into Calc pastes not only selected text, but also content of Header of page: Bug 45637 - EDITING: copy and paste text from Writer to Calc performs wrong (regression since 3.4)
I added Bug 46393 - PRINTING: VIEWING cell borders differs from PRINTING. Although it's still not confirmed, looks like a bug and behaves like a bug :)
I add issue #46498, am checking if it was in the 3.5.0 rel version
adding issue #46165 more ole array handling brokeness
Nominate Bug 44135 which could be related to Bug 40143: transparent color objects shows up in gray scale in PDF
adding bug #46568 This is data corruption in a pretty well used dialog in calc ( e.g. the Manage Names dialog ) note: it core dumps for me consistently with accessibility enabled ( but ymmv )
I would like to nominate confirmed bug #44937 for 'most annoying'. As a professor, I was using the 3.5 series, but I cannot give my lectures because of the above bug, so I have a revert back to using the 3.4 series.
(In reply to comment #201) > I would like to nominate confirmed bug #44937 for 'most annoying'. > > As a professor, I was using the 3.5 series, but I cannot give my lectures > because of the above bug, so I have a revert back to using the 3.4 series. It seems to be fixed in 3.5.1-rc1 => it does not need immediate attention => let's leave it out of the most annoying bugs. Feel free to put it into most annoying bugs if you still see it with 3.5.1-rc1 or never.
(In reply to comment #199) > Nominate Bug 44135 which could be related to Bug 40143: transparent color > objects shows up in gray scale in PDF I am not 100% sure that the bug is in LibreOffice. Anyway, it looks annoying, has more duplicates, so let's add it here.
Add 45171: Can't open document with password; It seems to be related to a Firefox upgrade. It affects many distro builds.
Printing problem on Windows 7. My be somebody can help to reproduce this or understand source of problem or knows workaround: Bug 44275 - Letter-size landscape 2-column Laser PRINTING bug
Please consider bug 36547, included in 'LibO 3.4 most annoying bugs', but still there in LibO 3.5.0...
@Raphaël I think that all 3.4 most annying bugs the will not be fixed in LibO 3.4.6 (last release of the 3.4.x series) will be then moved into the 3.5 list
removing bug# 46498 ( doesn't affect release build )
Added Bug 46769
Add bug 46687: undocked 'Find' toolbar freezes the application
When I hide a row and then copy the remaining rows Calc will also copy the hide rows.
(In reply to comment #211) > When I hide a row and then copy the remaining rows Calc will also copy the hide > rows. I'm not sure if this is a feature or a bug, but for now, there's an extension for the behaviour you want: http://extensions.libreoffice.org/extension-center/copy-only-visible-cells
(In reply to comment #212) > (In reply to comment #211) > > When I hide a row and then copy the remaining rows Calc will also copy the hide > > rows. > > I'm not sure if this is a feature or a bug, but for now, there's an extension > for the behaviour you want: > http://extensions.libreoffice.org/extension-center/copy-only-visible-cells Thanks for the pointer :-) Well, in general, please, do not discuss details about issues in this meta bug. It already has more than 200 comments, so any useful detail gets lost soon. I have asked Bas (in a private mail) to open bug for the problem and mention the bug number here.
Add bug 46843: Base Queries loose sorting-order when reopening for editing
Add "Bug 46532 - SLIDESHOW does not show pictures with Hardware Acceleration activated"
Add "Bug 46901 - SLIDESHOW shows characters too slim with Hardware Acceleration activated"
(In reply to comment #211) > When I hide a row and then copy the remaining rows Calc will also copy the hide > rows. As I know this only works with rows hidden by filters not if is hidden directly.
@bordfeldt@web.de: please don’t change Platform or Version here — this is a meta-bug to keep track of all "LibreOffice 3.5 most annoying bugs" (well, the headline says it all), and therefore, Platform should be All/All.
add Bug 39003 - Undo for automatic numbered/bulleted lists selects previous line, but the cursor should stay in position: a 1st class usability annoyance
Add "Bug 47052 - Recovery fails because no access to AppData Temp folder", data loss
Add "Bug 43882 - EDITING: CRASH when undo copy paste". It's rather a chin-up to get the crash, but we can't know whether there are other more simple ways to crash LibO because of this bug.
Adding 47068, nasty crash in Report Builder when moving a graphical object over a text field. Alex
I just add Bug 32886 - "recent documents list always blank with libreoffice" because it it quite annoying (it blocks an useful function also to first use users), it is a regression and it has been pointed out that cleaning the (linux only?) LibreOffice profile directory (~/.config/libreoffice/) solve the problem.
Bug 43021: https://bugs.freedesktop.org/show_bug.cgi?id=43021 This bug first appeared in OO3.2 ( see https://issues.apache.org/ooo/show_bug.cgi?id=110141) But it is still not fixed. The FilePicker is one of the most used functions in Macros, Extensions, and Templates. And therefore this bug should be fixed soon. You can read nearly every weak about this bug in the mailing-lists or a forum. (http://libreoffice-forum.de/viewtopic.php?f=12&t=6652, http://user.services.openoffice.org/en/forum/viewtopic.php?f=45&t=38912, http://user.services.openoffice.org/en/forum/viewtopic.php?f=20&t=47621 http://de.openoffice.info/viewtopic.php?f=8&t=49308...) Regards Frieder
Add "Bug 46230 - EDITING: impossible to perform a drag & drop of entire row/column", that's really annoying if you are used to work with those edit functions.
Added bug 47274 - EDITING: Crash when copy/paste table with data from Writer.
Nominating Bug 46809. Regression and big usability problem in Calc.
Nominating 46439 as blocker - can not access postgres db with official 3.5 builds on Mac and native postgres driver - works on build from master !!
(In reply to comment #228) > Nominating 46439 as blocker - can not access postgres db with official 3.5 > builds on Mac and native postgres driver - works on build from master !! Oh well, too late apparently !! Just seen the announcement for 3.5.1. Alex
Regression since 3.3.4 in Writer: wrapping text around object becomes or seen wrong after use Page Preview Bug 45376 - [FORMATTING] Incorrect text wrapping around drawing shapes
Adding #46509 as the functionality of wiki export is completely broken
Added an annoying installation issue.
.
Nominating bug 35132 - cannot print in landscape in writer
Nominate Bug 44011 - Movie and Sound media inserted into Impress presentations cause Impress to crash when the slide with inserted media is displayed on 32 and 64-bit Windows systems.
Nominate bug 44011, added videos or audio crash impress as soon as a presentation is started. This may be a windows specific issue, but it happens on 32 and 64 bit windows systems. This is a tremendous handicap and makes impress unusable for many.
Adding "Bug 45081 - SLIDESHOW CRASH on slide with embedded / linked video" (replaces Bug 44011)
Add this long standing bug to the list please. <a href="https://bugs.freedesktop.org/show_bug.cgi?id=40421"><b>Bug 40421</b></a> - 3.4.2 Draw with transparent layer loses bezier curves
Add "Bug 40421 - PRINTING shapes with transparent(?) Bitmap background loses bezier curves"
Add "Bug 40958 - EDITING: Copy row to clipboard incomplete ... or: pasting copied row to other rows, makes that data in that row is repeated until the last column"; Calc is more or less unusable for me with tht bug.
Add bug 47370: Base Queries mangle sorting-order when reopening for editing
Add bug 47406: Almost all graphics that have internal circuits is wrongly positioned in ODT import. It is a regression against 3.4.
May I nominate Bug 46020 — "Loss of footnotes when exporting to DOC-File"? A long-standing bug, of course, but IMHO very important, because this kind of silent, not easy to notice, but severe footnote data loss is exactly the kind of problem that could make LibreOffice useless for scientific, Academic and other purposes and could chase out many users if it became public ... (How can I say to my students: "Just use LibreOffice instead of MS Office, it's free and fast, you can save you document as DOC file later, if you ever need to do so", when there is the possibility that some footnotes get lost on DOC export? Then, if I say to a student: "This is a citation but you did not mark it! You made a plagiarism!" the student could just answer: "Oh no, there was footnote giving the complete reference, but LibreOffice must have killed the footnote when I saved the document as DOC file." Even the former German Minister of Defense, Karl Theodor zu Guttenberg, who had to withdraw because he missed so many many many quotation marks and references in his PhD thesis, could excuse himself by saying "I used OpenOffice, and it has killed all the footnotes." ;-)
Great nomination Roman - thanks for that ! :-)
please, consider this bug : https://issues.apache.org/ooo/show_bug.cgi?id=58415 this bug is also in libreoffice and is a very annoying bug...
(In reply to comment #245) @choffardet: Here we only can list LibO Bugzilla bugs. Please check whether that's already reported, if not please file a new LibO Bugzilla Bug!
Nominating Bug 47355. Regression and productivity killer.
(In reply to comment #246) > (In reply to comment #245) > > @choffardet: > Here we only can list LibO Bugzilla bugs. Please check whether that's already > reported, if not please file a new LibO Bugzilla Bug! what about ? https://bugs.freedesktop.org/show_bug.cgi?id=47662
added Bug 33914 - Presenter-Console duplicates (echoes) sound in video
Added Bug 47662 as nominated by choffardet
add Bug fdo#47717 - Paragraph border visible through an image
Sorry -- removed Bug 47662 ("EDITING: Inconsistent / unintuitive reference link handling for check boxes and other form fields when Copying Sheets") again because it is now considered as "enhanchement". BTW: Sortet list of bug numbers to make removing a specific bug easier (the displayed list is sorted anyway, but to remove a specific bug from the comma-separeted list, sorting it makes sense).
Added bug 47355 ("[EDITING] When shrinking an object anchored as character, paragraph below it doesn't update its position") again -- see the convincing comments by Rainer and Josiasmat on the bug report page. This is not a critical bug, right, but really a very annoying on, the workaround is not obvious, and, as Josiasmat put it, "this is the kind of bug that makes one consider going back to M$ Word". At least for beginners and part-time office-suite users, this is definitely true.
Add "Bug 47769 - FILEOPEN particular DOCX 2007 - pictures shown wrongly on page 1", at least also sampld of Bug 47527 affected, might make LibO completely unusable for .docx 2007 with pictures
Add Bug 39887 - Regression: ODT files no longer display in Explorer preview Explorer Preview and Icon thumb also broken in 3.5.2rc1 The Icon Thumb appeared to be working again in 3.4.6
Slide preview (on left side) of Impress not working correctly, all slides except of first looks corrupted: Bug 41261 - UI: Wrong slides preview when images on slide are cropped and scaled
Linux specific regression: Bug 48081 - Impress UI: impossible to select picture using left mouse click
regression in Impress: Bug 48093 - Impress: text in odp file looks incorrect (regression after 3.4.3)
Add 46904: single file collated printing creates broken PDF. This breaks "print to file" and "real" printing.
Add "Bug 44725 - VIEWING: Heading - Footer - Pagebreak lines appear somewhere in the page". It's harmless and acceptable for a x.x.0, but not acceptable for x.x.3 and a daunting view for someone who wants to try LibO. You don't get a second chance at a first impression.
Now really added Bug 44725
Adding bug 46071 - Upgrading from 3.4 to 3.5 breaks Math/Formula Editor
Writer, document with forms: impossible to export to any another format and retain information inside of forms, msOffice opens odt file without forms: Bug 45724 - FILESAVE, FORMATTING, Text field data loss
(almost) all doc files, opened by Writer, contain text approximately on 7% bigger than should be. It breaks layout and page division. Needed manual editing for each file. Bug 47838 - FORMATTING: Writer places text icorrectly in MS Office documents
Added Bug 44861 - Calc EDITING: function Find&Replace behaves incorrectly if regular expressions used. Related to problem of the character "&" at the beginning of the search or replace string.
I nominate "Bug 45340 - LO 3.4.5 Calc fails to print an .xls file correctly." There is a work-around, but out of the box, LO on a Linux machine will fail to print an xls file properly--this is probably frustrating a lot of newbies and gives them the wrong impression of LO.
(In reply to comment #265) > Added Bug 44861 - Calc EDITING: function Find&Replace behaves incorrectly if > regular expressions used. Related to problem of the character "&" at the > beginning of the search or replace string. No, very less number of people use this feature. I think it should be removed. Most important is Bug 32709, and probably the most difficult to fix too.
There're a lot of unconfirmed bugs here, and a lot which actually needs not be here. This should be a place for really annoying bugs.
I don't think these bugs should be added here - Bug 47355 -- the probability of someone placing the picture 'as character' and then resizing the image is very less... very few people are affected by this. Bug 48081 -- 99% of custom animation is used on simple static text. This bug has an easy workaround. Bug 46509 -- No one uses this feature. I don't yet understand how do you use it. Editing wiki directly in wiki's language is easier. Bug 45376 -- not a major problem for many and has a workaround, but cause this already has a patch,...... Bug 45341 -- unused feature. Bug 45171 -- it's not even confirmed. If you want security, encrypt your partitions, or put it in an encrypted archive. Bug 45085 -- not a big problem. Bug 45084 -- rarely used feature. Bug 45049 -- same Bug 44861 -- same Let's process these first.
I would like to nominate bug 48356 (https://bugs.freedesktop.org/show_bug.cgi?id=48356). It makes LO 3.5.x unusable in Eastern European countries when RTF export is concerned (and used). Since a lot of public sector uses rtf of MS Word files, that makes LO 3.5.x a releases very public-image-threatening to LO in these countries (those to decide whether to use open source in public sector, might start saying: "Why use open source if it has such serious bugs that can cause us severe headaches, loss of data?"). Thsnks.
changed importance of bug 45049 to major
(In reply to comment #271) > changed importance of bug 45049 to major Why do you think this's a major issue? Removing other pointed out bugs.
Made changes.
@ dE 1) here placed also regressions, not only annoying bugs 2) developers know what to do. Unimportant bugs they will ignore for now.
@dE I think you should ask advise to the QA team (Reiner & co.) before removing MABs. removing those existing bugs from this page does not solves them.
1) let not flame here 2) deleting something from "Depend on" not very important because: a) bug numbers still seen inside of comments b) most of them are closed because "Duplicate" c) bugreport owners often communicate directly to developers, not via MAB
IMHO, dE did great job. We could discuss particular bugs but some clean up was useful. For example. I am not sure about removing the bug 45171. IMHO, the password protected documents are used by some type of users and it is rather important feature. Other than that, I agree that the removed bugs were not that important and did not belong here. Bugs mentioned here are proceed in two ways: First, comments are send to the mailing list. So, if you mention a bug, it is read by many developers and it might get immediate attention. In this case, it does not matter if you update the dependency or not. Second, it is used for prioritization. Developers can't fix everything immediately. They look here when they finish something and look for another job. In this case, they do not read comments but they check list of opened bugs. So, the dependency, priority, and severity is important. So, we need to keep dependencies, priorities, and severities in a good state. Otherwise, we will end with another swamp where it will be hard to find the important bugs. IMHO, we need not spend too much time on it at this stage because the number of opened bugs is still reasonable low and developers could filter them easily. On the other hand, any clean up is good and we might even need it in the future.
Add "Bug 48778 - FILEOPEN arbitrary.pptx will CRASH", seems we (at least with WIN) lost ability to open that document type (created with MSO)
Hi dE (In reply to comment #269) > I don't think these bugs should be added here - Prolly this is not the best place to discuss. but ... > Bug 47355 -- the probability of someone placing the picture 'as character' and > then resizing the image is very less... very few people are affected by this. Would be my guess too. But a short discussion in the issue decided different.. > Bug 48081 -- 99% of custom animation is used on simple static text. This bug > has an easy workaround. Agree. > Bug 46509 -- No one uses this feature. I don't yet understand how do you use > it. Editing wiki directly in wiki's language is easier. How do you know no one uses this ? > Bug 45376 -- not a major problem for many and has a workaround, but cause this > already has a patch,...... Will be fixed in 3.6 anyway. Maybe in 3.5.x too. > Bug 45341 -- unused feature. How do you know? I agree it's not a MAB, since the use of native field cross-application is limited anyway. > Bug 45171 -- it's not even confirmed. If you want security, encrypt your > partitions, or put it in an encrypted archive. Not a MAB, where so many developers spend attention to this one? > Bug 45085 -- not a big problem. Formattig. Annoying people with existing document ... > Bug 45084 -- rarely used feature. Assigned, devs pay attention too it, and it actually blocks people opening certain files in LibreOffice. Indeed Annoying > Bug 45049 -- same Ah well, a Wordprocessor with broken cross-references.. OK, it's Non-standard caption number, but why would that have be added in the first place? > Bug 44861 -- same If a feature is used more or less, is not the sole scale to measure the annoyancy, IMO ;-)
(In reply to comment #275) > @dE > I think you should ask advise to the QA team (Reiner & co.) before removing > MABs. I think that indeed is the best idea. We have the QA list, and even can ask advise from users and discuss list if we think we got stuck ;-) Anyway, thanks for your thoughts and contribution dE. Cor
Adding again Bug 44861. I ask dE not to remove other people's bugs and not to discuss them here.
(In reply to comment #281) > Adding again Bug 44861. I ask dE not to remove other people's bugs and not to > discuss them here. The title clearly says "LibreOffice 3.5 most annoying bugs"... yours is not even a bug. You simply can't add your personal bugs or feature enhancements here... you gotta think about others also. And this way, the whole bugzilla will be added to the list. We're only interested in bugs which cause data loss, corruption, crashes, and other i/o errors (especially with MS office formats). I think it's time Rainer Bielefeld steps in and advice us what to do.
(In reply to comment #282) > (In reply to comment #281) > > Adding again Bug 44861. I ask dE not to remove other people's bugs and not to > > discuss them here. > > The title clearly says "LibreOffice 3.5 most annoying bugs"... yours is not > even a bug. I think that it is questionable. If it replaces 1345-1430 with 13.45-14..0, it is data loss. If you replace data in large documents and you do not notice, it might be very annoying. Please stop fighting about this bug. We are not in a state where we need to spend time on such long discussions. Developers are clever. They could filter few bugs that does not belong here. After all, this is just a helper bug. It does not enforce any work. It is just a suggestion. > You simply can't add your personal bugs or feature enhancements here... you > gotta think about others also. And this way, the whole bugzilla will be added > to the list. It is not Cor's pet bug. Cor have actively worked on bug triagging for a long time. He has great overview about type of bugs that people report. So, his opinion has some value. Note that nothing is black and white. There might be different views on some things.
First, I thank you all for spotting and fixing all those bugs, and especially for opening bug like this one. What's clear here is that's about bugs, and not enhancements. I'd like to discuss 2 issues, I apologize if it's already been done. 1. "Most annoying bugs" is relative, we don't have all the same opinion about what's most annoying. If it's like this, where is the limit, or this should mean "all bugs"? I'm not aware of some bug that is little annoying and thus not here. My opinion is that all bugs should be tracked, although some minor and hard may not be fixed. 2. "LibreOffice 3.5" has releases. Although in bug itself it can be seen in which release it will be/was fixed, it'd be convenient to see it also here. For example, to see "fixed in 3.5.1", "fixed in 3.5.2", etc below "Depends on". If it's a feature of Bugzilla, there should be some aggregating meta issue there, with that option, for bugs like this one.
IMHO, it currently works the following way: If you add a bug here, you send a message to developers. Hey, this is something that people really hates in this release. It annoys many people and discourage them from using this application. This is something that you should solve ASAP. Developers look at the bugs and fix them if possible. Note that developers are in CC in many other bugs, read mails, have other tasks from other people, have their personal life. They maintain their own priority lists. So, this bug does not enforce anything. It is still only a helper tool. Though, it seems that it works pretty well. My view of why we need this bug: First, any software has bugs and we can't fix everything. Any fix could potentially create another bug. Also we could not make everyone happy. Some people might like a feature that annoys other people. We can't make everything configurable because it would be hard to maintain all options. Even if we make it configurable, people will fight about defaults. So, we will always have any bug reports. Next, this bug won't be needed if people set severity and priority correctly. Unfortunately, it does not work in a real life. If a person gets into a state that she reports a bug, she is often quite annoyed and wants a solution quickly. The bug is often quite important for the person, so she tends to set high severity and priority. One the other hand, some people does not know about this setting and they use the default values. All this can be corrected by people doing the bug triage who see many bugs every day and could better prioritize them. Unfortunately, we do not have enough people this time, so many bugs still have the severity and priority set by the reporter. So the query for all bugs does not show the most annoying bugs on top. Finally, this bug is a workaround for the above problem. It is mostly updated by people doing the regular bug triage. They know the bigger picture and do their best guess what belongs here. They try to do not include their pet bugs. Of course, everyone has its own opinion. Also this bug is opened for anyone. Well, I think that it has worked quite well so far and we do not need any complex rules. IMHO, the name "most annoying bugs" set the right feeling in most people ;-)
If we want to keep it working, we need to keep a balance. If we mention too many bugs here, we will create another swamp of ideas and developers will ignore it. I am not sure where are the limits. IMHO, it somehow works now, so we do not need any regulation at this stage. In each case, fights about each bug are rather contra-productive. It is better to fix them than discuss their priorities ;-)
@ Timur > 2. "LibreOffice 3.5" has releases. Although in bug itself it can be seen We can see bug title when place mouse cursor over bug numbers in field "Depends on". Expected version, where bug will not exist may be added to end of titles of mentioned bugs. But it is much to work.
Hi Timar, (In reply to comment #284) > 1. "Most annoying bugs" is relative, we don't have all the same opinion about Yes, so the one acting with code (fixing a bug) decides. > My opinion is that all bugs should be tracked, although some minor and > hard may not be fixed. All are tracked. In bugzilla. > 2. "LibreOffice 3.5" has releases. Although in bug itself it can be seen in > which release it will be/was fixed, it'd be convenient to see it also here. In addition to what others said: the release notes give a list of fixed bugs.
Should I add more bugs (I can easily add a 100 more).
Yes, but preferred that only one bug per day. We should have time to think on one bug before appears another
(In reply to comment #289) > Should I add more bugs (I can easily add a 100 more). Yes and no. Bugs that belong here, pls do. However: I do not believe in doing it 'easily'. Since, steps in the correct work flow are: - reproduce, - test impact, workarounds, - query BugZilla for related and the same or closely related issues which may lead to do some bundling of issues - in case of doubt, consult others via the QA list.... But any bug that is really a problem, and that is not yet visible here: pls do. We have had issues in the past, that were in BugZilla for months, turned out to be very nasty, and were not recognised fast enough, but discovered just because I (or someone else) was confronted with a similar problem and did "the work" in BugZilla. So finding those bugs, is important and more helpful than adding just a load of bug numbers to this MAB. Thanks for your help!
@dE, Sasha, Cor: For discussions we have <libreoffice@lists.freedesktop.org>, please stop discussion here immediately! Same concerning discussion concerning relevance of bugs, discuss that in the bugs, not here. Tis Bug is only to be used for purposes as per Petr's report. All those 28 Users listed in CC do not want to read any of your thoughts!
I suggest removal of - Bug 34380 Bug 34436 bug 41261 See my comments in the above bugs for the reason why.
Added Bug 46805 - large autocorrect database make LibO freeze when start typing
Propose Bug 47777 Can cause serious annoyance to people distributing pdf docs created from LibO Writer. See example inside bug report.
Hello, I'd like to propose bug 38176 FILEOPEN, FILESAVE, FORMATTING in RTF with non-breaking spaces https://bugs.freedesktop.org/show_bug.cgi?id=38176 It is very complicated to edit RTF file with non-breaking spaces because a normal space is added just after each non-breaking space. Non-breaking space is quite common in French text, as there is one before each double punctuation: ':' ';' '?' '!'
Added bug 38176 As said by Laurent, this bug make RTF export unusable for French documents.
add Bug 45019 - FILEOPEN Password protected file opens in background (visible on task bar / invisible in Unity)
Nominate https://bugs.freedesktop.org/show_bug.cgi?id=46160 - Time lag makes Calc unusable for many business spreadsheets.
Add "Bug 49342 - CRASH EDITING TABLE when merge cells in .sxw" because of crash
I would like to nominate bug 39791. Reason: there is a large number of Libreoffice corporate deployments. A number of them, including my own, has a mixed environment which includes MS Office alongside LibO/Oo. Group policy-made deployments at LibO 3.4 broke, with LibO stealing associations from MS Office for Word files (.doc / .otx). As an example, on my 300-pc installation I rolled back to Oo, till this issue is solved. Unfortunately, issue persists on 3.5 Summarizing: bug 39791 is a blocker (IMHO always) for corporate installations.
adding Bug 49350 - freeze when saving new entry to a large autocorrect replacement table
Add "Bug 49545 - EDITING: CRASH when add custom animation to media (Movie, Sound)"
I added bug 35427 - Impossible to hide horizontal scrollbar in writer when zoom is over 100%. It's very annoying for users working with 'optimal zoom' on a small screen.
rtf files open corrupted. Seriously regression. Bug 45190
Add "Bug 49760 - Error during Installation, Error 1335", we have 2 DUPs, so I doubt that those are random problems.
Add "Bug 30920 - closing the license document closes LibO". I doubt that that crashes cause much problems, but it's a crash at a very visible place an can be used for malicious-joy, scorn and ridicule
removing feature bug from MAB list
Add 49522 - scrolling is broken in Base. Data are duplicated in fields.
Replacing bug 49522 by bug 48345 of which it is a duplicate.
added Bug 33484 - Printing multiple files from Windows Explorer at once makes LibreOffice unusable
Nominating bug 48039. Haven't seen working cross-references in quite a while.
Nominating bug 35079. This is a severe regression for all of us heavily using Draw. This regression appeared during the 3.3 developement cycle and is still present in LibO 3.5.3. moggi told me on IRC to add it here.
Nominating bug 37606 - Writer: Select All doesn't work on a document beginning with a table. It is a very old issue from OpenOffice.org. I guess it's not hard to fix.
(In reply to comment #314) > Nominating bug 37606 - Writer: Select All doesn't work on a document beginning > with a table. It is a very old issue from OpenOffice.org. I guess it's not hard > to fix. Sorry, but I removed this one. Just being an old OOo bug does not qualify for 'most annoying'. We could use an extra storage in that cast ;-)
Nominate bug 39007 - "Persistent 'Restore Windows' dialog won't disappear, disables key functionality." I know this bug is only present on one platform (MacOS X), and there is a workaround for it, but that workaround is not easy and the complete issue is particular "annoying" in the lexical meaning: this bug has the potential to drive ordinary (real!) users crazy ;-)
(In reply to comment 315) Cor, it seems that you and me have different perception of annoying bugs. I'll quote a comment from bug 35673 which describes my perception: > Then the task should be called "Most annoying major new bugs". This > bug is annoying, and the fact that it's old makes it more annoying, > not less annoying.
Add "Bug 50396 - EDITING: grouped shapes drawings become distorted", this one makes LibO DRAW completely unusable for me. Unfortunately it seems very difficult to reproduce the bug.
Add "50399 - FILESAVE document created with 3.4.5 destroys grouped elements for 3.4 VIEWING". Dataloss when interchange between versions.
Add bug 50415: Shortcut names are not localized on Linux; regression in 3.5.4; it worked well in 3.5.3
Add "Bug 45260 - EDITING: Pasted object not same position w.r.t. original object if border thickness greater 0". This bug makes DRAW completely unusable for technical sketches. Although there is a simple workaround (use AOOo3.4) we need a fix for this bug.
suggesting 50676 as it makes LibreOffice hardly usable for Chinese users.
Nominate Bug 46480 (Calc cannot filter data from the data source). This bug makes it impossible to draw data from a database and use that data in any helpful way in Calc, and there is no workaround. It is for this reason that my office has not been able to upgrade to LibO 3.5 at all. It looks to be a regression to a prior bug that may have been present in LibO 3.3.4.
I nominate Bug 49582 - FILESAVE: Long delays saving in XP .XLS format. Save as xls/xlsx with table column line must be possible.
I nominate Bug 42092 (SVG in PDF becomes Bitmap), because many business letters contain SVG-logos and cannot be converted to pdf any more.
(Reset Importance pickers after accidental change.)
(Bug 49610 should be in the "Depends on" list, not in the "Blocks" list. Therefore corrected.)
(In reply to comment #323) > Nominate Bug 46480 (Calc cannot filter data from the data source). This bug > makes it impossible to draw data from a database and use that data in any > helpful way in Calc, and there is no workaround. It is for this reason that my > office has not been able to upgrade to LibO 3.5 at all. It looks to be a > regression to a prior bug that may have been present in LibO 3.3.4. ok, added.
Added 40481 50509 46508 46510 of which only 46510 is still unresolved.
Nominating 49610: EDITING: Terminating 'Find' when reached end of document second time deletes slides, replaces contents by templates Nominated because many users use Find feature and would be affected if slides were deleted. Loss of data = really annoying ;)
bugzilla-daemon@freedesktop.org schrieb: > Nominating 49610: EDITING: Terminating 'Find' when reached end of document > second time deletes slides, replaces contents by templates Hi, you are a little late, and: <http://wiki.documentfoundation.org/QA-FAQ#How_to_ad_Bugs_to_MAB_Tracking_Bugs> Best Regards Rainer
I nominate again Bug 47355. There are daily duplicated reports for this nasty regression bug.
Add "Bug 51232 - EDITING: CRASH when paste in outline view after SLIDESHOW" because of crash
Add "Bug 51247 - EDITING: CRASH when modify Text Anmiation properties to "As one object" and check "Animate attached shape" option": rather unplausible user scenario, but crash!
Add "Bug 51253 - EDITING: CRASH when undo leads to a deleted style". Crash with rather normal proceeding
Added bug 51023 - "EDITING: Drag-and-drop slide sorting broken on Mac OS X, leading to data corruption and crashes". This bug seems to be limited to MacOS X for now, but is still really annoying and urgent: * it makes sorting slides in Impress completely impossible, * it leads to data corruption of a serious kind * and even to crashes. * Additionally, it is an regression introduced in LibreOffice 3.5.x. There are some reports about Drag-and-drop slide sorting not working on Linux, which could be related, so looking into this issue may also help to fix these Linux issues (and the other way around).
Add "Bug 46099 - Missing Search and Replace shortcut": If you use LibO for WORK that's worse than plague
Adding #51618, nasty crash and regression over 3.5.4 when opening a report based on a parameterized query on Linux 64bit
Sorry, that should read #51619 Alex
Add "Bug 36149 - CRASH hovering over Menu "File > Send" if no JRE is available and MediaWiki Publisher installed". We can't terminate 3.5 before this has been fixed.
bug 51239: embedded hsqldb too slow (regression)
I have resisted for a long time, but finally I have to nominate bug 47368 - "Many crashes when accessibility enabled on Mac". I have resisted for a long time, because this is not an easy candidate: * the problem is limited to a single platform (MacOS X); * it is not always reproducible out of the box; * it is not clear where the problem comes from, i.e. if the bug is in our code or in Apple's code. But nevertheless, it is definitely a "most annoying bug", and so I *have* to nominate it: * it affects quite more users than you may think (see the duplicates listed in bug 47368; and there are even more similar bug reports which are just not marked as duplicates of bug 47368!) * it causes crashes about crashes for the users which suffer from it; * these crashes appear in many different actions, giving our users the (wrong) impression that every piece of LibreOffice was unstable; * therefore this bug has the potential to drive users crazy; * and to make them leave LibreOffice once and for good. You may object: "We have an easy workaround: just disable the MacOS accessibility features, and LibreOffice is stable again"; this is true, but IMHO it does not make this bug less annoying: * It is very difficult for "normal" users to discover any connection between the crashes in LibreOffice and the MacOS accessibility features, * therefore "normal" users will not discover the workaround easily; * we, the QA volunteers, have to ask people again and again to check their accessibility settings, which shows that people even forget about these settings (and therefore will not use the workaround, even if we list it in the release notes and read_me files); * for many people which are physically disabled/handicapped in one or the other way the accessibility features are vitally necessary, so they just CAN NOT disable them * and have to leave LibreOffice instead; * therefore this workaround is NOT a workaround for them. In addition, it gives me a rather bad feeling about LibreOffice that we unwillingly discriminate people (physically disabled/handicapped people) which are already discriminated by our way of live in many ways. This is a bad thing to do for free and open software -- it should be free and open also in the meaning of being easily accessible and usable for as many people as possible. Therefore, we need to track down this issue some day. Even if we can't fix it because the problem is in Apple's code (I don't believe this, because many other applications seem to work fine with accessibility features enabled, including other office applications!), we need to find out about this, either in order to fix it (together with Apple) or at least to explain to our users that the crashes are not our fault. Sorry for this rant -- no offence! -- I just wanted to state clearly why this bug, even being limited to a single platform and not easy to track down, is nevertheless an important (!) candidate for our "most annoying bugs" list. So please don't remove it from this list, but let's think together about what we can to do to solve this issue.
Hi Roman, > I have resisted for a long time, but finally I have to nominate bug 47368 - > "Many crashes when accessibility enabled on Mac". Please don't resist so long - it's good to make these visible, even if they are ill-formed and hard to fix; the video in that bug is amazing :-) clearly we need to address this. It is possible of course that the bug is in OS/X - but if so we need to work out which versions of it - and then blacklist a11y only for those versions (if there is a consistent pattern there it'd be good to build data for that). Thanks for raising it :-)
add linked slide editing / potential data-loss ergonomic issue from 3.6 tracker - that is not specific to 3.6
Nominate Bug 51508 - Impossible to use Writer OLE object in drawing or presentation due to uncontrollable size and position. This is regression bug and it makes completely impossible to use releases after 3.3.4 if you need to have Writer OLE objects in your documents.
Add "Bug 52108 - CRASH on any action for particular big .odt". 7000 pages document is nothing affecting many users, but we had it working in 3.4, and who can know whether we also have an increased vulnerability with some hundreds pages documents?
Add "Bug 51034 - FILESAVE: # in hyperlink corrupts .docx (MSO2007) document": Dataloss Regression.
Add win32 specific crash loading Danish dictionary during startup after upgrade bug#38913 - sounds bad.
nominate bug 52433 : memory leak, crash under XP.
Bug 34467 - "FORMATTING Fit to Frame for text boxes is broken" should be removed from "LibreOffice 3.6 most annoying bugs" (bug 44446) and added here, because this bug goes back to LibreOffice 3.3.0.
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)
Add "Bug 46249 - CRASH when browse to HD root directory in FILEOPEN Template dialog": Crash, Regression, several DUPs
I deleted Bug36547 (DUPLICATE of Bug33591), added Bug33591 (FIXED), deleted Bug45078 (DUPLICATE of Bug40289), added Bug40289 (NEW).
Add "Bug 42939 - SVG Export ignores line width", currently SVG export is completely unusable.
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.
Add https://bugs.freedesktop.org/show_bug.cgi?id=52080 - Large files become unresponsive since version 3.5.0. Regression - working with large files was fine with Writer in the 3.4 series, now broken.
I'd like to nominate <a href="https://bugs.freedesktop.org/show_bug.cgi?id=48828">Bug 48828</a> as it actually corrupts document content. This was still an issue with 3.5.5 and is also an issue with 3.6.0
(In reply to comment #358) > I'd like to nominate <a > href="https://bugs.freedesktop.org/show_bug.cgi?id=48828">Bug 48828</a> as it > actually corrupts document content. This was still an issue with 3.5.5 and is > also an issue with 3.6.0 added
Add "Bug 54214 - FILESAVE: # in hyperlink corrupts .docx (OOXML) document", destroys documents, dataloss, similar to also listed Bug 51034
For the record: Sasha has added bug 35991 -- "merged cells in tables in DOC files not saved correctly by Writer on Linux 64bit".
I am adding #38606: "Under Style and Formatting, clicking Apply always resets to initial tab". If I understand correctly, no one worked on this, because there are plans to redesign style modification dialogs, and chances are that "Apply" button will be removed. But this redesign will happen in 3.7 at best, which is around six months from now. This bug has been opened for over a year. Instead of having users waiting next half year, please fix it in at least 3.6 branch.
Add bug 50284 - "FILEOPEN .doc/.docx (MSO2007) Bullet lists show wrong bullet symbols MacOS X". Rationale: This is a follow-up of the long-standing bug 34814, which was finally fixed in LibO 3.5.4. Since this fix, bullet lists are imported correctly from .doc/.docx files in LibO on Windows and Linux -- but still not on Mac OS X. For this special case (bullet lists still wrong on Mac OS X), the special bug 50284 was filed. Now bug 34814 was a MAB; therefore, bug 50284, which is about the same problem, just limited now to a single platform, must be a MAB, too. Additionally, cf. the user comments in bug 50284, e.g. comment 18 and 30.
bug 53557, base crasher on any calculated field
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).
Bug Proposal - Calc is too slow to open and work with big datasheet file Since I can't find any related bug so far, is there any bug open for this problem? The problem is simple, the file as 30,5Mb and almost 150,000 lines, with data from the last two years. It takes a lot to open and its very frustrating working this the filters (it takes to long just to open the menu). This has been reported to me since OOo 2.1 and only now I had access to a so large file at the enterprise I work. I want to start to migrate some office suites, but this bug is pulling the project out. I can prepare a file to share if needed.
Added Bug 40594 - "Charts embedded in .docx files are absent when opened in LibreOffice Writer"
Added Bug 53872 - "CRASH - opening database report" (was a 3.6/3.7 MAB, but is now already reproducible in LibO 3.5 daily, therefore moved to this list).
Add "Bug 48775 - CRASH when opening biblio.odb via tools menu without Base module installed", way to fix this one might lead via fix for Bug 54479 - CONFIGURATION: Menu 'Tools - (open) Bibliography Database', although Base not installed
Nominating 48569 as a MAB. Document shows instance of document crashing when saved as .docx, potential for loss of data is high.
Added Bug 35568 - "QuickStarter setting not remembered after upgrade" because it's required for a resolved Bug 46510 - "Turn on Quickstarter by silent install" to work.
Nominating fdo#50285 https://bugs.freedesktop.org/show_bug.cgi?id=50285 This bug has the potential of really creating an unprofessional document. This could be a real problem for business people or students if they save as a document and then submit the work as it completely changes the text.
Remove chart printing bug, as it is a feature request and has no place here. --- Please note that this doesn't mean the bug isn't important in its own right, but it is not a crasher, not a data loss bug and also not a small/big annoyance that's easy to turn off.
Bug 53340 is a change in Impress from 3.4.x which negatively impacts existing slides which are subsequently edited using 3.5.x: the available text area is reduced for any newly inserted slide creating an inconsistency with other slides in a slide set. Thus I think we have a regression. Problem also exists in 3.6.x.
Added Bug 48279 - autocorrect limit. acor.dat with entry 65535: Loop and/or loss of acor data. IMHO this is very annoying since the 65K limit of autocorrect entries is something that sooner or later any user will face and the after reaching that limit the autocorrect database will be reset to 0 loosing all entries collected. it seems the 65K limit is related to 16-bit encoding... is there any chance to raise this limit from 16^2 to 20^2 or 32^2 ? something similar was done in Calc to allow more than 65K columns (actually I think it can handle 1 million)
s(In reply to comment #376) > Added Bug 48279 - autocorrect limit. acor.dat with entry 65535: Loop and/or > loss of acor data. > sorry, I meant Added Bug 48729 - autocorrect limit. acor.dat with entry 65535: Loop and/or loss of acor data.
move bug#36815 (comment printing) from 3.7 MAB to here where it belongs.
Bug 50542 Showstopper bug for upgrade to LO 3.5/3.6 in some enterprise deployments that store user data in central file servers.
For the record: Lionel Elie Mamane has added * Bug 54930 - “EDITING Report builder: mouse-resize control allows to move top of control to out of section” * Bug 54933 - “EDITING Report builder: mouse-move control: gap between mouse position”
Added bug 53365 – DOCX file is opened properly but is re-saved to native LibreOffice ODT with mistakes and with missing formulas.
Add "Bug 55042 - No WINDOWS daily builds available for QA", without daily builds for 3.5 latest fixes for 3.5.7 can not be verified by QA
LibreOffice 3.5.4.2 When saving to *XML.docx (other save formats not usable), Paragraph > Borders > "Spacing to Contents" Settings are lost (not saved, or not read on re-open?) when the document is re-opened.
LibreOffice 3.5.4.2 When saving to *XML.docx (other save formats not usable), Imported graphic image lost; but place holder remains.
@Lou Vaughn please, cite an existing Bug number or in case it does not exist yet, file a new bug report with steps to reproduce and test documents.
As suggested by Timon in https://bugs.freedesktop.org/show_bug.cgi?id=44446#c137, I add bug 50774 -- “Incorrect numbering of paragraphs in docx document”. Makes LibO unsuitable for academic etc. usage.
If we speak about academic usage, then there is another Bug 53961 with OLE https://bugs.freedesktop.org/show_bug.cgi?id=53961 It also present in AOO and confirmed there https://issues.apache.org/ooo/show_bug.cgi?id=120678 This bug affects LibO 3.5, 3.6; AOO 3.4; may be other LibO and AOO more old versions
Adding bug 55786 fileopen read error on older Lotus 123 files. Add it here because already not working in 3.5.5.
Add Bug 56009 In Calc, object anchored to cell are moved to A1. Same as Bug 54695 which was corrected for LibO 3.6.2.
Added Bug 45495, because youre in trouble when you have to hold your slideshow and saved as pptx for that and this bug will appear on nearly any pptx show to a certain degree.
Adding 52392 - Biliography database is screwed. New entries to bibliography database cause random illegible data to be written to unfilled fields which then display both in the table view and any use of the biblio db in documents, e.g. for creating a bibliographic index. Alex
(In reply to comment #391) > Adding 52392 - Biliography database is screwed. New entries to bibliography > database cause random illegible data to be written to unfilled fields which > then display both in the table view and any use of the biblio db in > documents, e.g. for creating a bibliographic index. > > > Alex Bug 52392
add image cropping annoyance mis-added to 4.0
Added bug 42134 - FORMATTING: Autofit doesn't work properly on long texts This is terribly annoying for me: with longer lines, part of or all of the text in a text frame regularly gets squeezed together so the text becomes illegible. Workaround is to disable Autofit completely.
I would guess that bug 54933 is meant to be in the “Depends on” field, not in the “Blocks” list, isn’t it?!
Added bug 53909 - “FILEOPEN Word 97-2003 DOC structure is not recognized”. A regression, very important, introduced somewhere in the 3.6 development process and then backported to the 3.5 branch. According to my tests, the backporting was done between the releases of 3.5.5.3 and 3.5.6.2; this is a fairly limited range of commits which need to be checked. [I thought that this (3.5) list was more or less closed, but it seems to be still alive, therefore I add the bug to this (3.5) list, not to the 3.6 list ;-) Correct me if I am wrong ...]
Shouldn't be WONTFIX already?
@Urmas if I remember correctly I read on the dev list that Reiner and the QA team will probably review all the opened 3.5 MABs before the end of the year and then the still valid bugs to the 3.6 MAB list. a similar job was already done in the past when 3.4.x cicle ended and all the survivor MABs were shifted to the 3.5.x list
For the record: Norbert Scheibner has added * Bug 40788 - “FORMATTING - Calc ignores manual breaks when ‘fit to number of pages’ is chosen” Definitely a disputed case, but I agree that we need at least more consistency in manual breaks handling in Calc, so this seems a valid nomination.
Nominate https://bugs.freedesktop.org/show_bug.cgi?id=37814 (FILESAVE Save/Save As dialogs use last save folder (not original) with non-ascii path) Really annoying issue causing documents loss.
Removing Bug 53340 as it was marked as a DUPLICATE of bug 34987, and adding the later.
Is it possible to have some feedback about this very annoying bug about "incorrect cross-references in Master/Sub-document"? https://bugs.freedesktop.org/show_bug.cgi?id=48039 https://bugs.freedesktop.org/show_bug.cgi?id=35669 These two bug reports echo only users comments for several months, and it is still broken. Thanks in advance.
@nomnex - we try not to bump bugs in MAB or discuss them here in the comments. If a bug is already on MAB list, we do ALL discussion on the bug itself, not in the meta tracker. Thanks!
(In reply to comment #403) > @nomnex - we try not to bump bugs in MAB or discuss them here in the > comments. Yes, sorry about that.
And with that last bug removed from 3.5 MAB -- Set status to CLOSED/FIXED, in order to make it really obvious (especially for beginners) that no more bugs should be added to this tracking bug.
Really mark as CLOSED. Also add accidentally-removed mab3.6 back to 'See Also'.
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.5 STATS ...................... fixed bugs -> 215 open bugs -> 0 ......................