Bug 232617 - Fails on login message: "You have new mail."
Summary: Fails on login message: "You have new mail."
Status: RESOLVED DUPLICATE of bug 233467
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdesu bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-29 21:03 UTC by James Richard Tyrer
Modified: 2010-11-17 12:46 UTC (History)
2 users (show)

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

Attachments
Patch to fix my specific problem (730 bytes, patch)
2010-03-29 21:10 UTC, James Richard Tyrer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description James Richard Tyrer 2010-03-29 21:03:13 UTC 
Version:            (using KDE 4.4.1)
Compiler:          GCC 4.3.3 
OS:                Linux
Installed from:    Compiled From Sources

The problem appears to be in KDELibs.

When I supply the correct password, It still responds that I have entered the wrong password.

The problem appears to be caused by the login message:

You have new mail.
Comment 1 James Richard Tyrer 2010-03-29 21:10:24 UTC 
Created attachment 42357 [details]
Patch to fix my specific problem

This patch will fix my specific problem.  If there are others, either the if statement will need to have other cases added or it can be replaced with a case where the default action is: "return notauthorized;" and the others simply: "break;".  Failure should be the default -- otherwise there could be security issues.
Comment 2 Oswald Buddenhagen 2010-03-29 22:14:12 UTC 

*** This bug has been marked as a duplicate of bug 183671 ***
Comment 3 James Richard Tyrer 2010-11-06 10:06:02 UTC 
Since this is not really the same bug as 183671, I have reopened it.

I note that this bug and 183671 are both subsets of bug 233467.

There is a patch for the problem which I have reported and there is a patch for 183671.  However, these two patches don't appear to work the same way, so they should be modified to use the same method.
Comment 4 Oswald Buddenhagen 2010-11-06 10:20:28 UTC 
james, you are doing it again. just accept my friggin' conclusion, hmmkay?

*** This bug has been marked as a duplicate of bug 183671 ***
Comment 5 James Richard Tyrer 2010-11-06 11:27:42 UTC 
Since this is not really the same bug as 183671, I have reopened it.

I note that this bug and 183671 are both subsets of bug 233467.

There is a patch for the problem which I have reported and there is a patch for 183671.  However, these two patches don't appear to work the same way, so they should be modified to use the same method.

Please see Bug 233467 for new patch which should also fix Bug 183671.
Comment 6 Oswald Buddenhagen 2010-11-06 11:31:09 UTC 
you simply don't get it, huh?

*** This bug has been marked as a duplicate of bug 183671 ***
Comment 7 James Richard Tyrer 2010-11-06 12:04:10 UTC 
(In reply to comment #6)
> you simply don't get it, huh?
> 
> *** This bug has been marked as a duplicate of bug 183671 ***

Did your read the notes to this bug, and the other two bugs?  Did you look at the patch.  Are you interested in fixing bug, or do you have some other agenda?

Might I suggest that you simply don't get it.  When you close a bug that has a patch without committing the patch, what do you think will happen?  When your mark a bug as a duplicate of a bug that it isn't really a duplicate, or subset, of, what do you think will happen?

IAC, the patch for both this bug and Bug 183671 is posted to Bug 233467.  I you want o fix bugs, perhaps you might want to consider committing it.

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