| Summary: | OperationalError: database is locked | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aaron Sowry <aaron> | ||||||||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, joshua, tflink, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:769f8f7a7047100c5ad5a31c87d0a03484f0672b9df71f3221b479a789bad75c | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-06-04 23:02:43 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Aaron Sowry
2012-04-20 08:42:41 UTC
Created attachment 578919 [details]
File: anaconda-tb-EnXHxU
Had you been running yum or rpm prior to launching the live installer? Created attachment 579057 [details]
anconda traceback and dump
I get the same error during a DVD fresh install of default Graphical desktop, upon [Back] to recover from file conflict of samba-client-3.6.4-... with samba-client4-... . I composed the DVD myself about an hour ago, using updates-testing and fedora-17-branched; anaconda-17.21 was used during compose and on the DVD itself.
During install, I chose to proceed anyway despite incomplete dependencies. The many file conflicts [20 ?] between samba-client-3.6.4-... and samba-client4-... where discovered during installation of some package. I [Back]ed up to the repo selection screen, chose Customize Now, and removed samba (samba3; I could not find samba4 anywhere) from the Printing packages [beneath Servers ?]. Proceeding gave the attached traceback.
Created attachment 579058 [details]
/tmp/anaconda.log
Created attachment 579059 [details]
yum.log
My situation was very similar to John's, except for that I was installing from USB. My initial attempt at installation failed due to the samba dependency conflict - assuming this was an issue in updates-testing, I went back to the repository selection screen and disabled it. Then after proceeding again, I got the traceback. I hit this in F17 final TC4 when I attempted to install on a disk that wasn't big enough for the default graphical install. I went back to the package selection page, changed my selection to 'minimal'. I got the traceback once the install process started again. Closing this because newui is going to change how this works. |