Org Freedesktop Dbus Error Noreply Raised
2010-11-09 64 This bug affects 13 people Affects Status Importance Assigned to Milestone ubuntuone-client (Ubuntu) Edit Invalid Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: ubuntuone-client (Ubuntu) Filed here by: Jeff Lane When: 2010-11-09 Completed: 2011-12-01 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: ubuntuone-client While trying to add a folder to Ubuntu One using u1sdtool, I noticed that I kept getting these dbus errors... finally I tried u1sdtool -q and that failed to actually stop the syncdaemon. So I killed off the syncdaemon manually and tried restarting but this is what happened: bladernr@klaatu:~/development/checkbox/jobs$ u1sdtool --start Oops, an error ocurred: Traceback (most recent call last): Failure: dbus.exceptions.DBusException: 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 dbus timeout errors are the same ones I got previously when I tried to do ANYTHING with u1sdtool while syncdaemon was running. Unfortunately, I think the only way to get a working system again is to reboot, which not an optimal fix for whatever is causing this problem. First, this is what happened when I tried subscribing a folder to be synced: bladernr@klaatu:~/development/checkbox/jobs$ u1sdtool --subscribe-folder=/home/blade
Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug1242798 - DBus traceback happens when registration and attaching subscriptions. Summary: DBus traceback happens when registration and attaching subscriptions. Status: CLOSED DUPLICATE of bug 1241247 Aliases: None Product: Red Hat Enterprise Linux 7 Classification: Red Hat Component: subscription-manager (Show https://bugs.launchpad.net/bugs/672884 other bugs) Sub Component: --- Version: 7.2 Hardware: Unspecified Unspecified Priority unspecified Severity unspecified TargetMilestone: rc TargetRelease: --- Assigned To: candlepin-bugs QA Contact: John Sefler Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2015-07-14 04:22 EDT by qianzhan Modified: 2015-07-30 18:50 EDT (History) CC List: https://bugzilla.redhat.com/show_bug.cgi?id=1242798 3 users (show) alikins gxing shihliu See Also: Fixed In Version: subscription-manager-1.15.7-1 Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2015-07-30 18:50:04 EDT Type: Bug Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) rhsm.log (63.74 KB, text/plain) 2015-07-14 04:22 EDT, qianzhan no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description qianzhan 2015-07-14 04:22:02 EDT Description of problem: DBus traceback happens when registration and attaching subscriptions. Version-Release number of selected component (if applicable): How reproducible: always. Steps to Reproduce: 1. Remove rhsm.log [root@dhcp-128-65 ~]# rm -rf /var/log/rhsm/rhsm.log 2. Register system and check rhsm.log: [root@dhcp-128-65 ~]# subscription-manager register Username: admin Password: The system has been registered with ID: 3d523f7c-284c-40ff-9f98-3fe72d50407f [root@dhcp-128-65 ~]# tail -20 /var/log/rhsm/rhsm.log ImportError: No module named ga 2015-07-14 08:15:28,797 [DEBUG] subscription-manager:6422 @d
shutdown after kernel-update. How can i solve this? anilv1st September 2010, 06:00 PMJust try the following commands, # plymouth-set-default-theme -l # plymouth-set-default-theme -R