https://bugs.documentfoundation.org/show_bug.cgi?id=158364

            Bug ID: 158364
           Summary: Crash during the execution of BASIC macro with L10N
                    procedures on ExportToPOTFile
           Product: LibreOffice
           Version: 24.2.0.0 alpha1+ Master
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: proj...@tongtang.pl

Description:
Crash during the execution of BASIC macro with L10N procedures also with the
example itself from the help:
https://help.libreoffice.org/24.2/pl/text/sbasic/shared/03/sf_l10n.html?&DbPAR=SHARED&System=WIN
---
System info:
Library :   ScriptForge
Service :   L10N
Method :    ExportToPOTFile

The ScriptForge library has crashed. The reason is unknown.
Maybe a bug that could be reported on
    https://bugs.documentfoundation.org/

More details : 

Location : FileSystem.OpenTextFile/1567
Wystąpił wyjątek 
Type: com.sun.star.ucb.ContentCreationException
Message: Unable to create Content for <file:///myFile.pot>: at
C:/cygwin/home/tdf/jenkins/daily_workspace/tb/src_master/ucb/source/ucp/file/prov.cxx:122
at
C:/cygwin/home/tdf/jenkins/daily_workspace/tb/src_master/ucbhelper/source/client/content.cxx:264.

THE EXECUTION IS CANCELLED.

Steps to Reproduce:
1. write simple basic sub with service L10N and with export to po file (exaple
lines from help are enough good)
2. execute it
3. that's all

Actual Results:
THE EXECUTION IS CANCELLED.

Expected Results:
create PO file and go on macro execution


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 8566b767a24bc2c382391b6eb154f410c9f865b8
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: pl-PL (pl_PL); UI: pl-PL
Calc: threaded

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

Reply via email to