Your message dated Wed, 24 Oct 2012 08:23:06 +0200
with message-id <5087894a.2030...@iuculano.it>
and subject line Fixed
has caused the Debian Bug report #682616,
regarding chromium: Chromium keeps crashing with segfaults
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.)
--
682616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 20.0.1132.57~r145807-1
Severity: important
Dear Maintainer,
* What led up to the situation? I was browsing with Chromium as normal.
* What exactly did you do (or not do) that was effective (or
ineffective)? All crashes happened randomly.
* What was the outcome of this action? Chromium crashes with segfaults.
* What outcome did you expect instead? Not crash.
Here are the segfaults I gathered from dmesg:
[ 2419.690487] chromium[4043]: segfault at 100 ip 0000000000000100 sp
00007fff9805d758 error 14 in icon-theme.cache[7f0a5f99d000+41bb000]
[10199.843439] chromium[6900]: segfault at 64 ip 0000000000000064 sp
00007fff2d271298 error 14 in libspeexdsp.so.1.5.0[7fa88a878000+12000]
[10208.614005] chromium[10473]: segfault at 44 ip 0000000000000044 sp
00007fff17c798f8 error 14
[12644.372979] chromium[11300]: segfault at 0 ip (null) sp
00007fffe4a5d418 error 14 in SYSV00000000 (deleted)[7f40aabba000+4a8000]
[28646.980941] chromium[13056]: segfault at 55 ip 0000000000000055 sp
00007fffb82272d8 error 14 in ipag.ttf[7f4126af5000+5f3000]
[29006.979059] chromium[20435]: segfault at 45 ip 0000000000000045 sp
00007fff07b899e8 error 14 in SYSV00000000 (deleted)[7f80eb532000+4a8000]
The update came in this morning, then the floodgate opened.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 20.0.1132.57~r145807-1
ii gconf-service 3.2.5-1
ii libasound2 1.0.25-3
ii libatk1.0-0 2.4.0-2
ii libbz2-1.0 1.0.6-3
ii libc6 2.13-33
ii libcairo2 1.12.2-2
ii libcups2 1.5.3-1
ii libdbus-1-3 1.6.0-1
ii libevent-2.0-5 2.0.19-stable-3
ii libexpat1 2.1.0-1
ii libflac8 1.2.1-6
ii libfontconfig1 2.9.0-6
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.1-2
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 libgnome-keyring0 3.4.1-1
ii libgtk2.0-0 2.24.10-1
ii libjpeg8 8d-1
ii libnspr4 2:4.9.1-1
ii libnss3 2:3.13.5-1
ii libnss3-1d 2:3.13.5-1
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-1
ii libpulse0 2.0-3
ii libspeex1 1.2~rc1-6
ii libstdc++6 4.7.1-2
ii libudev0 175-3.1
ii libwebp2 0.1.3-3
ii libx11-6 2:1.5.0-1
ii libxcomposite1 1:0.4.3-2
ii libxext6 2:1.3.1-2
ii libxfixes3 1:5.0-4
ii libxml2 2.8.0+dfsg1-4
ii libxrender1 1:0.9.7-1
ii libxslt1.1 1.1.26-13
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-6
ii zlib1g 1:1.2.7.dfsg-13
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 22.0.1229.94~r161065-1
Hi,
I think this bug is fixed, feel free to reopen it if necessary.
Cheers,
Giuseppe.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
