Bug 721680

Summary: Installation Cannot Be Completed Due To Missing File
Product: [openSUSE] openSUSE 12.1 Reporter: Forgotten User xs3PtXj4XH <forgotten_xs3PtXj4XH>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P1 - Urgent CC: forgotten_cAXlJ_FoSf, forgotten_Wx0iJJoWsY, forgotten_xI2C5NvggO, rh
Version: Beta 1   
Target Milestone: ---   
Hardware: PC   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Hardware Information
Xorg Log
YaST Logs

Description Forgotten User xs3PtXj4XH 2011-10-02 21:50:45 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:6.0.2) Gecko/20100101 Firefox/6.0.2

Near the end of phase 1 of installation, during the running of the "finishing scripts", installation fails to complete, dropping out of graphical install to text-only console with the message:

error: Can't create transaction lock on /var/lib/rpm/.rpm.lock (no such file or directory)

Reproducible: Always

Steps to Reproduce:
1. Start installation, and de-select automatic configuration.
2. Choose to use the entire hard drive (propose separate Home partition was not selected)
3. Choose to use a different administrator password from the chosen user password
4. Enable boot from MBR and disable boot from root partition
5. Begin installation.
Actual Results:  
RPMs finish installing and the "finishing scripts" begin to run.  The last message shown on the screen prior to dropping to console is "rebuilding Kernel module dependencies".

Attempting to boot from hard drive on next boot takes the user to a login screen, but no login actually works.

Expected Results:  
Finishing scripts should have completed and the system rebooted.
Comment 1 Forgotten User xs3PtXj4XH 2011-10-02 21:51:32 UTC
I've labelled this bug urgent since it prevents testing of the Beta!
Comment 2 ray herman 2011-10-04 04:59:13 UTC
This looks like a duplicate of #721676
https://bugzilla.novell.com/show_bug.cgi?id=721676
Comment 3 Forgotten User cAXlJ_FoSf 2011-10-04 12:47:37 UTC
This looks like bug #721815, can you please check Xorg logs whether X segfaults
during installation?
Comment 4 Forgotten User xI2C5NvggO 2011-10-04 14:43:59 UTC
I am also seeing this (exact same symptoms, Intel P4 @ 2.48GHz, 512M RAM, Inno 3DX 440 (Nvidia ?) graphics.

I see via Control-Alt-F8 that X sever has seg-faulted. Do you want the log (I can try to extract it)
Comment 5 Forgotten User cAXlJ_FoSf 2011-10-04 15:12:04 UTC
I'd like to know from the original reporter if Xorg evdev segfaults which would be a dupe of bug #720571 (not bug #721815 as I wrote above, sorry for the confusion).
Comment 6 Forgotten User xs3PtXj4XH 2011-10-04 18:04:05 UTC
How can I find this out Guido?  How can I access the Xorg logs if the install won't complete?  Incidentally, my graphics card is a Radeon 5670.  I'm going to test the install with default boot settings to check if it is a dupe of https://bugzilla.novell.com/show_bug.cgi?id=721815 as well.
Comment 7 Forgotten User cAXlJ_FoSf 2011-10-04 18:52:20 UTC
(In reply to comment #6)
> How can I find this out Guido?  How can I access the Xorg logs if the install
> won't complete?  Incidentally, my graphics card is a Radeon 5670.  I'm going to

When this happens you can switch to a different console and check whether /var/log/Xorg.0.log contains the same segfault in the evdev driver as in https://bugzillafiles.novell.org/attachment.cgi?id=454290.

> test the install with default boot settings to check if it is a dupe of
> https://bugzilla.novell.com/show_bug.cgi?id=721815 as well.

Bug #721815 is likely just another dupe of this.
Comment 8 Forgotten User xs3PtXj4XH 2011-10-04 19:00:02 UTC
I'm sorry Guido, but how can I switch to a different console? After failure, the drop to console doesn't give me any login option...
Comment 9 Forgotten User xI2C5NvggO 2011-10-04 19:26:23 UTC
Does Control-Alt-<F{1-12} not switch consoles? It does for me in what looks like an identical crash.

Control-Alt-F8 should give you the X.org log
Control-Alt-F2 should give you a prompt

With teh latter, you should be able to ssh to another machine on the local network and / or copy files (such as the X.org log) using scp. Of course the second machine has to have sshd running (use "rcsshd start" at root). And it's simplest to use IP addresses rather than hoping for name resolution.

You can also use save_y2_logs if required and transfer that if they need it.

PS  - what is your hardware?

Cheers
Richard
Comment 10 Forgotten User xs3PtXj4XH 2011-10-05 10:16:48 UTC
I've managed to get the log files onto the local disk. I'll post them shortly, but it looks like it is indeed a X11 segfault.
Comment 11 Forgotten User xs3PtXj4XH 2011-10-05 16:34:14 UTC
Created attachment 454704 [details]
Hardware Information

OK, here it is, the requested information.  First attachement - hardware information.
Comment 12 Forgotten User xs3PtXj4XH 2011-10-05 16:35:11 UTC
Created attachment 454705 [details]
Xorg Log

Xorg Logs as requested.
Comment 13 Forgotten User xs3PtXj4XH 2011-10-05 16:37:09 UTC
Created attachment 454706 [details]
YaST Logs

YaST logs as requested.
Comment 14 Forgotten User cAXlJ_FoSf 2011-10-05 17:16:53 UTC
Thank you, this is bug #720571.

*** This bug has been marked as a duplicate of bug 720571 ***
Comment 15 Forgotten User Wx0iJJoWsY 2011-10-05 17:59:25 UTC
This bug is marked as resolved. 
I couldn't read the "solution" 
Can some one privide one hint?
THX
Comment 16 Forgotten User cAXlJ_FoSf 2011-10-05 18:07:38 UTC
(In reply to comment #15)
> This bug is marked as resolved. 
> I couldn't read the "solution" 
> Can some one privide one hint?

It has been identified and marked as a duplicate of bug 720571 where this issue will be tracked further.