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 580835 - Loggin difficulties when I don't allow epiphany to save my username and password
Loggin difficulties when I don't allow epiphany to save my username and password
Status: RESOLVED DUPLICATE of bug 679909
Product: epiphany
Classification: Core
Component: General
2.26.x
Other All
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-30 05:57 UTC by Jesse Nelson
Modified: 2012-10-07 16:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Jesse Nelson 2009-04-30 05:57:16 UTC
Please describe the problem:
When attempting to log into the Linux Mint sofware portal I was unable to proceed unless I chose to save my password.  When ever I chose the "Not Now" option, my loggin would fail and my username would be changed.  When I finally agreed to let epiphany save my password I was able to log in.  I think its because I had saved an incorrect username before.

Steps to reproduce:
1. Go to the Linux Mint software portal.  http://linuxmint.com/software/   and create an account.
2. Enter the wrong username and try to log in saving your password by chosing "Remember"
3. Enter the correct Username and password and try to log on with chosing "Not Now"
3. Try to log on by allowing your password to be saved.



Actual results:
You should fail to be able to login when using your correct username and password unless you allow epiphany to save it.

Expected results:
You should not need to save your username and password to log on if you don't want to.  But if you have entered an incorrect username and password you may have to.

Does this happen every time?
I don't know

Other information:
Comment 1 Jean-François Fortin Tam 2012-10-07 16:12:22 UTC

*** This bug has been marked as a duplicate of bug 679909 ***