abrt 1.0.0 detected a crash. backtrace ----- Summary: TB2eeafa98 tempfile.py:318:mkdtemp:OSError: [Errno 13] Permission denied: '/var/tmp/yum-alex-llWUUE' Traceback (most recent call last): File "/usr/bin/yum", line 29, in <module> yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 315, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 159, in main base.getOptionsConfig(args) File "/usr/share/yum-cli/cli.py", line 204, in getOptionsConfig (opts, self.cmds) = self.optparser.setupYumConfig(args=args) File "/usr/share/yum-cli/cli.py", line 1174, in setupYumConfig elif not self.base.setCacheDir(): File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 4148, in setCacheDir cachedir = misc.getCacheDir(tmpdir, reuse) File "/usr/lib/python2.6/site-packages/yum/misc.py", line 561, in getCacheDir cachedir = tempfile.mkdtemp(prefix=prefix, dir=tmpdir) File "/usr/lib64/python2.6/tempfile.py", line 318, in mkdtemp _os.mkdir(file, 0700) OSError: [Errno 13] Permission denied: '/var/tmp/yum-alex-llWUUE' Local variables in innermost frame: e: [Errno 13] Permission denied: '/var/tmp/yum-alex-llWUUE' name: llWUUE seq: 0 prefix: yum-alex- names: <tempfile._RandomNameSequence instance at 0x2baab48> file: /var/tmp/yum-alex-llWUUE dir: /var/tmp suffix: cmdline: /usr/bin/python /usr/bin/yum search bluez-gnome-analyzer component: yum executable: /usr/bin/yum kernel: 2.6.31.6-145.fc12.x86_64 package: yum-3.2.25-1.fc12 uuid: 2eeafa98
Created attachment 375652 [details] File: backtrace
what are ownerships on /var/tmp b/c it looks like users cannot create dirs there.
drwxr-xr-x root root /var/tmp --- As far as I know this directory was created this way, I never changed the permissions and I am the sole user of this machine [laptop].
that directory should have the tmp bit set. drwxrwxrwt 4 root root 4096 2009-12-02 22:21 /var/tmp run: rpm -V filesystem it should print a change on /var/tmp
Yes, you're right. I'm not sure how this happened, but I repaired the issue. Perhaps something odd happened during the upgrade? Regardless, thanks for your help.
while this is not a bug b/c of what changed I added a patch to make sure we don't traceback and we do the appropriate thing if this happens to someone else in the future.
(In reply to comment #6) > while this is not a bug b/c of what changed I added a patch to make sure we > don't traceback and we do the appropriate thing if this happens to someone else > in the future. Thank you, such simple things are much appreciated, and make troubleshooting easier (especially since this traceback looks a bit scary if you're not used to python).