Request for auto-connect and dbus slot for pwl-linux-pkgs-dw5826e (WWAN modem host services)

Snap: pwl-linux-pkgs-dw5826e, revision 1 (uploaded, not released to any channel; held for manual review for the dbus slot and gpio-control).

pwl-linux-pkgs-dw5826e provides the host-side services for the PWL cellular modem (Dell DW5826e, USB, 413c:8217/8218/8219/81ea/81eb/81ec) shipped in Dell notebooks: modem bring-up, AT/MBIM adaptation, firmware update, and carrier preference. Four daemons, strict confinement, core22. Published by Palcom International Corporation. The snap has been verified end to end on the target hardware under strict confinement — including a full firmware flash — with zero AppArmor denials.

Host-side integration (udev rules, a ModemManager drop-in, the FCC unlock hook) is not done from this snap. It ships as a separate OEM deb through the Dell/Canonical OEM channel, the same way lenovo-wwan-unlock and foxconn-pc-services do. Nothing in this request touches host configuration.

We are asking for the following. Each item is tied to a code path the product cannot function without.

1. dbus slot on the system bus, name com.pwl.core (allow-installation), and auto-connect of this snap’s own pwl-core-dbus-client plug to it

pwl-core owns this name; the other three daemons reach it by name, and the snap’s per-user dialog agent (daemon-scope: user) plugs the same name to receive the progress-dialog signal. Without the slot the daemons cannot find each other; without the plug connection the user never sees the firmware-update dialog.

2. modem-manager — auto-connect

This is the snap’s primary function. The daemons talk MBIM to the modem through the host’s mbim-proxy (MBIM_DEVICE_OPEN_FLAGS_PROXY), which this interface’s @mbim-proxy unix rule grants, and inhibit ModemManager over D-Bus around firmware flashing. Without it no daemon can reach the modem at all. Same justification as lenovo-wwan-dpr (2021-08) and quectel-firmware-switch (2021-12).

3. hardware-observe — auto-connect

Reads /sys/class/dmi/id/product_sku to select the firmware category for the machine, and walks /sys/bus/usb/devices/*/idVendor to detect the module. Without it every daemon exits at start with “unsupported device”.

4. raw-usb — auto-connect

Firmware is flashed with fastboot (staged in the snap) over usbfs while the module is re-enumerated as 413c:8219. Without it the flash cannot start.

5. gpio-control — allow-installation and auto-connect

Hardware recovery after a failed flash: the daemon power-cycles the module by writing /sys/class/gpio/export, gpioN/direction and gpioN/value for the pin that the machine’s SKU maps to. This is the last recovery step before the module is considered unrecoverable, so it has to be present on every machine, not connected by hand after a failure. gpio-control is a system slot on classic Ubuntu (implicitOnClassic); the pin numbers are selected at runtime from a SKU table in the daemon. We considered moving the GPIO write into the host deb as a helper; we would rather keep it in the snap so the recovery logic stays in one place under confinement, but can move it if reviewers prefer.

What is not requested

No system-files, no custom-device, no classic. The firmware images are bundled in this snap; the content plug (pwl-firmware) is kept for a future same-publisher split and needs nothing from the store.

Verification

Dell Pro 14 Plus (Ubuntu 24.04.3, kernel 6.17 OEM, snapd 2.76.3) with a DW5826e, SIM in, this revision plus the host OEM deb. Under strict confinement with the interfaces above connected: install and FCC unlock (the unlock’s verdict reaching pwl-core over the dbus slot), then two full firmware flashes by snap refresh (07.62 → 07.64 → 07.62, image over usbfs, module reboot). Each flash: ModemManager inhibited over D-Bus before the switch to download mode, the module unlocked after its first boot, the device released back to ModemManager, the preferred carrier set again, version read back and the modem registered. Zero AppArmor denials during both flows. gpio-control was verified separately: with the plug connected a strict snap can export and drive a pin through /sys/class/gpio.

Thanks & Regards, Tinny Tseng (Tinny.tseng@palcomwireless.com)

This request has been added to the queue for review by the @reviewers team.

Please post the relevant excerpts of your snapcraft yaml so we can review any attributes for these interfaces and how they are defined.

Hello @Tinny.tseng,

Is this a private or open-source project? If it is open-source, please provide a link to the upstream and your snapcraft.yaml. If it is private, as @kenvandine mentions above, please provide us with the relevant snapcraft.yaml excerpts for the above requested interfaces. This will aid with our review, thank you!

Thanks @kenvandine and @elisehdy. This is a private (proprietary) project: the snap bundles proprietary modem firmware images and an FCC unlock tool, and its snapcraft.yaml is not published. Below are the interface-related parts of snap/snapcraft.yaml for pwl-linux-pkgs-dw5826e (strict, core22). Comments trimmed; nothing else in the file touches interfaces.

One change since the original post: the store review of revision 1 rejected it because the D-Bus name com.pwl.core was too generic. Revision 2 (uploaded 2026-10-07, same version string 4.8.0+fw50.43+07.62) uses com.palcomwireless.pwl.core instead (palcomwireless.com is the publisher’s domain, see contact:), and it is now waiting for manual review (“allow-installation” and “deny-connection” constraints). The excerpts below are from revision 2, so please read the dbus slot request in the original post with the new name.

name: pwl-linux-pkgs-dw5826e
base: core22
grade: stable
confinement: strict
contact: Blake.Lin@palcomwireless.com

slots:
  pwl-core-dbus:
    interface: dbus
    bus: system
    name: com.palcomwireless.pwl.core

plugs:
  # client side of the same name: the dialog agent receives NotifyDialogSignal,
  # pref / madpt / fwupdate call pwl_core's methods
  pwl-core-dbus-client:
    interface: dbus
    bus: system
    name: com.palcomwireless.pwl.core
  # optional firmware override from a same-publisher content snap; unconnected
  # the bundled images are used. No default-provider.
  firmware:
    interface: content
    content: pwl-firmware
    target: $SNAP/firmware
  modem-manager:
    interface: modem-manager
  raw-usb:
    interface: raw-usb
  hardware-observe:
    interface: hardware-observe
  # module power-cycle after a failed switch to download mode:
  # /sys/class/gpio/export, gpioN/direction, gpioN/value (pin from the SKU table)
  gpio-control:
    interface: gpio-control

apps:
  core:
    command: bin/pwl_core
    daemon: simple
    restart-condition: on-failure
    slots: [pwl-core-dbus]
    plugs: [firmware, modem-manager, hardware-observe, gpio-control]
  pref:
    command: bin/pwl_pref
    daemon: simple
    restart-condition: on-failure
    after: [core]
    plugs: [firmware, hardware-observe, pwl-core-dbus-client]
  madpt:
    command: bin/pwl_madpt
    daemon: simple
    restart-condition: on-failure
    after: [pref]
    plugs: [firmware, modem-manager, hardware-observe, pwl-core-dbus-client]
  fwupdate:
    command: bin/pwl_fwupdate
    daemon: simple
    restart-condition: on-failure
    after: [madpt]
    plugs: [firmware, modem-manager, raw-usb, hardware-observe, pwl-core-dbus-client]
  dialog-agent:
    command: bin/pwl-dialog-agent
    daemon: simple
    daemon-scope: user
    restart-condition: on-failure
    extensions: [gnome]
    plugs: [pwl-core-dbus-client]

No system-files, custom-device, network-control or system-observe; no classic. The host-side files (udev rules, ModemManager drop-in, FCC unlock hook, mbim-proxy unit) are installed by a separate OEM deb, not by this snap.

Hello @Tinny.tseng,

Thank you for the extended info, and apologies for the delay on this request. The dbus request is well-scoped: granting dbus name com.palcomwireless.pwl.core, this is now live.

Based on the snaps described functionality, this is +1 from me for granting auto-connection for the modem-manager, hardware-observe, and raw-usb interfaces. Considering gpio-control, it is generally not granted installation in the global store, have you considered pursuing a brand store? Given this is a recovery-based functionality, this is a -1 from me for granting installation of the gpio-control interface to snap pwl-linux-pkgs-dw5826e.

What do other reviewers think?

Hi @elisehdy, thank you for the review, and for granting the dbus name com.palcomwireless.pwl.core.

Understood on gpio-control. In our snap the GPIO reset is only the last-resort recovery step (power-cycling the modem when it cannot be brought back otherwise), so we will take it out of the snap instead:

  • the next revision drops the gpio-control plug, and the snap no longer touches /sys/class/gpio at all;
  • the GPIO write moves into the host-side OEM deb (pwl-host-integration) that already has to be installed with the snap. When a reset is needed, the snap only writes a request file in its own $SNAP_COMMON; a root systemd path unit shipped by that deb picks it up and power-cycles the modem.

We have already tried this on a test machine with the plug disconnected: the request is picked up, the modem power-cycles and comes back, and mobile data reconnects, with no AppArmor denials from the snap. No new interface is needed for it.

We will upload a new revision without gpio-control and post here once it is up. The auto-connect request for modem-manager, hardware-observe and raw-usb stays as it is.

Thanks again.

Hi @elisehdy, revision 3 (4.8.2) is now uploaded, and it passed the automated review with no manual review flags.

  • The gpio-control plug is gone, and the snap no longer touches /sys/class/gpio.
  • The modem GPIO reset is now done on the host by the pwl-host-integration deb, as described above.
  • The other interfaces are unchanged from revision 2: the dbus slot com.palcomwireless.pwl.core, plus modem-manager, hardware-observe and raw-usb.

The auto-connect request for those three interfaces stays as it is. Could the remaining reviewers take a look when they have time?

Thanks.

Hi @Tinny.tseng

Apologies for the delay.

+1 from me to grant auto-connection of modem-manager, hardware-observe and raw-usb interfaces.

@policy-reviewers any update on the autoconnect request?

Hello,

Apologies for the further delay and thank you for your understand on gpio-control. +2 votes for, 0 votes against, granting auto-connect of interfaces modem-manager, hardware-observe, and raw-usb to snap pwl-linux-pkgs-dw5826e. This is now live!

Hi @elisehdy, thanks for granting the auto-connect of modem-manager, hardware-observe and raw-usb.

We released revision 3 to edge (the snap is private for now) and installed it from the store on a test machine (Ubuntu 24.04). Those three interfaces connected automatically. One connection did not: the snap’s own dbus plug to its own dbus slot.

$ snap connections pwl-linux-pkgs-dw5826e | grep dbus
dbus   -                                            pwl-linux-pkgs-dw5826e:pwl-core-dbus  -
dbus   pwl-linux-pkgs-dw5826e:pwl-core-dbus-client  -                                     -

This was part of item 1 in the original request, but our reply for revision 3 only listed the three interfaces above. Sorry for the confusion.

The snap’s services talk to each other through pwl-core on the system bus. Without this connection, AppArmor denies their access to the system bus, so the firmware update and the modem services do not work. After snap connect pwl-linux-pkgs-dw5826e:pwl-core-dbus-client pwl-linux-pkgs-dw5826e:pwl-core-dbus, everything works: the firmware update, the FCC unlock and the data connection, also after a reboot.

Could you also grant auto-connect for this plug?

  • plug pwl-core-dbus-client: interface dbus, bus system, name com.palcomwireless.pwl.core
  • to the same snap’s slot pwl-core-dbus (the name you granted on 10-17)

Thanks.