Bugzilla – Bug 158804
Installation fails on scr: relocation error: /lib/tls/libdl.so.2...
Last modified: 2006-04-18 06:37:28 UTC
Installation from CD1 (SUSE-10.0-CD-OSS-i386-GM-CD1) fails on multiple occurences of "Changing environment to target system was not successful" Console screen 1 shows: "scr: relocation error: /lib/tls/libdl.so.2: symbol _dl_catch_error, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference." CPU is AMD Athlon XP 2500, target IDE disk is Western Digital, partition size=14.65 GB.
Please, attach YaST logs. See: http://en.opensuse.org/Bug_Reporting_FAQ#YaST Thanks
Created attachment 73734 [details] TAR of files in /var/log/YaST2/ TAR ball created immediately after 'hang' in step 'Install Boot Manager' (creating initrd).
Created attachment 73737 [details] TAR of files in /var/log/YaST2/ after trying Expert Tools->Install New Boot Loader While trying to overcome problem while installing Suse 10.0, tried Expert Tools->Install New Boot Loader. Got "Error - changing environment to target system was not successful", "sh:/sbin/mkinitrd: no such file or directory". Is this related to or a side-effect of problem reported earlier?
Created attachment 73741 [details] TAR of files in /var/log/YaST2/ - in similar failure with Suse 9.3 Pro FYI: similar failure encountered while trying installation with Suse 9.3 Pro i386. Failed in "Install Boot Manager" (creating initrd) step.
jsrain: Installing bootloader hang because of no working SCR. switch_scr_finish.ycp maybe doesn't work well. btw: 10.0
This does not look like a YaST problem, but more like base system one.
In which version exactly did you encounter this problem? Correct the version and maby the product field for this bug.
(In reply to comment #7) > In which version exactly did you encounter this problem? Correct the version > and maby the product field for this bug. > Problem happened while trying to install Suse 10.0 as a upgrade to partition that had Suse 9.1. Similar problem also found with Suse 9.3, also trying to upgrade to same partition. Worked around the problem by complete installation on another partition. Installed OK.
OK then this is an update-issue. At which point exactly does the installation fail (what screen can you see last, ...)?
(In reply to comment #9) > OK then this is an update-issue. At which point exactly does the installation > fail (what screen can you see last, ...)? > 2 places: while checking Package Database during attempted installation repair and Install a New Boot Loader.
This is update problem of the package, not general Update problem. Please, assign to the package maintainer.
which package?
Dave: Do you know the affected packages here?
(In reply to comment #14) > Dave: Do you know the affected packages here? > Sorry, my notes from that day did not go into that detail. Is the info not in any of the TAR'ed logs I submitted? I do recall that the problem happened during the Boot Loader Installation step also. I'd since worked-around the problem and installed Suse 9.3 on another partition instead of trying to upgrade an existing partition. I can't go back and reproduce the problem. Sorry...
Stanislav, can you check the logs to point out what went wrong, please?
Which package contains this file? What is the output of rpm -qf /lib/tls/libdl.so.2 ?
Looks like we are stuck with this problem. Please, reopen if you can find out which package contains this file.