[Bug 596071] New: Milestone 5
http://bugzilla.novell.com/show_bug.cgi?id=596071 http://bugzilla.novell.com/show_bug.cgi?id=596071#c0 Summary: Milestone 5 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: 64bit OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: fbernasek@netscape.net QAContact: jsrain@novell.com Found By: --- Blocker: --- Created an attachment (id=354014) --> (http://bugzilla.novell.com/attachment.cgi?id=354014) Detailed Hardware Info from my System User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-2.1 Firefox/3.6 Installation openSUSE 11.3 Milestone 5 64 Bit not possible. Now before Hardware: ASUS M4N82 Deluxe Motherboard, 2x GeForce GTS 250 3x 1 TB Harddisk Drives , Illuminated Keyboard Logitech USB 1x Logitech USB Mouse 1x external USB 300 GB Harddisk 1x SAMSUNG SyncMaster 2433 Monitor 1x HP v220 Monitor Now the Problem: i have the last two Years installed every openSUSE Version and Release on this Hardware without any Problems. Last night i have download the new openSUSE 11.3 Milestone 5 64 Bit Version i have burned on three differend DVD 's and start the the installation with the default BIOS Settings with every DVD crashed the Yast2 with a SEGMENTATION FAULT after the checking and adding the repositories, i have this procedure done maybe 5 or 6 times , result allways the same error Reproducible: Always Steps to Reproduce: 1.DVD in 2.Start System 3.following the Steps was displayed Actual Results: SEGMENTAION FAULT on Yast2 and crashed -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c
Franz Bernasek
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c1
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c2
Uwe Buckesfeld
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c3
--- Comment #3 from Eric Jones
From a 64bit openSUSE 11.2 host (2.6.31.12-0.2-desktop) with Intel Q9650, running VirtualBox 3.1.6 r59338, the install segfaults during repository initialization. (GUI;CURSES,AutoYAST, all same results)
First part of /var/log/YaST2/signal: YaST got signal 11 at YCP file Packages.ycp:1428 Liberating suppressed debugging messages: [liby2] SymbolEntry.cc(setValue):107 SymbolEntry::setValue (progress_value@0x14378c0 = '0') [libycp] ExecutionEnvironment.cc(pushframe):105 Push frame StackSize () [libycp] ExecutionEnvironment.cc(popframe):115 Pop frame 0x1b297a0 [libycp] ExecutionEnvironment.cc(pushframe):105 Push frame TopState () [libycp] ExecutionEnvironment.cc(popframe):115 Pop frame 0x1b1bc40 [liby2] SymbolEntry.cc(setValue):107 SymbolEntry::setValue (prev_state@0x1438400 = '$["current_stage":9, "current_step":9, "last_subprogress_max":0, "progress_label":"Initializing package manager...", "progress_max":10,
From /usr/share/YaST2/modules/Packages.ycp:1428 global void Initialize_StageInitial (...) .. initial_source = Pkg::SourceCreateBase (base_url, "");
First part of callchain traceback: Backtrace: (use c++filt to demangle) /usr/lib64/liby2.so.2(_Z20signal_log_backtracev+0x1e)[0x7f0c9555d64e] /usr/lib64/liby2.so.2(_Z14signal_handleri+0x157)[0x7f0c9555d857] /lib64/libc.so.6(+0x32a20)[0x7f0c9365ea20] /usr/lib64/libzypp.so.631(_ZN4zypp4repo8susetags10Downloader12consumeIndexERKN5boost13intrusive_ptrINS_6parser8susetags9RepoIndexEEE+0xa3)[0x7f0c8f8d7f3] /usr/lib64/libzypp.so.631(_ZN4zypp6parser8susetags17ContentFileReader8endParseEv+0x45)[0xf70c8f6b2805] -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c4
Leonardo Chiquitto
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c5
Di Pe
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c
Michael Calmer
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c6
Michael Andres
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c7
Mark Davidson
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c8
Sanjay Kumar J
http://bugzilla.novell.com/show_bug.cgi?id=596071
http://bugzilla.novell.com/show_bug.cgi?id=596071#c9
--- Comment #9 from Michael Andres
Are you sure this is a duplicate?
Yes.
But as shown above in comment 3, the function names are from boost 1.3x ( ..consumeIndexERKN5boost13.. ) so I don't think this build happened after factory was contaminated with the new boost code.
No. Just do 'nm /usr/lib64/libzypp.so| grep boost | less' (nm is from package binutils). You'll see that the numbers int those cryptic strings is not related to any version. There are also boot6 and boost9 and others, so the above is a '13' and not an abbreviated 1.3. These are just the low-level names the compiler assigns to the symbols in the library. Calling 'nm -C /usr/lib64/libzypp.so' will demangle and show them in a human readable form (well, at least for humans that talk C++). (In reply to comment #8)
When is re-release expected if there is any.
Sorry, but I don't know. A preliminary fix was already submitted (libzypp-7.0), so I hope a working 64bit version is available soon. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com