Description: LO Crashes while creating table relationships in Base. It crashes in every database as I have more than one on which I am working. Details I believe may be of importance: This is a recent issue. LO worked fine until recently although the timing I can't place a specific update to the change either with LO or other systems updates. The crash is never recorded in Mint's Systems Reports. After uninstalling LO and installing AOO, AOO crashes also at the same point. The problem is persistent in safe mode so not my user profile. As for the enablement of openGL, I am not sure. Steps to Reproduce: 1.1. Open Tools > Relationships 2. Select > New Relationship 3. Using the drop down select the correct table for the relationship 4. Crash 2. 3. Actual Results: LO Error dialog pops up stating the following: Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. Expected Results: LO should have allowed me to choose the table and create the new relationship. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Unfortunately, As noted above, LO is now uninstalled. I used version 6.1.5.2.
Created attachment 150769 [details] Screenshot of Error Message
I can't reproduce it in Version: 6.3.0.0.alpha0+ Build ID: 0eaa0804085dd6e93257dd31361490720456679d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
*** Bug 124762 has been marked as a duplicate of this bug. ***
Well, I don't know if this is good news or bad news. It appears that the latest System Update pushed out and installed last night 4/16/19 fixed the issue. In attempting to satisfy your request I opened every single file and tried to reproduce the crash but could not. The only other thing that I can think of is that, as mentioned previously, I uninstalled LO and installed AOO hoping to continue my work but it experienced identical crashing. So, I removed AOO and again installed LO. Maybe that did something. Do you still want me to send one of the files that experienced the problem?
Please disregard the last comment. I have more specifics on the crash now. It is only when I open the database by clicking on it's respective icon in the LibreOffice Start Center. It does not crash when I open the file by clicking on Open File and the following the path to the file, it works fine. So, still a problem but no longer rendering LO useless. I will scrub the file and get it to you soon.
Created attachment 150891 [details] HSQLDB Still in development to track personal sales results Here is the sanitized file requested.
No crash for me with Version: 6.3.0.0.alpha0+ Build ID: c74ec989eabdf7ffb5ea4d6f43757116261eaeed CPU threads: 4; OS: Mac OS X 10.14.4; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded
@Scott : I used the test file you provided.
No crash with LO6073 Build ID : 1:6.0.7-0ubuntu0.18.04.5 on LinuxMint 19 No crash either with Snap LO6222 Build ID : libreoffice-6.2.2.2-snap1 on LinuxMint 19 with the test file provided.
No crash either when testing file on Linux ElementaryOS Juno with LO6073 or 6222(snap)
(In reply to Alex Thurgood from comment #10) > No crash either when testing file on Linux ElementaryOS Juno with LO6073 or > 6222(snap) Same situation here (Ubuntu 18.04) along with trying LO6.0 - LO6.3 I tried different Java packages: Java-11-openjdk jdk-10.0.2 jdk-8-openjdk No problem with any of them.
No crash Version: 6.3.0.0.alpha0+ Build ID: 1ae5ca077119982ae83833871326c86d9930ae11 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11;
Hello Scott, LibreOffice 6.1.6 as been announced as final this week. Could you please download it from https://www.libreoffice.org/download/libreoffice-fresh/ and retest this bug ? 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.
@Scott : - which theme are you using on Mint ? - which desktop ?
(In reply to Xisco Faulí from comment #13) > Hello Scott, > LibreOffice 6.1.6 as been announced as final this week. > Could you please download it from > https://www.libreoffice.org/download/libreoffice-fresh/ and retest this bug ? > 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. First, I apologize for not getting back to you in a timely fashion. Second, I did install 6.1.6 as instructed and the crash continues. Lastly, last night I just installed 6.2.4, which I love, still crashes. Specifically, the crash happens in the "New Relationship" creation dialog when invoking the right drop-down box to change tables. I would love to get this resolved and I totally appreciate all of the effort being done.
(In reply to Alex Thurgood from comment #14) > @Scott : > > - which theme are you using on Mint ? > - which desktop ? Alex, I am using Mint 19.1 Cinnamon 4.0.10. My desktop theme is as follows: Window Borders: Mint-Y-Dark Icons: Mint-X-Teal Controls: Mint-Y-Dark-Teal Mouse Pointer: DMZ-Black Desktop: Mint-Y-Dark-Teal Please advise if you think I should restore the original themes/use different themes/or even just be more consistent across the board with whatever theme I choose. Thanks. Scott
@Scott: I seem to recall having seen elsewhere reports of issues when using the Mint-Y Dark theming with libreoffice, which appear to be linked to the libreoffice GTK3+ package - perhaps there is a correlation here ?
(In reply to Alex Thurgood from comment #17) > @Scott: I seem to recall having seen elsewhere reports of issues when using > the Mint-Y Dark theming with libreoffice, which appear to be linked to the > libreoffice GTK3+ package - perhaps there is a correlation here ? @Alex, Thanks for the info. I switched all themes to Mint-X with all of the standard color Mint Green, no specialty color and even the pointer to DMZ-White. Rebooted. Crash still occurs. In the last few days I have attempted to invoke the New Relation Tool in different ways and initially invoked the database file in different ways but all ways crash. In fact, I am noticing that both dialog drop downs will cause a crash, not just the right side as I previously reported. I appreciate your help.
I can't reproduce it in Version: 6.3.0.0.alpha1+ Build ID: c98b1f1cd43b3e109bcaf6324ef2d1f449b34099 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided
@Xisco, Here is the paste of the Help-About LO of which you requested. Version: 6.2.4.2 Build ID: 1:6.2.4-0ubuntu0.18.04.1~lo1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Scott
Thank for providing the info. Could you please create and attach a screencast showing the steps? There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web). I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested screencast is provided.
Created attachment 152044 [details] Screen Recording of Base Crash Replication @Xisco, I have uploaded the screen recording as you requested. I used SimpleScreenRecorder as I run Linux Mint 19.1 Cinnamon. This is in .mkv file format. Please let me know if you would prefer a different format or even a different recording. Thanks Again, Scott
(In reply to Scott from comment #22) > Created attachment 152044 [details] > Screen Recording of Base Crash Replication > > @Xisco, > > I have uploaded the screen recording as you requested. I used > SimpleScreenRecorder as I run Linux Mint 19.1 Cinnamon. This is in .mkv > file format. Please let me know if you would prefer a different format or > even a different recording. > > Thanks Again, > > Scott Hi Scott, Thank you very much for providing the screencast. I've tried to reproduce the crash by following the same steps you performed in the video but I couldn't reproduce it. I see the file you attached is different from the file you're using in the video. Could you please attach the same file ?
@Xisco, Attached is the screen-cast of Base Crash using the original file. Not that the crash now occurs regardless of which drop-down control is invocated in the New Relationship tool. It used to be only the right drop down. Thanksm Scott
Created attachment 152077 [details] Screen Recording of Base Crash Replication using original file
@Et Al - I have some follow up information that might be helpful but not sure of protocol. I am listing it here. Please advise if it should go elsewhere. Thinking back through the initial installation of LO on this system, I chose to install via flatpak. I don't remember my exact reasoning but it may have been around upgrading to the most recent version, I decided to install LO via PPA and not flatpak. And I ran both for a short while until I removed the flatpak version. Maybe that's helpful...maybe I just crushed your world. Either way...let me know.
(In reply to Scott from comment #26) > Thinking back through the initial installation of LO on this system, I chose > to install via flatpak. I don't remember my exact reasoning but it may have > been around upgrading to the most recent version, I decided to install LO > via PPA and not flatpak. And I ran both for a short while until I removed > the flatpak version. > @Scott : flatpak and PPA installs should be completely separate...at least that is my understanding of the whole theory of flatpak installations. Whether or not that has had an impact on your particular ODB file over time is a whole other question. However, PPA versions are unfortunately not the most reliable, as experience has shown, time and time again, and as can be readily seen from other reports posted in this bugzilla, on the Ask forum, and in the Ubuntu launchpad bugtracker.
Sorry, still no repro, even when following the steps in your video, with the distrib provided version (current 6.0.7.3, Build ID: 1:6.0.7-0ubuntu0.18.04.6) for Linux Mint 19 Tara Using the test file you posted, I can add new Tables for the relationship, when I click on Create New Relationship, I can choose any of the added tables from the dropdown menu on the left hand side and choose any of the available tables from the right hand side drop down menu, without causing a crash. Also no repro with snap : Version: 6.2.2.2 Build ID: libreoffice-6.2.2.2-snap1 Threads CPU : 1; OS : Linux 4.15; UI Render : par défaut; VCL: gtk3; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded
(In reply to Alex Thurgood from comment #28) > Sorry, still no repro, even when following the steps in your video, with the > distrib provided version (current 6.0.7.3, Build ID: > 1:6.0.7-0ubuntu0.18.04.6) for Linux Mint 19 Tara > > Using the test file you posted, I can add new Tables for the relationship, > when I click on Create New Relationship, I can choose any of the added > tables from the dropdown menu on the left hand side and choose any of the > available tables from the right hand side drop down menu, without causing a > crash. > > Also no repro with snap : > > Version: 6.2.2.2 > Build ID: libreoffice-6.2.2.2-snap1 > Threads CPU : 1; OS : Linux 4.15; UI Render : par défaut; VCL: gtk3; > Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR > Calc: threaded @Alex at this point I am ready to assume I corrupted something either in Mint or Cinnamon. Having already completely purged LO from my system and reinstalling, I am ready to accept that I will need to do a complete fresh install of Mint. This may not be the forum for this, but would you have any other suggestions to attempt to fix my issue without the fresh install?
(In reply to Scott from comment #29) > > @Alex at this point I am ready to assume I corrupted something either in > Mint or Cinnamon. Having already completely purged LO from my system and > reinstalling, I am ready to accept that I will need to do a complete fresh > install of Mint. This may not be the forum for this, but would you have any > other suggestions to attempt to fix my issue without the fresh install? @Scott : I would guess, in order : 1) forcibly remove all of the flatpak installation - I've never used flatpak, so I'm afraid I can't advise you much there If the flatpak installation includes extras like the report-builder, report-builder-bin, and sdbc packages, make sure that they are also removed 2) Forcibly remove the distrib provided version of LO and any associated extras (lang-packs, extensions, sdbc drivers, report-builder, report-builder-bin, etc) This is usually achieved with sudo apt-get purge <packet-name>, so for libreoffice, you could try: sudo apt-get purge libreoffice-* 3) remove, or better, rename, your LO user profile folder. 4) Try reinstalling the various required LO bits via sudo apt-get install again. Other than that, you might well be up for a complete OS re-installation, but that's a pretty drastic measure for one software application.
@Scott : any news or update on this issue ?
(In reply to Alex Thurgood from comment #31) > @Scott : any news or update on this issue ? @Alex, Yes. Completed all suggested fixes with no change. While LO still crashes using the relationship tool's drop downs, drag/dropping the relationship and then opening the tool via the right button on the relationship line to select update/delete options is working fine. I have chosen not to do a complete reinstall given this work-around. Thanks for checking.
Hi Scott, Thanks for providing the video. Still, I can't reproduce it in Version: 6.2.7.0.0+ Build ID: 28c6af3ddc283ca9c5712359a9abcb385c1575b4 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Would you mind trying with the new LibreOffice 6.3.0.4 released last week ?
Dear Scott, 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 Scott, 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