| Author |
Message |
GdV87
|
|
Post subject: gimp segmentation fault
 Posted: 05.07.2012, 22:03
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
After the last D-U, gimp (version 2.8.0-2, with libgegl-0.2-0-2) no longer works and instead gives the following message: "segmentation error".
Using "--verbose" does not give different output.
Can you help me?
GdV87 |
Last edited by GdV87 on 06.07.2012, 20:51; edited 2 times in total
|
| |
|
|
|
 |
|
drb
|
|
|
Post subject:
Posted: 06.07.2012, 05:51
|
|
Joined: 2010-09-11
Posts: 96
Status: Offline
|
|
gimp runs OK here
Code:
apt-cache policy libgegl-0.2-0
libgegl-0.2-0:
Installed: 0.2.0-2
Candidate: 0.2.0-2
Version table:
*** 0.2.0-2 0
500 http://ftp.uk.debian.org/debian/ sid/main i386 Packages
500 http://ftp.uk.debian.org/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
apt-cache policy gimp
gimp:
Installed: 2.8.0-2+b1
Candidate: 2.8.0-2+b1
Version table:
*** 2.8.0-2+b1 0
500 http://ftp.uk.debian.org/debian/ sid/main i386 Packages
500 http://ftp.uk.debian.org/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
|
|
|
| |
|
|
|
|
|
GdV87
|
|
|
Post subject:
Posted: 06.07.2012, 20:21
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
"apt-cache policy" gives me the same results (reported below).
How can I obtain debug information for this problem? Are there any logs I can read?
Thanks
GdV87
Code:
apt-cache policy libgegl-0.2-0
libgegl-0.2-0:
Installato: 0.2.0-2
Candidato: 0.2.0-2
Tabella versione:
*** 0.2.0-2 0
500 http://ftp.it.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
apt-cache policy gimp
gimp:
Installato: 2.8.0-2+b1
Candidato: 2.8.0-2+b1
Tabella versione:
*** 2.8.0-2+b1 0
500 http://ftp.it.debian.org/debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
|
|
|
| |
|
|
|
|
|
DonKult
|
|
|
Post subject:
Posted: 06.07.2012, 20:30
|
|
Team Member
Joined: 2010-09-02
Posts: 485
Status: Offline
|
|
The first thing i see is that you have amd64 while drb has i386. Not to worrisome though as I have amd64, and it works here, too. Is your system up-to-date? Try another dist-upgrade just to be sure.
You can install 'gdb' (gnu debugger) and 'gimp-dbg' (debug symbols for gimp). Then run 'gdb gimp' and in a terminal and in the following prompt enter 'run'. It will segfault again (at least it does so far for you): Enter 'bt' (it is short for backtrace) and you have a few more details what went wrong and where. |
_________________
MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
|
|
GdV87
|
|
|
Post subject:
Posted: 06.07.2012, 20:46
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
Thanks drb and DonKult for your quick replies, doing another D-U somehow did the trick and now gimp is working again.
GdV87 |
|
|
| |
|
|
|
|
|
GdV87
|
|
|
Post subject:
Posted: 06.07.2012, 20:54
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
That's very strange: Gimp worked only the first time I opened it after the D-U! Now it is giving the same error (even after reboot). I'll try with 'gimp-dbg'.
GdV87 |
Last edited by GdV87 on 06.07.2012, 21:06; edited 1 time in total
|
| |
|
|
|
|
|
GdV87
|
|
|
Post subject:
Posted: 06.07.2012, 21:00
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
This is the output of gdb:
Code:
~$ gdb gimp
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http>...
Reading symbols from /usr/bin/gimp...Reading symbols from /usr/lib/debug/usr/bin/gimp-2.8...done.
done.
(gdb) run
Starting program: /usr/bin/gimp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeae0a700 (LWP 12683)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeae0a700 (LWP 12683)]
0x00007fffeb9489a5 in ?? () from /usr/lib/libblas.so.3gf
(gdb) bt
#0 0x00007fffeb9489a5 in ?? () from /usr/lib/libblas.so.3gf
#1 0x00007ffff3ca4b50 in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007ffff39ef6dd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x0000000000000000 in ?? ()
(gdb)
I've no idea of what it means: can someone help me?
GdV87 |
|
|
| |
|
|
|
|
|
DonKult
|
|
|
Post subject:
Posted: 07.07.2012, 08:32
|
|
Team Member
Joined: 2010-09-02
Posts: 485
Status: Offline
|
|
| Interesting, i don't even have 'libblas3gf' installed (which includes /usr/lib/libblas.so.3gf). Looks like it's brought into by 'gimp-plugin-registry'. Just for testing, try removing it, maybe one of the plugins it includes is incompatible with newer gimp versions. |
_________________
MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
|
|
GdV87
|
|
|
Post subject:
Posted: 07.07.2012, 09:29
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
Thanks DonKult: I've removed libblas3gf and now gimp is finally working again.
However, when I open it, it gives me this error:
"GEGL-geglmodule.c-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.2/matting-levin.so' load error: libblas.so.3gf"
but after that the program runs regularly. Should I mark this thread as "solved"?
GdV87 |
|
|
| |
|
|
|
|
|
DonKult
|
|
|
Post subject:
Posted: 07.07.2012, 10:07
|
|
Team Member
Joined: 2010-09-02
Posts: 485
Status: Offline
|
|
Mhh, yeah "fixed" by removing is usually just a workaround. You can't use the functionality provided by this package, so this isn't really solved (it is just that you don't seem to need this functionality).
It would be good if you could report this bug in debian against 'libblas3gf'. The 'reportbug' program can help you with that. Ensure that you tell them that gimp is segfaulting if 'libblas3gf' is installed and if not that 'libgegl-0.2-0' complains about it being missing if you execute gimp (but runs fine none-the-less) with the error message above. They might have additional questions, so it's always a good idea to talk to them directly.
As these blas packages seem to be in the middle of change add the output of 'dpkg -l libblas*' to the report. Might be that you have both blas-libraries installed and they don't co-exist as nicely as they should.
But that are all only guesses. The maintainers will know for sure and can actually fix that -- which ultimately means that you will make the world a better place with a report to them.  |
_________________
MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
|
|
GdV87
|
|
|
Post subject:
Posted: 08.07.2012, 17:44
|
|
Joined: 2010-10-11
Posts: 63
Location: Italy
Status: Offline
|
|
|
|
|
|
|
DonKult
|
|
|
Post subject:
Posted: 08.07.2012, 18:44
|
|
Team Member
Joined: 2010-09-02
Posts: 485
Status: Offline
|
|
|
|
|
|
|
|
