Bugzilla – Bug 217015
yast2 inst_source segfaults
Last modified: 2006-11-01 16:53:58 UTC
When trying to add http://download.suse.com/install/10.2/inst-source-extra/ as installation source, yast segfaults: brutus:~ # yast2 inst_source Segmentation fault at /usr/share/YaST2/clients/inst_source.ycp:114 /sbin/yast2: line 267: 28658 Segmentation fault (core dumped) $ybindir/y2base $module "$@" "$SELECTED_GUI" "$Y2_GEOMETRY" $Y2QT_ARGS This happens both in Qt and ncurser and it happens also during installation, which is the anoying part :-(
Created attachment 103334 [details] y2logs from a running system
Created attachment 103335 [details] y2logs from installation
I have this problem as well. The bug doesn't have anything to do with which source you want to add. It already appears after calling "yast2 inst_source".
(In reply to comment #3) > I have this problem as well. The bug doesn't have anything to do with which > source you want to add. It already appears after calling "yast2 inst_source". Then it could be some other problem. For me, it happens only when adding the above mentioned source and even that succeedes some times... maybe some nondeterministic network problem yast can't cope with...?
(In reply to comment #4) Your original description shows that this happens right after the call. If it is indeed a separate problem: sorry for changing the subject (it seemed obvious). About network: My system was installed from DVD and this was the first call to inst_source. To check if there is more than one problem, here is the complete output after my call: unterwegs:~ # yast2 inst_source Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. Segmentation fault at /usr/share/YaST2/clients/inst_source.ycp:542 /sbin/yast2: line 267: 5262 Speicherzugriffsfehler $ybindir/y2base $module "$@" "$SELECTED_GUI" "$Y2_GEOMETRY" $Y2QT_ARGS
seems to be know bug 214886 *** This bug has been marked as a duplicate of bug 214886 ***
Kevin, I don't know. Read bug 214886 and decide whether your problem is the same or not. If not, create another bug.