[SLE] yast online update aborting - SuSE 10.1
Folks, I have a strange problem after the last set up YOU updates. When I launt yast2 and clock on YOU, it immediately aborts. I cannot tell if the last update messed up or one of the updated packages was bad. Below is a dump after the abort: *** glibc detected *** /usr/lib/YaST2/bin/y2base: double free or corruption (out): 0x08527170 *** ======= Backtrace: ========= /lib/libc.so.6[0xb761a911] /lib/libc.so.6(__libc_free+0x84)[0xb761bf84] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb77b8e51] /usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1d)[0xb7794fed] /usr/lib/libstdc++.so.6(_ZNSsD1Ev+0x57)[0xb7797b77] /usr/lib/libzypp.so.0(_ZNSt10_List_baseIN4zypp9PublicKeyESaIS1_EE8_M_clearEv+0x36)[0xb70048f6] /usr/lib/libzypp.so.0(_ZN4zypp6target3rpm5RpmDb28importZyppKeyRingTrustedKeysEv+0x413)[0xb71885d3] /usr/lib/libzypp.so.0(_ZN4zypp6target3rpm5RpmDb12initDatabaseENS_10filesystem8PathnameES4_+0x9d8)[0xb7189918] /usr/lib/libzypp.so.0(_ZN4zypp6target10TargetImplC1ERKNS_10filesystem8PathnameE+0xb5)[0xb71564d5] /usr/lib/libzypp.so.0(_ZN4zypp6TargetC1ERKNS_10filesystem8PathnameE+0x4d)[0xb6fd7dad] /usr/lib/libzypp.so.0(_ZN4zypp11zypp_detail8ZYppImpl10initTargetERKNS_10filesystem8PathnameEb+0x1b8)[0xb7254ca8] /usr/lib/libzypp.so.0(_ZN4zypp4ZYpp10initTargetERKNS_10filesystem8PathnameEb+0x2f)[0xb6ff605f] /usr/lib/YaST2/plugin/libpy2Pkg.so.2(_ZN18PkgModuleFunctions10TargetInitERK9YCPStringRK10YCPBoolean+0x86)[0xb5e71ae6] /usr/lib/YaST2/plugin/libpy2Pkg.so.2(_ZN13Y2PkgFunction12evaluateCallEv+0xfc7)[0xb5e44cf7] /usr/lib/libycp.so.2(_ZN10YEFunction8evaluateEb+0x38e)[0xb7d429fe] /usr/lib/libycp.so.2(_ZN12YSExpression8evaluateEb+0x37)[0xb7d621f7] /usr/lib/libycp.so.2(_ZN6YBlock8evaluateEb+0x199)[0xb7d7c1b9] /usr/lib/libycp.so.2(_ZNK10YCPCodeRep8evaluateEb+0x114)[0xb7d337d4] /usr/lib/YaST2/plugin/libpy2wfm.so.2(_ZN14Y2WFMComponent12doActualWorkERK7YCPListP11Y2Component+0x613)[0xb7f1ba03] /usr/lib/liby2.so.2(main+0x1f1b)[0xb7cd6d5b] /lib/libc.so.6(__libc_start_main+0xdc)[0xb75cc87c] /usr/lib/YaST2/bin/y2base(main+0x5d)[0x8048501] ======= Memory map: ======== 08048000-08049000 r-xp 00000000 08:1d 124282 /usr/lib/YaST2/bin/y2base 08049000-0804a000 rw-p 00000000 08:1d 124282 /usr/lib/YaST2/bin/y2base 0804a000-08544000 rw-p 0804a000 00:00 0 [heap] b4300000-b433b000 rw-p b4300000 00:00 0 b433b000-b4400000 ---p b433b000 00:00 0 b4492000-b44c8000 r-xp 00000000 08:1d 124289 /usr/lib/YaST2/plugin/libpy2ag_ini.so.2.0.0 b44c8000-b44c9000 rw-p 00035000 08:1d 124289 /usr/lib/YaST2/plugin/libpy2ag_ini.so.2.0.0 b44c9000-b44f3000 r--p 00000000 08:1d 43773 /usr/X11R6/lib/X11/fonts/truetype/albwb.ttf b44f3000-b451e000 r-xp 00000000 08:1d 45498 /usr/lib/liblcms.so.1.0.15 b451e000-b4520000 rw-p 0002a000 08:1d 45498 /usr/lib/liblcms.so.1.0.15 b4520000-b4522000 rw-p b4520000 00:00 0 b4522000-b458f000 r-xp 00000000 08:1d 49132 /usr/lib/libmng.so.1.1.0.9 b458f000-b4592000 rw-p 0006c000 08:1d 49132 /usr/lib/libmng.so.1.1.0.9 b4593000-b45bd000 r--p 00000000 08:1d 43751 /usr/X11R6/lib/X11/fonts/truetype/albw.ttf b45bd000-b45db000 r-xp 00000000 08:1d 40093 /usr/lib/libjpeg.so.62.0.0 b45db000-b45dc000 rw-p 0001d000 08:1d 40093 /usr/lib/libjpeg.so.62.0.0 b4602000-b4606000 r-xp 00000000 08:1d 149432 /usr/lib/qt3/plugins/imageformats/libqmng.so b4606000-b4607000 rw-p 00003000 08:1d 149432 /usr/lib/qt3/plugins/imageformats/libqmng.so b4607000-b4631000 r-xp 00000000 08:1d 150430 /opt/kde3/lib/libkdefx.so.4.2.0 b4631000-b4633000 rw-p 00029000 08:1d 150430 /opt/kde3/lib/libkdefx.so.4.2.0 b4657000-b4658000 r--p 00000000 08:1d 25924 /usr/share/YaST2/locale/en_US/LC_MESSAGES/packages-qt.mo b4658000-b465d000 r-xp 00000000 08:1d 138204 /usr/lib/qt3/plugins/imageformats/libqjpeg.so b465d000-b465e000 rw-p 00005000 08:1d 138204 /usr/lib/qt3/plugins/imageformats/libqjpeg.so b465e000-b467d000 r-xp 00000000 08:1d 150410 /opt/kde3/lib/kde3/plugins/styles/plastik.so b467d000-b467e000 rw-p 0001e000 08:1d 150410 /opt/kde3/lib/kde3/plugins/styles/plastik.so b467e000-b467f000 ---p b467e000 00:00 0 b467f000-b4e7f000 rwxp b467f000 00:00 0 b4e7f000-b4e80000 r-xp 00000000 08:1d 124033 /usr/X11R6/lib/X11/locale/lib/common/xlcUTF8Load.so.2 b4e80000-b4e81000 rw-p 00000000 08:1d 124033 /usr/X11R6/lib/X11/locale/lib/common/xlcUTF8Load.so.2 b4e81000-b4e8c000 r--s 00001000 08:1d 338940 /var/cache/fontconfig/723d6c7d32b373f6b06cc7f9d1a8e946.cache-2 b4e8c000-b4e90000 r--s 00001000 08:1d 338941 /var/cache/fontconfig/de3900050b586a5b68cdc42e4d82842b.cache-2 b4e90000-b4f0a000 r--s 00001000 08:1d 338942 /var/cache/fontconfig/0b603ee0e9d5cb4fa2facb46225be8ca.cache-2 b4f0a000-b4f11000 r--s 00001000 08:1d 338943 /var/cache/fontconfig/29b9ff740f4303123e973fcf283b3937.cache-2 b4f11000-b4f6a000 r--s 00001000 08:1d 338945 /var/cache/fontconfig/0357813fd01911d26e40012cc37afd61.cache-2 b4f6a000-b4f77000 r--s 00001000 08:1d 338946 /var/cache/fontconfig/57fddf4aeff95a0b98650bf3f13c26fe.cache-2 b4f77000-b5042000 r--s 00001000 08:1d 338948 /var/cache/fontconfig/4ab329b95251bfa96df993af29394e5c.cache-2 b5042000-b5049000 r--s 00001000 08:1d 338951 /var/cache/fontconfig/dc6d8a077de3cb6b0544495765342202.cache-2 b5049000-b50a2000 r--s 00001000 08:1d 338953 /var/cache/fontconfig/a8eccb1d36c0cd55e07565774f02858e.cache-2 b50a2000-b50a3000 r--s 00001000 08:1d 338955 /var/cache/fontconfig/47969f914275157783f61e1bd1ed3d89.cache-2 b50a3000-b50a4000 r--s 00001000 08:1d 338958 /var/cache/fontconfig/43b8e6e859be885e1b4c4769cd73a3f9.cache-2 b50a4000-b50aa000 r--s 00001000 08:1d 338961 /var/cache/fontconfig/d0814903482a18ed8717ceb08fcf4410.cache-2 b50aa000-b50b0000 r--s 00001000 08:1d 338961 /var/cache/fontconfig/d0814903482a18ed8717ceb08fcf4410.cache-2 b50b0000-b50b5000 r--s 00001000 08:1d 338960 /var/cache/fontconfig/a5bb9318fc124018aaa8c1184e917bf0.cache-2 b50b5000-b510e000 r--s 00001000 08:1d 338953 /var/cache/fontconfig/a8eccb1d36c0cd55e07565774f02858e.cache-2 b510e000-b5115000 r--s 00001000 08:1d 338951 /var/cache/fontconfig/dc6d8a077de3cb6b0544495765342202.cache-2 b5115000-b51e0000 r--s 00001000 08:1d 338948 /var/cache/fontconfig/4ab329b95251bfa96df993af29394e5c.cache-2 b51e0000-b51ed000 r--s 00001000 08:1d 338946 /var/cache/fontconfig/57fddf4aeff95a0b98650bf3f13c26fe.cache-2 b51ed000-b5246000 r--s 00001000 08:1d 338945 /var/cache/fontconfig/0357813fd01911d26e40012cc37afd61.cache-2 b5246000-b524d000 r--s 00001000 08:1d 338943 /var/cache/fontconfig/29b9ff740f4303123e973fcf283b3937.cache-2 b524d000-b52c7000 r--s 00001000 08:1d 338942 /var/cache/fontconfig/0b603ee0e9d5cb4fa2facb46225be8ca.cache-2 b52c7000-b52d2000 r--s 00001000 08:1d 338940 /var/cache/fontconfig/723d6c7d32b373f6b06cc7f9d1a8e946.cache-2 b52d2000-b52ef000 r-xp 00000000 08:1d 35580 /usr/lib/libexpat.so.1.5.0 b52ef000-b52f1000 rw-p 0001d000 08:1d 35580 /usr/lib/libexpat.so.1.5.0 b52f1000-b52f5000 r-xp/sbin/yast2: line 233: 13278 Aborted $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS Thanks, Vahe
On Tue, Jul 25, 2006 at 09:56:24AM -0700, Vahe Avedissian wrote:
Folks,
I have a strange problem after the last set up YOU updates. When I launt yast2 and clock on YOU, it immediately aborts. I cannot tell if the last update messed up or one of the updated packages was bad. Below is a dump after the abort:
This is pretty bad. What repositories do you have added? Can you please open a bugreport with the backtrace you have below?
*** glibc detected *** /usr/lib/YaST2/bin/y2base: double free or corruption (out): 0x08527170 ***
Ciao, Marcus -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I submitted a bugzilla report and of course bugzilla aborted with error... I'll try to file it later. Vahe ----- Original Message ---- From: Marcus Meissner <meissner@suse.de> To: Vahe Avedissian <vyav@yahoo.com> Cc: suse list <suse-linux-e@suse.com> Sent: Tuesday, July 25, 2006 10:05:58 AM Subject: Re: [SLE] yast online update aborting - SuSE 10.1 On Tue, Jul 25, 2006 at 09:56:24AM -0700, Vahe Avedissian wrote:
Folks,
I have a strange problem after the last set up YOU updates. When I launt yast2 and clock on YOU, it immediately aborts. I cannot tell if the last update messed up or one of the updated packages was bad. Below is a dump after the abort:
This is pretty bad. What repositories do you have added? Can you please open a bugreport with the backtrace you have below?
*** glibc detected *** /usr/lib/YaST2/bin/y2base: double free or corruption (out): 0x08527170 ***
Ciao, Marcus -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi Marcus & co, Does this apply yo 64 bit version of 10.1? http://www.novell.com/linux/security/advisories/2006_pkupd.html I did the online update during initial install and was thrown into a YOU loop. cheers, dg UOFT/DUA Tel: 416.978.7719 -- This communication is intended for addressed recipients only and may contain sensitive or confidential information. If you have received this email in error, please immediately notify the sender, delete this email from all data storage and destroy all hard copies.
-----Original Message----- From: Vahe Avedissian [mailto:vyav@yahoo.com] Sent: Tuesday, July 25, 2006 4:05 PM To: Marcus Meissner Cc: suse list Subject: Re: [SLE] yast online update aborting - SuSE 10.1
I submitted a bugzilla report and of course bugzilla aborted with error...
I'll try to file it later.
Vahe
----- Original Message ---- From: Marcus Meissner <meissner@suse.de> To: Vahe Avedissian <vyav@yahoo.com> Cc: suse list <suse-linux-e@suse.com> Sent: Tuesday, July 25, 2006 10:05:58 AM Subject: Re: [SLE] yast online update aborting - SuSE 10.1
On Tue, Jul 25, 2006 at 09:56:24AM -0700, Vahe Avedissian wrote:
Folks,
I have a strange problem after the last set up YOU updates. When I launt yast2 and clock on YOU, it immediately aborts. I cannot tell if the last update messed up or one of the updated packages was bad. Below is a dump after the abort:
This is pretty bad. What repositories do you have added?
Can you please open a bugreport with the backtrace you have below?
*** glibc detected *** /usr/lib/YaST2/bin/y2base: double free or corruption (out): 0x08527170 ***
Ciao, Marcus
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Fri, Jul 28, 2006 at 11:24:49PM -0400, Darko Gavrilovic wrote:
Hi Marcus & co,
Does this apply yo 64 bit version of 10.1?
http://www.novell.com/linux/security/advisories/2006_pkupd.html
Yes.
I did the online update during initial install and was thrown into a YOU loop.
YOU will be restarted 3 times. This is expected. Then it will stop looping and install the large set of current updates. ciao, Marcus -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi MArcus, I submitted a bugzilla report (#196724). In the meantime any suggestions how to fix this and move forward? Other than manually downloading and installing all yast modules, is there anything else I can do? Thanks, Vahe ----- Original Message ---- From: Marcus Meissner <meissner@suse.de> To: Vahe Avedissian <vyav@yahoo.com> Cc: suse list <suse-linux-e@suse.com> Sent: Tuesday, July 25, 2006 10:05:58 AM Subject: Re: [SLE] yast online update aborting - SuSE 10.1 On Tue, Jul 25, 2006 at 09:56:24AM -0700, Vahe Avedissian wrote:
Folks,
I have a strange problem after the last set up YOU updates. When I launt yast2 and clock on YOU, it immediately aborts. I cannot tell if the last update messed up or one of the updated packages was bad. Below is a dump after the abort:
This is pretty bad. What repositories do you have added? Can you please open a bugreport with the backtrace you have below?
*** glibc detected *** /usr/lib/YaST2/bin/y2base: double free or corruption (out): 0x08527170 ***
Ciao, Marcus -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wed, Aug 02, 2006 at 08:28:39PM -0700, Vahe Avedissian wrote:
Hi MArcus,
I submitted a bugzilla report (#196724). In the meantime any suggestions how to fix this and move forward? Other than manually downloading and installing all yast modules, is there anything else I can do?
There is feedback in the bugreport, requesting more information... Ciao, Marcus
On Tuesday 25 July 2006 11:56, Vahe Avedissian wrote:
Folks,
I have a strange problem after the last set up YOU updates. When I launt yast2 and clock on YOU, it immediately aborts. I cannot tell if the last update messed up or one of the updated packages was bad. Below is a dump after the abort:
< snip the stuff Marcus knows more about than I ever will....>
Thanks,
Vahe
Did you get a kernel update last time and did you reboot? Stan -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (4)
-
Darko Gavrilovic -
Marcus Meissner -
Stan Glasoe -
Vahe Avedissian