The following was filed automatically by anaconda:
anaconda 16.12 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/yum/sqlutils.py", line 166, in executeSQLQmark
File "/usr/lib/python2.7/site-packages/yum/history.py", line 1097, in old
executeSQL(cur, sql, params)
File "/usr/lib/python2.7/site-packages/yum/history.py", line 1148, in last
ret = self.old(, 1, complete_transactions_only)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1477, in runTransaction
lastdbv = self.history.last()
File "/tmp/updates/pyanaconda/yuminstall.py", line 1034, in _run
File "/tmp/updates/pyanaconda/yuminstall.py", line 1017, in run
if self._run(instLog, cb, intf) == DISPATCH_BACK:
File "/tmp/updates/pyanaconda/yuminstall.py", line 1628, in doInstall
rc = self.ayum.run(self.instLog, cb, anaconda.intf)
File "/tmp/updates/pyanaconda/backend.py", line 205, in doInstall
File "/tmp/updates/pyanaconda/dispatch.py", line 338, in dispatch
self.dir = self.steps[self.step].target(self.anaconda)
File "/tmp/updates/pyanaconda/dispatch.py", line 235, in go_forward
File "/tmp/updates/pyanaconda/gui.py", line 1198, in nextClicked
File "/tmp/updates/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
File "/tmp/updates/pyanaconda/gui.py", line 1218, in handleRenderCallback
OperationalError: database is locked
Created attachment 513855 [details]
Attached traceback automatically from anaconda.
While testing anaconda-16.12-1  (with updates=http://jlaska.fedorapeople.org/updates/f16-alpha.img), during a @minimal package install, I encounter the failure listed in comment#0.
To reproduce this issue ....
1. Attempt a @default graphical installation ... the install must fail due to file conflicts
2. At the file conflict dialog, select Back
3. At the repo setup screen, change the install group to [X] Minimal
4. Proceed with installation
This error only happens when going back to the reposetup screen after some packaging failure.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.