Keeps crashing randomly since upgrade to Hardy

Bug #229486 reported by Trouilliez vincent
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
epiphany-browser (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: epiphany-browser

I upgraded Gutsy to Hardy (well, I did a clean install actually, keeping only my /home partition intact), and now Epiphany keeps crashing.
It does so about once a day, and I haven't been able to see a pattern, it seems really random, I have no clue what triggers the crash.

I was hopping that "apport" would catch the crash(es) on the fly (isn't it meant to do just that?), but unfortunately it always fails to detect that Epiphany crashes, so I don't know how to gather debug information about the crash. Since it crashes pretty much every day in average, it should not take long before I can reproduce it.

I am willing to do whetever it takes to debug it, so please just give me instructions, and I will execute ;-)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in epiphany-browser:
status: New → Invalid
Revision history for this message
Trouilliez vincent (vincent-trouilliez-modulonet) wrote :

With all due respect, I seems you didn't even read my bug report before closing it ?! :-/

Hint: you imply that I should use Apport to file a new bug report and get debug info... but I clearly explained that in my case, Apport precisely FAILS to detect the crash, so there is no debug info to be found in /var/crash.

Changed in epiphany-browser:
status: Invalid → New
Revision history for this message
Trouilliez vincent (vincent-trouilliez-modulonet) wrote :

> If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Oh, I see, it was disabled ! ok, I enabled it and started the apport init script. Closing the bug again, waiting for apport to trigger ;-)

Quite strange that apport was disabled by default... how useful can it be to users if it's disabled ? hmmm...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

ok, thanks.

Changed in epiphany-browser:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

> how useful can it be to users if it's disabled

it's not meant to be useful to user but to give informations to get the issues fixed rather, the common crashers have already been reported before the stable is available though, and bug reports can contain private datas and slow down the system so they usually create trouble for users rather than bring value that's why they are not activated on stable

Revision history for this message
Trouilliez vincent (vincent-trouilliez-modulonet) wrote :

Ok, I understand.

One last question: I was asked to enable apport in /etc/default/apport, then "restart".

Does that mean I have to reboot the machine ? I currently have 150 files downloading on amule, so I would rather not interrupt amule until the downlaods are complete.

So instead I navigated to /etc/init.d, saw the apport script and just issued "sudo ./apport start", and it said that it successfully started.
Is it enough to be sure that apport is up and running properly, or should I really restart the machine as asked ?

Thanks for your patience ;-)

Revision history for this message
Dean Sas (dsas) wrote : Re: [Bug 229486] Re: Keeps crashing randomly since upgrade to Hardy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Trouilliez vincent wrote:
> So instead I navigated to /etc/init.d, saw the apport script and just issued "sudo ./apport start", and it said that it successfully started.
> Is it enough to be sure that apport is up and running properly, or should I really restart the machine as asked ?

You can run "kill -SIGSEGV PID" where PID is a process ID taken from "ps
- -e" to force a program to crash. That'll probably trigger apport.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIKLcweedO8dcp9nYRAm0IAJ9QtThsf7lmK/ui/8+avjBfdWdwggCfZWes
s3CIkZ+D5rVkMZ7DBoL9CMU=
=RcLv
-----END PGP SIGNATURE-----

Revision history for this message
Sebastien Bacher (seb128) wrote :

restarting apport should be enough

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.