-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
License not persisting between reboots #376
Comments
same problem on linux arch, license key not persisting:
I'm using the VPN for work so I'm forced to use for the third time the license activation... |
Hi @anthropos9, @habby1337 can you help check the content under the |
what should i look for? |
The license file is generated. The license name is prefixed by the MAC address. Looks like your MAC address changes when restarts. |
I'll try to fix this. |
thank you very much. just an heads up i never changed anything on the machine, is a laptop, so every component is still the same. but while this is getting fixed, is there a way to increase the licenses or a way to use the CLI so i can send the fake HIP report and connect to the portal (pretty much the same configs as the gui settings) so i can keep working? |
The license can be managed on https://app.lemonsqueezy.com/my-orders, feel free to deactivate the unused activations. The CLI version also supports passing the HIP script, via the |
This is what's in my
|
@anthropos9 @habby1337 This should be fixed in 2.3.2. |
@yuezk my initial tests have been positive. I added the license then rebooted and it persisted. Thanks for your help. |
Describe the bug
I bought a license and added it to my client. It worked, but after rebooting my computer it now says that I don't have a license installed.
Expected behavior
The license should persist between reboots until it expires.
Logs
Environment:
ps aux | grep 'gnome-keyring\|kwalletd5' | grep -v grep
: [Required for secure store error]sdean 3637 0.0 0.0 463004 9152 ? SLl Jun12 0:05 /usr/bin/gnome-keyring-daemon --daemonize --login
The text was updated successfully, but these errors were encountered: