Bug 280746 - Once kmail is opened twice (same user, different session. e.g.: Opening a remote session). Messages are not available
Summary: Once kmail is opened twice (same user, different session. e.g.: Opening a rem...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-24 22:56 UTC by Aitor
Modified: 2017-01-07 22:43 UTC (History)
0 users

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 Aitor 2011-08-24 22:56:41 UTC
Version:           4.7 (using KDE 4.7.0) 
OS:                Linux

Opening kmail twice (for example through a ssh session) render messages on kmail unavailable. The original instance is not able to access selected messages and new instances are opened with a blank folders list. The following notification is reported for every configured account(I use Spanish so I hope translation is OK):
"mail@aitorpazos.es: Unknown error. (There is no transaction in progress.)"

After restart, everything comes back to normal.

Reproducible: Always

Steps to Reproduce:
Open kmail as usual.
Log in opening a new session where we can open GUI apps (ssh with X forwarding, Remote Desktop, etc)
Launch kmail
Try to read any mail

Actual Results:  
Errors are notified and messages are not available.

Expected Results:  
Messages should be available on both kmail instances or the second kmail instance should be refused to start.
Comment 1 Denis Kurz 2016-09-24 18:02:37 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 2 Denis Kurz 2017-01-07 22:43:45 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.