New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help wanted with AppImage #92

Open
csete opened this Issue Dec 10, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@csete
Owner

csete commented Dec 10, 2017

I have a script that can generate an AppImage from our PPA. It is based on the official documentation.

The generated package runs but the program can not find any image or data files from the package.

I need somebody to dig into it and find out how to properly package.

@csete csete added the help wanted label Dec 10, 2017

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Dec 12, 2017

Hi @csete - happy to help. Can you upload the AppImage for testing? Thanks.

probonopd commented Dec 12, 2017

Hi @csete - happy to help. Can you upload the AppImage for testing? Thanks.

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd commented Dec 12, 2017

In general, please refer to this section of the documentation:
https://github.com/AppImage/AppImageKit/wiki/Creating-AppImages#no-hard-coded-paths

@csete

This comment has been minimized.

Show comment
Hide comment
@csete

csete Dec 12, 2017

Owner

Hi @probonopd

Thanks for getting in touch even before I contacted you :)

I think you are right regarding hard coded paths. It is a Gtk+ based application and uses autotools. The data and image paths are defined at compile time based on the --prefix=... option.

I will check the documentation you link to. I have uploaded the scripts I used and the AppImage here:
http://files.oz9aec.net/gpredict/temp/

Owner

csete commented Dec 12, 2017

Hi @probonopd

Thanks for getting in touch even before I contacted you :)

I think you are right regarding hard coded paths. It is a Gtk+ based application and uses autotools. The data and image paths are defined at compile time based on the --prefix=... option.

I will check the documentation you link to. I have uploaded the scripts I used and the AppImage here:
http://files.oz9aec.net/gpredict/temp/

@probonopd

This comment has been minimized.

Show comment
Hide comment
@probonopd

probonopd Dec 12, 2017

Thanks @csete - does not run for me:

me@host:~$ Downloads/Gpredict-2.0.glibc-x86_64.AppImage 

** (gpredict:28105): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
me@host:~$ cat /etc/os-release 
PRETTY_NAME="Deepin 15"
NAME="Deepin"
VERSION_ID="15.5"

But yes, the first step is to get rid of the hardcoded absolute paths.

probonopd commented Dec 12, 2017

Thanks @csete - does not run for me:

me@host:~$ Downloads/Gpredict-2.0.glibc-x86_64.AppImage 

** (gpredict:28105): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
me@host:~$ cat /etc/os-release 
PRETTY_NAME="Deepin 15"
NAME="Deepin"
VERSION_ID="15.5"

But yes, the first step is to get rid of the hardcoded absolute paths.

@csete csete added this to the v2.4 milestone Jan 20, 2018

@csete

This comment has been minimized.

Show comment
Hide comment
@csete

csete Jan 21, 2018

Owner

So, the latest 2.2.1 release now has an AppImage where the paths have been fixed using the binary patch method. Since the hardcoded paths only exist three places I felt this was the easiest.

I have not yet looked into the runtime error you encountered.

Owner

csete commented Jan 21, 2018

So, the latest 2.2.1 release now has an AppImage where the paths have been fixed using the binary patch method. Since the hardcoded paths only exist three places I felt this was the easiest.

I have not yet looked into the runtime error you encountered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment