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

Gimp not working #2658

Closed
Neo00001 opened this issue Apr 21, 2019 · 9 comments
Closed

Gimp not working #2658

Neo00001 opened this issue Apr 21, 2019 · 9 comments

Comments

@Neo00001
Copy link
Collaborator

Neo00001 commented Apr 21, 2019

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

@FOSSONLY
Copy link

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.

@Neo00001
Copy link
Collaborator Author

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.

@curiosity-seeker
Copy link
Contributor

curiosity-seeker commented 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.

@Neo00001
Copy link
Collaborator Author

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

@Neo00001
Copy link
Collaborator Author

btw, firejail --noprofile is working for gimp.

@glitsj16
Copy link
Collaborator

@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.

@rusty-snake
Copy link
Collaborator

@Neo00001 duplicate of #2681?

@Neo00001
Copy link
Collaborator Author

Neo00001 commented 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.

@chiraag-nataraj
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants