Bug 1086709 - [abrt] hamster-time-tracker: __init__.py:58:__init__:ValueError: invalid literal for int() with base 10: '-7,'
Summary: [abrt] hamster-time-tracker: __init__.py:58:__init__:ValueError: invalid lite...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: hamster-time-tracker
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:35fdec37c5d2187b74b176bb4d6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-11 11:19 UTC by Matej
Modified: 2015-02-17 20:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 20:09:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (853 bytes, text/plain)
2014-04-11 11:19 UTC, Matej
no flags Details
File: environ (1.31 KB, text/plain)
2014-04-11 11:20 UTC, Matej
no flags Details

Description Matej 2014-04-11 11:19:54 UTC
Version-Release number of selected component:
hamster-time-tracker-1.04-1.fc19

Additional info:
reporter:       libreport-2.2.0
cmdline:        python /usr/bin/hamster
executable:     /usr/bin/hamster
kernel:         3.13.7-100.fc19.x86_64.debug
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
__init__.py:58:__init__:ValueError: invalid literal for int() with base 10: '-7,'

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/hamster/today.py", line 451, in on_switch_activity_clicked
    tags = self.new_tags.get_text().decode("utf8", "replace"))
  File "/usr/lib/python2.7/site-packages/hamster/lib/__init__.py", line 58, in __init__
    self.start_time = dt.datetime.now() + dt.timedelta(minutes = int(potential_time))
ValueError: invalid literal for int() with base 10: '-7,'

Local variables in innermost frame:
potential_time: u'-7,'
category: ''
activity_id: None
description: ''
potential_end_time: None
tags: u''
start_time: None
activity: u'-7, ostatn\xed@soukrom\xe9'
self: <hamster.lib.Fact object at 0x273f3d0>
input_parts: [u'-7,', u'ostatn\xed@soukrom\xe9']
end_time: None
delta: None
date: None
id: None

Comment 1 Matej 2014-04-11 11:19:59 UTC
Created attachment 885375 [details]
File: backtrace

Comment 2 Matej 2014-04-11 11:20:01 UTC
Created attachment 885376 [details]
File: environ

Comment 3 cqi 2014-11-25 06:38:10 UTC
what were you doing when this error happened

Comment 4 Fedora End Of Life 2015-01-09 21:18:09 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 5 Fedora End Of Life 2015-02-17 20:09:27 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.