Bug 1320585 - [abrt] will-crash: will_python3_raise:3:<module>:ZeroDivisionError: division by zero
Summary: [abrt] will-crash: will_python3_raise:3:<module>:ZeroDivisionError: division ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: will-crash
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Marko
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:8ce793be646b5779096d74b8945...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-23 14:41 UTC by Jakub Filak
Modified: 2017-12-12 10:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:54:46 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (494 bytes, text/plain)
2016-03-23 14:41 UTC, Jakub Filak
no flags Details
File: environ (3.30 KB, text/plain)
2016-03-23 14:41 UTC, Jakub Filak
no flags Details

Description Jakub Filak 2016-03-23 14:41:01 UTC
Version-Release number of selected component:
will-crash-0.10-2.fc24

Additional info:
reporter:       libreport-2.6.4.35.gd3db8
cmdline:        python3 /usr/bin/will_python3_raise
executable:     /usr/bin/will_python3_raise
kernel:         4.5.0-0.rc7.git3.2.fc25.x86_64
runlevel:       N 5
type:           Python3
uid:            18601

Truncated backtrace:
will_python3_raise:3:<module>:ZeroDivisionError: division by zero

Traceback (most recent call last):
  File "/usr/bin/will_python3_raise", line 3, in <module>
    0/0
ZeroDivisionError: division by zero

Local variables in innermost frame:
__doc__: None
__builtins__: <module 'builtins' (built-in)>
__cached__: None
__package__: None
__name__: '__main__'
__loader__: <_frozen_importlib_external.SourceFileLoader object at 0x7ff5057e8438>
__spec__: None
__file__: '/usr/bin/will_python3_raise'

Potential duplicate: bug 1062345

Comment 1 Jakub Filak 2016-03-23 14:41:05 UTC
Created attachment 1139619 [details]
File: backtrace

Comment 2 Jakub Filak 2016-03-23 14:41:06 UTC
Created attachment 1139620 [details]
File: environ

Comment 3 Jan Kurik 2016-07-26 05:00:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 5 Fedora End Of Life 2017-11-16 15:37:01 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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 25 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 6 Fedora End Of Life 2017-12-12 10:54:46 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.