|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST crash during install | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Richard Brown <rbrown> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | jreidinger |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
it is already known bug with dependency resolver. Marking as dup as original have better logs. *** This bug has been marked as a duplicate of bug 941398 *** |
YaST crashed on me during a remote install of the current tumbleweed snapshot Steps to reproduce (EXACT steps taken to cause this bug..possible many of these steps might not be relevant) Installing Tumbleweed over SSH, with SSH=1 and SSHPassword=Geeko123 Using X over SSH, running yast.ssh Selected Minimal Installation (Textmode) on the Desktop selection screen Went to Software Selection on the Installation Overview Screen Clicked on Dependencies and unticked 'Install Recommended Packages' Searched for and added mdadm Searched for an added salt Depdenency popup for minimal_base_conflicts appeared at this point, selected the option to remove the conflicts pattern CRASH >mounts/mp_0001/usr/share/YaST2/include/hwinfo/routines.rb:43: warning: duplicated key at line 592 ignored: "cache" >/mounts/mp_0001/usr/share/YaST2/include/hwinfo/routines.rb:343: warning: duplicated key at line 652 ignored: "vendor_id" >YaST got signal 11 at file /mounts/mp_0001/usr/share/YaST2/modules/PackagesUI.rb:303 >/usr/lib/YaST2/startup/YaST2.call: line 281: 3690 Segmentation fault $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS System failed, shut down, no opportunity to get y2logs and as the system is remote, I'm now rather unhappy with an unbootable system that's stuck on the linuxrc screen I guess..