Versions Compared

Old Version 11

changes.mady.by.user Daniel Ali

Saved on

compared with

New Version Current

changes.mady.by.user Daniel Ali

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Open seahorse:
    1. seahorse &
  2. Check if you have a "login" keyring in the left pane
  3. If you can see it:
    1. Close seahorse
    2. Relaunch the keyring daemon:
      1. gnome-keyring-daemon -r
    3. Open seahorse again
  4. Try to unlock your "login" keyring. Right-click over "login", then "unlock"
  5. Try your login password first, other old passwords if it doesn't work
  6. If you managed to unlock it using your username and password, and you want to sync its password with your ECMWF one, change it: Right-click, "change password"
  7. Otherwise (you couldn't find the right password that would unlock your keyring):
    1. Delete the keyring. Right-click, "delete"
    2. Go back to step 3

MySQL Workbench crashes when trying to connect directly to a MySQL / MariaDB database

This error, accompanied by a long backtrace that doesn't help very much, can be caused by:

  • Wrong credentials
  • Port 3306 not reachable (try to telnet to the destination using this port, see if the connection can be established). If this is the case, issue a ticket to NETSEC detailing the source and destination networks (all VDI to <SUBNET>:3306)
  • Database with incompatible features. This is the most likely cause for this error. If you try to connect directly, it will crash. This is the solution:
    Go to Database -> Manage Connections
    New -> Enter the connection details

Click "test connection". It will show a warning if you are connecting to an incompatible version. Carry on.

If your credentials are OK, the port 3306 is open in the destination host, and the given user is set to connect from any host, then a success message will appear.

From now on, mysql-workbench shouldn’t crash.

Possible explanation: It seems that connecting directly to an incompatible DB halts the application because it tries to expose full features to an incompatible DB and they forgot to capture this exception in their code.

However, after doing the above test, workbench identifies the limitations of the destination DB and then it can deal with them along the way.

Kate crashes when trying to configure it

A required configuration file doesn't exist. Kate fails to create a new one, the exception is not captured and it crashes.

Oddly enough, if you just open kate, resize its window and then go to "File - Exit", it generates that file, so the next time it's open it won't segfault when going to "Settings - Configure kate".