BZ 1953675 was accepted as a prioritized bug, but the assignee hasn't responded. Is this something the KDE SIG can look into and provide more information on?
I'm wondering if it's related to some hacks done to "fix" the user switching blocker for F33 and if that's the case it may or may not be easy to fix.
@rdieter, please take a look at this?
Metadata Update from @ngompa: - Issue assigned to rdieter
Metadata Update from @ngompa: - Issue tagged with: meeting
Have we made any progress on this Prioritized Bug? Is it a "cantfix" due to the hacks to fix user-switching for F33?
I can commit to commenting in the bugzilla this week. Most likely will require some debugging/logs from users to determine cause of db startup/upgrade failures... and work through it.
I suspect there's multiple issues
I'll take the liberty of closing this, with continued followup in bugzilla.
Current best (only?) way to resolve this is to document a manual fix as outlined in the bug already, something like: https://bugzilla.redhat.com/show_bug.cgi?id=1953675#c4 1. $ akonadictl stop 2. # dnf module switch-to mariadb:10.4 3. $ akonadictl start 4. $ akonadictl stop
[Note] InnoDB: Starting crash recovery from checkpoint LSN=42740240443 … [Note] InnoDB: 10.4.18 started; log sequence number 42740240452; transaction id 92259863 [Note] /usr/libexec/mysqld: ready for connections. Version: '10.4.18-MariaDB' socket: '/run/user/500/akonadi/mysql.socket' port: 0 MariaDB Server … [Note] /usr/libexec/mysqld (initiated by: unknown): Normal shutdown [Note] InnoDB: FTS optimize thread exiting. [Note] InnoDB: Starting shutdown... … [Note] InnoDB: Shutdown completed; log sequence number 42740296470; transaction id 92259875 [Note] /usr/libexec/mysqld: Shutdown complete
Metadata Update from @rdieter: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.