incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 120789] New: vis ver 3.4.1: stability, page break, update site inaccessible
Date Sat, 01 Sep 2012 14:01:30 GMT

          Priority: P3
            Bug ID: 120789
           Summary: vis ver 3.4.1: stability, page break, update site
          Severity: major
        Issue Type: DEFECT
    Classification: Application
                OS: Windows, all
          Hardware: PC
            Status: UNCONFIRMED
           Version: AOO 3.4.1
         Component: editing
           Product: word processor

I downloaded 3.4.1 a few minutes ago hoping that 2 major bugs would be
corrected -- but they're not:

1) The writer application sometimes crashes within seconds of loading.  Seems
worse than ver 3.4.0...  But you've probably heard that before, so something
that may be new:

2) (and even worse:) When I write, I separate sections with strings of
asterisks, as in **********.  In ver 3.4.0, one asterisk followed by the
"enter" key works normally -- even 2 or 3.  But beginning with 5 or so, and
certainly by  10, the enter key inserts a page break which effectively cannot
be removed.  Ever afterward, when something is ended with an "enter," a page
break is triggered.  The enter key has become a page-break key.  

A string of "minus" signs seems to have the same effect.  Perhaps others?  

The work-around is to copy everything but the last paragraph to a new document
page, and retype the contents of the last entry bounded by the page break. 
Copying that material simply transfers the page break problem to the new

In slightly modified form, this problem as been carried into ver 3.4.1...

3)  The installation "cannot reach the update site" error remains in 3.4.1. 
But you probably knew that too. 

There are other annoying quirks, but they matter less.  Thanks for all your
work, & hope this helps.  I've used OpenOffice for years (and as it stands,
wish I could go back to the releases of a few years ago). 


You are receiving this mail because:
You are the assignee for the bug.

View raw message