Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-05-13 Thread Ariel 


On Mon, 2 Jan 2012, Jonathan Nieder wrote:


chromium isn't available from backports.d.o.

Do you think it would make sense to add it there, and if so, would you
be willing to work on it?  What change, if any, should be made to the
standard chromium package to support that?


The main thing I had an issue with when backporting it for myself was 
the versioned dependency on libcups2-dev = 1.5.0.


Installing that from testing pulled a huge number of other packages along 
with it.


Everything else was available from backports or was just a single package 
(I believe gyp, libwebp-dev and libv8 were the only ones I needed from 
testing).


(I had the same NSS issues as everyone else, but somehow 3.13.4-1 broke 
nss for chromium and now chromium works - although for me using 
--single-process would not have been a problem.)


-Ariel



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-05-13 Thread Ariel 


On Sun, 13 May 2012, Ariel wrote:

The main thing I had an issue with when backporting it for myself was the 
versioned dependency on libcups2-dev = 1.5.0.


Installing that from testing pulled a huge number of other packages along 
with it.


Everything else was available from backports or was just a single package (I 
believe gyp, libwebp-dev and libv8 were the only ones I needed from testing).


Actually, never mind. libwebp-dev needs multiarch-support, which is only 
available in the same toolchain that comes in via libcups2-dev = 1.5.0


Maybe if someone backported a non multiarch-support libwebp-dev, but 
simply compiling it on squeeze was not enough. I guess the paths, etc are 
different. I guess I'll have to run a mixed system if I want chromium.


-Ariel



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-02-12 Thread Mark T. B. Carroll 
I found this bug because of experiencing the same failure. I use
squeeze but installed with apt-get install -t testing chromium-browser

The --single-process option corrects the problem for me.

Mark



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-06 Thread Daniel Baumann 

Michael Gilbert michael.s.gilb...@gmail.com wrote:
 Yes, I looked at a diff, but it wasn't immediately obvious which
 change would actually solve the problem.

i think we have a misunderstanding here, i never claimed to have a 
solution for the fix, rather, i reopened this bug *because* it still 
doesn't work. sorry for no better news, i'm happy to test whatever you 
want me to test though.


--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-04 Thread Daniel Baumann 
On 01/04/2012 12:44 AM, Michael Gilbert wrote:
 Which settings in particular do you know of that make the chromium
 backport work?

haven't you looked at the git repository[0]? e.g. 'git diff
debian-wheezy..progress-artax-backports' gives all the changes.

citing from changelog:

---snip---
chromium-browser (16.0.912.63~r113337-1~artax1) artax; urgency=low

  * Uploading to artax, remaining changes:
- Updating maintainer and uploaders fields.
- Updating vcs fields.
- Adding bugs field.
- Always building for debian-squeeze rather than autodetecting
  distribution, vendor and release number with lsb_release.
- Reverting use of binutils-gold to fix FTBFS.
- Reverting changes for cups (= 1.5).
- Reverting changes to use system ffmpeg.
- Reverting changes for multiarch.
- Updating chromium install file for upstreams ffmpegsumo_nolink
removal.

 -- Daniel Baumann daniel.baum...@progress-linux.org  Mon, 02 Jan 2012
07:17:39 +0100
---snap---

[0] http://vcs.progress-linux.org/?p=packages/chromium-browser.git

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-04 Thread Michael Gilbert 
On Wed, Jan 4, 2012 at 4:29 AM, Daniel Baumann wrote:
 On 01/04/2012 12:44 AM, Michael Gilbert wrote:
 Which settings in particular do you know of that make the chromium
 backport work?

 haven't you looked at the git repository[0]? e.g. 'git diff
 debian-wheezy..progress-artax-backports' gives all the changes.

Yes, I looked at a diff, but it wasn't immediately obvious which
change would actually solve the problem.  They're all rather mundane
changes each individually seemingly unlikely to fix these crashes.
Anyway, I'll take your word for it, and track down which of your
changes really fix the problem.

Best wishes,
Mike



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-03 Thread Michael Gilbert 
 What change, if any, should be made to the
 standard chromium package to support that?

 like other packages do, chromium-browser should build-depend on
 lsb-release and default automatically to certain settings depending on
 if it's build on sid or squeeze.

Which settings in particular do you know of that make the chromium
backport work?

Best wishes,
Mike



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-02 Thread Daniel Baumann 
reopen 647992
found 16.0.912.63~r113337-1
severity 647992 normal
thanks

Hi,

the issue still persists when backporting for squeeze. builds (any
version 14 till 16 is affected by it atm) can be found at:


http://archive-master.progress-linux.org/packages/backports/progress-artax-backports/chromium-browser/

git tree is at:

  http://vcs.progress-linux.org/?p=packages/chromium-browser.git

the builds are done against plain squeeze plus backports of libv8, nss,
nspr, and cairo (which is the same you would get on backports.d.o i
presume).

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-02 Thread Jonathan Nieder 
unmerge 647992
clone 647992 -1
merge -1 647994
submitter 647992 Daniel Baumann daniel.baum...@progress-technologies.net
tags 647992 = squeeze
block 647992 by 651912
retitle 647992 [squeeze-backports] chromium: unrecoverable Aw, Snap! on start up
quit

Daniel Baumann wrote:

 the issue still persists when backporting for squeeze.

Ok, we can keep a bug open for that.  I'll close the old bug with a
separate message.



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-02 Thread Jonathan Nieder 
severity 647992 wishlist
tags 647992 + moreinfo
quit

Hi again,

Daniel Baumann wrote:

 the issue still persists when backporting for squeeze.
[...]
 the builds are done against plain squeeze plus backports of libv8, nss,
 nspr, and cairo (which is the same you would get on backports.d.o i
 presume).

chromium isn't available from backports.d.o.

Do you think it would make sense to add it there, and if so, would you
be willing to work on it?  What change, if any, should be made to the
standard chromium package to support that?

Sorry for the trouble and hope that helps,
Jonathan



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2012-01-02 Thread Daniel Baumann 
On 01/02/2012 09:37 PM, Jonathan Nieder wrote:
 Do you think it would make sense to add it there

imho yes.

 would you be willing to work on it

to the extend as its relevent for the derivative, other than that, no.

however, my git tree is public, anyone can always pick from it in case
there would ever be anything interesting in the future.

 What change, if any, should be made to the
 standard chromium package to support that?

like other packages do, chromium-browser should build-depend on
lsb-release and default automatically to certain settings depending on
if it's build on sid or squeeze.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2011-11-20 Thread Jonathan Nieder 
Mattia Monga wrote:

 Chromium starts with a Aw, Snap! page and it is stuck on that. 

Still not clear what the underlying cause is (maybe libnspr is not
available in the sandboxed renderers to resolve weak references or
something like that), but here's a patch to get back to the version 14
behavior, of NSS modules not causing trouble because they are not
loaded at all.

Even with this patch, I can't reproduce the problem described at
http://bugs.debian.org/642219 (i.e., https://mail.google.com loads
fine, even with --user-data-dir=/tmp/nonexistent).

Maybe something along these lines can work as a temporary way to help
people use chromium with sandboxing until we figure the actual cause
out.

Yuck.  I'd go for something more explicit like --without-nss if it
existed.
---
 debian/patches/nss-workaround.patch |   49 +++
 debian/patches/series   |1 +
 2 files changed, 50 insertions(+), 0 deletions(-)
 create mode 100644 debian/patches/nss-workaround.patch

diff --git a/debian/patches/nss-workaround.patch 
b/debian/patches/nss-workaround.patch
new file mode 100644
index ..00c06745
--- /dev/null
+++ b/debian/patches/nss-workaround.patch
@@ -0,0 +1,47 @@
+Subject: Revert Merge 104421 - Fix library paths for preloading NSS on Ubuntu 
11.10.
+
+This backs out the change introduced by r104798, which allowed NSS to
+actually be initialized, where initialized means trip a sandboxing
+bug and take down the renderer.
+
+Works around: http://bugs.debian.org/647992
+
+--- 874/src/crypto/nss_util.cc 2011/10/10 22:14:15 104798
 874/src/crypto/nss_util.cc 2011/10/10 22:11:59 104797
+@@ -29,7 +29,6 @@
+ #include base/native_library.h
+ #include base/stringprintf.h
+ #include base/threading/thread_restrictions.h
+-#include build/build_config.h
+ #include crypto/scoped_nss_types.h
+ 
+ // USE_NSS means we use NSS for everything crypto-related.  If USE_NSS is not
+@@ -604,18 +603,9 @@
+   // Use relative path to Search PATH for the library files.
+   paths.push_back(FilePath());
+ 
++  // For Debian derivaties NSS libraries are located here.
+-  // For Debian derivatives NSS libraries are located here.
+   paths.push_back(FilePath(/usr/lib/nss));
+ 
+-  // Ubuntu 11.10 (Oneiric) places the libraries here.
+-#if defined(ARCH_CPU_X86_64)
+-  paths.push_back(FilePath(/usr/lib/x86_64-linux-gnu/nss));
+-#elif defined(ARCH_CPU_X86)
+-  paths.push_back(FilePath(/usr/lib/i386-linux-gnu/nss));
+-#elif defined(ARCH_CPU_ARMEL)
+-  paths.push_back(FilePath(/usr/lib/arm-linux-gnueabi/nss));
+-#endif
+-
+   // A list of library files to load.
+   std::vectorstd::string libs;
+   libs.push_back(libsoftokn3.so);
+@@ -638,7 +628,7 @@
+   if (loaded == libs.size()) {
+ VLOG(3)  NSS libraries loaded.;
+   } else {
++LOG(WARNING)  Failed to load NSS libraries.;
+-LOG(ERROR)  Failed to load NSS libraries.;
+   }
+ #endif
+ }
diff --git a/debian/patches/series b/debian/patches/series
index ad74c539..0f1cdaae 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -18,3 +18,4 @@ webkit-version.patch
 cups1.5.patch
 #system_v8.patch
 #protobuf.patch
+nss-workaround.patch
-- 
1.7.8.rc3




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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2011-11-08 Thread Mattia Monga 
Package: chromium
Version: 15.0.874.106~r107270-1
Severity: grave
Justification: renders package unusable

Chromium starts with a Aw, Snap! page and it is stuck on that. 

Using an empty user-data-dir doesn't help. I managed to get it working by using 
the --single-process option. Since I get a

[5720:5735:3873153110:ERROR:proxy_service_factory.cc(66)] Cannot use V8 Proxy 
resolver in single process mode.

I believe the problem is related to V8



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

Kernel: Linux 3.1.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chromium depends on:
ii  chromium-inspector  15.0.874.106~r107270-1 
ii  libasound2  1.0.24.1-4 
ii  libavcodec534:0.7.2-1+b1   
ii  libavformat53   4:0.7.2-1+b1   
ii  libavutil51 4:0.7.2-1+b1   
ii  libbz2-1.0  1.0.5-7
ii  libc6   2.13-21
ii  libcairo2   1.10.2-6.1 
ii  libcups21.5.0-10   
ii  libdbus-1-3 1.4.16-1   
ii  libdbus-glib-1-20.98-1 
ii  libevent-1.4-2  1.4.14b-stable-1   
ii  libexpat1   2.0.1-7.2  
ii  libflac81.2.1-6
ii  libfontconfig1  2.8.0-3
ii  libfreetype62.4.7-2
ii  libgcc1 1:4.6.2-4  
ii  libgconf2-4 2.32.4-1   
ii  libgcrypt11 1.5.0-3
ii  libgdk-pixbuf2.0-0  2.24.0-1   
ii  libglib2.0-02.30.1-2   
ii  libgtk2.0-0 2.24.7-1   
ii  libjpeg88c-2   
ii  libnspr4-0d 4.8.9-1
ii  libnss3-1d  3.13.1.with.ckbi.1.88-1
ii  libpango1.0-0   1.29.4-2   
ii  libpng12-0  1.2.46-3   
ii  libspeex1   1.2~rc1-1  
ii  libstdc++6  4.6.2-4
ii  libvpx0 0.9.7.p1-2 
ii  libwebp20.1.3-1
ii  libx11-62:1.4.4-2  
ii  libxext62:1.3.0-3  
ii  libxml2 2.7.8.dfsg-5   
ii  libxrender1 1:0.9.6-2  
ii  libxslt1.1  1.1.26-8   
ii  libxss1 1:1.2.1-2  
ii  xdg-utils   1.1.0~rc1-2
ii  zlib1g  1:1.2.3.4.dfsg-3   

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-l10n  none

-- no debconf information



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

Bug#647992: chromium: unrecoverable Aw, Snap! on start up

2011-11-08 Thread Jonathan Nieder 
merge 647992 648018 648035
quit

Mattia Monga wrote:

 Using an empty user-data-dir doesn't help. I managed to get it working by
 using the --single-process option.

Yep, that's inconvenient.

Backtrace: [1]

It seems that the segfault is happening somewhere within
BalloonViewHost::UpdateActualSize().

[1] 
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=gdb-chromium.txt;att=1;bug=648031



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