MX Package Installer has a difficulty writing file in /tmp  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Forum rules
Post Reply
Message
Author
User avatar
abhidesh128
Posts: 83
Joined: Sun Nov 08, 2020 6:03 am

MX Package Installer has a difficulty writing file in /tmp

#1 Post by abhidesh128 »

When MX Package Installer is launched, and clicked on MX Test Repo tab, the following error is shown:

Image

This is a fresh install of MX 23. System info:

Code: Select all

System:
  Kernel: 6.1.0-26-amd64 [6.1.112-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-26-amd64 root=UUID=<filter> ro quiet splash
    resume=UUID=<filter> resume_offset=12154880 init=/lib/systemd/systemd
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.4_KDE_x64 Libretto
    September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Dell product: OptiPlex 7060 v: N/A serial: <superuser required> Chassis:
    type: 3 serial: <superuser required>
  Mobo: Dell model: 0DWPVW v: A00 serial: <superuser required> UEFI: Dell v: 1.31.0
    date: 08/01/2024
CPU:
  Info: model: Intel Core i3-8100T bits: 64 type: MCP arch: Coffee Lake gen: core 8 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xB (11)
    microcode: 0xF6
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 900 min/max: 800/3100 scaling: driver: intel_pstate governor: powersave
    cores: 1: 900 2: 900 3: 900 4: 900 bogomips: 24799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode (locked)
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  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: IBRS; IBPB: conditional; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-2 empty: DP-1, DP-2,
    DP-3, HDMI-A-1, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:3e91 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31") s-diag: 398mm (15.69")
  Monitor-1: HDMI-A-2 mapped: HDMI-2 model: HDMI serial: <filter> built: 2048 res: 1280x800
    hz: 60 dpi: 90 gamma: 2.54 size: 360x290mm (14.17x11.42") modes: max: 1280x800 min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  API: ALSA v: k6.1.0-26-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15bb class-ID: 0200
  IF: eth0 state: down mac: <filter>
  IF-ID-1: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek 802.11ac NIC type: USB driver: btusb,rtl8821cu bus-ID: 1-5:2 chip-ID: 0bda:c820
    class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
  Info: acl-mtu: 1021:8 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept
Drives:
  Local Storage: total: 350.27 GiB used: 72.39 GiB (20.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lenovo model: LENSE30256GMSP34MEAT3TA
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 2.5.0412 temp: 39.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: R013 scheme: GPT
Partition:
  ID-1: / raw-size: 60 GiB size: 58.76 GiB (97.93%) used: 30.05 GiB (51.1%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 28 MiB (28.5%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 178.38 GiB size: 174.51 GiB (97.83%) used: 42.24 GiB (24.2%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 19.42 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 41.0 C pch: 44.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2537 libs: 1345 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  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 bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirror.kku.ac.th/mx-packages/mx//repo/ bookworm main non-free
    2: deb https://mirror.kku.ac.th/mx-packages/mx//repo/ bookworm ahs
Info:
  Processes: 213 Uptime: 21m wakeups: 0 Memory: 15.3 GiB used: 2.6 GiB (17.0%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
SecureBoot enabled
Loving Linux...Since ages...!
Top
User avatar
Adrian
Developer
Posts: 9264
Joined: Wed Jul 12, 2006 1:42 am

Re: MX Package Installer has a difficulty writing file in /tmp

#2 Post by Adrian »

Can you write with regular user to /tmp? Can you do something like "touch /tmp/testfile"?
Top
User avatar
abhidesh128
Posts: 83
Joined: Sun Nov 08, 2020 6:03 am

Re: MX Package Installer has a difficulty writing file in /tmp

#3 Post by abhidesh128 »

Yes. I was able to touch a testfile in /tmp without sudo.
Loving Linux...Since ages...!
Top
User avatar
Adrian
Developer
Posts: 9264
Joined: Wed Jul 12, 2006 1:42 am

Re: MX Package Installer has a difficulty writing file in /tmp

#4 Post by Adrian »

OK... hmm... how do you start the mx-packageinstaller from KDE menu?
Top
User avatar
abhidesh128
Posts: 83
Joined: Sun Nov 08, 2020 6:03 am

Re: MX Package Installer has a difficulty writing file in /tmp

#5 Post by abhidesh128 »

Yes. From the menu.
Loving Linux...Since ages...!
Top
User avatar
Adrian
Developer
Posts: 9264
Joined: Wed Jul 12, 2006 1:42 am

Re: MX Package Installer has a difficulty writing file in /tmp

#6 Post by Adrian »

Nevermind, it's my boneheaded way to handle errors, see this:

Code: Select all

    if (reply->error() != QNetworkReply::NoError) {
        QMessageBox::warning(
            this, tr("Error"),
            tr("There was an error writing file: %1. Please check if you have enough free space on your drive")
...
The issue is a network error, not a write error. So for some reason the app cannot download the file. Do you use a proxy? Do you do anything fancy with your networking? Can you access http://mxrepo.com/mx/ ?
Top
User avatar
j2mcgreg
Global Moderator
Posts: 7273
Joined: Tue Oct 23, 2007 12:04 pm

Re: MX Package Installer has a difficulty writing file in /tmp

#7 Post by j2mcgreg »

Code: Select all

SecureBoot enabled
This needs to be disabled and it's the reason that your write to /tmp failed. Te package that you are downloading / installing lacks the signature required by Secure Boot.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.
Top
User avatar
Adrian
Developer
Posts: 9264
Joined: Wed Jul 12, 2006 1:42 am

Re: MX Package Installer has a difficulty writing file in /tmp

#8 Post by Adrian »

Are you sure about that? How is SecureBoot changing /tmp write access?
Top
User avatar
abhidesh128
Posts: 83
Joined: Sun Nov 08, 2020 6:03 am

Re: MX Package Installer has a difficulty writing file in /tmp

#9 Post by abhidesh128 »

j2mcgreg wrote: Fri Oct 18, 2024 8:28 am

Code: Select all

SecureBoot enabled
This needs to be disabled and it's the reason that your write to /tmp failed. Te package that you are downloading / installing lacks the signature required by Secure Boot.
Ohh. Can secure boot affect access to /tmp ? BTW, I am not installing anything that needs any signature stuff. MXPI is not able to write package cache.
Loving Linux...Since ages...!
Top
User avatar
j2mcgreg
Global Moderator
Posts: 7273
Joined: Tue Oct 23, 2007 12:04 pm

Re: MX Package Installer has a difficulty writing file in /tmp

#10 Post by j2mcgreg »

abhidesh128 wrote: Fri Oct 18, 2024 8:36 am
j2mcgreg wrote: Fri Oct 18, 2024 8:28 am

Code: Select all

SecureBoot enabled
This needs to be disabled and it's the reason that your write to /tmp failed. Te package that you are downloading / installing lacks the signature required by Secure Boot.
Ohh. Can secure boot affect access to /tmp ? BTW, I am not installing anything that needs any signature stuff. MXPI is not able to write package cache.
MX is Secure Boot adverse and it needs Secure Boot disabled.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.
Top
Post Reply

Return to “MX KDE Official Release”