Bug 79660

Summary:	When restarted, KGET asks for user/pass for downloads even though it already has them (holding up the entire download list)
Product:	[Applications] kget	Reporter:	Jose Hernandez <code>
Component:	general	Assignee:	KGet authors <kget>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	geert.poels, mat69
Priority:	NOR	Keywords:	triaged
Version:	2.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jose Hernandez 2004-04-14 22:41:35 UTC

Version:           v0.8.3 (using KDE 3.2.90 (CVS >= 20040117), compiled sources)
Compiler:          gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)
OS:          Linux (i686) release 2.4.20-gentoo-r6

I have added many downloads in queue that are from different password sites. After restarting KGET and going through the download list, for each site, it asks the password of that site if it hasn't already, and pre-fills the USERNAME/PASSWORD areas. The effect is that queue downloading does not work if I am  not here to click the 'Ok" button every time.

Bug: There should be no dialog for password sites at all if kget already has the username/password.

Comment 1 Andrew Schulman 2005-03-11 11:58:40 UTC

Here's a variation of this bug:  when I download multiple files from the same site, kget generally doesn't cache the user/pass but asks me to reconfirm them for each file.  (I say "generally" because I'm not sure if this always happens-- I think kget doesn't prompt me again if I've already reconfirmed within the last minute or so?  Not sure.)  As in the original report, the form is prefilled with the user & pass, which is good.  But I still have to be there to click OK, making automated downloads impossible.

Comment 2 Matthias Fuchs 2010-07-10 18:09:12 UTC

*** Bug 186133 has been marked as a duplicate of this bug. ***

Comment 3 Matthias Fuchs 2011-08-09 11:16:12 UTC

Note to myself: Try with local ftp server

Comment 4 Myriam Schweingruber 2012-06-21 19:53:50 UTC

This was last reported against version 2.2.0. Is this still valid with version 2.8.0 or later?

Comment 5 Andrew Crouthamel 2018-09-23 02:32:20 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Andrew Crouthamel 2018-10-27 04:19:28 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!