Could you give a try to LO 7.1.4 from LO ppa (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa)?

Indeed 6.X branch is EOL and there won't be any new LO version on 7.0 branch after the released 7.0.6 version.

I have upgraded using the PPA

LO is now
Version: 7.1.4.2 / LibreOffice Community
Build ID: 10(Build:2)
CPU threads: 12; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Ubuntu package version: 1:7.1.4~rc2-0ubuntu0.20.04.1~lo1
Calc: threaded

libreoffice-mysql-connector/focal,now 1:7.1.4~rc2-0ubuntu0.20.04.1~lo1 amd64 [installed]

Problem still occurs. Second page forward browsing the test table results in Base crashing and recovery dialog starts.

It has also introduced authentication issues for my jdbc connection so I will will have to revert to previous version as this is not a testing system.

The test SQL dump has a collation "utf8mb4_0900_ai_ci" which unfortunately fails to get imported into my version 5 server.

Copied and pasted the SQL manually and removed the collation statement via the mysql CLI.

No crash for me when scrolling through result set in Table browse mode with

Version: 7.1.4.2 / LibreOffice Community
Build ID: a529a4fab45b75fefc5b6226684193eb000654f6
CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR
Calc: threaded

I scrolled from the first record to the last record with no crash.

This sounds like a bug that is specific to the Ubuntu version, whether it is GTK3 or some other handling error causing a crash.

Couldn't confirm the buggy behavior.

Tested with the attached table, also with a table with 8000 rows and 12 columns and a table with 30000 rows and 15 columns. Scrolled though the table to the end and back to the start. Couldn't reproduce a crash with direct connection - here to MariaDB - and LO 7.2.0.1 VCL:kf5 on OpenSUSE 15.2 64bit rpm Linux.

Think it is a special bug of Ubuntu version of LO and direct connection. Please try the packages from LO directly. You could install these packages parallel as a user-defined installation. If you need help for this: Send me a private mail.

The problem is occurring on a system I have just migrated from Ubuntu 18.04 with mysql 5 which connected fine, to Ubuntu 20.04 with mysql 8. Mysql 8 seems less supported in 20.04. odbc and jdbc drivers are no longer in Ubuntu repositories and needed to be obtained from mysql community. Have any of these attempts to reproduce issue been against a mysql 8 server?

On pc Debian x86-64 with master sources updated today, I don't reproduce this.
However since I use MariaDB server, I couldn't create the table with utf8mb4_0900_ai_ci since I had an unknown collation error.
I used utf8mb4_general_ci instead.

Also have in mind that the native connector used by LO is in fact MariaDB not Mysql one. (mariadb-connector-c-3.1.8-src.tar.gz)

Created attachment 178884 [details]
soffice --backtrace gdbtrace.log

I have revisited this problem after upgrading LO to 7.1 from backports

Base still crashes when I scroll through the t_table1 table (second pgdn)

Current software releases:

Ubuntu 5.13.0-35-generic #40~20.04.1-Ubuntu 

LibreOffice 7.1.7.2 10(Build:2)
libreoffice/focal-backports,now 1:7.1.7-0ubuntu0.21.04.1~bpo20.04.1 amd64 [installed]
libreoffice-mysql-connector/focal-backports,now 1:7.1.7-0ubuntu0.21.04.1~bpo20.04.1 amd64 [installed]

mysql  Ver 8.0.28-0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu))
mysql-client/focal-updates,focal-updates,focal-security,focal-security 8.0.28-0ubuntu0.20.04.3 all

Have reproduced the problem while running with --backtrace option see attached gdbtrace.log

If you are using the special Ubuntu packages for LO and the special connection to a MySQL 8.0-connection please report this bug to Ubuntu.

See https://wiki.documentfoundation.org/ReleaseNotes/6.2#Base
MySQL C++ connector has been removed and MariaDB C connector is used since LO 6.2 (LGPL).

You database is working without problems with LO directly installed from the packages of LO and MariaDB.

If the direct connector for MariaDB doesn't work well with your MySQL database please use JDBC or ODBC for the connection. 
You could get the JDBC connector from here:
https://dev.mysql.com/downloads/connector/j/
You will only need mysql-connector-java-8.0.27.jar for the connection.
The driver should be added in the class path for java (directly in LO).
Connection to the driver will be set by com.mysql.cj.jdbc.Driver

I am not using any special packages or extensions.

I am not using MariaDB, this is a mysql installation.

My understanding is that direct connection just requires installation of libreoffice-mysql-connector package.

I had problems with dependencies trying to install the ODBC Connector deb package from MySQL communities. I did not pursue.

The JDBC connector from communities is a functioning workaround, but not that easy to configure.
mysql-connector-java/now 8.0.28-1ubuntu20.04 all [installed,local]

(In reply to AJ from comment #11)
> 
> My understanding is that direct connection just requires installation of
> libreoffice-mysql-connector package.

I have looked through all packages, which are part of LO. There is no package like "libreoffice-mysql-connector" part of the *.deb or *.rpm packages. The connection is included in the package for base.

Could it be you installed an old connector, which worked in versions before LO 6.2? Since LO 6.2 the connector is included and couldn't be separately installed with packages from LO. 

When reading about your installation you are using special packages from Ubuntu, not from LO. Please download the packages from 
https://www.libreoffice.org/download/download/
and test this packages. You will get an installation like this:
Version: 7.3.1.3 / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

Have a look at the Build ID. This is an ID from LO. The Ubuntu packages are packed and combined by Ubuntu, not by LO.

Sorry didn't mean to mislead about special.
All my installs have been from Ubuntu repositories.

I tried removing the libreoffice-mysql-connector package.

Base seems to connect directly successfully without it.

Still get the crash though.

This problem does not seem to be affecting any one else, I think I will park it here for he moment as I have a workaround. 

I will probably be upgrading ubuntu when 22.04 releases with LO 7.2 I think and will test again.

(In reply to AJ from comment #13)

You couldn't get it working, because the direct connection from LO is a connection to MariaDB. So newer versions of MySQL might be not supported with direct connection.

Again: JDBC connection will work. Have a look at Base Guide
https://books.libreoffice.org/en/BG73/BG7302-CreatingADatabase.html#toc9

Could you try this:
- please uninstall any LO version you got
- upgrade to Ubuntu 23.10 (or 22.04 if you want to stick to LTS)
- install LO version from https://launchpad.net/~libreoffice/+archive/ubuntu/ppa to have recent LO version
- rename your LO directory profile (see https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile)

Dear AJ,

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