Bug 374222 - file layer export bug
Summary: file layer export bug
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.1.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-12-27 18:41 UTC by Manga Tengu
Modified: 2018-10-28 03:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
my script (327 bytes, application/x-shellscript)
2016-12-28 09:21 UTC, Manga Tengu
Details
kra sample file (2.88 MB, application/x-krita)
2016-12-28 10:20 UTC, Manga Tengu
Details
file layer (3.53 KB, image/png)
2016-12-28 10:22 UTC, Manga Tengu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Manga Tengu 2016-12-27 18:41:04 UTC
When exporting a .kra containing a file layer which displays correctly the krita app will ask you to relocate the file because it doesn't find it at "X" while X is actually the right path.
Then I need to specify the file by hand for each file in my batch everytime.
This happens to me with krita 2.9.7 and the 3.1.1 appImage.
Comment 1 Halla Rempt 2016-12-28 09:03:56 UTC
Hm, I have never seen this happen. What is the exact path to the file layer, and what is the file format you export to? Are you exporting from the gui, or on the command line?
Comment 2 Manga Tengu 2016-12-28 09:21:38 UTC
Created attachment 103034 [details]
my script

my lovely script
Comment 3 Halla Rempt 2016-12-28 09:28:36 UTC
What is the full path to the place from where you run the script?
Comment 4 Halla Rempt 2016-12-28 09:29:00 UTC
(Oh, and btw -- why don't you just get the mergedimage.png from the .kra file?)
Comment 5 Manga Tengu 2016-12-28 09:34:15 UTC
(In reply to Boudewijn Rempt from comment #3)
> What is the full path to the place from where you run the script?

Added an attachement, lost my comment :(...

So I was saying: I'm doing it in the commandLine via my trusty shell script that usually works fine as long as there is no file layer in the kra file.

The real path to the kra:
/media/b/3A6C7A2A6C79E155/Images WASTE/Manga/chapitre_7/pages/kra
The real path to the file layer:
/media/b/3A6C7A2A6C79E155/Images WASTE/Manga/chapitre_7/pages/svg/png

I place myself in the real path and launch my script (the attachement) and get:
****************************
The file associated to a file layer with the name "Cache" is not found.

Expected path:
/../svg/png/waste_c7_p10.png

Do you want to locate it manually?
****************************
if I concat the kra path and this relative path I get:
/media/b/3A6C7A2A6C79E155/Images WASTE/Manga/chapitre_7/pages/kra/../svg/png/waste_c7_p10.png
which is right (file name included).

Please note 3A6C7A2A6C79E155 is the name of my hard drive I mount.

I get the same issue with 2.9.7 and 3.1.1
Comment 6 Manga Tengu 2016-12-28 09:35:15 UTC
(In reply to Boudewijn Rempt from comment #4)
> (Oh, and btw -- why don't you just get the mergedimage.png from the .kra
> file?)

You mean pixelate the file layer into a regular paint layer ?
If I need to modify it later I lose the advantage of file layer.
Comment 7 Halla Rempt 2016-12-28 09:40:52 UTC
Hm... I'd also like to see one of the kra files. If there's a path in there that really starts with a /, then that's obviously one of the problems. At that point it's no longer relative but absolute. It might also be a problem that there's a space in the path.

The other thing is that a .kra file is a zip file; inside the zip file is a full-size preview of your image in png format. Getting that instead of asking krita to convert the image to png is more efficient.
Comment 8 Manga Tengu 2016-12-28 09:48:52 UTC
(In reply to Boudewijn Rempt from comment #7)
> Hm... I'd also like to see one of the kra files. If there's a path in there
> that really starts with a /, then that's obviously one of the problems. At
> that point it's no longer relative but absolute. It might also be a problem
> that there's a space in the path.
> 
> The other thing is that a .kra file is a zip file; inside the zip file is a
> full-size preview of your image in png format. Getting that instead of
> asking krita to convert the image to png is more efficient.

The / I'm writing is to give you the absolute path. In the script it's not present as I execute the script right aside from the files.
The script actually just calls a file name with no directories before.
There are no spaces in the kra files names.

Btw Yes I'll gladly use that ready to use png, but how do I access it ?
Comment 9 Halla Rempt 2016-12-28 10:06:06 UTC
Use the "unzip" utility to extract the file -- it's always called the same thing. But I'd still like to have access to one of your files to see what's up...
Comment 10 Manga Tengu 2016-12-28 10:19:24 UTC
(In reply to Boudewijn Rempt from comment #9)
> Use the "unzip" utility to extract the file -- it's always called the same
> thing. But I'd still like to have access to one of your files to see what's
> up...

I managed to get it under 4mb (60 originally) so here you go
Comment 11 Manga Tengu 2016-12-28 10:20:19 UTC
Created attachment 103036 [details]
kra sample file

the kra file.
I'll set the file layer which is called Cache in another attachement
Comment 12 Manga Tengu 2016-12-28 10:22:32 UTC
Created attachment 103037 [details]
file layer

Cache is  the file layer for the sample kra file
it is the same size and resolution
Comment 13 Manga Tengu 2016-12-28 10:29:31 UTC
Please not that this time adding a file layer worked...maybe because I reduced the size of the kra file ?
(In another bug report (374223) I reported it didn't work with the 3.1.1 appImage but it seems more tricky than that. I'll continue this in the other report)
Comment 14 wolthera 2017-10-18 13:38:31 UTC
I think I fixed this when I attempted to get the new file layer button to work. The file layer button is in 3.3.1(though, there's a little bug with toggling layer visibility that has to wait till 3.3.2). Could you check if you can still reproduce?
Comment 15 Andrew Crouthamel 2018-09-28 02:33:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 16 Andrew Crouthamel 2018-10-28 03:26:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!