Postman launches with a blank screen - postman

This is now the third or fourth time that this has happened in the last couple of weeks: When I launch Postman all I get is a blank screen:
The only way to get around this that I have found is to reboot my workstation, which is of course a PITA.
I am using Ubuntu 18.04.4 LTS, 7.20.0.
Any fixes, workarounds etc are welcomed.

I had same problem on my linux machine. Simply run the following on your terminal until they both tell you no more process to kill.
killall Postman
killall _Postman

I started facing this issue on updating to version - v8.2.3,
Try below approach, which worked for me..
Step 1: Add windows environment variable: POSTMAN_DISABLE_GPU, with the value: true
Step 2: From the same blank screen open a New Postman Window (File -> New Postman Window)

None of these worked for me, I had to go to "System Monitor" and kill a load of processes with names like "postman --no-sandbox", "postman --type=zygote".

Expanding on the previous answer, I put a script together that performs the loop as many times as needed to get Postman working again:
#!/bin/bash
OUTPUT=$(killall Postman 2>&1)
while [ "$OUTPUT" != "Postman: no process found" ]; do
OUTPUT=$(killall Postman 2>&1)
done
OUTPUT=$(killall _Postman 2>&1)
while [ "$OUTPUT" != "_Postman: no process found" ]; do
OUTPUT=$(killall _Postman 2>&1)
done
Make sure you set the permission for the file correctly so you can execute it:
chmod 700 kill_all_postman_procs.sh
To run it:
./kill_all_postman_procs.sh or may you need to do sudo ./kill_all_postman_procs.sh

It's all about GPU driver and setting, it may happen when you don't force disable that setting and running on dual monitor.
On windows 10, to disable it you can disable it from gpu control panel, POSTMAN_DISABLE_GPU, or try to run postman before plugging the 2nd monitor

FOr all options listed above failed to work. My os is Ubuntu 18. The only solution was to install a version that worked. Before you install this version uninstall the currently installed afterwards install this snap version
snap install --channel=v7/stable postman
If you have this specific version installed. run the following
snap refresh --channel=v7/stable postman

This issue came up overnight for me. I resolved this issue by just reinstalling Postman. It kept all my settings and collections. You might like this quick way instead of fiddling with settings.

According to this - https://github.com/postmanlabs/postman-app-support/issues/9193 and figuring out that issue is not fixed for 2 years, I recommend switching to another tool, like advanced rest client from google.

Related

bq command not found

I am currently working on windows machine. Installed WSL to be able to work in Linux env.
Installed the Google Cloud SDK and am able to run gsutil and gcloud commands.
However, while trying to run bq, I get the bq command not found error.
Can someone help me here?
"bq" is one of the default Cloud SDK components, and gets installed by default.
Please check with the command "gcloud components list" to confirm if "bq" is available.
If not, maybe somehow your installation got corrupted. Please try re-installing to fix this issue.
Otherwise, try running these commands, see how the path for all are set and same like "/usr/bin" in the given example. This may reveal some path setting related issues which need to be fixed.
I've run into a similar issue when working on a Windows environment. I have found that calling bq.cmd helps to get the BigQuery commands to execute.
So running:
bq.cmd ls
instead of running:
bq ls
To list datasets in your current project.
In WSL2, install the Google Cloud CLI with this command as shown in the documentation.
curl https://sdk.cloud.google.com | bash
Then restart your WSL installation. The bq command works at both a Windows command prompt and a WSL terminal.

odoo is not showing up properly

I use odoo9 on windows and I run it with pycharme with the following configuration
But when i use the address 'localhost: 8069' odoo is not displaying properly. I noticed in the console there are lines that display 404 and I do not know how to fix them. Even i tried to create a new database but every time it doesn't not shows correctely .Any idea for help please ??
Currently you don't have less in the system So odoo front end couldn't work with out it.
You need to install NodeJS:
Less CSS via nodejs on Windows, install nodejs, reboot (to update the
PATH) and install less:
C:\> npm install -g less
C:\> npm install -g less-plugin-clean-css

ColdFusion 10 Mandatory Update install fails on VM

I need to run the mandatory update for ColdFusion 10 so I can apply the later updates to the server. I downloaded the file and tried the instructions listed here: Mandatory Update Instructions.
I have a singular instance, so this should be fairly straightforward. I download the file, place it in the "hf-updates" folder, and then do java -jar cf10_man_updt.jar and I get the following notice:
Graphical installers are not supported by the VM. The console mode
will be used instead...
The installer proceeds to hang and fails to complete. I then go to option #2: Silent mode. I create my properties file and then do java -jar cf10_mdt_updt.jar -i silent -f install.cfg.txt. I get the following message:
Installer User Interface Mode Not Supported
Unable to load and to prepare the installer in console or silent mode.
This one has the courtesy to actually terminate so I don't have to close the command prompt window to retry, but I'm still nowhere. Any ideas on what I can do?
Alex provided the correct answer. I had been using the JRE in my program files folder (explicitly, actually. There was no javapath to speak of in the environment variables. I shorthanded the command for the sake of brevity). I changed the command to "C:\Coldfusion10\cfusion\jre\bin\java" -jar cf10_mdt_updt.jar and the install ran successfully.

Spring Tool Suite crashes on virtual OS X

I'm trying to get Spring Tool Suite (STS) running on a virtual OS X machine (VMWare 8.0.2) on a iMac host. The virtual OS X machine is the latest OS X: 10.11.2 and is a clean install with just NetBeans 8.1 (with JDK8 Java 1.8). NetBeans works flawlessly.
STS gets the startup splash, it loads the framework and I get to see the interface for approx. 1 second, then I get the "Spring Tool Suite quit unexpectedly"
I've tried STS 3.7.2 and 3.7.1, both have exactly the same problem. I've tried the copy that works native on my host iMac, that too gave the same problem.
Anyone familiar with this problem? Google gives me no results. Would it be impossible to run STS on a Virtual Machine?
I could post the dump from OS X but that would be a lot of text, please let me know if that would be helpful?
Thanks in advance!
STS Dumpfile (Dropbox)
There are at least two ways you could try to work around this problem.
1) run STS with a JDK7 at least once. JavaFx is not supported with JDK7 and STS will automatically fallback on using the old dashboard. This should allow you to launch STS succesfully. You can then change the preference here: "Preferences >> Spring >> Dashboard" to always use the old dashboard. Then go back to running with JDK8 if you wish.
2) Alternatively you can 'hack' the metadata in the workspace to set the preference to use the old dashboard (use this method if the above one seems too onerous, maybe you don't have a old JDK handy)
The metadata file you want to edit is this one (from the root of workspace folder):
.metadata/
.plugins/
org.eclipse.core.runtime/
.settings/
org.springsource.ide.eclipse.dashboard.ui.prefs
If the file doesn't exist, create it and add these two line:
eclipse.preferences.version=1
org.springsource.ide.eclipse.dashboard.uidashboard.use.old=true
If the file exists you only need to add (or change) this line:
org.springsource.ide.eclipse.dashboard.uidashboard.use.old=true
STS was keep crashing on my macos machine so I had to install every time
so I came up with a solution :
cd $HOME
sudo codesign --force --deep --sign - /Applications/SpringToolSuite4.app

How to build and install the latest nightly Firefox OS on Alcatel One Touch Fire?

I want to upgrade Firefox OS 1.1 on my Alcatel One Touch Fire to the master branch (the latest revision). After having read the Mozilla Wiki, I cloned the B2G repository, built it for the hamachi target by typing:
./config.sh hamachi && ./build.sh
(There are even prebuilt images)
Now is the hardest part, since Alcatel phones are not rooted and seems to have a locked bootloader.
The docs say that I should flash the device by typing:
./flash.sh
But all I get are these errors:
adbd cannot run as root in production builds
remount failed: Operation not permitted
push: /home/user/B2G/objdir-gecko/dist/b2g/dictionaries/en-US.aff -> /system/b2g/dictionaries/en-US.aff
failed to copy '/home/user/B2G/objdir-gecko/dist/b2g/dictionaries/en-US.aff' to '/system/b2g/dictionaries/en-US.aff': Read-only file system
Could anybody write an simple step-by-step tutorial (easier than this) on how to install the latest Firefox OS to a stock Alcatel One Touch Fire?
I guess first we can check if the phone itself is rooted.
You could try,
$ adb shell
And if shows,
root#android:/ #
Then I think the phone is rooted, and you can flash your phone with ./flash.sh.
If it is not rooted, I think the link you mentioned has provided the steps to create a new boot.img so that you could root the phone.
Here is an excerpt from Mozilla guide on flashing phones related to Hamachi (Alcatel One Touch Fire):
Best build for Hamachi: moz-central Use your LDAP to go here: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2g_ril/latest-hamachi-mozilla-central/
And then run this script command line: fullflash_gecko_ril_gaia.sh You
may need to preface this with ./ but it should just run upon your
hitting enter. DON'T run ./flash.sh. THIS CAN BRICK YOUR HAMACHI :( -
GB
What is my order of operations from the beginning?
FOR ALL DEVICES... AFTER you have installed ADB, Git, and Xcode, you should:
Connect your device to your machine via USB. You're SURE it's plugged in? OK then...
Get your build with your LDAP credentials (from moz-central): Buri: Need from Naoki Hamachi:
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2g_ril/latest-hamachi-mozilla-central/
Run this script: fullflash_gecko_ril_gaia.sh
Download gaia from github (it's easier than the command line as you avoid a pull request) at: https://github.com/mozilla-b2g/gaia Along
the right hand side there is an option to "Download ZIP." Unpack that
into a folder, open Terminal and "cd" (ask Stephany or Francis if you
need help with this) into the folder (i.e. wherever you unpacked your
zip file). Run "make reset-gaia".
You should see... a whole bunch of stuff scrolling by on the command line and your device should reboot. If your device does NOT
reboot, try ADB reboot.