Telegram questions

[Rava]

hi, when i have run telegram no issue on taskbar,so i think xfce4.18 is ok and i have noveau like gpu driver.

I have 4.16 (003-xfce.xzm:20230922) and 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm
And of course this kernel:

Code: Select all

guest@rava:/$ uname -a
Linux rava.myporteus.net 5.4.30-porteus #1 SMP Sat Apr 4 20:11:00 UTC 2020 x86_64 Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz GenuineIntel GNU/Linux

So
● could be 4.16 XFCE (aka 003-xfce.xzm:20230922)
● the NVidia driver (nvidia-340.108 for kernel 5.4.30) or
● the kernel (5.4.30-porteus)
that's causing the issue.

I can try creating the NV driver for Port 5.01 generic kernel using the patched .run I got from / for porteux 0.7 : NVIDIA-Linux-x86_64-340.108-patched-kernel-6.5.run

root@rava:/# mloop /mybin/linux/porteus/5.0.1/x86-64/Porteus-XFCE-v5.01-x86_64.iso
[…]
root@rava:/# file /mnt/loop/boot/syslinux/vmlinuz
/mnt/loop/boot/syslinux/vmlinuz: Linux kernel x86 boot executable bzImage, version 6.5.5-porteus (root@porteus.example.net) #1 SMP PREEMPT_DYNAMIC Sat Sep 23 18:21:43 MSK 2023, RO-rootFS, swap_dev 0X6, Normal VGA

Seems 5.01 kernel version is 6.5.5-porteus

[Rava]

Still no news or answers from the Telegram support team.

Hopefully later when I have enough time (I should have, but at times RL surprises you) I will boot and try if Porteux 0.7 boots okay in vanilla mode.
If it does I try compiling for the newest kernel the NV driver with the standard porteux 0.7 kernel.

If that works, then I also try the same NV *run file compiling the kernel for the standard kernel version for Porteus 5.01. If that is also successful I try booting Port 5.01 with the recent kernel and new NV driver and see if the updated Telegram works.

If so, then it might have been the older NV driver, or the older kernel.

[rych]

Then, of course, not everything is sunny.
I created a new module incorporating the newest Linux binary as provided by Telegram. But that fails.
I sent the Support team this message:

Can I ask why do you need to create a new module encapsulating the Telegram binary -- which is already a single big bundle binary (plus they have a separate updater binary I think)? Just put those somewhere on your USB and adjust the .desktop file with the correct (hopefully persistent) path, I think? Besides, Telegram is automatically self-updating -- how would it even work with a hand-made module on top of it?!

[Rava]

Can I ask why do you need to create a new module encapsulating the Telegram binary -- which is already a single big bundle binary (plus they have a separate updater binary I think)? Just put those somewhere on your USB and adjust the .desktop file with the correct (hopefully persistent) path, I think? Besides, Telegram is automatically self-updating -- how would it even work with a hand-made module on top of it?!

Good thoughts on that. I think I was just following the usual orthodox Porteus approach.

Indeed it seems to only have the Telegram binary would be enough. When the most recent working version always has the same full path, e.g. /mnt/sda2/bin/Telegram then one could simply create a symlink in /usr/bin or /usr/local/bin to that binary. When an update works, one should move the old binary to e.g. /mnt/sda2/bin/Telegram.old or better via its version number, e.g. /mnt/sda2/bin/Telegram-3.2.4-x86_64 and copy the new one from somewhere in /home/guest/.local/share/TelegramDesktop/ to /mnt/sda2/bin/Telegram - and all is set.

[rych]

When an update works, one should move the old binary to e.g. /mnt/sda2/bin/Telegram.old

Telegram does that by itself: it quietly downloads (under your home directory -- and we'd better not save that bloat in changes see above exclusions) the new binary while you're using Telegram Desktop, and presents you with a button "Restart" or "Update" or something -- and doesn't hurt to press it right away as it takes a few seconds, and then we're running the new binary already in place of the old one. No need to save the old binary.

[Rava]

and doesn't hurt to press it right away as it takes a few seconds

Oh yes it does hurt.
In my case I only got an error executing the new binary. (See above)

No reply from the Telegram support team for many days now.

And to top it all up: the not working Telegram binary also messes up my local Telegram files so that all my contacts are lost, all my previous posts are gone.

I had to remove the non working newer version.
And had to restore all my local files.

And then start the old version, only then I again had an working Telegram once more.

[rych]

Oh yes it does hurt.

Wow, okay then -- I just tried to find the root of your problems and saw you had made a module, but perhaps that's not the reason. Works without a problem on my OpenBox Porteus 5.01.

Obviously Telegram adoption in this community isn't that great So will have to think of another platform for Porteus eXchange where I'd be uploading my xzm to. But that's a different topic. Good luck with Telegram binary (if you really need it on Linux desktop that is

[Rava]

Good luck with Telegram binary (if you really need it on Linux desktop that is

Yes, because it sucks to always have to rely on my mobile phone. I like having that switched off quite often - when there is no need to be available 24/7/365

So will have to think of another platform for Porteus eXchange

To me, github is one fine hosting solution, but albeit I am a registered user there, I never hosted stuff on it myself.
But just look at this as example:
https://github.com/porteux/porteux
or this
https://github.com/yt-dlp/yt-dlp

I am sure you are familiar with both porteux and yt-dlp.

And then there is also sourceforge. Example:
https://sourceforge.net/projects/ventoy/
But while sourceforge was as good as github still is some years prior, they changed a lot in recent years and now it sucks more and more. But that's my opinion on sourceforge, your mileage may vary.