Bug 123696 - "Image filter not found" then "General input/output error" when exporting Draw document to PNG
Summary: "Image filter not found" then "General input/output error" when exporting Dra...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2019-02-25 10:24 UTC by Mike Kaganski
Modified: 2024-06-19 00:28 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2019-02-25 10:24:59 UTC
After https://gerrit.libreoffice.org/plugins/gitiles/core/+/046df0a876b3d948bb1e14443c00c180bc8cccaa, trying to export a Draw document to PNG, after I confirm settings (e.g., resolution) in export filter dialog, I get a warning:

> "Image filter not found"

and then error:

> "Error saving the document Untitled 1:
> General Error.
> General input/output error."

Also see it with Version: 6.2.1.1 (x64)
Build ID: 757c58e8cb70b2982843211a54750fb3cd79acd5
CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded,

and with current master (Build ID: ae4e0a81753dd280f6b77b5ee61cf7e9f85e5cfe).

To test, I used a new empty Draw document.

Tested on Windows 10.
Comment 1 Telesto 2019-02-25 16:22:00 UTC
Repro
Version: 6.3.0.0.alpha0+
Build ID: aa51774e6a309f277e71ca3a3b9d5d5b4b3dbf1a
CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-02-18_06:06:03
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 2 Xisco Faulí 2019-06-03 12:07:10 UTC
I can't reproduce it in

Version: 6.3.0.0.beta1+
Build ID: 219e128553645911685b6061f7c5ea359a4c551c
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

nor in

Versión: 6.2.4.2
Id. de compilación: 2412653d852ce75f65fbfa83fb7e7b669a126d64
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: threaded

@Mike Kaganski, @Telesto, could you please retest in master? If you still reproduce, please provide a file to reproduce it. Thanks
Comment 3 Telesto 2019-06-03 12:39:01 UTC
No Repro
Version: 6.4.0.0.alpha0+ (x86)
Build ID: 93477d1a963e38e3319013e43835a8ffef200972
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-06-02_10:16:52
Locale: it-IT (nl_NL); UI-Language: en-US
Calc: threaded

The dimensions of the resulting export (File -> Export -> PNG) are quite off.. (fine for PDF/JPG). Be might be a report for that somewhere
Comment 4 Xisco Faulí 2019-06-03 12:39:54 UTC
(In reply to Telesto from comment #3)
> No Repro
> Version: 6.4.0.0.alpha0+ (x86)
> Build ID: 93477d1a963e38e3319013e43835a8ffef200972
> CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
> TinderBox: Win-x86@42, Branch:master, Time: 2019-06-02_10:16:52
> Locale: it-IT (nl_NL); UI-Language: en-US
> Calc: threaded
> 
> The dimensions of the resulting export (File -> Export -> PNG) are quite
> off.. (fine for PDF/JPG). Be might be a report for that somewhere

Yes, bug 105998
Comment 5 scottie 2019-10-14 04:40:06 UTC
this bug is still present in v6.2.7.1 (x64) for export to jpg
Comment 6 scottie 2019-10-14 05:55:33 UTC
just found out "image Filter not found" when exporting to jpg from Libreoffice draw might mean the attributes user entered for the image export might be to large.

try changing units cm to px (if it was actually px the user was after)
Comment 7 scottie 2019-10-14 05:59:37 UTC
still a more helpful error message would be more helpful
Comment 8 Mike Kaganski 2019-10-14 06:26:14 UTC
(In reply to scottie from comment #7)
> still a more helpful error message would be more helpful

Please file a separate issue about a better error message in case of wrong user input, which is a different problem. Thanks!