SafeExamBrowser / seb-win-refactoring

Safe Exam Browser for Windows.
https://www.safeexambrowser.org/news_en.html
Mozilla Public License 2.0
190 stars 129 forks source link

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

Closed naveensethupathy closed 3 months ago

naveensethupathy commented 8 months ago

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 commented 8 months ago

Without logs there is nothing anyone could do about this.

dbuechel commented 8 months ago

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

naveensethupathy commented 8 months ago

@strau0106 please check this out 2024-03-15_06h54m25s_Client.log 2024-03-15_06h54m25s_Runtime.log

dbuechel commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

seb event.txt @strau0106 please check this out

strau0106 commented 8 months ago

Have you tried on another computer?

naveensethupathy commented 7 months ago

Have you tried on another computer?

yes it works fine in my friends computer

dbuechel commented 7 months ago

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 commented 7 months ago

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 commented 7 months ago

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 commented 7 months ago

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 commented 7 months ago

did you solve it? bro

dbuechel commented 7 months ago

@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.

github-actions[bot] commented 6 months ago

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.

SATHWIK-2004 commented 6 months ago

Yes same problem ! Did you found any solution

davidyucheng commented 6 months ago

Yes same problem ! Did you found any solution

Reset computer

SATHWIK-2004 commented 6 months ago

solution

SATHWIK-2004 commented 6 months ago

Yes same problem ! Did you found any solution

Reset computer

IMG20240514143243.jpg

dbuechel commented 6 months ago

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

SATHWIK-2004 commented 6 months ago

Please provide the log files of the affected session(s). They can be found under `%LocalAppData%\SafeExamBrowser\Logs`. 2024-05-14_12h56m54s_Client.log 2024-05-14_12h56m54s_Runtime.log 2024-05-14_13h08m41s_Client.log 2024-05-14_13h08m41s_Runtime.log 2024-05-14_13h33m34s_Client.log 2024-05-14_13h33m34s_Runtime.log 2024-05-14_13h39m43s_ResetUtility.log 2024-05-14_13h44m46s_Client.log 2024-05-14_13h44m46s_Runtime.log 2024-05-14_13h53m24s_Client.log 2024-05-14_13h53m24s_Runtime.log 2024-05-14_13h53m39s_Client.log 2024-05-14_13h53m39s_Runtime.log 2024-05-14_13h58m30s_Client.log 2024-05-14_13h58m30s_Runtime.log 2024-05-14_13h59m51s_Client.log 2024-05-14_13h59m51s_Runtime.log 2024-05-14_14h05m49s_Client.log 2024-05-14_14h05m49s_Runtime.log 2024-05-14_14h07m39s_Client.log 2024-05-14_14h07m39s_Runtime.log 2024-05-14_14h08m11s_Client.log 2024-05-14_14h08m11s_Runtime.log 2024-05-14_14h20m01s_Client.log 2024-05-14_14h20m01s_Runtime.log 2024-05-14_14h31m43s_Client.log 2024-05-14_14h31m43s_Runtime.log 2024-05-14_14h38m38s_Client.log 2024-05-14_14h38m38s_Runtime.log 2024-05-14_14h59m29s_Client.log 2024-05-14_14h59m29s_Runtime.log

strau0106 commented 6 months ago

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

dbuechel commented 6 months ago

@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 commented 5 months ago

IMG20240523090930.jpg

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

SATHWIK-2004 commented 5 months ago

@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 commented 5 months ago

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 commented 5 months ago

@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 commented 5 months ago

@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 commented 5 months ago

@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 commented 4 months ago

@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 commented 4 months ago

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

github-actions[bot] commented 3 months ago

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[bot] commented 3 months ago

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