I'm running Linux Mint (Ubuntu) and have recently installed KeePassX to keep track of my passwords.
But I can't make it work with Firefox....

I have made an entry with the following information:

Title: <title from the webpage>
Username: <e-mail used when logging in>
URL: <URL pointing to the page with the login form>
Password: <password>
Repeat: <the same password once again>
Comment:

Auto-Type: {USERNAME}{TAB}{PASSWORD}{ENTER}
Auto-Type-Window: <Windows title>

I have started the KeePassX application and logged in using the master password I have created for the database.
When I open Firefox and access the login page nothing happens.

(KeePassX is NOT compatible with KeeFox so I have removed that plugin from the Firefox plugins..)

Do I need to reset/disable the password database in Firefox ?
If so: How do I do that ?

Thanx for any help!

Dani AI

Generated

Short summary tied to the original posts: reported KeePassX’s Auto‑Type not triggering in Firefox (then noted they switched to KeePass2). KeePassX has no plugin API, so browser addons that expect a KeePass RPC backend (the Kee/KeeFox style workflow) cannot connect to it. KeePassX FAQ · Kee (KeeFox) overview / KeePassRPC. (keepassx.org)

Practical Auto‑Type troubleshooting (when using a standalone client): Auto‑Type matches the active window title (or an entry-specific window pattern), and is triggered either by the entry-level action or the global hotkey. Common failures come from a mismatched window pattern, the DB being locked, the text cursor not being in the correct field, or the hotkey being intercepted. Ensure entries use window-title patterns/wildcards that actually appear in the Firefox window title and that the database is unlocked before invoking Auto‑Type. [KeePass Auto‑Type docs (concepts & wildcards)]. (documentation.help)

Wayland / modern Linux caveat: many Linux desktops now run Wayland and block synthetic global input; KeePassXC (the actively maintained successor to KeePassX) documents that Auto‑Type is disabled under a Wayland compositor unless the app is forced to use X11 compatibility (for example via QT_QPA_PLATFORM=xcb or launching with -platform xcb). For reliable browser filling on current desktops, prefer a native browser integration instead of Auto‑Type. (keepassxc.org)

Recommended, more robust workflows (today): move to KeePassXC and use the official KeePassXC‑Browser extension (native pairing / autofill), or run KeePass2 with the Kee + KeePassRPC plugin if an RPC flow is required — both are different workflows from Auto‑Type. Firefox’s built‑in saved‑logins are independent and do not need to be “reset” to use external solutions. [KeePassXC docs] · [KeePassXC‑Browser repo] · [Firefox saved logins / Primary Password]. (keepassxc.org)

Cautions: Auto‑Type can accidentally input credentials into the wrong window and is affected by desktop compositor and packaging (Flatpak/Snap) choices. For long‑term reliability on modern Linux, browser integration is the preferred solution.

Obsolete. I'm using KeePass2 instead.. :-)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.