Running:
Operating System: MX Linux 23
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-10-amd64 (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 29.3 GiB of RAM
Graphics Processor: AMD Radeon Vega 11 Graphics
over the last few days I have been getting various errors applying the latest updates from Discover 5.27.5
I have been copying to clipboard and storing the errors in a text file.
Here is what I have so far
Aborted due to failure (While pulling runtime/org.freedesktop.Platform/x86_64/23.08 from remote flathub: opcode set-read-source: Opening content object c93b06a2ce457eca42d9635518df3281373ada691f222497885ec61079932e16: Opening content object c93b06a2ce457eca42d9635518df3281373ada691f222497885ec61079932e16: Couldn't find file object 'c93b06a2ce457eca42d9635518df3281373ada691f222497885ec61079932e16')
Aborted due to failure (While pulling app/org.inkscape.Inkscape/x86_64/stable from remote flathub: While fetching https://dl.flathub.org/repo/config: [6] Couldn't resolve host name)
Aborted due to failure (Error pulling from repo: tmpdir cleanup: Removing flatpak-cache-D684B2: Removing flatpak-cache-D684B2: unlinkat(be): No such file or directory)
Aborted due to failure (Error pulling from repo: tmpdir cleanup: Removing flatpak-cache-D684B2: Removing flatpak-cache-D684B2: unlinkat(b3): No such file or directory)
Aborted due to failure (While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08 from remote flathub: opcode open-splice-and-close: Writing metadata object: Creating temp file: No such file or directory)
Aborted due to failure (While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08-extra from remote flathub: opcode open: Creating temp file: No such file or directory)
Aborted due to failure (While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08 from remote flathub: No such file or directory)
Updates Aborted due to failure using Discover
Re: Updates Aborted due to failure using Discover
We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Forum Rules
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.
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.
- Eadwine Rose
- Administrator
- Posts: 14666
- Joined: Wed Jul 12, 2006 2:10 am
Re: Updates Aborted due to failure using Discover
Moved to help forum. You're asking for help, not chatting.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: Updates Aborted due to failure using Discover
Code: Select all
System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro rootflags=subvol=@
quiet splash
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_x64 Libretto July
31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASRock model: A300M-STX serial: <superuser required>
UEFI: American Megatrends v: P3.70B date: 03/26/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: discharging
Device-2: hidpp_battery_1 model: Logitech K350 serial: <filter> charge: 70% (should be ignored)
rechargeable: yes status: discharging
CPU:
Info: model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen/Zen+
note: check gen: 1 level: v3 note: check built: 2019 process: GF 12nm family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108102
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1382 high: 1400 min/max: 1400/3700 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 1400 6: 1261
7: 1400 8: 1400 bogomips: 59200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
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: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu
v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:15d8
class-ID: 0300 temp: 40.0 C
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: DP-1 mapped: DisplayPort-0 model: LG (GoldStar) Ultra HD serial: <filter>
built: 2018 res: 3840x2160 hz: 60 dpi: 163 gamma: 1.2 size: 600x340mm (23.62x13.39")
diag: 690mm (27.2") ratio: 16:9 modes: max: 3840x2160 min: 640x480
API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Vega 11 Graphics (raven LLVM
15.0.6 DRM 3.49 6.1.0-10-amd64) direct-render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 0.3.65 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.82 TiB used: 308.85 GiB (16.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Silicon Power model: SPCC M.2 PCIe SSD size: 1.82 TiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: VC2S038E temp: 56.9 C scheme: GPT
Partition:
ID-1: / raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 308.85 GiB (16.6%) fs: btrfs
dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 576 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 308.85 GiB (16.6%) fs: btrfs
dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 6 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p2
maj-min: 259:2
Sensors:
System Temperatures: cpu: 39.2 C mobo: N/A gpu: amdgpu temp: 39.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2468 pm: dpkg pkgs: 2441 libs: 1343 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 27
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
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/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bullseye main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:
Processes: 308 Uptime: 1d 3h 4m wakeups: 37 Memory: 29.3 GiB used: 3.95 GiB (13.5%)
Init: SysVinit v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Updates Aborted due to failure using Discover
I have provided the QSI report above. Please let me know if it's correct info or anything else needed. Thank you
Re: Updates Aborted due to failure using Discover
Try using Repo Manager in MX tools to switch your main repository to Salt Lake City, then reboot or log out / in and try your updates again. I've had enough problems in the past where the RIT mirror is not up to date, so the first thing I do after n install is switch my main repository to Salt Lake City. Salt Lake City is one of the four servers that are owned / operated by the MX team.
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.
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.