https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c5 --- Comment #5 from Felix Miata <mrmazda@earthlink.net> 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.