"Unhandled exception" error on Linux

I am using the latest version of Linux Intel DEB namely 8.2.4. I have purchased a license and I am disappointed with the Linux version.

Let me start with the most basic one - it's an error that is interfering with my work, namely: "Unhandled exception: Access violation". It appears whenever I scan any local range on my network. The default settings of the program.

In addition I noticed that there is no button to close the window of the account manager. The developer simply forgot to add a close button (cross).

I really hope that the above mentioned problems will be solved.

Unfortunately, we're unable to reproduce the problems you've described. The Credential Manager window does include a close button as shown in the attached screenshots, and we have not encountered any "Unhandled exception: Access violation" errors during network scans using the default settings.

To help us investigate further, could you please provide the following details:

1. Your exact Linux distribution and version
2. Your desktop environment (e.g., GNOME, KDE, etc.)
3. Any custom settings or modifications you've applied to the system or application

Linux parrot 6.12.12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.12-1parrot1 (2025-02-27) x86_64 GNU/Linux

MATE

No custom modifications.

I appreciate you looking into my problem and providing screenshots of the application from ubunta. Judging by the screenshots everything works well there and I'm thinking of using Ubuntu to use your application, but if the problem can be solved on my current OS it would be great.

I have tested the app on Parrot Linux 6.3 and can confirm the issue with some windows missing the close button.

It appears that certain themes do not draw any window decorations, including the [X] button for popup windows. As a workaround, you can close the windows using Alt + F4, or launch mate-appearance-properties in a terminal, select the current theme, then click Customise, go to Window Border, and choose, for example, BlueMenta. This should ensure that all popup windows display the close button.

However, we were still unable to reproduce the error message when scanning the network. If you would like us to investigate further, please submit a ticket and send us your configuration file via File - Current Config - Save to File from the main menu.

I appreciate that you have already tried to fix this problem. It would be easier for me to change the OS than to try to fix this bug, because if I give you the config it will not make much difference in my opinion. I am using the default config and have also tried several times to reset the settings with the "Reset to Default" function and still get the scanning error. I will assume that this problem occurs on my version of the OS.
Thank you again for your quick replies. You did a great job.

Thank you for your kind words and for the detailed explanation.

I would recommend updating to Parrot Linux 6.3, as it includes several fixes that may address the issue you're experiencing. If the problem persists after the update, please do let us know.

We'll be happy to investigate further using a debug build, as we're committed to resolving even rare and hard-to-reproduce bugs.

Hello. I hate to take up your time again but I think I've started to realize what the problem might be.
I took your advice and upgraded to Parrot Linux 6.3 and indeed the error disappeared when scanning with the default config but if I use the following settings (I have attached them to this post) the error comes back.
I don't really understand what's wrong but since the error appears only after setting these settings - I think it's in them.

I repeat that there is no error when scanning with default settings.

Download the configuration: https://limewire.com/d/Lanjc#5zqyTHxgCz
(I tried to attach it to this post but I understand I can't upload files here).

Thank you for sharing the configuration file. Unfortunately, the issue is still not reproducible on our end, which suggests it may be related to a specific setting on your system or a particular device on your network.

To help us investigate further, we have prepared a debug build that provides additional information in the error message. Please follow the steps below:

1. Download the debug netscan binary.
2. Unpack the archive and replace the existing /usr/bin/netscan file with the new one.
3. If required, make it executable by running chmod +x netscan.
4. Run the scan as usual and post a screenshot of the error message here.

This should provide us with the necessary details to identify the root cause.

Hi. Thank you for providing the debug version. I did manage to catch the error again with the current config I posted above.


In the regular version of the program when an error occurred I could click “Ok” and scanning continued but here after the error occurred all scanning froze but the program itself remains clickable, i.e. only the scanner itself froze. Perhaps this is a peculiarity of the debug version.

I also came across 2 other errors.

I have to report that I managed to catch this same error on Ubuntu 24.04.2 LTS.

I'm attaching the config and screenshots (actually the config hasn't changed, but just in case I'll upload it too)




config: http://temp.sh/vHEQW/config.xml

Thank you for sharing your findings. It's now clear where the crash occurs. However, the root cause appears to lie within third-party code. On Linux and macOS, our application uses an open-source library called libsmb2 to discover shared folders. This generally works well, but in rare instances, closing the connection (the Destroy method internally calls smb2_destroy_context from libsmb2) leads to stack corruption followed by a crash.

This issue may stem from a bug in libsmb2 or possibly from a specific network device returning a malformed SMB reply that causes the library to fail. I came across a similar case reported some time ago, but it appears the developer was unable to pinpoint the problem.

It doesn't seem to be a concurrency issue. I've scanned three different devices with various operating systems and shared folders multiple times without any problems:



What I would recommend is scanning your devices in smaller groups to help isolate which one might be triggering the problem. Once identified, we may be able to reproduce and investigate further.

Additionally, try disabling the features highlighted in the screenshot above one by one and re-running the scan each time:

1. First, disable authentication and run the scan again.
2. Second, turn off the disk space and write access checks, then scan again.
3. Third, disable scanning for shared folders entirely, and test once more.

It would be helpful to know which of these options, if any, resolves the issue.