Pamac's update search function broken? After the latest update that released 1 week ago (05/November/2024)

Support
1

Hello,
I upgraded pamac on both of my systems (Laptop & Pc), 1 week ago:

[2024-11-05T07:34:43+0100] [ALPM] transaction started
[2024-11-05T07:34:43+0100] [ALPM] upgraded discord (0.0.72-1 -> 0.0.73-1)
[2024-11-05T07:34:43+0100] [ALPM] upgraded libpamac (11.6.4+2+g1421283-4 -> 11.7.0-0)
[2024-11-05T07:34:43+0100] [ALPM] upgraded libpamac-flatpak-plugin (11.6.4+2+g1421283-4 -> 11.7.0-0)
[2024-11-05T07:34:44+0100] [ALPM] upgraded manjaro-release (24.1.1-1 -> 24.1.2-1)
[2024-11-05T07:34:44+0100] [ALPM] upgraded pamac-cli (11.6.0-5 -> 11.7.0-0)
[2024-11-05T07:34:44+0100] [ALPM] upgraded pamac-gtk (11.7.1-6 -> 11.7.2-0)
[2024-11-05T07:34:44+0100] [ALPM] transaction completed

After i download this packages on both my system, i experience that the update search was instant… in less then 1 second, which normally took at least (minimum) 5-10 seconds if i remember correctly.

I also have to add, that i deactivate AUR Update check in Pamac after latest stable release. But i don’t think this can accelerate the update search so heavily or?

I think something must be broken, when there is absolute no wait time.

So today i was looking for updates again (i also saw that the firefox client has a new version since yesterday).

I updated my mirrors as usual with:
sudo pacman-mirrors --fasttrack

So i started Pamac GUI and the search was instant again… click and nothing found in less then 1second.

So i openend the terminal and typed sudo pacman -Syu and found 2 packages, that was not shown in pamac earlier:

[2024-11-13T15:16:06+0100] [PAMAC] synchronizing package lists
[2024-11-13T15:18:17+0100] [PACMAN] Running 'pacman -Syu'
[2024-11-13T15:18:17+0100] [PACMAN] synchronizing package lists
[2024-11-13T15:18:17+0100] [PACMAN] starting full system upgrade
[2024-11-13T15:18:59+0100] [ALPM] transaction started
[2024-11-13T15:18:59+0100] [ALPM] upgraded archlinux-keyring (20240709-2 -> 20241015-1)
[2024-11-13T15:19:00+0100] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2024-11-13T15:19:02+0100] [ALPM-SCRIPTLET] ==> Updating trust database...
[2024-11-13T15:19:02+0100] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2024-11-18
[2024-11-13T15:19:02+0100] [ALPM] upgraded pamac-cli (11.7.0-0 -> 11.7.1-1)
[2024-11-13T15:19:02+0100] [ALPM] transaction completed
[2024-11-13T15:19:02+0100] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2024-11-13T15:19:02+0100] [ALPM] running '30-systemd-update.hook'...

Is there something broken with pamac after the latest update?

If something is broken now with my two systems, maybe it happend because i was updating pamac with pamac? :innocent:

Inxi:

System:
  Kernel: 6.6.54-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/vmlinuz-6.6-x86_64
    root=UUID=eb235aa7-d461-413d-800e-ea57385703fb rw sysrq_always_enabled=1
    nvidia_drm.modeset=1 retbleed=off
    resume=UUID=717b267e-7322-4bf9-a840-f1210d422d1a udev.log_priority=3
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z170X-UD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: Z170X-UD3-CF v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: F23d
    date: 12/01/2017
Memory:
  System RAM: total: 16 GiB available: 15.58 GiB used: 3.42 GiB (22.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: no module installed
  Device-2: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
  Device-3: ChannelB-DIMM0 type: no module installed
  Device-4: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 4500 min/max: 800/4700 scaling: driver: intel_pstate
    governor: performance cores: 1: 4500 2: 4500 3: 4500 4: 4500 5: 4500 6: 4500
    7: 4500 8: 4500 bogomips: 64026
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  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: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Vulnerable
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: Micro-Star MSI
    driver: nvidia v: 550.120 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-09; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none off: DP-3
    empty: DP-1, DP-2, HDMI-A-1, Unknown-1 bus-ID: 01:00.0 chip-ID: 10de:1e07
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 122 s-size: 532x302mm (20.94x11.89")
    s-diag: 612mm (24.08")
  Monitor-1: DP-3 mapped: DP-4 note: disabled model: Dell S2417DG
    serial: <filter> built: 2018 res: 2560x1440 dpi: 123 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.120
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
    memory: 10.74 GiB
  API: Vulkan v: 1.3.295 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 2080 Ti driver: nvidia v: 550.120 device-ID: 10de:1e07
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA TU102 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
  Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 0b:00.0 chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.6.54-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.5 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager
Drives:
  Local Storage: total: 5.93 TiB used: 418.33 GiB (6.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: MP600 PRO LPX
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: EIFM31.6 temp: 30.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HDN724030ALE640
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A5E0 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 88.61 GiB size: 86.66 GiB (97.80%) used: 19.67 GiB (22.7%)
    fs: ext4 dev: /dev/sdc1 maj-min: 8:33 label: N/A
    uuid: eb235aa7-d461-413d-800e-ea57385703fb
  ID-2: /boot raw-size: 2.93 GiB size: 2.82 GiB (96.15%)
    used: 121.9 MiB (4.2%) fs: ext3 dev: /dev/sdc3 maj-min: 8:35 label: N/A
    uuid: cbfeca98-b99d-4383-9ded-fe66cd598006
  ID-3: /home raw-size: 332.03 GiB size: 325.75 GiB (98.11%)
    used: 16.53 GiB (5.1%) fs: ext4 dev: /dev/sdc4 maj-min: 8:36 label: N/A
    uuid: ada4a6a2-bd0a-4652-b386-7c637bba7ee9
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdc2 maj-min: 8:34 label: N/A
    uuid: 717b267e-7322-4bf9-a840-f1210d422d1a
Sensors:
  System Temperatures: cpu: 30.0 C mobo: N/A gpu: nvidia temp: 31 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 25%
Info:
  Processes: 273 Power: uptime: 3h 23m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.22 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 256 default: graphical tool: systemctl
  Packages: 1603 pm: pacman pkgs: 1597 libs: 455 tools: pamac pm: flatpak
    pkgs: 6 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Bash v: 5.2.37
    running-in: konsole inxi: 3.3.36
2

You may face this issue Searching AUR points to unexpected db · Issue #1 · manjaro/pamac-cli · GitHub

You can try the following: pamac upgrade --aur --force-refresh --dry-run

As I saw your inxi report and your detailed forum profile, you alredy share more information about your hardware than mdd collect. So I wonder why comment so much around that topic?

Read my post which explains why data collected information is good.

3 Likes
3 
$ pamac upgrade --aur --force-refresh --dry-run
Preparing...
Failed to read AUR data from /var/lib/pacman/sync/packages-meta-ext-v1.json.gz : Error opening file /var/lib/pacman/sync/packages-meta-ext-v1.json.gz: No such file or directory
Nothing to do.
Transaction successfully finished.

I also send my system information to Valve, when they ask me and i have this overview right in front of me and the option to manually reject it or not if i don’t like it. Im missing that option around MDD.

I think the combination around a automatic process that refreshing my system information (unasked) is for me the biggest problem.

You guys also want to track the location in mdd, right?
I guess this is only possible with a IP that is refreshed daily.

And to have (MDD) a Telemetry Service which can also be modified in future.

Yeah i just read your post there. Where i asked you few questions just half hour ago :wink:

4

There is no IP address collected. Only snippets of 16 characters of the machine-id after hashing it. So the IP information will never leave your PC. Location is done via the timezone settings. You can check the code.

When I call pamac upgrade --aur --force-refresh --dry-run I have no AUR database error. Anyhow, on stable branch are not so many updates pushed lately.

3 Likes
5

Okay, timezone is spoofed in my system to english. No IP is sending out sounds good.

But i still think the information can be used to track me, to make my system Unique.

Like this browser fingerprint website shows:

I think when im freshly connect to my VPN and MDD wants to phone home (i still don’t know when this service will be triggered), it could instantly reveals my identity/my system, at least with my browser fingerprint i guess.

$ pamac upgrade --aur
Preparing...
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: Koboldx (koboldx)
Password: 
==== AUTHENTICATION COMPLETE ====
Synchronizing package databases...
Refreshing AUR...                                                                                                             
Nothing to do.                                                                                                                
Transaction successfully finished.
$ pamac upgrade --aur --force-refresh --dry-run
Preparing...
Nothing to do.
Transaction successfully finished.

With the combination to use earlier pamac upgrade --aur the dryrun works now without a error.

If Pamac GUI will now shown packages or not, i can’t tell on my PC
because i just refreshed my packages with pacman CLI earlier, where i downloaded the 2 packages that shown at the Topic above.

Anyways the Pamac Update Search is still instant finished with zero seconds wait time… this isn’t normal, even with disabled AUR Package check or not?

But i try this later out on my Laptop in a few hours (which i can’t use right now) and report back later or tomorrow.

Thank you so far for your support. :slight_smile:

6

Oh F…poop! I’m sorry, but this makes me so angry! I tell you what. I’ll give you my machine id gotten from MDD and you can use that to tell me about myself:

"device_id": "bdc15590-3ae6-5256-965e-0139d6f96339",

Ah heck, I’m feeling generous, here’s everything:

{
    "meta": {
        "version": 1,
        "timestamp": "2024-11-13T16:26:53.118433+00:00",
        "device_id": "bdc15590-3ae6-5256-965e-0139d6f96339",
        "distro_id": "manjaro",
        "release": "24.1.1",
        "inxi": true
    },
    "system": {
        "kernel": "6.6.54-2-MANJARO",
        "form_factor": "desktop",
        "install_date": "2024-10-13T09:53:41+00:00",
        "product_name": "Z370 HD3",
        "product_family": "Default string",
        "sys_vendor": "Gigabyte Technology Co., Ltd.",
        "board_name": "Z370 HD3-CF"
    },
    "boot": {
        "uefi": true,
        "uptime_seconds": 2365610
    },
    "cpu": {
        "arch": "x86_64",
        "model": "Intel Core i7-8700",
        "cores": 6,
        "threads": 12
    },
    "memory": {
        "ram_gb": 15.545059204101562,
        "swap_gb": 7.812496185302734
    },
    "graphics": {
        "comp": "kwin_x11",
        "dri": null,
        "gpus": [
            {
                "vendor": "Gigabyte",
                "model": "NVIDIA GM206 [GeForce GTX 960]",
                "driver": "nvidia"
            }
        ],
        "outputs": [
            {
                "model": "LG (GoldStar) ULTRAWIDE",
                "res": "2560x1080",
                "refresh": 60.0,
                "dpi": 97.0,
                "size": "673x284"
            },
            {
                "model": "LG (GoldStar) ULTRAWIDE",
                "res": "2560x1080",
                "refresh": 60.0,
                "dpi": 97.0,
                "size": "673x284"
            }
        ]
    },
    "audio": {
        "servers": [
            {
                "name": "PulseAudio",
                "active": true
            },
            {
                "name": "PipeWire",
                "active": false
            }
        ]
    },
    "disk": {
        "disks": [
            {
                "size_gb": 232.88591766357422,
                "root": {
                    "size_gb": 224.0934295654297,
                    "fstype": "ext4",
                    "crypt": false
                },
                "home": null
            }
        ],
        "windows": false
    },
    "locale": {
        "region": "en_ZA.UTF-8",
        "language": "en",
        "timezone": "Africa/Johannesburg"
    },
    "package": {
        "last_update": "2024-10-15T08:21:37+02:00",
        "branch": "stable",
        "pkgs": 1871,
        "foreign_pkgs": 40,
        "pkgs_update_pending": 12,
        "flatpaks": 0,
        "pacman_mirrors": {
            "total": 1,
            "ok": 1,
            "country_config": "Austria"
        }
    },
    "desktop": {
        "cli": "/bin/bash",
        "gui": "KDE Plasma",
        "dm": "SDDM",
        "wm": "kwin_x11",
        "display": "x11",
        "display_with": "Xwayland"
    }
}

Please, tell me where I live, exactly, tell me what I do, tell me my monthly remuneration, as well as the names of my children. Do that correctly with sources and I’d start worrying.

7

I responsed to exactly this argument in the second MDD Topic!

And i can only repeat myself… im not a tracking or advertising company. Im not sure how this all together works. Because i can’t reveal you (which i have zero intentions btw anyways), doesn’t mean that no one else can do it.

Please can we stop flood this Pamac problem that im facing here now, with Off-Topic stuff?

1 Like
8

What terms did you search in pamac?

9

Its just the “Updates” Button in Pamac GUI.

The UI behavior really changed after the update last week.

Its almost impossible to read, i have to spamm the refresh button to read: Checking For Updates 100%

And pacmanlog shows only this:

[2024-11-13T17:43:24+0100] [PAMAC] synchronizing package lists

Not sure if this is normal. :man_shrugging:

But again, i have no package to update right now at my PC… i can only mess around with my Laptop which should have still 2 available updates right now, which wasn’t displaying on my PC today in the Pamac GUI.

Edit:
My Laptop is still busy, but in around 2-3 hours i will report back.

10

1 Like
11

AUR contains >94,500 packages so checking for Repository updates only would be faster if pamac does not need to refresh Manjaro AUR database

1 Like
12

I just successfully updated with Pamac GUI on my Laptop and found pamac-cli and archlinux-keyring package without no problems. My Laptop used mirrored settings from my PC btw.

The packages was found right after i was clicking on the Update Button.

There was no need to pamac upgrade --aur --force-refresh --dry-run.

Since its confirmed now that i face this problem only on my PC now.
I think i can only report back when my PC will have available updates again.

I think this and the new pamac update accelerated the update check function. Positive for my Laptop but negative for my PC.

Hopefully pamac upgrade --aur --force-refresh --dry-run could fix this now on my PC, but i think i need to wait till the next package update is at the horizon.

1 Like
13

:crystal_ball: You live in Springfield, USA; a next-door neighbour of Ned Flanders. You are a safety inspector at the Springfield Nuclear Power Plant, and you are grossly overpaid relative to your skillset. You have three children named Bart, Lisa and Maggie, respectively. :crystal_ball:

14

This sounds similar to the problem I’ve been having with Pamac for the past couple of weeks. Clicking update completes the check almost immediately, but it never shows if any new updates are available. The difference with mine is that when I then close the Pamac window I get a notification after a second or so telling me I have updates available!

1 Like
15

Couple of weeks? Are you sure?

You know you can look in your logfile to verify when you updated the last time with pamac:

/var/log/pacman.log

I have Pamacs (background) automatic search function disabled.

So i can’t tell if this would be the same here, it could be…

But what would be interesting, if you see available packages then in the CLI with sudo pacman -Syu

16

Pamac (on my PC) is showing finally new updates again. :slight_smile:

pamac upgrade --aur

pamac upgrade --aur --force-refresh --dry-run

Probably fixed it already,
but I also Refresh Databases within Pamac and it works again.

Feedback: I don’t know if the new Pamac GUI version should work like that and if it is intended like that or not, but it shows a other behavior when i click on the Updates Button… it doesn’t triggering automatically to look for updates anymore. The last Timestamp check is not updated and im forced to click on the Refresh button to finally look for packages.

With the older Pamac version, i just had to click on the Updates Button and thats it.

17

I used the following command and it seems to have fixed things for me as well:

pamac upgrade --aur --force-refresh --no-confirm

1 Like
18

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