• pamac 7.3.4-1 changes/issues/thinkings


    @toxpal no failed or errors inside :(

  • Bildschirmfoto vom 2019-01-31 10-34-49.png
    looks like there is a pamac-indicator build in now for GNOME:
    pamac-app-indicator.png

  • @joekamprad said in pamac 7.3.4-1 changes/issues/thinkings:

    Bildschirmfoto vom 2019-01-31 10-34-49.png
    looks like there is a pamac-indicator build in now for GNOME:
    pamac-app-indicator.png

    Is working without topicons-plus, and is provided as a extension.

  • Just a note at @joekamprad 's findings, the icon adepts the icon theme that’s in use. This is not the worst thing, in fact I think it’s a good thing, but I’m just saying it, in case someone says the icon looks different in their system.

  • Folks, am I really the only one who has constant troubles with new updates manager almost every single time? Here are my problems so far:

    1. Very often, it starts downloading updates and then stops. Download progress bar gets locked and this is it. The only way to restart updates is reboot OS. Never happened with old updates manager.
    2. And of course, absolutely irrelevant numbers of available updates. Messages about new updates when there are no updates, random messages “X updates available” during update process itself, and messages about tons of updates, when there are very few updates. For example, here’s today’s screen - https://i.postimg.cc/kXcKYb7D/updates.jpg

    I manually counted all the updates, and there are less than 20 updates, not 54…

  • if you have yay for aur do in terminal : yay -Qua ? there any updates ?

  • Don’t have it, but can install (if that would help debugging)…

  • @toxpal ithink the other are Aur updates , you can checkup intoo the settig to switch of also to check if its so.

  • @toxpal
    Do you have AUR enabled in Pamac? The new version has reset the settings to default, so it could be AUR updates, from previous install, but pamac doesn’t show them, like @ringo32 already said.

  • Yes, I have AUR enabled. However, previous versions of updater always displayed the number of updates (including AUR updates) properly… So I did nothing now, rebooted OS, and… got a notification about available updates. Only this time (after reboot), the number of updates (displayed in notification tray) was correct (20 updates, not 54).

  • Frozen downloads drive me crazy… Now it got even worse, 30% of time updates freeze after downloading about 5 MB, even if connection works perfectly. Happened 10 minutes ago last time… Here’s the log:

    journalctl --since "2019-02-08" | grep pamac
    vas. 08 15:25:06 desktop ksmserver[986]: org.kde.kf5.ksmserver: Starting autostart service  "/etc/xdg/autostart/pamac-tray-appindicator.desktop" ("/usr/bin/pamac-tray-appindicator")
    vas. 08 15:25:06 desktop dbus-daemon[911]: [session uid=1000 pid=911] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.34' (uid=1000 pid=1083 comm="/usr/bin/pamac-tray-appindicator ")
    vas. 08 15:25:06 desktop dbus-daemon[620]: [system] Activating via systemd: service name='org.manjaro.pamac.system' unit='pamac-system.service' requested by ':1.66' (uid=1000 pid=1083 comm="/usr/bin/pamac-tray-appindicator ")
    vas. 08 15:25:06 desktop dbus-daemon[620]: [system] Successfully activated service 'org.manjaro.pamac.system'
    vas. 08 15:25:06 desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 15:25:06 desktop systemd[1]: pamac-system.service: Succeeded.
    vas. 08 15:25:06 desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 15:26:11 desktop dbus-daemon[620]: [system] Activating via systemd: service name='org.manjaro.pamac.system' unit='pamac-system.service' requested by ':1.127' (uid=1000 pid=1249 comm="pamac checkupdates -q --refresh-tmp-files-dbs --do")
    vas. 08 15:26:11 desktop dbus-daemon[620]: [system] Successfully activated service 'org.manjaro.pamac.system'
    vas. 08 15:26:11 desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 15:26:11 desktop kernel: audit: type=1130 audit(1549632371.070:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 15:26:27 desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 15:26:27 desktop systemd[1]: pamac-system.service: Succeeded.
    vas. 08 15:26:27 desktop kernel: audit: type=1131 audit(1549632387.034:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 18:29:23 desktop dbus-daemon[620]: [system] Activating via systemd: service name='org.manjaro.pamac.system' unit='pamac-system.service' requested by ':1.842' (uid=1000 pid=8856 comm="pamac-manager --updates ")
    vas. 08 18:29:23 desktop dbus-daemon[620]: [system] Successfully activated service 'org.manjaro.pamac.system'
    vas. 08 18:29:23 desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 18:29:23 desktop kernel: audit: type=1130 audit(1549643363.830:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    vas. 08 18:29:52 desktop polkitd[637]: Operator of unix-session:1 successfully authenticated as unix-user:toxpal to gain TEMPORARY authorization for action org.manjaro.pamac.commit for system-bus-name::1.842 [pamac-manager --updates] (owned by unix-user:toxpal)
    vas. 08 18:30:09 desktop audit[8859]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=8859 comm="pamac-system-da" exe="/usr/bin/pamac-system-daemon" sig=11 res=1
    vas. 08 18:30:09 desktop kernel: pamac-system-da[8950]: segfault at 820 ip 00007f8e54b39070 sp 00007f8e50de7de0 error 4 in libc-2.28.so[7f8e54ad5000+14b000]
    vas. 08 18:30:09 desktop kernel: audit: type=1701 audit(1549643409.314:56): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=8859 comm="pamac-system-da" exe="/usr/bin/pamac-system-daemon" sig=11 res=1
    vas. 08 18:30:09 desktop systemd[1]: pamac-system.service: Main process exited, code=killed, status=11/SEGV
    vas. 08 18:30:09 desktop systemd[1]: pamac-system.service: Failed with result 'signal'.
    vas. 08 18:30:09 desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
    vas. 08 18:30:09 desktop kernel: audit: type=1131 audit(1549643409.651:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pamac-system comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
    vas. 08 18:30:09 desktop systemd-coredump[8958]: Process 8859 (pamac-system-da) of user 0 dumped core.
                                                     #3  0x00005583d7564029 n/a (pamac-system-daemon)
                                                     #5  0x00005583d756405e n/a (pamac-system-daemon)
                                                     #3  0x00005583d75745c1 n/a (pamac-system-daemon)
                                                     #7  0x00005583d7572704 n/a (pamac-system-daemon)
                                                     #8  0x00005583d7573107 n/a (pamac-system-daemon)
                                                     #9  0x00005583d75790ae n/a (pamac-system-daemon)
    
    
pamac70 7.3.4-11 Posts 31Views 785
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.