MX Linux Forum

Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/

Later flatpak version is needed

http://www.forum.mxlinux.org/viewtopic.php?t=74678

Page 1 of 1

Later flatpak version is needed

Posted: Fri Mar 31, 2023 9:25 am
by amsel73
Telegram client cannot be updatet as flatpak. "A later flatpak version" is needed.
How can I solve this issue?
Thanks,
R.
===============================================================================================================
myuser@mx:~
$ flatpak update
Looking for updates…


ID Branch Op Remote Download
1. [✗] org.telegram.desktop stable u flathub < 77.7 MB

Error: org.telegram.desktop needs a later flatpak version
Updates complete.
error: There were one or more errors
myuser@mx:~
$
==============================================================================================================

Re: Later flatpak version is needed

Posted: Fri Mar 31, 2023 9:26 am
by Eadwine Rose
Please post your Quick System Info using Copy for forum, thanks.

Re: Later flatpak version is needed

Posted: Fri Mar 31, 2023 4:11 pm
by Stevo
It's not the very latest 4.7.1, but bullseye-backports does have Telegram 4.6.5, which can be easily installed with MXPI.

https://packages.debian.org/bullseye-ba ... am-desktop

and flatpak 1.14.4 https://packages.debian.org/bullseye-backports/flatpak

Re: Later flatpak version is needed

Posted: Mon Apr 03, 2023 11:14 am
by amsel73
Sorry,

here you can see the Quick System Info:

Code: Select all

System:    Kernel: 6.1.0-4mx-amd64 [6.1.11-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/vmlinuz-6.1.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_ahs_x64 Wildflower November 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Mini-pc System: HP product: HP ProDesk 400 G6 Desktop Mini PC v: N/A 
           serial: <filter> Chassis: type: 35 serial: <filter> 
           Mobo: HP model: 871A v: KBC Version 09.97.00 serial: <filter> UEFI: HP 
           v: S23 Ver. 02.10.00 date: 01/10/2022 
CPU:       Info: 6-Core model: Intel Core i5-10500T bits: 64 type: MT MCP arch: Comet Lake 
           family: 6 model-id: A5 (165) stepping: 3 microcode: F0 cache: L2: 12 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 55199 
           Speed: 900 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 900 2: 900 3: 2300 4: 2300 
           5: 2300 6: 2300 7: 2300 8: 2300 9: 2300 10: 2300 11: 2300 12: 2300 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable 
           Type: retbleed mitigation: Enhanced IBRS 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: Hewlett-Packard driver: i915 
           v: kernel bus-ID: 00:02.0 chip-ID: 8086:9bc8 class-ID: 0300 
           Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-8:4 
           chip-ID: 046d:081b class-ID: 0102 serial: <filter> 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") 
           diag: 604mm (23.8") 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CML GT2) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 
           class-ID: 0403 
           Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-8:4 
           chip-ID: 046d:081b class-ID: 0102 serial: <filter> 
           Sound Server-1: ALSA v: k6.1.0-4mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 15.0 running: yes 
Network:   Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl 
           port: 3000 bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e v: kernel 
           port: efa0 bus-ID: 00:1f.6 chip-ID: 8086:0d4c class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-14:6 chip-ID: 8087:0026 
           class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 200f hci-v: 5.2 rev: 200f 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio, telephony 
Drives:    Local Storage: total: 1.38 TiB used: 68.13 GiB (4.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNU512GZH size: 476.94 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: HPS1 temp: 23.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Toshiba model: MQ01UBD100 
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: HDD rpm: 5400 
           serial: <filter> scheme: MBR 
Partition: ID-1: / raw-size: 468.17 GiB size: 459.75 GiB (98.20%) used: 68 GiB (14.8%) fs: ext4 
           dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm 
           ID-2: /boot raw-size: 512 MiB size: 487.2 MiB (95.16%) used: 134.6 MiB (27.6%) fs: ext4 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
           ID-3: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.98 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/dm-1 maj-min: 253:1 mapped: swap 
Sensors:   System Temperatures: cpu: 24.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2617 note: see --pkg apt: 2602 lib: 1407 flatpak: 15 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           3: deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_11/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.easyname.at/mxlinux-packages/mx/repo/ bullseye main non-free
           2: deb http://mirror.easyname.at/mxlinux-packages/mx/repo/ bullseye ahs
Info:      Processes: 350 Uptime: 1m wakeups: 2 Memory: 15.41 GiB used: 1.31 GiB (8.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

Re: Later flatpak version is needed

Posted: Mon Apr 03, 2023 11:16 am
by Eadwine Rose
Moving to package requests

Re: Later flatpak version is needed

Posted: Mon Apr 03, 2023 11:29 am
by amsel73
Thanks for your fast reply :-)

Re: Later flatpak version is needed

Posted: Mon Apr 03, 2023 11:38 am
by Solon
amsel73 wrote: Fri Mar 31, 2023 9:25 am Telegram client cannot be updatet as flatpak. "A later flatpak version" is needed.
How can I solve this issue?
Thanks,
R.
For future reference: I too faced something similar using Odysee, which is based on the LBRY flatpak. Periodically, I would get a pop-up notice while running Odysee that a new update was available, and an outside Debian reference.

After discussions on this forum, and some trial and error, I discovered over a couple of months, that for programs like this, you should use your MX Package Installer (MXPI), and go out to the Flatpak Tab section, say, monthly, and do the following check:

Find the program (in my case: LBRY). Click on the 'button' on the left for the flatpak. Usually there will be nothing shown, but sometimes it will list a few lines up top showing something different.
When it lights up, check down at the bottom right of the MXPI. You will see some buttons, including "Uninstall".
But you will also see and you can use the "Upgrade All" button. Click on that button, and the newer version will be installed over the older version. In the event there is no upgrade, it will, after brief processing tell you that everything is already up to date.
You may also see a button that says, "Remove unused runtimes".
And after the update was successful, I would click the left button to highlight LBRY again, and then click the lower righthand button and remove the old unused runtimes. Again, no harm, if nothing needed to be removed, it will after brief processing tell you so!

In short, flatpaks work well, and they do get updated periodically. However, unlike the normal programs, which come down "automatically" in the normal updates, you have to go out manually and use the MXPI to keep your flatpaks up to 'snuff'.

Re: Later flatpak version is needed

Posted: Mon Apr 03, 2023 1:15 pm
by Stevo
What the heck is wrong with installing the current flat pack release from bullseye back ports?

We have limited time and resources to port stuff into MX repos, and duplicating existing back ports is not a productive use of those resources.
All times are UTC-04:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited