Bug#612945: Chromium browser not using system timezone

2011-06-17 Thread Jonathan Nieder 
# not fixed yet
tags 612945 = upstream
forwarded 612945 http://crbug.com/17535
merge 612945 628602
quit

Hi,

Jérémy Lal wrote:

 Actually this is :
 http://code.google.com/p/chromium/issues/detail?id=16800
 
 chromium-browser --no-sandbox
 works
 chromium-browser
 does not

Thanks, Jérémy.  More precisely, it looks like
http://crbug.com/17535



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#612945: Chromium browser not using system timezone

2011-02-22 Thread Jérémy Lal 
On 22/02/2011 03:10, Felipe Sateler wrote:
 Package: libv8
 Severity: normal
 
 I'm not sure this is actually a bug in libv8 but in how node and
 chromium call it. Copying the v8 example code (attached) and running it
 produces the desired output.

Your test shows it works here too.
I'm not sure either, because now i can't reproduce it with those combinations :
nodejs-0.2.6-4 with libv8-2.5.9.15-1 or libv8-2.5.9.15-2
nodejs-0.4.0 with libv8-3.0.12.9 (unreleased)

i don't get how i reproduced it in the first place :[

but i can reproduce with both libv8-2.5.9.15-1 or libv8-2.5.9.15-2
and chromium-browser 9.0.597.98~r74359-1

Jérémy.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#612945: Chromium browser not using system timezone

2011-02-22 Thread Jérémy Lal 
chromium-browser 9.0.576.0~r65344-1 is not affected.

Actually this is :
http://code.google.com/p/chromium/issues/detail?id=16800

chromium-browser --no-sandbox
works
chromium-browser
does not

reassigning to chromium-browser...

Jérémy



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#612945: Chromium browser not using system timezone

2011-02-21 Thread Felipe Sateler 
Package: libv8
Severity: normal

I'm not sure this is actually a bug in libv8 but in how node and
chromium call it. Copying the v8 example code (attached) and running it
produces the desired output.

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

Kernel: Linux 2.6.37-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
#include 
#include 

using namespace v8;

int main() {
 // Create a stack-allocated handle scope.
  HandleScope handle_scope;

  // Create a new context.
  Persistent context = Context::New();
  
  // Enter the created context for compiling and
  // running the hello world script. 
  Context::Scope context_scope(context);

  // Create a string containing the _javascript_ source code.
  Handle source = String::New("(new Date()).getTimezoneOffset()");

  // Compile the source code.
  Handle> script = Script::Compile(source);
  
  // Run the script to get the result.
  Handle result = script->Run();
  
  // Dispose the persistent context.
  context.Dispose();

  // Convert the result to an ASCII string and print it.
  String::AsciiValue ascii(result);
  printf("%s\n", *ascii);
  return 0;
}