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

Can't open images in hidden directories (Ubuntu) #799

Open
SamMatzko opened this issue Dec 26, 2022 · 3 comments
Open

Can't open images in hidden directories (Ubuntu) #799

SamMatzko opened this issue Dec 26, 2022 · 3 comments
Labels
bug Something isn't working platform-specific Related to specific platforms

Comments

@SamMatzko
Copy link

Pixelorama version:

0.10

OS/device including version:

Ubuntu 22.04 LTS (also occurred on Ubuntu 20.04 LTS)

Issue description:

The file dialog prevents me from being able to open files that are in hidden directories. Typing the directory/file path in either of the text boxes does nothing when I hit Enter. When I show hidden files and double-click a hidden directory, it goes to the hidden directory (for example the path at the top says /home/user/.local) but none of the files or folders inside the hidden directory are displayed; the list is empty.

Also, even when I run the app from the terminal, for example pixelorama /home/user/.local/inv.png, Pixelorama opens but gives me an error: Can't load file 'inv.png'. Error code 12 However, if I copy that exact inv.png and put it in a non-hidden directory, it works perfectly and imports the image.

Steps to reproduce:

In the file dialog:

  1. Open Pixleorama
  2. Open the File menu and click Open... (or just press Ctrl+O)
  3. You can either 1. Click on the eye icon to show hidden files and then double-click on a hidden directory (such as ~/.local) or 2. type the path to the hidden file in the File: text box and hit Enter
  4. Depending on which you do, either 1. the hidden directory will display as empty or 2. the file dialog will do nothing.

In the terminal:

  1. Open a terminal
  2. Type pixelorama followed by a space and the path to the file you want to open, for example: pixelorama /home/user/.local/image.png, then hit Enter
  3. Pixelorama will open, but once you close the spash screen you see a dialog like this one:
    image

This is rather annoying, especially considering that other image-editing apps with non-native file dialogs (like Krita and Gimp) can open hidden files.

@SamMatzko SamMatzko added the bug Something isn't working label Dec 26, 2022
@OverloadedOrama
Copy link
Member

I'm using openSUSE Tumbleweed and I cannot replicate this issue. I tried 0.10, 0.10.3 both flatpak and non-flatpak versions and the current master branch and they all seem to be able to load files from /home/user/.local normally. The hidden files and directories all appear in the file dialog also, once the eye icon has been pressed. Opening files from the terminal also worked fine for me. I'm not sure what is causing the issue for you, but I will keep my eye on it.

@tpillow
Copy link

tpillow commented Feb 14, 2023

Hello; I encountered this too. Here are some data points I found:

I too can reproduce exactly as described on Ubuntu 20.04.4 LTS, Pixelorama version 0.10 - but only on the installed version.

After cloning the repo and running from the Godot editor, hidden files show and open perfectly fine. If I manually export the project from Godot and run that executable (Linux/X11 64-bit), things also work fine.

@Variable-ind
Copy link
Contributor

have you tried enabling filesystem permission for pixelorama if you are using flatpak version?
sudo flatpak override com.orama_interactive.Pixelorama --filesystem=host
or sudo flatpak override com.orama_interactive.Pixelorama --filesystem=host

@OverloadedOrama OverloadedOrama added the platform-specific Related to specific platforms label Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working platform-specific Related to specific platforms
Projects
None yet
Development

No branches or pull requests

4 participants