I could use some help finding these monkeys

[jonathon]

Could it be related to

Check if a reboot is neccessary

So it’s basically just a list of packages that need reboot after an update? Well, that’s a bit disappointing. But it makes it easy to check in a script. This script will tell you whether reboot is necessary, with approximately the same accuracy as eos-update-notifier: #!/bin/bash # Check whether reboot is necessary after an update. # dependency: checkupdates UPDATES=$(checkupdates) # assume packages containing these strings in name need reboot after updating REBOOT="(ucode|cryptsetup|linux|nvi…

Check if a reboot is neccessary

Here’s a script that looks for reboot-requiring packages from /etc/pacman.d/hooks/eos-reboot-required.hook. Otherwise it is quite similar to what @Kresimir showed. #!/bin/bash # Check if a reboot would be necessary after system update. DIE() { echo "Error: $1" >&2 exit 1 } Main() { local updates local hookpkgs local up hook pacman -Q eos-update-notifier >&/dev/null || DIE "sorry, package eos-update-notifier is required." readarray -t updates <<< $(checkupdates…

somehow?

[dalto]

I don’t think so. I don’t use that.

[jonathon]

Anything obvious from sudo pacman -Qkk | grep -v "0 altered" ?

[dalto]

Nothing relevant or that wouldn’t be normal to be modified.

On a positive note, I learned a new pacman command

[jonathon]

Sooooo… have you recompiled pacman or something?

I’m running out of ideas…

[Resiliencia]

@dalto

Maybe … something related to this post of yours ? ↓

Finally got my main workstation back on Arch

[Kresimir]

I see no monkeys in my computer…

[keybreak]

By far that’s funniest thread!

I’m out of ideas too, not sure what it could be except hooks…

[freggel.doe]

Seems to early for any hook to be involved.
Perhaps something to do with tar/zstd when decompressing or something the install script of the packages triggers?

In the screenshot the “monkey” output seems to coincide with glibc and systemd package processing. Do you see the same when re-installing any of those?

[manuel]

Is there some peculiar setting in your /etc/pacman.conf?

There are some settings than modify the display of progress of updates, though I don’t know about a setting that could display monkeys…

[alenbasic]

If you’re getting desperate I would probably do a grep for monkey starting at root. I doubt it’s common enough of a word in a *nix environment to have to parse a lot of false positives…

[Kresimir]

@manuel I just downloaded the source code of pacman and did a grep -r monkey on it. The word monkey appears in all of pacman’s source code and documentation exactly zero times.

This is the strangest thing ever

[alenbasic]

On that note, if I were a betting man, starting a recursive grep at /etc would probably be what I’d go for to start IMO.

[dalto]

@Resiliencia

Maybe … something related to this post of yours ? ↓

No, it was happening before I did any of that.

@freggel.doe

In the screenshot the “monkey” output seems to coincide with glibc and systemd package processing. Do you see the same when re-installing any of those?

Yes, when I reinstall those it happens again. I wish I had saved the whole output. I know it also happens when I install virtualbox. Also when I install gconf from AUR.

@manuel

Is there some peculiar setting in your /etc/pacman.conf?

It is possible but I don’t see anything obvious. I haven’t modified it heavily.

@alenbasic

I doubt it’s common enough of a word in a *nix environment to have to parse a lot of false positives…

You would be surprised. There was a lot of hits just in my .config directory.

I may have no choice though.

@alenbasic

if I were a betting man, starting a recursive grep at /etc would probably be what I’d go for

That was the first thing I tried.

I did:

/etc
~/.config
/usr/share/libalpm/hooks

[anon83136962]

I stole your frogs, the rest of you can keep the monkeys.

[otherbarry]

Any monkey systemd units, like the monkey http daemon?

systemctl list-units | grep monkey

Is the monkey line being written to pacman log?

Monkey Pacman is a game apparently, no idea if related though.

Monkey Pacman

[dalto]

@otherbarry

Any monkey systemd units, like the monkey http daemon?

No

@otherbarry

Is the monkey line being written to pacman log?

Yes, good thinking.

Here is the list of packages that caused it:

[2020-09-08T17:52:08-0500] [ALPM] upgraded glibc (2.32-3 -> 2.32-4)
[2020-09-08T17:52:08-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:08-0500] [ALPM-SCRIPTLET] Generating locales...
[2020-09-08T17:52:09-0500] [ALPM-SCRIPTLET]   en_US.UTF-8... done
[2020-09-08T17:52:09-0500] [ALPM-SCRIPTLET] Generation complete.
[2020-09-08T17:52:11-0500] [ALPM] upgraded systemd (246.3-1 -> 246.4-1)
[2020-09-08T17:52:11-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:24-0500] [ALPM] upgraded libedit (20191231_3.1-1 -> 20191231_3.1-2)
[2020-09-08T17:52:24-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:24-0500] [ALPM] upgraded openssh (8.3p1-3 -> 8.3p1-4)
[2020-09-08T17:52:24-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:27-0500] [ALPM] upgraded flashplugin (32.0.0.414-1 -> 32.0.0.433-1)
[2020-09-08T17:52:27-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:27-0500] [ALPM-SCRIPTLET] :: Flash Player reaches end-of-life on December 31, 2020. After this date,
[2020-09-08T17:52:27-0500] [ALPM-SCRIPTLET]    it will be removed from the Arch repos since it is no longer supported.
[2020-09-08T17:52:29-0500] [ALPM] upgraded kwin (5.19.4-1 -> 5.19.5-1)
[2020-09-08T17:52:29-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:31-0500] [ALPM] upgraded ksshaskpass (5.19.4-1 -> 5.19.5-1)
[2020-09-08T17:52:31-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:31-0500] [ALPM] upgraded ksysguard (5.19.4-1 -> 5.19.5-1)
[2020-09-08T17:52:31-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:35-0500] [ALPM] upgraded pepper-flash (32.0.0.414-1 -> 32.0.0.433-1)
[2020-09-08T17:52:35-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:35-0500] [ALPM-SCRIPTLET] :: Flash Player reaches end-of-life on December 31, 2020. After this date,
[2020-09-08T17:52:35-0500] [ALPM-SCRIPTLET]    it will be removed from the Arch repos since it is no longer supported.
[2020-09-08T17:52:38-0500] [ALPM] upgraded xorg-server (1.20.9-1 -> 1.20.9-2)
[2020-09-08T17:52:38-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:39-0500] [ALPM] upgraded glusterfs (1:7.6-1 -> 1:8.1-1)
[2020-09-08T17:52:39-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:39-0500] [ALPM-SCRIPTLET] -- Read https://gluster.readthedocs.io/en/latest/Upgrade-Guide/ page!
[2020-09-08T17:52:53-0500] [ALPM] upgraded virtualbox-host-dkms (6.1.12-4 -> 6.1.14-1)
[2020-09-08T17:52:53-0500] [ALPM-SCRIPTLET] monkey
[2020-09-08T17:52:54-0500] [ALPM] upgraded virtualbox (6.1.12-4 -> 6.1.14-1)
[2020-09-08T17:52:54-0500] [ALPM-SCRIPTLET] monkey

[Elloquin]

There is an AUR package…

https://aur.archlinux.org/packages/monkey/

Home page:

http://monkey-project.com/

Related

[otherbarry]

@dalto

Here is the list of packages that caused it

Find the first instance and work back, assuming your pacman logs go back that far.

See what packages were introduced between the first monkey “sighting” and the last non monkey “sighting” update.

[jonathon]

@dalto

ALPM-SCRIPTLET

What’s one of these?