Open ghost opened 8 years ago
Same here: Arch, KDE Plasma 5
Same issue on Archlinux with GNOME. Only on PC reboot, not when restarting only gdm. Never had this problem on Debian and Windows machines.
Same on Ubuntu 14.04, every time I quit Cutegram (no need to log out). Downloaded from http://aseman.co/downloads/cutegram/2/cutegram_2.7.1-1-amd64.deb
On Gentoo though it's only on GDM restart.
+1 Arch (installed from official repo) KDE Plasma 5
This bug does not seems to be present on the OSX release.
Tested on an old MacBook late 2007 running OSX 10.6.8 Snow Leopard x64. After restarting Cutegram and rebooting the whole system the Telegram session were maintained.
I am the maintainer of cutegram package in Arch Linux [community] repo. I myself cannot reproduce this problem on all my devices (2 laptops and 1 desktop, running 3 Arch Linux and 1 OS X), but one of my friends said to me the same problem. He is using a VPN (actually a shadowsocks tunnel) when connecting to telegram (because he lives in mainland China). We didn't track down to whether using a vpn is related to this issue.
I know Archlinux behaves sometimes strange when it comes to maintain/reopen tcp sockets. Might this behaviour be connected to a breaking connection to the server? This would also explain VPN issues.
I have not found how to debug cutegram. Is there some env variable to be set?
I'm getting this too, on a pretty much clean install of Manjaro KDE on my laptop. No VPNs or anything odd. Has been working ok over the last few days while I've been been distro-hopping (Xfce and Gnome).
I having the same probloem in Debian Testing (strecht) (Sparky-linux Mate flavor). Maybe a missing recommended dependence? Which one recommend to be installed?
I have the same problem but it appeared only after I logged out manually once. I was using cutegram for month without that problem. I'm from Europe and I'm directly connecte no VPN tunnels or something like that. Btw. I'm also on Arch with Plasma 5 and it happens with the latest git build and the stable package.
I am using Arch with gnome and have the same problem. (By the way i think this is the same bug as #24)
If you want i can post a log created with cutegram --verbose --visible
but i am not sure if there are private information in this log.
Edit: I also remove the old config (~/.config/Cutegram/) and start with a fresh one. The same problem
Same problem here: Arch + gnome.
I could experiment a bit with my VPN to see if that has any effect. Will report back.
Same here with manjaro linux, cutegram from extra repository. VPN enable or disable didnt make a difference.
It seems the project is dead, the last commit is more then three month old. Commits on Jan 17, 2016. I tried to look into it but couldn't figure out the bug. Too bad I really hate the dependencies of the official telegram app.
You could also just install the Pidgin plugin. That's what I ended up doing.
Am 28. April 2016 12:42:55 MESZ, schrieb "Alexander Görtz" notifications@github.com:
It seems the project is dead, the last commit is more then three month old. Commits on Jan 17, 2016. I tried to look into it but couldn't figure out the bug. Too bad I really hate the dependencies of the official telegram app.
You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/Aseman-Land/Cutegram/issues/199#issuecomment-215383842
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi The project is not dead. We're working hard to release Cutegram 3.0. Cutegram 3.0 is redesigned and include many new features and improvments. Sorry. We're busy these days. We planned to release first alpha version in the next weeks.
@realbardia Hi, any news on this?
Maybe interesting to mention explicitly, that while I am affected by this issue in cutegram, if I run another client I don't have any problems. (tested with the libpurple plugin/pidgin)
Cutegram 3.0 alpha released #227
I have the same issue on Debian Jessie 32-bit with Gnome 3.14.1. I just renewed the profile in ~/.config/Cutegram, but nothing changed. I also cannot close Cutegram correct, there is no "close"-button for it. I need to push the "X" top right and then kill the process. Should be any button on my desktop?
Hello.
Every time I restart Cutegram (e.g. after PC restart), I'm asked to enter a "login code" sent to my phone.
Is this behavior intended? Is there a way to maintain the session always open on my computer?
The code always arrives in timely manner but would be awesome not having to input every time the program starts.
Happening on Ubuntu 15.10 x64