MX Linux Forum

Posted: **Fri Nov 17, 2023 9:44 pm**

I just tried to update m flatpaks by using the MX package installer. I went to the Flatpak tab an clicked "Update all".
Then, I got a list of 10 packages to be updated, but the question...

Code: Select all

Proceed with these changes to the Default system installation? [Y/n]:

...was already answered with an "n" and the MX package updater doesn't allow for the "n" to be changed into a "y".

How can I change this into a "y", in order to perform the flatpak updates, please?

EDIT:
Sorry, I forgot the Quick info, here it is:

Code: Select all

System:    Kernel: 5.8.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.0-3-amd64 
           root=UUID=<filter> ro quiet splashintel_idle.max_cstate=1 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: Compiz 0.8.18 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-19.4_x64 patito feo March 31  2021 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: MSI model: Z170A GAMING M5 (MS-7977) v: 1.0 serial: <filter> 
           UEFI: American Megatrends v: 1.I0 date: 06/26/2018 
CPU:       Info: Quad Core model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S 
           family: 6 model-id: 5E (94) stepping: 3 microcode: F0 cache: L2: 8 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 63999 
           Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           5: 800 6: 800 7: 800 8: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable 
Graphics:  Device-1: NVIDIA GM206 [GeForce GTX 960] driver: nvidia v: 455.45.01 bus-ID: 01:00.0 
           chip-ID: 10de:1401 class-ID: 0300 
           Device-2: Creative Live! Cam Chat HD [VF0700] type: USB 
           driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 1-3.2:6 chip-ID: 041e:4097 
           class-ID: 0300 serial: <filter> 
           Display: x11 server: X.Org 1.20.4 compositor: compiz v: 0.8.18 driver: loaded: nvidia 
           display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.0x11.3") 
           s-diag: 1055mm (41.6") 
           Monitor-1: DP-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           Monitor-2: HDMI-0 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") 
           diag: 604mm (23.8") 
           OpenGL: renderer: GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-H HD Audio 
           vendor: Micro-Star MSI 100 Series/C230 Series Family driver: snd_hda_intel v: kernel 
           bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403 
           Device-2: NVIDIA GM206 High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403 
           Device-3: Creative Live! Cam Chat HD [VF0700] type: USB 
           driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 1-3.2:6 chip-ID: 041e:4097 
           class-ID: 0300 serial: <filter> 
           Sound Server-1: ALSA v: k5.8.0-3-amd64 running: yes 
           Sound Server-2: PulseAudio v: 12.2 running: yes 
           Sound Server-3: PipeWire v: 0.2.5 running: no 
Network:   Device-1: Intel 82574L Gigabit Network driver: e1000e v: 3.2.6-k port: d000 
           bus-ID: 03:00.0 chip-ID: 8086:10d3 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: TP-Link type: USB driver: rtl8812au bus-ID: 1-4:3 chip-ID: 2357:010d 
           class-ID: 0000 serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb 
           v: 0.8 bus-ID: 1-9:5 chip-ID: 0a12:0001 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 
           sub-v: 22bb hci-v: 4.0 rev: 22bb 
           Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park 
           link-mode: slave accept service-classes: rendering, capturing 
Drives:    Local Storage: total: 4.09 TiB used: 2.53 TiB (61.9%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM000-1F2168 size: 3.64 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5900 
           serial: <filter> rev: CC54 scheme: GPT 
Partition: ID-1: / raw-size: 40.83 GiB size: 39.9 GiB (97.70%) used: 31.58 GiB (79.2%) fs: ext4 
           dev: /dev/sda12 maj-min: 8:12 
           ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 31.4 MiB (32.7%) 
           fs: vfat dev: /dev/sda2 maj-min: 8:2 
           ID-3: /home raw-size: 62.53 GiB size: 61.25 GiB (97.95%) used: 53.74 GiB (87.7%) 
           fs: ext4 dev: /dev/sda13 maj-min: 8:13 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 31.25 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda7 maj-min: 8:7 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 29.8 C gpu: nvidia temp: 61 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 24% 
Repos:     Packages: 2856 note: see --pkg apt: 2806 lib: 1532 flatpak: 50 
           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 buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.eu.oneandone.net/linux/distributions/mx/packages/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 308 Uptime: 6h 42m wakeups: 1 Memory: 31.33 GiB used: 4.64 GiB (14.8%) 
           Init: SysVinit v: 2.93 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 8.3.0 
           alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 running-in: quick-system-in 
           inxi: 3.3.06

Posted: **Fri Nov 17, 2023 10:01 pm**

There was a bug that was fixed (hopefully) in the last build, what's your version, the last one is 23.11.05.

Posted: **Sat Nov 18, 2023 11:17 am**

I cannot find the version number, because I cannot find the name of the package of that installer.

EDIT:
I've found it.
The package name is mx-packageinstaller and my version is 23.11.01.

So, I do have the latest version (EDIT2: I mean, the lastest available for MX 19.4), but still I have the "n" preselected there.

How can I get rid of that "n" now, please?

Posted: **Sat Nov 18, 2023 4:00 pm**

Ok now, obviously, the mx-packageinstaller was updated to version 23.11.05, which doesn't support MX 19.4, and therefore I'm stuck now to version 23.01.1, which has this bug.
This makes me wonder, why don't you (the MX developers) make version 23.11.05 available for MX 19.4, if MX 19.4 is still supported (until April 2024, right?)?

EDIT:
The only chance I see is downgrading that package to 23.9.01, but that version is not available in the package installer, nor in Synaptic.

What can I do now, besides upgrading to MX 23, please?

Posted: **Sat Nov 18, 2023 5:05 pm**

I just sent up 23.11.06 which should work on buster.

Posted: **Sat Nov 18, 2023 5:34 pm**

Where can I find that new version, please?
It is not available in Synaptic or when I check MX for updates.

Posted: **Sat Nov 18, 2023 5:54 pm**

madmax25 wrote: Sat Nov 18, 2023 5:34 pm Where can I find that new version, please?
It is not available in Synaptic or when I check MX for updates.

it will be in a while.

here's a link to the debs

https://drive.google.com/file/d/1uQHhSP ... drive_link

Posted: **Sat Nov 18, 2023 6:29 pm**

Thank you very much, I have it, now.
Unfortunately, I made a mistake.
I updated the flatpaks using the terminal, but now I have to wait for the next update(s) of any flatpak(s) to verify that the "n" is gone, because currently the MX package installer just says "Nothing to do!".

Posted: **Sun Nov 19, 2023 3:46 am**

Sorry but there is still something wrong.
I moved to my notebook, installed the deb and the update history says I have 23.11.05, but both Synaptic and the About screen of that package are still claiming 23.11.01 was installed.

Posted: **Sun Nov 19, 2023 8:47 am**

Code: Select all

apt policy mx-packageinstaller

although at the moment it doesn't look like its in our repo yet.

I might have messed up the internal version number, but the package version should be 23.11.06.

Posted: **Sun Nov 19, 2023 10:45 am**

Yes, according to the update history, it is the new version, it is only the About screen.

I just checked it once more on both my desktop computer and my notebook.
Both have the new version in the update history and Synaptic.
Only the About screen has the wrong number.
I'm not sure why Synaptic on my noteook showed the wrong number yesterday evening.

the policy command gave me this output:

Code: Select all

apt policy mx-packageinstaller
mx-packageinstaller:
  Installed:           23.11.06
  Installation candidate: 23.11.06
  Version table:
 *** 23.11.06 100
        100 /var/lib/dpkg/status
     23.11.01 500
        500 https://mirror.eu.oneandone.net/linux/distributions/mx/packages/mx/repo buster/main amd64 Packages

Posted: **Sun Nov 19, 2023 10:53 am**

Yep that is correct. The internal version number has been corrected for next update but there should be not change in function.

Posted: **Sun Nov 19, 2023 2:24 pm**

Yes, I confirm that.
The preselected "n" is gone, so it is working.
It is only... well, let's say, a "cosmetical" issue.

Will there be an update where the About screen is fixed, too, in the near future?

Btw. sorry, I forgot to translate the terminal output, but I just fixed it.

Posted: **Sun Nov 19, 2023 2:33 pm**

my about says i am not the sharpest tool in the shed. i do not worry about it.

:-)))

Posted: **Sat Dec 23, 2023 6:02 pm**

I just wanted to use guiscrcpy to connect my Android to MX 19.4 xfce 64 bit, and again. I cannot open the display of my phone within guiscrcpy.
Usually I enter the PIN on my PC's keyboard and the display of the phone is opening but now, it remains black.

the phone got a FW updfate this evening, and so i thought, let's see if there's an update for guiscrcpy, too, but since I use the flatpak version of that tool, I found (again!) I cannot access the flatpak tab of mx-packageinstaller.
ThenI tried to update the flatpaks using the terminal, but there, I also failed, because I got the following output:

Code: Select all

flatpak update
Looking for updates…
Info: org.kde.Platform//6.4 is end-of-life, with reason:
   We strongly recommend moving to the latest stable version of the Plaform and SDK
Info: org.kde.Platform//5.15-21.08 is end-of-life, with reason:
   We strongly recommend moving to the latest stable version of the Platform and SDK
Applications using this runtime:
   in.srev.guiscrcpy
Info: org.gnome.Platform//43 is end-of-life, with reason:
   The GNOME 43 runtime is no longer supported as of September 20, 2023. Please ask your application developer to migrate to a supported platform.
Info: org.gnome.Platform//42 is end-of-life, with reason:
   The GNOME 42 runtime is no longer supported as of March 21, 2023. Please ask your application developer to migrate to a supported platform.
Info: org.gnome.Platform//41 is end-of-life, with reason:
   The GNOME 41 runtime is no longer supported as of September 17, 2022. Please ask your application developer to migrate to a supported platform.
Info: org.freedesktop.Platform//21.08 is end-of-life, with reason:
   org.freedesktop.Platform 21.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Info: org.freedesktop.Platform//1.6 is end-of-life, with reason:
   The Freedesktop 1.6 runtime is no longer supported and does not receive security updates. Please ask your application developer to migrate to a supported runtime.
Info: org.freedesktop.Platform.ffmpeg//1.6 is end-of-life, with reason:
   The Freedesktop 1.6 runtime is no longer supported and does not receive security updates. Please ask your application developer to migrate to a supported runtime.
Info: org.freedesktop.Platform.ffmpeg-full//21.08 is end-of-life, with reason:
   org.freedesktop.Platform 21.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Info: org.freedesktop.Platform.GL.default//21.08 is end-of-life, with reason:
   org.freedesktop.Platform 21.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Required runtime for org.kde.kdenlive/x86_64/stable (runtime/org.kde.Platform/x86_64/5.15-23.08) found in remote flathub
Do you want to install it? [Y/n]:

Obviously, there' s an issue with the mx-packageinstaller again, because that's the only thing that changed since guiscrcpy was working properly the last time.

Again, I wonder, why is it not supported anymore, when MX 19.4 is still supported until april 2024?
And what can I do now to fix this, please?

Posted: **Sat Dec 23, 2023 8:20 pm**

flatpaks are outside our control. if the runtimes are EOL, there isn't anything we can do about it.

Posted: **Sat Dec 23, 2023 8:59 pm**

in the terminal I tried to just hit enter according to the question at the end of the above output, so it seems, at least I managed to do these updates using the terminal, but well ... your post sounds like time has defiinitely come for me to upgrade to MX 23.1. I've been thinking, I could get a little closer to the EOL of MX 19.4, but doesn't look like that, does it?!

Merry Xmas everybody!

MX Linux Forum

MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer

Re: MX 19.4 xfce 64bit - can't update flatpaks using MX package installer