Bug 297799 - wallet manager doesn't start for password-protected page
Summary: wallet manager doesn't start for password-protected page
Status: RESOLVED DUPLICATE of bug 323663
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: Konqueror Developers
URL: https://lists.sourceforge.net/lists/a...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-09 19:43 UTC by Volker Kuhlmann
Modified: 2013-12-15 13:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Kuhlmann 2012-04-09 19:43:14 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.7.2 Safari/534.34
Build Identifier: 

For sourceforge lists with URL
https://lists.sourceforge.net/lists/admindb/<listname>
kwalletmanager doesn't start up, so no password can be stored and no password is filled in by the manager.

Reproducible: Always

Steps to Reproduce:
1. Load one of the sourceforge lists in konqueror.

Actual Results:  
Note the absence of a wallet manager asking whether to store the password or whether to fill it in.

Expected Results:  
The password is handled like it used to work in KDE 3.x.

Turning the proxy off doesn't make any difference.

I had trouble submitting this report, the system rejects it with "there is no version 1.8". Yes it's the KDE 4.7.2 one from openSUSE 12.1.
Comment 1 Volker Kuhlmann 2012-04-09 19:49:05 UTC
The submit problem comes from the package sources being listed under "hardware platforms" in the report form. I selected "openSUSE rpms", which then causes the report to be impossible to submit because the system always dies with

"There is no version named '1.8' in the 'kwalletmanager' product.
Press back"
Comment 2 Valentin Rusu 2013-09-02 21:19:42 UTC
I don't think this is a kwalletmanager issue.
Comment 3 Volker Kuhlmann 2013-09-02 22:43:44 UTC
It lookslike it is this problem: bug#323663
Comment 4 Dawit Alemayehu 2013-12-15 13:35:44 UTC

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