Description of problem: When typing a non existing command in the shell and the name starts with a dot the message "bash: .name: command not found" is missing because the command is starting with a dot. Version-Release number of selected component (if applicable): The problem has been introduced in this commit: https://github.com/hughsie/PackageKit/commit/0e85001b How reproducible: Try to execute a non existing command that starts with a dot. Steps to Reproduce: 1. In bash/zsh Type: $ .anything Actual results: <nothing> Expected results: bash: .anything: command not found Additional info: The problem popped up on Stackoverflow: http://stackoverflow.com/questions/34309107/bash-does-not-print-any-error-msg-upon-non-existing-commands-starting-with-dot/34309633#34309633 The problem was introduced as a response to a previous bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1151185
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
This bug still exists. Reopening.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.
Still exists.
still there in what fedora release? 25 , 26, both?
Confirmed fixed in current F27 with updates. (Upstream: https://github.com/hughsie/PackageKit/commit/d3533878038ebdcf6ae2b3524c8c8e2f1b47e84b)
(In reply to Rex Dieter from comment #6) > still there in what fedora release? 25 , 26, both? It’s still present in 25 and 26, but was fixed in 27 with PackageKit 1.1.8 (the actual commit is https://github.com/hughsie/PackageKit/commit/d3533878038ebdcf6ae2b3524c8c8e2f1b47e84b — thanks to mattdm for spotting it).