Results 1 to 4 of 4

Thread: yast in 10.3 x86_64

  1. #1
    elsigiz NNTP User

    Default yast in 10.3 x86_64

    I've got strangely corrupted yast, making it absolutely useless in software management section.
    Almost any task (update configuration, yast -i, online update) ends up with this:

    *** glibc detected *** /usr/lib/YaST2/bin/y2base: free(): invalid pointer: 0x00002afe4038d192 ***
    ======= Backtrace: =========
    /lib64/libc.so.6[0x2afe3d93821d]
    /lib64/libc.so.6(cfree+0x76)[0x2afe3d939f76]
    /usr/lib64/libcurl.so.4[0x2afe4036dacf]
    /usr/lib64/libcurl.so.4[0x2afe40370fad]
    /usr/lib64/libcurl.so.4[0x2afe4037147e]
    /usr/lib64/libcurl.so.4[0x2afe403729ce]
    /usr/lib64/libcurl.so.4[0x2afe4037534f]
    /usr/lib64/libcurl.so.4[0x2afe40382206]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media9MediaCurl13doGetFileCopyERKNS_10filesystem8PathnameES5_RNS_8callback10SendReportINS0_22DownloadProgressReportEEE+0xfc2)[0x2afe3ee52402]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media9MediaCurl11getFileCopyERKNS_10filesystem8PathnameES5_+0x175)[0x2afe3ee48e55]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media9MediaCurl7getFileERKNS_10filesystem8PathnameE+0xf3)[0x2afe3ee46e23]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media12MediaHandler11provideFileENS_10filesystem8PathnameE+0x173)[0x2afe3ee25703]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media11MediaAccess11provideFileERKNS_10filesystem8PathnameEbb+0x76)[0x2afe3ee1d916]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media12MediaManager11provideFileEjRKNS_10filesystem8PathnameEbb+0x66)[0x2afe3ee64906]
    /usr/lib64/libzypp.so.324(_ZN4zypp14MediaSetAccess19provideFileInternalERKNS_10filesystem8PathnameEjbb+0x19c)[0x2afe3f0571cc]
    /usr/lib64/libzypp.so.324(_ZN4zypp14MediaSetAccess11provideFileERKNS_10filesystem8PathnameEj+0xf)[0x2afe3f05832f]
    /usr/lib64/libzypp.so.324(_ZN4zypp14MediaSetAccess11provideFileERKNS_15OnMediaLocationE+0x12)[0x2afe3f058352]
    /usr/lib64/libzypp.so.324(_ZN4zypp7Fetcher4Impl5startERKNS_10filesystem8PathnameERNS_14MediaSetAccessERKN5boost8functionIFbRKNS_12ProgressDataEESaIvEEE+0x5e6)[0x2afe3f05d2a6]
    /usr/lib64/libzypp.so.324(_ZN4zypp4repo3yum10Downloader8downloadERNS_14MediaSetAccessERKNS_10filesystem8PathnameERKN5boost8functionIFbRKNS_12ProgressDataEESaIvEEE+0xe2b)[0x2afe3eebc2ab]
    /usr/lib64/libzypp.so.324(_ZN4zypp11RepoManager15refreshMetadataERKNS_8RepoInfoENS0_24RawMetadataRefreshPolicyERKN5boost8functionIFbRKNS_12ProgressDataEESaIvEEE+0x3e6)[0x2afe3f06d436]
    /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN18PkgModuleFunctions20RefreshWithCallbacksERKN4zypp8RepoInfoE+0x94)[0x2afe45206d34]
    /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN18PkgModuleFunctions19createManagedSourceERKN4zypp3UrlERKNS0_10filesystem8PathnameEbRKSsS9_+0x7d1)[0x2afe45208c51]
    /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN18PkgModuleFunctions14SourceCreateExERK9YCPStringS2_bS2_+0x46f)[0x2afe4520b75f]
    /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN18PkgModuleFunctions12SourceCreateERK9YCPStringS2_+0x7d)[0x2afe4520c22d]
    /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN13Y2PkgFunction12evaluateCallEv+0xd2fd)[0x2afe451c78bd]
    /usr/lib64/libycp.so.3(_ZN10YEFunction8evaluateEb+0x35b)[0x2afe3aeffe3b]
    /usr/lib64/libycp.so.3(_ZN8YSAssign8evaluateEb+0x77)[0x2afe3af105b7]
    /usr/lib64/libycp.so.3(_ZN6YBlock8evaluateEb+0x1ca)[0x2afe3af2a4aa]
    /usr/lib64/libycp.so.3(_ZNK10YCPCodeRep8evaluateEb+0xe9)[0x2afe3aeef9b9]
    /usr/lib64/libycp.so.3[0x2afe3af61831]
    /usr/lib64/libycp.so.3(_ZN9YEBuiltin8evaluateEb+0xa44)[0x2afe3af00e84]
    /usr/lib64/libycp.so.3(_ZN12YSExpression8evaluateEb+0x21)[0x2afe3af102d1]
    /usr/lib64/libycp.so.3(_ZN6YBlock8evaluateEb+0x1ca)[0x2afe3af2a4aa]
    /usr/lib64/libycp.so.3(_ZN13Y2YCPFunction12evaluateCallEv+0x2f2)[0x2afe3af07162]
    /usr/lib64/libycp.so.3(_ZN10YEFunction8evaluateEb+0x35b)[0x2afe3aeffe3b]
    /usr/lib64/libycp.so.3(_ZN8YSReturn8evaluateEb+0x64)[0x2afe3af106e4]
    /usr/lib64/libycp.so.3(_ZN6YBlock8evaluateEb+0x1ca)[0x2afe3af2a4aa]
    /usr/lib64/libycp.so.3(_ZN13Y2YCPFunction12evaluateCallEv+0x2f2)[0x2afe3af07162]
    /usr/lib64/libycp.so.3(_ZN10YEFunction8evaluateEb+0x35b)[0x2afe3aeffe3b]
    /usr/lib64/libycp.so.3(_ZN8YSAssign8evaluateEb+0x77)[0x2afe3af105b7]
    /usr/lib64/libycp.so.3(_ZN6YBlock8evaluateEb+0x1ca)[0x2afe3af2a4aa]
    /usr/lib64/libycp.so.3(_ZN7YSBlock8evaluateEb+0x11)[0x2afe3af101c1]
    /usr/lib64/libycp.so.3(_ZN4YSIf8evaluateEb+0x1ee)[0x2afe3af10e8e]
    /usr/lib64/libycp.so.3(_ZN6YBlock8evaluateEb+0x1ca)[0x2afe3af2a4aa]

    I have manually upgraded yast, zypper, glibc to the latest, rebuilt zypper cache and rpm db.
    Still, it changed nothing, i constantly get this error.

    Any ideas?

    wbr,
    /sigiz

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,729
    Blog Entries
    20

    Default Re: yast in 10.3 x86_64

    Try this as su

    LC_ALL=C zypper ve

    it should verify your system


    what does this give:
    zypper lu
    also try:

    zypper in -f yast2-core yast2-perl-bindings libzypp zypper
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3
    elsigiz NNTP User

    Default ***SOLVED***

    Looks like there's no verify in 10.3's zypper.

    # LC_ALL=C zypper ve
    Unknown command 've'
    Try -h for help.

    Also, lu fails too, with a familiar error:

    # LC_ALL=C zypper lu
    Refreshing 'openSUSE-10.3-FTP 10.3'
    *** glibc detected *** zypper: free(): invalid pointer: 0x00002b0da6625192 ***
    ======= Backtrace: =========
    /lib64/libc.so.6[0x2b0da4f1b21d]
    /lib64/libc.so.6(cfree+0x76)[0x2b0da4f1cf76]
    /usr/lib64/libcurl.so.4[0x2b0da6605acf]
    /usr/lib64/libcurl.so.4[0x2b0da6608fad]
    /usr/lib64/libcurl.so.4[0x2b0da660947e]
    /usr/lib64/libcurl.so.4[0x2b0da660a9ce]
    /usr/lib64/libcurl.so.4[0x2b0da660d34f]
    /usr/lib64/libcurl.so.4[0x2b0da661a206]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media9MediaCurl13doGetFileCopyERKNS_10filesystem8PathnameES5_RNS_8callback10SendReportINS0_22DownloadProgressReportEEE+0xfc2)[0x2b0da3d2b402]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media9MediaCurl11getFileCopyERKNS_10filesystem8PathnameES5_+0x175)[0x2b0da3d21e55]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media9MediaCurl7getFileERKNS_10filesystem8PathnameE+0xf3)[0x2b0da3d1fe23]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media12MediaHandler11provideFileENS_10filesystem8PathnameE+0x173)[0x2b0da3cfe703]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media11MediaAccess11provideFileERKNS_10filesystem8PathnameEbb+0x76)[0x2b0da3cf6916]
    /usr/lib64/libzypp.so.324(_ZNK4zypp5media12MediaManager11provideFileEjRKNS_10filesystem8PathnameEbb+0x66)[0x2b0da3d3d906]
    006b0000-007bb000 rw-p 006b0000 00:00 0 [heap]
    [...skipped...]
    Aborted

    which led me to upgrade libcurl.

    Looks like it was a libcurl bug.
    After updating it yast and zypper recovered too.

    Thanks.

  4. #4
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,729
    Blog Entries
    20

    Default Re: ***SOLVED***

    Yes. Sorry about that, I forgot it 10.3 as I was typing zypper commands.

    Usually a -f (force) update will do the trick.

    Well done.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •