Firefox crash every time I go to http://www.howtoforge.com/editing_pdf_files_pdfedit_ubuntu_feisty (Hardy)

[Paul Dufresne]

Binary package hint: firefox

Every time I try to go to:
http://www.howtoforge.com/editing_pdf_files_pdfedit_ubuntu_feisty
Firefox crash.

Apport is not launched automatically, and if I go to /var/crash/ there is a crash on Firefox bug with a lock.
Clicking on the crash file result in 'This problem report is damaged and cannot be processed.'.
Maybe it need to reboot before sending it, not sure.

I am using 'ubuntu-bug' to report this, hoping that at least firefox version will be included in the report.

ProblemType: Bug
Architecture: i386
Date: Sat Dec 15 13:54:34 2007
DistroRelease: Ubuntu 8.04
Uname: Linux paul-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Paul Dufresne (paulduf)]

Hum, not so usefull.
paul@paul-desktop:~$ dpkg -l | grep firefox
ii firefox 2.0.0.10+2nobinonly-0ubuntu2 lightweight web browser based on Mozilla
ii firefox-gnome-support 2.0.0.10+2nobinonly-0ubuntu2 Support for Gnome in Mozilla Firefox
ii mozilla-firefox-locale-en-gb 2.0.0.7+1-0ubuntu2 Mozilla Firefox English language/region pack
ii mozilla-firefox-locale-fr-fr 2.0.0.7+1-0ubuntu2 Mozilla Firefox French language/region packa
ii ubufox 0.4~beta1-0ubuntu4 modifications for ubuntu firefox (default) i
paul@paul-desktop:~$

My .xsession-errors contains:
The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 22978 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
hum, would it only be that I miss some memory?
paul@paul-desktop:~$ cat /proc/meminfo
MemTotal: 1027120 kB
MemFree: 42440 kB
Buffers: 100184 kB
Cached: 538524 kB
SwapCached: 0 kB
Active: 619580 kB
Inactive: 269888 kB
HighTotal: 122432 kB
HighFree: 224 kB
LowTotal: 904688 kB
LowFree: 42216 kB
SwapTotal: 514040 kB
SwapFree: 514040 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 250760 kB
Mapped: 90248 kB
Slab: 50360 kB
SReclaimable: 38220 kB
SUnreclaim: 12140 kB
PageTables: 2464 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 1027600 kB
Committed_AS: 719632 kB
VmallocTotal: 114680 kB
VmallocUsed: 4500 kB
VmallocChunk: 110008 kB
paul@paul-desktop:~$

[Alexander Sack (asac)]

Hi,

please submit the crash report by (double) clicking on it (e.g. using gnome file manager). Otherwise, we won't be able to process it efficiently. The .crash files can be found in the /var/crash directory.

Thanks,
 - Alexander

[Paul Dufresne (paulduf)]

2007/12/28, Alexander Sack <email address hidden>:
> Hi,
>
> please submit the crash report by (double) clicking on it (e.g. using
> gnome file manager).
Like I said, double-clicking the report result in a message: "This problem report is damaged and cannot be processed.", making it quite useless.

Have you tried the link yourself? If it crash for you too, then you don't need MY crash report.

Well, I am attaching the crash report anyway, as it is small: 37kB.
There was no rights on the file, have to give myself +r before uploading.
paul@Arcturus:/var/crash$ ls -l
total 148
-rw------- 1 root root 24308 Dec 26 05:43 _usr_bin_displayconfig-gtk.0.crash
---------- 1 paul paul 37630 Dec 28 15:00 _usr_lib_firefox_firefox-bin.1000.crash
-rw------- 1 root root 24118 Dec 24 13:57 ghc6-libsrc.0.crash
-rw------- 1 root root 53712 Dec 28 06:06 sun-java5-bin.0.crash

[Paul Dufresne (paulduf)]

BTW, after making the crash file +rw, I still get an error while double-clicking it after having closed all programs to free as much memory as possible:
"Sorry, the program 'firefox-bin' closed unexpectedly

Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers."

[Alexander Sack (asac)]

On Sat, Dec 29, 2007 at 03:55:24AM -0000, Paul Dufresne wrote:
> 2007/12/28, Alexander Sack <email address hidden>:
> > Hi,
> >
> > please submit the crash report by (double) clicking on it (e.g. using
> > gnome file manager).
> Like I said, double-clicking the report result in a message: "This problem report is damaged and cannot be processed.", making it quite useless.
>
> Have you tried the link yourself? If it crash for you too, then you
> don't need MY crash report.

It doesn't crash for me. Try to remove the .crash file and see if the
next crash creates a better one.

 status incomplete

Thanks,

 - Alexander

[Felipe Venegas (fvenegas)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!