Flatpak doesn't work #1

Closed
opened 2024-11-10 14:38:44 +01:00 by Adiee5 · 3 comments

Hello, I've downloaded this app in form of flatpak, when i ran this, app crashed before even any gui appeared. here are console logs:

$ flatpak run me.sergiotarxz.JapaChar
Couldn't find an appropriate DIRECTORY for Inline to use.

 at /app/JapaChar/scripts/japchar.pl line 0.
INIT failed--call queue aborted, <DATA> line 1.
Hello, I've downloaded this app in form of flatpak, when i ran this, app crashed before even any gui appeared. here are console logs: ``` $ flatpak run me.sergiotarxz.JapaChar Couldn't find an appropriate DIRECTORY for Inline to use. at /app/JapaChar/scripts/japchar.pl line 0. INIT failed--call queue aborted, <DATA> line 1. ```
Owner

Hello, I've downloaded this app in form of flatpak, when i ran this, app crashed before even any gui appeared. here are console logs:

$ flatpak run me.sergiotarxz.JapaChar
Couldn't find an appropriate DIRECTORY for Inline to use.

 at /app/JapaChar/scripts/japchar.pl line 0.
INIT failed--call queue aborted, <DATA> line 1.

Hi, can you share if you are using x86_64 or aarch64 and distribution?

> Hello, I've downloaded this app in form of flatpak, when i ran this, app crashed before even any gui appeared. here are console logs: > > ``` > $ flatpak run me.sergiotarxz.JapaChar > Couldn't find an appropriate DIRECTORY for Inline to use. > > at /app/JapaChar/scripts/japchar.pl line 0. > INIT failed--call queue aborted, <DATA> line 1. > ``` Hi, can you share if you are using x86_64 or aarch64 and distribution?
Author

I'm using x86_64 Arch Linux

I'm using x86_64 Arch Linux
Owner

I have migrated from Inline::C to XS and that solved the issue, Inline::C assumes _Inline is property of the user running the program even if it doesn't need to write into the directory, that was causing the issues when using system installed remotes.

I have migrated from Inline::C to XS and that solved the issue, Inline::C assumes _Inline is property of the user running the program even if it doesn't need to write into the directory, that was causing the issues when using system installed remotes.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sergiotarxz/JapaChar#1
No description provided.