Pamac updates broken without explanation

Hey all, been a while since I’ve had any real issues, so in true Linux fashion here I am, looking for assistance.

Here goes. A couple of weeks ago I started having this problem where I can no longer update through the pamac gui, or pamac at all for that matter. Now, I know the “proper” way is to use “garuda-update”, but I just prefer the GUI and there’s some packages that just won’t update through garuda-update, such as Opera. Problem appeared I think after an update to pamac, but I’m not sure. Whenever I try to update it will get stuck at “refreshing chaotic-aur” during the databases refresh. At first I thought it was a problem with chaotic-aur, but it doesn’t seem to be the case. Garuda-update works like normal. Thing is, if I try to use pamac it will just stop at refreshing chaotic aur indefinitely and if I cancel and try again it will tell me that it’s waiting for another package manager to quit and it will just stay there. Also, if I use pamac and cancel after it fails, then nothing works, even garuda-update will say it failed to lock databases. As troubleshooting I tried removing the database lock file, both through Garuda Settings Manager and manually, but it doesn’t work. Weirdly, just installing standalone packages through pamac works, it’s the update function that is busted.

Any tips are welcome, as I’m at my wit’s end at this point. Thanks!

PS : In case that wasn’t enough, I’m also getting dependency errors with flutter packages now that aren’t getting resolved. AHHHHH!

 ╭─tolis@ZephyrusG14 in ~ 
 ╰─λ garuda-inxi
System:
  Kernel: 6.8.2-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=8174d900-03e1-4c54-859f-3276705fc84f rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    nvidia-drm.modeset=1 amd_pstate=active psi=1# Modified by
    garuda-migrations: splash mitigations=off ibt=off
  Desktop: GNOME v: 46.0 tk: GTK v: 3.24.41 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 46.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA401IV_GA401IV
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: GA401IV v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: GA401IV.221
    date: 07/14/2023
Battery:
  ID-1: BAT0 charge: 44.3 Wh (72.5%) condition: 61.1/76.0 Wh (80.4%)
    power: 9.7 W volts: 15.8 min: 15.8 model: ASUSTeK ASUS Battery type: Li-ion
    serial: N/A status: discharging
CPU:
  Info: model: AMD Ryzen 9 4900HS with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x8600104
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 551 high: 1800 min/max: 400/4422 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 400
    4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 1800
    14: 1429 15: 400 16: 400 bogomips: 95830
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Renoir [Radeon RX Vega 6 ] vendor: ASUSTeK driver: amdgpu
    v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: HDMI-A-1
    bus-ID: 04:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 30.0 C
  Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: Najing CEC Panda 0x0050 built: 2019 res: 1920x1080
    dpi: 158 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.3-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    renoir LLVM 17.0.6 DRM 3.57 6.8.2-zen2-1-zen) device-ID: 1002:1636
    memory: 500 MiB unified: no display-ID: :0.0
  API: Vulkan v: 1.3.279 layers: 8 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 24.0.3-arch1.2
    device-ID: 1002:1636 surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
    v: 24.0.3-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 04:00.1
    chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x,
    snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir,
    snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63 pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.8.2-zen2-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.0.4 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 Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-4:3 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 1.82 TiB used: 159.05 GiB (8.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 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: 2B2QEXM7 temp: 39.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 256 GiB size: 256 GiB (100.00%) used: 159.03 GiB (62.1%)
    fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 260 MiB size: 259.5 MiB (99.80%)
    used: 27.6 MiB (10.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 256 GiB size: 256 GiB (100.00%)
    used: 159.03 GiB (62.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-4: /var/log raw-size: 256 GiB size: 256 GiB (100.00%)
    used: 159.03 GiB (62.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-5: /var/tmp raw-size: 256 GiB size: 256 GiB (100.00%)
    used: 159.03 GiB (62.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.04 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p7 maj-min: 259:7
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A gpu: amdgpu temp: 30.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15.04 GiB used: 8.14 GiB (54.1%)
  Processes: 494 Power: uptime: 2h 21m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 5.97 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Packages: 1975 pm: pacman pkgs: 1912 libs: 563 tools: gnome-software,
    octopi, pamac, paru pm: flatpak pkgs: 63 Compilers: clang: 17.0.6
    gcc: 13.2.1 Shell: garuda-inxi default: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.33
Garuda (2.6.23-1):
  System install date:     2024-03-19
  Last full system update: 2024-03-22
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

This is a dangerous system state and can lead to exactly the problems you are experiencing. Solve this problem first. :slight_smile:

4 Likes

Well, this is what the PS in my post is about. I finished updating all I could through garuda-update, but this showed up because flutter dependencies can’t be resolved. I will solve it, but the problem with pamac started before this.

However, as always, thanks Bro!

Welp, I deleted flutter to resolve the dependency issues and now pamac gets stuck at “Synchronizing package databases”. WHAAAAAAAAT

garuda-update -a

updates also AUR packages, if this is your issue.

4 Likes

This usually happens when two instances of pacman are running at the same time.

For your flutter issue look here:

1 Like

Here in the forum it says, at least four times, that you should not use pamac because it can cause problems.

What do the users who know this do?
Right, they use it. :crazy_face:

Same for grub-customizer :smiley:
10 Likes

If you want a bit of a gui I recommend using garuda assistant.

If you have aur packages that you wish to update often I recommend going into your garuda update config an removing the # from # UPDATE_AUR=1
which you can find /etc/garuda/garuda-update/
After doing so running garuda-update will always update your AUR packages.

I’m using kde here but these steps also work in gnome an the other spins

4 Likes

Friends that like friends don’t let them drive Pamac, a Manjaro-created critter.

6 Likes

Was the issue resolved by using garuda-update -a (upd -a)?

Well, that was partially my issue, so thanks for that! I didn’t know that garuda-update could also handle aur packages, so that’s good to know!

Well, I figured as much. Thing is, I can’t ever find two instances running. It will try updating the databases after a fresh boot, but it will hang there as if it’s actually doing something, but it’s doing nothing. The whole “waiting for another package manager” thing appears only after I cancel the process, at which point it’s all gone down. Pamac, Pacman, garuda-update, nothing works until after a restart.

Hey man, if I liked being told what to do and not do, I’d be using a Mac! :rofl:

In all seriousness though, it’s been working mostly just fine for me ever since I installed Garuda. I don’t know what went into it now and it decided to just stop working. I know we’re not supposed to use it, but I didn’t know since the beginning and I got used to it, so as long as I didn’t have any problems I just kept using it. Habits can change, but having a nice clean UI was great. I could see all pending updates, search for packages etc. I know this is heresy, but I don’t really have an allergy to GUIs and I prefer them over the CLI. Not only for me personally, the command line is a huge reason why Linux doesn’t really get more popular with “the normies”. It’s always nice to have it there, but it shouldn’t be the only option IMO.

I’m now gonna take my exile and your stone throwing like a man. :saluting_face:

Thanks, that’s cool to know! But still, it’s just a GUI instead of typing garuda-update by myself. That’s not the point. As I wrote above, the Pamac GUI was nice to have, with everything in it. It’s not that I can’t live without it.

Too late. You betrayed me. You let me fall to the dark side. I even went as far as installing Manjaro before coming here. Where were you when I needed you? Where were you when I was getting distro paralysis from all the choices? WHERE WAS GONDOR WHEN THE WESTFOLD FELL?

Well, the packages that were failing to update did indeed update, so no issue there. My Opera installation is now up to date and all is functioning as it should. Pamac is still FUBAR tho.

2 Likes

I think my last post in the Manjaro Forums was thus, as @c00ter, my old nemesis before becoming @Bro. It is kinda old. : Web Browser Slow - #2 by cscs - Support - Manjaro Linux Forum

The only reason my nic changed from c00ter to Bro was out of a desire to alleviate the other Linux users here from being assaulted by that term, i. e. “Hey, bro…”
Get it? :smiley:

I have never met a Linux user worthy or liking being addressed suchlike. :wink:

1 Like

Mostly, not always. This can also have other causes.

Remove octopi, pamac and gnome-software-center and try again.

1 Like

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