> Does "ls /usr/local/lib/libg*" show anything?
Yes, the following output:
/usr/local/lib/libgimp-2.0.la /usr/local/lib/libgimpconfig-2.0.la
/usr/local/lib/libgimpthumb-2.0.la
/usr/local/lib/libgimp-2.0.so /usr/local/lib/libgimpconfig-2.0.so
/usr/l
Does "ls /usr/local/lib/libg*" show anything?
On Fri, 2007-09-07 at 10:38 +0200, Ronny Standtke wrote:
> > Did gimp used to work before?
>
> Yes, without any problem.
>
> > What happens if you move your ~/.gimp-2.2 directory out of the way?
>
> The problem remains.
--
To UNSUBSCRIBE, email
Did gimp used to work before? What happens if you move your ~/.gimp-2.2
directory out of the way?
On Wed, 2007-09-05 at 12:15 +0200, Ronny Standtke wrote:
> Package: gimp
> Version: 2.2.17-1
> Severity: grave
>
> --- Please enter the report below this line. ---
>
> Starting up gimp results in a
Package: gimp
Version: 2.2.17-1
Severity: grave
--- Please enter the report below this line. ---
Starting up gimp results in a segmentation fault. Here comes the console
output of a gdb run:
$ gdb gimp
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software,
4 matches
Mail list logo
