ImageMagick not detected despite being on Kubuntu system

[MMachado05]

I have ImageMagick installed as a deb package on my Kubuntu system, but when trying to make an export with compatibility turned on, it says it couldn't find an HEIC converter. I also tried installing the AppImage and adding it to my $PATH, but still, no dice. Is there some way I can confirm that imessage-exporter is searching for ImageMagick in the right place?

[ReagentX]

On non-Windows platforms, imessage-exporter checks the output of the type command to determine if it can use ImageMagick:

imessage-exporter/imessage-exporter/src/app/converter.rs

Lines 47 to 62 in 511d17d

	/// Determine if a shell program exists on the system
	#[cfg(not(target_family = "windows"))]
	fn exists(name: &str) -> bool {
	if let Ok(process) = Command::new("type")
	.args(vec![name])
	.stdout(Stdio::null())
	.stderr(Stdio::null())
	.stdin(Stdio::null())
	.spawn()
	{
	if let Ok(output) = process.wait_with_output() {
	return output.status.success();
	}
	};
	false
	}

When you run imessage-exporter do you get the No HEIC converter found log? Or does it fail to convert images altogether?

[MMachado05]

I get the No HEIC converter found log, and it says that it won't convert the images.

Weirdly, however, despite APT telling me I have the latest ImageMagick version installed, trying to run the magick command doesn't do anything. It may be that something is strangely configured in my system.

[ReagentX]

If you figure out why, can you post what you found here? It may help other people in the future.

[MMachado05]

I will! Uninstalling and reinstalling didn't do anything... :( I'll keep trying, though!

[MMachado05]

I may have found something; on *Ubuntu 22.04, the version of ImageMagick installed is from the 6.x series, which doesn't yet unify all the commands under the magick umbrella. Does imessage-exporter expect a version 7.x or above, @ReagentX?

[ReagentX]

Yes; v7 was released in 2016.

[MMachado05]

Why in the world is Ubuntu shipping with such an obscenely out-of-date binary... 💀

Well, at least we know what the issue is... I suppose an upgrade might be in order!