This bug was filed from the crash reporting server and is br-0aec7e1d-9bdd-43f8-b661-aad03f0b9a4c. ========================================= LibreOffice unexpectedly crashed while editing slide, i.e. I was selected a line and tried to move it. Version: 5.4.2.2 ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 Processor threads: 4; OS: openSUSE Leap 42.3 Linux kernel: 4.4; GUI: default; VCL: gtk2 Processor: Intel i5-4300M Graphics: Intel HD Graphics 4600 MESA version: 17.1.6 LibreOffice installed via RPMs from LibreOffice site. I can not intentionally reproduce this bug.
@devs: searching about deque in vcl part of code, I found "typedef std::deque<std::pair<GdkScreen*, int> > ScreenMonitors_t;" on gtksys.hxx Searching about ScreenMonitors_t + "push_back", I found this: 109 for (gint j(0); j != nMonitors; ++j) 110 { 111 GdkRectangle aGeometry; 112 gdk_screen_get_monitor_geometry(pScreen, j, &aGeometry); 113 aGeometries.push_back(aGeometry); 114 } in GtkSalSystem::countScreenMonitors() see https://opengrok.libreoffice.org/xref/core/vcl/unx/gtk/gtksys.cxx#113 @reporter: just to be sure, do you use several monitors? Also, are you able to reproduce the crash? If yes, could you try with another rendering, I mean: - launch a terminal, - type one of these: - for gen rendering: export SAL_USE_VCLPLUGIN=gen - for kde rendering: export SAL_USE_VCLPLUGIN=kde4 - launch LO with your file
I have only one monitor, this is laptop monitor. But as Linux user, I use a lot of virtual desktops (in KDE Plasma 5), and some LibreOffice documents were in different desktops.
I still can not reproduce this bug, however in https://crashreport.libreoffice.org/stats/signature/_ZNSt5dequeImSaImEE16_M_push_back_auxIJRKmEEEvDpOT_ I see that 12 other Linux users had same problem in last month.
Could you please share the document?
Unfortunetly document was not saved before crash
@devs: I gave the wrong pointer, it's some lines below in fact: https://opengrok.libreoffice.org/xref/core/vcl/unx/gtk/gtksys.cxx#122 emplace_back replaced push_back with c856ae17aff5db258eb16713f56fce9f28400d47 @@ -119,7 +119,7 @@ GtkSalSystem::countScreenMonitors() GdkRectangleCoincident())); nMonitors = std::distance(aGeometries.begin(), aUniqueEnd); } - maScreenMonitors.push_back(std::make_pair(pScreen, nMonitors)); + maScreenMonitors.emplace_back(pScreen, nMonitors); } } c++filt _ZNSt5dequeImSaImEE16_M_push_back_auxIJRKmEEEvDpOT_ gives: void std::deque<unsigned long, std::allocator<unsigned long> >::_M_push_back_aux<unsigned long const&>(unsigned long const&)
Seeing the 12 same reports in crashreporter, let's put this one to NEW. Searching about what could segfault when creating std::pair, I found this: https://stackoverflow.com/questions/19009070/stdmake-pair-segmentation-fault-with-custom-class Since "pScreen" type is GdkScreen*, this could be the pb. Caolán: thought you might be interested in this one since it concerns gtk part (+virtual desktop).
I think you've definitely found the crashing line. That appears to be the only std::deque::push_back pScreen is just a GdkScreen *pointer* though and nMonitors just a number so custom classes doesn't arise, just as well be two integers really, so perhaps the problem is with the maScreenMonitors or above in the stack trace I can't actually see how one could get from vcl::Window::AcquireGraphics to GtkSalSystem::countScreenMonitors countScreenMonitors is called either from GtkSalSystem::GtkSalSystem which should be done long before now or from screenSizeChanged and monitorsChanged which should be called from signal callbacks which isn't the case here. so I don't know what's going on here. I feel a more generic bug further up the stack though.
Dear opensuse.lietuviu.kalba, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Looking at https://crashreport.libreoffice.org/stats/signature/_ZNSt5dequeImSaImEE16_M_push_back_auxIJRKmEEEvDpOT_ we only have crash report from LibreOffice 5.4.2.2 which is EOL version. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Dear opensuse.lietuviu.kalba, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear opensuse.lietuviu.kalba, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp