Your message dated Sat, 04 Jul 2026 11:02:56 +0000
with message-id <[email protected]>
and subject line Bug#1126850: fixed in mariadb 1:11.8.8-0+deb13u1
has caused the Debian Bug report #1126850,
regarding mariadb-server: "mysqldump --system=users" fails with error "Illegal 
mix of collations"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1126850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126850
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server
Version: 1:11.8.3-0+deb13u1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

using "mysqldump --system=users" for backing up MariaDB users fails with the 
following error:

mysqldump: Couldn't execute 'SELECT CONCAT(QUOTE(u.user), '@', QUOTE(u.Host)) 
AS u FROM mysql.user u  /*!80001 LEFT JOIN mysql.role_edges e             ON 
u.user=e.from_user               AND u.host=e.from_host          WHERE 
e.from_user IS NULL */ /*M!100005 WHERE is_role='N' */': Illegal mix of 
collations (utf8mb4_general_ci,COERCIBLE) and (utf8mb4_uca1400_ai_ci,COERCIBLE) 
for operation '=' (1267)

I experience this error on a fresh install and also on a system upgraded from 
bookworm.

On Debian Bookworm this command successfully provides a SQL dump for backup.

Best,
 Sven


-- System Information:
Debian Release: 13.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.18.5+deb14-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mariadb-server depends on:
ii  adduser                3.152
ii  debconf [debconf-2.0]  1.5.91
ii  galera-4               26.4.23-0+deb13u1
ii  gawk                   1:5.2.1-2+b1
ii  init-system-helpers    1.69~deb13u1
ii  iproute2               6.15.0-1
ii  libc6                  2.41-12+deb13u1
ii  libdbi-perl            1.647-1
ii  libgcc-s1              14.2.0-19
ii  libpam0g               1.7.0-5
ii  libssl3t64             3.5.4-1~deb13u2
ii  libstdc++6             14.2.0-19
ii  lsof                   4.99.4+dfsg-2
ii  mariadb-client         1:11.8.3-0+deb13u1
ii  mariadb-common         1:11.8.3-0+deb13u1
ii  mariadb-server-core    1:11.8.3-0+deb13u1
ii  passwd                 1:4.17.4-2
ii  perl                   5.40.1-6
ii  procps                 2:4.0.4-9
ii  psmisc                 23.7-2
ii  rsync                  3.4.1+ds1-5+deb13u1
ii  socat                  1.8.0.3-1
ii  zlib1g                 1:1.3.dfsg+really1.3.1-1+b1

Versions of packages mariadb-server recommends:
pn  libhtml-template-perl           <none>
pn  mariadb-plugin-provider-bzip2   <none>
pn  mariadb-plugin-provider-lz4     <none>
pn  mariadb-plugin-provider-lzma    <none>
pn  mariadb-plugin-provider-lzo     <none>
pn  mariadb-plugin-provider-snappy  <none>
pn  pv                              <none>

Versions of packages mariadb-server suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20220412cvs-1.1
pn  mariadb-test       <none>
ii  netcat-openbsd     1.229-1

-- debconf information:
  mariadb-server/nis_warning:
  mariadb-server/old_data_directory_saved:
  mariadb-server/postrm_remove_databases: false

--- End Message ---
--- Begin Message ---
Source: mariadb
Source-Version: 1:11.8.8-0+deb13u1
Done: Otto Kekäläinen <[email protected]>

We believe that the bug you reported is fixed in the latest version of
mariadb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen <[email protected]> (supplier of updated mariadb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 26 Jun 2026 13:13:13 +0000
Source: mariadb
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 1:11.8.8-0+deb13u1
Distribution: trixie
Urgency: medium
Maintainer: Debian MySQL Maintainers <[email protected]>
Changed-By: Otto Kekäläinen <[email protected]>
Closes: 1104533 1110683 1126850 1127431 1137221
Changes:
 mariadb (1:11.8.8-0+deb13u1) trixie; urgency=medium
 .
   * New upstream version 11.8.8 with critical fix for regression in 11.8.7 as
     noted at 
https://mariadb.com/docs/release-notes/community-server/11.8/11.8.8
     and for the following security issues:
     - CVE-2026-48165
     - CVE-2026-48163
   * Previous upstream version 11.8.7 included fixes for several defects as 
noted
     at https://mariadb.com/docs/release-notes/community-server/11.8/11.8.7 as
     well the following security issues:
     - CVE-2026-44173
     - CVE-2026-44172
     - CVE-2026-44171
     - CVE-2026-44170
     - CVE-2026-44169
     - CVE-2026-44168
   * New upstream version included fixes for these Debian tracked issues:
     - MDEV-38698 Upgrade did not fix charset and collation for mysql.user,
       leading to "Illegal mix of collations" errors on upgrades or when trying
       to restore backups (Closes: #1104533, #1126850, #1137221)
     - MDEV-39479 Mroonga hangs on invalid index flag (Closes: #1110683)
     - MDEV-38811 Crash in information_schema.table_constraints when running in
       'skip-grant-tables' mode (Closes: #1127431, affected Akonadi)
   * Also cherry-pick the following upstream debian/ changes:
     - MDEV-34902 debian-start erroneously reports issues (includes security 
fix)
   * Update configuration traces to match changes in system variables
     - new variable 'innodb-buffer-pool-in-core-dump' (default: FALSE)
     - new default value 0->8796093022208 in 'innodb-buffer-pool-size-max'
   * Salsa CI: Disable the uscan job as it is incompatible with MariaDB
Checksums-Sha1:
 f1fb0a4cd80ddf24b3c332eb5150dc4ac46cf291 5675 mariadb_11.8.8-0+deb13u1.dsc
 3d2ae312418e2f40dd14e51eefd4d7751c4c5f25 119402982 mariadb_11.8.8.orig.tar.gz
 2837ef2bd5121662c891e7b1970f40042cf933b1 833 mariadb_11.8.8.orig.tar.gz.asc
 a24d7cfd9a11c991e8d167693a461e6afe07a05d 289544 
mariadb_11.8.8-0+deb13u1.debian.tar.xz
 ef5bc1efb634871e1234b715c2f356125c535c81 10853 
mariadb_11.8.8-0+deb13u1_source.buildinfo
Checksums-Sha256:
 6489e93b0fe80811ff19fb620f59bdcdd2f2287834bda4fe20382f25545b11a9 5675 
mariadb_11.8.8-0+deb13u1.dsc
 bd023a4959faf012db7f0ebfc0d276729e67e5443df193163f98d80fdfc524c9 119402982 
mariadb_11.8.8.orig.tar.gz
 12601a392e99fc15abd5c03abe3b5217d50e8a8578fc93fd3a6cd871552e6065 833 
mariadb_11.8.8.orig.tar.gz.asc
 1d02fac420032f08704d2885aefa52dfe65aa8d6c36a8d44132065b7b88cbd40 289544 
mariadb_11.8.8-0+deb13u1.debian.tar.xz
 bb27c5191e32d6ac569af59b728076d3d1fac32ec1b5cb141f355e00dcc77bd0 10853 
mariadb_11.8.8-0+deb13u1_source.buildinfo
Files:
 70e5880ff08516a46d932bf295047400 5675 database optional 
mariadb_11.8.8-0+deb13u1.dsc
 2d28267407373d2771127eec3416b043 119402982 database optional 
mariadb_11.8.8.orig.tar.gz
 a1ba25c9186dc62e45542dc79d79bc4f 833 database optional 
mariadb_11.8.8.orig.tar.gz.asc
 05cd17186307ceef9294834c272a2727 289544 database optional 
mariadb_11.8.8-0+deb13u1.debian.tar.xz
 aba0f58a08d58f66614a9d956f10d46c 10853 database optional 
mariadb_11.8.8-0+deb13u1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEY+78PeFNUUbOfyS/NLitfZUp55MFAmpG3IEACgkQNLitfZUp
55PK3xAAhiB+Ovr5q/CvyOYfM7rsv+L8S+7d9kGKdsn1anqj5OdKsHR4fXlF1WRa
99tiF6sxOswvOOtVORhST9QaOtmcCiFpw2a3Fazx3CO07OisFpm4Q/GvVNRVF7JV
pj7eEV9Wk7FgxcxXekM/hl73E6DVPlWF/B57tMS+DlsUnDqlDqDdNadA1BSNMKbj
8cca/DgGT+VzaU6faudmKc+ZQB/Bv1FUu+g9ObxzDBxKGUe14lSVSi4Nkdpgw8N1
fkQF7RlS4jGBb/DNyQjXKfrxMuIE+/FLL7H42NK+aunM/LmQRLB/Fh9arwENBS+y
hZBR1bcbw0BMRhlpw671fPEiSZ9aobGPwdfIGn9AxMluhpDSpdznKO3OjnAJH17W
OCrtnA81QXB0mr4ecWeVJv9f2wU2SNHZ2yrPILamnvb8ZYnaQK/2wBj8WPTeShYp
6BjvkBqgIPp6Gm800ldjNpgikhmjDHi/0dw6jdr0PClOrqrGdKhgOZ44xLdtBUVL
p1cMeNooa7DHzDxfFJQ5GB86E+9HTWAQZyDt095Hzc0sXEpxWc/z8MN2Tz2GG6Fb
1grYIKwkPB+9tX6/8/0eVy0pn1kLDAY4BwhF3mECAW7q1LQWW2FZubCgMz46tc72
GowW2gEuW95hvA/cE8pKnh/tjI+h4MH+LzfW67pjnMFYR+RMqO4=
=mZRv
-----END PGP SIGNATURE-----

Attachment: pgpzxWTx25gY2.pgp
Description: PGP signature


--- End Message ---

Reply via email to