doesn't survive a restart?

[uslacker99]

The plugin seems to work when I add the account for the first time, but when I kill pidgin and restart it, it will not log back into WhatsApp. Is this a known issue? If it helps at all, I'm using Ubuntu 22.04 with the nightly built binary on Pidgin 2.14.8.

[hoehermann]

Thank you for the report. This is not a known issue and certainly not intended behaviour. Unfortunately, I cannot reproduce the problem. Is there an error message? Can you start pidgin -d and send me the logs via eMail to [email protected]?

Please note that the WhatsApp credentials are stored in the purple home directory, but in a non-standard location which might be blocked by security mechanisms such as AppArmor. In the debug log, there should be a line like whatsmeow: [Database] sqlite3 connecting to file:/home/username/.purple/whatsmeow.db?_foreign_keys=on&_busy_timeout=3000.

[uslacker99]

Thanks! Emailed you the outputs. I tried disabling AppArmor and it didn't change the result.

…

On Wed, Nov 29, 2023 at 4:00 AM Hermann Höhne ***@***.***> wrote: Thank you for the report. This is not a known issue and certainly not intended behaviour. Unfortunately, I cannot reproduce the problem. Is there an error message? Can you start pidgin -d and send me the logs via eMail to ***@***.***? Please note that the WhatsApp credentials are stored in the purple home directory, but in a non-standard location which might be blocked by security mechanisms such as AppArmor. In the debug log, there should be a line like whatsmeow: [Database] sqlite3 connecting to file:/home/username/.purple/whatsmeow.db?_foreign_keys=on&_busy_timeout=3000 . — Reply to this email directly, view it on GitHub <#180 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOMLZILZZF35VCWN22LADDYG4PUPAVCNFSM6AAAAAA76QVXG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZRG43DANZYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hoehermann]

Thank you for the information and the message exchange we had in private. Unfortunately the debug information are not insightful. This issue will remain unresolved for now. Dear other users: In case this issue affects you, too, please leave a comment here.