Bugzilla – Bug 136012
some yast modules crashed after last yast update.
Last modified: 2005-12-12 12:14:29 UTC
as mentioned above, after last system update we can see /home/lslarry> sudo /sbin/YaST2 language *** glibc detected *** free(): invalid pointer: 0xbfba8aa4 *** /sbin/YaST2: line 207: 7728 Aborted $ybindir/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" $Y2QT_ARGS /home/lslarry> sudo /sbin/yast language *** glibc detected *** free(): invalid pointer: 0xbfe8fd44 *** /sbin/yast: line 207: 7752 Aborted $ybindir/y2base "$module" "$@" ncurses it happends after last system update ... 2005-11-22 15:19:11 evolution-pilot-2.4.1-7.i586.rpm installed ok 2005-11-28 15:51:50 luma-2.2.1-0.pm.0.i586.rpm installed ok 2005-11-28 15:52:48 nautilus-2.12.1-7.i586.rpm installed ok 2005-11-28 15:53:08 scpm-1.1.2-8.i586.rpm installed ok 2005-11-28 15:53:35 yast2-core-2.13.4-2.i586.rpm installed ok 2005-11-28 15:53:55 yast2-packagemanager-2.13.7-2.i586.rpm installed ok Additional rpm output: Updating etc/sysconfig/onlineupdate... 2005-11-28 15:53:56 yast2-trans-stats-2.11.0-8.noarch.rpm installed ok 2005-11-28 15:54:01 yast2-country-2.13.6-2.i586.rpm installed ok 2005-11-28 15:54:04 yast2-transfer-2.12.0-3.i586.rpm installed ok 2005-11-28 15:54:08 yast2-profile-manager-2.12.1-3.i586.rpm installed ok 2005-11-28 15:54:14 autoyast2-installation-2.13.2-2.noarch.rpm installed ok /var/log/YaST2/y2logRPM lines 1777-1829/1829 after this profile manager module works, language (I think yast2-country) and packagemanager doesn't. strace output for language module available at http://tic-tac.ru/strace.output /home/lslarry> rpm -qa | grep -i yast yast2-bootfloppy-2.12.28-2 yast2-network-2.12.14-2s /var/log/YaST2/ yast2-printer-2.12.4-2емо yast2-uml-2.12.0-2 yast2-dhcp-server-2.12.5-2var/log/YaST2/ yast2-irda-2.12.1-2итаемо yast2-ntp-client-2.12.6-2 yast2-samba-server-2.12.8-2ar/log/YaST2/y2logRPM yast2-tv-2.12.7-2 yast2-country-2.13.6-2 yast2-slp-2.12.0-2 yast2-vm-2.12.3-2 yast2-firstboot-2.12.1-2 yast2-mail-2.12.4-2 yast2-powertweak-2.12.3-2 yast2-security-2.12.2-2 yast2-users-2.12.9-0.1 autoyast2-installation-2.13.2-2 autoyast2-2.12.15-2 yast2-control-center-2.12.4-2 yast2-mouse-2.12.7-3 yast2-online-update-2.12.4-2 yast2-pkg-bindings-2.12.7-2 yast2-qt-2.12.11-2 yast2-storage-lib-2.12.26-2 yast2-backup-2.12.5-2 yast2-firewall-2.12.5-2 yast2-installation-2.12.27-2 yast2-ldap-client-2.12.9-2 yast2-nfs-server-2.12.1-2 yast2-phone-services-2.12.0-2 yast2-runlevel-2.12.4-2 yast2-schema-2.12.2-2 yast2-tftp-server-2.12.2-2 yast2-ncurses-2.12.6-2 yast2-packagemanager-2.13.7-2 yast2-profile-manager-2.12.1-3 yast2-ldap-2.12.2-2 yast2-nis-client-2.12.2-2 yast2-perl-bindings-2.12.8-2 yast2-storage-2.12.26-2 yast2-update-2.12.7-2 yast2-xml-2.12.0-2 yast2-dns-server-2.12.6-2 yast2-inetd-2.12.5-2 yast2-kerberos-client-2.12.5-2 yast2-nfs-client-2.12.3-2 yast2-pam-2.12.3-2 yast2-restore-2.12.5-2 yast2-scanner-2.12.16-2 yast2-core-2.13.4-2 yast2-transfer-2.12.0-3 yast2-sysconfig-2.12.3-2 yast2-packager-2.12.30-2 yast2-sound-2.12.9-2 yast2-x11-2.12.6-3 yast2-http-server-2.12.13-2 yast2-mail-aliases-2.12.4-2 yast2-repair-2.12.9-2 yast2-support-2.12.3-2 yast2-bootloader-2.12.33-0.1 yast2-2.12.26-2 yast2-power-management-2.12.3-2 yast2-tune-2.12.1-2 yast2-bluetooth-2.12.1-2 yast2-instserver-2.12.3-2 yast2-nis-server-2.12.4-2 yast2-samba-client-2.12.4-2 yast2-theme-SuSELinux-2.12.7-2 yast2-trans-stats-2.11.0-8 /home/lslarry> cat /etc/SuSE-release SUSE LINUX 10.0 (i586) OSS VERSION = 10.0 /home/lslarry> uname -a Linux fenchurch 2.6.13-3-default #1 Mon Aug 29 19:48:23 UTC 2005 i686 i686 i386 GNU/Linux additional information is also available if needed.
i'm a little bit confused. Last update for 10.0 is 2.12.21 for the yast2-packagemanager. Are you sure this is 10.0? Which installation source do you have, which directory are you using for online-update?
hmm. dunno what real version is :) I've installed it as opensuse-rc3(or 2?) and regular update after. sorry, I've came to linux from freebsd and I still didn't quiet understand suse versioning. with freebsd I just regular cvsup source tree and rebuild the system to keep it up to date. and system version change with it. something like 5.2-stable, 5.2-stable, 5.3-rc1, 5.3-rc2, 5.3-stable... where is nothing special to change os version, just regular update. so I thought the same with suse, and the difference is only in building system/packages from source (freebsd) or binary patches (suse). please tell me if I'm mistaking. and how I can check the real version? now I'm using the next sources /home/lslarry> installation_sources -s Installation Sources: [x]* SUSE LINUX Version 10.0 (dir:///suse/) [x]* Packman (SuSE LINUX 10.0) (http://packman.iu-bremen.de//suse/10.0/) [x]* SUSE LINUX Version 10.0.42 (http://mirrors.kernel.org/opensuse/distribution/SL-OSS-edge/inst-source/) [x]* SUSE LINUX Version 10.0 (http://mirrors.kernel.org/opensuse/distribution/SL-OSS-stable/inst-source-java/) [x]* SUSE LINUX Version 10.0 (http://mirrors.kernel.org/suse/i386/current/SUSE-Linux10.0-GM-Extra/) [x]* SUSE LINUX Version 10.0 (ftp://mirror.switch.ch/mirror/opensuse/distribution/SL-OSS-stable/inst-source/) [ ]* SUSE LINUX Version 10.0 (cd:///;devices=/dev/hdc) the first is a local copy of 5 suse cd's on my hd /home/lslarry> head -4 /suse/README ------------------------ README on SuSE Linux 10.0 2005/09/04
ok, we handle it different. patches, the packages you recieve via the online update usually have the same version (if possible). When you add another installation source with a newer version, you have to select system update. But afaik this is not supported. Usually you download a ISO file and select update instead of installation. I guess this is the problem here, it's a mix of 2 Versions. You installed some packages from edge and when you do an online update it will search for 10.0 packages. You can try system update, but as i said usually you boot from CD and select update.
I have to agree with Martin: Updates are always critical in a certain manner. Buf before using new packages, an update has to be done, of course. The crash could resolve from a binary incompatability against a linked libray, for example, which would then be natural. Dimitry: Have you actually done an update here (by booting and select update)? Or did you just add new installation sources? Updating a running system is not really supported, sorry. It will probably work if you change all dependent packages, too. But then you could create problems with other packages...
i will close the bug now, for me it's not a bug. If you think it is one, please reopen, thanks.