| 2012-04-06 09:47:41 |
Rafał Cieślak |
bug |
|
|
added bug |
| 2012-04-06 09:49:20 |
Rafał Cieślak |
description |
In case the client is unable to start the daemon, it should a) try again and again, every few seconds or b) notify the user about the problem. As for now, it crashes instead, with
AttributeError: 'TrophyinfoWindow' object has no attribute 'ask_to_start_daemon'
because the notification has been recently removed.
It may be possible to join both a) and b) by using following procedure:
1) Try starting the daemon, if it succeeds - continue normally
2) If it does not, set appropriate message in the status bar
3) Wait 15 seconds, and proceed to 1) |
In case the client is unable to start the daemon (which may happen due to packaging problems, binary file unavailability, daemon crashing on startup due to some bug, or invalid daemon installation), it should a) try again and again, every few seconds or b) notify the user about the problem. As for now, it crashes instead, with
AttributeError: 'TrophyinfoWindow' object has no attribute 'ask_to_start_daemon'
because the notification has been recently removed.
It may be possible to join both a) and b) by using following procedure:
1) Try starting the daemon, if it succeeds - continue normally
2) If it does not, set appropriate message in the status bar
3) Wait 15 seconds, and proceed to 1) |
|
| 2012-04-06 09:57:22 |
Rafał Cieślak |
ubuntu-accomplishments-system: assignee |
|
Rafal Cieślak (rafalcieslak256) |
|
| 2012-04-06 09:58:36 |
Rafał Cieślak |
tags |
|
bitesize |
|
| 2012-04-06 10:01:42 |
Rafał Cieślak |
description |
In case the client is unable to start the daemon (which may happen due to packaging problems, binary file unavailability, daemon crashing on startup due to some bug, or invalid daemon installation), it should a) try again and again, every few seconds or b) notify the user about the problem. As for now, it crashes instead, with
AttributeError: 'TrophyinfoWindow' object has no attribute 'ask_to_start_daemon'
because the notification has been recently removed.
It may be possible to join both a) and b) by using following procedure:
1) Try starting the daemon, if it succeeds - continue normally
2) If it does not, set appropriate message in the status bar
3) Wait 15 seconds, and proceed to 1) |
In case the client is unable to connect to the daemon after trying to run it (which may happen due to:
- packaging problems
- binary file unavailability
- daemon crashing on startup due to some bug (this actually may be a likely case)
- invalid daemon installation
- problems with DBus connection),
it should a) try again and again, every few seconds or b) notify the user about the problem.
As for now, it crashes instead, with
AttributeError: 'TrophyinfoWindow' object has no attribute 'ask_to_start_daemon'
because the notification has been recently removed.
It may be possible to easily join both a) and b) by using following procedure:
1) Try starting the daemon, if it succeeds - continue normally,
2) If it does not, set appropriate message in the status bar,
3) Wait several seconds, and proceed to 1). |
|
| 2012-04-06 10:02:38 |
Rafał Cieślak |
branch linked |
|
lp:~rafalcieslak256/ubuntu-accomplishments-system/daemon-fails |
|
| 2012-04-06 16:27:39 |
Jono Bacon |
ubuntu-accomplishments-system: status |
New |
Fix Committed |
|
| 2012-04-06 16:35:22 |
Jono Bacon |
ubuntu-accomplishments-system: milestone |
|
0.1 |
|
| 2012-04-06 16:35:43 |
Jono Bacon |
ubuntu-accomplishments-system: importance |
Undecided |
Medium |
|
| 2012-04-09 05:26:00 |
Jono Bacon |
affects |
ubuntu-accomplishments-system |
ubuntu-accomplishments-viewer |
|
| 2012-04-09 05:26:00 |
Jono Bacon |
ubuntu-accomplishments-viewer: milestone |
0.1 |
|
|
| 2012-04-09 05:26:26 |
Jono Bacon |
ubuntu-accomplishments-viewer: milestone |
|
0.1 |
|
| 2012-05-01 06:27:08 |
Jono Bacon |
ubuntu-accomplishments-viewer: status |
Fix Committed |
Fix Released |
|
