Debian Bug report logs - #515946
libxi6 2:1.2.0-2 makes iceweasel (when selecting text) and midori crash

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: iceweasel crashes in safe mode when I select some text in an xterm

Date: Wed, 18 Feb 2009 13:40:09 +0100

Package: iceweasel
Version: 3.0.6-1
Severity: grave
Justification: renders package unusable

Iceweasel crashes when I select some text in an xterm. This
is always reproducible, even in safe mode, making the package
unusable in practice.

Core was generated by `/usr/lib/iceweasel/firefox-bin -a iceweasel -safe-mode'.
Program terminated with signal 11, Segmentation fault.
[New process 19251]
[New process 19267]
[New process 19266]
[New process 19265]
[New process 19264]
[New process 19260]
[New process 19255]
[New process 19254]
#0  0x00007f88db2d4ed5 in raise () from /lib64/libc.so.6
#0  0x00007f88db2d4ed5 in raise () from /lib64/libc.so.6
#1  0x00007f88d9f75f15 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#2  <signal handler called>
#3  _gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffe3d1fed0)
    at /tmp/buildd/gtk+2.0-2.12.12/gdk/x11/gdkscreen-x11.c:779
#4  0x00007f88d57466bc in gdk_event_translate (display=0x1d60000, 
    event=0x2e97480, xevent=0x7fffe3d1fed0, return_exposes=0)
    at /tmp/buildd/gtk+2.0-2.12.12/gdk/x11/gdkevents-x11.c:2089
#5  0x00007f88d5746be7 in _gdk_events_queue (display=0x1d60000)
    at /tmp/buildd/gtk+2.0-2.12.12/gdk/x11/gdkevents-x11.c:2285
#6  0x00007f88d5746fbe in gdk_event_dispatch (source=<value optimized out>, 
    callback=0x7fffe3d1fed0, user_data=0x1d60000)
    at /tmp/buildd/gtk+2.0-2.12.12/gdk/x11/gdkevents-x11.c:2345
#7  0x00007f88d6f38afb in IA__g_main_context_dispatch (context=0x1d6d1d0)
    at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2144
#8  0x00007f88d6f3c2bd in g_main_context_iterate (context=0x1d6d1d0, block=1, 
    dispatch=1, self=<value optimized out>)
    at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2778
#9  0x00007f88d6f3c47b in IA__g_main_context_iteration (context=0x1d6d1d0, 
    may_block=1) at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2841
#10 0x00007f88da600c25 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#11 0x00007f88da600d73 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#12 0x00007f88da6a6699 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#13 0x00007f88da67c712 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#14 0x00007f88da600e91 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#15 0x00007f88da4e43c1 in ?? () from /usr/lib/iceweasel/xulrunner/libxul.so
#16 0x00007f88d9f6fa08 in XRE_main ()
   from /usr/lib/iceweasel/xulrunner/libxul.so
#17 0x00000000004014cb in ?? ()
#18 0x00007f88db2c11a6 in __libc_start_main () from /lib64/libc.so.6
#19 0x0000000000401139 in ?? ()
#20 0x00007fffe3d217c8 in ?? ()
#21 0x000000000000001c in ?? ()
#22 0x0000000000000004 in ?? ()
#23 0x00007fffe3d21f67 in ?? ()
#24 0x0000000000000000 in ?? ()

Note: I don't know if the bug is in iceweasel itself (I could find
nothing in the xulrunner-1.9 bug reports). But perhaps someone else
knows...

-- System Information:
Debian Release: 5.0
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26.5-20080922 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages iceweasel depends on:
ii  debianutils                   2.31       Miscellaneous utilities specific t
ii  fontconfig                    2.6.0-3    generic font configuration library
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  libglib2.0-0                  2.18.4-2   The GLib library of C routines
ii  libgtk2.0-0                   2.12.12-1  The GTK+ graphical user interface 
ii  libnspr4-0d                   4.7.1-4    NetScape Portable Runtime Library
ii  libstdc++6                    4.3.3-3    The GNU Standard C++ Library v3
ii  procps                        1:3.2.7-11 /proc file system utilities
ii  psmisc                        22.6-1     Utilities that use the proc filesy
ii  xulrunner-1.9                 1.9.0.6-1  XUL + XPCOM application runner

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  latex-xft-fonts       <none>             (no description available)
ii  libkrb53              1.6.dfsg.4~beta1-6 MIT Kerberos runtime libraries
pn  mozplugger            <none>             (no description available)
pn  ttf-mathematica4.1    <none>             (no description available)
pn  xfonts-mathml         <none>             (no description available)
pn  xprint                <none>             (no description available)
pn  xulrunner-1.9-gnome-s <none>             (no description available)

-- no debconf information

Message #10 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: 515946@bugs.debian.org

Subject: iceweasel crashes in safe mode when I select some text

Date: Wed, 18 Feb 2009 13:52:48 +0100

retitle 515946 iceweasel crashes in safe mode when I select some text
thanks

On 2009-02-18 13:40:09 +0100, Vincent Lefevre wrote:
> Package: iceweasel
> Version: 3.0.6-1
> Severity: grave
> Justification: renders package unusable
> 
> Iceweasel crashes when I select some text in an xterm. This
> is always reproducible, even in safe mode, making the package
> unusable in practice.

In fact, not just in xterm, but also in iceweasel itself, for instance.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #17 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: 515946@bugs.debian.org

Subject: Re: iceweasel crashes in safe mode when I select some text

Date: Wed, 18 Feb 2009 14:24:44 +0100

The bug is probably in a library since midori 0.1.2-1 also crashes
for the same reason. But emacs22-gtk 22.2+2-5 doesn't crash.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #22 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <mh@glandium.org>

To: Vincent Lefevre <vincent@vinc17.org>, 515946@bugs.debian.org

Subject: Re: Bug#515946: iceweasel crashes in safe mode when I select some text

Date: Wed, 18 Feb 2009 14:34:38 +0100

On Wed, Feb 18, 2009 at 02:24:44PM +0100, Vincent Lefevre <vincent@vinc17.org> wrote:
> The bug is probably in a library since midori 0.1.2-1 also crashes
> for the same reason. But emacs22-gtk 22.2+2-5 doesn't crash.

Try downgrading glib and gtk.

Mike

Message #27 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Mike Hommey <mh@glandium.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: iceweasel crashes in safe mode when I select some text

Date: Wed, 18 Feb 2009 15:19:37 +0100

On 2009-02-18 14:34:38 +0100, Mike Hommey wrote:
> On Wed, Feb 18, 2009 at 02:24:44PM +0100, Vincent Lefevre <vincent@vinc17.org> wrote:
> > The bug is probably in a library since midori 0.1.2-1 also crashes
> > for the same reason. But emacs22-gtk 22.2+2-5 doesn't crash.
> 
> Try downgrading glib and gtk.

I've downgraded some packages to stable (and "apt-get install -f"
doesn't complain). But I still have a segfault in both iceweasel
and midori.

Versions of packages iceweasel depends on:
ii  debianutils                   2.31       Miscellaneous utilities specific t
ii  fontconfig                    2.6.0-3    generic font configuration library
ii  libc6                         2.9-1      GNU C Library: Shared libraries
ii  libglib2.0-0                  2.16.6-1   The GLib library of C routines
ii  libgtk2.0-0                   2.12.11-4  The GTK+ graphical user interface 
ii  libnspr4-0d                   4.7.1-4    NetScape Portable Runtime Library
ii  libstdc++6                    4.3.3-4    The GNU Standard C++ Library v3
ii  procps                        1:3.2.7-11 /proc file system utilities
ii  psmisc                        22.6-1     Utilities that use the proc filesy
ii  xulrunner-1.9                 1.9.0.6-1  XUL + XPCOM application runner

Versions of packages midori depends on:
ii  dbus-x11                   1.2.12-1      simple interprocess messaging syst
ii  libatk1.0-0                1.22.0-1      The ATK accessibility toolkit
ii  libc6                      2.9-1         GNU C Library: Shared libraries
ii  libcairo2                  1.8.6-2       The Cairo 2D vector graphics libra
ii  libglib2.0-0               2.16.6-1      The GLib library of C routines
ii  libgtk2.0-0                2.12.11-4     The GTK+ graphical user interface 
ii  libpango1.0-0              1.20.5-3      Layout and rendering of internatio
ii  libsqlite3-0               3.5.9-6       SQLite 3 shared library
ii  libunique-1.0-0            1.0.4-1       Library for writing single instanc
ii  libwebkit-1.0-1            1.0.1-4       Web content engine library for Gtk
ii  libxml2                    2.6.32.dfsg-5 GNOME XML library

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #32 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Mike Hommey <mh@glandium.org>

Cc: 515946@bugs.debian.org

Subject: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Wed, 18 Feb 2009 16:18:29 +0100

reassign 515946 libxi6
found 515946 libxi6/2:1.2.0-2
thanks

On 2009-02-18 15:19:37 +0100, Vincent Lefevre wrote:
> I've downgraded some packages to stable (and "apt-get install -f"
> doesn't complain). But I still have a segfault in both iceweasel
> and midori.

The bug comes from libxi6 2:1.2.0-2 (downgrading to 2:1.1.4-1
solves the problem).

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #41 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: 515946@bugs.debian.org

Subject: Re: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Wed, 18 Feb 2009 16:34:54 +0100

retitle 515946 libxi6 2:1.2.0-2 makes iceweasel (when selecting text) and midori crash
thanks

On 2009-02-18 16:18:29 +0100, Vincent Lefevre wrote:
> The bug comes from libxi6 2:1.2.0-2 (downgrading to 2:1.1.4-1
> solves the problem).

To summarize, when libxi6 2:1.2.0-2 is installed:
  * midori immediately crashes when it is started;
  * iceweasel crashes as soon as some text is selected (not just
    in iceweasel, but also in xterm, for instance).

But emacs22-gtk and liferea don't seem to crash.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #52 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Brice Goglin <Brice.Goglin@ens-lyon.org>

To: Vincent Lefevre <vincent@vinc17.org>, 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Fri, 20 Feb 2009 07:12:46 +0100

Vincent Lefevre wrote:
> retitle 515946 libxi6 2:1.2.0-2 makes iceweasel (when selecting text) and midori crash
> thanks
>
> On 2009-02-18 16:18:29 +0100, Vincent Lefevre wrote:
>   
>> The bug comes from libxi6 2:1.2.0-2 (downgrading to 2:1.1.4-1
>> solves the problem).
>>     
>
> To summarize, when libxi6 2:1.2.0-2 is installed:
>   * midori immediately crashes when it is started;
>   * iceweasel crashes as soon as some text is selected (not just
>     in iceweasel, but also in xterm, for instance).
>
> But emacs22-gtk and liferea don't seem to crash.
>   


Can you try with xserver-xorg-core 2:1.4.2-11? It looks like we had
issues (eg #515734, #515905 and #515976) because libxi6 was built
against newer input proto headers. The new xserver-xorg-core has been
rebuilt with the same headers now and it seems to help.

Brice

Message #57 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Brice Goglin <Brice.Goglin@ens-lyon.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Fri, 20 Feb 2009 14:35:07 +0100

On 2009-02-20 07:12:46 +0100, Brice Goglin wrote:
> Can you try with xserver-xorg-core 2:1.4.2-11?

This is not possible because I've put xserver-xorg-input-kbd on hold,
waiting for bug 432011 to be fixed (or any workaround). I'm sticked
to xserver-xorg-core 2:1.1.1-21etch5.

> It looks like we had issues (eg #515734, #515905 and #515976)
> because libxi6 was built against newer input proto headers. The new
> xserver-xorg-core has been rebuilt with the same headers now and it
> seems to help.

If the new libxi6 depends on a new xserver-xorg-core, a dependency
should be added.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #62 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Vincent Lefevre <vincent@vinc17.org>, 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Mon, 25 May 2009 15:58:31 +0200

tag 515946 unreproducible moreinfo
kthxbye

On Fri, Feb 20, 2009 at 14:35:07 +0100, Vincent Lefevre wrote:

> If the new libxi6 depends on a new xserver-xorg-core, a dependency
> should be added.
> 
It doesn't, and such a dependency wouldn't make any sense.  So, if
you can still reproduce this bug, you'll have to provide more
information.  There wasn't any change in libXi that would explain this
crash as far as I can tell..

Cheers,
Julien

Message #69 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Julien Cristau <jcristau@debian.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Mon, 25 May 2009 16:52:50 +0200

found 515946 libxi/2:1.2.1-2
thanks

On 2009-05-25 15:58:31 +0200, Julien Cristau wrote:
> So, if you can still reproduce this bug, you'll have to provide more
> information. There wasn't any change in libXi that would explain
> this crash as far as I can tell..

This bug still occurs with the latest libxi6 version.
Here's the dpkg log corresponding to the upgrade that
makes the crash occur.

2009-05-25 16:33:07 startup archives unpack
2009-05-25 16:33:08 upgrade libxi-dev 2:1.1.4-1 2:1.2.1-2
2009-05-25 16:33:08 status half-configured libxi-dev 2:1.1.4-1
2009-05-25 16:33:08 status unpacked libxi-dev 2:1.1.4-1
2009-05-25 16:33:08 status half-installed libxi-dev 2:1.1.4-1
2009-05-25 16:33:08 status triggers-pending man-db 2.5.5-1
2009-05-25 16:33:08 status half-installed libxi-dev 2:1.1.4-1
2009-05-25 16:33:08 status half-installed libxi-dev 2:1.1.4-1
2009-05-25 16:33:08 status unpacked libxi-dev 2:1.2.1-2
2009-05-25 16:33:09 status unpacked libxi-dev 2:1.2.1-2
2009-05-25 16:33:09 upgrade libxi6 2:1.1.4-1 2:1.2.1-2
2009-05-25 16:33:09 status half-configured libxi6 2:1.1.4-1
2009-05-25 16:33:09 status unpacked libxi6 2:1.1.4-1
2009-05-25 16:33:09 status half-installed libxi6 2:1.1.4-1
2009-05-25 16:33:09 status half-installed libxi6 2:1.1.4-1
2009-05-25 16:33:09 status unpacked libxi6 2:1.2.1-2
2009-05-25 16:33:09 status unpacked libxi6 2:1.2.1-2
2009-05-25 16:33:09 trigproc man-db 2.5.5-1 2.5.5-1
2009-05-25 16:33:09 status half-configured man-db 2.5.5-1
2009-05-25 16:33:10 status installed man-db 2.5.5-1
2009-05-25 16:33:11 startup packages configure
2009-05-25 16:33:11 configure libxi6 2:1.2.1-2 2:1.2.1-2
2009-05-25 16:33:11 status unpacked libxi6 2:1.2.1-2
2009-05-25 16:33:11 status half-configured libxi6 2:1.2.1-2
2009-05-25 16:33:11 status installed libxi6 2:1.2.1-2
2009-05-25 16:33:11 configure libxi-dev 2:1.2.1-2 2:1.2.1-2
2009-05-25 16:33:11 status unpacked libxi-dev 2:1.2.1-2
2009-05-25 16:33:11 status half-configured libxi-dev 2:1.2.1-2
2009-05-25 16:33:11 status installed libxi-dev 2:1.2.1-2

After installing libxi6 2:1.2.1-2, I logged out and logged in again,
started X, ran Iceweasel, and selected some text; the crash occurred
immediately.

What information do you need? Would a test under valgrind be useful?

In case this matters, my window manager is fvwm.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #76 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Vincent Lefevre <vincent@vinc17.org>, 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Wed, 27 May 2009 12:16:23 +0200

On Mon, May 25, 2009 at 16:52:50 +0200, Vincent Lefevre wrote:

> What information do you need? Would a test under valgrind be useful?
> 
I guess that's worth a try.

Cheers,
Julien

Message #81 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Julien Cristau <jcristau@debian.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Wed, 27 May 2009 17:58:08 +0200

On 2009-05-27 12:16:23 +0200, Julien Cristau wrote:
> On Mon, May 25, 2009 at 16:52:50 +0200, Vincent Lefevre wrote:
> > What information do you need? Would a test under valgrind be useful?
> > 
> I guess that's worth a try.

Here's an example with midori 0.1.4-1 (as it is light that iceweasel).
The crash is immediate (I don't have to do anything).

$ valgrind midori
==10974== Memcheck, a memory error detector.
==10974== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
==10974== Using LibVEX rev 1884, a library for dynamic binary translation.
==10974== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP.
==10974== Using valgrind-3.4.1-Debian, a dynamic binary instrumentation framework.
==10974== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al.
==10974== For more details, rerun with: -v
==10974== 
==10974== Invalid read of size 8
==10974==    at 0x58BD854: _gdk_x11_screen_process_owner_change (gdkscreen-x11.c:1124)
==10974==    by 0x58B13E3: gdk_event_translate (gdkevents-x11.c:2093)
==10974==    by 0x58B18B6: _gdk_events_queue (gdkevents-x11.c:2298)
==10974==    by 0x58B1C8D: gdk_event_dispatch (gdkevents-x11.c:2358)
==10974==    by 0x7895F79: g_main_context_dispatch (gmain.c:1814)
==10974==    by 0x789963F: g_main_context_iterate (gmain.c:2448)
==10974==    by 0x7899B0C: g_main_loop_run (gmain.c:2656)
==10974==    by 0x5323B33: gtk_dialog_run (gtkdialog.c:1090)
==10974==    by 0x41D652: main (in /usr/bin/midori)
==10974==  Address 0x338 is not stack'd, malloc'd or (recently) free'd
==10974== 
==10974== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==10974==  Access not within mapped region at address 0x338
==10974==    at 0x58BD854: _gdk_x11_screen_process_owner_change (gdkscreen-x11.c:1124)
==10974==    by 0x58B13E3: gdk_event_translate (gdkevents-x11.c:2093)
==10974==    by 0x58B18B6: _gdk_events_queue (gdkevents-x11.c:2298)
==10974==    by 0x58B1C8D: gdk_event_dispatch (gdkevents-x11.c:2358)
==10974==    by 0x7895F79: g_main_context_dispatch (gmain.c:1814)
==10974==    by 0x789963F: g_main_context_iterate (gmain.c:2448)
==10974==    by 0x7899B0C: g_main_loop_run (gmain.c:2656)
==10974==    by 0x5323B33: gtk_dialog_run (gtkdialog.c:1090)
==10974==    by 0x41D652: main (in /usr/bin/midori)
==10974==  If you believe this happened as a result of a stack overflow in your
==10974==  program's main thread (unlikely but possible), you can try to increase
==10974==  the size of the main thread stack using the --main-stacksize= flag.
==10974==  The main thread stack size used in this run was 8388608.
==10974== 
==10974== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 13 from 2)
==10974== malloc/free: in use at exit: 1,195,307 bytes in 12,078 blocks.
==10974== malloc/free: 38,284 allocs, 26,206 frees, 3,911,189 bytes allocated.
==10974== For counts of detected errors, rerun with: -v
==10974== searching for pointers to 12,078 not-freed blocks.
==10974== checked 9,009,056 bytes.
==10974== 
==10974== LEAK SUMMARY:
==10974==    definitely lost: 15,762 bytes in 341 blocks.
==10974==      possibly lost: 144,280 bytes in 178 blocks.
==10974==    still reachable: 1,035,265 bytes in 11,559 blocks.
==10974==         suppressed: 0 bytes in 0 blocks.
==10974== Rerun with --leak-check=full to see details of leaked memory.
zsh: segmentation fault  valgrind midori

And the backtrace of previous execution (without valgrind):

vin:~> gdb =midori core
GNU gdb 6.8-debian
[...]
Core was generated by `midori'.
Program terminated with signal 11, Segmentation fault.
[New process 10943]
#0  _gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffe53b6900)
    at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c:1124
1124    /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c: No such file or directory.
        in /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c
(gdb) bt
#0  _gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffe53b6900)
    at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c:1124
#1  0x00007feadc5103e4 in gdk_event_translate (display=0x1bb10a0, 
    event=0x1c27ea0, xevent=0x7fffe53b6900, return_exposes=0)
    at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2093
#2  0x00007feadc5108b7 in _gdk_events_queue (display=0x1bb10a0)
    at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2298
#3  0x00007feadc510c8e in gdk_event_dispatch (source=<value optimized out>, 
    callback=0x7fffe53b6900, user_data=0x1bb10a0)
    at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2358
#4  0x00007feada4dbf7a in IA__g_main_context_dispatch (context=0x1bbd400)
    at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:1814
#5  0x00007feada4df640 in g_main_context_iterate (context=0x1bbd400, block=1, 
    dispatch=1, self=<value optimized out>)
    at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2448
#6  0x00007feada4dfb0d in IA__g_main_loop_run (loop=0x1ccfed0)
    at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2656
#7  0x00007feadc81eb34 in IA__gtk_dialog_run (dialog=0x1bff050)
    at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkdialog.c:1090
#8  0x000000000041d653 in main ()

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #86 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Julien Cristau <jcristau@debian.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Tue, 16 Jun 2009 18:18:07 +0200

This bug occurs on a machine called "vin". The same problem occurs on
a different machine (xvii) when I use the X server of "vin", i.e.

1. On vin, I run "ssh xvii".
2. In the remote shell, I run iceweasel.
3. I double-click on a word in iceweasel, which makes iceweasel crash.

Note: both are x86_64 machines.

Is there a way to trace the XWindow messages? If I provide the
responses from the X server, perhaps you could reproduce the bug.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Message #91 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Vincent Lefevre <vincent@vinc17.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Tue, 16 Jun 2009 18:30:41 +0200

On Tue, Jun 16, 2009 at 18:18:07 +0200, Vincent Lefevre wrote:

> Is there a way to trace the XWindow messages? If I provide the
> responses from the X server, perhaps you could reproduce the bug.
> 
xtrace (xtrace.alioth.debian.org), xscope
(http://cgit.freedesktop.org/xorg/app/xscope), tcpdump/wireshark, and
probably others, might work.

Cheers,
Julien

Message #96 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Julien Cristau <jcristau@debian.org>

Cc: 515946@bugs.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Tue, 16 Jun 2009 21:16:57 +0200

[Message part 1 (text/plain, inline)]

On 2009-06-16 18:30:41 +0200, Julien Cristau wrote:
> xtrace (xtrace.alioth.debian.org), xscope
> (http://cgit.freedesktop.org/xorg/app/xscope), tcpdump/wireshark, and
> probably others, might work.

Here's the xtrace output with midori 0.1.7-1.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

[xtrace-midori.out.bz2 (application/octet-stream, attachment)]

Message #101 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Vincent Lefevre <vincent@vinc17.org>, 515946@bugs.debian.org

Cc: libgtk2.0-0@packages.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Wed, 12 Aug 2009 15:14:36 +0200

On Wed, May 27, 2009 at 17:58:08 +0200, Vincent Lefevre wrote:

> And the backtrace of previous execution (without valgrind):
> 
> vin:~> gdb =midori core
> GNU gdb 6.8-debian
> [...]
> Core was generated by `midori'.
> Program terminated with signal 11, Segmentation fault.
> [New process 10943]
> #0  _gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffe53b6900)
>     at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c:1124
> 1124    /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c: No such file or directory.
>         in /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c

this is:
  Atom xcm_selection_atom = gdk_x11_atom_to_xatom_for_display (screen_x11->display,
                                                               screen_x11->cm_selection_atom);

and screen_x11 is NULL.  It might be worth printing *event, too.

> (gdb) bt
> #0  _gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffe53b6900)
>     at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c:1124
> #1  0x00007feadc5103e4 in gdk_event_translate (display=0x1bb10a0, 
>     event=0x1c27ea0, xevent=0x7fffe53b6900, return_exposes=0)
>     at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2093

eww. gdk_event_translate() is a freaking monster...
the relevant code seems to be:

  window = NULL;
[...]
  get_real_window (display, xevent, &xwindow, &filter_xwindow);

  window = gdk_window_lookup_for_display (display, xwindow);
[...]
  if (window && !GDK_IS_WINDOW (window))
    window = NULL;
[...]
  if (window)
    {
      screen = GDK_WINDOW_SCREEN (window);
      screen_x11 = GDK_SCREEN_X11 (screen);
      toplevel = _gdk_x11_window_get_toplevel (window);
    }
[...]

      if (xevent->type - display_x11->xfixes_event_base == XFixesSelectionNotify)        {
          XFixesSelectionNotifyEvent *selection_notify = (XFixesSelectionNotifyEvent *)xevent;
          _gdk_x11_screen_process_owner_change (screen, xevent);

and we crash here with a NULL screen.  No clue why the libXi bump gets
gtk confused over a fixes event...  cc:ing the gtk maintainers.

According to your xtrace dump the event is something like
000:>:00df: Event XFIXES SelectionNotify(116) subtype=set owner(0x00) window=0x00600001 owner=0x00000000 selection=0x1("PRIMARY") timestamp=0xe9facbed selectionTimestamp=0xe9facbed

One thing you might be able to do is try to spot a difference in xtrace
dumps between the working and broken cases?

> #2  0x00007feadc5108b7 in _gdk_events_queue (display=0x1bb10a0)
>     at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2298
> #3  0x00007feadc510c8e in gdk_event_dispatch (source=<value optimized out>, 
>     callback=0x7fffe53b6900, user_data=0x1bb10a0)
>     at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2358
> #4  0x00007feada4dbf7a in IA__g_main_context_dispatch (context=0x1bbd400)
>     at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:1814
> #5  0x00007feada4df640 in g_main_context_iterate (context=0x1bbd400, block=1, 
>     dispatch=1, self=<value optimized out>)
>     at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2448
> #6  0x00007feada4dfb0d in IA__g_main_loop_run (loop=0x1ccfed0)
>     at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2656
> #7  0x00007feadc81eb34 in IA__gtk_dialog_run (dialog=0x1bff050)
>     at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkdialog.c:1090
> #8  0x000000000041d653 in main ()
> 

Cheers,
Julien

Message #106 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.org>

To: Julien Cristau <jcristau@debian.org>

Cc: 515946@bugs.debian.org, libgtk2.0-0@packages.debian.org

Subject: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash

Date: Thu, 13 Aug 2009 16:34:35 +0200

[Message part 1 (text/plain, inline)]

On 2009-08-12 15:14:36 +0200, Julien Cristau wrote:
> On Wed, May 27, 2009 at 17:58:08 +0200, Vincent Lefevre wrote:
> > And the backtrace of previous execution (without valgrind):
> > vin:~> gdb =midori core
> > GNU gdb 6.8-debian
> > [...]
> > Core was generated by `midori'.
> > Program terminated with signal 11, Segmentation fault.
> > [New process 10943]
> > #0  _gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffe53b6900)
> >     at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c:1124
> > 1124    /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c: No such file or directory.
> >         in /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkscreen-x11.c

Now:

vin:~> gdb midori
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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://www.gnu.org/software/gdb/bugs/>...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/midori 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe62b1950 (LWP 28279)]
[Thread 0x7fffe62b1950 (LWP 28279) exited]

Program received signal SIGSEGV, Segmentation fault.
_gdk_x11_screen_process_owner_change (screen=0x0, event=0x7fffffffd430)
    at /tmp/buildd/gtk+2.0-2.16.5/gdk/x11/gdkscreen-x11.c:1127
1127    /tmp/buildd/gtk+2.0-2.16.5/gdk/x11/gdkscreen-x11.c: No such file or directory.
        in /tmp/buildd/gtk+2.0-2.16.5/gdk/x11/gdkscreen-x11.c

> this is:
>   Atom xcm_selection_atom = gdk_x11_atom_to_xatom_for_display (screen_x11->display,
>                                                                screen_x11->cm_selection_atom);
> 
> and screen_x11 is NULL.  It might be worth printing *event, too.

(gdb) print *event
$1 = {type = 116, xany = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, window = 0}, xkey = {type = 116, serial = 219, 
    send_event = 0, display = 0x696800, window = 0, root = 50331649, 
    subwindow = 0, time = 50331694, x = 0, y = 0, x_root = 8201632, 
    y_root = 0, state = 50331689, keycode = 1, same_screen = 0}, xbutton = {
    type = 116, serial = 219, send_event = 0, display = 0x696800, window = 0, 
    root = 50331649, subwindow = 0, time = 50331694, x = 0, y = 0, 
    x_root = 8201632, y_root = 0, state = 50331689, button = 1, 
    same_screen = 0}, xmotion = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, window = 0, root = 50331649, subwindow = 0, 
    time = 50331694, x = 0, y = 0, x_root = 8201632, y_root = 0, 
    state = 50331689, is_hint = 1 '\1', same_screen = 0}, xcrossing = {
    type = 116, serial = 219, send_event = 0, display = 0x696800, window = 0, 
    root = 50331649, subwindow = 0, time = 50331694, x = 0, y = 0, 
    x_root = 8201632, y_root = 0, mode = 50331689, detail = 1, 
    same_screen = 0, focus = 0, state = 36861488}, xfocus = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, window = 0, 
    mode = 50331649, detail = 0}, xexpose = {type = 116, serial = 219, 
    send_event = 0, display = 0x696800, window = 0, x = 50331649, y = 0, 
    width = 0, height = 0, count = 50331694}, xgraphicsexpose = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, drawable = 0, 
    x = 50331649, y = 0, width = 0, height = 0, count = 50331694, 
    major_code = 0, minor_code = 0}, xnoexpose = {type = 116, serial = 219, 
    send_event = 0, display = 0x696800, drawable = 0, major_code = 50331649, 
    minor_code = 0}, xvisibility = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, window = 0, state = 50331649}, xcreatewindow = {
    type = 116, serial = 219, send_event = 0, display = 0x696800, parent = 0, 
    window = 50331649, x = 0, y = 0, width = 50331694, height = 0, 
    border_width = 0, override_redirect = 0}, xdestroywindow = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, event = 0, 
    window = 50331649}, xunmap = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, event = 0, window = 50331649, from_configure = 0}, 
  xmap = {type = 116, serial = 219, send_event = 0, display = 0x696800, 
    event = 0, window = 50331649, override_redirect = 0}, xmaprequest = {
    type = 116, serial = 219, send_event = 0, display = 0x696800, parent = 0, 
    window = 50331649}, xreparent = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, event = 0, window = 50331649, parent = 0, 
    x = 50331694, y = 0, override_redirect = 0}, xconfigure = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, event = 0, 
    window = 50331649, x = 0, y = 0, width = 50331694, height = 0, 
    border_width = 0, above = 8201632, override_redirect = 50331689}, 
  xgravity = {type = 116, serial = 219, send_event = 0, display = 0x696800, 
    event = 0, window = 50331649, x = 0, y = 0}, xresizerequest = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, window = 0, 
    width = 50331649, height = 0}, xconfigurerequest = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, parent = 0, 
    window = 50331649, x = 0, y = 0, width = 50331694, height = 0, 
    border_width = 0, above = 8201632, detail = 50331689, value_mask = 0}, 
  xcirculate = {type = 116, serial = 219, send_event = 0, display = 0x696800, 
    event = 0, window = 50331649, place = 0}, xcirculaterequest = {type = 116, 
    serial = 219, send_event = 0, display = 0x696800, parent = 0, 
    window = 50331649, place = 0}, xproperty = {type = 116, serial = 219, 
    send_event = 0, display = 0x696800, window = 0, atom = 50331649, time = 0, 
    state = 50331694}, xselectionclear = {type = 116, serial = 219, 
    send_event = 0, display = 0x696800, window = 0, selection = 50331649, 
    time = 0}, xselectionrequest = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, owner = 0, requestor = 50331649, selection = 0, 
    target = 50331694, property = 0, time = 8201632}, xselection = {
    type = 116, serial = 219, send_event = 0, display = 0x696800, 
    requestor = 0, selection = 50331649, target = 0, property = 50331694, 
    time = 0}, xcolormap = {type = 116, serial = 219, send_event = 0, 
    display = 0x696800, window = 0, colormap = 50331649, new = 0, state = 0}, 
  xclient = {type = 116, serial = 219, send_event = 0, display = 0x696800, 
    window = 0, message_type = 50331649, format = 0, data = {
      b = ".\0\0\3", '\0' <repeats 12 times>, " %}", s = {46, 768, 0, 0, 0, 0, 
        0, 0, 9632, 125}, l = {50331694, 0, 8201632, 4345298985, 0}}}, 
  xmapping = {type = 116, serial = 219, send_event = 0, display = 0x696800, 
    window = 0, request = 50331649, first_keycode = 0, count = 0}, xerror = {
    type = 116, display = 0xdb, resourceid = 0, serial = 6907904, 
    error_code = 0 '\0', request_code = 0 '\0', minor_code = 0 '\0'}, 
  xkeymap = {type = 116, serial = 219, send_event = 0, display = 0x696800, 
    window = 0, 
    key_vector = "\1\0\0\3", '\0' <repeats 12 times>, ".\0\0\3", '\0' <repeats 11 times>}, pad = {116, 219, 0, 6907904, 0, 50331649, 0, 50331694, 0, 8201632, 
    4345298985, 0, 36861488, 178, 1393, 8203328, 140737274477152, 0, 0, 
    8201712, 50331690, 0, 36861488, 182}}

> One thing you might be able to do is try to spot a difference in xtrace
> dumps between the working and broken cases?

The only differences seem to be the order of the events (that is
slightly changed) and the numbers. I'm attaching an archive with
the results of the test...

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

[midori-xtrace.tar.xz (application/octet-stream, attachment)]

Message #111 received at 515946@bugs.debian.org (full text, mbox, reply):

From: Nathan Kidd <nkidd@opentext.com>

To: 515946@bugs.debian.org

Subject: Root Cause of This Bug

Date: Wed, 25 Nov 2009 17:11:10 -0500

Root cause of this bug is described here: 
http://lists.freedesktop.org/archives/xorg/2009-November/048184.html

inputproto recently *dropped* from 19 to 17 events, which is probably 
why you noticed it on the same client/xserver machine.

-Nathan

Message #128 received at 515946-close@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: 515946-close@bugs.debian.org

Subject: Bug#515946: fixed in libxi 2:1.3-2

Date: Thu, 07 Jan 2010 10:21:18 +0000

Source: libxi
Source-Version: 2:1.3-2

We believe that the bug you reported is fixed in the latest version of
libxi, which is due to be installed in the Debian FTP archive:

libxi-dev_1.3-2_amd64.deb
  to main/libx/libxi/libxi-dev_1.3-2_amd64.deb
libxi6-dbg_1.3-2_amd64.deb
  to main/libx/libxi/libxi6-dbg_1.3-2_amd64.deb
libxi6_1.3-2_amd64.deb
  to main/libx/libxi/libxi6_1.3-2_amd64.deb
libxi_1.3-2.diff.gz
  to main/libx/libxi/libxi_1.3-2.diff.gz
libxi_1.3-2.dsc
  to main/libx/libxi/libxi_1.3-2.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 515946@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau <jcristau@debian.org> (supplier of updated libxi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 06 Jan 2010 16:23:44 +0000
Source: libxi
Binary: libxi6 libxi6-dbg libxi-dev
Architecture: source amd64
Version: 2:1.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Julien Cristau <jcristau@debian.org>
Description: 
 libxi-dev  - X11 Input extension library (development headers)
 libxi6     - X11 Input extension library
 libxi6-dbg - X11 Input extension library (debug package)
Closes: 515734 515946
Changes: 
 libxi (2:1.3-2) unstable; urgency=low
 .
   * Initialize extension with the right number of events.  This should fix
     issues when libXi announces more events than the X server will actually
     send for that extension, and thus smashes Xlib's event vector (closes:
     #515734, #515946).  Patch by Peter Hutterer, analysis by Nathan Kidd.
   * Upload to unstable.
Checksums-Sha1: 
 c199afef89a5fe2d9658614a0afd679b176bf9ec 2154 libxi_1.3-2.dsc
 2e707cf4fff8aa34205c5bcde7da910dfbb50656 18131 libxi_1.3-2.diff.gz
 f54169c60119dca195ed321b19aae493128fc630 55624 libxi6_1.3-2_amd64.deb
 48034963ba6c50523a8347efc354ac27ea67cebd 400718 libxi6-dbg_1.3-2_amd64.deb
 e56b94f61521353aea169a22bdb28fec1f05cc4a 142410 libxi-dev_1.3-2_amd64.deb
Checksums-Sha256: 
 eba89b80de9b7582a63f493d574cf79ba9546d93e7dfea288ccefa39375fc2fd 2154 libxi_1.3-2.dsc
 e60463381379c09d03ee21ee288fc1380dee4987283b581eec750b6a654fcc90 18131 libxi_1.3-2.diff.gz
 beb8aac50b7f1334d40c2191d460d9a2a56af73220662f4c5d680180ea31a4f7 55624 libxi6_1.3-2_amd64.deb
 d6a96ce641d422ffadb13744b738f9088221a0917fb1694240bd6a6516152b58 400718 libxi6-dbg_1.3-2_amd64.deb
 23895ab58334987535b327a2e27b4b7a462dd36e99654ba55dc30ac903598c70 142410 libxi-dev_1.3-2_amd64.deb
Files: 
 e78803dbc9f68aaaf2e89e8bead4da8a 2154 x11 optional libxi_1.3-2.dsc
 ce2cc28fcb81ceff53d2ef5a81463645 18131 x11 optional libxi_1.3-2.diff.gz
 6af86a0202591a186a401530d692efa6 55624 libs optional libxi6_1.3-2_amd64.deb
 0a172acd363c42ded404202107e045eb 400718 debug extra libxi6-dbg_1.3-2_amd64.deb
 f412e83d461f10c37790c4b10a252b23 142410 libdevel optional libxi-dev_1.3-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLRLriAAoJEDEBgAUJBeQMxFQQAM1OKjpN6YBJnV2pK0bqc9oS
wp4pBm5FoaQUZwO+cc1NRLRvzt7w0baxBwWDLbpCSUjJC2bCfLFmLhe9JpKHPfiG
BsqGQ9a0Dl86aH5G4yqD7SlmcngQHIDU6QHgv0tDR4DsEbqXQhB6398srBec1daJ
G0Weg1ub6IVTuTmAr9p5b2CYerl38zjQRV/ZO0kI41oHzGlZRco9J0YmEYs9NHuR
x0jocLOZ7qVIKpLjjxJIVQoQhEDe1CFfCvSoHD3m3t2tLYwCDFiVSpjjj/w0Y3hr
q1FU6h0cONhu6kiai8vo4Qkvxmuk2+uniMiwUr02YyqAtKa/vYCdndKlcQGxfyLn
n7DIFei/2VXdfvdM9rMB5BMroNZvEQe8xqn/Gga9xP4SGmtUiWaLa1tLE7TmqI6i
P7/141eeTV5DlriJ8MRmR61mG7/furbl0wDBhZmarWS87xOkRZiBekJS6s1/nein
iK4I6pq1+Xj5J6LdNHdglZs8QS9LsS7oglNI4KsR2UF05zoSjXFHRt0qwwIIcc73
jtP1YkmvkFrcCB9aRQseS0V0K6kdPaEdkdaSGvWISYxwUvZuQ8JGhkZjUL9n06q1
Zo6IuqGJZynuk6LbgQ0QfgA40T15ooloZlRsT130jVZpj1XjZonjUZR/X1cZB6tz
ZpRwecqePgDhzcGd9Hec
=/gmS
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.