Is it normal for pamac-manager?

Support
1

Please help me figure it out.
If periodically run the ‘System Monitor’ program, then pamac-manager works there with a CPU reaching up to 36% and Memory reaching from 300 MB to 700 MB, after which the program ends, but if immediately run ‘System Monitor’ again, then pamac-manager appears again with the same scenario. In the settings of the program the ‘Check for updates’ checkbox is removed.

In the ‘Logs’ program, in the ‘Security’ section, entries occur on average every 2 minutes
Sender: system
Message: dbus-:1.2-
org.manjaro.pamac.manager@17.service:
Consumed 7.151s CPU time.
Priority: 6
Subject: Resources consumed by unit runtime

Is this normal behavior for the program?

1 Like
2

Yes - when you enable AUR it is using quite a lot of resources.

Don’t enable AUR for the GUI. It is still available for CLI.

Please use the search function :mag: you are not the first to ask.

1 Like
3

This is not a solution

  1. Why does pamac-manager work at all if I didn’t set the ‘Check for updates’ setting? I want to manually manage updates.
  2. After disabling the ‘aur’, memory consumption decreased, but the ‘Security’ section of the ‘Logs’ program still has entries, although Consumed 7.151s CPU time changed to 2.706s CPU time.
4

But it is - if you are concerned about memory and cpu - this is one way of lowering …

5

Probably you misunderstand here something. Pamac does/check updates through systemd services. The mentioned service pamac-daemon.service runs all the time waiting for pamac to request something through dbus.

Remove pamac if that little cpu time is not acceptable… it depends on how good you system is. Stay with pacman alone on the terminal and you can do your updates manually.

The service just consumes 57ms on my system :man_shrugging:

systemctl status pamac-daemon.service  
● pamac-daemon.service - Pamac Daemon
     Loaded: loaded (/usr/lib/systemd/system/pamac-daemon.service; static)
     Active: active (running) since Wed 2024-03-06 12:46:05 CET; 18min ago
   Main PID: 78172 (pamac-daemon)
      Tasks: 4 (limit: 37689)
     Memory: 9.8M (peak: 12.9M)
        CPU: 57ms
     CGroup: /system.slice/pamac-daemon.service
             └─78172 /usr/bin/pamac-daemon

Mär 06 12:46:05 Elitedesk systemd[1]: Starting Pamac Daemon...
Mär 06 12:46:05 Elitedesk systemd[1]: Started Pamac Daemon.

Btw… no idea what you mean here. A program called “Logs” ?

6

Why didnt you mentioned this not in first place?

I first thought you talking about this issue, when you actively running pamac and searching in the GUI.

I need to investigate this too… this sounds like a heavy bug to me (When its true).

Which CPU are you using, can you post your system infos?

Edit:

$ systemctl status pamac-daemon.service
● pamac-daemon.service - Pamac Daemon
     Loaded: loaded (/usr/lib/systemd/system/pamac-daemon.service; static)
     Active: active (running) since Wed 2024-03-06 10:38:15 CET; 2h 49min ago
   Main PID: 2266 (pamac-daemon)
      Tasks: 4 (limit: 19110)
     Memory: 7.4M (peak: 9.4M)
        CPU: 14ms
     CGroup: /system.slice/pamac-daemon.service
             └─2266 /usr/bin/pamac-daemon

Mär 06 10:38:15 koboldx-z170 systemd[1]: Starting Pamac Daemon...
Mär 06 10:38:15 koboldx-z170 systemd[1]: Started Pamac Daemon.

I also have AUR enabled in the Pamac UI btw and 14ms sounds like nothing to me.

I dont have your Problem on my system, when my system idling
there is not a single core in HTOP above 5% usage and even that is a peak Limit.

7

Yep, this program.

8

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