github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #2658] Gimp not working #1675

New issue

Closed

opened 2026-05-05 08:19:26 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 08:19:26 -06:00

Owner

Originally created by @CodeArtisan00 on GitHub (Apr 21, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2658

Specs- Manjaro(KDE): kernel-4.19.34.1, Firejail-0.9.58.2-1, GIMP-2.10.10-1

I tried to open gimp but nothing launches. When I looked at task manager it shows gimp as zombie. Don't know what goes wrong. Debug

Originally created by @CodeArtisan00 on GitHub (Apr 21, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2658 Specs- Manjaro(KDE): kernel-4.19.34.1, Firejail-0.9.58.2-1, GIMP-2.10.10-1 I tried to open gimp but nothing launches. When I looked at task manager it shows gimp as [zombie](https://imgur.com/Ov7x5fn). Don't know what goes wrong. [Debug](https://gist.github.com/Neo00001/c30e3939b547c5646bb42904c5831f97)

gitea-mirror closed this issue

2026-05-05 08:19:27 -06:00

gitea-mirror commented

2026-05-05 08:19:29 -06:00

Author

Owner

@FOSSONLY commented on GitHub (Apr 21, 2019):

Hm.. with Debian-Buster and Firejail 0.9.58, Gimp is running flawlessly. I would kill all Gimp/Firejail instances, and retest it again. Sometimes a process hangs under some circumstances, what block new instance of same process. I didn't found any other problems.

@FOSSONLY commented on GitHub (Apr 21, 2019): Hm.. with Debian-Buster and Firejail 0.9.58, Gimp is running flawlessly. I would kill all Gimp/Firejail instances, and retest it again. Sometimes a process hangs under some circumstances, what block new instance of same process. I didn't found any other problems.

gitea-mirror commented

2026-05-05 08:19:31 -06:00

Author

Owner

@CodeArtisan00 commented on GitHub (Apr 21, 2019):

Hm.. with Debian-Buster and Firejail 0.9.58, Gimp is running flawlessly. I would kill all Gimp/Firejail instances, and retest it again. Sometimes a process hangs under some circumstances, what block new instance of same process. I didn't found any other problems.

same thing is happening with kdenlive. Most likely, it's an arch issue. Although browsers & many other apps are working flawlessly.

@CodeArtisan00 commented on GitHub (Apr 21, 2019): > Hm.. with Debian-Buster and Firejail 0.9.58, Gimp is running flawlessly. I would kill all Gimp/Firejail instances, and retest it again. Sometimes a process hangs under some circumstances, what block new instance of same process. I didn't found any other problems. same thing is happening with kdenlive. Most likely, it's an arch issue. Although browsers & many other apps are working flawlessly.

gitea-mirror commented

2026-05-05 08:19:32 -06:00

Author

Owner

@curiosity-seeker commented on GitHub (Apr 21, 2019):

Have you tried firejail --debug /usr/bin/gimp ? What's the output of echo $PATH ? I'm asking because I'm also using Manjaro and I had to modify the PATH as /usr/local/bin was not included (or, at least, not at the beginning of PATH). I added the following to ~/.bashrc:

export PATH="/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/seeker/bin"

If my assumption is correct, firejail --list should reveal that your browser etc. are not sandboxed.

@curiosity-seeker commented on GitHub (Apr 21, 2019): Have you tried `firejail --debug /usr/bin/gimp` ? What's the output of `echo $PATH` ? I'm asking because I'm also using Manjaro and I had to modify the PATH as `/usr/local/bin` was not included (or, at least, not at the beginning of PATH). I added the following to ~/.bashrc: `export PATH="/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/seeker/bin" ` If my assumption is correct, `firejail --list` should reveal that your browser etc. are **not** sandboxed.

gitea-mirror commented

2026-05-05 08:19:32 -06:00

Author

Owner

@CodeArtisan00 commented on GitHub (Apr 21, 2019):

If my assumption is correct, firejail --list should reveal that your browser etc. are not sandboxed.

Apart from gimp & kdenlive, everything else is working for me. Both are being showed as zombie.
debug output- https://gist.github.com/Neo00001/c30e3939b547c5646bb42904c5831f97

@CodeArtisan00 commented on GitHub (Apr 21, 2019): > If my assumption is correct, `firejail --list` should reveal that your browser etc. are **not** sandboxed. Apart from gimp & kdenlive, everything else is working for me. Both are being showed as zombie. debug output- https://gist.github.com/Neo00001/c30e3939b547c5646bb42904c5831f97

gitea-mirror commented

2026-05-05 08:19:33 -06:00

Author

Owner

@CodeArtisan00 commented on GitHub (Apr 21, 2019):

btw, firejail --noprofile is working for gimp.

@CodeArtisan00 commented on GitHub (Apr 21, 2019): btw, firejail --noprofile is working for gimp.

gitea-mirror commented

2026-05-05 08:19:33 -06:00

Author

Owner

@ghost commented on GitHub (Apr 28, 2019):

@Neo00001 Looking at your debug log, I see this on line 482:

Warning: an existing sandbox was detected. /usr/bin/gimp will run without any additional sandboxing features

To me that suggests gimp was called from within another firejailed application (an image-viewer or the likes?). If so, that would explain what you're describing. As a general rule, applications started from within any other firejailed program inherit the parent's profile. And in this case that profile isn't built to access gimp. If what I'm describing here fits your use-case, try starting gimp independently and open whatever image file(s) you need from within gimp.

@ghost commented on GitHub (Apr 28, 2019): @Neo00001 Looking at your debug log, I see this on line 482: `Warning: an existing sandbox was detected. /usr/bin/gimp will run without any additional sandboxing features` To me that suggests gimp was called from within another firejailed application (an image-viewer or the likes?). If so, that would explain what you're describing. As a general rule, applications started from within any other firejailed program inherit the parent's profile. And in this case that profile isn't built to access gimp. If what I'm describing here fits your use-case, try starting gimp independently and open whatever image file(s) you need from within gimp.

gitea-mirror commented

2026-05-05 08:19:34 -06:00

Author

Owner

@rusty-snake commented on GitHub (May 11, 2019):

@Neo00001 duplicate of #2681?

@rusty-snake commented on GitHub (May 11, 2019): @Neo00001 duplicate of #2681?

gitea-mirror commented

2026-05-05 08:19:34 -06:00

Author

Owner

@CodeArtisan00 commented on GitHub (May 12, 2019):

@rusty-snake I've re-installed manjaro & after that everything is working smoothly again.I'm not sure what actually did go wrong.
btw,I haven't changed anything in gimp.profile. I was having problem in kdenlive also but after re-installation of manjaro that's also working properly.

@CodeArtisan00 commented on GitHub (May 12, 2019): @rusty-snake I've re-installed manjaro & after that everything is working smoothly again.I'm not sure what actually did go wrong. btw,I haven't changed anything in gimp.profile. I was having problem in kdenlive also but after re-installation of manjaro that's also working properly.

gitea-mirror commented

2026-05-05 08:19:34 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 22, 2019):

Great! Glad to hear it resolved itself on your end :)

@chiraag-nataraj commented on GitHub (May 22, 2019): Great! Glad to hear it resolved itself on your end :)

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#1675

No description provided.

Rows
Columns