This is the Meta issue to track the potential stoppers for the release of LibO 3.3. 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 want to declare that issue as a blocker for a.m. release.
Nominate Bug 31494 - LibreOffice 3.3 crashes upon exiting on Windows: It seems that no "real" problems exists, but such a visible error message is too deterring for new LibreOffice users.
Well, bug #31494 is already fixed, in the sense that there is a workaround in place that causes it not to happen. (The same workaround was already present in 3.2.1.) That bug is kept open because we would of course like to know, and fix, the root cause to the problem. (Also, the workaround has been added to the libreoffice-3-3 branch only.) So bug #31494 is not really a blocker.
CC
Nominate bug 31654 - clearly that's a regression relative to 3.2.1
Nominate bug #30929 - c#5 Printing crash using some documents, the issue is still being investigated. It would be severe if impacts more wide than we have observed. It is a regression against 3.2.1.
Nominate bug #31134 Unable to make presentations with multiple backgrounds: "Apply background to the current slide only" does not work in Impress... Only one background entry is present in styles.xml This is regression since OpenOffice.org 3.1
I think we need to have here only bugs that cause crashes in common sitautions, or make the application practically unusable in some common situation. Missing functionality, even if it is a regression, is not a blocker. So I would like to drop bug #31134 from this list?
@Tor: I believe "crashes only" is a too narrow definition for blockers. Concerning bug 31134 please see my comments on the bug page.
Adding me to CC
Note that I proposed definition of blocker bug at http://wiki.documentfoundation.org/Release_Criteria
Nominating bug 31308 as a blocker. Several popup icons not working at all on Windows.
Nominating bug 31741 and bug 31833 as blockers.
added known broffice branding issue.
Nominate: Bug 31770 - BrOffice brand and LibreOffice Nominate: Bug 31585 - Writer crashes on mail merge
Nominate: Bug 31734 - Loading many small documents causes crash Currently it seems that this one will be the last one of existing bugs I want to nominate.
Remove bug 31134 - can't save different background images per slide Reason: old bug, less common scenario
Nominating Bug 31805 as a blocker. It's a simple little thing, but it is a regression, and has been a long standing bug since the Go-OO time. I'd like to fix it once and for all.
I just filed Bug 32007 - EvolutionLocal database has no table to display. Do you guys think that this should be a blocker? It's not life-threatening, but a bit weird and embarrassing. Also, the fix may be potentially very simple.
Nominate bug 32010 - LibO crashes when clicking a Table control body with control design mode off. Though I am not sure how many users will use this function, in my side, this can only be revealed by an exceptional automation testing log. This risky scenario happens when a user opens a document contains a 'Table control'. By default, LibreOffice opens a document with Design mode Off. So whenever the user click a control table body, Libreoffice will crash always.
I don't think bug #32007 is a blocker, it appears in quite rarely used functionality, as far as I can guess. And if the user doesn't know what an "EvolutionLocal" is, why would he/she click it (except just to intentionally test what happens)?
(In reply to comment #19) > Nominate bug 32010 - LibO crashes when clicking a Table control body with > control design mode off. > > Though I am not sure how many users will use this function, in my side, this > can only be revealed by an exceptional automation testing log. > > This risky scenario happens when a user opens a document contains a 'Table > control'. By default, LibreOffice opens a document with Design mode Off. So > whenever the user click a control table body, Libreoffice will crash always. Take out this from blocker, the issue only happens when Assistive Technologies enabled.
suggest add 32126 (Oracle mention wrt. ODF icons & formats in alt text).
Nominate Bug 32142 - Replace "Beta" download buttons for stable release As reminder
I'd like to nominate Bug 32133 - [RC1] overlapping controls on Tools - Options - General panel.
Adding bug #31716 back.
Nominating Bug 32196 (Data Form shows corrupted string) as a blocker. This is just ugly, plus the fix will be relatively safe and easy.
Nominating Bug 32209 as a blocker. A hard-coded English only string which should really be localized.
Nominating bug #32185. The libreoffice string translations were not used in the Windows build.
Nominating bug #31820. I can't setup LibO 3.3 rc 1 on 2 computers with Windows 7 x64 due to this bug.
Nominating bug 32250 : installation of RC1 impossible on small HD under XP. Regression to beta3. RC1 asks for 4 times free space than OOo.
blockers badly added: fixed
I would like to nominate Bug 32304. Saving an Impress document to ppt with grouped object(s) corrupts the file.
There is a serious encoding problem about non-ascii letters in MS Office formats (bug 32219), also a related issue is reported here[1]. [1] http://www.openoffice.org/issues/show_bug.cgi?id=114482
Nominate Bug 32338 - [WIKIHELP]: Missing context sensitive Help
Olivier suggest 32377 as a blocker; though there is perhaps a suitable workaround for him there now.
I suggest bug #31518.
(In reply to comment #36) > I suggest bug #31518. I do not see it in the plain LibreOffice build. I think that it is related to the Novell branding. It would have been better to report it in the Novell bugzilla. In each case, it should not block the LibreOffice release.
Ah, good point.
Nominate the bug #32229. It describes some more BrOffice branding problems.
Nominating Bug 30571 - Dragging some toolbars on the left side makes them unusable. That's not totally compatible with our blocker definition, but imho too visible to leave it as a known bug
Suggest issue 32583 - Hebrew language pack not usable because of wrong folder.
I would like to nominate bug 32573 Not being able to print landscape is a bit of a problem for a word processor
Note that there seems to be some confusion about what it means to "nominate" a bug here. In my opinion, nominating a bug as a blocker is just a request for comments and discussion that eventually then will end up with a consensus (or developer decision) to accept or reject the bug being as a blocker. Others seem to take each nomination as an immediate change in status of the bug to blocker. Which is correct? Is "nominate" a synonym of "make a candidate", (as in "nominate somebody to be a candidate in an election") or a synonym to "make"? (Wiktionary lists both meanings, but says that the latter is obsolete.)
(In reply to comment #42) > I would like to nominate bug 32573. Not being able to print landscape is a bit > of a problem for a word processor. I am not able to reproduce it. It seems to be system specific, so I do not consider it as a blocker for now.
(In reply to comment #43) > Note that there seems to be some confusion about what it means to "nominate" a > bug here. > > In my opinion, nominating a bug as a blocker is just a request for comments and > discussion that eventually then will end up with a consensus (or developer > decision) to accept or reject the bug being as a blocker. > > Others seem to take each nomination as an immediate change in status of the bug > to blocker. > > Which is correct? Is "nominate" a synonym of "make a candidate", (as in > "nominate somebody to be a candidate in an election") or a synonym to "make"? I do not have any strong opinion here. I think that both ways are fine and it depends on the reporter's confidence. If it is evident blocker, it might be added to bug dependency immediately. If the reporter is not sure, it might be enough to mention it in the comment... We must investigate all nominated bugs before the release anyway. We could remove bugs from the list if there is a good reason and vice versa...
(In reply to comment #41) > Suggest issue 32583 - Hebrew language pack not usable because of wrong folder. Looks like a real blocker => accepted
(In reply to comment #40) > Nominating Bug 30571 - Dragging some toolbars on the left side makes them > unusable. That's not totally compatible with our blocker definition, but imho > too visible to leave it as a known bug It went out that it was pretty old bug even in OOo => not a blocker.
(In reply to comment #35) > Olivier suggest 32377 as a blocker; though there is perhaps a suitable > workaround for him there now. The extensions can be disabled in the Windows installer in LO-3.3-rc2 => should be solved.
(In reply to comment #22) > suggest add 32126 (Oracle mention wrt. ODF icons & formats in alt text). Yup, I think that we should fix this => accepted.
(In reply to comment #19) > Nominate bug 32010 - LibO crashes when clicking a Table control body with > control design mode off. It happened only on Linux with 'Assistive Technologies' enabled. There were more similar problems with 'Assistive Technologies' in the past and were old bugs => not a blocker.
(In reply to comment #15) > Nominate: Bug 31734 - Loading many small documents causes crash > > Currently it seems that this one will be the last one of existing bugs I want > to nominate. I guess that it is a pretty old bug. Also it is not typical scenario. If you open more than 10 documents, you have mess on the desktop, ... I think that it might be a candidate for memory footprint and speedup optimization but not a real blocker.
Removing the bug #31820. The extensions registration fails only in some strange circumstances. It does not affect the base function...
Added bug #32635. Another problem with BrOffice branding.
Added License Dialog Added missing langpacks
I've created a new task/tracker bug for issues for 3.3.1 as bug#32894#
nominate Bug 32790 as stopper
I'm nominating Bug #32929 ("Use system font for user interface" ignored) since this feature works fine in RC1 and is broken in RC2.
Nominate Bug 32052 - hat, vector and tilde doesn't appear. With this bug LibreOffice is unusable for physicist and some other scientists. It is regression to OO 3.2.
(In reply to comment #52) > Removing the bug #31820. The extensions registration fails only in some strange > circumstances. It does not affect the base function... I have error on 4 computers with libreoffice rc2. And I don't have any workaround to install libreoffice on them, so I can't use "base function". After installation without "Optional components" I can't run any libreoffice application - see comments to #31820. At the same time openoffice 3.2 succesfully setups on all this 4 computers. Nominating bug #31820 to release blockers again.
Nominate Bug #32991 - FORMATTING TABLES Alignment lost when exporting to DOC It is regression. Many people use tables, many people export to doc. Would be nice to fix it.
hello friends, there seems to be a grave problem: lo crashes after attempt to run python macros: bug #32939. best regards, alex
Hi, I added this as a blocker bug: https://bugs.freedesktop.org/show_bug.cgi?id=32930 Writer crashes after copy&paste of content of certain web pages on Ubuntu.
(In reply to comment #60) > Nominate Bug #32991 - FORMATTING TABLES Alignment lost when exporting to DOC > It is regression. Many people use tables, many people export to doc. > Would be nice to fix it. It seems to be pretty old bug. We are sorry but it does not fit the release blocker criteria.
drop bug #32930, Linux and Java specific, and specific to LanguageTool that we don't bundle now; moving it to 3.3.1 in case we have a fix by then.
I'd like to nominate #32964 and #32960: they both break a rather basic functionality, which is having reports with grouping and/or sorting. They both imply regressions in some cases.
(In reply to comment #44) > (In reply to comment #42) > > I would like to nominate bug 32573. Not being able to print landscape is a bit > > of a problem for a word processor. > > I am not able to reproduce it. It seems to be system specific, so I do not > consider it as a blocker for now. Using the XPS driver works, using a real printer doesn't - RC3 is the same
(In reply to comment #66) > (In reply to comment #44) > > (In reply to comment #42) > > > I would like to nominate bug 32573. Not being able to print landscape is a bit > > > of a problem for a word processor. > > > > I am not able to reproduce it. It seems to be system specific, so I do not > > consider it as a blocker for now. > > Using the XPS driver works, using a real printer doesn't - RC3 is the same Forget this, I withdraw it as a blocker, however I do still think it's a bug If you use Postscript printer drivers it works fine, PCL5c and PCL6 don't for me at least
add 33099 - crasher with no help pack when selecting help.
I nominate Bug 33151 - Onlinehelp: Danish and Hungarian contents
we need a decision on bug#33135 and bug#33105 is an l10n blocker too.
I'm unsubscribing from this bug (and all LibereOffice bugs) because bugs.freedesktop.org uses an untrusted security certificate, and I am tired of clicking away the warning dialog(s) for every e-mail bug report I receive in Thunderbird. Who thought that using the untrusted certificate from CAcert was a good idea? See: https://bugzilla.mozilla.org/show_bug.cgi?id=215243#c158
bug 33355 consider to be a blocker
No new blockers after RC4 phase, this makes RC4 into final -> fixed.
Any new blocker bugs need to go vs. the 3.3.1 release - ie. as dependents of bug#32894. Please add new issues there. We need to retire this bug now :-)