Code: Select all

sudo apt install mysql-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) mysql-server:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un puN Ib >
Broken mysql-server:amd64 Depends on mysql-server-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH >
  Considering mysql-server-8.0:amd64 1 as a solution to mysql-server:amd64 9999
  Re-Instated mariadb-common:amd64
  Re-Instated mariadb-client-core-10.3:amd64
  Re-Instated mysql-client-core-8.0:amd64
  Re-Instated mysql-client-8.0:amd64
    Reinst Failed early because of mysql-server-core-8.0:amd64
  Considering mysql-server-8.0:amd64 1 as a solution to mysql-server:amd64 9999
Investigating (0) mariadb-client-core-10.3:amd64 < none -> 1:10.3.22-1ubuntu1 @un uN Ib >
Broken mariadb-client-core-10.3:amd64 Conflicts on mysql-client-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN >
  Considering mysql-client-8.0:amd64 0 as a solution to mariadb-client-core-10.3:amd64 0
  Holding Back mariadb-client-core-10.3:amd64 rather than change mysql-client-8.0:amd64
Investigating (0) mysql-client-core-8.0:amd64 < none -> 0.4+p20.04+git20200805.1207 @un uN Ib >
Broken mysql-client-core-8.0:amd64 Depends on mariadb-client-core-10.3:amd64 < none | 1:10.3.22-1ubuntu1 @un uH >
  Considering mariadb-client-core-10.3:amd64 0 as a solution to mysql-client-core-8.0:amd64 0
  Holding Back mysql-client-core-8.0:amd64 rather than change mariadb-client-core-10.3:amd64
Investigating (0) mysql-client-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-client-8.0:amd64 Depends on mysql-client-core-8.0:amd64 < none | 0.4+p20.04+git20200805.1207 @un uH >
  Considering mysql-client-core-8.0:amd64 0 as a solution to mysql-client-8.0:amd64 0
  Holding Back mysql-client-8.0:amd64 rather than change mysql-client-core-8.0:amd64
Investigating (1) mysql-server:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un puN Ib >
Broken mysql-server:amd64 Depends on mysql-server-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH >
  Considering mysql-server-8.0:amd64 1 as a solution to mysql-server:amd64 9999
  Considering mysql-server-8.0:amd64 1 as a solution to mysql-server:amd64 9999
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mysql-server : Depends: mysql-server-8.0 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

This is a fresh install

Thank you for all your hard work

Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.72.0
Qt Version: 5.14.2
Kernel Version: 5.4.0-42-generic
OS Type: 64-bit
Processors: 16 × Intel® Core™ i7-10875H CPU @ 2.30GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

have same problem, anyone will help ?

I had the same issue during an upgrade from 18.04 to 20.04. After some poking around, I found /etc/apt/preferences.d/50-neon-mariadb, which was pinning mysql:

Code: Select all

# SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
# SPDX-FileCopyrightText: 2020 Harald Sitter <sitter@kde.org>

# Pin our mysql dummy packages, akonadi breaks on mysql 8 in focal but
# the bionic -> focal upgrade has apt insisting on installing mysql
# (or uninstalling akonadi) so we make a dummy package.  If you want
# mysql you can remove this file but it'll break akonadi.

Package: mysql-client-core-8.0
Pin: origin "archive.neon.kde.org"
Pin-Priority: 1100
 
Package: mysql-server-core-8.0
Pin: origin "archive.neon.kde.org"
Pin-Priority: 1100

I don't use akonadi, so I:

1. commented out the contents of the file
2. ran:
   

   Code: Select all

   $ sudo sudo pkcon -c 1 refresh force
$ sudo pkcon update

3. mysql-server still failed on the post install, this fixed it (I'm not a pkcon expert):
   

   Code: Select all

   sudo apt install --fix-broken

Hope this helps. . .

It looks like the mysql server is corrupted by some update. I didn't get from Neon to look at Manjaro and here I see that he doesn't do anything at all with the mysql server connection. I don't know who screwed up, I just know that the whole local Ubuntu forum failed because the mysql was updated by the provider and the new version was incompatible.

dlb wrote:I had the same issue during an upgrade from 18.04 to 20.04. After some poking around, I found /etc/apt/preferences.d/50-neon-mariadb, which was pinning mysql:

Code: Select all

# SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
# SPDX-FileCopyrightText: 2020 Harald Sitter <sitter@kde.org>

# Pin our mysql dummy packages, akonadi breaks on mysql 8 in focal but
# the bionic -> focal upgrade has apt insisting on installing mysql
# (or uninstalling akonadi) so we make a dummy package.  If you want
# mysql you can remove this file but it'll break akonadi.

Package: mysql-client-core-8.0
Pin: origin "archive.neon.kde.org"
Pin-Priority: 1100
 
Package: mysql-server-core-8.0
Pin: origin "archive.neon.kde.org"
Pin-Priority: 1100

I don't use akonadi, so I:

1. commented out the contents of the file
2. ran:
   

   Code: Select all

   $ sudo sudo pkcon -c 1 refresh force
$ sudo pkcon update

3. mysql-server still failed on the post install, this fixed it (I'm not a pkcon expert):
   

   Code: Select all

   sudo apt install --fix-broken

Hope this helps. . .

Its work like a charm I can nnow install packages.

dlb wrote:I had the same issue during an upgrade from 18.04 to 20.04. After some poking around, I found /etc/apt/preferences.d/50-neon-mariadb, which was pinning mysql:

Code: Select all

# SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
# SPDX-FileCopyrightText: 2020 Harald Sitter <sitter@kde.org>

# Pin our mysql dummy packages, akonadi breaks on mysql 8 in focal but
# the bionic -> focal upgrade has apt insisting on installing mysql
# (or uninstalling akonadi) so we make a dummy package.  If you want
# mysql you can remove this file but it'll break akonadi.

Package: mysql-client-core-8.0
Pin: origin "archive.neon.kde.org"
Pin-Priority: 1100
 
Package: mysql-server-core-8.0
Pin: origin "archive.neon.kde.org"
Pin-Priority: 1100

I don't use akonadi, so I:

1. commented out the contents of the file
2. ran:
   

   Code: Select all

   $ sudo sudo pkcon -c 1 refresh force
$ sudo pkcon update

3. mysql-server still failed on the post install, this fixed it (I'm not a pkcon expert):
   

   Code: Select all

   sudo apt install --fix-broken

Hope this helps. . .

Followed the steps with no success. Still getting the same error message as before (same as OP), but now it starts directly by "investigating" mariadb-server for some reason I don't really get. Anybody got any ideas on how to fix this? I really cannot format right now, and I need mysql to be working on my machine pretty urgently...

Here's the log:

Code: Select all

sudo apt install mysql-server                                                                                                      ⏎
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) mariadb-server:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mR > (>= 1:10.3.22-1ubuntu1)
  Considering mariadb-server-10.3:amd64 -2 as a solution to mariadb-server:amd64 0
  Added mariadb-server-10.3:amd64 to the remove list
  Fixing mariadb-server:amd64 via keep of mariadb-server-10.3:amd64
Investigating (0) mysql-server-core-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-server-core-8.0:amd64 Conflicts on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
  Considering mariadb-server-10.3:amd64 -2 as a solution to mysql-server-core-8.0:amd64 0
  Added mariadb-server-10.3:amd64 to the remove list
  Fixing mysql-server-core-8.0:amd64 via remove of mariadb-server-10.3:amd64
Investigating (1) mariadb-server:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mR > (>= 1:10.3.22-1ubuntu1)
  Considering mariadb-server-10.3:amd64 -2 as a solution to mariadb-server:amd64 0
  Added mariadb-server-10.3:amd64 to the remove list
  Fixing mariadb-server:amd64 via keep of mariadb-server-10.3:amd64
Investigating (1) mysql-server-core-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-server-core-8.0:amd64 Conflicts on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
  Considering mariadb-server-10.3:amd64 -2 as a solution to mysql-server-core-8.0:amd64 0
  Added mariadb-server-10.3:amd64 to the remove list
  Fixing mysql-server-core-8.0:amd64 via remove of mariadb-server-10.3:amd64
Investigating (2) mariadb-server:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
Broken mariadb-server:amd64 Depends on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mR > (>= 1:10.3.22-1ubuntu1)
  Considering mariadb-server-10.3:amd64 -2 as a solution to mariadb-server:amd64 0
  Added mariadb-server-10.3:amd64 to the remove list
  Fixing mariadb-server:amd64 via keep of mariadb-server-10.3:amd64
Investigating (2) mysql-server-core-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-server-core-8.0:amd64 Conflicts on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
  Considering mariadb-server-10.3:amd64 0 as a solution to mysql-server-core-8.0:amd64 0
  Holding Back mysql-server-core-8.0:amd64 rather than change mariadb-server-10.3:amd64
Investigating (2) mysql-server-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-server-8.0:amd64 Depends on mysql-server-core-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH > (= 8.0.21-0ubuntu0.20.04.4)
  Considering mysql-server-core-8.0:amd64 0 as a solution to mysql-server-8.0:amd64 0
  Holding Back mysql-server-8.0:amd64 rather than change mysql-server-core-8.0:amd64
Investigating (2) mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
Broken mariadb-server-10.3:amd64 Depends on mariadb-client-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mR > (>= 1:10.3.22-1ubuntu1)
  Considering mariadb-client-10.3:amd64 -2 as a solution to mariadb-server-10.3:amd64 0
  Added mariadb-client-10.3:amd64 to the remove list
Broken mariadb-server-10.3:amd64 Depends on mariadb-server-core-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mR > (>= 1:10.3.22-1ubuntu1)
  Considering mariadb-server-core-10.3:amd64 -1 as a solution to mariadb-server-10.3:amd64 0
  Added mariadb-server-core-10.3:amd64 to the remove list
  Fixing mariadb-server-10.3:amd64 via keep of mariadb-client-10.3:amd64
  Fixing mariadb-server-10.3:amd64 via keep of mariadb-server-core-10.3:amd64
Investigating (3) mysql-server:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un puN Ib >
Broken mysql-server:amd64 Depends on mysql-server-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH >
  Considering mysql-server-8.0:amd64 0 as a solution to mysql-server:amd64 9999
  Re-Instated mysql-server-core-8.0:amd64
  Re-Instated mysql-server-8.0:amd64
Investigating (3) mysql-client-core-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-client-core-8.0:amd64 Conflicts on mariadb-client-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
  Considering mariadb-client-10.3:amd64 0 as a solution to mysql-client-core-8.0:amd64 0
  Holding Back mysql-client-core-8.0:amd64 rather than change mariadb-client-10.3:amd64
Investigating (3) mysql-server-core-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-server-core-8.0:amd64 Conflicts on mariadb-server-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
  Considering mariadb-server-10.3:amd64 0 as a solution to mysql-server-core-8.0:amd64 0
  Holding Back mysql-server-core-8.0:amd64 rather than change mariadb-server-10.3:amd64
Investigating (3) mysql-client-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-client-8.0:amd64 Depends on mysql-client-core-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH >
  Considering mysql-client-core-8.0:amd64 0 as a solution to mysql-client-8.0:amd64 0
  Holding Back mysql-client-8.0:amd64 rather than change mysql-client-core-8.0:amd64
Investigating (3) mysql-server-8.0:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un uN Ib >
Broken mysql-server-8.0:amd64 Depends on mysql-client-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH > (>= 8.0.21-0ubuntu0.20.04.4)
  Considering mysql-client-8.0:amd64 0 as a solution to mysql-server-8.0:amd64 0
  Holding Back mysql-server-8.0:amd64 rather than change mysql-client-8.0:amd64
Investigating (3) mariadb-client-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mK Ib >
Broken mariadb-client-10.3:amd64 Depends on mariadb-client-core-10.3:amd64 < 1:10.3.22-1ubuntu1 @ii mR > (>= 1:10.3.22-1ubuntu1)
  Considering mariadb-client-core-10.3:amd64 -1 as a solution to mariadb-client-10.3:amd64 0
  Added mariadb-client-core-10.3:amd64 to the remove list
  Fixing mariadb-client-10.3:amd64 via keep of mariadb-client-core-10.3:amd64
Investigating (4) mysql-server:amd64 < none -> 8.0.21-0ubuntu0.20.04.4 @un puN Ib >
Broken mysql-server:amd64 Depends on mysql-server-8.0:amd64 < none | 8.0.21-0ubuntu0.20.04.4 @un uH >
  Considering mysql-server-8.0:amd64 0 as a solution to mysql-server:amd64 9999
  Considering mysql-server-8.0:amd64 0 as a solution to mysql-server:amd64 9999
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mysql-server : Depends: mysql-server-8.0 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


EDIT, UPDATE:
I've been able to install mysql-server now by trying to specify a version (I tried and failed before), with

Code: Select all

sudo apt install mysql-server-8.0

Now the issue is:

Code: Select all

mysql -u ***** -p                                                                         
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)


which brings me to:

Code: Select all

sudo service mysql start                                                                                                           
Failed to start mysql.service: Unit mysql.service not found.

which looks strange, since mysql looks registered properly as a service:

Code: Select all

sudo service --status-all                                                                                                     

....
 [ - ]  mysql
....


EDIT:
Found some unexpected mariadb leftovers (the 20.04 rebase seems to have installed some maria stuff), so removed each one with

Code: Select all

sudo apt remove --purge *****

Now the service gets found, but still doesn't want to start:

Code: Select all

sudo service mysql start     
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.

and the logs seem to be:

Code: Select all

-- A start job for unit mysql.service has begun execution.
--
-- The job identifier is 3106.
ago 26 11:47:02 pc systemd[6802]: mysql.service: Failed to determine user credentials: No such process
ago 26 11:47:02 pc systemd[6802]: mysql.service: Failed at step USER spawning /usr/share/mysql/mysql-systemd-start: No such process
-- Subject: Process /usr/share/mysql/mysql-systemd-start could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /usr/share/mysql/mysql-systemd-start could not be executed and failed.


Basically I've tried everything I could. I completely removed everything mysql (and maria, ofc) related and reinstalled everything from ground up. Now installing with a simple "apt install mysql-server" works, but it's like the installation doesn't properly configure the system to work with mysql. I keep getting errors such as "ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)" and the mysql server cannot seem to be started for some reason. I'm literally out of ideas.

did you try removing mariadb-server?