Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13898 - [gimp] doesn't start

Attached to Project: Arch Linux
Opened by Shiki (shiki) - Saturday, 21 March 2009, 09:32 GMT
Last edited by Tobias Kieslich (tobias) - Sunday, 31 May 2009, 19:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Eric Belanger (Snowman)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I just cant start up my Gimp. It was working until I did an upgrade to 2.6.5 , and then to 2.6.6. I tried removing the gimp config folder and so on.. but nothing helped. Any idea?.

Additional info:
* package version(s):
2.6.5-1
2.6.6-1

Steps to reproduce:
Start gimp?.. This is all what happens.. :
[shiki@ayanami ~]$ gimp
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
[shiki@ayanami ~]$

Versions:
http://pastebin.com/m18147f18
This task depends upon

Closed by  Tobias Kieslich (tobias)
Sunday, 31 May 2009, 19:26 GMT
Reason for closing:  Works for me
Additional comments about closing:  Closed on reporters request
Comment by Isenmann Daniel (ise) - Saturday, 21 March 2009, 12:05 GMT
Can't reproduce it, everything is fine here.
Comment by Matthew Gyurgyik (pyther) - Saturday, 21 March 2009, 13:55 GMT
Can you run gdb and paste a traceback? (paste it to something like http://rafb.net/paste)
Comment by Mauro Santos (R00KIE) - Saturday, 21 March 2009, 15:33 GMT
Also starts fine here (even after deleting ~/.gimp-2.6), and I haven't noticed any problems with any update so far.
Comment by filippo colombo (ombra85) - Saturday, 21 March 2009, 20:41 GMT
Here gimp 2.6.6 starts well.
Comment by Jørn Gabrielsen (dr_relling) - Wednesday, 01 April 2009, 21:52 GMT
I have the same problem. I do not have support for xv in X due to this is not currently supported by the radeon driver for my card.
Can the problem be the gimp as of 2.6.6 is compilesd with some option requiring Xv support in X in order to run? (Wild guess)
Comment by Jørn Gabrielsen (dr_relling) - Wednesday, 01 April 2009, 22:42 GMT
As I wrote in an e-mail to you: It worked again after restarting X, but still giving the "Xlib: extension "Generic Event Extension" missing on display ":0.0"." messages, so please ignore my last post.
Comment by Michael (SiD) - Sunday, 05 April 2009, 15:40 GMT
Can't confirm it. gimp-2.6.6-1 works fine here. (i686)
Comment by Shiki (shiki) - Tuesday, 14 April 2009, 20:03 GMT
Just found a solution:
gimp -n
(-n as in 'new instance'). Don't ask me why I have to use this method ... I cant 'killall gimp'.. so beats me. Any idea?
Comment by Alessandro Doro (adoroo) - Wednesday, 15 April 2009, 00:24 GMT
Can you "killall -9 gimp"?

What is the output of
$ ps ax|grep gimp
and
$ type -a gimp
Comment by farid (osc) - Thursday, 30 April 2009, 04:02 GMT
cant confirm neither. it works fine.
Comment by Shiki (shiki) - Sunday, 03 May 2009, 17:39 GMT
Okay it happens again.

I can't kill it.
[shiki@tenshi ~]$ gimp
[shiki@tenshi ~]$ killall gimp
gimp: no process killed
[shiki@tenshi ~]$ killall -9 gimp
gimp: no process killed

[shiki@tenshi ~]$ ps ax|grep gimp
22688 ? Sl 0:11 gimp-2.6 file:///home/shiki/pic%20003.jpg
29079 pts/0 S+ 0:00 grep gimp

[shiki@tenshi ~]$ type -a gimp
gimp is /usr/bin/gimp

The system is up-to-date. x86-64 Arch.

Comment by Shiki (shiki) - Sunday, 03 May 2009, 17:41 GMT
After killing the process ID which I get with "$ ps ax|grep gimp" (what Adoroo suggested (Thank you very much)), I can run gimp again. Running it from terminal gives only this:

[shiki@tenshi ~]$ gimp
/usr/lib/gimp/2.0/plug-ins/file-pdf: error while loading shared libraries: libpoppler-glib.so.4: cannot open shared object file: No such file or directory

(gimp:29136): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/help-browser: error while loading shared libraries: libwebkit-1.0.so.1: cannot open shared object file: No such file or directory

(gimp:29136): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error

Thats all. But its still NOT A SOLUTION TO KILL THE ID. For an R=1 user, I cant tell to do these steps..
Comment by Shiki (shiki) - Sunday, 03 May 2009, 17:48 GMT
By the way, Im using Nvidia AND Intel based vga cards. So it is NOT an issue with Xorg. It happens on both machines. Different WMs, different settings, same OS, same gimp.

Anyway, it not happening ALWAYS. Like I can open few pictures, edit it, create images. THen I close it, leave the PC at it is. Then come back, and I cant start it.. I havent got any clue. (Sorry for posting so many comments, I cant edit my posts.)
Comment by Tobias Kieslich (tobias) - Sunday, 31 May 2009, 19:11 GMT
same maybe buggy gtk-engine on the different systems?
Comment by Shiki (shiki) - Sunday, 31 May 2009, 19:19 GMT
I'm using MIST and the other uses Murrine.

By the way soon (NOT NOW .. I dont want to reopen it if it happens again) you can close this report. It didn't happen for a while now..

Loading...