am failed #906

aljustiet · 2024-09-15T05:05:23Z

Erroneous Behavior

am failed: 
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Expected Behavior

shouldn't fail

Steps to reproduce

run topgrade

Problem persists without calling from topgrade

Yes
No

Did you run topgrade through `Remote Execution`

Yes
No

If yes, does the issue still occur when you run topgrade directlly in your
remote host

Yes
No

Configuration file (Optional)

https://rentry.co/zcq7rsy9

Additional Details

Arch
Package source
Installation

AUR
Topgrade version (topgrade -V)
15.0.0

Verbose Output (`topgrade -v`)

DEBUG Step "am"
DEBUG Detected "/usr/local/bin/am" as "am"

── 10:04:25 - AM ───────────────────────────────────────────────────────────────
DEBUG Executing command `/usr/local/bin/am -u`
-----------------------------------------------------------------------------
 "AM" CAN MANAGE UPDATES FOR THE FOLLOWING PROGRAMS:

 ◆ jan 0.5.3
 ◆ thorium 126.0.6478.231
 ◆ zoom 6.1.10.1400.glibc2.27

 All self-updatable programs are excluded
-----------------------------------------------------------------------------
 >> START OF ALL PROCESSES <<
-----------------------------------------------------------------------------
DEBUG Command failed: Err(
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Location:
   src/steps/os/linux.rs:593)
DEBUG Step "am" failed: 
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Location:
   src/steps/os/linux.rs:593
am failed: 
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Location:
   src/steps/os/linux.rs:593

The text was updated successfully, but these errors were encountered:

SteveLauC · 2024-09-15T12:16:23Z

Looks like there is no error message indicating the reason behind the failure?

aljustiet · 2024-09-23T18:01:19Z

Looks like there is no error message indicating the reason behind the failure?

I just don't want to see the red color in my output. If something is in red, my brain tries to get rid of it. It says AM failed, so I guess it's failing?
Summary also says that AM is failing

── 23:01:50 - Summary ──────────────────────────────────────────────────────────
System update: OK
config-update: OK
am: FAILED
Firmware upgrades: OK
Flatpak: OK
TLDR: OK
rustup: OK

SteveLauC · 2024-09-24T01:27:07Z

Yeah, I know that step AM failed, I was saying that:

This step failed, but does not give any reason why it failed.

I need to the reason to debug the issue🤔

aljustiet · 2024-09-24T07:10:00Z

Yeah, I know that step AM failed, I was saying that:

This step failed, but does not give any reason why it failed.

I need to the reason to debug the issue🤔

Here's the verbose output:

── 11:33:31 - AM ───────────────────────────────────────────────────────────────
DEBUG Executing command `/usr/local/bin/am -u`
-----------------------------------------------------------------------------
 "AM" CAN MANAGE UPDATES FOR THE FOLLOWING PROGRAMS:

 ◆ jan 0.5.3
 ◆ thorium 126.0.6478.231
 ◆ vesktop 1.5.3
 ◆ zoom 6.1.10.1400.glibc2.27

 All self-updatable programs are excluded
-----------------------------------------------------------------------------
 >> START OF ALL PROCESSES <<
-----------------------------------------------------------------------------
DEBUG Command failed: Err(
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Location:
   src/steps/os/linux.rs:609)
DEBUG Step "am" failed: 
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Location:
   src/steps/os/linux.rs:609
am failed: 
   0: Command failed: `/usr/local/bin/am -u`
   1: `/usr/local/bin/am` failed: exit status: 1

Location:
   src/steps/os/linux.rs:609
Retry? (y)es/(N)o/(s)hell/(q)uit

Isn't it failing at the 609 line of linux.rs?

SteveLauC · 2024-09-24T08:29:19Z

There is nothing in line 609, it simply spawns the child process and runs the specified command. So that is not a reason.

Could you please try directly executing it in your terminal and give me the output?

$ am -u

aljustiet · 2024-09-24T08:30:56Z

am -u

❯ am -u
-----------------------------------------------------------------------------
 "AM" CAN MANAGE UPDATES FOR THE FOLLOWING PROGRAMS:

 ◆ jan 0.5.3
 ◆ thorium 126.0.6478.231
 ◆ vesktop 1.5.3
 ◆ zoom 6.1.10.1400.glibc2.27

 All self-updatable programs are excluded
-----------------------------------------------------------------------------
 >> START OF ALL PROCESSES <<
-----------------------------------------------------------------------------

SteveLauC · 2024-09-24T08:40:31Z

Could you please do:

$ am -u
$ echo $?

aljustiet · 2024-09-24T08:41:52Z

echo $?

It outputs 1

SteveLauC · 2024-09-24T09:49:53Z

It outputs 1

That's the root cause, normally, exit code 0 means success, and non-zero code means failure, so Topgrade treats this 1 as a sign of failure.

Gentle ping on @ivan-hc, is this normal, i.e., will AM exit with 1 on success?

ivan-hc · 2024-09-24T12:12:37Z

Using Topgrade (I refused system updates on purpose, don't pay attention to "FAILED")

Only "AM"

I can't reprduce the issue.

SteveLauC · 2024-09-25T00:51:27Z

Thanks for being here and for the help! @ivan-hc

@aljustiet Does your $ am -u successfully update the installed app images?

ivan-hc · 2024-09-25T02:18:59Z

The -u or update option of "AM"/"AppMan" does the following, in order:

update installed applications;
check for changes between the originally used installation script and the one in the repository;
update modules related to non-core options (there are only 4 scripts);
update "AM"/"AppMan" itself.

The only one that can cause problems is point 1, as the following scenarios can occur:

if the app to update is hosted on github.com, api.github.com is contacted too many times, and github.com has an hourly limit on calls to its APIs;
if the app to update has an origin site that has been changed by the author, deleted, or is no longer reachable.

In both cases this does not prevent the -u option from continuing! It will keep update apps that do not have such problems at point 1 and continue to perform steps 2, 3 and 4.

That said, what happens in this issue is not related to "AM" malfunctions.

SteveLauC · 2024-09-25T02:32:27Z

Hi, thanks for the reply!

The only one that can cause problems is point 1, as the following scenarios can occur:

if the app to update is hosted on github.com, api.github.com is contacted too many times, and github.com has an hourly > limit on calls to its APIs;

if the app to update has an origin site that has been changed by the author, deleted, or is no longer reachable.

Will "AM" warn the user if the above things happen?

ivan-hc · 2024-09-25T02:44:03Z

Normally you would get a notification that the app is updating and a notification that the app is updated... but nothing was updated.

My co-worker has about fifty programs installed via AppMan, and in the early days he was doing so much testing that at some point his desktop would fill up with update notifications, but in reality the script that updates the application had simply not contacted the update URL, recognizing that it had changed.

However, a couple of months ago we upgraded all the install scripts, adding an exit 1 in case the download failed, so the problem of numerous notifications should no longer occur.

ivan-hc · 2024-09-25T02:53:51Z

The above limitations of the github API can be bypassed by adding an alphanumeric key with the apikey option, while the limitations of apps hosted on random sites are not traceable.

You know, the purpose of portable apps (and in particular of AppImages) is to be downloadable from the developer's site or repository. And that's what every script in my repository does.

"AM" is a sort of AUR for AppImage packages and other portable apps: it intercepts the URL, executes the dedicated commands depending on whether it is an AppImage, a TAR, a ZIP or a static binary, and finally integrates it into the system, with symbolic links, launchers and icons where necessary. It is not a centralized archive of physical packages (I wish it were like that).

ivan-hc · 2024-09-25T02:57:41Z

An example of apps that are difficult to trace: "inkscape", the AppImage is hosted on the official site, and sometimes it happens that the owners change the interface, but also the links or paths where the apps are hosted... and the last time their site was down (they had failed to update the SSL certificates, I think).

These are unexpected events that can happen.

ivan-hc · 2024-09-25T03:00:27Z

But again, updates for other apps that don't have these problems will continue, in fact the apps update in parallel! It doesn't matter if another app fails. The -u option will continue until the end.

If -u fails completelly at all it means one thing: github.com is down.

And in that case, "AM" would recognize that github.com is down, so it will give an exit with the message ""AM" is offline, please check your internet connection and try again".

SteveLauC · 2024-09-25T03:47:29Z

Ok, thanks for the detailed explanations!

So for Topgrade, we still need to treat this exit code 1 as an error, so nothing to fix here, closing.

@aljustiet you need to figure out the issue you have, either you triggered the GH API rate limit, or you have an application whose URL recorded by AM's install script became invalid.

Appreciate the help @ivan-hc! Thanks!

ivan-hc · 2024-09-25T03:59:26Z

@aljustiet I have just installed zoom, thorium and jan as you have shown in the first comment, no issues here when updating

aljustiet · 2024-09-25T17:23:11Z

@aljustiet I have just installed zoom, thorium and jan as you have shown in the first comment, no issues here when updating

What do you get for echo $? after am -u finishes? I get this.

ivan-hc · 2024-09-25T17:47:25Z

anyway, your am -u has been interrupted, as a CTRL+C action or something.

Is your "AM" updated to the last version? Run am -s to update only AM and modules.

ivan-hc · 2024-09-25T17:48:29Z

Also, what SHELL are you using?

aljustiet · 2024-09-25T17:48:51Z

Also, what SHELL are you using?

I use zsh, but with bash I have the same behavior

ivan-hc · 2024-09-25T17:49:42Z

Try am -s and then retry.

aljustiet · 2024-09-25T17:50:19Z

Try am -s and then retry.

I tried it, but nothing changed.

aljustiet · 2024-09-25T17:51:27Z

anyway, your am -u has been interrupted, as a CTRL+C action or something.

Is your "AM" updated to the last version? Run am -s to update only AM and modules.

I haven't terminated the am using ctrl+c. After it "finishes", it still outputs, and I don't why so

aljustiet · 2024-09-25T17:53:28Z

I have this /usr/local/bin/am

ivan-hc · 2024-09-25T18:00:33Z

your file is different from my /opt/am/APP-MANAGER

reinstall AM

am -R am && wget https://raw.githubusercontent.com/ivan-hc/AM/main/INSTALL && chmod a+x ./INSTALL && sudo ./INSTALL

be sure that you have not a file named INSTALL in your working directory

ivan-hc · 2024-09-27T19:45:53Z

let do another test then, replace the whole function at line 150

function _update_all_apps() {
	for f in "$APPSPATH"/*/; do
		cd "$f" 2>/dev/null || exit 1
		arg=$(printf '%s\n' "${PWD##*/}")
		if test -f "$APPSPATH"/"$arg"/AM-updater; then
			_update_app
		fi
	done
	wait
	echo "$DIVIDING_LINE"
	_update_determine_apps_version_changes
	rm -Rf "$APPSPATH/*/tmp"
}

with this

function _update_all_apps() {
	PID=$!
	for f in "$APPSPATH"/*/; do
		cd "$f" 2>/dev/null || exit 1
		arg=$(printf '%s\n' "${PWD##*/}")
		if test -f "$APPSPATH"/"$arg"/AM-updater; then
			_update_app
		fi
	done
	wait $PID
	echo "$DIVIDING_LINE"
	_update_determine_apps_version_changes
	rm -Rf "$APPSPATH/*/tmp"
}

and run am -u --apps

aljustiet · 2024-09-27T19:48:25Z

let do another test then, replace the whole function at line 150

function _update_all_apps() {
	for f in "$APPSPATH"/*/; do
		cd "$f" 2>/dev/null || exit 1
		arg=$(printf '%s\n' "${PWD##*/}")
		if test -f "$APPSPATH"/"$arg"/AM-updater; then
			_update_app
		fi
	done
	wait
	echo "$DIVIDING_LINE"
	_update_determine_apps_version_changes
	rm -Rf "$APPSPATH/*/tmp"
}

with this

function _update_all_apps() {
	PID=$!
	for f in "$APPSPATH"/*/; do
		cd "$f" 2>/dev/null || exit 1
		arg=$(printf '%s\n' "${PWD##*/}")
		if test -f "$APPSPATH"/"$arg"/AM-updater; then
			_update_app
		fi
	done
	wait $PID
	echo "$DIVIDING_LINE"
	_update_determine_apps_version_changes
	rm -Rf "$APPSPATH/*/tmp"
}

and run am -u --apps

Still having the same behavior and code 1.
1050 line*

ivan-hc · 2024-09-27T19:56:58Z

can you share here both your zshrc and bashrc?

ivan-hc · 2024-09-27T19:58:29Z

can you share here both your zshrc and bashrc?

and maybe also your .profile file, thanks

ivan-hc · 2024-09-27T20:03:55Z

@aljustiet just curious, have you got appimagelauncher installed on your system?

I ask because it conflicts with AM and other AppImage managers https:/ivan-hc/AM?tab=readme-ov-file#failed-to-open-squashfs-image

Samueru-sama · 2024-09-27T21:01:42Z

~/.bashrc is created automatically, I'm not an expert about ZSH, in this could help me @Samueru-sama

I haven't been able to reproduce the issue.

aljustiet · 2024-09-28T06:31:16Z

can you share here both your zshrc and bashrc?

and maybe also your .profile file, thanks

zshrc.txt
bashrc.txt
profile.txt
bash_profile.txt

aljustiet · 2024-09-28T06:34:51Z

@aljustiet just curious, have you got appimagelauncher installed on your system?

I ask because it conflicts with AM and other AppImage managers https:/ivan-hc/AM?tab=readme-ov-file#failed-to-open-squashfs-image

Yes, I have it installed

aljustiet · 2024-09-28T06:39:43Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

ivan-hc · 2024-09-28T07:29:50Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

remove it and reboot, then try again.

In my experience, many users had issues when AppImageLauncher is installed, as you can see from the issues linked in the throubleshot I linked above.

Also, AppImageLauncher is no more developed from 2 years, if you need a tool that does the same thing, use GearLever (flatpak) or the --launcher option available in AM (yes, AM can do also this).

Samueru-sama · 2024-09-28T07:37:16Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

What appimage isn't in the AM repo btw?

AppImage launcher is basically abandoned (the maintainer is still active on github so I don't know why it hasn't been updated), it doesn't support the static runtime so the appimages of Cemu, PCSX2, Zen Browser, etc and all the appimages that Ivan and I make cannot work when appimagelauncher is installed, you cannot even launch them.

aljustiet · 2024-09-28T07:37:35Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

remove it and reboot, then try again.

In my experience, many users had issues when AppImageLauncher is installed, as you can see from the issues linked in the throubleshot I linked above.

Also, AppImageLauncher is no more developed from 2 years, if you need a tool that does the same thing, use GearLever (flatpak) or the --launcher option available in AM (yes, AM can do also this).

I removed it using pacman and deleted leftovers in ~/.local/share/applications, then rebooted, but still having the same behavior.

aljustiet · 2024-09-28T07:39:19Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

What appimage isn't in the AM repo btw?

AppImage launcher is basically abandoned (the maintainer is still active on github so I don't know why it hasn't been updated), it doesn't support the static runtime so the appimages of Cemu, PCSX2, Zen Browser, etc and all the appimages that Ivan and I make cannot work when appimagelauncher is installed, you cannot even launch them.

KeePassXC snapshot builds

Samueru-sama · 2024-09-28T07:43:59Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

What appimage isn't in the AM repo btw?
AppImage launcher is basically abandoned (the maintainer is still active on github so I don't know why it hasn't been updated), it doesn't support the static runtime so the appimages of Cemu, PCSX2, Zen Browser, etc and all the appimages that Ivan and I make cannot work when appimagelauncher is installed, you cannot even launch them.

KeePassXC snapshot builds

Those are like devel builds from here right?

Regarding the issue, I would test using appman and install a few apps and then run appman -u and check if it doesn't exit with zero.

aljustiet · 2024-09-28T07:49:14Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

What appimage isn't in the AM repo btw?
AppImage launcher is basically abandoned (the maintainer is still active on github so I don't know why it hasn't been updated), it doesn't support the static runtime so the appimages of Cemu, PCSX2, Zen Browser, etc and all the appimages that Ivan and I make cannot work when appimagelauncher is installed, you cannot even launch them.

KeePassXC snapshot builds

Those are like devel builds from here right?

Regarding the issue, I would test using appman and install a few apps and then run appman -u and check if it doesn't exit with zero.

Yes, they're from there.
I installed Appman, then keepassxc, and it doesn't exit with code 1, btw.

aljustiet · 2024-09-28T07:50:34Z

Should I replace AM with appman then?

Samueru-sama · 2024-09-28T08:05:19Z

Should I replace AM with appman then?

As long as you are happy with that. I personally find appman better since I'm fine with installing appimages in $HOME and I don't need root to use it.

However this issue is very weird nonetheless, you might wanna try slowly install and remove the apps from AM to AppMan and do am -u on both until you find a possible culprit.

aljustiet · 2024-09-28T08:14:55Z

Should I replace AM with appman then?

As long as you are happy with that. I personally find appman better since I'm fine with installing appimages in $HOME and I don't need root to use it.

However this issue is very weird nonetheless, you might wanna try slowly install and remove the apps from AM to AppMan and do am -u on both until you find a possible culprit.

I removed all apps in am, and it still finished with code 1.
I will just port all my apps to AppMan then.

Samueru-sama · 2024-09-28T08:18:45Z

Should I replace AM with appman then?

As long as you are happy with that. I personally find appman better since I'm fine with installing appimages in $HOME and I don't need root to use it.
However this issue is very weird nonetheless, you might wanna try slowly install and remove the apps from AM to AppMan and do am -u on both until you find a possible culprit.

I removed all apps in am, and it still finished with code 1.

run am -r am and if you want, reinstall am again and check if it still exits with 1.

aljustiet · 2024-09-28T08:21:09Z

Should I replace AM with appman then?

As long as you are happy with that. I personally find appman better since I'm fine with installing appimages in $HOME and I don't need root to use it.
However this issue is very weird nonetheless, you might wanna try slowly install and remove the apps from AM to AppMan and do am -u on both until you find a possible culprit.

I removed all apps in am, and it still finished with code 1.

run am -r am and if you want, reinstall am again and check if it still exits with 1.

Yet, it still exits with 1.

ivan-hc · 2024-09-28T08:52:21Z

zshrc.txt bashrc.txt profile.txt bash_profile.txt

I'm unable to download the bashrc

I have seen a lot of stuff in the zshrc file, while .profile is really different from mine.

The zshrc file also contain several aliases and export PATH=

@Samueru-sama have you seen the files?

EDIT: again, who knows if among all these changes there is something that affects the normal behaviour of AM, and who know if it would work with a "virgin" file

Samueru-sama · 2024-09-28T08:54:21Z

Yes, it still exits with 1.

Yeah seems like some deeper debugging with set -x in am might be needed.

Anyway I just PRed the devel buidls of keepassxc once merged you will be able to get the snapshot builds by running appman -i keepassxc-devel.

@ivan-hc I'm not sure that the shell config files have anything to do here given that appman doesn't have the issue.

aljustiet · 2024-09-28T08:55:56Z

zshrc.txt bashrc.txt profile.txt bash_profile.txt

I'm unable to download the bashrc

I have seen a lot of stuff in the zshrc file, while .profile is really different from mine.

The zshrc file also contain several aliases and export PATH=

@Samueru-sama have you seen the files?

EDIT: again, who knows if among all these changes there is something that affects the normal behaviour of AM, and who know if it would work with a "virgin" file

I don't think so. I changed my default shell both on root and user to bash. And rebooted, and ran am -u, but still got the same behavior.

ivan-hc · 2024-09-28T09:28:18Z

I don't use ZSH, but these are my .bashrc and .profile

bashrc.txt
profile.txt

can you give them a try?

aljustiet · 2024-09-28T09:33:32Z

I don't use ZSH, but these are my .bashrc and .profile

bashrc.txt profile.txt

can you give them a try?

Should I reboot changing the default shell after copying them into their proper locations?
Right now if I run bash from zsh, then run am -u it still finishes with code 1.

ivan-hc · 2024-09-28T09:34:43Z

yes, you should change the default shell first and reboot, and after that you can do a backup of the four files you have and use just these two.

aljustiet · 2024-10-07T13:19:10Z

Should I remove it? I use it when there isn't appimage that I want in the AM repos

remove it and reboot, then try again.

In my experience, many users had issues when AppImageLauncher is installed, as you can see from the issues linked in the throubleshot I linked above.

Also, AppImageLauncher is no more developed from 2 years, if you need a tool that does the same thing, use GearLever (flatpak) or the --launcher option available in AM (yes, AM can do also this).

But it doesn't work.
I launched the electrum-ltc AppImage using it; it created the file in ~/.local/bin, but it isn't desktop, and because of that, it's usable only in dmenu mode.
But I use rofi, and it doesn't appear there.

ivan-hc · 2024-10-07T16:33:06Z

Recap:

I have this /usr/local/bin/am

your file is different from my /opt/am/APP-MANAGER
reinstall AM
am -R am && wget https://raw.githubusercontent.com/ivan-hc/AM/main/INSTALL && chmod a+x ./INSTALL && sudo ./INSTALL
be sure that you have not a file named INSTALL in your working directory

I ran this command, and I got this output:

❯ am -R am && wget https://raw.githubusercontent.com/ivan-hc/AM/main/INSTALL && chmod a+x ./INSTALL && sudo ./INSTALL
------------------------------------------------------------------------------
 "am" has been removed!
------------------------------------------------------------------------------
--2024-09-26 10:22:33--  https://raw.githubusercontent.com/ivan-hc/AM/main/INSTALL
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.111.133, 185.199.109.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2467 (2.4K) [text/plain]
Saving to: ‘INSTALL.1’

INSTALL.1               100%[===============================>]   2.41K  --.-KB/s    in 0.006s  

2024-09-26 10:22:39 (417 KB/s) - ‘INSTALL.1’ saved [2467/2467]

--------------------------------------------------------------------------
 Installing "AM" in /opt/am
--------------------------------------------------------------------------
 Installing modules
 ◆ Downloading database.am...
 ◆ Downloading management.am...
 ◆ Downloading sandboxes.am...
 ◆ Downloading install.am...
 ◆ Downloading template.am...
--------------------------------------------------------------------------
 "AM" has been successfully installed!
 Please, run "am -h" to see the list of the options.
--------------------------------------------------------------------------
~ ❯

I checked the /usr/local/bin/am using ls -l, and it turns out that it's symlink to /opt/am/APP-MANAGER.

May it be that it is updating something and you need to wait?

No, the process finishes.
1.mp4

let do another test, remove or comment the line1058, the one containing only wait and try am -u --apps again

It still finishes with 1, which makes topgrade fail the am.

@aljustiet just curious, have you got appimagelauncher installed on your system?
I ask because it conflicts with AM and other AppImage managers https:/ivan-hc/AM?tab=readme-ov-file#failed-to-open-squashfs-image

Yes, I have it installed

Should I remove it? I use it when there isn't appimage that I want in the AM repos

remove it and reboot, then try again.
In my experience, many users had issues when AppImageLauncher is installed, as you can see from the issues linked in the throubleshot I linked above.
Also, AppImageLauncher is no more developed from 2 years, if you need a tool that does the same thing, use GearLever (flatpak) or the --launcher option available in AM (yes, AM can do also this).

I removed it using pacman and deleted leftovers in ~/.local/share/applications, then rebooted, but still having the same behavior.

Should I replace AM with appman then?

As long as you are happy with that. I personally find appman better since I'm fine with installing appimages in $HOME and I don't need root to use it.
However this issue is very weird nonetheless, you might wanna try slowly install and remove the apps from AM to AppMan and do am -u on both until you find a possible culprit.

I removed all apps in am, and it still finished with code 1.

run am -r am and if you want, reinstall am again and check if it still exits with 1.

Yet, it still exits with 1.

I don't use ZSH, but these are my .bashrc and .profile
bashrc.txt profile.txt
can you give them a try?

Should I reboot changing the default shell after copying them into their proper locations? Right now if I run bash from zsh, then run am -u it still finishes with code 1.

Should I remove it? I use it when there isn't appimage that I want in the AM repos

remove it and reboot, then try again.
In my experience, many users had issues when AppImageLauncher is installed, as you can see from the issues linked in the throubleshot I linked above.
Also, AppImageLauncher is no more developed from 2 years, if you need a tool that does the same thing, use GearLever (flatpak) or the --launcher option available in AM (yes, AM can do also this).

But it doesn't work. I launched the electrum-ltc AppImage using it; it created the file in ~/.local/bin, but it isn't desktop, and because of that, it's usable only in dmenu mode. But I use rofi, and it doesn't appear there.

@aljustiet its better if I move this issue to the AM repo directly

aljustiet added the C-bug Something isn't working label Sep 15, 2024

SteveLauC closed this as completed Sep 25, 2024

Samueru-sama mentioned this issue Sep 28, 2024

Add keepassxc-devel ivan-hc/AM#966

Merged

ivan-hc mentioned this issue Oct 7, 2024

Cannot update apps in bulk with "am -u", the process is stuck on second app. To reproduce: run echo $?, result should be "0" (correct), not "1" ivan-hc/AM#991

Closed

am failed #906

am failed #906

Comments

aljustiet commented Sep 15, 2024

Erroneous Behavior

Expected Behavior

Steps to reproduce

Problem persists without calling from topgrade

Did you run topgrade through Remote Execution

Configuration file (Optional)

Additional Details

Verbose Output (topgrade -v)

SteveLauC commented Sep 15, 2024

aljustiet commented Sep 23, 2024 • edited Loading

SteveLauC commented Sep 24, 2024

aljustiet commented Sep 24, 2024

SteveLauC commented Sep 24, 2024

aljustiet commented Sep 24, 2024

SteveLauC commented Sep 24, 2024

aljustiet commented Sep 24, 2024

SteveLauC commented Sep 24, 2024

ivan-hc commented Sep 24, 2024

SteveLauC commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

SteveLauC commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

ivan-hc commented Sep 25, 2024 • edited Loading

SteveLauC commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

aljustiet commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

aljustiet commented Sep 25, 2024 • edited Loading

ivan-hc commented Sep 25, 2024

aljustiet commented Sep 25, 2024

aljustiet commented Sep 25, 2024

aljustiet commented Sep 25, 2024

ivan-hc commented Sep 25, 2024

ivan-hc commented Sep 27, 2024

aljustiet commented Sep 27, 2024 • edited Loading

ivan-hc commented Sep 27, 2024

ivan-hc commented Sep 27, 2024

ivan-hc commented Sep 27, 2024

Samueru-sama commented Sep 27, 2024 • edited Loading

aljustiet commented Sep 28, 2024 • edited Loading

aljustiet commented Sep 28, 2024

aljustiet commented Sep 28, 2024

ivan-hc commented Sep 28, 2024

Samueru-sama commented Sep 28, 2024

aljustiet commented Sep 28, 2024 • edited Loading

aljustiet commented Sep 28, 2024

Samueru-sama commented Sep 28, 2024

aljustiet commented Sep 28, 2024 • edited Loading

aljustiet commented Sep 28, 2024

Samueru-sama commented Sep 28, 2024

aljustiet commented Sep 28, 2024 • edited Loading

Samueru-sama commented Sep 28, 2024

aljustiet commented Sep 28, 2024 • edited Loading

ivan-hc commented Sep 28, 2024 • edited Loading

Samueru-sama commented Sep 28, 2024

aljustiet commented Sep 28, 2024

ivan-hc commented Sep 28, 2024

aljustiet commented Sep 28, 2024

ivan-hc commented Sep 28, 2024

aljustiet commented Oct 7, 2024

ivan-hc commented Oct 7, 2024

Did you run topgrade through `Remote Execution`

Verbose Output (`topgrade -v`)

aljustiet commented Sep 23, 2024 •

edited

Loading

ivan-hc commented Sep 25, 2024 •

edited

Loading

aljustiet commented Sep 25, 2024 •

edited

Loading

aljustiet commented Sep 27, 2024 •

edited

Loading

Samueru-sama commented Sep 27, 2024 •

edited

Loading

aljustiet commented Sep 28, 2024 •

edited

Loading

aljustiet commented Sep 28, 2024 •

edited

Loading

aljustiet commented Sep 28, 2024 •

edited

Loading

aljustiet commented Sep 28, 2024 •

edited

Loading

aljustiet commented Sep 28, 2024 •

edited

Loading

ivan-hc commented Sep 28, 2024 •

edited

Loading