Package: libcairo2
Version: 1.0.4-2
Severity: normal

I have had a crash with Eclipse 3.1.2 (Sun JDK 1.4.2_11):

SIGSEGV (0xb) at pc=0x9e0ca73a, pid=18346, tid=3084458208

# Problematic frame:
# C  [libcairo.so.2+0x1573a]

The crash occurs as soon as Eclipse tries to open the GUI designer
(form window) in Visual Editor (VE) plugin.

More info:

Stack: [0xbfd1f000,0xbff11000),  sp=0xbff0ccd4,  free space=1975k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code,
C=native code)
C  [libcairo.so.2+0x1573a]
C  [libcairo.so.2+0x9f85]
C  [libcairo.so.2+0xd047]
C  [libcairo.so.2+0x6803]  cairo_create+0x53
C  [libswt-cairo-gtk-3139.so+0x56c6]
Java_org_eclipse_swt_internal_cairo_Cairo_cairo_1create+0x18
j  org.eclipse.swt.internal.cairo.Cairo.cairo_create()I+0
j  org.eclipse.swt.graphics.GC.initCairo()V+27
...

After removing libcairo1, VE does work.

Please add a Conflicts: libcairo1 so that the old lib is removed
during installation. This is better than doing it in Eclipse
package, because it might affect other applications using libcairo
as well.

Andre Heynatz

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.9
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libcairo2 depends on:
ii  libc6                       2.3.6-7      GNU C Library: Shared
libraries
ii  libfontconfig1              2.3.2-5.1    generic font
configuration library
ii  libfreetype6                2.1.10-3     FreeType 2 font engine,
shared lib
ii  libpng12-0                  1.2.8rel-5.1 PNG library - runtime
ii  libx11-6                    2:1.0.0-6    X11 client-side library
ii  libxrender1                 1:0.9.0.2-4  X Rendering Extension
client libra
ii  zlib1g                      1:1.2.3-11   compression library -
runtime

libcairo2 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to