Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-19 Thread Jonathan Nieder
Fabien C. wrote: > I may be wrong here, but couldn't you use the --no-sandbox option instead? Unfortunately "chromium --no-sandbox" doesn't exhibit the problem. Vincent (or anyone else), if you send debugging patches, I can, with time, test them. Though this is not a particularly beefy laptop.

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-19 Thread Fabien C.
> In sandbox.c, I would suppress chdir(), chroot() and chdir() calls in > SpawnChrootHelper(). I would also replace MoveToNewNamespaces() by > "return true;". Running with no limit for core dumps would allow to get > a core file. Maybe this will give additional hints. I may be wrong here

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-19 Thread Vincent Bernat
OoO En ce milieu de nuit étoilée du mercredi 16 novembre 2011, vers 03:19, Jonathan Nieder disait : >> All I know is that changing the source to say >> >> if (nodb_init) { >> std::cerr << "about to call NSS_NoDB_Init(NULL)\n"; >> status = NSS_NoDB_Init(NULL); >> std::cerr << "finished NSS_N

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-15 Thread Jonathan Nieder
Jonathan Nieder wrote: > All I know is that changing the source to say > > if (nodb_init) { > std::cerr << "about to call NSS_NoDB_Init(NULL)\n"; > status = NSS_NoDB_Init(NULL); > std::cerr << "finished NSS_NoDB_Init(NULL)\n"; > > causes the "about to call" line to be

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-15 Thread Jonathan Nieder
Jonathan Nieder wrote: > All I know is that changing the source to say > > if (nodb_init) { > std::cerr << "about to call NSS_NoDB_Init(NULL)\n"; > status = NSS_NoDB_Init(NULL); > std::cerr << "finished NSS_NoDB_Init(NULL)\n"; > > causes the "about to call" line to be

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-15 Thread Jonathan Nieder
Mike Hommey wrote: > On Tue, Nov 15, 2011 at 04:36:31PM -0600, Jonathan Nieder wrote: >> Chromium (15)'s renderer processes are all dying here: >> >> NSSInitSingleton() >> : opencryptoki_module_(NULL), >>software_slot_(NULL), >>test_slot_(NULL), >>

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-15 Thread Mike Hommey
On Tue, Nov 15, 2011 at 04:36:31PM -0600, Jonathan Nieder wrote: > Hi Mike et al, > > Chromium (15)'s renderer processes are all dying here: > > NSSInitSingleton() > : opencryptoki_module_(NULL), > software_slot_(NULL), > test_slot_(NULL), > tpm

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-15 Thread Jonathan Nieder
Hi Mike et al, Chromium (15)'s renderer processes are all dying here: NSSInitSingleton() : opencryptoki_module_(NULL), software_slot_(NULL), test_slot_(NULL), tpm_slot_(NULL), root_(NULL), chromeos_user_logg

Bug#647992: chromium 14 broken with libnss3-1d from sid

2011-11-15 Thread Sebastian Reichel
Hi, I noticed, that Chromium 14 has the same problem when libnss3-1d from sid (3.13.1.with.ckbi.1.88-1) is used (at least the symptoms are the same). Installing libnss3-1d from testing (3.12.11-3) it works as expected. Chromium 15 doesn't work with either of them, though. -- Sebastian signatur