Status module perl failure

[nixnut]

SYSTEM INFORMATION
OS type and version	AlmaLinux 9.7
Webmin version	2.640

have just upgraded webmin and this in status module when going to edit a service

HTTP/1.0 500 Perl execution failed Server: MiniServ/2.640 Date: Sat, 9 May 2026 12:34:44 GMT Content-type: text/html; Charset=utf-8 Connection: close

Error — Perl execution failed

Can’t locate object method “text” via package “mon_cmdmode0” (perhaps you forgot to load “mon_cmdmode0”?) at /usr/libexec/webmin/status/edit_mon.cgi line 243.

[Ilia]

Hello,

Thanks for the heads-up!

This is a bug which was already fixed! You can fix it by applying this patch:

webmin patch https://github.com/webmin/webmin/commit/a92b52f

It was also reported here:

https://github.com/webmin/webmin/issues/2686

@Jamie, we’ll need a new Webmin 2.641 release this weekend, including the latest theme updates.

Also, when doing a large Webmin release after months of changes on GitHub, it’s better to mark it as a pre-release (there’s a checkbox for that). That way, it won’t go straight to the production Virtualmin repos.

[nixnut]

thank you

[Jamie]

@Ilia

@Jamie, we’ll need a new Webmin 2.641 release this weekend, including the latest theme updates.

Yeah, I’ll do that tomorrow.

@Ilia

That way, it won’t go straight to the production Virtualmin repos.

But the repos are pushed by me as part of the release process, not from github?

[Ilia]

@Jamie

But the repos are pushed by me as part of the release process, not from github?

For Virtualmin production repos, it’s pushed automatically after you tag a new release for any repo, including Webmin. We discussed this in the design docs.

So for tomorrow’s minor release, there’s no need to mark it as a pre-release. But for something like Webmin 2.650, when a lot of changes happen, it’s better to wait a few days to catch any weird bugs like this. After a few days, all you need to do is edit the existing release and mark it as final.