After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673232 - [Epiphany 3.4.0.1] Epiphany ask if we want to recover last pages even if it was closed successfully using quit option from menu.
[Epiphany 3.4.0.1] Epiphany ask if we want to recover last pages even if it w...
Status: RESOLVED NOTABUG
Product: epiphany
Classification: Core
Component: General
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-31 11:33 UTC by Frederic Bezies
Modified: 2012-08-14 11:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frederic Bezies 2012-03-31 11:33:03 UTC 
Strange bug, reported for the first time in this post on archlinux forum :

https://bbs.archlinux.org/viewtopic.php?pid=1080052#p1080052

If you launch epiphany, use it for a moment, close it cleanly (using quit for unified menu), recovering options are shown on next start

Dmesg | tail said this (from original post)

"epiphany[5211]: segfault at 140 ip 00007f669f035b3c sp 00007f66942e24b0 error 4 in libc-2.15.so[7f669efff000+197000]

and/or

epiphany[5221]: segfault at 0 ip 00007fb05dbb89bf sp 00007fffdbb4a6b0 error 4 in libgobject-2.0.so.0.3000.2[7fb05dbab000+4d000]"

Did not get the same error in dmesg | tail on my computer, but I verified it without problem.

Evolution version :

[fred@fredo-arch ~]$ pacman -Qi evolution
Name                  : evolution
Version               : 3.4.0.1-1
Comment 1 Frederic Bezies 2012-03-31 15:35:59 UTC 
Sorry, I meant epiphany, not evolution :/

[fred@fredo-arch ~]$ pacman -Qi epiphany
Name                  : epiphany
Version               : 3.4.0.1-1
URL                   : http://www.gnome.org/projects/epiphany/
Licences              : GPL
Comment 2 Xan Lopez 2012-04-20 14:55:32 UTC 
Well, it seems it's segfaulting, not exiting cleanly?
Comment 3 Xan Lopez 2012-08-14 11:35:30 UTC 
As said in the last comment, it seems the browser was actually segfaulting, so this would not be a bug. Please re-open if you have more information.Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.