Package Details: postman-bin 11.37.1-1

Git Clone URL: https://aur.archlinux.org/postman-bin.git (read-only, click to copy)
Package Base: postman-bin
Description: Build, test, and document your APIs faster
Upstream URL: https://www.getpostman.com
Licenses: custom
Conflicts: postman
Provides: postman
Submitter: claudiodangelis
Maintainer: j.taala
Last Packager: j.taala
Votes: 296
Popularity: 1.84
First Submitted: 2016-10-21 18:18 (UTC)
Last Updated: 2025-03-20 10:38 (UTC)

Pinned Comments

j.taala commented on 2021-09-17 09:50 (UTC) (edited on 2021-12-21 22:53 (UTC) by j.taala)

@ntfc I was going to go the other way (update to 9.0.1 instead of reverting back to 8.11.1).

P.S. postman are pretty bad at updating their release notes page (even after a new version is out).

If you want to revert to any previous version you can do so by cloning the aur repo and changing the version in the PKGBUILD file and using makepkg to build it (it will download and install that version for you). E.g.:

git clone https://aur.archlinux.org/postman-bin.git
cd postman-bin

Edit the PKGBUILD file with whatever editor you like: edit line 4 to be pkgver=8.11.1 or whatever version you like, then save and exit out of the editor and run

updpkgsums
makepkg -sif

updpkgsums will download the file and update sha for file in PKGBUILD so it will install with makepkg

Latest Comments

1 2 3 4 5 6 .. 22 Next › Last »

arseru commented on 2025-02-20 18:06 (UTC)

I finally managed to get v11.32.3-1 working by just cloning the repo locally and making sure node v20 was used:

git clone https://aur.archlinux.org/postman-bin.git && cd postman-bin
nvm install 20 && nvm use 20
makepkg -si

arseru commented on 2025-02-20 17:10 (UTC)

Hey @hbayrousson, thanks for the answer - unfortunately that doesn't work for me either:

$ npm i --force

npm warn using --force Recommended protections disabled.
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@postman%2fruntime - Not found
npm error 404
npm error 404  '@postman/runtime@^0.4.12' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.

hbayrousson commented on 2024-12-03 08:23 (UTC) (edited on 2024-12-05 07:53 (UTC) by hbayrousson)

Hey @arseru, I had the same issue than you.

It seems it is related with node version that was used to install the node modules and the one that you have on your computer.

Check you have a node version compatible :

node --version should be close to v20.18.0 (you can use nvm for instance)

To have it working : 

cd /opt/postman/app/resources/app/
rm -rf ./node_modules/@sentry
npm i --force

and there hopefully it is working !

If someone have a more elegant way without play with the node_modules ;)

arseru commented on 2024-12-02 11:37 (UTC)

Hey @j.taala, thanks for the reply! Unfortunately rebuilding/reinstalling didn't work for me, so I'll stay on the previous version for now, which still works :)

j.taala commented on 2024-12-02 10:54 (UTC)

Hey @arseru,

I did get it to work by uninstalling and then reinstalling.

Try

sudo pacman -R postman-bin

Then reinstall (I use yay), e.g.

yay -S postman-bin

arseru commented on 2024-12-02 10:32 (UTC)

@j.taala I bumped into the same crash error as you, I'm running 11.21.0-1. Did you find a fix for it?

j.taala commented on 2024-11-28 21:53 (UTC)

Thanks @kstolp. Looks like an issue on my side.

kstolp commented on 2024-11-28 19:39 (UTC)

@j.taala I'm on 11.21.0-1, and it's working normally. I'm not seeing the same error as you. Note: I haven't changed any settings related to proxies within Postman, and I build in a clean chroot.

j.taala commented on 2024-11-27 20:29 (UTC)

Hey all, after updating this package to 11.21.0 I'm now getting a crash on startup:

[jay@m16 ~]$ postman 
The disableGPU setting is set to undefined
Not disabling GPU
Main: Starting cleanup of stale files
Main: Cleanup of stale files completed
Main~createDefaultWorkingDir - Default working dir creation already attempted
Main~booting: Failed TypeError: _this._getProxy is not a function
    at new HTTPSTransport (/opt/postman/app/resources/app/node_modules/@sentry/node/dist/transports/https.js:13:27)
    at NodeBackend._setupTransport (/opt/postman/app/resources/app/node_modules/@sentry/node/dist/backend.js:55:16)
    at NodeBackend.BaseBackend (/opt/postman/app/resources/app/node_modules/@sentry/core/dist/basebackend.js:19:32)
    at new NodeBackend (/opt/postman/app/resources/app/node_modules/@sentry/node/dist/backend.js:15:42)
    at NodeClient.BaseClient (/opt/postman/app/resources/app/node_modules/@sentry/core/dist/baseclient.js:53:25)
    at new NodeClient (/opt/postman/app/resources/app/node_modules/@sentry/node/dist/client.js:33:24)
    at Object.initAndBind (/opt/postman/app/resources/app/node_modules/@sentry/core/dist/sdk.js:28:18)
    at Object.init (/opt/postman/app/resources/app/node_modules/@sentry/node/dist/sdk.js:117:12)
    at Object.init (/opt/postman/app/resources/app/services/CrashReporter.js:47:16)
    at Array.<anonymous> (/opt/postman/app/resources/app/main.js:324:19)
LeaderSelection: Error while initializing TypeError: Cannot read properties of undefined (reading 'channel')
    at Object.initialize (/opt/postman/app/resources/app/services/LeaderSelection.js:16:48)
    at onEndSeries (/opt/postman/app/resources/app/main.js:434:19)
    at asyncSeries (/opt/postman/app/resources/app/main.js:1301:3)
(node:8469) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'channel')
    at module.exports (/opt/postman/app/resources/app/common/services/AppBootListener.js:11:31)
    at onEndSeries (/opt/postman/app/resources/app/main.js:438:3)
    at asyncSeries (/opt/postman/app/resources/app/main.js:1301:3)
(Use `postman --trace-warnings ...` to show where the warning was created)
(node:8469) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

Has anyone else seen this on the latest postman (11.21.0)?

ll931217 commented on 2024-08-29 08:23 (UTC) (edited on 2024-09-10 01:55 (UTC) by ll931217)

I am having a very strange issue recently, whenever I start it from rofi (Wayland fork), the postman app doesn't start up. I looked around the internet and saw that people requested the coredump (Unfortunately I don't know how to get the full coredump, postman just terminates whenever it launches.

However, I have discovered that whenever I open a new terminal and immediately launch postman from /usr/bin/postman, it starts up normally without any issues.

Looking at the coredump, the signal that caused the crash is SEGV or signal 11. I am not sure how to fix this issue, could the electron of this postman installation trying to access some unavailable memory?

Here is the output of journalctl:

Aug 29 16:21:31 BaoArch sudo[63062]: ll931217 : TTY=pts/13 ; PWD=/home/ll931217 ; USER=root ; COMMAND=/usr/bin/nvim /usr/share/appl
ications/postman.desktop
Aug 29 16:21:53 BaoArch systemd-coredump[63189]: Process 63112 (postman) of user 1000 terminated abnormally with signal 11/SEGV, pr
ocessing...
Aug 29 16:21:54 BaoArch systemd-coredump[63190]: Process 63112 (postman) of user 1000 dumped core.

Seems fixed in v11.10.0 EDIT: nevermind, its not

1 2 3 4 5 6 .. 22 Next › Last »