Your message dated Sat, 14 Jun 2014 19:33:58 +0100
with message-id <1402770838.4701.12.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#751610: google-chrome-stable: Chrome 35 kills xfce
session on startup
has caused the Debian Bug report #751610,
regarding google-chrome-stable: Chrome 35 kills xfce session on startup
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.)
--
751610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-chrome-stable
Version: 35.0.1916.153-1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
I just updated to chrome 35 from chrome 34. After this update, starting
chrome kills my xfce session, taking down all running apps.
This isn't quite the result I expected.
google-chrome-beta 36 crashes the session too. chromium 35 also crashes the
session.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages google-chrome-stable depends on:
ii ca-certificates 20140325
ii dpkg 1.17.10
ii gconf-service 3.2.6-2
ii libasound2 1.0.27.2-4
ii libc6 2.19-1
ii libcairo2 1.12.16-2
ii libcap2 1:2.22-1.2
ii libcups2 1.7.2-3
ii libcurl3 7.37.0-1
ii libdbus-1-3 1.8.4-1
ii libexpat1 2.1.0-5
ii libfontconfig1 2.11.0-5
ii libfreetype6 2.5.2-1
ii libgcc1 1:4.9.0-6
ii libgconf-2-4 3.2.6-2
ii libgcrypt11 1.5.3-4
ii libgdk-pixbuf2.0-0 2.30.7-1
ii libglib2.0-0 2.40.0-3
ii libgtk2.0-0 2.24.23-1
ii libnspr4 2:4.10.6-1
ii libnss3 2:3.16.1-1
ii libpango1.0-0 1.36.3-1
ii libstdc++6 4.9.0-6
ii libudev0 175-7.2
ii libudev1 204-8
ii libx11-6 2:1.6.2-2
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1
ii libxdamage1 1:1.1.4-1
ii libxext6 2:1.3.2-1
ii libxfixes3 1:5.0.1-1
ii libxi6 2:1.7.2-1
ii libxrandr2 2:1.4.2-1
ii libxrender1 1:0.9.8-1
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1
ii lsb-base 4.1+Debian13
ii wget 1.15-1
ii xdg-utils 1.1.0~rc1+git20111210-7.1
google-chrome-stable recommends no packages.
google-chrome-stable suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 2014-06-14 at 14:22 -0400, Jerry Quinn wrote:
> Package: google-chrome-stable
> Version: 35.0.1916.153-1
> Severity: grave
> Justification: causes non-serious data loss
I'm afraid that google-chrome-stable isn't distributed by Debian, so
we're unable to fix issues in the package.
If you're able to reproduce your issues using Debian's chromium-browser
packages, please report a bug against the relevant version of that.
Regards,
Adam
--- End Message ---
