Your message dated Mon, 17 Feb 2014 17:19:38 -0500
with message-id 
<CANTw=mpreo3ezekdu0_shmz8rs_a0qslfnpf62i4lpgbj7x...@mail.gmail.com>
and subject line Re: Bug#673176: Fwd: Chromium is locking up entire Gnome-Shell 
regularly
has caused the Debian Bug report #673176,
regarding chromium: Chromium is locking up entire Gnome-Shell regularly
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.)


-- 
673176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673176
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 18.0.1025.168~r134367-1
Severity: critical
Tags: upstream
Justification: breaks unrelated software

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
Regular browsing behaviour, nothing out of the ordinary.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Logged in via console and quit Xorg

   * What was the outcome of this action?

Able to run Chromium again until next Gnome-Shell Lockup





-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-486
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chromium depends on:
ii  chromium-inspector  18.0.1025.168~r134367-1
ii  gconf-service       3.2.5-1
ii  libasound2          1.0.25-2
ii  libavcodec53        7:0.10.3-dmo1
ii  libavformat53       7:0.10.3-dmo1
ii  libavutil51         7:0.10.3-dmo1
ii  libbz2-1.0          1.0.6-1
ii  libc6               2.13-32
ii  libcairo2           1.12.2-1
ii  libcups2            1.5.2-11
ii  libdbus-1-3         1.5.12-1
ii  libevent-2.0-5      2.0.19-stable-1
ii  libexpat1           2.1.0-1
ii  libflac8            1.2.1-6
ii  libfontconfig1      2.9.0-5
ii  libfreetype6        2.4.9-1
ii  libgcc1             1:4.7.0-8
ii  libgconf-2-4        3.2.5-1
ii  libgcrypt11         1.5.0-3
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-0        2.32.3-1
ii  libgtk2.0-0         2.24.10-1
ii  libjpeg8            8d-1
ii  libnspr4-0d         2:4.9-2
ii  libnss3-1d          3.13.4-1
ii  libpango1.0-0       1.30.0-1
ii  libpng12-0          1.2.49-1
ii  libpulse0           2.0-1
ii  libspeex1           1.2~rc1-3.1
ii  libstdc++6          4.7.0-8
ii  libudev0            175-3.1
ii  libwebp2            0.1.3-3
ii  libx11-6            2:1.4.99.901-2
ii  libxext6            2:1.3.1-2
ii  libxfixes3          1:5.0-4
ii  libxml2             2.7.8.dfsg-9
ii  libxrender1         1:0.9.7-1
ii  libxslt1.1          1.1.26-11
ii  libxss1             1:1.2.2-1
ii  xdg-utils           1.1.0~rc1+git20111210-6
ii  zlib1g              1:1.2.7.dfsg-1

chromium recommends no packages.

Versions of packages chromium suggests:
ii  chromium-l10n  18.0.1025.168~r134367-1

-- no debconf information



--- End Message ---
--- Begin Message ---
On Mon, Feb 17, 2014 at 11:21 AM, Stephen Allen wrote:
> Not experiencing this anymore with Gnome-Shell 3.8

--- End Message ---

Reply via email to