https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c2 --- Comment #2 from Felix Miata 2013-08-01 09:28:38 UTC --- Comment 1 should have been written for 12.2, but 12.3 has the same problem. zypper[3492]: segfault at 0 ip b76b2631 sp bff7de10 error 4 in libzypp.so.1200.13.3[b733c000+471000] kernel-default-3.7.10-1.16.1.i586 libzypp-12.13.3-1.11.1.i586 zypper-1.8.16-1.10.1.i586 zypper-log-1.8.16-1.10.1.noarch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c3 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #3 from Michael Andres 2013-08-01 18:38:42 CEST --- Is zypper the only tool no longer working? Could you attach the systems zypper.log (12.2, 12.3, 13.1). May they contain a hint. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c5 --- Comment #5 from Felix Miata 2013-08-02 02:51:27 UTC --- Created an attachment (id=550802) --> (http://bugzilla.novell.com/attachment.cgi?id=550802) manually collected installation logs: /var/log/YaST2/ and /var/log/zypp/ I'm still not entirely convinced this is 100% a hardware problem. I ran memtest 4.10 192 minutes with 0 errors on the repaired power supply. Then I did a HTTP factory-snapshot E17 installation. Everything went apparently well until the last package was installed, then the installation GUI spontaneously exited and the ncurses failure message appeared. I then rebooted to 12.3 and mounted the aborted 13.1 /. No logs were written to /root/inst-sys. No X log was written anywhere I've found. Last week I found a bad cap on another motherboard. I replaced 10 of the 13 it had of that brand and type, which was all I had in stock. This motherboard has more than a dozen of that same brand and type, and most likely same vintage. None are obviously bad, but I'm going to buy more and then replace these before doing any more follow-up on this bug, unless someone from the zypp team has suggestions for other things to do first. All that said, I do have one idea. This has never happened to me in all the years of using openSUSE and SuSE before it, but I wonder if something related to https://bugzilla.redhat.com/show_bug.cgi?id=680508 is happening here. I also had the same trouble with Mandriva and likely Mandrake before it, but its bug DB is no longer available. Such trouble appeared only on certain combinations of hardware and software, and was far far short of ubiquitous. Virtually all my / partitions, as here, are smallish, usually 4.8G, and use a 1024 blocksize to minimize sector overhang waste. Has there been a compiler change for building zypper, libzypp and/or rpm in recent weeks? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mrmazda@earthlink.net |ma@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c8 --- Comment #8 from Felix Miata 2013-08-02 19:00:00 UTC --- Created an attachment (id=551027) --> (http://bugzilla.novell.com/attachment.cgi?id=551027) zypper.log from fresh customized minimal X 12.3 HTTP installation to host kt880 I run openSUSE only on hardware solver.onlyRequires = true on all my openSUSE installations download.use_deltarpm = false on most of my openSUSE installations (In reply to comment #7)

Maybe you can check whether a fresh 12.3 fails after updating to the latest libzypp/ibsolv-tools-0.3.0. If so, please attach the zypper log, so we can check whether it's again the dataiterator.

From second boot (to 'runlevel 3') following uneventful installation of 12.3:

# bash_history tail #1375466729 zypper clean -a #1375466799 zypper al zypper libzypp rpm #1375466809 zypper al kernel-desktop #1375466815 zypper ref #1375467415 zypper -v in mc-4.8.9 #1375467516 zypper -v in seamonkey-irc seamonkey-dom-inspector #1375467550 zypper -v in seamonkey-irc-2.17 seamonkey-dom-inspector-2.17 #1375467977 zypper -v in MozillaFirefox-21.0 #1375468261 zypper al MozillaFirefox seamonkey-irc seamonkey-dom-inspector #1375468268 zypper up # dmesg tail portion [ 1601.745021] zypper[2000]: segfault at 70596b4 ip b4ccd00b sp bf89bf40 error 4 # from rpm querying glibc-2.17-4.4.1.i586 kernel-default-3.7.10-1.1.1.i586 libsolv-tools-0.2.4-2.1.1.i586 libudev1-195-13.11.1.i586 libzypp-12.9.0-1.1.1.i586 python-satsolver-0.45.0-4.1.1.i586 udev-195-13.11.1.i586 zypper-1.8.11-1.1.1.i586 zypper-log-1.8.11-1.1.1.noarch A subsequent 'zypper -v in -f prctl' succeeded. Let me know if you want the new zypper.log tail, 229929 more bytes. Motherboard caps are on order, due in 3-7 days. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

From original 12.3: cpuinfo: model name : AMD Athlon(tm) XP 2400+ flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c10 --- Comment #10 from Felix Miata 2013-08-08 04:07:36 UTC --- After replacing 18 1000uf 6.3v caps on the motherboard, and 3.2 hours doing 3 full memtest86+ 4.10 passes with no errors, zypper se -s still segfaults in both 13.1m3 (desktop kernel) and the original 12.3 installation (default kernel), but not in the newer 12.3 (default kernel). pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow last dmesg line: zypper[1154]: segfault at f6349840 ip b63583f2 sp bff68350 error 7 cmdline: root=LABEL=wd80suse123 ipv6.disable=1 noresume splash=verbose vga=794 video=1152x864@60 3 noapic nolapic (normally neither noapic nor nolapic, but I was testing to see if they helped) uname -a: Linux kt880.ij.net 3.7.10-1.16-default #1 SMP Fri May 31 20:21:23 UTC 2013 (97c14ba) i686 athlon i386 GNU/Linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c12 --- Comment #12 from Felix Miata 2013-08-10 08:34:50 UTC --- Created an attachment (id=552095) --> (http://bugzilla.novell.com/attachment.cgi?id=552095) /var/log/zypp/history following fresh 13.1M4 installation Previous comment forgot to mention the installation failed to complete while I wasn't looking. It booted successfully after the abort, but I could not login until after copying passwd/shadow files from another installation and rebooting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c14 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mls@suse.com --- Comment #14 from Michael Andres 2013-08-27 13:06:15 CEST --- (Sorry for the late response, I've been on vacation) @mls: Any idea? The crash in zypp::sat::LookupAttr::iterator::increment is the location we had to touch after the libsolv dataiterator fixes (added the ::dataiterator_strdup call). void LookupAttr::iterator::increment() { if ( _dip ) { if ( ! ::dataiterator_step( _dip.get() ) ) { _dip.reset(); base_reference() = 0; } else { ::dataiterator_strdup( _dip.get() ); } } } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c16 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mls@suse.com |mrmazda@earthlink.net --- Comment #16 from Michael Andres 2013-09-02 11:51:46 CEST --- This problem still seems to be unique to your machine. We debugged into libsolv using the information provided so far, but this did not reveal anything. We'd need a core file to get more information. Maybe you can install on your 12.3 libzypp and zypper from the zypp:Code12_3-Branch repo as the packages there are not stripped. (http://download.opensuse.org/repositories/zypp:/Code12_3-Branch/openSUSE_12....). Execute 'ulimit -c unlimited' to enable core file creation. If zypper crashes, attach the core file and the zypper.log. (please keep/backup /usr/bin/zypper and /usr/lib/libzypp.so.1200.15.0 in case we need additional info) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c18 --- Comment #18 from Michael Andres 2013-09-03 11:18:32 CEST --- Found it in my mailbox, thanks. (you can use 'split' to divide the file into smaller pieces...) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c20 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #20 from Michael Andres 2013-09-03 18:40:36 CEST --- All crashes so far seem to happen, when applying the hardlocks. I'd like to know if this is just a coincidence or if other query or non query actions fail as well. Could you please - on the 12.3 system - move away the /etc/zypp/locks file (containing your locked packages); if it still crashes also move away the /var/lib/zypp/SoftLocks file. If it still crashes, please attach the zypper.log. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c22 --- Comment #22 from Michael Andres 2013-09-04 16:39:35 CEST --- That's strange. There's nothing in the lock file that could explain the crash. And also after an excessive debugging session we're not sure what actually happens on your system. We'd recommend to call 'zypper clean -m', so all cached data files are recreated. It would be interesting to know if you can recreate all the packages locks again, and if the same procedure also helps on the 13.1 system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c24 --- Comment #24 from Felix Miata 2013-09-04 16:13:44 UTC --- Created an attachment (id=555794) --> (http://bugzilla.novell.com/attachment.cgi?id=555794) /etc/zypp/zypp.conf from kt880's 13.1m4 12.3: # zypper clean -m # mv /etc/zypp/locks /etc/zypp/locks-new # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper se -s GL # zypper -v up no segfault 13.1: # zypper clean -m # mv /etc/zypp/locks /etc/zypp/locks-new # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper se -s GL segfault # cp -a /etc/zypp/locks-new /etc/zypp/locks # zypper se -s GL no segfault # zypper clean -a # zypper ref # zypper ll # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper ll # zypper se -s GL segfault Any more suggestions? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c26 --- Comment #26 from Felix Miata 2013-09-04 17:04:32 UTC --- 13.1: # zypper clean -m # cp -a /etc/zypp/locks-new /etc/zypp/locks # zypper se -s GL no segfault # zypper al kernel-default # zypper al kernel-desktop # zypper se -s GL segfault # zypper ll # | Name | Type | Repository --+----------------+---------+----------- 1 | MozillaFirefox | package | (any) 2 | seamonkey | package | (any) 3 | kernel-default | package | (any) 4 | kernel-desktop | package | (any) # uname -a Linux kt880 3.11.0-rc7-1.g99e1318-default #1 SMP Tue Aug 27 13:32:27 UTC 2013 (99e1318) i686 athlon i386 GNU/Linux # cat /proc/cmdline root=/dev/disk/by-label/wd80suse131 ipv6.disable=1 apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 (reboot) #cat /proc/cmdline root=LABEL=wd80suse131 ipv6.disable=1 noresume splash=verbose vga=794 video=1152x864@70 3 noapic nolapic # zypper clean -m # cp -a /etc/zypp/locks-new /etc/zypp/locks # zypper se -s GL # zypper al kdm # zypper se -s GL # zypper al kernel-default # zypper se -s GL segfault # zypper rl kernel-default # zypper se -s GL # zypper al kernel-desktop # zypper se -s GL segfault # zypper rl kdm # zypper se -s GL no segfault Looks like it can handle 3 locks or less without segfaulting, but no more. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c28 --- Comment #28 from Felix Miata 2013-09-05 15:31:21 UTC --- # zypper ll # 3 items # zypper ref # zypper -v in valgrind # zypper al kernel-default # valgrind zypper se -s GL .. in use at exit: 6,618,521 bytes in 253,096 blocks total heap usage: 435,978 allocs, 182,882 frees, 942,946,588 bytes allocated .. definitely lost: 6,480 bytes in 39 blocks indirectly lost: 0 possibly lost: 645,389 bytes in 21,986 blocks suppressed: 0 Rerun with --leak-check=full to see details of leaked memory For counts of detected and suppressed errors, rerun with: -v ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) no segfault # mv /etc/zypp/locks /etc/zypp/locks-4 # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper ll # 40 items # valgrind zypper se -s GL (valgrind output) similar to with 4 locks as above, aka no segfault # zypper se -s GL segfault -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c30 --- Comment #30 from Felix Miata 2013-09-05 18:56:12 UTC --- 12.3: # zypper ll (41 locks) # zypper ref # zypper se -s GL # zypper lu # zypper se -s kern | grep def | grep -v src returned nothing # zypper se -s kern segfault # zypper se -s GL segfault # zypper clean -m # zypper se -s GL segfault # cp -a /etc/zypp/locks-OK /etc/zypp/locks # 2 locks # zypper se -s GL No segfault, so build it for 12.3 if you please. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c32 --- Comment #32 from Felix Miata 2013-09-06 18:20:41 UTC --- Created an attachment (id=556260) --> (http://bugzilla.novell.com/attachment.cgi?id=556260) zypper se -s GL segfault core using comment 31 attachment, part 1 of split bz2 (In reply to comment #31)

Simply unpack and install it in /usr/lib:

Would "simply" have done it? Permissions as unpacked were 664 or 644, 755 as I installed it, to match perms of the original file. Core size: 55388K What clears "ulimit -c unlimited" when done? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

What clears "ulimit -c unlimited" when done?

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c34 --- Comment #34 from Michael Andres 2013-09-09 18:52:14 CEST --- ulimit -c 0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c37 --- Comment #37 from Michael Andres 2013-09-18 13:13:32 CEST --- We were afraid this would happen. The libzypp you installed from the zypp:Code12_3-Branch repo and the two libzypp versions I attached were all compiled from the same code; just compiler optimization is different. This could hint to a misscompilation. The core files we saw could also hint to a misscompilation. But then the crashes should not be limited to your system. It would be great it you could stay with the libzypp from comment 35 for a while, 'hoping' it will crash an produce a core which reveals a bug. --- The lib has BuildID[sha1]=0xc29dca57f0993572283073455f20964658e7dc0e. You can easily check whether zypper actually uses the right one: $ ldd /usr/bin/zypper | grep libzypp libzypp.so.1200 => /usr/lib/libzypp.so.1200 VVVVVVVVVVVVVVVVVVVVVVVV $ file --dereference /usr/lib/libzypp.so.1200 .....BuildID[sha1]=0xc29dca57f0993572283073455f20964658e7dc0e -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Alberto Planas Dominguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c40 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #40 from Michael Andres 2013-12-04 08:58:23 CET --- Thanks for the feedback. I'm going to close this report for now. Please reopen, if the problem shows up again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c42 --- Comment #42 from Felix Miata 2013-12-14 02:05:00 UTC --- FWIW, on same I host I HTTP installed 13.2 from Factory repos last night. Zypper seems perfectly happy running with well in excess of 40 locks set and kernel-default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c44 --- Comment #44 from Felix Miata 2014-04-25 03:58:06 EDT --- using 32 bit 12.3 running kernel-default-3.7.10-1.16 with libzypp-12.16.4-1.33.1 zypper-1.8.24-1.26.1 zypper -v up with more than 3 locks set segfaulted after refreshing but before beginning to list packages it wants an answer y to (while "reading installed packages"?), but works as expected with only 3 locks set. using 32 bit 13.1 running kernel-default-3.11.10-7 with libzypp-13.9.0-13.1 zypper-1.9.12-16.1 zypper -v up with a 3433 byte locks file (41 entries, including kernel* as #40, with firefox-esr as #41) worked as expected. Just afterward, zypper rl kernel*; zypper -v up segfaulted after "Reading installed packages..." appeared on screen. Removing the locks file, then zypper al seamonkey; zypper se -s kernel-default; zypper ll; zypper -v up succeeded to upgrade kernel-firmware. using 32 bit Factory running kernel-default-3.14.rc7 with libzypp-14.17.5-1.1 zypper-1.11.4-1.1 zypper -v dup with a 3726 byte locks file (45 locks, including kernel* as #45), followed by zypper rl kernel*; zypper -v dup all worked as expected. 8 days ago on same machine, urpmi --auto-select on Cauldron and yum upgrade on Rawhide again worked fine too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c46 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #46 from Michael Matz 2014-04-28 12:27:20 UTC --- Does valgrind say anything now (and does the segfault still happen with it)? If that doesn't reveal anything: run zypper under gdb (install libzypp-debuginfo and -debugsource, as well as zypper-debuginfo/debugsource): % gdb --args /usr/bin/zypper <your arguments> ... (gdb) r ... wait until it crashes ... (gdb) backtrace Show us the output of that backtrace. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c48 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|mrmazda@earthlink.net | --- Comment #48 from Felix Miata 2014-04-28 18:33:06 EDT --- Created an attachment (id=588015) --> (http://bugzilla.novell.com/attachment.cgi?id=588015) copy & paste from Konsole gdb attempt Is this attachment from 13.1 host kt880 useful? valgrind --leak-check=yes zypper se -s n-page failed to produce a segfault. Process tail: ==3509== LEAK SUMMARY: ==3509== definitely lost: 0 bytes in 0 blocks ==3509== indirectly lost: 0 bytes in 0 blocks ==3509== possibly lost: 1,044,588 bytes in 33,654 blocks ==3509== still reachable: 10,250,326 bytes in 394,738 blocks ==3509== suppressed: 0 bytes in 0 blocks ==3509== Reachable blocks (those to which a pointer was found) are not shown. ==3509== To see them, rerun with: --leak-check=full --show-reachable=yes ==3509== ==3509== For counts of detected and suppressed errors, rerun with: -v ==3509== ERROR SUMMARY: 52 errors from 52 contexts (suppressed: 0 from 0) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c50 --- Comment #50 from Felix Miata 2014-07-03 00:18:27 EDT --- Factory (1.11.8-1.1/14.24.0-1.2) seems to be OK with lots of locks currently, but not 13.1 (1.9.16-22.2/13.10.2-19.6). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c52 --- Comment #52 from Michael Andres 2014-09-08 09:32:31 CEST --- Thanks for the update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.