Bug 396978 - Installing openSUSE 11.0 (x86) in VMware- unexpected finish
Summary: Installing openSUSE 11.0 (x86) in VMware- unexpected finish
Status: RESOLVED DUPLICATE of bug 381755
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stefan Hundhammer
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-04 07:59 UTC by Shyukri Shyukriev
Modified: 2008-06-13 14:27 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
installation theme screens and a gtk error report (47.07 KB, application/zip)
2008-06-04 08:04 UTC, Shyukri Shyukriev 		Details
Yast2 logs (1.09 MB, application/x-gzip)
2008-06-13 06:52 UTC, Shyukri Shyukriev 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shyukri Shyukriev 2008-06-04 07:59:17 UTC 
I configured my VM with SCSI hard drive and started the installation.
At the Configuration section the theme colors have changed and some of the buttons don't even have icons. The installation finished without asking anything else and i was able to log in.
After a restart i got message that previous install was not successful.
Comment 1 Shyukri Shyukriev 2008-06-04 08:04:43 UTC 
Created attachment 220004 [details]
installation theme screens and a gtk error report
Comment 2 Lukas Ocilka 2008-06-10 12:27:09 UTC 
Attach YaST logs, please.

http://en.opensuse.org/Bugs/YaST
Comment 3 Lukas Ocilka 2008-06-11 08:05:20 UTC 
Shyukri, could you, please, attach YaST logs?
Comment 4 Shyukri Shyukriev 2008-06-13 06:52:39 UTC 
Created attachment 221947 [details]
Yast2 logs
Comment 5 Lukas Ocilka 2008-06-13 13:57:01 UTC 
genericfrontend.cc(signal_handler):149 got signal 11 at YCP file Wizard.ycp:593

Wizard.ycp:593
    any input = UI::UserInput();

It might have happened that something has closed the UI before and that's why UI::UserInput failed but it's not obvious for me. Maybe UI maintainer could help?
Comment 6 Stefan Hundhammer 2008-06-13 14:27:11 UTC 

*** This bug has been marked as a duplicate of bug 381755 ***