Postman does not open

[guilhermesousa-cwi]

Ubuntu 22.04.3 LTS

X11

Postman when run via CLI or GUI does not open.

Installed the latest version from the Ubuntu app store. Flathub website is returning 404 page not found.

Via CLI we can see some logs.

flatpak run com.getpostman.Postman
The disableGPU setting is set to undefined Not disabling GPU Gtk-Message: 12:19:22.829: Failed to load module "xapp-gtk3-module" Gtk-Message: 12:19:22.942: Failed to load module "canberra-gtk-module" Gtk-Message: 12:19:22.946: Failed to load module "canberra-gtk-module" [10:0921/121923.009665:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Arquivo ou diretório inexistente [10:0921/121923.009772:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: Arquivo ou diretório inexistente Main: Starting cleanup of stale files Main: Cleanup of stale files completed ProtocolHandler~setDefaultProtocolClient: Command failed: xdg-mime default Postman.desktop x-scheme-handler/postman /bin/sh: linha 1: xdg-mime: comando não encontrado

LaunchProcess: failed to execvp: xdg-settings Main~createDefaultWorkingDir - Default working dir creation already attempted 1695309563229 main info "Booting Postman 10.18.4, linux-6.2.0-33-generic on x64" 1695309563232 main info "EventBus~initialize - Success" 1695309563235 main info "Proxy configuration has not been setup" 1695309563237 main info "CloudProxyManager~init - Success" 1695309563298 main info "performShellDataMigration: Migration has already been done. Bailing out" 1695309563316 main info "UpdateHandler~init - Success" 1695309563320 main info "LeaderSelection: Initialized successfully" 1695309563322 main info "VersionDependencyService: Initialized successfully" error reading fileError: ENOENT: no such file or directory, open '/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt' 1695309563347 main info "Generated root certificate for linux" 1695309563350 main info "LinuxAutoUpdater~Cleanup - Initial cleanup successful" 1695309563392 main info "GPU detected VID 32902 DID 39745 ACTIVE true" [47:0921/121923.421370:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. 1695309563465 main info "shellController~init: Success" 1695309563502 main info "shellMeta~init: Success" 1695309563503 main info "partitionMigrationService: State of V7 partition:" 1695309563504 main info "partitionMigrationService: V7 partitions",[] 1695309563505 main info "partitionMigrationService~rectifyNamespaceOfScratchPadPartition: There is no partition with scratchpad namespace" 1695309563506 main info "partitionMigrationService~rectifyNamespaceOfScratchPadPartition: There is no transit partition which could have been used for scratchpad" 1695309563506 main info "partitionMigrationService~init: Success" 1695309563573 main info "partitionMigrationService~runV8PartitionsIntegrity: Two way migration~ removing the following partitions from v8",[] 1695309563680 main error "Error encountered while creating root CA",{"name":"Error","message":"Invalid openssl exit code: 1\n% openssl req -new -sha256 -subj /C=US/CN=Postman Proxy CA -key /home/guilherme/.var/app/com.getpostman.Postman/cache/ac7027ce6ef85f21fd7b36a6651478f010abb82c\n4017FEC9EA7F0000:error:03000093:digital envelope routines:default_check:command not supported:../crypto/evp/ctrl_params_translate.c:329:\n","stack":"Error: Invalid openssl exit code: 1\n% openssl req -new -sha256 -subj /C=US/CN=Postman Proxy CA -key /home/guilherme/.var/app/com.getpostman.Postman/cache/ac7027ce6ef85f21fd7b36a6651478f010abb82c\n4017FEC9EA7F0000:error:03000093:digital envelope routines:default_check:command not supported:../crypto/evp/ctrl_params_translate.c:329:\n\n at done (/app/extra/Postman/resources/app/node_modules/@postman/pem/webpack:/pem/lib/openssl.js:171:1)\n at ChildProcess. (/app/extra/Postman/resources/app/node_modules/@postman/pem/webpack:/pem/lib/openssl.js:188:1)\n at ChildProcess.emit (node:events:390:28)\n at ChildProcess.emit (node:domain:475:12)\n at maybeClose (node:internal/child_process:1064:16)\n at Socket. (node:internal/child_process:450:11)\n at Socket.emit (node:events:390:28)\n at Socket.emit (node:domain:475:12)\n at Pipe. (node:net:687:12)"} 1695309563680 main error "Error generating rootCA certificate for HTTPS proxy",{"name":"Error","message":"Invalid openssl exit code: 1\n% openssl req -new -sha256 -subj /C=US/CN=Postman Proxy CA -key /home/guilherme/.var/app/com.getpostman.Postman/cache/ac7027ce6ef85f21fd7b36a6651478f010abb82c\n4017FEC9EA7F0000:error:03000093:digital envelope routines:default_check:command not supported:../crypto/evp/ctrl_params_translate.c:329:\n","stack":"Error: Invalid openssl exit code: 1\n% openssl req -new -sha256 -subj /C=US/CN=Postman Proxy CA -key /home/guilherme/.var/app/com.getpostman.Postman/cache/ac7027ce6ef85f21fd7b36a6651478f010abb82c\n4017FEC9EA7F0000:error:03000093:digital envelope routines:default_check:command not supported:../crypto/evp/ctrl_params_translate.c:329:\n\n at done (/app/extra/Postman/resources/app/node_modules/@postman/pem/webpack:/pem/lib/openssl.js:171:1)\n at ChildProcess. (/app/extra/Postman/resources/app/node_modules/@postman/pem/webpack:/pem/lib/openssl.js:188:1)\n at ChildProcess.emit (node:events:390:28)\n at ChildProcess.emit (node:domain:475:12)\n at maybeClose (node:internal/child_process:1064:16)\n at Socket. (node:internal/child_process:450:11)\n at Socket.emit (node:events:390:28)\n at Socket.emit (node:domain:475:12)\n at Pipe. (node:net:687:12)"} 1695309563681 main error "HTTPSProxy~Unable to generate certificates",{"name":"Error","message":"Invalid openssl exit code: 1\n% openssl req -new -sha256 -subj /C=US/CN=Postman Proxy CA -key /home/guilherme/.var/app/com.getpostman.Postman/cache/ac7027ce6ef85f21fd7b36a6651478f010abb82c\n4017FEC9EA7F0000:error:03000093:digital envelope routines:default_check:command not supported:../crypto/evp/ctrl_params_translate.c:329:\n","stack":"Error: Invalid openssl exit code: 1\n% openssl req -new -sha256 -subj /C=US/CN=Postman Proxy CA -key /home/guilherme/.var/app/com.getpostman.Postman/cache/ac7027ce6ef85f21fd7b36a6651478f010abb82c\n4017FEC9EA7F0000:error:03000093:digital envelope routines:default_check:command not supported:../crypto/evp/ctrl_params_translate.c:329:\n\n at done (/app/extra/Postman/resources/app/node_modules/@postman/pem/webpack:/pem/lib/openssl.js:171:1)\n at ChildProcess. (/app/extra/Postman/resources/app/node_modules/@postman/pem/webpack:/pem/lib/openssl.js:188:1)\n at ChildProcess.emit (node:events:390:28)\n at ChildProcess.emit (node:domain:475:12)\n at maybeClose (node:internal/child_process:1064:16)\n at Socket. (node:internal/child_process:450:11)\n at Socket.emit (node:events:390:28)\n at Socket.emit (node:domain:475:12)\n at Pipe. (node:net:687:12)"} 1695309563692 main info "userPartitionService~getRecentV8UserPartition: recent v8 user context partition ","50b2391e-b37c-421f-bd4f-231d2a493541" 1695309563692 main info "userPartitionService~_rectifyTheActivePartitionOfApplication: Setting the active partition to ","50b2391e-b37c-421f-bd4f-231d2a493541" 1695309563719 main info "userPartitionService~init: Success" 1695309563764 main info "userPartitionService: State of v8 partition system:" 1695309563778 main info "shell~init~getPartitionToLoad: loading active partition" 1695309563784 main info "userPartitionService: List of partitions:",[{"partitionId":"50b2391e-b37c-421f-bd4f-231d2a493541","namespace":"users","userId":"21137513","teamId":"1285670","lastUpdated":"2023-09-21T14:20:15.045Z"},{"partitionId":"5a9b379b-1c82-43e0-9e43-9b2c20aeb041","namespace":"scratchPad","userId":0,"teamId":0,"isDirty":false}] 1695309563784 main info "userPartitionService: users global meta:",{} 1695309570805 main info "RuntimeIPCAgent~started: Success" 1695309571502 main info "Main~getRemoteInitPath:: " 1695309571990 main info "UpdateHandler~app-update-events - Received event",{"name":"checkForElectronVersionUpdated","namespace":"appUpdate"} Error: ENOENT: no such file or directory, open '/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt' 1695309572000 main error "Main~handleUncaughtError - Uncaught errors",{"errno":-2,"code":"ENOENT","syscall":"open","path":"/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt","name":"Error","message":"ENOENT: no such file or directory, open '/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt'","stack":"Error: ENOENT: no such file or directory, open '/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt'"} Main~handleUncaughtError - Uncaught errors [Error: ENOENT: no such file or directory, open '/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt'] { errno: -2, code: 'ENOENT', syscall: 'open', path: '/home/guilherme/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt' } INTERCEPTOR CONNECTIVITY: Connecting to Interceptor Bridge IPCClient ~ WindowHandler: New event is received { type: 'window-opened' } 1695309572047 main info "windowManager: First requester booted successfully." 1695309572047 main info "windowManager~restoreWindows: Restoring requester windows" 1695309572048 main info "Main~AppEvents - Received booted event for process requester.Version 10.18.5 UI Version: 10.18.5-ui-230920-1358 Desktop Platform Version: 10.18.4"

[kamenlitchev]

Same for Fedora 38 / KDE

[joligoms]

Same for Fedora 38 Workstation here.

[anaximeno]

Many are having this problem.

Refs:

• https://github.com/postmanlabs/postman-app-support/issues/12330
• https://github.com/postmanlabs/postman-app-support/issues/11620

This solution worked for me https://github.com/postmanlabs/postman-app-support/issues/11620#issuecomment-1727280639 for now you may try it, but this still has to be fixed in the app.

[kerryhatcher]

Error confirmed on Pop!_OS 22.04 LTS .

To see the actual error, run the flatpack from the CLI. Just opening via GUI results in a crash with no details:

flatpak run com.getpostman.Postman

Also as @anaximeno mentioned, running the following OpenSSL command (found here) resolves the problem (post install).

Note: Slightly modified the file path names from the original to make it easier to copy and paste the command for future visitors here.

openssl req -subj '/C=US/CN=Postman Proxy' -new -newkey rsa:2048 -sha256 -days 365 -nodes -x509 -keyout ~/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.key -out ~/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt

What I don't know is if there are in downstream or long term effects of this. Obviously when dealing with certs and security, its best to leave it alone and let smarter people work it out. So This needs to get fixed asap. Willing to help however I can but I don't know anything about flatpack development.

[LLNet]

@kamenlitchev it work - thanks for help :-)

[Klusio19]

Same problem for latest Debian testing with KDE. Running from icon on dekstop or via cli with flatpak run com.getpostman.Postman results in that error ONLY WHEN LOGGED IN. Running provided OpenSSL command as @kerryhatcher mentioned works.

[DiracSpace]

@kerryhatcher your solution worked for me on Ubuntu 23.10, thank you!

[rokdelak]

Still broken, I installed popOS on 3 machines in the last 3 months (the last one yesterday) and every time I had to generate the certificates by hand, then it works fine.

[feliperdamaceno]

@kerryhatcher this worked for Pop Os 22.04 LTS

[QazCetelic]

I also have this issue on openSUSE Tumbleweed 20240704 with KDE Plasma 6.1.2 and Wayland.

Overwriting the certificate with @kerryhatcher's command helped.

[maxtheaxe]

Error confirmed on Pop!_OS 22.04 LTS .

To see the actual error, run the flatpack from the CLI. Just opening via GUI results in a crash with no details:

flatpak run com.getpostman.Postman

Also as @anaximeno mentioned, running the following OpenSSL command (found here) resolves the problem (post install).

Note: Slightly modified the file path names from the original to make it easier to copy and paste the command for future visitors here.

openssl req -subj '/C=US/CN=Postman Proxy' -new -newkey rsa:2048 -sha256 -days 365 -nodes -x509 -keyout ~/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.key -out ~/.var/app/com.getpostman.Postman/config/Postman/proxy/postman-proxy-ca.crt

What I don't know is if there are in downstream or long term effects of this. Obviously when dealing with certs and security, its best to leave it alone and let smarter people work it out. So This needs to get fixed asap. Willing to help however I can but I don't know anything about flatpack development.

This solved the insta-crashing issue for me, but in case it helps anyone else, I also needed to fully sign out and clear local data, restart the app, and then sign in again to get it working.

[Jhynn]

I found a post which I had success in solving this problem, just follow the steps below, I use arch btw.

1. Go to the directory ~/.var/app/com.getpostman.Postman/config/Postman/proxy, then.
2. Generate a valid certificate:

Simply just run the below instructions on your terminal.

cd ~/.var/app/com.getpostman.Postman/config/Postman/proxy

openssl req -subj '/C=US/CN=Postman Proxy' -new -newkey rsa:2048 -sha256 -days 365 -nodes -x509 -keyout postman-proxy-ca.key -out postman-proxy-ca.crt

[miguilimzero]

I'm also facing this issue. Fedora 40 with Wayland.

[Jhynn]

@miguilimzero have you tried my answer (the comment above yours)? Please consider executing both of those instructions.