On lundi, 11 juillet 2016 08.49:45 h CEST ellanios82 wrote:

On 07/07/2016 08:45 AM, ellanios82 wrote:

...

tw: starting LibreOffice is causing xfce to crash

- today crash happened on initial opening of LibreOffice , and CLICK on ICON of recent Spreadsheet to Open. ..........

regards

If you have a look at coredumpctl you should be able to see if a coredump occurs with libreoffice. then you could debug it (will certainly ask for -debuginfo package installation) sudo coredumpctl gdb [PID NUMBER] once inside issue bt it should show something similar ( sorry this one is for zypper ) sudo coredumpctl gdb 28340 PID: 28340 (zypper) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: lun 2016-07-11 07:59:14 CEST (1min 16s ago) Command Line: zypper -v up 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: 13c8107727b1411184a713b4a32a668d Machine ID: 5796a69412fbda1c055a261856a26e81 Hostname: qt-kt.labaroche.ioda.net Coredump: /var/lib/systemd/coredump/core.zypper. 0.13c8107727b1411184a713b4a32a668d.28340.1468216754000000.xz Message: Process 28340 (zypper) of user 0 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11 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...(no debugging symbols found)...done. [New LWP 28340] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `zypper -v up'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000000044cb3a in ?? () Missing separate debuginfos, use: zypper install zypper- debuginfo-1.13.2-1.2.x86_64 (gdb) bt #0 0x000000000044cb3a in ?? () #1 0x000000000044d3b6 in ?? () #2 0x00007fcabe571278 in __run_exit_handlers (status=8, listp=0x7fcabe8d65d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #3 0x00007fcabe5712c5 in __GI_exit (status=<optimized out>) at exit.c:104 #4 0x000000000043e119 in signal_handler(int) () #5 <signal handler called> #6 __strcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcpy-sse2- unaligned.S:295 #7 0x00007fcabf77a40f in ?? () from /usr/lib64/libzypp.so.1600 #8 0x00007fcabf777e14 in ?? () from /usr/lib64/libzypp.so.1600 #9 0x00007fcabf53a461 in zypp::target::TargetImpl::commitFindFileConflicts(zypp::ZYppCommitPolicy const&, zypp::ZYppCommitResult&) () from /usr/lib64/libzypp.so.1600 #10 0x00007fcabf533a3c in zypp::target::TargetImpl::commit(zypp::ResPool, zypp::ZYppCommitPolicy const&) () from /usr/lib64/libzypp.so.1600 #11 0x00007fcabf6aa275 in zypp::zypp_detail::ZYppImpl::commit(zypp::ZYppCommitPolicy const&) () from / usr/lib64/libzypp.so.1600 #12 0x00007fcabf6a1825 in zypp::ZYpp::commit(zypp::ZYppCommitPolicy const&) () from /usr/lib64/libzypp.so.1600 #13 0x000000000050c411 in solve_and_commit(Zypper&) () #14 0x000000000046b638 in Zypper::doCommand() () #15 0x0000000000476f7d in Zypper::safeDoCommand() () #16 0x000000000043cf25 in Zypper::main(int, char**) () #17 0x000000000043c279 in main () (gdb) If you can get a correct coredump, it will certain help to add it to your bugzilla entry. -- 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