Properties window sometimes silently triggers samba error notification window in the background

[marshy719]

Distribution

22.2

Package version

6.4.5

Frequency

Quite often

Bug description

First of all, to be clear, I'm not even using samba or any file sharing related.

Now the problem: Right clicking a file and opening Properties window, sometimes triggers a "Samba" error silently in the background, stating that the file or folder is not shared. And I'm like, ...okay ?? So, that silently opened samba error message blocks me from closing the Properties window, and first I needed to find the samba error window in the background, then close it and then properties is also closeable now.

When I first met with this bug, I was confused of why I'm unable to close the properties window, then I accidentally noticed that silently opened samba error notification window in the background, and I was like whaaa'

This bug happens rarely and totally random, but when it does, it's very annoying. Like, 1 out of 50 is the frequency, but thats just a rough estimate. I tried to trigger it now to no avail, but I'm sure other people out there also already experienced this at least once.

Steps to reproduce

Right click on file or folder, go into properties, and sometimes a samba error window will trigger in the background silently

Expected behavior

Samba error shouldn't happen, it's irrelevant.

Additional information

Thank you for fixing this.

[mtwebster]

Try disabling nemo-share - Edit->Preferences->Plugins:

Then restart nemo.

[marshy719]

Update: I could trigger it. Sorry the interface language is not english, but u can see that it's the properties window, and that error message appeared (It got triggered on the 11th time)

@mtwebster I checked that option, and it was disabled for me the whole time

[mtwebster]

But if nemo-share is disabled, you won't have a 'Sharing' tab in file properties - only Basic, Permissions and Emblems.

If you don't need it, just uninstall it: apt remove nemo-share - this won't affect anything else. Then make sure to restart nemo (close all windows), or:

nemo --quit

[marshy719]

But if nemo-share is disabled, you won't have a 'Sharing' tab in file properties - only Basic, Permissions and Emblems.

If you don't need it, just uninstall it: apt remove nemo-share - this won't affect anything else. Then make sure to restart nemo (close all windows), or:

nemo --quit

I know, and thats why its odd. I ticked it back on then off, now the share tab disappeared. Okay, but doing this just ignoring a bug basically... Other people who dont know about this, still will get this popup, this isn't a solution, its just a workaround

[mtwebster]

I don't know why you're getting the popup - at most the warning is printed at startup if you run nemo from a terminal. If you open a folder's properties and navigate to the Sharing tab it will offer to set it up for you (in Debian-based distros, at least):

I can try in a clean install of Mint 22 and get the same behavior.

Without knowing more about your system or any changes you've made, I'm not sure what to suggest.

[marshy719]

I don't know why you're getting the popup - at most the warning is printed at startup if you run nemo from a terminal. If you open a folder's properties and navigate to the Sharing tab it will offer to set it up for you (in Debian-based distros, at least):

Without knowing more about your system or any changes you've made, I'm not sure what to suggest.

It's a technically a 10days fresh 22.2 install (not an upgraded from earlier versions), no modifications were made, and this bug appeared on day 0 of installing Mint, when nothing was really made..

here's my sys info, I don't know what else you'd want in order to start troubleshooting this, otherwise than testing - as I already said, this bug is randomly appearing and is rare, so you need to keep closing and opening properties window until it triggers. Obviously a user would not open/close properties normally, its just for the test case that it exists and might pop up for a user on a 1st try - hence: random and rare.

You're also getting the same terminal output as I am, so we can already know this pop-up error might be the root of this issue.

[marshy719]

any progress with this? need any further info?