Bug 981466 - starting terminal show error : "Permission denied bash: $TMP: ambiguous redirect"
Summary: starting terminal show error : "Permission denied bash: $TMP: ambiguous redir...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Oprala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-04 20:03 UTC by Curtis Adkins
Modified: 2015-02-18 13:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 13:58:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Curtis Adkins 2013-07-04 20:03:03 UTC
Description of problem:
Starting terminal shows this error :

"mktemp: failed to create file via template ‘/tmp/.colorlsXXX’: Permission denied
bash: $TMP: ambiguous redirect"

Seems to be a repeat of bug 948008

Version-Release number of selected component (if applicable):
19

How reproducible:
start terminal

Steps to Reproduce:
1.start terminal
2.no need to su to root.  Error happens as soon as termianl is started
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ondrej Vasik 2013-07-09 06:56:14 UTC
Quite strange - it probably means you have /tmp/ with permissions that doesn't allow write for everyone or full. Could you please check this? It would be good to know what's the reason for permission denied on your system.

Either way - it is not really repeat of the bug #948008, as this is much less likely scenario - but the script still seems to be still quite fragile. We may probably check if the mktemp works and skip the "support for INCLUDE" feature if not.

Comment 2 Curtis Adkins 2013-07-09 19:37:45 UTC
I have not been able to reproduce this error since the last update.

I would be more than glad to test anything needed though.

Comment 3 Ondrej Vasik 2013-07-10 10:44:08 UTC
We will need some changes in include support handling anyway(because of https://bugzilla.redhat.com/show_bug.cgi?id=981373) , as $TMP variable is too generic and sometimes breaks other things. That being said, we may probably handle the access rights to $TMPDIR as well.

Comment 4 Fedora End Of Life 2015-01-09 22:10:44 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 5 Fedora End Of Life 2015-02-18 13:58:09 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.