Bug 1729682

Summary: dc calculator always exits with exit code 1
Product: [Fedora] Fedora Reporter: Nathaniel Carroll <qazxcvbnm.nat>
Component: bcAssignee: Gerd Pokorra <gp>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 29CC: frantisek.kluknavsky, gp, kasal, ken, ovasik, qazxcvbnm.nat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 23:30:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
bug fix from upstream none

Description Nathaniel Carroll 2019-07-13 13:29:48 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Build Identifier: 

dc calculator will always exit with code 1, both when used interactively and with an input file. 

Reproducible: Always

Steps to Reproduce:
echo "q" > testfile #quit command in dc
dc testfile
echo "$?"
Actual Results:  
The second echo displays 1, indicating that was the exit code of dc.

Expected Results:  
The expected outcome is exit code 0 (success).

version: dc (GNU bc 1.07.1) 1.4.1

bc does not seem to suffer from the same problem.

Comment 1 Nathaniel Carroll 2019-10-03 14:28:14 UTC
Having a more detailed look at this bug, this seems to only happen when the script is exited by the "q" command, exiting via running off the end of the program has the expected exit code of 0.

This bug seems to have been introduced in dc 1.4.1 (bc 1.07.1). The expected exit code of 0 happens with dc 1.4 (bc 1.07).

Comment 2 ken 2019-10-03 17:06:57 UTC
Created attachment 1622367 [details]
bug fix from upstream

This patch is sitting in upstream's source repository; some day dc-1.4.2 will be released with this fix, but in the meantime one can apply this locally.

Comment 3 Ben Cotton 2019-10-31 18:47:37 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 4 Ben Cotton 2019-11-27 23:30:37 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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

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