I am running in the same Linux distro two environments: Plasma (former KDE) and i3wm.

I use the same command on both environments: sudo systemctl start mysql.service && sudo mysql -u root -p -h localhost -P 3306, but while on KDE/Plasma I get no error, on i3wm I get a “the name is not activatable” error, and I don’t know how to fix it (here’s a screenshot).

Here’s an extract from MySQL Workbench:

04:32:53 [ERR][SQL Editor Form]: SQL editor could not be connected: The name is not activatable
04:32:53 [ERR][SQL Editor Form]: Your connection attempt failed for user 'root' to the MySQL server at 127.0.0.1:3306:
  The name is not activatable

Also, I found out firefox doesn’t connect to 127.0.0.1:3306 either on i3; on Plasma I get something like (“The connection has been restarted. The connection to the server was reset while the page was loading.”).

I find is interesting too, because syncthing can connects through the localhost on i3wm, but mariadbd can’t for some reason:

sudo lsof -n | grep TCP | grep LISTEN
[…]
syncthing   841 31843 syncthing          alberto  14u     IPv4              11863       0t0        TCP 127.0.0.1:8384 (LISTEN)
mariadbd   2537                            mysql  32u     IPv4              16382       0t0        TCP *:mysql (LISTEN)
  • Moshpirit@lemmy.worldOP
    1·
    8 months ago

    I see!

    I included it into the i3 config file (I saw that it was set up to execute gnome-toolkit (which isn’t installed)), but after changing it to KDE’s, it gets initialized when logging in, but it doesn’t seem to affect Workbench

    • jrgd@lemm.eeEnglish
      2·
      8 months ago

      Perhaps it is possible that multiple issues are involved? Looking back at other issues with SQL Workbench causing DBus failures due to missing DBus endpoints could include the fact that SQL Workbench seems to rely on a keyring (be it Gnome Keyring or KDE Wallet). In an issue posted from 2022, SQL Workbench outright fails to connect to DBs in the same manner described if the keyring application isn’t running. It might be worth using KWalletManager to check through your KDE keyring to see if SQL Workbench has been attempting to store and resolve database passwords through your keyring, which won’t be running by default in a plain i3 session.

      • Moshpirit@lemmy.worldOP
        1·
        8 months ago

        It worked!! Is there any way to solve this issue without depending on Kwallet? I’ll investigate for lightweight alternatives :)

        • jrgd@lemm.ee
          1·
          8 months ago

          As the original issues over on MySQL forums suggested, using DBeaver or other similar software rather than SQL Workbench is the best option. You unfortunately seem to be locked into using a keychain solution if you want to use SQL Workbench.