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

Nemo context menu on smb share not working as expected - nemo-image-converter does not show up #541

Open
ABenCoding opened this issue Dec 30, 2024 · 1 comment
Assignees

Comments

@ABenCoding
Copy link

Distribution

Linux Mint 22 Cinnamon

Package version

6.2.8

Frequency

Always

Bug description

When accessing a smb network share in Nemo via the network overview the context menu does not show the entry to resize images via the nemo-image-converter. If a mount point is created and the smb share is mounted directly by the user the context menu does show the entry to resize the images as expected. For the user the different behavior is not consisted. It should be the same, no matter how the network share is accessed.

Steps to reproduce

  1. Install nemo-image-converter.
  2. Access a smb networt share via the network overview within Nemo. Do not use a already existing mount point where the network share is mounted to.
  3. Navigate to picture and open the context menu with a right click. The entry to resize the image is missing.

Expected behavior

The context menu should show the entry to resize the selected image no matter how the network share is accessed
If the file / file system is read only the following behavior would be expected:

  • Option A: The resize entry in the context menu should be visible but inactive if the file is read only
  • Option B: Nemo should ask for a location with write access to save the converted image to.

Additional information

No response

@mtwebster mtwebster transferred this issue from linuxmint/nemo Dec 31, 2024
@mtwebster
Copy link
Member

This is probably because currently the extension only works on local files, or at least files with a real path, and not a virtual location (like smb://foo.bar/...)

I'm not sure why this is - the nemo-image-converter extension was ported from nautilus originally. It's probably an artificial restriction to prevent excessive i/o over slow remote connections.

We're planning on revisiting some of these 'internal' restrictions on special file locations in a future release* - we can consider improving access to nemo extensions as well.

@mtwebster mtwebster self-assigned this Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants