abrt 1.0.8 detected a crash. architecture: x86_64 cmdline: /usr/bin/python /usr/bin/miro.real component: Miro executable: /usr/bin/miro.real kernel: 2.6.32.10-92.fc12.x86_64 package: Miro-2.5.4-3.fc12 reason: player.py:54:skip_forward:TypeError: unsupported operand type(s) for +: 'NoneType' and 'float' release: Fedora release 12 (Constantine) backtrace ----- player.py:54:skip_forward:TypeError: unsupported operand type(s) for +: 'NoneType' and 'float' Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/miro/frontends/widgets/gtk/window.py", line 127, in do_key_press_event return WrappedWindow.do_key_press_event(self, event) File "/usr/lib64/python2.6/site-packages/miro/frontends/widgets/gtk/window.py", line 113, in do_key_press_event if wrappermap.wrapper(self).emit('key-press', key, modifiers): File "/usr/lib64/python2.6/site-packages/miro/signals.py", line 155, in emit if callback.invoke(self, args): File "/usr/lib64/python2.6/site-packages/miro/signals.py", line 89, in invoke return callback(obj, *(args + self.extra_args)) File "/usr/lib64/python2.6/site-packages/miro/frontends/widgets/application.py", line 150, in on_key_press return playback.handle_key_press(key, mods) File "/usr/lib64/python2.6/site-packages/miro/frontends/widgets/playback.py", line 556, in handle_key_press app.widgetapp.on_skip_forward() File "/usr/lib64/python2.6/site-packages/miro/frontends/widgets/application.py", line 272, in on_skip_forward app.playback_manager.skip_forward() File "/usr/lib64/python2.6/site-packages/miro/frontends/widgets/playback.py", line 463, in skip_forward self.player.skip_forward() File "/usr/lib64/python2.6/site-packages/miro/player.py", line 54, in skip_forward pos = min(duration, current + 30.0) TypeError: unsupported operand type(s) for +: 'NoneType' and 'float' Local variables in innermost frame: duration: 2501L current: None self: <miro.frontends.widgets.gtk.video.VideoPlayer object at 0x2ac1c8274990>
Created attachment 405181 [details] File: backtrace
Looking at the trace, almost certainly a dupe of bug #569199. *** This bug has been marked as a duplicate of bug 569199 ***