Skip to content
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

Error In Settings View #15

Closed
jmwright opened this issue Jul 18, 2017 · 7 comments
Closed

Error In Settings View #15

jmwright opened this issue Jul 18, 2017 · 7 comments

Comments

@jmwright
Copy link

I'm running the latest AppImage on Ubuntu 16.04 64-bit. The app starts up fine, but I see the following error in the Settings view.

screenshot_2017-07-18_09-22-55

@jmwright
Copy link
Author

Just realized that there's an Application Info section of that settings screen.

screenshot_2017-07-18_09-57-56

@sabrehagen
Copy link
Member

sabrehagen commented Jul 18, 2017

Thanks for reporting this. When running the application for the first time, did you get a prompt that looked like this (except for Stemn)?

If you choose to integrate the app with your OS, our app will have the permissions to run at startup, and will be listed in Ubuntu's application launcher.

Alternatively, if you did see this dialog, clicked yes, and you're still seeing the red banner, then it is displaying in error and this is a bug.

@jmwright
Copy link
Author

Yes, I saw that dialog and clicked the "Yes" button. There is an item in my system tray for your app, so I'm not sure why it thinks it's not integrated. I haven't tried creating a project yet, so maybe it's the Dropbox integration or something?

@sabrehagen
Copy link
Member

We check for the existence of ${/home/you-user-name/.local/share/applications/appimagekit-STEMN.desktop to know if the Yes button was clicked on the integration dialogue. I expect this file doesn't exist for you. Can you check if it exists on your system?

@jmwright
Copy link
Author

The file that was created on my system has different capitalization appimagekit-stemn.desktop. With the Linux convention of case-sensitivity, it won't accept that as the same filename.

@sabrehagen
Copy link
Member

Thanks, we will update the check to be case insensitive :) Fixed in the next release!

@jmwright
Copy link
Author

Awesome, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants