I’m trying to follow https://linuxconfig.org/redhat-8-recover-root-password to reset a root password on a RHEL8 box.
I successfully select ‘e’ on image ‘4.18.0-240.1.1.el8_3.x86_64’ and arrive at the ‘edit’ screen.
I see a ‘linux’ line, but content ends after “crashkernel=auto”. The “resume=” and other stuff from the tutorial is missing.
I added “ rd.break” right after “crashkernel=auto”, but after Ctrl-X, it hangs indefinitely (I waited up to 30 minutes). I never get the switch_root prompt shown by the tutorial.
Any ideas why it would not get to that prompt?
Related
Not able to set session time out in Sitecore 10.2.
I have the following settings, but if I leave the browser open for more than 20 minutes with the launchpad displayed, and then click any button After that, when I click on some button, I expected to be forcibly logged out, but I expected that the session timeout would occur when I left the system for more than 20 minutes without logging out, and then clicked some button.
Please let me know if there is a way to force a session timeout logout.
Having this strange situation. My code is resulting in no such element exception in scenario 1, but in scenario 2 it’s working.
Note: This issue is only on Android, on iOS tests not having issue on login.
Scenario 1: [FAIL]
The activity loads,
Using webdriver wait for checking if the element is clickable,
Timeout after the time limit 20 - 30 second.
Debugging:
I am waiting for app to complete login on the emulator and then performed step 2. Still facing no such element exception despite of activity completely being loaded.
Scenario 2: [PASS] pusing to background
The activity loads,
Pushing app to background and bringing it back,
Using webdriver wait for checking if the element is clickable,
Element is recognized, going ahead with remaining tests.
Operating sytem:
Android - Nexus 6 emulator on Android 8.0
POM:
<testng.version>6.14.3</testng.version>
<appium.java.version>6.1.0</appium.java.version>
<apachepoi.version>3.17</apachepoi.version>
<selenium.version>3.14.0</selenium.version>
<allure.version>1.4.0.RC4</allure.version>
<aspectj.version>1.8.11</aspectj.version>
<firefox.version>3.14.0</firefox.version>
<sauceondemand.version>2.14</sauceondemand.version>
<sauceclientfactory.version>2.14</sauceclientfactory.version>
<saucetestng.version>2.1.23</saucetestng.version>
<log4j.version>1.2.17</log4j.version>
<maven.compiler.target>1.8</maven.compiler.target>
<maven.compiler.source>1.8</maven.compiler.source>
Using Appium, when I launched the app then firstly splash screen appeared then login screen with a keypad. Forgot password button gets hidden by keypad. In this case, Appium is not able to locate forgot password. Click here.
How can I handle this type of problem?
I have also used the code driver.hideKeyboard();, then I get the error in the console as
org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing
the command. (Original error: Soft keyboard not present, cannot hide keyboard) (WARNING: The server did not provide any stack trace information)
Command duration or timeout: 118 milliseconds
MPRemoteMediaPickerController timed out waiting for fence barrier from com.apple.MusicUIService
I get this error on iOS7... only.
I saw another post regarding this error, but no one responded to it.
Cant find any solution on google either
I just started receiving this when I first ran my app on iOS7.1. I'm not even using MPRemoteMediaPickerController (directly). I'm using MPMediaPickerController, but I'm purposefully reusing the object so the user goes back to the same place that they left the next time they choose a song.
In 7.1 I'm getting this warning and the picker displays a useless (can't cancel out) white view.
Solution was to toss the MPMediaPickerController after each use. The error does not seem to happen if I have a fresh one each time.
I have a strange problem. After I logged in with the standard SPLoginViewController, I save the username and the credential. After I startup again, I try to call:
[[SPSession sharedSession] attemptLoginWithUserName:
existingCredential:
On the iOS Simulator (iOS 6.0), it works just fine. On my iPhone (iOS 6.0.1), it does not. SPSession is logging in exactly five minutes after I called the attemptLogin method. SPSession is also logging in when I put my app in the background.
Does anyone know more about this and maybe a solution?
Thanks
It appears there's a known bug in libspotify where sp_session_process_events() will sometimes return excessively high values in next_timeout. I've seen values such as 300100 and 300195 come out of the routine.
One workaround is to set your wait to the max of next_timeout and 50. (Or 100 or whatever your heart desires.) See https://github.com/spotify/cocoalibspotify/issues/140
I wish Spotify would start a known-issues list for libspotify. I wasted over a day trying to dig this one out. Hopefully this post will save someone else the same fate.