Bug 756906

Summary:	Cannot create temporary file in /tmp/ - multiple programs
Product:	[Fedora] Fedora	Reporter:	rjcup3 <cuthbertson.richard>
Component:	distribution	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WORKSFORME	QA Contact:	Bill Nottingham <notting>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dennis, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-05 20:00:09 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 rjcup3 2011-11-25 03:48:07 UTC

Description of problem:
Cannot create temporary files in /tmp/ directory. Is not due to permissions (1777) nor due to tmp dir full. Could not compile c++ code with gcc in Anjuta due to this error, so I downloaded Code::Blocks, same error. Went to firefox to download code::blocks manual, could not download pdf because it couldn't write to /tmp/ ie same error.

Code::Blocks error:

-------------- Build: Debug in MP6b ---------------

Linking console executable: bin/Debug/MP6b
Cannot create temporary file in /tmp/: Invalid argument
g++: internal compiler error: Aborted (program collect2)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Process terminated with status 4 (0 minutes, 0 seconds)
0 errors, 0 warnings
 
How reproducible:
By trying to write anything to tmp/


Steps to Reproduce:
1. cd to tmp
2. touch tempfile
  
Actual results:
touch: setting times of 'temp': no such file or directory

Expected results:
I expected it to make the damned file lol.

Additional info:
"For your information, the Supreme Court has roundly rejected prior restraint." - Walter Sobchak

Comment 1 rjcup3 2011-11-26 04:21:37 UTC

Solved it. There are 3 options now in GRUB instead of 2...:
1) Fedora 3.1.1-2...
2) Fedora with Linux, with Linux 3.1.1-1...
3) Fedora with Linux, with Linux 3.1.1-1... (Recovery)

No bug in number 2, but default if I don't catch the bootloader is 1. What is 1 and why is it there now? I didn't create that intentionally. Is it because I used preupgrade from f15-f16? How do I get rid of it if it is unnecessary?

Comment 2 Bill Nottingham 2011-11-28 21:29:47 UTC

The kernel version should be irrelevant.

Can you attach the output of 'strace /tmp/boo' in the situation where it doesn't work for you?

Comment 3 Bill Nottingham 2012-01-05 20:00:09 UTC

Closing, please reopen if you have the requested data.