There are quite a few crashes reported for LibreOffice on bugzilla. A great way to help developers to resolve these issues is to reproduce the crash and provide and attach a stacktrace to the bug.
Deleted "Easyhack" from summary.
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
*** Bug 47652 has been marked as a duplicate of this bug. ***
Lets forget about this. Getting bt is a good idea in general that doesn't need a specific bug for it
Reopening, there needs to be an open but for it to show up in the list of EasyHacks.
Status 'NEW' is more appropriate for this bug.
how to get a backtrace on Linux, Windows or Mac is documented on this page:
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner SkillDebug, TopicDebug -> TopicDebugging)
Remove skillDebug, superceded by topicDebug.
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
can anyone please explain what needs to be done here??(in some detail please)
Created attachment 139446 [details]
Backtrace on linux
Hi, as suggested in https://bugs.documentfoundation.org/show_bug.cgi?id=46892#c7 i tried to produce the backtrace on linux. Please let me know if this can be of any use.
wantBacktrace keyword is used to track which bugs need backtrace -> https://bugs.documentfoundation.org/buglist.cgi?keywords=wantBacktrace%2C%20&keywords_type=allwords&list_id=771020&query_format=advanced&resolution=---
Starting to Resolve this issue.
No need to assign this issue to yourself. People can work in parallel here