• Members 9 posts
    Dec. 19, 2018, 3:13 p.m.

    For several users the pEp mode isn't working anymore, as some already pointed out at the Enigmail Forum

    In my case this occurred one or two weeks ago. Before it was working without problems for several month. I already tried deactivating other plugins, reinstalling pEp-Engine and Enigmail - no success.

    Enigmail 2.0.9
    Thunderbird 60.3.0
    debian 9.6
    pEp JSON Adapter version 0.14.1 "(39) Gemünden". package_version="1.0.24"
    pEpEngine version 0.9.0

    I attached a (anonymized with XXXXX) logfile covering start, switching to forced pep mode and then sending the message (from 15:48:02)


    Text, 41.2 KB, uploaded by peri on Dec. 19, 2018.

  • Dec. 23, 2018, 7:01 p.m.

    Do you get any errors when starting the


    Indicates that the pep adapter isn't listening to calls

  • Members 9 posts
    Dec. 23, 2018, 11:49 p.m.
  • Dec. 25, 2018, 1:48 p.m.

    Does ~/.pEp.management.db exist? Might be corrupt or have the wrong permissions

  • Members 9 posts
    Dec. 26, 2018, 12:51 p.m.

    Yes, normal permissions (-rw-r--r--)
    I even renamed it and it was rebuild at restart. Also uninstalled pEp-Files and Enigmail and reinstalled everything again.

  • Members 9 posts
    Dec. 28, 2018, 9:35 a.m.

    Probably helpful: I discovered that on my laptop everything is running fine. It's the same system and the same versions and has the same or at least a very similar thunderbird profile (i copied it from my desktop some months ago). But I discovered some differences:
    1. pEp didn't generate a .pEp_management.db-shm and .pEp_management.db-wal on the defective desktop install
    2. Enigmail on the defective desktop has the normal long enigmail menu (Decrypt/Verify ... [12 other points] ... About Enigmail).
    On the working laptop it's the short Enigmail menu (key management and preferences)

    EDIT: Ok, I think that's not helpful, the file came from another software opening the database and the missing pEp menue seems to be a consequence from the pep service not running.

  • Members 9 posts
    Dec. 28, 2018, 10:37 a.m.

    It seems that the .pEp_management.db can't be generated anymore (even if I uninstall and reinstall enigmail and PEP completly). If I start pep-json-server manually, it is generated, but seems to be empty (4kb instead of 225kb on the working laptop install)

  • Members 9 posts
    March 7, 2019, 12:26 p.m.

    It seems that some weeks ago half of this forum thread got lost ... can you imagine how unprofessional this looks like from outside: You write a hotifx for a bug, which contains another bug and then the forum thread, in which a user reports and tracks down the bug gets lost on your server, while the bug still isn't fixed.

    This is disappointing.

  • March 7, 2019, 2:05 p.m.

    I understand your frustration. There was a DB issue and we had to choose between deleting new content and loosing a bit of old content.
    Neither of which is perfect.

  • Members 9 posts
    April 22, 2019, 5:33 p.m.

    Are you aware that this bug is still unfixed and me and probably several other users have to manually delete the backup files (gpg-agent.conf.0.pep.bkp and gpg.conf.0.pep.bkp) every some weeks manually in order to still use your tool?

    I found out what the problem was and you weren't able to fix it in 3 months??? While the problem is just a crazy backup-routine which stops after 98, because it never was intended to run wild like that???

    I'm out. I've done a lot to spread word about your approach, but now I will not use it anymore and advise all people in the GDPR and security sector to stop using it, because the way you work is unreliable and unstable. Sorry!

    P.S.: I wasn't able to comment anymore under the original thread. Is there even something which is working here???

  • call_merge

    The Bug still unfixed. Was: Send button of emails not working anymore in pEp mode thread has been merged into this thread.

  • April 23, 2019, 7:11 p.m.

    So far i am not aware of any problems with answering your own topics. I merged it into the old thread to keep everything together.