search

TelegramOfficial / Support

Telegram Support
https://telegram.org
3 stars 0 forks source link

FATAL: Could not move logging to '/home/me/.var/app/org.telegram.desktop/data/TelegramDesktop/log.txt'! #3

Closed yhilgjff closed 2 months ago

yhilgjff commented 4 months ago

Following this last update, I am now incapable of opening Telegram on my Linux desktop with the following error on start:

[2024.07.12 08:12:09] Launched version: 5002003, install beta: [FALSE], alpha: 0, debug mode: [FALSE] [2024.07.12 08:12:09] Executable dir: /app/bin/, name: telegram-desktop [2024.07.12 08:12:09] Initial working dir: /home/me/ [2024.07.12 08:12:09] Working dir: /home/me/.var/app/org.telegram.desktop/data/TelegramDesktop/ [2024.07.12 08:12:09] Command line: /app/bin/telegram-desktop [2024.07.12 08:12:09] Executable path before check: /app/bin/telegram-desktop [2024.07.12 08:12:09] Logs started [2024.07.12 08:12:09] App ID: org.telegram.desktop [2024.07.12 08:12:09] Connecting local socket to 86ac9ddf30817fd6f2d48631f3236773-TelegramDesktop... [2024.07.12 08:12:09] Socket connect error 0, starting server and app... [2024.07.12 08:12:09] Could not copy '/home/me/.var/app/org.telegram.desktop/data/TelegramDesktop/log_start1.txt' to '/home/me/.var/app/org.telegram.desktop/data/TelegramDesktop/log.txt' to start new logging: Cannot create /home/me/.var/app/org.telegram.desktop/data/TelegramDesktop/log.txt for output: No such file or directory [2024.07.12 08:12:09] Executable path before check: /app/bin/telegram-desktop [2024.07.12 08:12:09] FATAL: Could not move logging to '/home/me/.var/app/org.telegram.desktop/data/TelegramDesktop/log.txt'!

The application works fine on Android.

Uninstalling via FlatPak and reinstalling did not fixed the issue.

$ uname -a
Linux MYBOX 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun  7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
$
suhaibkn commented 4 months ago

I had the same issue. I switched to the snap version and that fixed the issue for me.

yhilgjff commented 4 months ago

I had the same issue. I switched to the snap version and that fixed the issue for me.

Thanks for your reply. One of the first thing I do when deploying Ubuntu is getting rid of snapd. Therefore this solution will not work out for me.

Also, when I tried syncing my device via the downloaded standalone app from the website, it gives me an authentication token error.

yhilgjff commented 3 months ago

After several updates on both the Android side and Flatpak side, this problem is still happening but without giving the same problem.

This time the Flatpak interface loads but is incapable to synchronize via QR with the Android account.

yhilgjff commented 3 months ago

Android app says: desktop device is linked while the desktop device remains at the QR code and never logs in.

yhilgjff commented 2 months ago

As of today this has officially been fixed.