On vendredi, 15 juillet 2016 16.48:11 h CEST Lindsay Mathieson wrote:

On 15 July 2016 at 16:44, Knurpht - Gertjan Lettink

wrote:

...

Seeing this as well, wait longer.

Yup, I did, took 15min+ got got there. Thanks.

...

Do you have the kernel-source packages installed ?

Yes I do - was fiddling with the nvidia drivers.

Me too, but I'm impatient so I do a gdb attach to the pid of zypper strangely I got this backtrace (sorry don't have yet installed all debuginfo) coredumpctl gdb 14620 PID: 14620 (zypper) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Mon 2016-07-11 16:22:28 CEST (3 days ago) Command Line: zypper -v --no-refresh up --replacefiles Executable: /usr/bin/zypper Control Group: /user.slice/user-1502.slice/session-1.scope Unit: session-1.scope Slice: user-1502.slice Session: 1 Owner UID: 1502 (bruno) Boot ID: a6f7e8b4ec1e4c94ad83586985e41353 Machine ID: 5796a69412fbda1c055a261856a26e81 Hostname: qt-kt.labaroche.ioda.net Coredump: /var/lib/systemd/coredump/core.zypper. 0.a6f7e8b4ec1e4c94ad83586985e41353.14620.1468246948000000.xz Message: Process 14620 (zypper) of user 0 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://bugs.opensuse.org/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/zypper...Reading symbols from /usr/lib/debug/ usr/bin/zypper.debug...done. done. [New LWP 14620] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `zypper -v --no-refresh up --replacefiles'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000000044cb3a in Out::ProgressBar::~ProgressBar (this=0x1cdc6f0, __in_chrg=<optimized out>) at /usr/src/debug/zypper-1.13.2/src/output/Out.h: 835 835 /usr/src/debug/zypper-1.13.2/src/output/Out.h: No such file or directory. Missing separate debuginfos, use: zypper install libacl1- debuginfo-2.2.52-8.6.x86_64 libattr1-debuginfo-2.4.47-7.99.x86_64 libaugeas0- debuginfo-1.5.0-1.2.x86_64 libcurl4-debuginfo-7.49.1-1.1.x86_64 libelf1- debuginfo-0.164-3.67.x86_64 libicu57_1-debuginfo-57.1-1.3.x86_64 libidn11- debuginfo-1.32-1.5.x86_64 liblua5_3-debuginfo-5.3.3-1.1.x86_64 libmodman1- debuginfo-2.0.1-17.5.x86_64 libncurses6-debuginfo-6.0-10.1.x86_64 libnghttp2-14-debuginfo-1.11.1-1.2.x86_64 libpopt0-debuginfo-1.16-28.91.x86_64 libproxy1-debuginfo-0.4.13-2.2.x86_64 libpsl5-debuginfo-0.13.0-1.3.x86_64 libreadline6-debuginfo-6.3-87.2.x86_64 libssh2-1-debuginfo-1.7.0-1.3.x86_64 libudev1-debuginfo-228-9.1.x86_64 libzypp-debuginfo-16.0.1-1.3.x86_64 rpm- debuginfo-4.12.0.1-13.14.x86_64 (gdb) bt #0 0x000000000044cb3a in Out::ProgressBar::~ProgressBar (this=0x1cdc6f0, __in_chrg=<optimized out>) at /usr/src/debug/zypper-1.13.2/src/output/Out.h: 835 #1 0x000000000044d3b6 in boost::checked_deleteOut::ProgressBar (x=0x1cdc6f0) at /usr/include/boost/core/checked_delete.hpp:34 #2 boost::scoped_ptrOut::ProgressBar::~scoped_ptr (this=0x7c8518 main::rpm_callbacks+88, __in_chrg=<optimized out>) at /usr/include/boost/ smart_ptr/scoped_ptr.hpp:88 #3 ZmartRecipients::FindFileConflictstReportReceiver::~FindFileConflictstReportReceiver (this=0x7c8510 main::rpm_callbacks+80, __in_chrg=<optimized out>) at /usr/src/debug/zypper-1.13.2/src/callbacks/rpm.h:343 #4 RpmCallbacks::~RpmCallbacks (this=0x7c84c0 main::rpm_callbacks, __in_chrg=<optimized out>) at /usr/src/debug/zypper-1.13.2/src/callbacks/ rpm.h:463 #5 0x00007fa81e91f278 in __run_exit_handlers (status=8, listp=0x7fa81ec845d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #6 0x00007fa81e91f2c5 in __GI_exit (status=<optimized out>) at exit.c:104 #7 0x000000000043e119 in signal_handler (sig=<optimized out>) at /usr/src/ debug/zypper-1.13.2/src/main.cc:46 #8 <signal handler called> #9 0x00007fa81fb284e5 in ?? () from /usr/lib64/libzypp.so.1600 #10 0x00007fa81fb25e14 in ?? () from /usr/lib64/libzypp.so.1600 #11 0x00007fa81f8e8461 in zypp::target::TargetImpl::commitFindFileConflicts(zypp::ZYppCommitPolicy const&, zypp::ZYppCommitResult&) () from /usr/lib64/libzypp.so.1600 #12 0x00007fa81f8e1a3c in zypp::target::TargetImpl::commit(zypp::ResPool, zypp::ZYppCommitPolicy const&) () from /usr/lib64/libzypp.so.1600 #13 0x00007fa81fa58275 in zypp::zypp_detail::ZYppImpl::commit(zypp::ZYppCommitPolicy const&) () from / usr/lib64/libzypp.so.1600 #14 0x00007fa81fa4f825 in zypp::ZYpp::commit(zypp::ZYppCommitPolicy const&) () from /usr/lib64/libzypp.so.1600 #15 0x000000000050c411 in solve_and_commit (zypper=...) at /usr/src/debug/ zypper-1.13.2/src/solve-commit.cc:780 #16 0x000000000046b638 in Zypper::doCommand (this=this@entry=0x1c8f8c0) at / usr/src/debug/zypper-1.13.2/src/Zypper.cc:4789 #17 0x0000000000476f7d in Zypper::safeDoCommand (this=this@entry=0x1c8f8c0) at /usr/src/debug/zypper-1.13.2/src/Zypper.cc:1321 #18 0x000000000043cf25 in Zypper::main (this=this@entry=0x1c8f8c0, argc=argc@entry=5, argv=argv@entry=0x7fff5ec0a188) at /usr/src/debug/ zypper-1.13.2/src/Zypper.cc:377 #19 0x000000000043c279 in main (argc=5, argv=0x7fff5ec0a188) at /usr/src/ debug/zypper-1.13.2/src/main.cc:111 (gdb) When I rerun the update (only on oss) it took time (very loong, a shower + a coffee, and outside break) but finally success. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org