Opened 13 years ago
Closed 13 years ago
#2269 closed defect (fixed)
sugar-emulator crashes on startup (rpms)
| Reported by: | bernie | Owned by: | tomeu |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Unspecified | Keywords: | |
| Cc: | pbrobinson | Distribution/OS: | Fedora |
| Bug Status: | Unconfirmed |
Description
Tested on Fedora 14, using the 0.89.6 packages.
After a few seconds, the emulator quits. This is what I've found in shell.log:
Traceback (most recent call last):
File "/usr/bin/sugar-session", line 274, in <module>
main()
File "/usr/bin/sugar-session", line 257, in main
home_window = homewindow.get_instance()
File "/usr/lib/python2.7/site-packages/jarabe/desktop/homewindow.py", line 191, in get_instance
_instance = HomeWindow()
File "/usr/lib/python2.7/site-packages/jarabe/desktop/homewindow.py", line 65, in __init__
self._mesh_box = MeshBox()
File "/usr/lib/python2.7/site-packages/jarabe/desktop/meshbox.py", line 410, in __init__
self._model = neighborhood.get_model()
File "/usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py", line 862, in get_model
_model = Neighborhood()
File "/usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py", line 586, in __init__
obj = bus.get_object(ACCOUNT_MANAGER_SERVICE, ACCOUNT_MANAGER_PATH)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
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.
Change History (3)
comment:1 Changed 13 years ago by bernie
- Component changed from untriaged to sugar
- Distribution/OS changed from Unspecified to Fedora
- Owner set to tomeu
- Version changed from Unspecified to Git as of bugdate
comment:2 Changed 13 years ago by bernie
- Cc pbrobinson added
- Summary changed from sugar-emulator crashes on startup to sugar-emulator crashes on startup (rpms)
comment:3 Changed 13 years ago by bernie
- Resolution set to fixed
- Status changed from new to closed
This is fixed now.
Note: See
TracTickets for help on using
tickets.
This bug may be related to #2270, although the tracebacks in the logs are very different.