[GH-ISSUE #1268] After using firecfg there are lot's of GIMP errors when launching it #862

Closed
opened 2026-05-05 06:59:45 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @ghost on GitHub (May 7, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1268

Here are some:

Failed to open file “/home/biohazard/.gimp-2.8/devicerc”: open() failed: Permissão negada

Failed to open file “/home/biohazard/.gimp-2.8/controllerrc”: open() failed: Permissão negada

Impossível abrir um ficheiro swap de teste.

Para evitar a perda de dados, verifique a localização e permissões da pasta de swap definida nas suas Preferências (atualmente "/home/ekari/.gimp-2.8").

As mensagens são redirecionadas para stderr.

Originally created by @ghost on GitHub (May 7, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1268 Here are some: Failed to open file “/home/biohazard/.gimp-2.8/devicerc”: open() failed: Permissão negada Failed to open file “/home/biohazard/.gimp-2.8/controllerrc”: open() failed: Permissão negada Impossível abrir um ficheiro swap de teste. Para evitar a perda de dados, verifique a localização e permissões da pasta de swap definida nas suas Preferências (atualmente "/home/ekari/.gimp-2.8"). As mensagens são redirecionadas para stderr.
gitea-mirror 2026-05-05 06:59:45 -06:00
Author
Owner

@SYN-cook commented on GitHub (May 7, 2017):

Can you please run

mkdir ~/.config/firejail
cp /etc/firejail/gimp.profile ~/.config/firejail

and then in ~/.config/firejail/gimp.profile you comment out ipc-namespace, in case there is something like this in the profile?

EDIT: Sorry, I see a bug in GIMP related to this line, but it probably has nothing to do with your issue. What you could quickly check however is folder and file ownerships inside ~/.gimp-2.8. I ask because one way to get to this error is by running sudo gimp in an unfortunate moment.

<!-- gh-comment-id:299707770 --> @SYN-cook commented on GitHub (May 7, 2017): Can you please run ``` mkdir ~/.config/firejail cp /etc/firejail/gimp.profile ~/.config/firejail ``` and then in ~/.config/firejail/gimp.profile you comment out `ipc-namespace`, in case there is something like this in the profile? EDIT: Sorry, I see a bug in GIMP related to this line, but it probably has nothing to do with your issue. What you could quickly check however is folder and file ownerships inside ~/.gimp-2.8. I ask because one way to get to this error is by running `sudo gimp` in an unfortunate moment.
Author
Owner

@ghost commented on GitHub (May 7, 2017):

Ownership is good

<!-- gh-comment-id:299718777 --> @ghost commented on GitHub (May 7, 2017): Ownership is good
Author
Owner

@netblue30 commented on GitHub (May 7, 2017):

You might be running into this problem: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1246908

I would delete ~/.gimp-2.8 directory and start all over again - unless you have some plugins you installed in that directory.

<!-- gh-comment-id:299727635 --> @netblue30 commented on GitHub (May 7, 2017): You might be running into this problem: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1246908 I would delete ~/.gimp-2.8 directory and start all over again - unless you have some plugins you installed in that directory.
Author
Owner

@SYN-cook commented on GitHub (May 7, 2017):

Alternatively, to figure out how is the link with Firejail, you could try to run from the command line simply /usr/bin/gimp, and if that works ok try firejail --noprofile gimp and then firejail gimp

<!-- gh-comment-id:299737095 --> @SYN-cook commented on GitHub (May 7, 2017): Alternatively, to figure out how is the link with Firejail, you could try to run from the command line simply `/usr/bin/gimp`, and if that works ok try `firejail --noprofile gimp` and then `firejail gimp`
Author
Owner

@ghost commented on GitHub (May 8, 2017):

@SYN-cook I followed your commands by order after deleting .gimp and no errors where shown.
@netblue30 Maybe that is the bug, I'm using ubuntu 17.04 but I saw the directory and it was not owned by root

<!-- gh-comment-id:299757898 --> @ghost commented on GitHub (May 8, 2017): @SYN-cook I followed your commands by order after deleting .gimp and no errors where shown. @netblue30 Maybe that is the bug, I'm using ubuntu 17.04 but I saw the directory and it was not owned by root
Author
Owner

@SYN-cook commented on GitHub (May 8, 2017):

Thanks. But you are still running into this issue when launching from a menu? One reason could be that Firejail picks the wrong profile. What you could try

mkdir ~/.config/firejail
cp /etc/firejail/gimp.profile ~/.config/firejail/gimp-2.8.profile
<!-- gh-comment-id:299843324 --> @SYN-cook commented on GitHub (May 8, 2017): Thanks. But you are still running into this issue when launching from a menu? One reason could be that Firejail picks the wrong profile. What you could try ``` mkdir ~/.config/firejail cp /etc/firejail/gimp.profile ~/.config/firejail/gimp-2.8.profile ```
Author
Owner

@netblue30 commented on GitHub (May 9, 2017):

@SYN-cook is right, it will pick up /etc/firejail/default.profile - this one disables ~/.config/gimp* directories. I put a fix in mainline. Thanks for the bug.

<!-- gh-comment-id:300218599 --> @netblue30 commented on GitHub (May 9, 2017): @SYN-cook is right, it will pick up /etc/firejail/default.profile - this one disables ~/.config/gimp* directories. I put a fix in mainline. Thanks for the bug.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#862
No description provided.