Password Management Error

Help
,
#54

OK this is what the :man_facepalming: emoji is for. I didn’t realize there were two sections of the .desktop file, I was editing the Exec for [Desktop Action NewMessage] not [Desktop Entry]. Now working fine

2 Likes
#56

The way I solve this issue.

  1. Delete any previous auto-start entry of Mailspring from System Settings and/or from ~/.config/autostart directory.
  2. I do not prefer flatpak or snap. I use the .deb file, downloaded from official website.
  3. After install, do not run/launch the app.
  4. Locate Mailspring.desktop file in /usr/share/applications/ directory and open it in text editor.
  5. In [Desktop Entry] section, not [Desktop Action NewMessage],
    replace this line
    Exec=mailspring %U
    with
    Exec=mailspring --password-store="gnome-libsecret" %U
  6. Save the file & now run mailspring.

Everything should work as expected.

2 Likes
#57

This works for me now!

I copied Mailspring-folder in username/.config into a backup folder and installed a new Linux distribution. After copying the folder back into the new distribution, I got this error message when starting Mailspring for the first time. Now I’m able to use Mailspring again. Thanks! :+1:

1 Like
#58

I think it is broken with the KDE 6 update and shows this error. Not sure who’s fault it is. I’ve seen other people mention this so it shouldn’t be a me problem…

#59

I have also recieved this issue upon updating to KDE 6, the “libsecret” fix won’t give me temporary repireve as well…

#60

Same issue here after upgrading to KDE6 on Arch Linux, also took the opportunity to finally move from X11 to Wayland, though that should be N/A? Any bandaids? Totally locked out :frowning: @Phylu

Moving into it’s own issue thread saw was created the other day, anyone with this issue should shimmy over here and vote:

@1nikolas @Quanthum

Unable to add accounts, login, anything after fedora 40 kde update
#61

That sounds like there was a switch from wallet5 to kwallet6 in the background. So your Mailspring is not able to access it’s encryption key for the passwords anymore. See: safeStorage | Electron

I’d assume that removing all mail accounts, logging out of your mailspring id and then logging in to everything again should work.

#62

Another reason could be that the electron version shipped with Mailspring does not yet contain the bindings for kwallet6. In that case you could try to Ensure that kwallet5 is installed an force it’s usage with the corresponding flag in the desktop file.

I am currently traveling, but will try to figure out a solution when I am back.

1 Like
#63

I finally found a solution with KDE 6 that solved the problem for me.

  1. In the Application Launcher, search for Mailspring.
  2. Right click on it and select “Edit Application…”
  3. Navigate to the “Application” tab.
  4. Update the “Arguments” field to read '--password-store=gnome-libsecret %U'
  5. Click “OK” at the bottom and close the menu.

Hope this helps anyone else encountering this issue in KDE 6.

3 Likes
Mailspring keeps asking for login
e-mail password problem
#64

Thanks, mate. This worked good in Arch Linux KDE Plasma 6 and have been able to setup my Mailspring accounts at last.

#65

Unfortunately no success here: Tumbleweed KDE 20240329, KDE Plasma 6.0.3, KDE Framework 6.0.0, QT: 6.6.3, Kernel 6.8.1, Graphics: Wayland
But thanks anyway :slight_smile:

#66

Hi there,

KDE Plasma 6 is out for a while now. But still I can’t use Mailspring, because it cannot load my PW from my keychain. As I mentioned in my former post, editing the application as Tom Gariepy suggests, didn’t work for me. For now I am using Kmail instead, but let’s say the user experience is not as … smooth as with Mailspring. Will there be a fix for the PW-issue?

#67

Same issue here on Fedora 40 Kionite

#68

Same issue, kde6. none of this worked. Seems like it doesn’t get to the point during installation that any of these files exist to be edited. thunderbird installed with no issues. Guess I’m using that now.

#69

@Xzygy @l-zacarias @avwasser @NickOChile @tommygee @F1nny @Quanthum @1nikolas

I am sorry for the delay, but I finally got a Fedora 40 KDE running for me and was able to find a workaround that actually worked smoothly for me. Please try to use kwallet5 as the backend store for the password encryption. I have documented this here: Password Management Error - #2 by system

Please let me know if this solves the issue for you.

1 Like
#70

works now without any parameters. Something got fixed along the way

1 Like
#71

Many thanks, Phylu. Two quite simple steps and Mailspring is running as smooth as before :slight_smile:

#72

Rejoiced too soon.
After a reboot the solution no longer works. I have to reconnect to my Mailspring account every time. Sometimes this works, sometimes not. Starting Mailspring via command line always seems to work - at least until the next reboot.
By the way, Yast tells me that kwallet5 is not installed on my system. Trying to install it would result in practically all Plasma 6 upgrades being undone. I have therefore refrained from attempting to install it.

#73

Here’s how I got Mailspring working:

  1. I am on Arch Linux.
  2. I installed the Mailspring Flatpak from Flathub.
  3. I saw it wasn’t working and tried the --password-store="kwallet5" steps but without initial success.
  4. I then tried, in the KDE Plasma Flatpak settings (included in the flatpak-kcm package), adding the following permissions, adding the following Session Bus Policies:
    • org.kde.kwalletd5: talk
    • org.kde.kwalletd6: talk
  5. Note: you can also use Flatseal to do step 4 if you’re on a different DE like GNOME.
  6. I then edited the Application entry in the Plasma Menu using Plasma’s Menu Editor and adding the
  7. Finally, I ran Mailspring from the Applications Menu in Plasma and volla, it works that way or if you run it from the command-line with flatpak run com.getmailspring.Mailspring --password-store="kwallet5"!
2 Likes
#74

@cameronbosch said:

Here’s how I got Mailspring working:

Thank you! It was enough to just do step 4 on Fedora 39 KDE 5.x.