Bug 585079 - [abrt] crash in gnome-activity-journal-0.3.3-1.fc13: view.py:142:jump:IndexError: list index out of range
Summary: [abrt] crash in gnome-activity-journal-0.3.3-1.fc13: view.py:142:jump:IndexEr...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-activity-journal
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mads Villadsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c8f02154
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-23 05:09 UTC by David Le Sage
Modified: 2010-08-11 18:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-11 18:51:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (507 bytes, text/plain)
2010-04-23 05:09 UTC, David Le Sage
no flags Details

Description David Le Sage 2010-04-23 05:09:27 UTC
abrt 1.0.9 detected a crash.

architecture: i686
cmdline: python /usr/share/gnome-activity-journal/gnome-activity-journal
component: gnome-activity-journal
executable: /usr/share/gnome-activity-journal/gnome-activity-journal
kernel: 2.6.33.1-19.fc13.i686.PAE
package: gnome-activity-journal-0.3.3-1.fc13
reason: view.py:142:jump:IndexError: list index out of range
release: Fedora release 13 (Goddard)

backtrace
-----
view.py:142:jump:IndexError: list index out of range

Traceback (most recent call last):
  File "/usr/share/gnome-activity-journal/src/main.py", line 205, in moveback
    self.activityview.jump(-86400)
  File "/usr/share/gnome-activity-journal/src/view.py", line 142, in jump
    diff = self.start - self.cal.histogram.get_datastore()[0][0]
IndexError: list index out of range

Local variables in innermost frame:
self: <ActivityView object at 0xa42c34c (src+view+ActivityView at 0xa3c4210)>
offset: -86400

Comment 1 David Le Sage 2010-04-23 05:09:29 UTC
Created attachment 408493 [details]
File: backtrace

Comment 2 Mads Villadsen 2010-08-11 18:51:40 UTC
I am unable to reproduce this. If you can provide a step-by-step guide on how to trigger this problem, please feel free to reopen this bug.


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