-
Notifications
You must be signed in to change notification settings - Fork 71
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
go-appimaged continuus error codes logged #240
Comments
This occurs when both |
Since that PR has been open for over a month, any chance the fix for this issue can get merged independently? |
You could always build my fork, or you can add the single line I forgot and it should work properly. diff --git a/src/appimaged/udisks.go b/src/appimaged/udisks.go
index 7295ce1..efdb140 100644
--- a/src/appimaged/udisks.go
+++ b/src/appimaged/udisks.go
@@ -127,6 +127,7 @@ retry:
} else {
log.Println("org.kde.Solid.PowerManagement might not be started yet. Waiting a moment then retrying")
time.Sleep(500 * time.Millisecond)
+ retried = true
goto retry
}
} else { |
The progam itself seems to work fine, creating and deleting menu entries for appimages, but a continuous stream of the following message is being created, e.g.
2023/01/08 12:18:58 org.kde.Solid.PowerManagement might not be started yet. Waiting a moment then retrying
The message is repeated about twice a second.
The go-appimaged program works on Arch Linux, Debian Bookworm, Fedora 37 and OpenSUSE Tumbleweed. But the error message occurs on all of the distros too.
The text was updated successfully, but these errors were encountered: