GUI not opening after update last night.

[gedw99]

Issue Description

GUI not opening after update yesterday.

Intel Mac

podman version
Client:       Podman Engine
Version:      4.5.0
API Version:  4.5.0
Go Version:   go1.20.3
Git Commit:   75e3c12579d391b81d871fd1cded6cf0d043550a
Built:        Fri Apr 14 15:28:20 2023
OS/Arch:      darwin/amd64

Server:       Podman Engine
Version:      4.4.2
API Version:  4.4.2
Go Version:   go1.19.6
Built:        Wed Mar  1 12:22:59 2023
OS/Arch:      linux/amd64
apple@x-MacBook-Pro-2 app % podman info
host:
  arch: amd64
  buildahVersion: 1.29.0
  cgroupControllers:
  - cpu
  - io
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.7-2.fc37.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.7, commit: '
  cpuUtilization:
    idlePercent: 98.5
    systemPercent: 1.2
    userPercent: 0.3
  cpus: 1
  databaseBackend: ""
  distribution:
    distribution: fedora
    variant: coreos
    version: "37"
  eventLogger: journald
  hostname: localhost.localdomain
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 1000000
    uidmap:
    - container_id: 0
      host_id: 502
      size: 1
    - container_id: 1
      host_id: 100000
      size: 1000000
  kernel: 6.2.8-200.fc37.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 276037632
  memTotal: 2048835584
  networkBackend: netavark
  ociRuntime:
    name: crun
    package: crun-1.8.3-2.fc37.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.8.3
      commit: 59f2beb7efb0d35611d5818fd0311883676f6f7e
      rundir: /run/user/502/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/502/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: true
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.0-8.fc37.x86_64
    version: |-
      slirp4netns version 1.2.0
      commit: 656041d45cfca7a4176f6b7eed9e4fe6c11e8383
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.3
  swapFree: 0
  swapTotal: 0
  uptime: 55h 33m 56.00s (Approximately 2.29 days)
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries:
  search:
  - docker.io
store:
  configFile: /var/home/core/.config/containers/storage.conf
  containerStore:
    number: 9
    paused: 0
    running: 2
    stopped: 7
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/core/.local/share/containers/storage
  graphRootAllocated: 106769133568
  graphRootUsed: 17446096896
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 9
  runRoot: /run/user/502/containers
  transientStore: false
  volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
  APIVersion: 4.4.2
  Built: 1677669779
  BuiltTime: Wed Mar  1 12:22:59 2023
  GitCommit: ""
  GoVersion: go1.19.6
  Os: linux
  OsArch: linux/amd64
  Version: 4.4.2

Steps to reproduce the issue

Steps to reproduce the issue:

1. brew install podman

install gpgme (needed for podman's Go binding dependenices)

2. brew install gpgme

3. brew install podman-desktop

4. sudo podman-mac-helper install

Final manual setup.

5. podman machine init -v $HOME:$HOME
6. podman machine start

Describe the results you received

GUI jst not opening ...

Describe the results you expected

a gui...

podman info output

Intel mac..

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[gedw99]

got it going but it seems a little confused.

[vrothberg]

Thanks for reaching out, @gedw99! I moved the issue to github.com/containers/podman-desktop.

[Nyvyan]

Hi, I am having a similar issue on Windows. After system reboot I am unable to open the Podman desktop gui. I can still start podman machine and my containers from Powershell console.

Using Windows installer, version v1.0.1

I was unable to find any logs from the failed start attempts. Are there any options to try starting Podman desktop with logging enabled?

[benoitf]

@gedw99 I think that autostart is not displaying a dialog box anymore

about the issue 'exit 255', that is the root cause, it'a failure in Podman machine https://github.com/containers/podman/issues/17403

you could disable the 'auto start Podman each time I run Podman Desktop' in preferences so that it doesn't bring the message when you launch Podman Desktop

[benoitf]

@Nyvyan: when you say that you're not able to open the Podman Desktop gui, do you see something ?

I may think that after a reboot, Podman Desktop is restarted automatically and then stay minimized in the tray icon. So it's already launched, you just need to open the dashboard from the tray icon ?

[gedw99]

I fixed it by re opening .

I I stalled initially with brew on Mac.

last update for v1 worked cleanly btw .

Hope that helps …

[benoitf]

ok thanks, closing the issue.