This is the Meta issue to track most annoying bugs for the release of LibO 3.4.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 35671. Wiki help does not show the right pages and thus is hard to use.
Depending on failing complex and unoapi tests: 35660, 35661, 35662, 35663, 35666, 35667.
@Björn: Can you please explain why you see bugs nominated by you as "most annoying ... that are important for users"?
35602: Reason is quite clear. I personaly know three people who have lost their hours of work.
@Rainer: please see http://lists.freedesktop.org/archives/libreoffice/2011-March/009626.html 35668 is a well reproducible crasher and should be fixed in any case. The others are not that critical IMHO, but keeping the complex and unoapi tests clean is a very valid goal. Luckily, because there are tests for these, they should be rather easy to fix.
(In reply to comment #5) > please see > http://lists.freedesktop.org/archives/libreoffice/2011-March/009626.html I see that Michael actually suggested to link the bugs here ;-) > 35668 is a well reproducible crasher and should be fixed in any case. > > The others are not that critical IMHO, but keeping the complex and unoapi tests > clean is a very valid goal. Luckily, because there are tests for these, they > should be rather easy to fix. Well, I would prefer to link here only bugs that really annoys people and breaks their daily work. Otherwise, we would end up with all bugs linked here and the purpose of the meta bug would be gone ;-) If you are going to fix them any time soon or you think that they point to serious problems, feel free to keep them linked.
Removed all bugs but 35668 here as they seem not absolutely critical. All subsequenttest bugs have now their own metabug: https://bugs.freedesktop.org/show_bug.cgi?id=35690 (added as "see also:" URL)
Nominating: Bug 31606-PRINTING selected pages of long documents pick up the wrong pagerange It's really a pain to have a text processor that has difficulties (or better: is not able) to print correctly selected pages
I would like to nominate: Bug 34814 "Bullet lists in .docx are loaded incorrectly", it already has some patches that need to be tested.
Please add: https://bugs.freedesktop.org/show_bug.cgi?id=33522 [CALC] [PRINT] Option “Print only selected sheets” does not work in “Page Preview” mode A large number of pages can be involuntarily printed instead of a single page (Very boring when the printer is in another room).
I would like to nominate bug 33463 [.docx no comments saved] as replacement for bug 35602 (cf. comment 4). (Both bugs are the same, except that the latter has now been marked as duplicate of the former. Hence, the latter (bug 35602) appears as CLOSED in the dependency list.)
Well, bug 33522 being a duplicate of bug 32826, I would like nominate bug 32826 for the same reason : "A large number of pages can be involuntarily printed instead of a single page (Very boring when the printer is in another room)".
bug 35345 (Cells hidden with filters get changed) A user unaware of the problem can lose data, as the expected behavior when you filter is that the hidden cells don't get modified.
Add bug #36045: LO does not allow to insert any media
Accepted bug #34814. Broken bullets DOCX import. Well, AFAIK this might be a bit complicated.
(In reply to comment #13) > bug 35345 (Cells hidden with filters get changed) > > A user unaware of the problem can lose data, as the expected behavior when you > filter is that the hidden cells don't get modified. This is a feature request thus should not be considered a stopper bug. Plus this requires non-trivial change, too risky for 3.4 especially after the feature freeze.
(In reply to comment #16) > This is a feature request thus should not be considered a stopper bug. Plus > this requires non-trivial change, too risky for 3.4 especially after the > feature freeze. Hmm... actually on 2nd look, this may be a bug.
(In reply to comment #17) > (In reply to comment #16) > > > This is a feature request thus should not be considered a stopper bug. Plus > > this requires non-trivial change, too risky for 3.4 especially after the > > feature freeze. > > Hmm... actually on 2nd look, this may be a bug. And there is a patch in OpenOffice. From http://openoffice.org/bugzilla/show_bug.cgi?id=89232#c27: "Fixed in CWS calc66, based on a patch from the IBM Symphony team. Filtered rows are skipped, and if there are filtered rows, the default is copying instead of incrementing."
Bug 35017: LibreOffice resets all information about user assigned keyboard shortcuts while start. Users therefore can not assign any keyboard shortcuts permanently.
Add bug 33915: user settings get lost after several restarts; It is quite annoying. Unfortunately, it is hard to fix because we still do not have a reasonable way to reproduce it.
Added bug 36262 to undo BrOffice modifications and return to LibreOffice for the Brazilian locale.
Nominate: Bug 36263 - No icons in user interface That's a heavy blocker
Nominate: Bug 36271 Writer won't open for people on Windows. Blocker bugs don't get more severe than this.
Nominate: Bug 36284 LO won't save files. This is a very serious blocker.
Nominate: Bug 36320 Impossible to open an existing file (odt, ods, odg, odp) via Startcenter or Menu > Open (Writer, Calc, Draw, Impress)
Checkboxes missing from Options panel - makes the options panel completely unusable.
Nominating Bug 36285 - LibO 3.4 beta1 – No available language modules, spell check is impossible We can't ship a text processor without working spellchecker
Added bug https://bugs.freedesktop.org/show_bug.cgi?id=36404 More than one text cursor at the same time in textfields in dialog boxes. This bug occur on all dialog boxes who have more than one textfields.
Really add bug 36404.
https://bugs.freedesktop.org/show_bug.cgi?id=32672 no chance to get DBF-files to work as dataexchange-format, This bug: LO corruptes N0-field, which were used as counters, and will cause dataloss in foreign (non-LO) application on data-export. Martin
Bug 36301 You can't ship a program that crashes on exit every time.
Nominating Bug 32899. A feature in completely broken. Already fixed in OpenOffice.org
Nominate: Bug 36524 - EDITING: Delete Index causes crash I believe 3.4 can't be shipped with this crash
Nominating Bug 36481 as stopper. Serious spinbox defect under Windows.
36551 surely is a blocker, as the user must be able to install 3.4.0 when the user already was a user of LO 3.3.2, either as update (i.e. removes 3.3.2) or alongside 3.3.2 (having both 3.3.2 as well as 3.4.0 installed)
Bug 34910 langpack becomes several times larger and has problem with installation (because one file already installed)
Seeing as this is an annoying bug list and not a blocker bug list, I'd like to nominate Bug 36439 as an annoying bug. Since it involves a new feature, I think new features should work correctly before shipping a new product.
(In reply to comment #30) > https://bugs.freedesktop.org/show_bug.cgi?id=32672 > no chance to get DBF-files to work as dataexchange-format, > This bug: LO corruptes N0-field, which were used as counters, and will cause > dataloss in foreign (non-LO) application on data-export. Sounds serious, so added the bug to the list.
(In reply to comment #36) > Bug 34910 langpack becomes several times larger and has problem with > installation (because one file already installed) It affects more locations and should get fixed => adding to the list
Bug 36613. It's a regressive bug that's annoying but certainly not a blocker. If people vehemently disagree with adding this bug to the list feel free to remove it.
Bug 36615. Regressive bug that is very annoying.
Adding Bug 36275 - LibO 3.4b1-b2 fails to start with "symbol lookup error": undefined symbol: sal_detail_initialize. Bugs don't get much more serious that the program failing to start at all.
Nominating Bug 36678 - Missing user-defined dictionaries with a specified language attribute via "Spelling and Grammar" <F7> You cannot add a word to user-defined dictionaries with a specified language attribute via "Spelling and Grammar" <F7>.
Nominating "Bug 36571 - Find bar does not appear properly at top of screen". This one can really drive you crazy by messing up all toolbars until you will have learned that docking to the bottom will solve the problem.
Please look at bug 36547: a very annoying compatibility problem with openoffice .odp files...
Nominate: "Bug 36684 - UI: Menu 'View> Toolbars' relations to toolbars messed up". We can not shil 3.4 with that bug.
Nominating Bug 36662. "Right click > Wrap" over an image has missing icons. This is not only cosmetic, but it prevents to understand the option status.
Nominating Bug 36667. Function result update in Writer is broken. Regression form 3.3.2
There are a number of bugs here that are long standing, and not regressions, so - annoying as they are I don't believe we should really focus on fixing them for 3.4: bug #32672, bug #32862, bug #34814, bug #36547 So - I nominate them for removal :-)
Add bug #35554: GNOME integration still does not work with 3.4.0-beta3.
Add bug #36802: the built-in testtool.bin crashes
Consider Bug 35706 – Ctrl F, Ctrl Alt F doesn't work in Basic IDE Also, in Draw and Writer components, when the Draw panel is active, the Find toolbar doesn't have enough space whith Default icons and 1280*800 screen resolution. IMHO, this patch is not stable for release yet. Also note these Basic IDE bugs: https://bugs.freedesktop.org/show_bug.cgi?id=30545#c7 And this bug: Bug 35480 – Curves have round control points with black background (the solution is to use the picture markers2.png from hg.services.openoffice.org or to save it with options given in the bug) The fix for the filter would be better, but as far as it is not fixed, IMHO, the picture should be fixed, because it is publicly visible contrary to the hidden bug with PNG exporting that appears in very rare cases.
I would like nominate bug 36519 : it is may be received as a very bad signal by ODF adepts.
Nominate "Bug 36820 - PDF export with option "Tagged PDF" crashes for particular big complex WRITER documents". I prefer to nominate only confirmed reports, but the performance of UNCONFIRMED confirming still is lousy ...
Nominating bug 36676. Paragraph borders disappear when adding background to paragraph style.
(In reply to comment #52) > Consider Bug 35706 – Ctrl F, Ctrl Alt F doesn't work in Basic IDE accepted > Also, in Draw and Writer components, when the Draw panel is active, the Find > toolbar doesn't have enough space whith Default icons and 1280*800 screen > resolution. IMHO, this patch is not stable for release yet. Is there any bug number for this? > Also note these Basic IDE bugs: > https://bugs.freedesktop.org/show_bug.cgi?id=30545#c7 I suggest to open separate bugs for the problems. In general, it is a bad idea to discuss to many problems in a single bug. It usually results in a mess. It takes a long to read the history. It is easy to miss important information or lost track of what is fixed and what still need to be fixed, ... Short and clear bugs usually more motivates developers to work on them. > And this bug: Bug 35480 – Curves have round control points with black > background It is a minor issue, no duplicates, no other interested people in CC (except for two developres). I am sorry but it does not fit into the group of most annoying bugs. > (the solution is to use the picture markers2.png from > hg.services.openoffice.org or to save it with options given in the bug) The fix > for the filter would be better, but as far as it is not fixed, IMHO, the > picture should be fixed, because it is publicly visible contrary to the hidden > bug with PNG exporting that appears in very rare cases. This is not the right place to discuss solution of a particular bug. It is better to add comment to the bug.
(In reply to comment #56) > > Is there any bug number for this? > No. > > Also note these Basic IDE bugs: > > https://bugs.freedesktop.org/show_bug.cgi?id=30545#c7 > > I suggest to open separate bugs for the problems. In general, it is a bad idea > to discuss to many problems in a single bug. It usually results in a mess. It > takes a long to read the history. It is easy to miss important information or > lost track of what is fixed and what still need to be fixed, ... Short and > clear bugs usually more motivates developers to work on them. > Bug 36831, Bug 36832, Bug 36833, Bug 36834, Bug 36835
Add bug 36838: soffice/oosplash.bin does not process relative paths to documents
(In reply to comment #49) > There are a number of bugs here that are long standing, [...] On <http://wiki.documentfoundation.org/Release_Criteria#Blocker_Bug_Nomination> this bug is listed as blocker tracking task, and I believe we should - "redefine" it as a 3.4.0 blocker tracking task - remove bugs that do not fulfill blocker definition with a pseudo keyword in the whiteboard "former 3.4 mab" (or similar), because most of them are not really blockers, but may be bugs with superior severity, so that tracking of them can be continued easily Currently we have several bugs without any realistic chance to be fixed in 3.4. listed here, I see your proposals as such ones (may be except "Bug 34814 - Bullet lists in .docx are loaded incorrectly", IMHO. I agree with your suggestion. Additional candidates for removal IMHO might be: Bug 36613 - LO 3.4 Beta 2 - Hover over icons produces the wrong behavior Bug 35706 - Ctrl F, Ctrl Alt F doesn't work in Basic IDE in LibO version dev300m103 Bug 35017 - Shortcuts that can not be modified permanently should be marked Bug 36262 - Undo BrOffice, return to LibreOffice Bug 36439 - Find Toolbar won't close if left open Bug 36519 - For default saving options, ODF format is replaced by the filter names (writer8, calc8, etc.) Bug 36547 - Impress: Rendering problems with some .odp files Bug 36551 - 3.4beta2 can neither be installed as update to 3.3.2 nor alongside 3.3.2 because of packaging conflicts Bug 36676 - sourroundig lines in paragraphs are missing Bug 36662 - Missing icons (option controls) in right click > Wrap over an image Bug 36613 - LO 3.4 Beta 2 - Hover over icons produces the wrong behavior
This could be a stopper (if confirmed): Bug 36816 – Document statistics: Paragraph Count doesn't work
Nominating bug 36306 Alex
Nominating 36483, the Address Datasource wizard no longer works, a regression compared to LibO 3.3.2. Alex
Sorry, my bad mixed up 4 and 8 in bug number dependencies, corrected now. Alex
Nominating bug 36848. Named range can not be selected with Name Box. Regression
Nominating Bug 36863. [Math] Crash updating formula. Crash and regression
add #36898 : dir() function broken
propose #36673 formatting of Dates in spreadsheet changed
nominating bug #36903 as it is a nasty regression
Nominating https://bugs.freedesktop.org/show_bug.cgi?id=32709 This bug is a regression from OOo that means no file exported as ppt format can be opened by a MS Office product that has up to date patches. It has been around since December and affects every version ever made of LibreOffice, but does not affect any version of OpenOffice as far as I am aware, and I have installed all the betas and several nightlies as well as releases. The bug has clear and defined test cases, and it should be relatively simple to find where the regression occurred, because it happened very early on and only affects a fairly specific part of LibreOffice.
Nominating Bug 36926 - Missing bundled English dictionary extension dict-en. Regression
Nominating Bug 36927 - Some content not localized. Regression from 3.4 Beta 3
Replaced "Bug 36903 - export of tables (.doc) produces corrupted document" by "Bug 35805 - Tables corrupted in exported doc-files" where those problems have been reported for a much more early version.
Nominating: Bug 36915 – Beanshell scripts don't work (LibO 3.4 beta4) https://bugs.freedesktop.org/show_bug.cgi?id=36915
Nominating bug 36545, causes systematic crash on hyperlink insert and target choice, OS independent. Alex
Nominating 36756, broken links in Impress PDF export, as data is lost and a patch, albeit for OO, is available.
Nominating Bug 36957. Crash and regression.
I should like to nominate Bug 35798 to be added to this list. This bug/improvement is regarding Suppression of Blank Lines (fields) in Addresses when merging from Database into a Text Document to print Envelopes and Labels. Without this amendment users have to work out how to suppress blank lines using special codes and because the codes have to be added at the "Prepare to Print" drop down box stage, it is impossible to back track after you have entered the print cycle
Hi Alan (In reply to comment #77) > I should like to nominate Bug 35798 to be added to this list. This > bug/improvement is regarding Suppression of Blank Lines (fields) in Addresses > [..] How much I support the wish for that feature: it will not make it to the list of most annoying bugs. This list really is focused on must-repairs for the next release. Very useful improvements, do not apply for that.
Add bug 35805: table DOC export looks completely broken
(In reply to comment #73) > Nominating: > Bug 36915 – Beanshell scripts don't work (LibO 3.4 beta4) > https://bugs.freedesktop.org/show_bug.cgi?id=36915 accepted
(In reply to comment #77) > I should like to nominate Bug 35798 to be added to this list. This > bug/improvement is regarding Suppression of Blank Lines (fields) in Addresses > when merging from Database into a Text Document to print Envelopes and Labels. > Without this amendment users have to work out how to suppress blank lines using > special codes and because the codes have to be added at the "Prepare to Print" > drop down box stage, it is impossible to back track after you have entered the > print cycle I am afraid that we have other bugs that are more annoying for more users. I do not think that this one belongs here.
(In reply to comment #60) > This could be a stopper (if confirmed): Bug 36816 – Document statistics: > Paragraph Count doesn't work accepted; this feature is relatively important, for example, for students, ...
Nominating Bug 37013 as blocker. Saving in DOC format loses all styles. Nasty regression that makes DOC saving completely unusable.
Nominating bug 34699, regression compared to 3.3.2. I might add that all of the other scripts apart from Basic appear to be unavailable or non-functional / executable. Alex
Add bug 37014, cannot insert formula in Writer table. Makes formulas in Writer unusable.
After discussion with cloph, removing 34699 and will enter a new report for all scripting on Mac OS. Alex
Now nominating 37015, scripting other than Basic unavailable on Mac, regression compared to 3.3.2. Alex
nominate #37017: Bullets in presentation not saved
Nominating 37008, binary filters for SDW, SDC missing on Mac 3.4b4, regression compared to 3.3.2. Alex
Add bug #33355: Python scripting not available
(In reply to comment #88) > nominate #37017: Bullets in presentation not saved accepted; annoying, affects almost all Impress users.
Add bug #36907: Extremely slow after installation
nominating bug #36991
Nominate "Bug 36482 - PDF EXPORT Options dialog missing". Currently not a real blocker, but should we risk that lots of users might have to restore all their settings after deletion of user profile?
nominating 37045, seems like some evil mem access when printing, causes at least a crash for me on linux but apparently worse some undefined ( strange ) behaviour on macos
valgrind says ==1706== Invalid read of size 1 ==1706== at 0x1EC41058: SwViewImp::SetFirstVisPageInvalid() (viewimp.hxx:186) ==1706== by 0x1EF750D3: ViewShell::SetFirstVisPageInvalid() (viewsh.cxx:907) ==1706== by 0x1EC58A98: SwPageFrm::Modify(SfxPoolItem const*, SfxPoolItem const*) (pagechg.cxx:554) ==1706== by 0x1E966638: SwClient::ModifyNotification(SfxPoolItem const*, SfxPoolItem const*) (calbck.hxx:111) ==1706== by 0x1E969140: SwFmt::~SwFmt() (format.cxx:267) ==1706== by 0x1EA3BF3E: SwFrmFmt::~SwFrmFmt() (in /data4/OOO_BUILD_GIT/ooo-build/bootstrap/solver/300/unxlngx6.pro/lib/libswlx.so) ==1706== by 0x1EC5F5BC: SwPageDesc::~SwPageDesc() (pagedesc.cxx:114) ==1706== by 0x1EC5F691: SwPageDesc::~SwPageDesc() (pagedesc.cxx:116) ==1706== by 0x1E9D80DB: SwPageDescs::DeleteAndDestroy(unsigned short, unsigned short) (doc.cxx:144) ==1706== by 0x1EA537E2: SwDoc::~SwDoc() (docnew.cxx:561) ==1706== by 0x1EA549BB: SwDoc::~SwDoc() (docnew.cxx:664) ==1706== by 0x1EF7CAFB: ViewShell::~ViewShell() (vnew.cxx:320) ==1706== Address 0x50 is not stack'd, malloc'd or (recently) free'd ==1706== ==1706== ==1706== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==1706== Access not within mapped region at address 0x50 ==1706== at 0x1EC41058: SwViewImp::SetFirstVisPageInvalid() (viewimp.hxx:186) ==1706== by 0x1EF750D3: ViewShell::SetFirstVisPageInvalid() (viewsh.cxx:907) ==1706== by 0x1EC58A98: SwPageFrm::Modify(SfxPoolItem const*, SfxPoolItem const*) (pagechg.cxx:554) ==1706== by 0x1E966638: SwClient::ModifyNotification(SfxPoolItem const*, SfxPoolItem const*) (calbck.hxx:111) ==1706== by 0x1E969140: SwFmt::~SwFmt() (format.cxx:267) ==1706== by 0x1EA3BF3E: SwFrmFmt::~SwFrmFmt() (in /data4/OOO_BUILD_GIT/ooo-build/bootstrap/solver/300/unxlngx6.pro/lib/libswlx.so) ==1706== by 0x1EC5F5BC: SwPageDesc::~SwPageDesc() (pagedesc.cxx:114) ==1706== by 0x1EC5F691: SwPageDesc::~SwPageDesc() (pagedesc.cxx:116) ==1706== by 0x1E9D80DB: SwPageDescs::DeleteAndDestroy(unsigned short, unsigned short) (doc.cxx:144) ==1706== by 0x1EA537E2: SwDoc::~SwDoc() (docnew.cxx:561) ==1706== by 0x1EA549BB: SwDoc::~SwDoc() (docnew.cxx:664) ==1706== by 0x1EF7CAFB: ViewShell::~ViewShell() (vnew.cxx:320) ==1706== If you believe this happened as a result of a stack ==1706== overflow in your program's main thread (unlikely but ==1706== possible), you can try to increase the size of the ==1706== main thread stack using the --main-stacksize= flag. ==1706== The main thread stack size used in this run was 8388608. ==1706== Thread 5: ==1706== Invalid free() / delete / delete[] ==1706== at 0x4C25F7B: free (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==1706== by 0x60DD2FA: ??? (in /lib64/libc-2.11.2.so) ==1706== by 0x60DCEA1: ??? (in /lib64/libc-2.11.2.so) ==1706== by 0x4A215C8: _vgnU_freeres (in /usr/lib64/valgrind/vgpreload_core-amd64-linux.so) ==1706== Address 0x4048480 is not stack'd, malloc'd or (recently) free'd ==1706== ==1706== ==1706== HEAP SUMMARY: ==1706== in use at exit: 28,320,758 bytes in 394,600 blocks ==1706== total heap usage: 2,037,752 allocs, 1,643,153 frees, 582,416,425 bytes allocated ==1706== ==1706== LEAK SUMMARY: ==1706== definitely lost: 68,984 bytes in 141 blocks ==1706== indirectly lost: 40,647 bytes in 1,304 blocks ==1706== possibly lost: 11,996,865 bytes in 166,370 blocks ==1706== still reachable: 16,214,262 bytes in 226,785 blocks ==1706== suppressed: 0 bytes in 0 blocks ==1706== Rerun with --leak-check=full to see details of leaked memory ==1706== ==1706== For counts of detected and suppressed errors, rerun with: -v ==1706== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 94 from 9) Killed
Add bug 37108: binfilters missing also on windows
Adding Bug 36679 - Virus detected on installation (Windows)
nominate data loss / corruption during odf presentation load & then save: bug#37131
(In reply to comment #99) > nominate data loss / corruption during odf presentation load & then save: > bug#37131 It is a duplicate of the bug 37017 that is already here and has been fixed today.
Nominating Bug 37211 – "Del" and "Ctrl A" keys don't work in Basic IDE https://bugs.freedesktop.org/show_bug.cgi?id=37211 (regression against LibO3.4beta4)
propose 37077: extreme UI flickering op opening ODT
Proposing 36443 as it renders base useless for some users.
Nominating Bug 37277 as blocker. Formulas in table are inserted into the wrong cell. Regression from 3.3.2.
Very annoying, but not blocker Bug 32861 - Impress hangs part way through slide show Linux specific bug, Impress hangs if slide contains gif animation
(In reply to comment #105) > Bug 32861 - Impress hangs part way through slide show > Linux specific bug, Impress hangs if slide contains gif animation it seems to affect more users => accepted
Nominating Bug 37252 as blocker. Crashing when using "Function Wizard" button. Regression and crash.
One another iteresting regression if will confirmed: Writer corrupts tables when saving in doc format Bug 37309 - regression: when table in Writer saved in doc format, it becomes corrupted
(In reply to comment #107) > Nominating Bug 37252 as blocker. Crashing when using "Function Wizard" button. > Regression and crash. Kohei provided the fix and we plan to use it for LO-3.4.0-rc2. Anyway, I think that it was not blocker because it happened only with the particular function. Similar bugs used to be even in older final releases. Note that this is the purpose of the time-based release to do not wait for every single fix that affects only limited number of users. It is better to fix them in more frequent bug fix releases.
Nominating Bug 37317. Select comments print position in print dialog and closing crashes writer. Regression and crash.
Add 37319: Filecopy function no longer works as before; block several extensions
Nominating Bug 37356 - [Calc] Paste Special of copied cells with transposition causes LibreOffice to hang. Hang and regression from 3.3.2
nominating bug #37370
Nominate as BLOCKER: "Bug 37030 - Crash when Copy/Paste as GDI metafile selected cell range from CALC to WRITER"
Nominate 37429, crash LibO when Copy/Paste from Writter to Calc
I suggest to add bug 36766: very severe regression, hit all Impress users, and can be a blocker for a lot of them.
Nominating Bug 37520 - [Calc] Crash with Insert Names Labels. Crash and regression.
Nominating 37487 as most annoying bug - crash in Writer on Mac when using drag and drop to copy data from datasource navigator to Writer document. Alex
Nominating 37529 as most annoying - crash when using data source navigator in Writer (F4) to browse tree listing of tables in a mysql jdbc driver connected database. Alex
I nominate bug 37516. It is a regression, invalid DOC file (MS Office Binary Format) is saved from LibreOffice 3.4.
Nominating Bug 37584. [Writer] Track changes: deleted text lost. Regression and data loss.
Nominating 37620. Affects multiple OSes. Builtin report wizard made reports no longer display data, merely ipsem lorum typesetter text. Actual data not displayed, making these reports useless. Alex
Re bug 37620 - regression compared to 3.3.2. Looks like the problem occurred after integration of OOo 3.4 code, since the problem also exists in OOo-dev 3.4m0. Alex
Nominating 37590 - radio buttons in Base forms no longer transmit reference data to underlying database field. This is a regression over 3.3.2 and causes data loss when switching between 3.4 and 3.3.2 and earlier. Also, the bug is not present in OOo 3.4beta. Alex
Nominating Bug 37622. [Calc] XLS file loses formatting. Regression.
Add bug #32948: we should get the address book stuff fixed until 3.4.2.
Nominating Bug 37668 - Math crashed after put some elements
Nominate Bug 34805 - Recovery of MS OFFICE documents fails after crash
Nominating Bug 37763. Define a range name prevents recognition of a label. Regression.
Nominate "Bug 37179 - [UX] options set in Find&Replace dialog, influence how Find tool bar works". "Find" is a very basic, very important function what should work error free
I nominate "Bug 37799 - Crash when Break (remove) DDE link to CALC". I believe Such DDE links are frequently used (at least I do that), and a crash there is not a bagatelle.
Nominating Bug 37869 - Missing symbols in Math Elements windows (regression against LibO 3.3.2)
I suggest adding this https://bugs.freedesktop.org/show_bug.cgi?id=37516 and fixing if in 3.4.1 release
I nominate bug 37930 : it is a crash with the filepicker of Seven/Vista when you insert an hyperlink.
Nominating Bug 3794. Some formulas not recognized. Regression against 3.3.2. Similar or maybe related to Bug 37860.
(In reply to comment #135) > Nominating Bug 3794. Some formulas not recognized. Regression against 3.3.2. > Similar or maybe related to Bug 37860. Sorry, was Bug 37942. I correct it.
Adding #35784 EDITING - unable to update postgresql databases using postgres SDBC driver
(In reply to comment #133) > I suggest adding this https://bugs.freedesktop.org/show_bug.cgi?id=37516 and > fixing if in 3.4.1 release It has already been added few days ago.
(In reply to comment #134) > I nominate bug 37930 : it is a crash with the filepicker of Seven/Vista when > you insert an hyperlink. Yup, it deserves to be here.
Nominate "Bug 37488 - PRINTING result completely messed up", tables and DRAW objects crippled in WIN printouts.
Nominating Bug 38000. [Writer] crash with a closing parenthesis on the beginning of a line. Crash and regression.
Nominating bug 37693 as unacceptable table border line behaviour / rendering
suggest 37825 - can't un-encrypt a file.
bug 37888 – crash when saving to doc format
(In reply to comment #142) > Nominating bug 37693 as unacceptable table border line behaviour / rendering Hmm, I am afraid that it does not fit here. I understand that it is very annoying for the reporter but I doubt that it affects a big group of other users. Also there is a comment that the behavior is random. These bugs are usually very hard to debug. In the real life, such bugs are often fixed only when another better reproducible scenario is found.
(In reply to comment #143) > suggest 37825 - can't un-encrypt a file. Sounds annoying => added.
bug 38067 – serious performance issue with tables in Writer
https://bugs.freedesktop.org/show_bug.cgi?id=34940 This is basic functionality that appears not to work.
Nominate bug 37771: the ridiculous password size for protected sections, make this function unusable.
Add bug #38374: data loss when exporting pasted forms into DOC.
Nominating "Bug 37195 - Dictionary access lost after LibO upgrade". It's not acceptable that users have to edit the user profile folders to regain access to their dictionaries.
Nominating bug 38544 : regression and accessibility issue, no mean to edit an object in Calc without using the mouse.
I don't know if this is the correct place to add a mention of one or more annoying bugs in the current 3.4.0 release, but i have to add something annoying. In LibreOffice Calc 3.4.0 there is an issue concerning cell borders. When i create a table in Calc and give personalized cell borders in the formatting cell dialog, i get the correct cell borders. I want to use vertical borders with double line (one thin and one thick next to each other). After formatting everything is fine, i save the file on a network drive and close Calc. My next question is: Where can i add feature requests? Feel free to move my comment, my experience with this bugzilla is not so good. But after reopening the file these cell borders disappered and i have to reformat the cells again. With big tables this is a quite waste of time. M
@NX: For a novice starting his comment with "I don't know" you really modify settings with stupendous courage ;-) Of course this is not the correct place, and please do not touch Bugzilla pickers if you do not know exactly for what they are. You can get information on <http://wiki.documentfoundation.org/BugReport> <http://wiki.documentfoundation.org/BugReport_Details> I recommend to post questions on [tdf-discuss] or a user mailing list, I do not understand your border Problem. If discussion on a user mailing list has a result, you can file a new bug report, or you will find someone in the discussion who will do it for you, or you can ask me by personal mail with a draft of your bug report. For an enhancement request I recommend the same proceeding, present your idea in a mailing list (may be someone is already working on it).
I nominate bug 38590 : fd-leak which blocks the file-system and possible data loss
(In reply to comment #153) Thanks for interesting information about bug. I filed report about this: Bug 38595 - Calc not saves borders of cell This bug looks like annoying. Meanwhile try use bigger width of line, at least 1.0, this bug my not appear then.
Nominating 38623 - regression over 3.3.3, nasty crash on opening Word doc. Alex
(In reply to comment #156) > Meanwhile try use bigger width of line, at least 1.0, this bug my not appear then. Works fine. Thanks for that "workaround". :)
writer redlining/undo bug #38745 might be an interesting candidate if verified ;-)
(In reply to comment #159) > writer redlining/undo bug #38745 might be an interesting candidate if verified > ;-) It was confirmed and added to the list.
For 3.4.2 Blockers please see "Bug 38993 - [TASK]: Bugfixes required for enterprise deployment LibO 3.4.2" and add yourself to CC if you are interested!
Nominate "Bug 39155 - FORMATTING: Word wrap does work in the header, footer, table", what makes Writer unusable for lots of users. DATALOSS, the problem persists when you open the damaged document with a version what normally does not show that problem.
Nominate "Bug 39159 - PRINTING: Switching radio buttons "Selection <-> All" Crashes".
Adding Bug 36688.
Nominate Bug 38619 - Picture of type wmf is not printed correctly. It is a regression to LO 3.3.2. wmf is the most important format for external vector graphics.
I just tested LO3.4.2rc1 and now wmf-pictures print fine for me. So I cancel the nomination.
Nominate: "Bug 33593 - FindBar use breaks the normal 'Find and replace' by columns". We have to get rid of trouble with Find function
Nominate "Bug 33379 - Searching in all sheets will not work after using the Find toolbar", another Find problem
Nominate: "Bug 37499 - Find and Replace Values does not work"
Nominating: "Bug 39236 - EDITING Calc crashes when deleting a sheet with a pivot table on it"
Removing bug 39155, the reason described in the bug 39155 comment 6.
Bug 36555, Prevents read Microsoft Access database. Is a regression from OOo 3.3 Works well in 3.4 Seems as something is no shipped with 3.4.
Nominate "Bug 38542 - FORMATTING TABLE double borders incompatibility with old LibO / OOo Versions", makes 3.4 unusable for all users using tables with double lines. Dataloss problem!
Nominating Bug 39447. Crash and regression in Writer.
perhaps bug #39520 - crash on exit on mac after cut/paste
Nominating Bug 37658. Format loss in ODF format and regression.
Nominating Bug 39659. Java 1.7.0 not recognised,
Nominate Bug 39510 - CRASH closing document with footnotes, makes LibO unusable for scientific texts or other ones with many footnotes.
Add https://bugs.freedesktop.org/show_bug.cgi?id=31481 "Split pane in same window" -- inherited from OOo, this seems the single most wanted feature for years.
@HansPL This meta is not for Enhancements, please read original report! And if a bug is a most annoying one, it's for "Depends on"
Nominate Bug 32181 - underlining bleed over margin; This bug makes PDF export unusable for certain documents.
Nominate "Bug 39799 - CRASH when insert SVG image while EDITING"
Nominate Bug 39919 - CRASH when insert particular SVG picture from file. This one alone might not be a typical "most annoying" one, but we have lots or SVG crash, does not open, result is unusable problems, it would be great if we could get SVG into focus for a while. Or may be this would b better for "Bug 37361 LibreOffice 3.5 most annoying bugs"?
Nominate #40079; when in this situation the user is confronted with the situation that (s)he cannot save their document, and feels forced to discard changes to exit LibO and/or turn computer off, which one could consider a form of data loss. The work-around is simple enough *when you know it*, but it is not a natural idea that comes to one's mind when one encounters the problem.
(In reply to comment #184) > Nominate #40079; Of course, if you are affected, that is a very annoying problem, but I doubt that many users are affected. I do not see "Bug 40079 - "File/Save (as)" inoperant if macro, but not dialog library loaded " as a "most annoying" one.
(In reply to comment #181) > Nominate Bug 32181 - underlining bleed over margin; This bug makes PDF export > unusable for certain documents. Looks quite ugly => accepted.
Nominate bug 40113 in 3.4.x branch. Spreadsheet header/footer background does not display color or image.
Following "Most Annoying" Bugs still are without assignee, can developers please check? 1. Bug 37620 - Data in reports created by Report Wizard do not display all data records in LO 3.4 RC1 2. Bug 38745 - redlining / undo document breakage / corruption 3. Bug 39510 - CRASH closing document with footnotes
I have just added bug 32849 "Table borders in pdf export". I also am not sure that that bug would not depend on bug 37488 that has been declared "Resolved - Worksform"... The quality of the Libò generated PDF files has to be very high and now is not so. Carlo
Currently we only know that a problem seems to exist, but not, what it is, how many users might be affected, ... . So I remove the bug 32849 for now until we have gathered more knowledge.
Nominating 39950 - regression with regard to 3.3.3 and 3.3.4. Copy/pasting report designer objects (fields, labels, etc) between sections causes systematic crash. Alex
Can we add Bug 39355 ? This can be rather humiliating when you send a PDF to someone who uses Adobe Reader instead of a free PDF reader.
(In reply to comment #192) > Can we add Bug 39355 ? This can be rather humiliating when you send a PDF to > someone who uses Adobe Reader instead of a free PDF reader. Hi Everyone, may be this issue is related to this old one https://bugzilla.novell.com/show_bug.cgi?id=467181 whose title was "PDF/A export broken - Adobe Acrobat reports Invalid ColorSpace" and the fix (take a look to comment 11) would be the same because it's a new regression? I just have added this comment to the coming back (?) bug. Carlo p.s. Comment 11: https://bugzilla.novell.com/show_bug.cgi?id=467181#c11
Hi Everyone, may be this issue is related to this old one https://bugzilla.novell.com/show_bug.cgi?id=467181 whose title was "PDF/A export broken - Adobe Acrobat reports Invalid ColorSpace" and the fix (take a look to comment 11) would be the same because it's a new regression? I just have added this comment to the coming back (?) bug. Carlo p.s. Comment 11: https://bugzilla.novell.com/show_bug.cgi?id=467181#c11 Il 31/08/2011 21:05, bugzilla-daemon@freedesktop.org ha scritto: > https://bugs.freedesktop.org/show_bug.cgi?id=35673 > > --- Comment #192 from Aaron Strontsman<heinzlesspam@gmail.com> 2011-08-31 12:05:35 PDT --- > Can we add Bug 39355 ? This can be rather humiliating when you send a PDF to > someone who uses Adobe Reader instead of a free PDF reader. >
bugzilla-daemon@freedesktop.org schrieb: > https://bugs.freedesktop.org/show_bug.cgi?id=35673 > > --- Comment #194 from Carlo Strata<carlo.strata@tiscali.it> 2011-09-01 02:10:14 PDT --- > Hi Everyone, > > may be this issue is related to this old one > https://bugzilla.novell.com/show_bug.cgi?id=467181 THIS one definitively not! Please stop this discussion at the wrong place, Bug 35673 is a tracking task bug! Such a question has to be discussed in Bug 39355! CU Rainer
Nominating Bug 40571 - UI EDITING Crash when modifying defined name. Crash and regression.
Nominating bug 38065 - PDF Export with OS or LibO Appearance background color. This is a quite old bug in Draw (it bit me first time in OOO 3.1 - see http://openoffice.org/bugzilla/show_bug.cgi?id=110948).
agree 36662 for removal - purely cosmetic and debatable.
(In reply to comment #198) > agree 36662 for removal - purely cosmetic and debatable. It's not only cosmetic... see comment 4.
Nominating Bug 40701. Base crashes with runtime error when "Find Record" button is clicked with certain documents. Crash and regression.
Nominating Bug 40482 - Non-printing characters become invisible. This is a rather annoying regression in Writer (LibO ver. 3.4.3).
nominating 37579: it fired some ~130 duplicates in the first two weeks of beta.
I nominate bug 37129 - Dotted and Dashed table borders are not drawn correctly I find this incredibly annoying; dotted and dashed borders display as solid lines in liberoffice calc 3.3 & 3.4
nominating 39205 spaces and TABs added in footnotes when saving as .docx
Nominating bug 38177 because of the data loss issue. Alex
I would wish to add 39052, which is a basic funcionality that doesn't work.
40854 : because, it's really annoying that sometimes you cannot select two drawings with the mouse and CTRL key. With the bug report is attached a document that show the problem. Plus, this is true that the bug exists since openoffice.
Nominating 41022 as blocker. Nasty crash in database form edit mode when using automatic field order activation function.
(In reply to comment #209) > Nominating 41022 as blocker. Nasty crash in database form edit mode when using > automatic field order activation function. It is also a regression over 3.3.4 where the crash does not occur and the function works as intended. Alex
LE GARREC Vincent - it is normal for someone else to add a 'most annoying' bug as a dependency after triage, just suggest things in the comments. Also - wrt. most annoyingness, a bug being a regression is a huge issue here - and it seems there is a suitable workaround for 40854 - so I recommend dropping it. Thanks for suggesting it though, it does sound annoying :-)
(In reply to comment #211) > LE GARREC Vincent - it is normal for someone else to add a 'most annoying' bug > as a dependency after triage, just suggest things in the comments. > Also - wrt. most annoyingness, a bug being a regression is a huge issue here - > and it seems there is a suitable workaround for 40854 - so I recommend dropping > it. Thanks for suggesting it though, it does sound annoying :-) Sorry, I just read to much strictly the first post "please add the Bug ID as dependent Bug here to the Meta Bug in field "Depends on"." without noticing that everyone add bugs in comment. I didn't knew the workaround but I still think that bug should be solved because it's really disappointing when you select two draws at page 100 and you always move to page 30 and select another draw. This behavior always make me thing "It's not really a bug; it's an undocumented feature". If you still think that bug should be drop, I let you removing from "Depends on". No prob.
Proposing bug 39928 - VIEWING: pictures in particular .doc shown wrong, picture size correct, but contents shrunken and surrounded by white margin Because it is a regression over LO 3.3 Because it corrupts you documents Because you don't see it happening, so when you see the bug, you have already corrupted many documents
Nominating bug 34548 - "Undo" in Impress fails to work at times and sometimes crashes LibreOffice altogether. This bug is probably inherited from OOo, as I could also reproduce it on their 3.4 dev-snapshot I had laying around.
I would like to nominate Bug 41657 - Inserting Powerpoint file into LibreOffice Impress CRASHES every time.
Like to nomiante 2 bugs. Have one more, but wasn't able to find it reported. No difference between different border thikness - https://bugs.freedesktop.org/show_bug.cgi?id=33634 Borders behaviour irradical, not WYSIWYG - https://bugs.freedesktop.org/show_bug.cgi?id=42339
Finally found bug that I experience offten since most of company use Excel 2003 and few of us use LO 3.4.3 XLS files saved by CALC have split added on top - https://bugs.freedesktop.org/show_bug.cgi?id=39589
"Bug 42339 - EDITING and VIEWING cell borders differs from expected and print" exists at least since OOo 1.1.4., so I can't see any founding why this one should have become such a high priority suddenly. "33634 - VIEWING: No difference between cell border 0,5pt and 1,0pt" is rated as "minor" in the bug, so I also can't see any reason for a listing here. Both ones are too far away from a blocker to be listed here, because of that I remove them.
Argh, something went terribly wrong here, please excuse me for the SPAM. Hope this post fixed the unintended removing of many bugs, please excuse me for the SPAM!
Nominating Bug 42097. Calc: Search criteria fail with parenthesis and bracket characters.
Nominating Bug 42382. Scripting in JavaScript and BeanShell broken. Regression.
Nominating Bug 38817. It's a regression from 3.3.x series, and screws up display of forms/reports when you're attempting for a clean professional look. It has blocked me from upgrading to the 3.4.x series so far.
Nominating Bug 40967. Using IF and OR in array formulas is a standard among all scenarios to be used in array formulas. I use it very often to validate data or generate data values continued to use in other formulas. This should be fixed, especially as it perfectly works in OpenOffice ever since. I wonder if this a regression of refactoring the code of Ooo.
Nominating Bug 40990. Entering array formulas in LO 3.4.3 with big ranges draw a lot of ressources. With a range around a thousand cells it eventually crashes. This shold be fixed otherwise using array formulas with vast ranges will be obsolete.
Bug 42259 Crash if copying a cell from Lotus Notes or OOo. Occurs on Ms-windows and Linux (x86). Occurs every time, if cell has formatting. (colour and/or font size) If content is special copied to paste as plain text, no problem. Would guess that is related to some change in format with LibO, since copying a similar cell from LibO to OOo also crashes OOo. Data copied to LibO should always be filtered to ensure that it is validly formatted for LibO. No matter what the source.
Nominate UI [AR]: "Bug 42537 - active indication" background with border (for icons) in menu at left instead at right. Unacceptable very visible bug for RTL. IMHO a "Must have" for 3.4.5
(In reply to comment #224) > Nominating Bug 40990. Entering array formulas in LO 3.4.3 with big ranges draw > a lot of ressources. With a range around a thousand cells it eventually > crashes. This shold be fixed otherwise using array formulas with vast ranges > will be obsolete. Such performance improvement would be too big change for 3.4. It affects only limited group of users, so it even does not belong to the most annoying bugs. Kohei will try to fix it for LO-3.5.
Hi Everyone, I nominate Bug 37083 (just fixed!) as very important to be included ("cherry picked" ;-) ) for Libò 3.4.4-RC3. Its description is is "Position and Size change for picture anchored to cell" it's important for quality in video rendering and in printing. Have a nice Sunday, Carlo
Nominating #42714, a crasher when one copy/paste a control in report builder.
Nominating Bug 42723. A nasty UI regression bug.
(In reply to comment #230) > Bug 42723 Sorry, is Bug 40948
Nominate "Bug 42762 - FILEOPEN particular document with Math Formula object will CRASH" Nominate "Bug 37003 - FILEOPEN particular .odt with formula object crashes" Nominate "Bug 39006 - FILEOPEN: LibreOffice hangs with 100% CPU usage on specific .doc file" Might all have the same or similar roots.
Propose Bug 42684 - FILEOPEN very slow, network/dns related, it takes about 15 minutes ...
Nominate bug 42772: LO-3.4.4 does not start on Windows 7, 64-bit.
Nominate bug 43266: Another problem to start 3.4.4 on 64-bit Windows Hmm, we screwed up something on 64-bit Windows systems.
Nominate bug 42958 3.3 -> 3.4 regression with xls formatting
Nominating Bug 41996 - Can't move slides in slide sorter. Quite annoying. (Seems to not affect everyone, though.)
Propose Bug 43867 - MAILMERGE: Mail Merge with image in header of document, causes crash
Nominate "Bug 43868 - FILEOPEN document saved with password: correct password not recognized"
Nominate "Bug 41089 - FILESAVE: Impossible with password protection"
(In reply to comment #240) > Nominate "Bug 41089 - FILESAVE: Impossible with password protection" Yup, I have added it. Well, it might be a duplicated of the bug 43868. I guess that the fix will be the same for both of them.
I would like to propose Bug 36982. It should have been a blocker before. It was a regression against 3.3.x and it causes data loss. The argument that it is not important because it only affects docx users seems irrelevant to me (many of the cases here are also very specific) and this one causes data loss.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
.
Nominate Bug 42073: Writer input fields are not populated using the Java UNO API
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.
pls fix issue fdo#41054 in the 3.4.6
pls fix fod#39118 in 3.4.6 too
Added #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
Nominate: https://bugs.freedesktop.org/show_bug.cgi?id=36876 which should be, if it that's not clear, OpenOffice bug 13791. It prevents import of .doc with table. Nominate: https://bugs.freedesktop.org/show_bug.cgi?id=38261 because current LO's Find&Replace doesn't take care of original word case and it doesn't preserve capitalisation. But, it should be overall enhanced, just like "Alternative Find & Replace" extension which doesn't work properly on LO anymore.
@Timur Please do not "nominate", nobody will check such nominations. Consider wise, add a bug or do not add it. <https://bugs.freedesktop.org/show_bug.cgi?id=37361#c91> Enhancement Requests do not sound like "most annoying" <http://wiki.documentfoundation.org/BugReport_Details#Version>
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
Add "Bug 44208 - CRASH when click Tools -> Options with UI [ta_IN], [hi_IN] and other [xx_IN]", very ugly crash affecting lots of WIN users who can not use LibO with this issue
I add "Bug 45355 - CRASH if characters in text of BENGALI, TIBETAN, MALAYALAM, MARATHI, NEPALI, TAMIL, TELUGU", LibO is unusable for several Asian languages.
Added Bug 39724, without the necessary change to the Windows installer (to include XML filters in the default installation), Flat ODF (XML) fails to work on Windows.
Please don't change the fields in this bug. It is a meta bug and covers all platforms.
since 3.4.x cicle is terminated and all the still 3.4.x open bugs have been moved to the 3.5. MAB page I suggest to close this bug.
oops, forgot this final step. @tommy27: thank you for the hint.
... and there was much rejoicing!
Thanks Rainer for all that careful work ! :-) and on with the MAB fixing in 3.5 ...
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.
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.4 STATS ...................... fixed bugs -> 119 open bugs -> 0 ......................