Version-Release number of selected component: yum-3.4.3-106.fc19 Additional info: reporter: libreport-2.1.6 cmdline: /usr/bin/python /usr/bin/yum --enablerepo=* clean all executable: /usr/bin/yum kernel: 3.10.9-200.fc19.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: cli.py:482:waitForLock:YumBaseError: No se puede crear archivo de bloqueo, ya existe uno 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 316, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 123, in main base.waitForLock() File "/usr/share/yum-cli/cli.py", line 482, in waitForLock raise yum.Errors.YumBaseError, _("Can't create lock file; exiting") YumBaseError: No se puede crear archivo de bloqueo, ya existe uno Local variables in innermost frame: lockerr: u'No se ha podido crear el bloqueo en /var/tmp/yum-w4r3d-1m0jgj/x86_64/19/yum.pid: [Errno 28] No queda espacio en el dispositivo' self: <cli.YumBaseCli object at 0x2233ed0> e: LockError()
Created attachment 790554 [details] File: backtrace
Created attachment 790555 [details] File: environ
There was a bug in commit 8c214b3b that moved the waitForLock() function, it does not handle failures as it should. This includes wait_for_lock=True case, too. Fixed upstream.
*** Bug 1019381 has been marked as a duplicate of this bug. ***