Paul Martin wrote:
On Tue, Jul 17, 2012 at 05:43:41PM -0500, Jonathan Nieder wrote:
Rumor has it that 3.5-rc7~10 (x86/vsyscall: allow seccomp filter in
vsyscall=emulate, 2012-07-13) fixes it. Can you confirm?
Yes, I think I can confirm the rumours. The current chromium package
On Tue, Jul 17, 2012 at 05:43:41PM -0500, Jonathan Nieder wrote:
Hi Paul,
Rumor has it that 3.5-rc7~10 (x86/vsyscall: allow seccomp filter in
vsyscall=emulate, 2012-07-13) fixes it. Can you confirm?
Yes, I think I can confirm the rumours. The current chromium package
Data point: 20.0.1132.27~r140692-2 works fine. Anything later has the
hang followed by It's dead, Jim.
Also running a 3.5 kernel here:
Linux thinkpad 3.5.0-rc6-3-g8c84bf4 #30 SMP
--
Paul Martin p...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Hi Paul,
Paul Martin wrote:
Data point: 20.0.1132.27~r140692-2 works fine. Anything later has the
hang followed by It's dead, Jim.
Also running a 3.5 kernel here:
Linux thinkpad 3.5.0-rc6-3-g8c84bf4 #30 SMP
Rumor has it that 3.5-rc7~10 (x86/vsyscall: allow seccomp filter in
severity 679827 important
thanks
Only affects chromium on linux 3.5 or greater. Wheezy will ship with
linux 3.2, so downgrading to non-rc severity.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Mike,
Michael Gilbert wrote:
severity 679827 important
thanks
Only affects chromium on linux 3.5 or greater. Wheezy will ship with
linux 3.2, so downgrading to non-rc severity.
Is this to quiet apt-listbugs in case it doesn't understand the
'experimental' tag?
Curious,
Jonathan
--
On Sat, Jul 14, 2012 at 2:16 PM, Jonathan Nieder wrote:
Hi Mike,
Michael Gilbert wrote:
severity 679827 important
thanks
Only affects chromium on linux 3.5 or greater. Wheezy will ship with
linux 3.2, so downgrading to non-rc severity.
Is this to quiet apt-listbugs in case it doesn't
tags 679827 + experimental
quit
Soeren Sonnenburg wrote:
Kernel: Linux 3.5.0-rc3-sonne+ (SMP w/2 CPU cores; PREEMPT)
holisme upstream noticed that this is the relevant variable. Ah.
One less release-critical bug for wheezy. ;-)
--
To UNSUBSCRIBE, email to
I now created a fresh new user to test this - same thing. 100% reliably
hangs on github and various other pages. Tried to disable all kinds of
gpu and related hardware accel in about:flags - no change: still
crashes.
I asked other people and for them everything was fine (intel gfx) so it
might
Which version of libcairo2 are you held at? Could you try the latest
version (1.12.2-2) and see if you can still reproduce the issue?
On Mon, Jul 2, 2012 at 3:13 AM, Soeren Sonnenburg so...@debian.org wrote:
I now created a fresh new user to test this - same thing. 100% reliably
hangs on
too bad I am already on 1.12.2-2 :/
On Mon, 2012-07-02 at 10:58 -0700, Andrew Chant wrote:
Which version of libcairo2 are you held at? Could you try the latest
version (1.12.2-2) and see if you can still reproduce the issue?
On Mon, Jul 2, 2012 at 3:13 AM, Soeren Sonnenburg so...@debian.org
Package: chromium
Version: 20.0.1132.43~r143823-1
Severity: grave
On various webpages like e.g. https://github.com chromium reproducibly
hangs since this upgrade to 20.X (same with google-chrome even from dev
channel 21.X).
This occurs with all plugins and extensions disabled and even in
Doesn't happen for me. Out of curiosity, how did you manage to install
chromium without libcairo2?
On Sun, Jul 1, 2012 at 2:30 PM, Soeren Sonnenburg so...@debian.org wrote:
Package: chromium
Version: 20.0.1132.43~r143823-1
Severity: grave
On various webpages like e.g. https://github.com
13 matches
Mail list logo
