Bug#711901: random xserver deadlocks in evdev
I applied the patch i.e. 1cb8f074df8d16879ec80d778d26fb5b9af05a3b from git://git.debian.org/git/pkg-xorg/driver/xserver-xorg-input-evdev and it seems that the problem disappeared. at least it did not show up in the last two days. Thanks ! Cheers, Götz Gaycken -- Götz Gaycken - Physikalisches Institut der Universität Bonn Office : CERN bat. 304-1-042 Tel : +41-22-76-78052 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711901: random xserver deadlocks in evdev
Package: xserver-xorg-input-evdev Version: 1:2.7.1-1 Xorg randomly hangs about once per day. As far as I remember the problem occurred when I had the stupid idea to install gnome-shell 3.8, which, I think, also pulled in a xorg update. I am using Debian GNU/Linux amd64 unstable + xorg and gnome from experimental (so I get what I deserve) with a custom kernel 3.8.13 (gcc version 4.7.3 (Debian 4.7.3-4) ), libc6 2.17-4 on a macbook pro 4,1. When the Xserver deadlocks it is still possible to ssh into the machine. It also was possible to attach gdb and force a return from _int_free( ... ) and continue to work. Backtraces with limited information) are attached in the hope that they are useful. The macbook pro has a hardware problem which causes the usb touchpad to disconnect from time to time due to a bad electrical connection. Not sure whether this problem is related to the xserver deadlock. This hardware problem seems to be a general problem for these models and is transparently handled under MacOS X. Such a problem happened about at the times when I experienced this problem. With many regards, Götz Gaycken -- Götz Gaycken - Physikalisches Institut der Universität Bonn Office : CERN bat. 304-1-042 Tel : +41-22-76-78052 System information: Custom kernel: Linux version 3.8.13 (goetz@pcatlbnp01) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 ii xorg-dev 1:7.7+3 all X.Org X Window System development libraries ii xorg-sgml-doctools 1:1.10-1 all Common tools for building X.Org SGML documentation ii xserver-xorg 1:7.7+3 amd64X.Org X server ii xserver-xorg-core2:1.12.4-6 amd64Xorg X server - core server ii xserver-xorg-dev 2:1.12.4-6 amd64Xorg X server - development files ii xserver-xorg-input-evdev 1:2.7.1-1 amd64X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1:1.6.1-1+b1 amd64X.Org X server -- keyboard input driver ii xserver-xorg-input-mtrack0.3.0-1 amd64Multitouch X input driver ii xserver-xorg-input-synaptics 1.6.2-2 amd64Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-wacom 0.15.0+20120515-2 amd64X.Org X server -- Wacom input driver gnome-shell 5Thread 0x7f5e71e5b700 (LWP 28160) "gdbus" 0x7f5e7daa61bd in poll () at ../sysdeps/unix/syscall-template.S:81 4Thread 0x7f5e69b0c700 (LWP 28163) "dconf worker" 0x7f5e7daa61bd in poll () at ../sysdeps/unix/syscall-template.S:81 3Thread 0x7f5e6930b700 (LWP 28164) "gnome-shell" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 2Thread 0x7f5e4effc700 (LWP 28274) "gmain" 0x7f5e7daa61bd in poll () at ../sysdeps/unix/syscall-template.S:81 * 1Thread 0x7f5e8763f9c0 (LWP 4693) "gnome-shell" 0x7f5e7daa61bd in poll () at ../sysdeps/unix/syscall-template.S:81 (gdb) bt #0 0x7f5e7daa61bd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5e7b71d1c2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f5e7b71e697 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f5e7b71e8bb in xcb_wait_for_reply () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7f5e803de32d in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x7f5e81c0d7bc in ?? () from /usr/lib/x86_64-linux-gnu/libXi.so.6 #6 0x7f5e81c0d9c3 in XIGrabKeycode () from /usr/lib/x86_64-linux-gnu/libXi.so.6 #7 0x7f5e86c9b0fa in ?? () from /usr/lib/libmutter.so.0 #8 0x7f5e86c9b2cb in ?? () from /usr/lib/libmutter.so.0 #9 0x7f5e86c9b7d3 in meta_window_grab_keys () from /usr/lib/libmutter.so.0 #10 0x7f5e86c9b8a8 in ?? () from /usr/lib/libmutter.so.0 #11 0x7f5e86c90414 in ?? () from /usr/lib/libmutter.so.0 #12 0x7f5e86cdb6a7 in ?? () from /usr/lib/libmutter.so.0 #13 0x7f5e7fa82801 in gdk_event_apply_filters (xevent=xevent@entry=0x7fffc54dea20, event=event@entry=0xd770c20, window=window@entry=0x0) at /build/buildd-gtk+3.0_3.8.0-1-amd64-grmSSt/gtk+3.0-3.8.0/./gdk/x11/gdkeventsource.c:81 #14 0x7f5e7fa829d7 in gdk_event_source_translate_event (xevent=0x7fffc54dea20, event_source=0x1dafec0) at /build/buildd-gtk+3.0_3.8.0-1-amd64-grmSSt/gtk+3.0-3.8.0/./gdk/x11/gdkeventsource.c:195 #15 _gdk_x11_display_queue_events (display=0x1dae050) at /build/buildd-gtk+3.0_3.8.0-1-amd64-grmSSt/gtk+3.0-3.8.0/./gdk/x11/gdkeventsource.c:338 #16 0x7f5e7fa55be
Bug#674131: evolution hangs when trying to synchronising with imapx server after suspend/resume
Package: evolution Version: 3.4.2-1 After hibernate or suspend/resume evolution hangs when trying to synchronise with an imapx server. The problem appeared, if I remember correctly, at about version 3.2.2-1. I was hoping that 3.4.2.1 would solve the problem but it did not. The problem did not exist in for example the first gnome3 version and the late gnome 2 versions. A backtrace is attached. I am using debian (mostly) unstable amd64, libc6 2.13-27, custom linux 3.2.13 SMP PREEMPT. With many regards Götz Gaycken evolution_gdb.log.gz Description: GNU Zip compressed data
Bug#648562: gtk3 applications abort on errors XI_BadDevice
> Could you subscribe to the upstream report? They will probably ask you > for details. Sure, thanks ! Götz Gaycken -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648562: gtk3 applications abort on errors XI_BadDevice
Package: libgtk-3-0 Version: 3.2.1-1 After updating to gtk3/gnome3 applications I experience frequent application aborts due to "XI_BadDevice (invalid Device parameter)" see below. The equivalent gtk2 applications handled the XI_BadDevice without aborting. I experienced the problem also in earlier versions of libgtk-3-0 e.g. 3.0.12-2 The XI_BadDevice seems to be caused in my case by a (not so uncommon) hardware problem which leads to disconnects and reconnects of the USB keyboard and touchpad of my Macbook pro. When using gtk2 applications the problem only lead to a short interruption during which the touchpad and keyboard was not functional. After the touchpad and keyboard get reconnected everything works normally, except for the gtk3 applications which abort (see below for error messaes) [The disconnects and reconnects also occur under OSX and are from a user point of view hardly noticable]. After updating to gnome3, the "disconnects" also abort the gnome-session i.e. I get logged out whenever this problem occurs. With many regards, Götz Gaycken (evolution:14840): Gdk-WARNING **: The program 'evolution' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadDevice (invalid Device parameter)'. (Details: serial 63439 error_code 160 request_code 143 minor_code 48) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ... ... (nm-applet:12109): Gdk-WARNING **: The program 'nm-applet' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadDevice (invalid Device parameter)'. (Details: serial 5255 error_code 160 request_code 143 minor_code 48) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) gnome-session[12009]: Gdk-WARNING: The program 'gnome-session' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadDevice (invalid Device parameter)'. (Details: serial 191 error_code 160 request_code 143 minor_code 48) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
