Description: LibreOffice crashes when trying to save a new document, or save an existing document with a new name. When started from the terminal, after the crash the following message appears: LibreOffice(17047) KSambaSharePrivate::getNetUserShareInfo: We got some errors while running 'net usershare info' LibreOffice(17047) KSambaSharePrivate::getNetUserShareInfo: "Failed to init messaging context The error arose in the 5.3 release series, don't know when exactly. But in 5.4 RC it is still there. Happens in Wrtier, Calc and Impress,other components not tested. Steps to Reproduce: 1. Start LO (be it Writer, Calc, or Impress) (to see error messages, start it from the terminal) 2. Make a new document, fill it with something 3. (Try to) save it Actual Results: LO crashes, leaving the message LibreOffice(17047) KSambaSharePrivate::getNetUserShareInfo: We got some errors while running 'net usershare info' LibreOffice(17047) KSambaSharePrivate::getNetUserShareInfo: "Failed to init messaging context Expected Results: LO saves the document, and returns to standard LO-environment Reproducible: Always User Profile Reset: Yes, a few times, with different LO-releaes; no result. Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
You could try getting a backtrace: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information Are you using Samba, then? You have no step of setting it up.
Created attachment 135807 [details] Backtrace of LO Writer Backtrace of LO-writer, after trying to save a document.
No, I am not using Samba. No Windows-systems in our infra, so no need to use it. I've made a backtrace, add it as an attachment.
Lots of "Missing separate debuginfo" messages - is the backtrace any use this way? Or must I add *all* debug components to my system?
"/usr/lib64/libreoffice/program/gdbtrace:9: Error in sourced command file: No stack." -> generation of the backtrace failed.
Looks like you are using openSUSE, so check here for the debug packages instructions: https://en.opensuse.org/openSUSE:Bugreport_LO#How_to_get_backtrace
Created attachment 135814 [details] Backtrace following openSuse method Created a new backtrace, following the method from openSuse as indicated. Doubt if this is more useful...
(In reply to Jogchum Reitsma from comment #7) > Created attachment 135814 [details] > Backtrace following openSuse method > > Created a new backtrace, following the method from openSuse as indicated. > > Doubt if this is more useful... Just to clarify, did you install the debuginfo packages? If yes, it is weird that it is not working.
I added all the LO-dubug packages of the LO-components I use. But no more. As mentioned in a previous post, should I install *all* the debug packages that are indicated missing in the gdb.log file? Of course I can, but they are quite a few, so it will take some time and space.
Created attachment 135815 [details] Backtrace with all missing dubug packages installed I installed all the debug packages gdb complained where missing, 128 in total. The result is the same I think, except for the complaints of gdb.
While the debug-problem is not solved, the original problem is, automagically. Somewhere before my current version 5.4.1.2.0 the bug, which sat quiet for at least half a year, has flown away. Hopefully to not return! Thanks for thinking with me!
(In reply to Jogchum Reitsma from comment #11) > While the debug-problem is not solved, the original problem is, > automagically. Somewhere before my current version 5.4.1.2.0 the bug, which > sat quiet for at least half a year, has flown away. Hopefully to not return! > > Thanks for thinking with me! Great! Let's close as WFM.