Description of problem: Stopped timer for one task. Add earlier activity. ...problem to report. Version-Release number of selected component: hamster-time-tracker-1.04-4.fc22 Additional info: reporter: libreport-2.6.3 cmdline: python /usr/bin/hamster dso_list: dbus-python-1.2.0-7.fc22.x86_64 executable: /usr/bin/hamster kernel: 4.1.6-201.fc22.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: connection.py:651:call_blocking: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. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/hamster/edit_activity.py", line 302, in on_window_key_pressed self.on_save_button_clicked(None) File "/usr/lib/python2.7/site-packages/hamster/edit_activity.py", line 209, in on_save_button_clicked runtime.storage.update_fact(self.fact_id, fact, temporary) File "/usr/lib/python2.7/site-packages/hamster/client.py", line 222, in update_fact temporary_activity) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) 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. Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SessionBus (session) at 0x7ff1daf977d0> args: (dbus.Int32(17890), u'SW322150@P8,Ming ST asking me to look. #Brazos #P8 #help', 1442580060, 1442581260, False) object_path: '/org/gnome/Hamster' signature: u'isiib' bus_name: dbus.UTF8String(':1.69') get_args_opts: {'byte_arrays': False, 'utf8_strings': False} timeout: -1.0 kwargs: {} dbus_interface: 'org.gnome.Hamster' message: <dbus.lowlevel.MethodCallMessage path: /org/gnome/Hamster, iface: org.gnome.Hamster, member: UpdateFact dest: :1.69> method: 'UpdateFact' Potential duplicate: bug 1044520
Created attachment 1101062 [details] File: backtrace
Created attachment 1101063 [details] File: environ
hamster-time-tracker-2.0-0.1.rc1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-401ab10316
hamster-time-tracker-2.0-0.2.rc1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e7bfef7108
hamster-time-tracker-2.0-0.2.rc1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e7bfef7108
hamster-time-tracker-2.0-0.2.rc1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Missed this update. Update from 1.04-5.fc23 to 2.0-0.2.rc1.fc23 resulted in crash. Bug 1307110 created by Report tool: https://bugzilla.redhat.com/show_bug.cgi?id=1307110
Too bad that we could not test better when 2.0 rc1 has been in testing. *** This bug has been marked as a duplicate of bug 1307110 ***