-
Notifications
You must be signed in to change notification settings - Fork 93
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
dnfdaemon do_transaction error #1978
Comments
I should say that this is issue is blocking. It happens very often here. Can we talk about this as we had for list_fd? i experienced it in both fedora and mageia |
Hmm, this sounds like the |
I haven't found that option described, anyway it seems not to work:
|
The Let me share the whole testing script, not only the line which set the timeout. I used made up
|
I maybe wrong in something, my patch is:
Same issue. I wonder if i can trap the exception and connect to daemon again. The transaction finishes correctly as far as i can say. |
Thank you, I'll check out the dnfdragora sources. |
I also created a test case by using a single script. |
Using dnfdragora I often have a noreply from dbus after a do_transaction call.
Called at
2025-01-02 17:09:52,987 [dnfdaemon.client]{dnfd_client.py:424}(DEBUG) __async_thread_loop proxy org.rpm.dnf.v0.Goal method do_transaction
Then i had some download signals and next:
2025-01-02 17:10:18,320 [dnfdaemon.client]{dnfd_client.py:478}(ERROR) __async_thread_loop (RunTransaction) proxy org.rpm.dnf.v0.Goal, method do_transaction - Exception org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
The text was updated successfully, but these errors were encountered: