Different packagers update this, so assigning this update globally.

Assignee: bugsquad => pkg-bugs

cockpit in cauldron is now 338.
However, I don't know how to have it working.

Version: Cauldron => 9
Whiteboard: MGA9TOO => (none)
CC: (none) => yvesbrungard

(In reply to papoteur from comment #2)
> cockpit in cauldron is now 338.
> However, I don't know how to have it working.

Thank you I did not play with this @Ezequiel can you give some light in this?

I forget to add Ezequiel's mail I backported cockpit 338 to blogdrake's 
Repository can you test if works and if cockpit-machines works too?

CC: (none) => ezequiel_partida

Created attachment 14999 [details]
Tested spec of cockpit 338

@papotuer I fine tune cockpit 338 and cokpit-machines (bug#34056) with the help of Ezequiel's test is fine for you the I:

- Update cockpit in cauldron for custom pam and some fixes that I have to do to make it build in copr
- Updata cockpit version in mageia 9
- Import cockpit-machines in cauldron

Created attachment 15000 [details]
custom cokpit.pam

I reworked upstream cockpit.pam with the modifications done in current cockpit in mageia 9

@Jani a question before send cockpit to 9/core/updates_testing (maintdb says belong to nobody)
The CVE is fixed in version 320, but can I use 338 for mageia 9 too ?

I katnatek,
For getting admin privileges (cauldron), user should be in sudoers, what is not the default in Mageia configuration for now.
Password for the user is asked, but fails.
Is there means to ask for root anthentication in settings?

For memory, /etc/nsswitch.conf has to be edited by adding systemd on lines passwd, shadow and group
glibc is now modified for the default configuration at installation time, but old installations have to be updated manually. This should go in errata.

(In reply to katnatek from comment #7)
> @Jani a question before send cockpit to 9/core/updates_testing (maintdb says
> belong to nobody)
> The CVE is fixed in version 320, but can I use 338 for mageia 9 too ?

I don't have an answer for this one as I don't really care about cockpit.

CC: jani.valimaa => (none)

(In reply to papoteur from comment #8)
> I katnatek,
> For getting admin privileges (cauldron), user should be in sudoers, what is
> not the default in Mageia configuration for now.
> Password for the user is asked, but fails.
> Is there means to ask for root anthentication in settings?
> 
> For memory, /etc/nsswitch.conf has to be edited by adding systemd on lines
> passwd, shadow and group
> glibc is now modified for the default configuration at installation time,
> but old installations have to be updated manually. This should go in errata.

I wonder if the change of system-auth for password-auth in cockpit.pam is related or not with that issue.

OK need to rework the cockpit.pam again /etc/pam.d/password-auth is not in official packages I will think un import authselect for cauldron ar make the same fix in pam file

Created attachment 15002 [details]
Cockpit update log

I did update to -1 release and caught the issue with the pam file
Then update to -1.1 release

installing cockpit-networkmanager-338-1.1.mga9.noarch.rpm cockpit-storaged-338-1.1.mga9.noarch.rpm cockpit-bridge-338-1.1.mga9.noarch.rpm cockpit-ws-selinux-338-1.1.mga9.x86_64.rpm cockpit-338-1.1.mga9.x86_64.rpm cockpit-system-338-1.1.mga9.noarch.rpm cockpit-packagekit-338-1.1.mga9.noarch.rpm cockpit-ws-338-1.1.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ##################################################################################################
      1/8: cockpit-bridge        ##################################################################################################
      2/8: cockpit-system        ##################################################################################################
      3/8: cockpit-networkmanager
                                 ##################################################################################################
      4/8: cockpit-storaged      ##################################################################################################
      5/8: cockpit-packagekit    ##################################################################################################
      6/8: cockpit-ws-selinux    ##################################################################################################
      7/8: cockpit-ws            ##################################################################################################
**** WARNING:
**** WARNING: pam_cockpit_cert is a no-op and will be removed in a
**** WARNING: future release; remove it from your /etc/pam.d/cockpit.
**** WARNING:
      8/8: cockpit               ##################################################################################################
      1/8: removing cockpit-338-1.mga9.x86_64
                                 ##################################################################################################
      2/8: removing cockpit-networkmanager-338-1.mga9.noarch
                                 ##################################################################################################
      3/8: removing cockpit-packagekit-338-1.mga9.noarch
                                 ##################################################################################################
      4/8: removing cockpit-storaged-338-1.mga9.noarch
                                 ##################################################################################################
      5/8: removing cockpit-system-338-1.mga9.noarch
                                 ##################################################################################################
      6/8: removing cockpit-ws-338-1.mga9.x86_64
                                 ##################################################################################################
      7/8: removing cockpit-ws-selinux-338-1.mga9.x86_64
                                 ##################################################################################################
      8/8: removing cockpit-bridge-338-1.mga9.noarch
                                 ##################################################################################################

systemctl start cockpit-wsinstance-http.service
systemctl status cockpit-wsinstance-http.service 
● cockpit-wsinstance-http.service - Cockpit Web Service http instance
     Loaded: loaded (/usr/lib/systemd/system/cockpit-wsinstance-http.service; static)
     Active: active (running) since Sat 2025-05-31 20:08:30 CST; 7s ago
TriggeredBy: ● cockpit-wsinstance-http.socket
       Docs: man:cockpit-ws(8)
   Main PID: 120445 (cockpit-ws)
      Tasks: 3 (limit: 6877)
     Memory: 888.0K
        CPU: 81ms
     CGroup: /system.slice/cockpit-wsinstance-http.service
             └─120445 /usr/libexec/cockpit-ws --no-tls --port=0

may 31 20:08:30 jgrey.phoenix systemd[1]: Started cockpit-wsinstance-http.service.

Then open http://localhost:9090 in browser get the login page, star session with my user , get a warning about I'm in limited mode (I'm not sudoer)
The message about pam_cockpit_cert point that we need to take care of the cockpit.pam in future releases

Is good to me but I'll not test all the other modules not included in my update log
Look like despite the networkmanager packages fetched, the tool works well without switching to networkmanager

Sorry, the following package cannot be selected:

- cockpit-kdump-338-1.1.mga9.noarch (due to unsatisfied /usr/bin/kdumpctl)

CC: (none) => herman.viaene

And
Sorry, the following package cannot be selected:

- cockpit-selinux-338-1.1.mga9.noarch (due to unsatisfied setroubleshoot-server[>= 3.3.3])

# systemctl start httpd
# systemctl -l status httpd
● httpd.service - The Apache HTTP Server
     Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; preset: disabled)
     Active: active (running) since Mon 2025-06-02 11:28:48 CEST; 16s ago
   Main PID: 54071 (/usr/sbin/httpd)
     Status: "Total requests: 0; Idle/Busy workers 100/0;Requests/sec: 0; Bytes served/sec:   0 B/sec"
      Tasks: 6 (limit: 8806)
     Memory: 24.2M
        CPU: 719ms
     CGroup: /system.slice/httpd.service
             ├─54071 /usr/sbin/httpd -DFOREGROUND
             ├─54180 /usr/sbin/httpd -DFOREGROUND
             ├─54181 /usr/sbin/httpd -DFOREGROUND
             ├─54182 /usr/sbin/httpd -DFOREGROUND
             ├─54183 /usr/sbin/httpd -DFOREGROUND
             └─54185 /usr/sbin/httpd -DFOREGROUND

Jun 02 11:28:47 mach3.hviaene.thuis systemd[1]: Starting httpd.service...
Jun 02 11:28:48 mach3.hviaene.thuis systemd[1]: Started httpd.service.

# systemctl start cockpit-wsinstance-http.service
A dependency job for cockpit-wsinstance-http.service failed. See 'journalctl -xe' for details.

# journalctl -xe
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit cockpit-session-socket-user.service has successfully entered the 'dead' state.
Jun 02 11:30:46 mach3.hviaene.thuis systemd[1]: Stopped cockpit-session-socket-user.service.
░░ Subject: A stop job for unit cockpit-session-socket-user.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit cockpit-session-socket-user.service has finished.
░░ 
░░ The job identifier is 3756 and the job result is done.
Jun 02 11:30:47 mach3.hviaene.thuis systemd[1]: cockpit-issue.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit cockpit-issue.service has successfully entered the 'dead' state.
Jun 02 11:30:47 mach3.hviaene.thuis systemd[1]: Finished cockpit-issue.service.
░░ Subject: A start job for unit cockpit-issue.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit-issue.service has finished successfully.
░░ 
░░ The job identifier is 3752.
...skipping...
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit cockpit-session-socket-user.service has successfully entered the 'dead' state.
Jun 02 11:30:46 mach3.hviaene.thuis systemd[1]: Stopped cockpit-session-socket-user.service.
░░ Subject: A stop job for unit cockpit-session-socket-user.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit cockpit-session-socket-user.service has finished.
░░ 
░░ The job identifier is 3756 and the job result is done.
Jun 02 11:30:47 mach3.hviaene.thuis systemd[1]: cockpit-issue.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit cockpit-issue.service has successfully entered the 'dead' state.
Jun 02 11:30:47 mach3.hviaene.thuis systemd[1]: Finished cockpit-issue.service.
░░ Subject: A start job for unit cockpit-issue.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit-issue.service has finished successfully.
░░ 
░░ The job identifier is 3752.

Hello Herman,
You don't have to do this
> systemctl start cockpit-wsinstance-http.service

You have to connect to http://localhost:9090
But previously, you need to configure by changing 
/etc/nsswitch.conf
by adding systemd to lines shadow, passwd and group. See comment 8

So, edited /etc/nsswitch.conf, rebooted to be sure the system has seen the changes, but connect to http://localhost:9090 gives:

Unable to connect

Firefox can’t establish a connection to the server at localhost:9090.

You have to open port 9090/tcp in firewall configuration.
And as root:
systemctl enable cockpit.socket

Ooops, there is still a problem with our Firefox: 
Ce navigateur est trop vieux pour faire fonctionner la console Web (manquant selector(:is():where()))
(this browser is too old for running web console: missing selector(:is():where()))

    Firewall was already opened, did enable, but still same error.
    Looked at bug 29890 and
    # systemctl start cockpit
    [root@mach3 ~]# systemctl -l status cockpit
    ● cockpit.service - Cockpit Web Service
         Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static)
         Active: active (running) since Mon 2025-06-02 14:27:19 CEST; 16s ago
    TriggeredBy: ● cockpit.socket
           Docs: man:cockpit-ws(8)
        Process: 6272 ExecStartPre=/usr/libexec/cockpit-certificate-ensure --for-cockpit-tls (code=exited, status=0/SUCCESS)
       Main PID: 6302 (cockpit-tls)
          Tasks: 1 (limit: 8806)
         Memory: 2.0M
            CPU: 4.761s
         CGroup: /system.slice/cockpit.service
                 └─6302 /usr/libexec/cockpit-tls

    Jun 02 14:27:14 mach3.hviaene.thuis systemd[1]: Starting cockpit.service...
    Jun 02 14:27:15 mach3.hviaene.thuis cockpit-certificate-ensure[6289]: /usr/libexec/cockpit-certificate-helper: line 31: sscg: command not found
    Jun 02 14:27:18 mach3.hviaene.thuis cockpit-certificate-ensure[6290]: ...+......+.....+............+.+...........+...+.+......+....................+.+++++++>
    Jun 02 14:27:19 mach3.hviaene.thuis cockpit-certificate-ensure[6290]: ......+........+..................................+........+++++++++++++++++++++++++++>
    Jun 02 14:27:19 mach3.hviaene.thuis cockpit-certificate-ensure[6290]: -----
    Jun 02 14:27:19 mach3.hviaene.thuis systemd[1]: Started cockpit.service.

    Now I get into a login page, but here I am stuck again:
    my normal user is not accepted without any message, just returns to the login page.
    Trying to login as root is also rejected with "Permission denied"

(In reply to papoteur from comment #21)
> Ooops, there is still a problem with our Firefox: 
> Ce navigateur est trop vieux pour faire fonctionner la console Web (manquant
> selector(:is():where()))
> (this browser is too old for running web console: missing
> selector(:is():where()))

Exist a fix for that, I have not caught because I not use ESR firefox

Thank you Herman for your test I can' find why cockpit-wsinstance-http.service not works for you in the text you provide

I will disable selinux in general and kdump for mageia 9 if kdump-utils not builds in mageia 9

Herman, I think that your problem is with nsswitch.conf
you should have

passwd:         files systemd
shadow:         files systemd
group:          files systemd

Running Firefox release, I pass the login phase.
To gain admin credentials, you have to configure sudo access

Would it be possible to make cockpit-ws not require cockpit-ws-selinux (maybe just recommend)?

$ urpmq --requires cockpit-ws | grep selinux
cockpit-ws: cockpit-ws-selinux[== 338-1.1.mga9]

CC: (none) => mageia

(In reply to PC LX from comment #25)
> Would it be possible to make cockpit-ws not require cockpit-ws-selinux
> (maybe just recommend)?
> 
> $ urpmq --requires cockpit-ws | grep selinux
> cockpit-ws: cockpit-ws-selinux[== 338-1.1.mga9]

Not sure, I wish to disable selinux packages, I have to check if is a spec require or autodetect require

(In reply to katnatek from comment #23)
> (In reply to papoteur from comment #21)
> > Ooops, there is still a problem with our Firefox: 
> > Ce navigateur est trop vieux pour faire fonctionner la console Web (manquant
> > selector(:is():where()))
> > (this browser is too old for running web console: missing
> > selector(:is():where()))
> 
> Exist a fix for that, I have not caught because I not use ESR firefox

I am afraid this is a bug in our firefox,  I use Mozilla Firefox 128.11 ESR and I could login

(In reply to katnatek from comment #27)
> (In reply to katnatek from comment #23)
> > (In reply to papoteur from comment #21)
> > > Ooops, there is still a problem with our Firefox: 
> > > Ce navigateur est trop vieux pour faire fonctionner la console Web (manquant
> > > selector(:is():where()))
> > > (this browser is too old for running web console: missing
> > > selector(:is():where()))
> > 
> > Exist a fix for that, I have not caught because I not use ESR firefox
> 
> I am afraid this is a bug in our firefox,  I use Mozilla Firefox 128.11 ESR
> and I could login

As workaround use chromium-browser

(In reply to katnatek from comment #28)for that, I have not caught because I not use ESR firefox
> > 
> > I am afraid this is a bug in our firefox,  I use Mozilla Firefox 128.11 ESR
> > and I could login
> 
> As workaround use chromium-browser

I tried from our package, without success.
I can only from firefox-release, from MLO.

(In reply to katnatek from comment #26)
> (In reply to PC LX from comment #25)
> > Would it be possible to make cockpit-ws not require cockpit-ws-selinux
> > (maybe just recommend)?
> > 
> > $ urpmq --requires cockpit-ws | grep selinux
> > cockpit-ws: cockpit-ws-selinux[== 338-1.1.mga9]
> 
> Not sure, I wish to disable selinux packages, I have to check if is a spec
> require or autodetect require

It would be fine, if possible

Created attachment 15005 [details]
Alternative nsswitch.conf

(In reply to papoteur from comment #29)
> (In reply to katnatek from comment #28)for that, I have not caught because I
> not use ESR firefox
> > > 
> > > I am afraid this is a bug in our firefox,  I use Mozilla Firefox 128.11 ESR
> > > and I could login
> > 
> > As workaround use chromium-browser
> 
> I tried from our package, without success.
> I can only from firefox-release, from MLO.
> 
I try current mageia firefox, chromium-browser, and Mozilla's ESR firefox without issues

Are you sure you are using packages in comment#13? madb was listing the previous release

Try the attached nsswitch.conf to see if makes some difference

After trying again, (and reboot) I can access cockpit with our Firefox ESR and Chromium.
Thus, for me, the update is OK.

Installed new version, checked port 9090/tcp open in firewall, checked additions in /etc/nsswitch.conf, all OK.# systemctl enable cockpit.socket
Created symlink /etc/systemd/system/sockets.target.wants/cockpit.socket → /usr/lib/systemd/system/cockpit.socket.
# systemctl start cockpit
# systemctl -l status cockpit
● cockpit.service - Cockpit Web Service
     Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static)
     Active: active (running) since Wed 2025-06-04 09:54:29 CEST; 4s ago
TriggeredBy: ● cockpit.socket
       Docs: man:cockpit-ws(8)
    Process: 13372 ExecStartPre=/usr/libexec/cockpit-certificate-ensure --for-cockpit-tls (code=exited, status=0/SUCCESS)
   Main PID: 13383 (cockpit-tls)
      Tasks: 1 (limit: 8806)
     Memory: 900.0K
        CPU: 313ms
     CGroup: /system.slice/cockpit.service
             └─13383 /usr/libexec/cockpit-tls

Jun 04 09:54:29 mach3.hviaene.thuis systemd[1]: Starting cockpit.service...
Jun 04 09:54:29 mach3.hviaene.thuis systemd[1]: Started cockpit.service.
 
Navigating to localhost:9090 in Firefox (128.10.1) brings me in same situation as in Comment 22.
Trying the same with Chromium allows login and gives me a correct interface as far as my knowledge goes.

Hi Herman,
Perhaps cookies are living from a previous failing connection in Firefox, where session in Chromium was just new.

Indeed, clearing de cookies gets me into cockpit. Give it the OK if you think this has been tested enough.

(In reply to Herman Viaene from comment #35)
> Indeed, clearing de cookies gets me into cockpit. Give it the OK if you
> think this has been tested enough.

Sadly I overcut packages, the sosreport package will back in next subrelease

Installed and run OK.

The installation still recommends cockpit-ws-selinux, which I presume is not wanted.
with the --norecommends option, the installation went fine.
Running is OK

(In reply to papoteur from comment #39)
> The installation still recommends cockpit-ws-selinux, which I presume is not
> wanted.
> with the --norecommends option, the installation went fine.
> Running is OK

Ups A bad condition

New version installed, first time I dare to run it with administrative privileges.
Looks OK, except for "Networking", first click enables Network Manager, but then  I get "Networkmanager is not running" and button "Start service". Click that one and nothing seems to happen, except that wifi is disconnected, and the interface is stuc here. I can click on "Troiubleshoot" and that one tells that the service is running, but i cann't get any further.
I had to plug in Ethernet, and then I can proceed (fill this in) and try to activate the wifi again in cockpit, but that fails.
Most other things seem to work (nothing on wifi in the logs), but running diagnostic report fails completely giving "ModuleNotFoundError: No module named 'magic' "

I will try, after saving now, to remove the Ethernet and get wifi going from cockpit, but all in all, I am not impressed (polite formulating).

No joy with wifi in cockpit. Stopped networkmanager, quit cockpit and restored wifi connection (using it now) from MCC.
Deleting cockpit from my laptop as fast as I can.

(In reply to Herman Viaene from comment #43)
> New version installed, first time I dare to run it with administrative
> privileges.
> Looks OK, except for "Networking", first click enables Network Manager, but
> then  I get "Networkmanager is not running" and button "Start service".
> Click that one and nothing seems to happen, except that wifi is
> disconnected, and the interface is stuc here. I can click on "Troiubleshoot"
> and that one tells that the service is running, but i cann't get any further.
> I had to plug in Ethernet, and then I can proceed (fill this in) and try to
> activate the wifi again in cockpit, but that fails.
> Most other things seem to work (nothing on wifi in the logs), but running
> diagnostic report fails completely giving "ModuleNotFoundError: No module
> named 'magic' "
> 
> I will try, after saving now, to remove the Ethernet and get wifi going from
> cockpit, but all in all, I am not impressed (polite formulating).

Perhaps if/when mageia switch to networkmanager the integration works better(In reply to Herman Viaene from comment #43)
> New version installed, first time I dare to run it with administrative
> privileges.
> Looks OK, except for "Networking", first click enables Network Manager, but
> then  I get "Networkmanager is not running" and button "Start service".
> Click that one and nothing seems to happen, except that wifi is
> disconnected, and the interface is stuc here. I can click on "Troiubleshoot"
> and that one tells that the service is running, but i cann't get any further.
> I had to plug in Ethernet, and then I can proceed (fill this in) and try to
> activate the wifi again in cockpit, but that fails.
> Most other things seem to work (nothing on wifi in the logs), but running
> diagnostic report fails completely giving "ModuleNotFoundError: No module
> named 'magic' "
> 
> I will try, after saving now, to remove the Ethernet and get wifi going from
> cockpit, but all in all, I am not impressed (polite formulating).

I could ask you too much but can confirm if install python3-python-magic helps?

Installed python3-python-magic along cockpit, now diagnostics report runs OK.

Skip the last packages the python3-python-magic require was misplaced and is not feched, ugh

RPMS:

cockpit-338-1.6.mga9
cockpit-bridge-338-1.6.mga9
cockpit-doc-338-1.6.mga9
cockpit-networkmanager-338-1.6.mga9
cockpit-packagekit-338-1.6.mga9
cockpit-sosreport-338-1.6.mga9
cockpit-storaged-338-1.6.mga9
cockpit-system-338-1.6.mga9
cockpit-ws-338-1.6.mga9

SRPM:
cockpit-338-1.6.mga9

Status comment: Packages in comment 47 => Packages in comment 49

urpmq --requires cockpit-system
cockpit-system: /usr/bin/date
cockpit-system: /usr/bin/pwscore
cockpit-system: cockpit-bridge[>= 338-1.6.mga9]
cockpit-system: grep
cockpit-system: python3dist(python-magic)
cockpit-system: shadow-utils
cockpit-system: /usr/bin/date
cockpit-system: /usr/bin/pwscore
cockpit-system: cockpit-bridge[>= 269-2.mga9]
cockpit-system: grep
cockpit-system: shadow-utils
cockpit-system: /usr/bin/date
cockpit-system: /usr/bin/pwscore
cockpit-system: cockpit-bridge[>= 338-1.4bdk_mga9]
cockpit-system: grep
cockpit-system: shadow-utils

LC_ALL=C urpmi cockpit cockpit-sosreport
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Release (Installer) (DVD1)")
  lib64newt0.52                  0.52.23      1.mga9        x86_64  (recommended)
  lib64nm0                       1.40.18      2.mga9        x86_64  (recommended)
  lib64nma-gtk4_0                1.10.6       1.mga9        x86_64  (recommended)
  lib64nma0                      1.10.6       1.mga9        x86_64  (recommended)
  lib64openconnect5              9.11         1.mga9        x86_64  (recommended)
  lib64teamdctl0                 1.31         6.mga9        x86_64  (recommended)
  lib64tspi1                     0.3.15       3.mga9        x86_64  (recommended)
  libnma                         1.10.6       1.mga9        x86_64  (recommended)
  mobile-broadband-provider-info 1.20221107   1.mga9        noarch  (recommended)
  modemmanager                   1.20.4       1.mga9        x86_64  (recommended)
  networkmanager                 1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-adsl            1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-bluetooth       1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-ppp             1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-pptp            1.2.10       3.mga9        x86_64  (recommended)
  networkmanager-team            1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-tui             1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-wifi            1.40.18      2.mga9        x86_64  (recommended)
  networkmanager-wwan            1.40.18      2.mga9        x86_64  (recommended)
  openconnect                    9.11         1.mga9        x86_64  (recommended)
  perl-Authen-PAM                0.160.0      28.mga9       x86_64  (recommended)
  ppp                            2.4.9        3.mga9        x86_64  (recommended)
  pptp-linux                     1.8.0        6.mga9        x86_64  (recommended)
  vpnc                           0.5.3        17.mga9       x86_64  (recommended)
  xl2tpd                         1.3.17       1.mga9        x86_64  (recommended)
(medium "QA Testing (64-bit)")
  cockpit                        338          1.6.mga9      x86_64  
  cockpit-bridge                 338          1.6.mga9      noarch  
  cockpit-networkmanager         338          1.6.mga9      noarch  (recommended)
  cockpit-packagekit             338          1.6.mga9      noarch  (recommended)
  cockpit-sosreport              338          1.6.mga9      noarch  
  cockpit-storaged               338          1.6.mga9      noarch  (recommended)
  cockpit-system                 338          1.6.mga9      noarch  
  cockpit-ws                     338          1.6.mga9      x86_64  
(medium "Core Release")
  lib64bd_btrfs2                 2.28         2.mga9        x86_64  (recommended)
  lib64bd_lvm2                   2.28         2.mga9        x86_64  (recommended)
  python3-argcomplete            2.0.0        1.mga9        noarch  (recommended)
  python3-importlib-resources    5.4.0        2.mga9        noarch  
  python3-python-magic           0.4.27       2.mga9        noarch  
  python3-tracer                 0.7.8        1.mga9        noarch  (recommended)
  sos                            4.4          1.mga9        noarch  
  tracer-common                  0.7.8        1.mga9        noarch  (recommended)
  udisks2-btrfs                  2.9.4        3.mga9        x86_64  (recommended)
  udisks2-lvm2                   2.9.4        3.mga9        x86_64  (recommended)
(medium "Core Updates")
  lib64ndp0                      1.8          2.1.mga9      x86_64  (recommended)
  lib64tss2-tcti-cmd0            4.0.2        1.mga9        x86_64  (recommended)
  lib64tss2-tcti-device0         4.0.2        1.mga9        x86_64  (recommended)
  lib64tss2-tcti-mssim0          4.0.2        1.mga9        x86_64  (recommended)
  lib64tss2-tcti-pcap0           4.0.2        1.mga9        x86_64  (recommended)
  lib64tss2-tcti-spi-helper0     4.0.2        1.mga9        x86_64  (recommended)
  lib64tss2-tcti-swtpm0          4.0.2        1.mga9        x86_64  (recommended)
  lib64tss2-tctildr0             4.0.2        1.mga9        x86_64  (recommended)
  multipath-tools                0.8.8        2.1.mga9      x86_64  (recommended)
  networkmanager-l2tp            1.8.8        1.1.mga9      x86_64  (recommended)
  networkmanager-libreswan       1.2.24       1.mga9        x86_64  (recommended)
  networkmanager-openconnect     1.2.10       1.mga9        x86_64  (recommended)
  networkmanager-openvpn         1.10.2       1.mga9        x86_64  (recommended)
  networkmanager-vpnc            1.2.8        1.1.mga9      x86_64  (recommended)
  openvpn                        2.5.9        1.1.mga9      x86_64  (recommended)
  wpa_supplicant                 2.11         1.1.mga9      x86_64  (recommended)
58MB of additional disk space will be used.
20MB of packages will be retrieved.
Proceed with the installation of the 59 packages? (Y/n) y

Start the cockpit service, looks good

I'm not hope this is the last round as could be more missing python packages that I not see listed in other places and getbuildrequires not works with this software :(

I removed previous version and python3-python-magic after previous test, so did a complete new install, and all works OK AFAICS.

Installed and tested with a one minor issue. 

The one minor issue is in the /metrics page where the following message is displayed.
"""
PCP is missing for metrics history
"""

I looked in the repositories and there is no pcp or python3-pcp packages. If possible, it would be good to include these packages in the repositories, but I don't think it is a deal breaker for cockpit.

I did not test cockpit-networkmanager because this server doesn't use NetworkManager. Instead, it uses systemd-networkd.

I don't usually use cockpit so I only did some quick tests, but everything tested seems to be working correctly.

I also had some issues due to my local specific configuration but will make a comment here in cause it helps someone else (or me in future tests of cockpit).
- sudo is required for "administrative access". I had to install sudo and add my user account to the wheel group.
- For the cockpit's terminal to work I had to disable privacy.resistFingerprinting in LibreWolf's about:config.

From me, this update get and OK.



System: Mageia 9, x86_64, Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz.



$ uname -a
Linux marte 6.6.92-server-1.mga9 #1 SMP PREEMPT_DYNAMIC Thu May 22 19:00:17 UTC 2025 x86_64 GNU/Linux
$ rpm -qa | grep cockpit | sort
cockpit-338-1.6.mga9
cockpit-bridge-338-1.6.mga9
cockpit-packagekit-338-1.6.mga9
cockpit-storaged-338-1.6.mga9
cockpit-system-338-1.6.mga9
cockpit-ws-338-1.6.mga9
# systemctl status cockpit.service 
● cockpit.service - Cockpit Web Service
     Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static)
     Active: active (running) since Sun 2025-06-08 16:34:45 WEST; 23min ago
TriggeredBy: ● cockpit.socket
       Docs: man:cockpit-ws(8)
    Process: 1754288 ExecStartPre=/usr/libexec/cockpit-certificate-ensure --for-cockpit-tls (code=exited, status=0/SUCCESS)
   Main PID: 1754320 (cockpit-tls)
      Tasks: 2 (limit: 19018)
     Memory: 5.0M
        CPU: 35.873s
     CGroup: /system.slice/cockpit.service
             └─1754320 /usr/libexec/cockpit-tls

jun 08 16:34:45 marte systemd[1]: Starting cockpit.service...
jun 08 16:34:45 marte systemd[1]: Started cockpit.service.

(In reply to PC LX from comment #52)
Thank you please open a request for pcp, I don't know if can be imported in mageia 9, but a thing to do in cauldron

Whiteboard: (none) => MGA9-64-OK
CC: (none) => andrewsfarm

Created package request at bug 34361.

Thank you everyone, for all the hard work. Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

A reminder to remove legacy packages

From 9/core/updates_testing

i586:
cockpit-kdump-338-1.1.mga9.noarch.rpm
cockpit-selinux-338-1.1.mga9.noarch.rpm
cockpit-ws-selinux-338-1.1.mga9.i586.rpm

x86_64:
cockpit-kdump-338-1.1.mga9.noarch.rpm
cockpit-selinux-338-1.1.mga9.noarch.rpm
cockpit-ws-selinux-338-1.1.mga9.x86_64.rpm

From cauldron/core/release

i686:
cockpit-kdump-338-3.mga10.noarch.rpm
cockpit-selinux-338-3.mga9.noarch.rpm
cockpit-ws-selinux-338-3.mga9.i686.rpm

x86_64:
cockpit-kdump-338-3.mga9.noarch.rpm
cockpit-selinux-338-3.mga9.noarch.rpm
cockpit-ws-selinux-338-3.mga9.x86_64.rpm

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2025-0181.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED

(In reply to katnatek from comment #56)
> A reminder to remove legacy packages
> 
> From 9/core/updates_testing
> 
> i586:
> cockpit-kdump-338-1.1.mga9.noarch.rpm
> cockpit-selinux-338-1.1.mga9.noarch.rpm
> cockpit-ws-selinux-338-1.1.mga9.i586.rpm
> 
> x86_64:
> cockpit-kdump-338-1.1.mga9.noarch.rpm
> cockpit-selinux-338-1.1.mga9.noarch.rpm
> cockpit-ws-selinux-338-1.1.mga9.x86_64.rpm
> 
> From cauldron/core/release
> 
> i686:
> cockpit-kdump-338-3.mga10.noarch.rpm
> cockpit-selinux-338-3.mga9.noarch.rpm
> cockpit-ws-selinux-338-3.mga9.i686.rpm
> 
> x86_64:
> cockpit-kdump-338-3.mga9.noarch.rpm
> cockpit-selinux-338-3.mga9.noarch.rpm
> cockpit-ws-selinux-338-3.mga9.x86_64.rpm

Dan , Please take care of this

CC: (none) => dan

Those packages are now gone (pending the next hdlists update).