I wonder if anyone experienced that - after the executable is finished (using Appium Windows driver for WPF application) - the Ctrl is pressed.
I experienced it on 2 out of 3 machines and cant find the reason why it is happening
regards,
arbus
You can verify at the along your test if Ctrl key is pressed, but to do that you will need to standby your test and only after Ctrl be pressed your test will run till the end.
Otherway your test will run so fast you will not press Ctrl at the right moment of that Assert verification.
Related
Newbie here. For education purposes I needed to download the OVA file of Sans Sift workstation to run on my VMware workstation 16 pro. It downloaded but never really open up. It ended up with a black screen with a blinking cursor. Ran it again and it is the same again. Uninstall and install again same outcome. Anyone encountered something like this?
Thanks
You may still be able to login - press Alt + F2 (or maybe F1). Login at the prompts and then type the command startx
This should hopefully give you the gui.
Just as above, I was able to get the login screen to show up by pressing alt f1, altf2 then alt f1 again, so i don't know which one really worked. Anyway once I logged in I was able to use apt-get update and then i used apt-get dist-upgrade, and once that was complete I restarted the VM and the login screen appeared and once logged in, the Ubuntu GUI was there and it has been working ever since.
I want to run a program on a server.
But I don't want it shoutdown immediately after I press power button.
The expected result is server could finish program properly and get the test result. Then shutdown finally.
The program running environment would be under the Ubuntu 20.04 Virtual Terminals(TTY).
I have tried some methods on the web I found (like change some system files). But it just disabled the power button function. I can't connect how to detect in my program.
I am curious is it possible to detect power button pressed or not in the program we wrote?
If it is possible, how to do?
Thank you very much!
I would have preferred to comment but I don't have enough reputation.
Have you tried to modify the /usr/share/doc/acpid/examples/powerbtn.sh script?
This page seems to describe how to proceed. But I haven't gone deep.
I'm using a thrid-party screen capturing application (Screenpresso). It's configured to start screen-capturing when I press PrtSc. And indeed it works except when Intellij has Windows focus. In fact, to screen capture code I have to focus on any other window press PrtSc and then select the area within Intellij.
I've looked through all the settings, and especially the Keymap settings, and I can't see anything else that has been assigned to PrtSc. Of course, I'm not really sure; when I try to find a setting via nothing happens, as pressing PrtSc has no effect.
I know this used to work for me in previous versions of Intellij (though I can't remember what versions). But PrtSc used to work in Intellij just like every other application.
So I guess the question is, why is Intellij eating the PrtSc keypress event? And can I turn it off so that the event gets correctly passed to my dedicated screen capturing application.
Intellij 2019.2.4
Windows 10, 64b
This turned out to be an issue with Screenpresso:
https://www.screenpresso.com/support/hot-keys/
Why shortcut [print screen] key does not always work?
This must be because you run your application with elevated
privileges (with admin rights) (the UAC must have displayed a popup
at startup).
For security reasons, Screenpresso can handle shortcuts
from Windows running with elevated privileges only when it is
installed in Program Files folder.
To fix this, you should install
Screenpresso in Program Files folder which is not the default
behavior:
Uninstall Screenpresso
Run again Screenpresso: Right click Screenpresso.exe and select Run as administrator
Click on the INSTALL on this computer button while holding the Control key or click on the sub-menu Install for all users:
Some users have this problem, first reported 5 years ago: Find here
Crash dumps (java_error_in_*.log in the user's home directory) can help to understand it better.
I have encountered a problem with uVision and Hitex emulator (Tanto2) on a Win10 laptop (fresh install).
My initial setup was UV5.23, I updated to 5.24 and made tentative with 5.25 on Keil's request.
I have a dedicated SDK release for UV5.23, I switched to a new one for UV5.24.
Firmware emulator was reflashed when I was using SDK for UV5.23, and updated when moving to UV5.24
What I can do:
- start UV5, open my project,
- start a debug session on the emulator, load my project, make the first run and stop debug session.
Whatever the release I use, the problem appears when I want to start a second debug session on the emulator. Once I click on the Start Debug, UV5 crashes with this message:
"uVision IDE has stopped working
A problem caused the program to stop working correctly. Windows will ..."
I need to relaunch UV5 to run a new debug session.
The setup using Keil 5.23 and its dedicated SDK release was OK till the end of March.
Since the end of March, the Windows updates that have appeared are: KB4088776, KB4093110, KB4093112, KB890830, KB4099989.
I tried uninstalling KB4099989, but there was no change, the problem is still present.
Is there a link with these updates?
If someone encounters the same problem and was able to solve it, I hear you :-)
The same problem appears on the laptop of my colleague whereas it is working fine before the last Windows update.
Thank you in advance for your help.
This is because of the below issue. If there is a crash in application during dll unload, windows adds an entry in registry to ignore a future unload dll request. So if the application tries to load the dll again within the same session, then the application crashes.
As a workaround goto the below location in registry,
My Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
and delete the unload registry path. Everytime if there is a new crash then the dll will be added back which needs to be removed.
[work around]
I also get crashes when entering debugger session, however I noticed that it occurs only if I click the debugger icon and then leave the pointer over that icon. I have never had it crash if I click and immediately move the pointer away.
I have to run some test suite on two remote machines.
So, after one suite, i reset the app and for the next suite, app starts well.
But the problem is, after completing the total execution
driver.quit()
just close the app but it does not close the simulator as
no reset is true.
So, is there a way to close the xcode simulator using appium or selenium?
I do not want to use ssh and full reset option.
I also do not want to use
killall "Simulator" as it needs ssh connection.
try this
String closesim[] = {"killall","iOS Simulator"};
Runtime.getRuntime().exec(closesim);
You can try directly close simulator by passing below code in you AfterClass,Or AfterSuit method . which close all the simulator which is open in system.
For my case its working i am not sure in your cases its work because if you pass below command in terminal you can find its close your simulator.
runtime.exec("xcrun simctl shutdown all");