Comment # 7 on bug 1219363 from Matej Cepl

(In reply to Johannes Segitz from comment #6)
> hm, can you based on the timestamp identify when this is happening? E.g. is
> this happening then the service starts? Or when you log into you desktop
> environment?

9 seconds after the beginning of the boot, so I guess somewhere during the boot
process.

systemctl status says:

● ModemManager.service - Modem Manager
     Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled;
preset: enabled)
     Active: active (running) since Wed 2024-02-28 18:47:25 CET; 2 days ago
   Main PID: 1209 (ModemManager)
      Tasks: 4 (limit: 4915)
        CPU: 341ms
     CGroup: /system.slice/ModemManager.service
             └─1209 /usr/sbin/ModemManager

úno 28 18:47:25 mitmanek.cepl.eu systemd[1]: Started Modem Manager.
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <info>  [base-manager]
couldn't check support for device
'/sys/devices/pci0000:00/0000:00:08.3/0000:34:00.4/usb10/10-1/10-1.1': not >
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <info>  [device
/sys/devices/pci0000:00/0000:00:08.1/0000:33:00.3/usb1/1-4] creating modem with
plugin 'quectel' and '3' ports
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <warn>  [plugin/quectel]
could not grab port cdc-wdm0: Cannot add port 'usbmisc/cdc-wdm0', unhandled
port type
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <info>  [base-manager]
modem for device '/sys/devices/pci0000:00/0000:00:08.1/0000:33:00.3/usb1/1-4'
successfully created
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <info>  [modem0] state
changed (unknown -> locked)
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <warn>  [modem0] modem
couldn't be initialized: Couldn't check unlock status: SIM not inserted
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <info>  [modem0] state
changed (locked -> failed)
úno 28 18:47:28 mitmanek.cepl.eu ModemManager[1209]: <warn>  [modem0] error
initializing: Modem in failed state: sim-missing
úno 28 18:47:29 mitmanek.cepl.eu ModemManager[1209]: <info>  [base-manager]
couldn't check support for device
'/sys/devices/pci0000:00/0000:00:02.2/0000:01:00.0': not supported by any p>


> In the first case: Can you re-trigger the AVC by restarting the service?
> In the second case: an you re-trigger the AVC by logging out of you GUI and
> then back in?

Let me check it and write next comment.