|
Bugzilla – Full Text Bug Listing |
| Summary: | yast livelocks on writing menu.lst in chroot environment | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Matthias Hopf <mhopf> |
| Component: | YaST2 | Assignee: | Olaf Dabrunz <odabrunz> |
| Status: | RESOLVED WONTFIX | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Major | ||
| Priority: | P4 - Low | CC: | suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2logs | ||
|
Description
Matthias Hopf
2006-05-15 15:28:19 UTC
I'm not sure whether this is support. Please attach /var/log/YaST2 as tarball. Does it freeze or is there any error message? Why shouldn't this be supported? It's an almost trivial action (just writing a config file), and it is the easiest way to include the currently booted system in the boot loader of another partition, that is not yet included in the menu.lst of the currently used menu.lst. AFAIR this worked perfectly with all versions up to 10.0. This is a full freeze (livelock). No messages. Created attachment 83463 [details]
y2logs
OK this initially took place whule writing the menu.lst. Ruediger, please have a look. Sorry, should've gone to Olaf. closing this bug wontfix. If it can still be reproduced with openSUSE 10.3, feel free to reopen. |