-
Notifications
You must be signed in to change notification settings - Fork 11
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
New eog version does not install additional files #5
Comments
Quick follow-up; it does not seem to be specific to when you're upgrading from a self-installed version. After having removed the extension completely, logged out and back in, I re-installed the extension but it still does not seem to trigger the installation of the Edit: I can confirm that when I manually install the accompanying tool, the extension starts working right away. I ran |
That's strange, it should've shown a notification to install when it's enabled the first time after a gnome-shell restart. I'll see if I can figure it out |
Easy fix, I moved the firstRun variable to be a class member but forgot to set it to true in the constructor |
The update is out on EGO now |
Awesome, you're lightning fast! I just had a change to boot up my laptop and after logging out and back in I got the additional step notification, entered my password, and then success notification! I didn't try this after first uninstalling the extension, but everything is still working after this update at least. Thank you again! :) |
It seems like after automatically having the extension updated to the eog version, the installation step is not triggered (presumably because the extension was already considered installed previously), but this seems to break the functionality of the extension, as it is unable to located required files (e.g.
/usr/local/bin/screenpad-$USER
). Or at least I think that's what happened?Attached are the journal logs I could find, this is after attempting to press the disable secondary screen button and adjusting the brightness (neither of which actually worked, of course):
The text was updated successfully, but these errors were encountered: