Issue: Updating software after system update after one year

Issues & Assistance
1

Hello Garuda Linux Forum,

I’ll admit I haven’t dabbled with Garuda in quite some time, and applied a recent garuda-update in the konsole.

System:
Kernel: 6.5.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=73c5507d-4265-4269-ac80-cbf5d27d3c33 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B550I AORUS PRO AX v: x.x
serial: <superuser required> UEFI: American Megatrends LLC. v: F15
date: 01/04/2022
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA201205
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2687 high: 3700 min/max: 2200/4650 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3700 2: 2200
3: 2200 4: 2200 5: 2874 6: 3700 7: 2200 8: 2200 9: 3700 10: 2200 11: 2874
12: 2200 bogomips: 88633
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 0d:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.0
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: LCD TV built: 2013
res: 1920x1080 hz: 60 dpi: 3048 gamma: 1.2 size: 16x9mm (0.63x0.35")
diag: 6mm (0.2") ratio: 15:9 modes: max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 23.1.7-arch1.1 renderer: AMD Radeon RX 6700 XT
(navi22 LLVM 16.0.6 DRM 3.54 6.5.2-zen1-1-zen) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0d:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.5.2-zen1-1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.79 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 RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 09:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 0a:00.0 chip-ID: 14c3:0608
class-ID: 0280
IF: wlp10s0 state: down mac: <filter>
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 0e8d:0608
class-ID: e001 serial: <filter>
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
rfk-block: hardware: no software: no address: see --recommends
Drives:
Local Storage: total: 3.64 TiB used: 42.1 GiB (1.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD Blue SN570 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234140WD temp: 37.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Western Digital
model: WD Blue SN570 2TB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234140WD temp: 27.9 C
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 42.1 GiB (2.3%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 42.1 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 42.1 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 42.1 GiB (2.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 42.8 C mobo: 33.0 C gpu: amdgpu temp: 36.0 C
mem: 30.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Processes: 317 Uptime: 5m wakeups: 0 Memory: total: 32 GiB
available: 31.25 GiB used: 2.2 GiB (7.0%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1473 libs: 412 tools: octopi,pamac,paru
Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.29
Garuda (2.6.16-1):
System install date:     2022-06-17
Last full system update: 2023-09-11
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       No/Undetected
Failed units:

While everything seems to be working as should upon startup (including software itself), for every time I attempt an update on the software (this time using an update tool to manually select updates), I receive a notification from the System Maintenance tool, issuing the following…

Dependency resolution failed:<br/><br/>plasma-framework &lt;- latte-dock: could not satisfy dependencies

Nevertheless, my system overall seems to be up to date, though please correct me if I’m wrong, and perhaps if I missed an integral system upgrade or configuration that might be the cause of this issue.

My experience with this distro has been stellar, even as we speak - I’m just concerned regarding upon the current issue, and hopefully preventing it from impacting anything else in the long-run.

Thank you,

2

You’ll need to remove Latte Dock cause it’s not supported by Plasma 6. If you don’t mind me asking how old is the ISO you used to install Garuda?

1 Like
4

It’s all in garuda-inxi

I don’t mean this in a bad way, but if you haven’t used or updated a rolling Linux distribution for so long, you should reinstall it. Even if an update were to run now,
which hasn’t happened (partially upgraded), new problems will surely arise over time.

You can of course keep trying, but I don’t know what would motivate us to solve one problem after another for you under these circumstances?

Back up your important data beforehand. :slight_smile:

2 Likes
6

I just wanted to make sure I wasn’t seeing things :rofl: :rofl: :rofl:

1 Like
7

You should explain this a little more.
What tool?
What do you mean with “manually select updates”?
One may think that you are applying partial updates… :thinking:

As for the update issues, you may be lucky and you just have to uninstall latte-dock . If so, you are very lucky. :smiley:

6 Likes
10

That is not a way to update arch. use garuda-update -a at the least but yea at this point. a back up an reinstall would be faster an pain free.

2 Likes
12

You can just move the home dir to another drive though before you move it back you have to set the permissions to your new user or you will have some problems

14

That’s at least how I do it when I need to. you can use you file manager or use terminal what ever floats your poat though the permission bit i would do with terminal but it can be done with root priv in a gui

I cant say this is the 100% correct way but it works. though since your setup is pretty old i might be best not to include the . files like .config .local an all that

1 Like
16

That or paru -R latte-dock or to also remove dependencies with it paru -Rs

17

With the amount of time on this I would of simply gotten the current release ISO and reinstalled Garuda. For myself from start of install, to landing on the desktop, to tweaking, to getting all my software installed it’s under 6 hours.

As for the age of the install and someone can correct me if I’m wrong since you did a recent update you should be on Plasma 6 unless something in the old install simply won’t allow Plasma to update.

Without this being updated to the latest Plasma I see no reason to give support cause if Plasma isn’t updated most likely plenty isn’t updated.

1 Like
19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.