mirror of
https://github.com/absadiki/whatsapp-msgstore-viewer.git
synced 2026-04-27 04:45:57 +03:00
[GH-ISSUE #19] Feedback about my installation experience under Ubuntu 24.04.1 LTS (WSL2) #14
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whatsapp-msgstore-viewer#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nohir0 on GitHub (Aug 20, 2025).
Original GitHub issue: https://github.com/absadiki/whatsapp-msgstore-viewer/issues/19
Hi,
I want to share my installation experience on a typical Ubuntu system.
Ubuntu Version:
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
Running on Linux Subsystem (WSL2) for Windows 11
First of all, on above system Python 3.12.3 is installed as default.
I used pyenv to install latest 3.9.23 to solve the Kivy installation issues as proposed in issue:
https://github.com/absadiki/whatsapp-msgstore-viewer/issues/4
In a vitualenv running 3.9,23 I still faced following issues that prevented the app UI to start:
I could solve above installing:
Then following error appeared, since Ubuntu seems not to use ~/.config directory any more:
Simply solved by:
mkdir -p ~/.config/whatsappmsgstoreviewAfter that, the app started successfully and I could open my previously decrypted whatsapp backup.
Maybe this helps to fix some OS dependent issues...
It would be great if the app would offer an export to text files feature in the future ;)
Thanks for you efforts!
@absadiki commented on GitHub (Aug 21, 2025):
Hi @nohir0,
thanks a lot for sharing your installation experience and the workaround!
Once I get some time, I’ll add a fix so the config folder gets created automatically if it’s missing. In the meantime, I’ll reference this issue from the README in case someone runs into the same situation on a similar setup.
The export-to-text feature is a great suggestion, I’ll keep it in mind for a future update.
Really appreciate your feedback!