-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Nextcloud AppImage Update does not work anymore - URL does not work #214
Comments
I'm not sure but you have a V in the version. |
The URL is correct like it is in my beginning post. I just copied it and it contains a "V": And as i posted before, it was already working. |
I am having similar issues with an app called "novelWriter". Today, I used GearLever to update "novelWriter" successfully - from 2.5.2 to 2.5.3. But judging from the logs, it was a messy process:
Afterwards, I noticed that I still had an app called "MuseScore" installed. It had an update available. But since I haven't been using it, I decided to uninstall it.
At some point along the line, I realized that "Check updates on system startup" is an option in GearLever. I enabled it. I don't remember if this was before or after I uninstalled MuseScore. Now, GearLever keeps telling me that there's an update available (red '1' notification icon in the dock), even though "novelWriter" currently is the only image being managed by GearLever. It's possible that this is a bug with the "Dash to Dock" Gnome Extension somehow. Maybe. I don't know how any of that stuff works. In the GearLever UI itself, GearLever tells me that "novelWriter" has "No updates available". I tried unpinning and re-pinning GearLevel to the dock to hopefully reset that notification icon. But so far I've had no luck with that. Rebooting the machine doesn't fix it either. Now, every time I tell GearLever to "Reload metadata" for "novelWriter" this is what the logs look like:
My biggest issue right now is that red notification icon. I'm going to continue battling to get rid of it... Wish me luck. The "does not return a valid content-type header" warning may or may not have anything to do with it. But I figured I'd share my logs from today's battle, in case they help with debugging the header error issue. :) |
Same here. With Orca-Slicer and Nextcould. Worked before without a problem.
|
Hi,
i update Nextclound via GitHub Release url.
I have constructed this URL with placeholder:
https://github.com/nextcloud-releases/desktop/releases/download/*/Nextcloud-*-x86_64.AppImage
The target URL is this as an example:
https://github.com/nextcloud-releases/desktop/releases/download/v3.15.2/Nextcloud-3.15.2-x86_64.AppImage
This is the error i get from Gearlever:
---- Application startup | version 2.3.2 2024-12-28 10:05:32,695 WARNING [BackgroudUpdatesFetcher.py:14] Fetching updates in the background 2024-12-28 10:05:32,695 INFO [AppImageProvider.py:77] Activating AppImage provider 2024-12-28 10:05:33,418 ERROR [UpdateManager.py:196] 404 Client Error: Not Found for url: https://github.com/nextcloud-releases/desktop/releases/download/*/Nextcloud-*-x86_64.AppImage 2024-12-28 10:05:33,418 WARNING [UpdateManager.py:200] Head request failed, trying with stream mode... 2024-12-28 10:05:33,559 ERROR [UpdateManager.py:209] 404 Client Error: Not Found for url: https://github.com/nextcloud-releases/desktop/releases/download/*/Nextcloud-*-x86_64.AppImage 2024-12-28 10:05:33,559 WARNING [UpdateManager.py:127] Provided url "https://github.com/nextcloud-releases/desktop/releases/download/*/Nextcloud-*-x86_64.AppImage" does not return a valid content-type header 2024-12-28 10:05:33,908 WARNING [BackgroudUpdatesFetcher.py:48] No available updates found
It worked in the past, but not anymore. Any ideas?
The text was updated successfully, but these errors were encountered: