Bug#651746:
The lock seems to be occure in pulse: Running gnome-shell inside gdb, show that backtrace: Program received signal SIGINT, Interrupt. 0x73a2d2b7 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 (gdb) bt #0 0x73a2d2b7 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fffee98b7a0 in pa_threaded_mainloop_wait () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fffe34cc962 in pulse_driver_play () from /usr/lib/libcanberra-0.28/libcanberra-pulse.so #3 0x74f6445b in ca_context_play_full () from /usr/lib/libcanberra.so.0 #4 0x74f647af in ca_context_play () from /usr/lib/libcanberra.so.0 #5 0x7743bce4 in meta_workspace_activate_with_focus () from /usr/lib/libmutter.so.0 #6 0x7517a7bc in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.5 #7 0x7517a237 in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.5 #8 0x771abf45 in ?? () from /usr/lib/libgjs.so.0 #9 0x771acfb0 in ?? () from /usr/lib/libgjs.so.0 #10 0x76cc5540 in ?? () from /usr/lib/libmozjs.so.8d #11 0x76cba8f2 in ?? () from /usr/lib/libmozjs.so.8d #12 0x76cc5490 in ?? () from /usr/lib/libmozjs.so.8d #13 0x76c949f0 in ?? () from /usr/lib/libmozjs.so.8d #14 0x76cc54d3 in ?? () from /usr/lib/libmozjs.so.8d #15 0x76cc5b87 in ?? () from /usr/lib/libmozjs.so.8d #16 0x76c3e2b1 in JS_CallFunctionValue () from /usr/lib/libmozjs.so.8d #17 0x7719ff0c in gjs_call_function_value () from /usr/lib/libgjs.so.0 #18 0x771aa8fd in gjs_closure_invoke () from /usr/lib/libgjs.so.0 #19 0x771b3ba9 in ?? () from /usr/lib/libgjs.so.0 #20 0x7fffee718804 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7fffee72a78a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7fffee733e11 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x7fffee733fb2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x77b7ad69 in ?? () from /usr/lib/gnome-shell/libgnome-shell.so #25 0x77417c78 in ?? () from /usr/lib/libmutter.so.0 #26 0x77418e4c in meta_display_process_key_event () from /usr/lib/libmutter.so.0 #27 0x7740d75b in ?? () from /usr/lib/libmutter.so.0 #28 0x77457ef6 in ?? () from /usr/lib/libmutter.so.0 #29 0x7079a7f1 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #30 0x7079a94b in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #31 0x707728d1 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #32 0x7079a692 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #33 0x7fffee04b0cf in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7fffee04b8c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fffee04be02 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7741a691 in meta_run () from /usr/lib/libmutter.so.0 #37 0x00402c61 in main () (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/gnome-shell --replace -- Jean Schurger http://schurger.org (broken) 030A C5CB 269B E2DB FE8A F6FE 2749 CC01 AFBA 3712 signature.asc Description: This is a digitally signed message part
Bug#651746: libc6: upgrade lead to GNOME desktop freezing up
Package: libc6 Version: 2.13-22 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Hi! After upgrading to 2.13-22 this morning and performing a login into my GNOME (3.2) desktop, it (mainly the window manager) froze up within 20 seconds. I was only able to unfreeze it by killing the window manager and starting it again from the console, followed by a quick freeze-up again and again. This is not only case using gnome-shell, but also when using the GNOME Classic desktop and thus metacity. After downgrading to libc6 2.13-21, things started working again. Kind regards, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii libc-bin 2.13-21 ii libgcc1 1:4.6.2-7 libc6 recommends no packages. Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.41 ii glibc-doc none ii locales2.13-22 -- debconf information: * glibc/upgrade: true glibc/disable-screensaver: glibc/restart-failed: * glibc/restart-services: ssh postfix cups cron atd libraries/restart-without-asking: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
