Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"SEB is Locked" red screen #422

Open
srineer-toddleapp opened this issue Jul 4, 2024 · 4 comments
Open

"SEB is Locked" red screen #422

srineer-toddleapp opened this issue Jul 4, 2024 · 4 comments
Assignees
Labels
in roadmap A solution for the issue is planed for upcoming versions.

Comments

@srineer-toddleapp
Copy link

Describe the bug
When we try to open SEB directly from the search bar or while opening a test, it randomly gives this screen, with no other option than to quit.
Once we get this screen, no matter how many times I restart seb, only this screen is visible. I found that we can solve this if we restart the mac or by reinstalling the seb. What is the reason for this and is there any way to prevent this.

To Reproduce
Steps to reproduce the behavior:

  1. Start a normal already configured seb / or just open safe exam browser app
  2. It randomly gives this issue.

Expected behavior
We should be able to redirected to the start link instead of this screen

Screenshots
SEBlocked

Version Information
Please complete the following information:

@srineer-toddleapp
Copy link
Author

Hey @danschlet , sorry to ping you, but I wanted to know if this is an issue from Seb or is this because of any wrong config?

@danschlet
Copy link
Member

SEB checks if a specific security-related process is running. Unfortunately it turned out that macOS doesn't run this process every time an app is run (results are cached). We will fix this check in an update.
In the meantime you can start some other app (which wasn't running just before) when this error is displayed in SEB. Then that security process is started and SEB shouldn't display the error anymore.

@acamacho-unige
Copy link

For your information, in our BYOD exams what seemed to solved this issue was :

  • Resetting SEB ConfigureClient configuration with defaults delete org.safeexambrowser.SafeExamBrowser
  • Rebooting the computer
  • Configuring client with same configuration again
  • Starting the mock or real exam

Reading your answer @danschlet should I do it differently ?

Thank you very much

@danschlet
Copy link
Member

@acamacho-unige what you did to solve the issue is definitely not necessary.

I will attempt to solve this issue in the next patch update.

@danschlet danschlet added the in roadmap A solution for the issue is planed for upcoming versions. label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in roadmap A solution for the issue is planed for upcoming versions.
Projects
None yet
Development

No branches or pull requests

3 participants