Your message dated Fri, 28 Aug 2015 11:36:30 +0200 with message-id <[email protected]> and subject line Re: Bug#652709: gnome-shell: hangs when going into activities, never returns has caused the Debian Bug report #652709, regarding gnome-shell: hangs when going into activities, never returns to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 652709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652709 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-shell Version: 3.2.1-8 Severity: important Hi all, just another bug report on that funny gnome-shell: Doing some long running task (converting images to smaller size, several thousands), suddenly everything stopped. I killed phatch (the converter program) and went into activities to restart it. Alas, going there, typing "phat" it showed up, so I clicked onto it and that was the end. gnome-shell did not react to *anything* anymore. No kbd, no mouse, nothing. I could still switch between console and X, I could still use the console without any problem, but gnome-shell decided to go into solipsistic mode and didn't interact with anyone. I tried from the console to send gnome-shell some signals to wake up, but also these were rejected. When I killed the gnome shell with kill -9, it restarted for a short time, but stopped again. Then it started to get funny, because I kill -9 again, and then the window manager was gone, but all the windows (without frames) were still present. So I closed them one by one (to make sure that there is no data loss due to this g-s bastard). Then I killed the gnome-session process which restarted the X server and I was back to normal. I captured the output of .xsession-errors (the end of it, where it started): ------------- end of xsession-errors.log ----------- (gnome-settings-daemon:3458): PackageKit-WARNING **: failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (gnome-settings-daemon:3458): updates-plugin-WARNING **: failed to get time: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Window manager warning: Log level 8: meta_window_lower: assertion `!window->override_redirect' failed Traceback (most recent call last): File "/usr/share/phatch/phatch/pyWx/gui.py", line 701, in on_menu_tools_execute self._execute(actionlist) File "/usr/share/phatch/phatch/pyWx/gui.py", line 300, in _execute update=self._send_update_event, **keyw) File "/usr/share/phatch/phatch/core/api.py", line 729, in apply_actions_to_photos is_done, image_index, repeat) File "/usr/share/phatch/phatch/core/api.py", line 780, in apply_actions_to_photo photo.close() AttributeError: 'NoneType' object has no attribute 'close' Window manager warning: Log level 8: meta_window_raise: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_lower: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_raise: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_lower: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_raise: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_lower: assertion `!window->override_redirect' failed WARNING: gnome-keyring:: invalid error response from gnome-keyring-daemon: too short WARNING: gnome-keyring:: invalid message: couldn't read call identifier WARNING: gnome-keyring:: invalid error response from gnome-keyring-daemon: too short gnome-shell: gkm-rpc-module.c:421: call_read: Assertion `len > 0' failed. (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! ** Message: applet now removed from the notification area gnome-shell-calendar-server[9493]: Got HUP on stdin - exiting Window manager warning: Workarounds for broken applications disabled. Some applications may not behave properly. (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices (gnome-shell:11294): folks-DEBUG: individual-aggregator.vala:310: Setting primary store IDs to defaults. (gnome-shell:11294): folks-DEBUG: individual-aggregator.vala:338: Primary store IDs are 'eds' and 'system'. JS ERROR: !!! WARNING: 'assignment to undeclared variable idx' JS ERROR: !!! WARNING: file '/home/norbert/.local/share/gnome-shell/extensions/[email protected]/extension.js' line 4 exception 0 number 156 JS LOG: GNOME Shell started at Tue Dec 20 2011 17:12:21 GMT+0900 (JST) gnome-session[3377]: WARNING: Application 'gnome-shell.desktop' killed by signal gnome-session[3377]: WARNING: App 'gnome-shell.desktop' respawning too quickly (gnome-settings-daemon:3458): color-plugin-WARNING **: Done switch to new account, reload devices ------------------------------------------------------- I also collected the output of Ctrl-PrtScr-t, so the running task traces, I attach the syslog (compressed, otherwise it is too big). Maybe someone can find an explanation. For me it was looking like everything froze when I clicked the icon of phatch. Enjoy Norbert -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (501, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc6+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii gir1.2-accountsservice-1.0 0.6.15-2 ii gir1.2-atk-1.0 2.2.0-2 ii gir1.2-caribou-1.0 0.4.1-2 ii gir1.2-clutter-1.0 1.8.2-2 ii gir1.2-cogl-1.0 1.8.2-1 ii gir1.2-coglpango-1.0 1.8.2-1 ii gir1.2-folks-0.6 0.6.6-1 ii gir1.2-freedesktop 1.31.1-1 ii gir1.2-gconf-2.0 3.2.3-1 ii gir1.2-gdkpixbuf-2.0 2.24.0-2 ii gir1.2-gee-1.0 0.6.1-3 ii gir1.2-gkbd-3.0 3.2.0-1 ii gir1.2-glib-2.0 1.31.1-1 ii gir1.2-gmenu-3.0 3.2.0.1-2 ii gir1.2-gnomebluetooth-1.0 3.2.1-1 ii gir1.2-gtk-3.0 3.2.2-3 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.0 3.2.1-2 ii gir1.2-networkmanager-1.0 0.9.2.0-1 ii gir1.2-pango-1.0 1.29.4-2 ii gir1.2-polkit-1.0 0.103-1 ii gir1.2-soup-2.4 2.36.1-1 ii gir1.2-telepathyglib-0.12 0.16.2-1 ii gir1.2-telepathylogger-0.2 0.2.10-2 ii gir1.2-upowerglib-1.0 0.9.15-1 ii gjs 1.30.0-2 ii gnome-bluetooth 3.2.1-1 ii gnome-icon-theme-symbolic 3.2.1-1 ii gnome-settings-daemon 3.2.2-2 ii gnome-shell-common 3.2.1-8 ii gsettings-desktop-schemas 3.2.0-2 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-23 ii libcairo-gobject2 1.10.2-6.2 ii libcairo2 1.10.2-6.2 ii libcamel-1.2-29 3.2.2-1 ii libcanberra0 0.28-3 ii libclutter-1.0-0 1.8.2-2 ii libcogl-pango0 1.8.2-1 ii libcogl5 1.8.2-1 ii libcroco3 0.6.2-2 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-2 0.98-1 ii libdrm2 2.4.29-1 ii libebook-1.2-12 3.2.2-1 ii libecal-1.2-10 3.2.2-1 ii libedataserver-1.2-15 3.2.2-1 ii libedataserverui-3.0-1 3.2.2-1 ii libffi5 3.0.10-3 ii libfolks25 0.6.6-1 ii libfontconfig1 2.8.0-3 ii libfreetype6 2.4.8-1 ii libgconf2-4 3.2.3-1 ii libgdk-pixbuf2.0-0 2.24.0-2 ii libgee2 0.6.1-3 ii libgirepository-1.0-1 1.31.1-1 ii libgjs0b [libgjs0-libmozjs8d] 1.30.0-2 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.30.2-4 ii libgnome-desktop-3-2 3.2.1-3 ii libgnome-keyring0 3.2.2-1 ii libgnome-menu-3-0 3.2.0.1-2 ii libgstreamer0.10-0 0.10.35-1 ii libgtk-3-0 3.2.2-3 ii libical0 0.44-3 ii libjson-glib-1.0-0 0.14.2-1 ii libmozjs8d 8.0-3+b1 ii libmutter0 3.2.1-2 ii libnm-glib4 0.9.2.0-1 ii libnm-util2 0.9.2.0-1 ii libnspr4-0d 4.8.9-1 ii libnss3-1d 3.13.1.with.ckbi.1.88-1 ii libpango1.0-0 1.29.4-2 ii libpolkit-agent-1-0 0.103-1 ii libpolkit-gobject-1-0 0.103-1 ii libpulse-mainloop-glib0 1.1-2 ii libpulse0 1.1-2 ii libsoup2.4-1 2.36.1-1 ii libsqlite3-0 3.7.9-2 ii libstartup-notification0 0.12-1 ii libtelepathy-glib0 0.16.2-1 ii libtelepathy-logger2 0.2.10-2 ii libx11-6 2:1.4.4-4 ii libxcomposite1 1:0.4.3-2 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.0-3 ii libxfixes3 1:5.0-4 ii libxi6 2:1.4.3-3 ii libxml2 2.7.8.dfsg-5 ii python 2.7.2-9 ii telepathy-mission-control-5 1:5.10.1-1 Versions of packages gnome-shell recommends: ii gnome-contacts 3.2.2-2 ii gnome-control-center 1:3.2.2-2 ii gnome-session-fallback 3.2.1-1 ii gnome-themes-standard 3.2.1-2 gnome-shell suggests no packages. -- no debconf information
syslog.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---Norbert Preining wrote (28 Aug 2015 00:51:39 GMT) : >> This bug is now almost 4 years old. Can you still reproduce it on >> current Debian? > Sorry, no idea. I have banished and burned out all traces of > Gnome3 from all my computers. > Feel free to close the bug Thanks, doing so.
--- End Message ---
