Bug 456759
| Summary: | Sync Error with HTC TyTN II Windows Mobile 6.1 | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rudolf <rudolf.kunzli> | |
| Component: | synce-sync-engine | Assignee: | Andreas Bierfert <andreas.bierfert> | |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 8 | |||
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | i386 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 480536 (view as bug list) | Environment: | ||
| Last Closed: | 2009-01-09 06:41:28 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
Please try with the synce upgrades from updates-testing. Also look at http://www.synce.org/moin/SynceSetup for instructions on how to setup the connection correctly. Please report back if this does not fix your problem. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: sync-engine gives an error message when started Version-Release number of selected component (if applicable):0.11 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: [root@dhcppc254 rudolf]# sync-engine SynCE sync-engine starting up 2008-07-26 18:00:11,290 DEBUG syncengine : running main loop 2008-07-26 18:00:11,291 DEBUG syncengine : creating SyncEngine object Traceback (most recent call last): File "/usr/bin/sync-engine", line 149, in <module> engine = SyncEngine(configObj,mainloop) File "/usr/lib/python2.5/site-packages/SyncEngine/kernel.py", line 70, in __init__ dbus.service.Object.__init__(self, dbus.service.BusName(DBUS_SYNCENGINE_BUSNAME, bus=dbus.SessionBus()), DBUS_SYNCENGINE_OBJPATH) File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 218, in __new__ mainloop=mainloop) File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 107, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 121, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) 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. Expected results: Additional info: