Bugzilla – Bug 357757
Boot loader segmentation fault
Last modified: 2008-04-17 13:50:58 UTC
Cannot open Boot Loader module. Got the following xmessage: YaST got signal 11 at YCP file Progress.ycp:106 /sbin/yast2: line 439: 14198 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS If I'm not mistaken this bug was previsouly reported, but fixed meanwhile. So far it only affects this YaST module. Running Factory (31 Jan)
Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks!
Created attachment 192814 [details] YaST logs
Created attachment 202542 [details] My latest log
Both qt & ncurses versions of:- all in hardware section, bootloader and partitioner, in fact anything relating to hardware in yast doesn't work. I'm using latest factory at date of posting. Various segmentation faults and sometimes the program quietly dies.
It seems to be problem of qt.
Then why does the command "yast bootloader" crash with this output :- YaST got signal 11 at YCP file Arch.ycp:44 /sbin/yast: line 420: 394 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS I cannot use any yast hardware setup functions.
(In reply to comment #5 from Jozef Uhliarik) > It seems to be problem of qt. This is too simple for an explanation. Sorry, but I don't debug each and any segfault everywhere without any reasonable explanation why it would be a problem of the UI. Many segfaults are caused by inconsistent library versions. Other possible reasons may be memory corruption anywhere. It can't be the job of the UI maintainer to debug all this everywhere, in particular not if only one YaST2 module of over 100 is affected.
P.S. With the same reasoning somebody could say it's a compiler bug or a kernel bug.
I updated yast2-core yast2-hardware-detection glibc libstdc++ hwinfo and all the gcc dependencies and I'm happy to say my entire yast2 suite is working well, except for software version tab display but thats a different bug. I don't know what went right so I'll leave marking fixed to someone else.
It's duplicated of bug# 360646 *** This bug has been marked as a duplicate of bug 360646 ***