Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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=0x7fffd430)
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,
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 0x7feadc5103e4 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=0x0061 owner=0x 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 0x7feadc5108b7 in _gdk_events_queue (display=0x1bb10a0)
at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2298
#3 0x7feadc510c8e 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 0x7feada4dbf7a in IA__g_main_context_dispatch (context=0x1bbd400)
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:1814
#5 0x7feada4df640 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 0x7feada4dfb0d in IA__g_main_loop_run (loop=0x1ccfed0)
at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2656
#7 0x7feadc81eb34 in IA__gtk_dialog_run (dialog=0x1bff050)
at /scratch/build-area/gtk+2.0-2.16.1/gtk/gtkdialog.c:1090
#8 0x0041d653 in main ()
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 vinc...@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) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 vinc...@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 Description: Binary data
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 0x7feadc5103e4 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 0x7feadc5108b7 in _gdk_events_queue (display=0x1bb10a0) at /scratch/build-area/gtk+2.0-2.16.1/gdk/x11/gdkevents-x11.c:2298 #3 0x7feadc510c8e 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 0x7feada4dbf7a in IA__g_main_context_dispatch (context=0x1bbd400) at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:1814 #5 0x7feada4df640 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 0x7feada4dfb0d in IA__g_main_loop_run (loop=0x1ccfed0) at
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
Processing commands for cont...@bugs.debian.org: tag 515946 unreproducible moreinfo Bug#515946: libxi6 2:1.2.0-2 makes iceweasel (when selecting text) and midori crash There were no tags set. Tags added: unreproducible, moreinfo kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
Processing commands for cont...@bugs.debian.org: found 515946 libxi/2:1.2.1-2 Bug#515946: libxi6 2:1.2.0-2 makes iceweasel (when selecting text) and midori crash Bug marked as found in version libxi/2:1.2.1-2. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 vinc...@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) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 vinc...@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) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
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 vinc...@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) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
