Description of problem:I can't connect to my Telegram account from Pidgin with the tdlib protocol. On the official website they show this link to "Modern Telegram", which I see is not the same source that we have in Mageia. This is the source from official website: https://github.com/BenWiederhake/tdlib-purple/#readme This is the source from our spec: https://github.com/ars3niy/tdlib-purple/ You may need an update to the source of official website. Version-Release number of selected component (if applicable): Pidgin with purple-telegram-tdlib protocol. How reproducible: Install Pidgin with tdlib-telegram protocol and create Telegram account. Steps to Reproduce: 1. Install Pidgin and tdlib-telegram protocol. 2. Create Telegram account and connect. 3. Appears a warning "Authetication error: code 406 (UPDATE_APP_TO_LOGIN)
When you carfully read the github description, you will see that Mageia uses the original source. BenWiederkake is the fork.
Well something don't work with this version now....
It may be that the source is the original. But in this case, the last commit in the original source is from 3 years ago... And the last commit in the fork is from 3 days ago... There is a bug reported on Upstream in the original source, where it is recommended to upgrade tdlib to version 1.8.34. Maybe that's what we need.
Here the report: https://github.com/ars3niy/tdlib-purple/issues/185
As I see that both forks: - https://github.com/BenWiederhake/tdlib-purple - https://github.com/667bdrm/tdlib-purple (this is the one recommended to update in the upstream report). They are currently on version 1.8.35, so I think we should update to one of them. Preferably the one indicated on the official Pidgin site.
We need to be sure what to update; these are tdlib-related packages: pidgin-telegram-tdlib purple-telegram-tdlib and none for 'tdlib' per se. Both pkgs are from SRPM 'purple-telegram-tdlib'. Exactly what package/SRPM is being debated here? Our pidgin is 2.14.12, our pidgin-telegram-tdlib 0.8.1.
Source RPM: Pidgin - tdlib - Telegram => purple-telegram-tdlib-0.8.1-1.mga9.src.rpm
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #6) > We need to be sure what to update; these are tdlib-related packages: > pidgin-telegram-tdlib > purple-telegram-tdlib > and none for 'tdlib' per se. Both pkgs are from SRPM > 'purple-telegram-tdlib'. > > Exactly what package/SRPM is being debated here? > Our pidgin is 2.14.12, our pidgin-telegram-tdlib 0.8.1. pidgin-telegram-tdlib & purple-telegram-tdlib are generated by the same src.rpm and tdlib by tdlib-1.8.0-2.mga9, the complex thing is in tdlib as, the suggested fix points to yet other fork!
Looking deep in this We need https://github.com/tdlib/td/tree/8d08b34e22a08e58db8341839c4e18ee06c516c5 that is 1.8.35 version of the lib And https://github.com/BenWiederhake/tdlib-purple/tree/43e6cc2f14ccd08171b1515f6216f4bbf84eed80
Source RPM: purple-telegram-tdlib-0.8.1-1.mga9.src.rpm => purple-telegram-tdlib,tdlib
That's what I wanted to say, Katnatek has made it clear.
This is baffling me. The only package references to tdlib are: purple-telegram-tdlib pidgin-telegram-tdlib and this: $ urpmf tdlib | grep -v stdlib | grep -v Stdlib returns only 'purple-telegram-tdlib'. $ urpmq --requires-recursive pidgin-telegram-tdlib | grep tdlib lib64python3.10-stdlib purple-telegram-tdlib $ urpmq --requires-recursive purple-telegram-tdlib | grep tdlib lib64python3.10-stdlib I can find nothing which hangs on 'tdlib' SRPM - which *is* in Cauldron, version not evident but reported above tdlib-1.8.0-2.mga9. But thanks to Katnatek, we can forward this - to DavidG, who put up both tdlib and purple-telegram-tdlib SRPMs.
Assignee: bugsquad => geiger.david68210CC: lewyssmith => (none)
(In reply to Lewis Smith from comment #10) > This is baffling me. The only package references to tdlib are: > purple-telegram-tdlib > pidgin-telegram-tdlib > and this: > $ urpmf tdlib | grep -v stdlib | grep -v Stdlib > returns only 'purple-telegram-tdlib'. > > $ urpmq --requires-recursive pidgin-telegram-tdlib | grep tdlib > lib64python3.10-stdlib > purple-telegram-tdlib > $ urpmq --requires-recursive purple-telegram-tdlib | grep tdlib > lib64python3.10-stdlib > > I can find nothing which hangs on 'tdlib' SRPM - which *is* in Cauldron, > version not evident but reported above tdlib-1.8.0-2.mga9. > > But thanks to Katnatek, we can forward this - to DavidG, who put up both > tdlib and purple-telegram-tdlib SRPMs. The binary packages are not evident lib64td-devel-1.8.0-2.mga9.x86_64.rpm Development package for tdlib lib64td-static-devel-1.8.0-2.mga9.x86_64.rpm Static library for developing static programs that use tdlib lib64tdapi1.8.0-1.8.0-2.mga9.x86_64.rpm Cross-platform library for building Telegram clients lib64tdclient1.8.0-1.8.0-2.mga9.x86_64.rpm Cross-platform library for building Telegram clients lib64tdjson1.8.0-1.8.0-2.mga9.x86_64.rpm Cross-platform library for building Telegram clients
CC: (none) => ngompa13
Created attachment 14658 [details] Diff from tdlib spec in cauldron Use the recommended tdlib commit , build with success for mageia 9 and cauldron
Created attachment 14659 [details] Diff from purple-telegram-tdlib spec in cauldron Build against tdlib 1.8.35 commit in mageia 9 and cauldron
Remove all information about the account in ~/.purple Confirm the bug Close pidgin Update to builded packages LC_ALL=C urpmi --auto --auto-update --force updated medium "QA Testing (64-bit)" medium "Core Release (distrib1)" is up-to-date medium "Core Updates (distrib3)" is up-to-date medium "Nonfree Release (distrib11)" is up-to-date medium "Nonfree Updates (distrib13)" is up-to-date medium "Tainted Release (distrib21)" is up-to-date medium "Tainted Updates (distrib23)" is up-to-date medium "Core 32bit Release (distrib31)" is up-to-date medium "Core 32bit Updates (distrib32)" is up-to-date medium "Nonfree 32bit Release (distrib36)" is up-to-date medium "Tainted 32bit Release (distrib41)" is up-to-date medium "Tainted 32bit Updates (distrib42)" is up-to-date medium "BDK-Free-x86_64" is up-to-date medium "BDK-Free-noarch" is up-to-date medium "BDK-NonFree-x86_64" is up-to-date installing lib64tdclient1.8.35-1.8.35-1.20240813git8d08b34.mga9.x86_64.rpm lib64tdapi1.8.35-1.8.35-1.20240813git8d08b34.mga9.x86_64.rpm purple-telegram-tdlib-0.8.1-2.20240907git43e6cc2.mga9.x86_64.rpm pidgin-telegram-tdlib-0.8.1-2.20240907git43e6cc2.mga9.noarch.rpm from //home/katnatek/qa-testing/x86_64 Preparing... ################################################################################################## warning: lib64tdapi1.8.35-1.8.35-1.20240813git8d08b34.mga9.x86_64: Header V4 RSA/SHA256 Signature, key ID a1281639: NOKEY 1/4: lib64tdapi1.8.35 ################################################################################################## 2/4: lib64tdclient1.8.35 ################################################################################################## 3/4: purple-telegram-tdlib ################################################################################################## 4/4: pidgin-telegram-tdlib ################################################################################################## 1/2: removing pidgin-telegram-tdlib-0.8.1-1.mga9.noarch ################################################################################################## 2/2: removing purple-telegram-tdlib-0.8.1-1.mga9.x86_64 ################################################################################################## Start pidgin Now I can activate the telegram account
Created attachment 14660 [details] Obsolete previous libs @David in this version I obsolete the previous libraries, I let to your decision what version to use, but I not like to keep both version in the system
(In reply to katnatek from comment #15) > Created attachment 14660 [details] > Obsolete previous libs > > @David in this version I obsolete the previous libraries, I let to your > decision what version to use, but I not like to keep both version in the > system The changes work as expected LC_ALL=C urpmi --auto --auto-update --force updated medium "QA Testing (64-bit)" medium "Core Release (distrib1)" is up-to-date medium "Core Updates (distrib3)" is up-to-date medium "Nonfree Release (distrib11)" is up-to-date medium "Nonfree Updates (distrib13)" is up-to-date medium "Tainted Release (distrib21)" is up-to-date medium "Tainted Updates (distrib23)" is up-to-date medium "Core 32bit Release (distrib31)" is up-to-date medium "Core 32bit Updates (distrib32)" is up-to-date medium "Nonfree 32bit Release (distrib36)" is up-to-date medium "Tainted 32bit Release (distrib41)" is up-to-date medium "Tainted 32bit Updates (distrib42)" is up-to-date installing lib64tdapi1.8.35-1.8.35-1.20240813git8d08b34.mga9.x86_64.rpm pidgin-telegram-tdlib-0.8.1-2.20240907git43e6cc2.mga9.noarch.rpm lib64tdclient1.8.35-1.8.35-1.20240813git8d08b34.mga9.x86_64.rpm purple-telegram-tdlib-0.8.1-2.20240907git43e6cc2.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64 Preparing... ################################################################################################## warning: lib64tdapi1.8.35-1.8.35-1.20240813git8d08b34.mga9.x86_64: Header V4 RSA/SHA256 Signature, key ID a1281639: NOKEY 1/4: lib64tdapi1.8.35 ################################################################################################## 2/4: lib64tdclient1.8.35 ################################################################################################## 3/4: purple-telegram-tdlib ################################################################################################## 4/4: pidgin-telegram-tdlib ################################################################################################## 1/4: removing pidgin-telegram-tdlib-0.8.1-1.mga9.noarch ################################################################################################## 2/4: removing purple-telegram-tdlib-0.8.1-1.mga9.x86_64 ################################################################################################## removing package lib64tdclient1.8.0-1.8.0-2.mga9.x86_64 3/4: removing lib64tdclient1.8.0-1.8.0-2.mga9.x86_64 ################################################################################################## removing package lib64tdapi1.8.0-1.8.0-2.mga9.x86_64 4/4: removing lib64tdapi1.8.0-1.8.0-2.mga9.x86_64 ##################################################################################################
Fixed both mga9 and Cauldron! Assigning to QA, Packages in 9/Core/Updates_testing: ====================== pidgin-telegram-tdlib-0.8.1-2.git20240907.mga9.noarch.rpm purple-telegram-tdlib-0.8.1-2.git20240907.mga9 libtd-devel-1.8.35-1.git20240813.mga9 libtd-static-devel-1.8.35-1.git20240813.mga9 libtdapi1.8.35-1.8.35-1.git20240813.mga9 libtdclient1.8.35-1.8.35-1.git20240813.mga9 libtdjson1.8.35-1.8.35-1.git20240813.mga9 lib64td-devel-1.8.35-1.git20240813.mga9 lib64td-static-devel-1.8.35-1.git20240813.mga9 lib64tdapi1.8.35-1.8.35-1.git20240813.mga9 lib64tdclient1.8.35-1.8.35-1.git20240813.mga9 lib64tdjson1.8.35-1.8.35-1.git20240813.mga9 From SRPMS: purple-telegram-tdlib-0.8.1-2.git20240907.mga9.src.rpm tdlib-1.8.35-1.git20240813.mga9.src.rpm
Assignee: geiger.david68210 => qa-bugs
Hi all, Installed from testing repos. I have opened Pidgin and I have created Telegram Account. Works fine for me. Perfect and fast update. Thank yoy very much!
Whiteboard: (none) => MGA9-64-OKCC: (none) => andrewsfarm
Keywords: (none) => advisory
Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0196.html
Status: NEW => RESOLVEDResolution: (none) => FIXED