Bug 1293094

Summary:	last loaded pages reset
Product:	[Fedora] Fedora	Reporter:	Richard Jasmin <spike85051>
Component:	midori	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	kevin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 18:37:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Richard Jasmin 2015-12-20 06:34:00 UTC

Description of problem:
last loaded pages reset on midori. I dont know why.home page reset to fedora news feed page for some reason.

Version-Release number of selected component (if applicable):
22

How reproducible:
not yet known

Steps to Reproduce:
1.re-open midori after doing some surfing elsewhere

Actual results:
!!!

Expected results:
this should not happen, even on crash

Additional info:
I was looking up some wii and ps3 stuff last, not surfing here.

Comment 1 Kevin Fenzi 2016-01-02 21:24:02 UTC

Can you get this to happen again? Or was it a one time event?

Did it crash or did you close it as normal?

I assume you have it set to restore session on start?

Comment 2 Fedora End Of Life 2016-07-19 18:37:02 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.