Bug#492488: Reproduction of the Iceweasel crashes

2008-10-29 Thread Mike Hommey
Hi again,

Thanks to Michele Baldessari, I have spotted the probable cause of the
crash. It seems somehow, the /usr/lib/xulrunner-1.9/chrome file ended up
being a directory instead of a symbolic link to
/usr/share/xulrunner-1.9/chrome.

Please all check /usr/lib/xulrunner-1.9/chrome is not a directory
and if it is a directory, try to check what packages it belongs to
with dpkg -S /usr/lib/xulrunner-1.9/chrome.

If the only output is xulrunner-1.9, it means there has been a package
creating this directory in the past, but it is not installed on your
system anymore. The fact is, /usr/lib/xulrunner-1.9/chrome has been a
symbolic link since the beginning of the xulrunner-1.9 package. And
apparently, there is no package shipping /usr/lib/xulrunner-1.9/chrome
other than xulrunner-1.9 in unstable, so any new install should be
safe.

Anyways, if /usr/lib/xulrunner-1.9/chrome is a directory on your system,
please check if it is empty.
If so, please remove it and create the missing symbolic link with
ln -s ../../share/xulrunner-1.9/chrome /usr/lib/xulrunner-1.9/chrome
If not, please send a list of files, move them to
/usr/share/xulrunner-1.9/chrome, then do the same as above.

After these operations, iceweasel should stop crashing.

Cheers,

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-29 Thread [EMAIL PROTECTED]
I removed the empty folder:
/usr/lib/xulrunner-1.9/chrome/
and made the symbolic link:
ln -s ../../share/xulrunner-1.9/chrome /usr/lib/xulrunner-1.9/chrome

and iceweasel runs!!!

I really think iceweasel should not crash this way for a missing folder but 
give an error at the console at least of the missing files.

I also think iceweasel installation should check this issue and proceed with 
your fix as I think we are not the only ones having this problem.



Ahora también puedes acceder a tu correo Terra desde el móvil.
Infórmate pinchando aquí.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-28 Thread Mike Hommey
Hi everyone,

For those still experiencing crashes at Iceweasel, can you try the
following:
- Save the contents of /usr/lib/xulrunner-1.9 and /usr/share/xulrunner-1.9
somewhere. It would be nice if you could send them to me, too, if the
rest of the procedure works.
- Purge xulrunner-1.9 (apt-get remove --purge xulrunner-1.9) ; take note
of the packages that removes.
- Remove what remains in /usr/lib/xulrunner-1.9 and /usr/share/xulrunner-1.9
- Reinstall xulrunner-1.9 and all that got removed when purging it.
- Please tell me it works.
- Send me the files you saved on the first step if it worked.

Thanks,

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-28 Thread Charles Plessy
Hi all,

just for the record, I got the list of the packages currently installed on
Michele's system, and tried to set up a similar system on a test partition:

  1) I installed a minimal amd64 system on a test partition with the latest
 Lenny installer.
  2) I converted the list he gave me into something that can be given back to
 dpkg to set a list of packages to install.
  3) I removed from the list some packages which are not in Debian (installed
 by alien?) and ran dpkg --set-selection  the_list.
  4) I then installed all the packages with apt-get dselect-upgrade
 
On the resulting system, Iceweasel was working.

It strongly corroborates the idea of Mike that the problem may be in some extra
files that are not distributed nor created in latest versions. If people
experiencing crashes want to test this at home, to better exclude the
possibility of strange hardware issue, they can use the same methodology
(provided that they have a free partition for tests). The best way to get a
list for dpkg --set-selection is to save the output of dpkg --get-selections.

Note however that if you have limited time, trying what Mike suggests in his
latest email is probably the most important.

Have a nice day,

-- 
Charles



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-27 Thread [EMAIL PROTECTED]
I have added the crash log (copiling with --enable-debug) and a bt full to show 
that it is the same bug at the forwarded upstream mozilla bug report.
Mike, your diff makes my xulrunner not compile:
/usr/bin/ld: unrecognized option '--no-relax'



Ahora también puedes acceder a tu correo Terra desde el móvil.
Infórmate pinchando aquí.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-26 Thread Mike Hommey
On Sun, Oct 26, 2008 at 12:26:52PM +1300, Michael Cree wrote:
 Charles Plessy wrote:
 I am contacting you because you reported crashes with Iceweasel. Do you still
 have this problem? If yes, are you running an up-to-date Lenny system now or
 can you upgrade? 

 Yes, the latest iceweasel (3.0.3-2) crashes on the Alpha architecture.  I 
 am running an up-to-date Lenny system.

 I've CCed this to Bob Tracy since he has done quite a bit of work trying 
 to track down the problem,, that is reported in the debian-alpha mail 
 list.  He may wish to comment further.

 Bob compiled vanilla 3.0.3 firefox sources, and I compiled 3.0.3-g1 
 icecat sources for testing (mainly because iceweasel was still back at 
 3.0.1 at the time).  These also crash.  For me the symptom is that the 
 browser window opens on the screen and then immediately disappears again 
 with the crash.

 Both Bob and I got working versions of firefox and icecat, respectively, 
 with a static link of the xul stuff, using --no-relax in the link stage, 
 and disabling optimisation.  The following messages from debian-alpha 
 mail list discussion are the most relevant.

 http://lists.debian.org/debian-alpha/2008/10/msg00022.html
 http://lists.debian.org/debian-alpha/2008/10/msg00024.html
 http://lists.debian.org/debian-alpha/2008/10/msg00028.html

Note that we *do* use --no-relax on xulrunner-1.9, but in the CFLAGS.
Without it, libxul.so won't build at all ; the same applies to webkit,
BTW.

OTOH, the crash on alpha may be unrelated to the other crash we're
trying to tackle.

Could you send a backtrace of yours ?

Cheers

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-26 Thread Bob Tracy
On Sun, Oct 26, 2008 at 12:26:52PM +1300, Michael Cree wrote:
 I've CCed this to Bob Tracy since he has done quite a bit of work trying to 
 track down the problem,, that is reported in the debian-alpha mail list.  
 He may wish to comment further.
 
 Bob compiled vanilla 3.0.3 firefox sources, and I compiled 3.0.3-g1 icecat 
 sources for testing (mainly because iceweasel was still back at 3.0.1 at 
 the time).  These also crash.  For me the symptom is that the browser 
 window opens on the screen and then immediately disappears again with the 
 crash.

That is the symptom I'm seeing as well.  Significantly, this occurs
both with Iceweasel and with firefox executables built from the
vanilla firefox-3.x sources.  The main browser window with two tabs
appears: the two tabs correspond to the you've upgraded web page and
the normal home page.  As soon as the two pages start to load, the
browser crashes with a segfault.

For a vanilla firefox-3.0.3 build, disabling optimization took care of
the segfaults, while adding -Wl,--no-relax to DSO_LDOPTS allowed
libxul.so to be built.  The build process was aborting during the final
link-edit of libxul.so with GPREL16 relocation errors, and a 2007
bugzilla report I found implicated the relax code in binutils.

The same workarounds allow firefox-3.1b1 to build and work properly.

My alpha is a PWS 433au (miata), currently running a kernel.org
2.6.27 kernel.  gcc/g++ is version 4.2.4-3, and binutils is version
2.18.0.20080103.

-- 

Bob Tracy  |  I was a beta tester for dirt.  They never did
[EMAIL PROTECTED]   |   get all the bugs out. - Steve McGrew on /.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-26 Thread Mike Hommey
On Sun, Oct 26, 2008 at 02:52:46AM -0500, Bob Tracy wrote:
 On Sun, Oct 26, 2008 at 12:26:52PM +1300, Michael Cree wrote:
  I've CCed this to Bob Tracy since he has done quite a bit of work trying to 
  track down the problem,, that is reported in the debian-alpha mail list.  
  He may wish to comment further.
  
  Bob compiled vanilla 3.0.3 firefox sources, and I compiled 3.0.3-g1 icecat 
  sources for testing (mainly because iceweasel was still back at 3.0.1 at 
  the time).  These also crash.  For me the symptom is that the browser 
  window opens on the screen and then immediately disappears again with the 
  crash.
 
 That is the symptom I'm seeing as well.  Significantly, this occurs
 both with Iceweasel and with firefox executables built from the
 vanilla firefox-3.x sources.  The main browser window with two tabs
 appears: the two tabs correspond to the you've upgraded web page and
 the normal home page.  As soon as the two pages start to load, the
 browser crashes with a segfault.
 
 For a vanilla firefox-3.0.3 build, disabling optimization took care of
 the segfaults, while adding -Wl,--no-relax to DSO_LDOPTS allowed
 libxul.so to be built.  The build process was aborting during the final
 link-edit of libxul.so with GPREL16 relocation errors, and a 2007
 bugzilla report I found implicated the relax code in binutils.
 
 The same workarounds allow firefox-3.1b1 to build and work properly.

Can you try to rebuild a xulrunner-1.9 package with the attached patch
and see if iceweasel gets better?

Thanks

Mike
diff --git a/debian/rules b/debian/rules
index 2ae4a21..6fac4e3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -34,10 +34,6 @@ ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
CONFIGURE_FLAGS += --disable-optimize
 endif
 
-ifeq ($(DEB_BUILD_ARCH),alpha)
-   CFLAGS += -Wl,--no-relax
-endif
-
 ifeq ($(DEB_BUILD_ARCH),ppc64)
CFLAGS += -mminimal-toc
 endif
@@ -90,7 +86,7 @@ build-stamp:  config.status
PYTHON_SO=$(shell objdump -p /usr/lib/lib$(PYVER).so | awk 
'/SONAME/ {print $$2}') \
$(JAVA_VARS) \
DEB_NO_JAR=1 \
-   OS_LDFLAGS=-Wl,--as-needed $(shell sed -n 
's/^OS_LDFLAGS\s*=\s*//p' config/autoconf.mk)
+   OS_LDFLAGS=-Wl,--no-relax -Wl,--as-needed $(shell sed -n 
's/^OS_LDFLAGS\s*=\s*//p' config/autoconf.mk)
#docbook-to-man debian/xulrunner.sgml  xulrunner.1
 
touch build-stamp


Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-25 Thread Charles Plessy
Dear Michele, Michael, Roberto, Nathan, Tim, Josh, and Riku.

I am contacting you because you reported crashes with Iceweasel. Do you still
have this problem? If yes, are you running an up-to-date Lenny system now or
can you upgrade? 

You probably know that other users on the same platform reported that they
could use Iceweasel with no problem. I therefore will try to look for a common
denominator to your installations.

Can you save the output of the command 'dpkg -l' on your system, send it to me
(in private if you want to preserve your privacy), and tell me if you installed
third-party software? I will actually try to reproduce the bug on fresh
installs with the same package combination.

Have a nice week-end,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-25 Thread Michael Cree

Charles Plessy wrote:

I am contacting you because you reported crashes with Iceweasel. Do you still
have this problem? If yes, are you running an up-to-date Lenny system now or
can you upgrade? 


Yes, the latest iceweasel (3.0.3-2) crashes on the Alpha architecture.  I am running an up-to-date 
Lenny system.


I've CCed this to Bob Tracy since he has done quite a bit of work trying to track down the problem,, 
that is reported in the debian-alpha mail list.  He may wish to comment further.


Bob compiled vanilla 3.0.3 firefox sources, and I compiled 3.0.3-g1 icecat sources for testing 
(mainly because iceweasel was still back at 3.0.1 at the time).  These also crash.  For me the 
symptom is that the browser window opens on the screen and then immediately disappears again with 
the crash.


Both Bob and I got working versions of firefox and icecat, respectively, with a static link of the 
xul stuff, using --no-relax in the link stage, and disabling optimisation.  The following messages 
from debian-alpha mail list discussion are the most relevant.


http://lists.debian.org/debian-alpha/2008/10/msg00022.html
http://lists.debian.org/debian-alpha/2008/10/msg00024.html
http://lists.debian.org/debian-alpha/2008/10/msg00028.html


Can you save the output of the command 'dpkg -l' on your system, send it to me
(in private if you want to preserve your privacy), and tell me if you installed
third-party software?


Yes, I have quite a lot of self-compiled software, mainly multimedia stuff, installed in /usr/local 
directories.


Cheers
Michael




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#492488: Reproduction of the Iceweasel crashes.

2008-10-25 Thread Tim Allen
On Sat, Oct 25, 2008 at 11:56:21PM +0900, Charles Plessy wrote:
 Dear Michele, Michael, Roberto, Nathan, Tim, Josh, and Riku.
 
 I am contacting you because you reported crashes with Iceweasel. Do you still
 have this problem? If yes, are you running an up-to-date Lenny system now or
 can you upgrade? 

I was having crash-on-startup issues with Iceweasel 3 on PowerPC,
especially the RC builds from Experimental. Happily, these crashes
seemed to go away about the time that Iceweasel 3 was added to Unstable.

Checking some logs, it seems that my bug was #482415 and I got it
working in message 188:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482415#188




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]