amd athlon 64 x2 5000+, 4gb ram, nvidia 8400gs + 256mb video
os: windows 7 sp1 home premium 64 bit, sun java jre v6-28
problem occurs in Calc, Writer and Base
Open Tools/Options/Internet. Just clicking on the word Proxy immediately crashes Calc, Writer or Base and orphans the options dialog. The dialog must then be forcibly terminated. Initiates document recovery mode.
This issue occurs every time, is consistent and repeatable.
Also occurs on 3.4.3
Discovered crash occurs immediately when selecting ANY Internet option (Proxy, Search or Browser Plug-in)
Not reproducible for me. You can try with a clean user profile.
I did a clean install of 3.4.3 after uninstalling LibreOffice and removing
product folders from %appdata%/roaming and %programfiles%.
It still crashes when selecting ANY Internet option (proxy, search or
browser plug-in). Are profiles kept elsewhere?
On Tue, Sep 6, 2011 at 1:52 PM, <email@example.com> wrote:
> --- Comment #2 from vitriol <firstname.lastname@example.org> 2011-09-06
> 10:52:11 PDT ---
> Not reproducible for me. You can try with a clean user profile.
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
[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:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
The problem persists with 3.4.4 (release) and 3.5.0 beta 2.
If you can provide methods to create more detailed debug logs, please do.
I cannot reproduce this with LibreOffice 22.214.171.124 Build ID: dc9775d-05ecbee-0851ad3-1586698-727bf66 under Windws 7 32-bit
Quite few similar reports - see Bug 47044 comment 5.
@Bfoman: thanks for finding all those duplicates!
*** This bug has been marked as a duplicate of bug 47044 ***