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 freezes while initializing the user interface." #814

Closed
naveensethupathy opened this issue Feb 28, 2024 · 33 comments
Closed

"SEB freezes while initializing the user interface." #814

naveensethupathy opened this issue Feb 28, 2024 · 33 comments
Assignees
Labels
can't reproduce This issue cannot be reproduced and thus also not be fixed. information required This issue lacks information or requires feedback. stale This issue had no recent activity and will thus soon be closed.

Comments

@naveensethupathy
Copy link

WhatsApp Image 2024-02-28 at 07 42 01_a94847ea
SEF freezes during the initialization of the user interface. I'm using the latest version, but it's not working for me. I have McAfee antivirus installed, and the screen hangs for an extended period

@strau0106
Copy link

Without logs there is nothing anyone could do about this.

@dbuechel
Copy link
Member

dbuechel commented Mar 6, 2024

Exactly, please provide the log files of the affected session as mentioned by @strau0106. They can be found under %LocalAppData%\SafeExamBrowser\Logs.

@dbuechel dbuechel added the information required This issue lacks information or requires feedback. label Mar 6, 2024
@naveensethupathy
Copy link
Author

@dbuechel
Copy link
Member

dbuechel commented Mar 15, 2024

Okay, something is definitely interfering with SEB, the startup procedure can't even be terminated successfully:

2024-03-15 06:54:49.368 [07] - WARNING: [DesktopMonitor] Failed to get currently active desktop!
2024-03-15 06:54:50.410 [23] - WARNING: [DesktopMonitor] Failed to get currently active desktop!
2024-03-15 06:54:51.416 [23] - WARNING: [DesktopMonitor] Failed to get currently active desktop!

The client log shows an array of process terminations and then both runtime and client logs end. Please search the Windows Event Viewer system utility for any warning or error messages related to Safe Exam Browser. They are normally found under Windows Logs > Application, but the other logs may also contain relevant information.

@naveensethupathy
Copy link
Author

Okay, something is definitely interfering with SEB, the startup procedure can't even be terminated successfully:

2024-03-15 06:54:49.368 [07] - WARNING: [DesktopMonitor] Failed to get currently active desktop!
2024-03-15 06:54:50.410 [23] - WARNING: [DesktopMonitor] Failed to get currently active desktop!
2024-03-15 06:54:51.416 [23] - WARNING: [DesktopMonitor] Failed to get currently active desktop!

The client log shows an array of process terminations and then both runtime and client logs end. Please search the Windows Event Viewer system utility for any warning or error messages related to Safe Exam Browser. They are normally found under Windows Logs > Application, but the other logs may also contain relevant information.

how to fix this issue

@naveensethupathy
Copy link
Author

seb event.txt
@strau0106 please check this out

@strau0106
Copy link

Have you tried on another computer?

@naveensethupathy
Copy link
Author

Have you tried on another computer?

yes it works fine in my friends computer

@dbuechel
Copy link
Member

Again, please search the Windows Event Viewer system utility for any warning or error messages related to Safe Exam Browser. They are normally found under Windows Logs > Application, but the other logs may also contain relevant information. If we can't reproduce an issue, we cannot investigate and potentially fix it.

@dbuechel
Copy link
Member

yes it works fine in my friends computer

That would indicate that an issue with your computer or its configuration is more likely than an issue with SEB itself.

@naveensethupathy
Copy link
Author

yes it works fine in my friends computer

That would indicate that an issue with your computer or its configuration is more likely than an issue with SEB itself.

how to fix that

@dbuechel
Copy link
Member

Again, please search the Windows Event Viewer system utility for any warning or error messages related to Safe Exam Browser. They are normally found under Windows Logs > Application, but the other logs may also contain relevant information. If we can't reproduce an issue, we cannot investigate and potentially fix it.

@davidyucheng
Copy link

did you solve it? bro

@dbuechel
Copy link
Member

dbuechel commented Apr 9, 2024

@davidyucheng Try to abstain from unnecessary comments. We need a (ideally reliable) way to reproduce an issue, otherwise we cannot do much in most cases.

@dbuechel dbuechel added the can't reproduce This issue cannot be reproduced and thus also not be fixed. label Apr 9, 2024
Copy link

github-actions bot commented May 8, 2024

This issue is stale because it has been open for 28 days with no activity. It will soon be closed automatically if there are no updates.

@github-actions github-actions bot added the stale This issue had no recent activity and will thus soon be closed. label May 8, 2024
@SATHWIK-2004
Copy link

Yes same problem ! Did you found any solution

@davidyucheng
Copy link

Yes same problem ! Did you found any solution

Reset computer

@SATHWIK-2004
Copy link

solution

  • Yes I restart my computer but the issue is still going on

@SATHWIK-2004
Copy link

Yes same problem ! Did you found any solution

Reset computer

IMG20240514143243.jpg

@dbuechel
Copy link
Member

Please provide the log files of the affected session(s). They can be found under %LocalAppData%\SafeExamBrowser\Logs.

@strau0106
Copy link

@SATHWIK-2004 Do you use something like wallpaper engine?

@github-actions github-actions bot removed the stale This issue had no recent activity and will thus soon be closed. label May 15, 2024
@dbuechel
Copy link
Member

dbuechel commented May 16, 2024

@SATHWIK-2004 Something (or rather some third-party software) interferes with the kiosk mode induction of SEB. Specifically, the desktop monitoring seems to be failing:

2024-05-14 13:05:49.423 [29] - WARNING: [DesktopMonitor] Failed to get currently active desktop!

Try to consecutively exclude resp. deactivate any potentially interfering software. It might also be an anti-virus software which is interfering, in case you're using one.

@SATHWIK-2004
Copy link

IMG20240523090930.jpg

I have deleted the log files many times but - this problem is not solved

@SATHWIK-2004
Copy link

@SATHWIK-2004 Something (or rather some third-party software) interferes with the kiosk mode induction of SEB. Specifically, the desktop monitoring seems to be failing:

2024-05-14 13:05:49.423 [29] - WARNING: [DesktopMonitor] Failed to get currently active desktop!

Try to consecutively exclude resp. deactivate any potentially interfering software. It might also be an anti-virus software which is interfering, in case you're using one.

I uninstalled the safe exam browser I deleted the log files and I tried all methods that mentioned !
Worst experience with the app !
More bugs less user experience
Worst app I have ever seen

@emberfox205
Copy link

Hello, I have also encountered a similar problem. Though it seems to begin at the moodle page. There was a class in my university that went over the installation steps for SEB, and I was the only one with this issue. The version issued by the school was 3.5.0 but this issue appears with the latest version of SEB as well.

image

Despite that, I can still access SEB, but then another issue pops up, which is the frozen screen while initializing user interface:

image

Logs:

2024-06-19_22h33m06s_Client.log
2024-06-19_22h33m06s_Runtime.log
2024-06-19_22h37m27s_Client.log
2024-06-19_22h37m27s_Runtime.log
2024-06-19_22h47m29s_Client.log
2024-06-19_22h47m29s_Runtime.log
2024-06-19_23h40m49s_Client.log
2024-06-19_23h40m49s_Runtime.log
2024-06-19_23h50m28s_Client.log
2024-06-19_23h50m28s_Runtime.log
2024-06-20_00h25m10s_Client.log
2024-06-20_00h25m10s_Runtime.log

@dbuechel
Copy link
Member

@emberfox205 Thanks for the information. I can't see anything suspicious in the log files, but it is apparent that the initialization of the application does not complete. Can you find any related information in the Event Viewer system application (under Windows Logs > Application)?

Either way, please update to version 3.7.1 and try whether that resolves your issue. If not, I'm afraid I'd need a way to reproduce the issue, otherwise there's not much I can do without a clear idea of what could be the problem.

@emberfox205
Copy link

@dbuechel All the event logs with the source SafeExamBrowser are just Service Started Successfully. Updating to 3.7.1 did not work either. I am currently in Windows Insider Program (Dev Channel) so that might interfere with things. I'll report back after resetting the device.

@emberfox205
Copy link

@dbuechel After unenrolling from Windows Insider and resetting my device, I was met with a different issue: "ERROR: Caught unexpected exception while performing operation 'LazyInitializationOperation'!". The most recent info in Event Viewer are Windows Error Reporting's MoAppCrash and AppxDeploymentFailureBlue

Logs:

2024-06-21_17h34m46s_Client.log
2024-06-21_17h34m46s_Runtime.log

@dbuechel
Copy link
Member

@emberfox205 Please update to the latest version 3.7.1. If the issue still occurs, ensure that you have given SEB permission to access the location services (see Settings > Privacy & security > Location in the system control panel of Windows).

@emberfox205
Copy link

@dbuechel Thank you very much. The issue has been resolved.

Copy link

This issue is stale because it has been open for 28 days with no activity. It will soon be closed automatically if there are no updates.

@github-actions github-actions bot added the stale This issue had no recent activity and will thus soon be closed. label Jul 24, 2024
Copy link

github-actions bot commented Aug 7, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can't reproduce This issue cannot be reproduced and thus also not be fixed. information required This issue lacks information or requires feedback. stale This issue had no recent activity and will thus soon be closed.
Projects
None yet
Development

No branches or pull requests

6 participants