|
Bugzilla – Full Text Bug Listing |
| Summary: | Bootloader error in Yast2 and subsequent segfault | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User NX4nrDp_bN <forgotten_NX4nrDp_bN> |
| Component: | Bootloader | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | forgotten_NX4nrDp_bN, jreidinger |
| Version: | 13.2 | Flags: | jsrain:
needinfo?
(forgotten_NX4nrDp_bN) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Text shown in error popup Yast2
Output journalctl -e after fresh reboot and attempt to configure bootloader in Yast2 tarball /var/log/YaST2 |
||
Could you, please, attach full logs as the pop-up says? http://en.opensuse.org/Bugs/YaST Created attachment 613200 [details]
Output journalctl -e after fresh reboot and attempt to configure bootloader in Yast2
This is the only log I know to produce currently (I am not proficient with this new journalctl means, sorry).
Please, instruct me what to do if you need more or other logs (the pop up is not very specific about what logs exist and how to obtain them)
See the link I sent you in my last comment; in short, we need a tarball of /var/log/YaST2 directory. Created attachment 613324 [details]
tarball /var/log/YaST2
Sorry Jiri, I did notice the link but did not interprete its presence being a hint how to obtain de logs. Anyway, I herewith upload the tarball you requested. I will read the pages behind the link later.
May be good to know the following, which might be related to the reported problem and might offer you another clue.
- My system showing the problem is a multiboot configuration with SUSE 13.1 (fall back), SUSE 13.2 aside WIN8.1. As I experienced problems with the booting mechanism when using Grub2 as primary bootloader in SUSE 13.1 previously, at the time I had to use the WIN8.1 bootloader. So I did this time too. I configured to not use MBR as location, but another option, which is the system root partition.
- On installing the 13.2 system the first time I used de BTRFS filesystem as proposed by Yast. It failed to install the bootloader properly, however.
Next I re-installed the whole system but then requesting to use the EXT4 file system. Then it seemingly worked, until I tried to edit the bootloader config in Yast.
- I do have another pure single boot SuSE 13.2 machine running with standard offered BTRFS and using the root partition as boot location as well. Here I do NOT encounter the problem when open the bootloader configuration in Yast
I hope this all helps you. If I can provide you with more information, I will be happy to help you.
Best regards, Thijs
this bug is already reported and arvin working on fix. *** This bug has been marked as a duplicate of bug 902385 *** |
Created attachment 613188 [details] Text shown in error popup Yast2 Attempt to open bootloader in Yast2 results in Error pop-up (see attachment for screencapture) announcing internal error and requesting a bug report. Yast2 ends in segault stating: yast2 bootloader YaST got signal 11 at file /usr/share/YaST2/modules/Popup.rb:1058 /sbin/yast2: line 440: 2155 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Journalctl only shows log until end of succesfull system startup. Don't know what more logs to look for.