Description: I made an element transparent, I put it in background, and I moved some element which were in front of this element. After few seconds, Libre Office draw began slow and xorg crashed. In the syslog journal I see: libreoffice-draw.desktop[16874]: ** (soffice:16892): WARNING **: Unknown event notification 36 gnome-session[15884]: (tracker-miner-fs:16055): Tracker-CRITICAL **: (Sparql buffer) Error in task 0 of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url (strerror of errno (not necessarily related): Aucun fichier ou dossier de ce type) I have Ubuntu Gnome 16.04 Steps to Reproduce: 1. Create an element E1 2. Create an other element E2 3. Change the transparency of the element E2 4. Put the element E2 in background 5. Move the element E1 Actual Results: LibreOffice Draw began slow or/and xorg crash Expected Results: no crash Reproducible: Sometimes User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Created attachment 134301 [details] crash file
I had also the bug on libreoffice 5.3 I attach a file which create crash of gnome. You just need to change the transparency of the legends to crash the interface. Thank you,
When you say the legend you mean the blue square, right? I can't reproduce it in Version: 6.0.0.0.alpha0+ Build ID: 08f6f9dded1b142b858c455da03319abac691655 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group or gtk3 Could you please copy the info from Help - About LibreOffice?
Yes I mean the blue square. My about: Version: 5.3.4.2 Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; VCL: gtk2; Layout Engine: new; Locale: fr-FR (fr_FR.UTF-8); Calc: group Thank you for your help
I think that Tracker-CRITICAL message is irrelevant: https://bugzilla.redhat.com/show_bug.cgi?id=1192224 I wonder, if the same happens in Ubuntu Gnome 17.04.
Not reproducible for me under Ubuntu 16.04 (Unity) with: Version: 5.4.1.2 Build ID: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; Locale: fr-FR (fr_FR.UTF-8); Calc: single Version: 5.4.3.0.0+ Build ID: 5deb6f29a4038f2de88abbc676e485f5bb5c150d Threads CPU : 4; OS : Linux 4.4; UI Render : par défaut; VCL : gtk3; Ubuntu_16.04_x86-64 Locale : fr-FR (fr_FR.UTF-8); Calc: single Version: 6.0.0.0.alpha0+ Build ID: a1976555e0ebb9fc1575c2241e8b0878ccb66410 Threads CPU : 4; OS : Linux 4.4; UI Render : par défaut; VCL: gtk3; Ubuntu_16.04_x86-64 Locale : fr-FR (fr_FR.UTF-8); Calc: single @Michael: You are using GTK2 VCL plugin. Please could you try the GTK3 plugin ? To do that install libreoffice-gtk3 package, launch LibreOffice and check About LibreOffice: you should see VCL: gtk3 instead of VCL: gtk2. If you still see gtk2, you can test in a terminal forcing using gtk3: open a terminal and type the command export SAL_USE_VCLPLUGIN="gtk3" then launch LibreOffice from the terminal (command libreoffice). Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
Thank you very much Jean-Baptiste Faure, Your solution seems work. :)
(In reply to michael from comment #8) > Thank you very much Jean-Baptiste Faure, Your solution seems work. :) Thank you for the feedback. Changed the summary accordingly: GTK2 needed. Best regards. JBF
no repro in Xubuntu 16.04.3 in Version: 6.0.0.0.alpha1 Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Linux 4.11; UI render: default; VCL: gtk2; Locale: ru-RU (ru_RU.UTF-8); Calc: group
Hi Michael, Which version of Gtk2 are you using?
Dear Bug Submitter, 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-20180502
Dear Bug Submitter, 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-20180530
QA Administrator, Sorry I didn't see your previous message... Jean-Baptiste Faure solved my problem. Since, my bug submit I change my operating system. And now everything work fine. I can't reproduce the bug. So I change the status to fixed. Thank you,
Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.