Bug 298001

Summary: wallet request pops up on a different display than kmail2 is running on
Product: [Applications] kmail2 Reporter: Christopher Heiny <christopherheiny>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: carstengrohmann, kdenis
Priority: NOR    
Version: 4.8   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christopher Heiny 2012-04-12 22:00:09 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Build Identifier: 

Running kmail2 on a remote machine using SSH X11 forwarding to display on my local machine.  Remote machine was recently rebooted and KDE was running, but kmail2 had not been run on the remote machine.

Or so I thought, when I started kmail2, it complained that it was already running.  I kill -HUP'ed it, and restarted it.

It started up, but did NOT display a kwallet request on the local display nor did it show evidence of bug #297143.   Both of these are typical behaviors in when kmail2 is used of SSH X11 forwarding.

I read some emails, suffering through bug # 296563 in the process.

Eventually I composed a new email and tried to send it.  It sat in the outbox.  "Send Queued Messages" failed to help.  The message sat in the outbox.  CTL-Q and restart failed to remedy the situation.

Some hours later I visited the remote machine, and found a kwallet request displayed on that machine.  After a few seconds of WTF?!???, I typed in my kwallet password, just to see what would happen.  Nothing of interest happened on that display.

Returning to the other machine, though, I found that the pending email had finally been sent.

These would seem to be something of a security hole.

Reproducible: Sometimes
Comment 1 Carsten Grohmann 2013-10-16 16:16:59 UTC 
Hi,

I see the behaviour sometimes too. 

I use a current Debian Testing with:
Qt: 4.8.6
KDE: 4.10.5
KMail: 4.10.5

Regards,
Carsten
Comment 2 Denis Kurz 2016-09-24 18:11:41 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Christopher Heiny 2016-09-25 05:59:31 UTC 
I gave up on Kmail about a year and a half ago.  As far as I'm concerned, you can close this bug.
Comment 4 Denis Kurz 2017-01-07 23:15:20 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.