Bug#648052: metacity segfaults after todays update to wheezy
On 14.11.2011, 12:22 +0100 S. G. wrote: A Gnome fall-back session crashes when trying to open the first window. Further investigations revealed that this is caused by my mac-os-like button layout defined in ~/.gconf/apps/metacity/general/%gonf.xml: close,minimize,maximize It's sufficient to 'shift' the buttons to the right to let metacity operate properly. :close,minimize,maximize *** .gconf/apps/metacity/general/%gonf.xml ?xml version=1.0? gconf entry name=num_workspaces mtime=1321347443 type=int value=1/ entry name=compositing_manager mtime=1320858200 type=bool value=false/ entry name=button_layout mtime=1297690075 type=string stringvalueclose,minimize,maximize/stringvalue /entry entry name=theme mtime=1315909815 type=string stringvalueMurrinePixmap/stringvalue /entry /gconf Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648052: metacity segfaults after todays update to wheezy
On 13.11.2011, 21:54 +0100 Michael Biebl wrote: the compiz autostart file looks suspicious. You can't really run compiz together with gnome-shell, as it has its builtin compositor. Good to know :-) Are there any plans regarding coexistence of gnome-shell and compiz other then using the fallback mode? Could you try moving that autostart file away and test again. I did so. Now a Gnome default session starts up and works flawlessly. But ... A Gnome fall-back session crashes when trying to open the first window. *** /var/log/messages Nov 14 11:15:28 t500sg kernel: [ 2006.351576] metacity[6877]: segfault at 14bf84d0 ip 00458395 sp 7fff425781e8 error 4 in metacity[40+88000] And this is the corresponding backtrace: #0 0x00458395 in ?? () #1 0x0045e3bb in ?? () #2 0x0045f3fc in ?? () #3 0x0044a5f9 in ?? () #4 0x0044c690 in ?? () #5 0x7f3bd21c01a8 in _gtk_marshal_BOOLEAN__BOXED (closure=0x1088160, return_value=0x7fff6d5999e0, n_param_values=optimized out, param_values=0x111c430, invocation_hint=optimized out, marshal_data=optimized out) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gtk/gtkmarshalers.c:86 #6 0x7f3bd102e03e in g_closure_invoke (closure=0x1088160, return_value=0x7fff6d5999e0, n_param_values=2, param_values=0x111c430, invocation_hint=0x7fff6d5999a0) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./gobject/gclosure.c:767 #7 0x7f3bd103eced in signal_emit_unlocked_R (node=optimized out, detail=0, instance=0x110c000, emission_return=0x7fff6d599b40, instance_and_params=0x111c430) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./gobject/gsignal.c:3290 #8 0x7f3bd104844b in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=optimized out) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./gobject/gsignal.c:2993 #9 0x7f3bd1048832 in g_signal_emit (instance=optimized out, signal_id=optimized out, detail=optimized out) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./gobject/gsignal.c:3040 #10 0x7f3bd22d9051 in gtk_widget_event_internal (widget=0x110c000, event=0x7fff6d599d20) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gtk/gtkwidget.c:4984 #11 0x7f3bd21be987 in IA__gtk_main_do_event (event=0x7fff6d599d20) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gtk/gtkmain.c:1620 #12 0x7f3bd1e11b0c in _gdk_window_process_updates_recurse (window=0x1062480, expose_region=0x111c490) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gdk/gdkwindow.c:5429 #13 0x7f3bd1e0cad3 in gdk_window_process_updates_internal (window=0x1062480) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gdk/gdkwindow.c:5588 #14 0x7f3bd1e0ec71 in IA__gdk_window_process_all_updates () at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gdk/gdkwindow.c:5696 #15 0x7f3bd1e0ecd9 in gdk_window_update_idle (data=optimized out) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gdk/gdkwindow.c:5322 #16 0x7f3bd1dec286 in gdk_threads_dispatch (data=0x111a740) at /build/buildd-gtk+2.0_2.24.7-1-amd64-huURlY/gtk+2.0-2.24.7/gdk/gdk.c:512 #17 0x7f3bcfd35edd in g_main_dispatch (context=0x1037fe0) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./glib/gmain.c:2441 #18 g_main_context_dispatch (context=0x1037fe0) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./glib/gmain.c:3014 #19 0x7f3bcfd366b8 in g_main_context_iterate (context=0x1037fe0, block=optimized out, dispatch=1, self=optimized out) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./glib/gmain.c:3092 #20 0x7f3bcfd36cfa in g_main_loop_run (loop=0x1038420) at /build/buildd-glib2.0_2.28.8-1-amd64-O6EeLn/glib2.0-2.28.8/./glib/gmain.c:3300 #21 0x00411166 in ?? () #22 0x7f3bce76fead in __libc_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff6d59a608) at libc-start.c:228 #23 0x00411555 in ?? () #24 0x7fff6d59a608 in ?? () #25 0x001c in ?? () #26 0x0001 in ?? () #27 0x7fff6d59bc20 in ?? () #28 0x in ?? () Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648052: metacity segfaults after todays update to wheezy
severity 648052 important thanks On 09.11.2011 14:24, S. G. wrote: Hi Is this problem reproducible after a reboot? On Tuesday, 08.11.2011, 17:50 +0100 wrote S. G.: Rebooting system didn't help. Yes, it is. Can you also test with a newly created user account. A newly created user account works. Obviously as no metacity process has been started. Hm, could you elaborate on this? Why is it obvious that no metacity process has been started? To be clear: You are trying to start a default GNOME session, i.e. not the fallback one. And your hardwared is 3D capable, so should be able to run gnome-shell. But metacity is started anyway? Do you maybe have an autostart file for metacity in ~/.config/autostart? Logging into my normal accout starting a Gnome fallback session also works for the same reason. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#648052: metacity segfaults after todays update to wheezy
On 13.11.2011, 14:24 +0100 Michael Biebl wrote: severity 648052 important thanks On 09.11.2011 14:24, S. G. wrote: Hi Is this problem reproducible after a reboot? On Tuesday, 08.11.2011, 17:50 +0100 wrote S. G.: Rebooting system didn't help. Yes, it is. Can you also test with a newly created user account. A newly created user account works. Obviously as no metacity process has been started. Hm, could you elaborate on this? Why is it obvious that no metacity process has been started? For the newly created user a default Gnome session consists of the following processes /usr/sbin/gdm3 \_ /usr/lib/gdm3/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1 \_ /usr/bin/Xorg :0 -br -verbose -novtswitch -auth /var/run/gdm3/auth-for-Debian-gdm-mYMD6w/database -nolisten tcp vt7 \_ /usr/lib/gdm3/gdm-session-worker \_ gnome-session \_ /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session gnome-session \_ /usr/lib/gnome-settings-daemon/gnome-settings-daemon \_ gnome-power-manager \_ /usr/bin/gnome-shell | \_ gnome-terminal | \_ gnome-pty-helper | \_ bash | \_ ps axwfu \_ update-notifier \_ /usr/lib/evolution/3.0/evolution-alarm-notify \_ /usr/lib/gnome-disk-utility/gdu-notification-daemon \_ kerneloops-applet \_ gnome-screensaver \_ nm-applet \_ python /usr/bin/system-config-printer-applet Before I used to see a /usr/bin/metacity in the tree below gnome-session. To be clear: You are trying to start a default GNOME session, i.e. not the fallback one. Exactly. And your hardwared is 3D capable, Yes, it is. I use to run compiz. so should be able to run gnome-shell. But metacity is started anyway? Yes, that's the way it seems to me, because of the segfaults logged to /var/log/messages whenever I try to log into a default GNOME session. Do you maybe have an autostart file for metacity in ~/.config/autostart? 'Unfortunately' not. sg@t500sg:~$ ls -l .config/autostart/ total 12 -rw-r--r-- 1 sg sg 2744 Feb 12 2011 cairo-dock.desktop -rw-r--r-- 1 sg sg 241 Feb 12 2011 compiz.desktop -rw-r--r-- 1 sg sg 191 Mar 11 2011 remmina-applet.desktop Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648052: metacity segfaults after todays update to wheezy
On 13.11.2011 20:56, S. G. wrote: Do you maybe have an autostart file for metacity in ~/.config/autostart? 'Unfortunately' not. sg@t500sg:~$ ls -l .config/autostart/ total 12 -rw-r--r-- 1 sg sg 2744 Feb 12 2011 cairo-dock.desktop -rw-r--r-- 1 sg sg 241 Feb 12 2011 compiz.desktop the compiz autostart file looks suspicious. You can't really run compiz together with gnome-shell, as it has its builtin compositor. Could you try moving that autostart file away and test again. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#648052: metacity segfaults after todays update to wheezy
Hi Is this problem reproducible after a reboot? On Tuesday, 08.11.2011, 17:50 +0100 wrote S. G.: Rebooting system didn't help. Yes, it is. Can you also test with a newly created user account. A newly created user account works. Obviously as no metacity process has been started. Logging into my normal accout starting a Gnome fallback session also works for the same reason. If the problem is reproducible, please try to get a backtrace I will do my very best. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648052: metacity segfaults after todays update to wheezy
Hi If the problem is reproducible, please try to get a backtrace I will do my very best. There is no package metacity-dbg hence no symbols. The backtrace result doesn't look helpfully to me, see below. sg@t500sg:~/bin$ gdb metacity GNU gdb (GDB) 7.3-debian Copyright (C) 2011 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/... Reading symbols from /usr/bin/metacity...(no debugging symbols found)...done. (gdb) set pagination 0 (gdb) run --replace Starting program: /usr/bin/metacity --replace [Thread debugging using libthread_db enabled] Gtk-Message: Failed to load module pk-gtk-module [New Thread 0x7fffeeaba700 (LWP 13658)] Program received signal SIGSEGV, Segmentation fault. 0x00458395 in ?? () (gdb) set logging on Copying output to gdb.txt. (gdb) thread apply all bt Cannot find new threads: generic error (gdb) bt #0 0x00458395 in ?? () Cannot access memory at address 0x7fffcda8 (gdb) bt full #0 0x00458395 in ?? () No symbol table info available. Cannot access memory at address 0x7fffcda8 When running in gdb no segmentation fault is logged to /var/log/messages. Additionally I had to 'kill -KILL' metacity to get access to the console window again to issue command 'set logging on', etc. Please give advice how to do better debugging. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648052: metacity segfaults after todays update to wheezy
Package: metacity Version: 1:2.34.1-2 Severity: critical Justification: breaks the whole system Dear Maintainer, since doing the last update documented below after '*** var-log-apt-history.log' I am not able to start the GUI anymore. metacity is logging segmentation faults to /var/log/messages, see '*** var-log-messages' below. X seems to start properly, see '*** var-log-Xorg.0.log' below. Rebooting system didn't help. *** var-log-apt-history.log Start-Date: 2011-11-07 18:08:24 Commandline: /usr/sbin/synaptic Install: printer-driver-foo2zjs:amd64 (20111023dfsg0-1, automatic), libgtksourceview-3.0-0:amd64 (3.2.2-1, automatic), gir1.2-gtksource-3.0:amd64 (3.2.2-1, automatic), libgtksourceview-3.0-common:amd64 (3.2.2-1, automatic), gir1.2-gucharmap-2.90:amd64 (3.0.1-1, automatic) Upgrade: gedit-common:amd64 (2.30.4-2, 3.0.6-2), libunique-1.0-0:amd64 (1.1.6-2, 1.1.6-3), libunistring0:amd64 (0.9.3-4, 0.9.3-5), gedit:amd64 (2.30.4-2, 3.0.6-2), librsvg2-common:amd64 (2.34.1-2, 2.34.1-3), sudo:amd64 (1.8.2-2, 1.8.3p1-1), foo2zjs:amd64 (20110811dfsg-1, 20111023dfsg0-1), gedit-plugins:amd64 (2.30.0-1, 3.0.6-1), librsvg2-2:amd64 (2.34.1-2, 2.34.1-3), ca-certificates:amd64 (20110502+nmu1, 20111025) End-Date: 2011-11-07 18:09:48 Start-Date: 2011-11-07 18:10:46 Commandline: /usr/sbin/synaptic Purge: python-gtksourceview2:amd64 (2.10.1-2), libgtksourceview2.0-0:amd64 (2.10.4-1), libgtksourceview2.0-common:amd64 (2.10.4-1) End-Date: 2011-11-07 18:10:48 Start-Date: 2011-11-08 10:57:00 Commandline: /usr/sbin/synaptic Install: libgupnp-av-1.0-2:amd64 (0.8.0-2, automatic), python-packagekit:amd64 (0.6.18-1, automatic), python-libproxy:amd64 (0.3.1-4, automatic), libgnome-bluetooth8:amd64 (3.2.1-1, automatic), gir1.2-rb-3.0:amd64 (2.90.1~git20110919.2dfea6-3, automatic), gir1.2-gnomebluetooth-1.0:amd64 (3.2.1-1, automatic), gnome-shell:amd64 (3.0.2-5, automatic), libdmapsharing-3.0-2:amd64 (2.9.12-1, automatic), gir1.2-upowerglib-1.0:amd64 (0.9.14-1, automatic), libcanberra-pulse:amd64 (0.28-3, automatic), libgnome-control-center1:amd64 (3.0.2-3, automatic), libgail-3-common:amd64 (3.0.12-2, automatic), pulseaudio:amd64 (1.0-4, automatic), gir1.2-telepathyglib-0.12:amd64 (0.16.0-1, automatic), libevince3-3:amd64 (3.2.1-1, automatic), gnome-icon-theme-extras:amd64 (3.0.0-3, automatic), packagekit-backend-aptcc:amd64 (0.6.18-1+b1, automatic), accountsservice:amd64 (0.6.15-1, automatic), telepathy-idle:amd64 (0.1.10-1, automatic), pulseaudio-module-x11:amd64 (1.0-4, automatic), gnome-control-ce nter-data:amd64 (3.0.2-3, automatic), vinagre:amd64 (3.2.1-1, automatic), librhythmbox-core4:amd64 (2.90.1~git20110919.2dfea6-3, automatic), libtotem0:amd64 (3.0.1-3, automatic), mutter-common:amd64 (3.0.2.1-4, automatic), gir1.2-polkit-1.0:amd64 (0.102-1, automatic), libaccountsservice0:amd64 (0.6.15-1, automatic), libgtk-vnc-2.0-0:amd64 (0.4.3-6+b1, automatic), gir1.2-soup-2.4:amd64 (2.34.3-1, automatic), gnome-icon-theme-symbolic:amd64 (3.2.1-1, automatic), gir1.2-gkbd-3.0:amd64 (3.2.0-1, automatic), gnome-session-fallback:amd64 (3.0.2-3, automatic), gir1.2-totem-1.0:amd64 (3.0.1-3, automatic), libmutter0:amd64 (3.0.2.1-4, automatic), gir1.2-telepathylogger-0.2:amd64 (0.2.10-2, automatic), apg:amd64 (2.2.3.dfsg.1-2, automatic), telepathy-butterfly:amd64 (0.5.15-2.1, automatic), rtkit:amd64 (0.10-2, automatic), libpanel-applet-4-0:amd64 (3.0.2-1, automatic), gnome-packagekit-data:amd64 (3.0.3-2, automatic), fonts-cantarell:amd64 (0.0.6+git20110405-1, automatic), libavahi-u i-gtk3-0:amd64 (0.6.30-5, automatic), libmetacity-private0a:amd64 (2.34.1-2, automatic), pulseaudio-esound-compat:amd64 (1.0-4, automatic), gir1.2-totem-plparser-1.0:amd64 (2.32.6-1, automatic), gjs:amd64 (1.29.0-2+b1, automatic), rdesktop:amd64 (1.7.0-1, automatic), python-telepathy:amd64 (0.15.19-2.1, automatic), librest-0.7-0:amd64 (0.7.10-1, automatic), libgnomekbd7:amd64 (3.2.0-1, automatic), libgnome-media-profiles-3.0-0:amd64 (3.0.0-1, automatic), gstreamer0.10-pulseaudio:amd64 (0.10.30-1, automatic), grilo-plugins-0.1:amd64 (0.1.17-1, automatic), packagekit:amd64 (0.6.18-1+b1, automatic), zeitgeist-core:amd64 (0.8.2-1, automatic), libpackagekit-glib2-14:amd64 (0.6.18-1+b1, automatic), libgvnc-1.0-0:amd64 (0.4.3-6+b1, automatic), gir1.2-networkmanager-1.0:amd64 (0.9.0-2, automatic), python-farsight:amd64 (0.0.31-1, automatic), python-papyon:amd64 (0.5.5-2, automatic), gir1.2-mutter-3.0:amd64 (3.0.2.1-4, automatic), gir1.2-webkit-3.0:amd64 (1.4.2-2, automatic), libgril o-0.1-0:amd64 (0.1.17-1, automatic), gnome-font-viewer:amd64 (3.0.1-5, automatic), libnautilus-extension1a:amd64 (3.0.2-4, automatic), gir1.2-panelapplet-4.0:amd64 (3.0.2-1, automatic), gnome-packagekit:amd64 (3.0.3-2, automatic), libgjs0b:amd64 (1.29.0-2+b1, automatic), libbrasero-media3-1:amd64 (3.0.0-4, automatic), nautilus-sendto-empathy:amd64 (3.2.0.1-1, automatic), pulseaudio-utils:amd64 (1.0-4, automatic),
Bug#648052: metacity segfaults after todays update to wheezy
Hello, I just upgraded my Debian Testing AMD64 system, and I cannot confirm this bug. Upgraded all 70 packages, 42 new, 5 deleted. After rebooting my profile was been successfully loaded, but GNOME3 runs in fallback mode (due to problem with graphic driver, it said - I will investigate it later). I suggest to you to revert system from backup, do safe-upgrade and wait for responses/ideas in this bug report. Regards, Piotr Drozdek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648052: metacity segfaults after todays update to wheezy
severity 648052 grave thanks Is this problem reproducible after a reboot? Can you also test with a newly created user account. If the problem is reproducible, please try to get a backtrace following the steps at [1]. Michael [1] http://wiki.debian.org/HowToGetABacktrace -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
