Your message dated Mon, 2 Jan 2012 03:57:59 -0600
with message-id <20120102095759.gc10...@elie.hsd1.il.comcast.net>
and subject line Re: chromium: unrecoverable Aw, Snap! on start up
has caused the Debian Bug report #654186,
regarding No longer works since this morning's update
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 ow...@bugs.debian.org
immediately.)
--
654186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 15.0.874.106~r107270-1
Severity: grave
Hi,
Since this morning's update, starting chromium as 'chromium' or
'chromium-browser' does not as expected. Sometimes it just shows a blank
page; sometimes it shows the 'unhappy browser' blue screen. In both
cases, trying to browse to a webpage does not work.
I tried producing a backtrace, but it doesn't seem to be segfaulting or
anything; it just sits there, doing nothing.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 15.0.874.106~r107270-1
ii libasound2 1.0.24.1-4
ii libavcodec53 4:0.7.2-1+b1
ii libavformat53 4:0.7.2-1+b1
ii libavutil51 4:0.7.2-1+b1
ii libbz2-1.0 1.0.5-7
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libcups2 1.5.0-10
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.98-1
ii libevent-1.4-2 1.4.14b-stable-1
ii libexpat1 2.0.1-7.2
ii libflac8 1.2.1-6
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.7-2
ii libgcc1 1:4.6.2-4
ii libgconf2-4 2.32.4-1
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.8-1
ii libgtk2.0-0 2.24.7-1
ii libjpeg8 8c-2
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 libpng12-0 1.2.46-3
ii libspeex1 1.2~rc1-1
ii libstdc++6 4.6.2-4
ii libvpx0 0.9.7.p1-2
ii libwebp2 0.1.3-1
ii libx11-6 2:1.4.4-2
ii libxext6 2:1.3.0-3
ii libxml2 2.7.8.dfsg-5
ii libxrender1 1:0.9.6-2
ii libxslt1.1 1.1.26-8
ii libxss1 1:1.2.1-2
ii xdg-utils 1.1.0~rc1-2
ii zlib1g 1:1.2.3.4.dfsg-3
chromium recommends no packages.
Versions of packages chromium suggests:
ii chromium-l10n 15.0.874.106~r107270-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 15.0.874.121~r109964-1
severity 654186 grave
quit
Daniel Baumann wrote:
> the issue still persists when backporting for squeeze.
However, the workaround in wheezy/sid still works. The underlying bug
is tracked at <http://crbug.com/21540>.
--- End Message ---
