Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2019-01-19 Thread 積丹尼 Dan Jacobson 
Thanks but one still must forbid
# aptitude search ~U
iFA libilmbase23
iFA libopenexr23
if gimp is to start on experimental.

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2019-01-19 Thread Adrian Bunk 
Control: reassign -1 src:openexr 2.3.0-1
Control: affects -1 libopenexr23 gimp
Control: close -1 2.3.0-4

On Sun, Jan 06, 2019 at 12:55:13AM +0800, 積丹尼 Dan Jacobson wrote:
> retitle 917130 libIlmImf-2_2.so.23: cannot open shared object file
> thanks
> 
> On my other machine gimp starts, but is in an ugly grey color.
> Let's clean up these warnings first,
> 
> # su - nobody -c "DISPLAY=$DISPLAY HOME=/tmp/ gimp"&
> GEGL-Message: 00:12:37.527: Module 
> '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
> libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
> GEGL-Message: 00:12:37.926: Module 
> '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
> libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
> And many
> (gimp:1448): Gtk-WARNING **: 00:12:40.336: Unable to locate theme engine in 
> module_path: "pixmap",
> And
> /usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
> libraries: libIlmImf-2_2.so.23: cannot open shared object file: No such file 
> or directory
> gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
> 
> $ dlocate libIlmImf
> libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24.0.0
> libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImfUtil-2_3.so.24.0.0
> libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24
> libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImfUtil-2_3.so.24
> $ aptitude search libopenexr
> p   libopenexr-dev - development 
> files for the OpenEXR image library
> i A libopenexr23   - runtime files 
> for the OpenEXR image library
> p   libopenexr24   - runtime files 
> for the OpenEXR image library
> $ apt-cache policy libopenexr23
> libopenexr23:
>   Installed: 2.3.0-3
>   Candidate: 2.3.0-3
>   Version table:
>  *** 2.3.0-3 990
> 990 http://opensource.nchc.org.tw/debian experimental/main amd64 
> Packages
> 100 /var/lib/dpkg/status
>  2.2.1-4 500
> 500 http://opensource.nchc.org.tw/debian unstable/main amd64 Packages
> # aptitude install libopenexr23=2.2.1-4
> The following packages will be DOWNGRADED:
>   libopenexr23  
> # su - nobody -c "DISPLAY=$DISPLAY HOME=/tmp/ gimp"&
> GEGL-Message: 00:49:09.357: Module 
> '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
> libImath-2_2.so.23: cannot open shared object file: No such file or directory
> GEGL-Message: 00:49:09.387: Module 
> '/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
> libImath-2_2.so.23: cannot open shared object file: No such file or directory
> and
> /usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
> libraries: libIex-2_2.so.23: cannot open shared object file: No such file or 
> directory
> 
> Now the message becomes libImath and libIex.
>...

Thanks for the update, I'm moving this bug to the package where it was fixed.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2019-01-19 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:openexr 2.3.0-1
Bug #917130 [gimp] libIlmImf-2_2.so.23: cannot open shared object file
Bug reassigned from package 'gimp' to 'src:openexr'.
No longer marked as found in versions gimp/2.10.8-1.
Ignoring request to alter fixed versions of bug #917130 to the same values 
previously set
Bug #917130 [src:openexr] libIlmImf-2_2.so.23: cannot open shared object file
Marked as found in versions openexr/2.3.0-1.
> affects -1 libopenexr23 gimp
Bug #917130 [src:openexr] libIlmImf-2_2.so.23: cannot open shared object file
Added indication that 917130 affects libopenexr23 and gimp
> close -1 2.3.0-4
Bug #917130 [src:openexr] libIlmImf-2_2.so.23: cannot open shared object file
Marked as fixed in versions openexr/2.3.0-4.
Bug #917130 [src:openexr] libIlmImf-2_2.so.23: cannot open shared object file
Marked Bug as done

-- 
917130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2019-01-05 Thread 積丹尼 Dan Jacobson 
retitle 917130 libIlmImf-2_2.so.23: cannot open shared object file
thanks

On my other machine gimp starts, but is in an ugly grey color.
Let's clean up these warnings first,

# su - nobody -c "DISPLAY=$DISPLAY HOME=/tmp/ gimp"&
GEGL-Message: 00:12:37.527: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
GEGL-Message: 00:12:37.926: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
And many
(gimp:1448): Gtk-WARNING **: 00:12:40.336: Unable to locate theme engine in 
module_path: "pixmap",
And
/usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
libraries: libIlmImf-2_2.so.23: cannot open shared object file: No such file or 
directory
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error

$ dlocate libIlmImf
libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24.0.0
libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImfUtil-2_3.so.24.0.0
libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24
libopenexr23:amd64: /usr/lib/x86_64-linux-gnu/libIlmImfUtil-2_3.so.24
$ aptitude search libopenexr
p   libopenexr-dev - development files 
for the OpenEXR image library
i A libopenexr23   - runtime files for 
the OpenEXR image library
p   libopenexr24   - runtime files for 
the OpenEXR image library
$ apt-cache policy libopenexr23
libopenexr23:
  Installed: 2.3.0-3
  Candidate: 2.3.0-3
  Version table:
 *** 2.3.0-3 990
990 http://opensource.nchc.org.tw/debian experimental/main amd64 
Packages
100 /var/lib/dpkg/status
 2.2.1-4 500
500 http://opensource.nchc.org.tw/debian unstable/main amd64 Packages
# aptitude install libopenexr23=2.2.1-4
The following packages will be DOWNGRADED:
  libopenexr23  
# su - nobody -c "DISPLAY=$DISPLAY HOME=/tmp/ gimp"&
GEGL-Message: 00:49:09.357: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
libImath-2_2.so.23: cannot open shared object file: No such file or directory
GEGL-Message: 00:49:09.387: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
libImath-2_2.so.23: cannot open shared object file: No such file or directory
and
/usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
libraries: libIex-2_2.so.23: cannot open shared object file: No such file or 
directory

Now the message becomes libImath and libIex.

# set libgegl-0.4-0
# apt-cache policy $@
libgegl-0.4-0:
  Installed: 0.4.12-2
  Candidate: 0.4.12-2
  Version table:
 *** 0.4.12-2 500
500 http://opensource.nchc.org.tw/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status

Processed: Re: Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2019-01-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 917130 libIlmImf-2_2.so.23: cannot open shared object file
Bug #917130 [gimp] gimp: crashes at start: segmentation fault in 
g_slice_alloc() (memory corruption?)
Changed Bug title to 'libIlmImf-2_2.so.23: cannot open shared object file' from 
'gimp: crashes at start: segmentation fault in g_slice_alloc() (memory 
corruption?)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
917130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2018-12-29 Thread Simon McVittie 
On Sat, 29 Dec 2018 at 15:10:20 +0800, 積丹尼 Dan Jacobson wrote:
> The rest of the commands you gave me failed to start gimp.

Please send their output to the bug anyway. I'm not suggesting
workarounds, I'm suggesting ways you can give the gimp maintainers
information that they might need to be able to identify and fix this bug.

smcv

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2018-12-28 Thread 積丹尼 Dan Jacobson 
Indeed with G_SLICE=debug-blocks it starts, but still says
 
GEGL-Message: 15:02:47.435: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
GEGL-Message: 15:02:47.499: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
Failed to execute child process “dbus-launch” (No such file or directory)
(gimp:7862): Gtk-WARNING **: 15:02:47.681: Unable to locate theme engine in 
module_path: "pixmap",
/usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
libraries: libIlmImf-2_2.so.23: cannot open shared object file: No such file or 
directory
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
(gimp:7862): GLib-GObject-CRITICAL **: 15:02:55.648: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

G_SLICE=debug-blocks G_MESSAGES_DEBUG=all gave:

GEGL-Message: 15:07:29.514: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
GEGL-Message: 15:07:29.578: Module 
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-load.so' load error: 
libIlmImf-2_2.so.23: cannot open shared object file: No such file or directory
(gimp:8067): GLib-DEBUG: 15:07:29.580: posix_spawn avoided (fd close requested) 
Failed to execute child process “dbus-launch” (No such file or directory)
(gimp:8067): GLib-DEBUG: 15:07:29.652: posix_spawn avoided (fd close requested) 
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: gdk_pixbuf_from_pixdata() called on:
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Encoding raw
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Dimensions: 64 x 64
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Rowstride: 256, Length: 16408
(gimp:8067): GdkPixbuf-DEBUG: 15:07:29.658: Copy pixels == false
(gimp:8067): Gtk-WARNING **: 15:07:29.664: Unable to locate theme engine in 
module_path: "pixmap",
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: gdk_pixbuf_from_pixdata() called on:
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Encoding rle
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Dimensions: 22 x 22
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Rowstride: 88, Length: 1606
(gimp:8067): GdkPixbuf-DEBUG: 15:07:30.110: Copy pixels == true
/usr/lib/gimp/2.0/plug-ins/file-exr/file-exr: error while loading shared 
libraries: libIlmImf-2_2.so.23: cannot open shared object file: No such file or 
directory
gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
(file-rawtherapee:8080): GLib-DEBUG: 15:07:30.160: posix_spawn avoided (fd 
close requested) 
(file-darktable:8082): GLib-DEBUG: 15:07:30.172: posix_spawn avoided (fd close 
requested) 
(gimp:8067): GLib-GObject-CRITICAL **: 15:07:34.515: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

The rest of the commands you gave me failed to start gimp. I did add the
symbols packages yet.

Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2018-12-24 Thread Simon McVittie 
Control: retitle -1 gimp: crashes at start: segmentation fault in 
g_slice_alloc() (memory corruption?)
Control: tags -1 + moreinfo

On Sun, 23 Dec 2018 at 11:24:49 +0800, 積丹尼 Dan Jacobson wrote:
> Thread 1 (Thread 0x7f1aae82ce00 (LWP 3715)):
> #0  0x7f1ab0f8a484 in read () from /lib/x86_64-linux-gnu/libpthread.so.0
> No symbol table info available.
> #1  0x7f1ab1e81d34 in gimp_stack_trace_print () from 
> /usr/lib/libgimpbase-2.0.so.0
> No symbol table info available.
> #2  0x55bffd0fc4a0 in ?? ()
> No symbol table info available.
> #3  0x55bffd0fc8d8 in gimp_fatal_error ()
> No symbol table info available.
> #4  0x55bffd0fd037 in ?? ()
> No symbol table info available.
> #5  
> No symbol table info available.
> #6  0x7f1ab118d92a in g_slice_alloc () from 
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> No symbol table info available.
> #7  0x55bffd47ba9e in gimp_temp_buf_new ()
> No symbol table info available.

A crash in memory allocation infrastructure is usually evidence of earlier
memory corruption, so the root cause probably happened before this.
I can't reproduce this crash myself.

Please install debug symbols for GIMP and relevant libraries (at least
libglib2.0-0-dbgsym, libgimp2.0-dbgsym and gimp-dbgsym), which you can
get from the debian-debug apt repository:

This will produce a more informative backtrace.

If you create a new user account on the same system and run gimp as
that user, does it crash in the same way?

If you run with the environment variable G_SLICE set to "debug-blocks",
do you still get a crash? If you do, what is the output?

If you run with environment variables G_SLICE=always-malloc and
MALLOC_CHECK_=2, do you still get a crash? If you do, what is the output?

Setting G_DEBUG=fatal-criticals and/or G_MESSAGES_DEBUG=all might also
produce useful logging.

smcv

Processed: Re: Bug#917130: gimp: crashes at start: segmentation fault in g_slice_alloc() (memory corruption?)

2018-12-24 Thread Debian Bug Tracking System 
Processing control commands:

> retitle -1 gimp: crashes at start: segmentation fault in g_slice_alloc() 
> (memory corruption?)
Bug #917130 [gimp] crashs at start
Changed Bug title to 'gimp: crashes at start: segmentation fault in 
g_slice_alloc() (memory corruption?)' from 'crashs at start'.
> tags -1 + moreinfo
Bug #917130 [gimp] gimp: crashes at start: segmentation fault in 
g_slice_alloc() (memory corruption?)
Added tag(s) moreinfo.

-- 
917130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems