Bug 201080 - The composer window does not appear when running KMail from an NX xterm session
Summary: The composer window does not appear when running KMail from an NX xterm session
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: composer (show other bugs)
Version: 1.12.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 226527 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-22 09:57 UTC by Diederik van der Boor
Modified: 2016-09-10 18:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diederik van der Boor 2009-07-22 09:57:40 UTC
Version:           1.12.0 (using 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) "release 142", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.20-0.4-default

I'm using "xterm" as desktop choice, to prevent loading a whole desktop, and integrate the remote apps with my local ones.

When I'm trying to open a compose window (forward/reply to a message), the compose window does not appear at all.

After logging in to my normal desktop, all the compose windows I tried to open are restored too.
Comment 1 Diederik van der Boor 2009-07-22 09:59:12 UTC
Note for the "xterm" thing: I'm referring to an NX session, with the settings:
"Desktop: UNIX" -> Custom -> "Run the console".
Comment 2 Tristan Miller 2011-03-10 17:46:44 UTC
*** Bug 226527 has been marked as a duplicate of this bug. ***
Comment 3 Tristan Miller 2011-03-10 17:59:11 UTC
I've been experiencing this problem off and on (mostly on) for over a year.  I've tried everything I can think of to determine the cause, but it's a bit difficult since it can't always be reproduced.  I suspect it may be a problem on the local environment (i.e., the one running the NX client, not the one running kmail).  I am able to reproduce the problem fairly consistently on my main account running KDE 4.6.  When I log in with a different windowing environment (for example, IceWM), the problem does not occur.  I also tried creating a completely new user account and logging in with KDE 4.6; the problem did not occur then.  So I went back to my normal account and deleted everything in /tmp and almost every dot file and dot directory in my home directory (~/.kde4, ~/.config, ~/.local, ~/.nx, etc.).  In ~/.kde4 I kept only the application and configuration files for ktorrent, krdc, kopete, konsole, amarok.  Even with this nearly-pristine home directory, the problem occurred.  I also tried logging into KDE 4.6 and then replacing the running kwin window manager with IceWM, but that didn't fix the problem.

Diederick, if there's anything you've done since filing this bug report which has narrowed down the cause of the problem, or has solved it, please post that information here.
Comment 4 Tristan Miller 2012-10-17 08:19:20 UTC
Confirming problem still occurs with KDE 4.9.2.  Some additional observations:

* I'm pretty sure this bug is specific to KDE on the host environment.  I am not able to reproduce it when using GNOME 2 or IceWM.

* The problem occurs only when certain windows are opened with certain actions.  The original bug report noted that the composer window fails to open when "Reply" or "Forward" is used.  I can reproduce this behaviour.  However, the composer window always appears for me when I use "New Message".  Some other windows also fail to appear, such as Settings->Configure KMail…->Accounts->Receiving->Modify….

Could a developer indicate whether there's any difference in how the composer window is launched between the Reply/Forward commands and the New Message command?  Perhaps different windowing API calls are used, and one of them works whereas the other doesn't.
Comment 5 Tristan Miller 2013-02-07 09:20:02 UTC
I can confirm the problem still occurs with a client running KDE 4.9.5.  I can also confirm that this problem happens with at least the following NX client/server packages:

* NoMachine NX
* x2go

There are a couple others (NeatX and FreeNX) which I haven't tested yet.
Comment 6 Laurent Montel 2015-04-12 10:15:34 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.
Comment 7 Tristan Miller 2016-08-30 08:49:53 UTC
I can confirm that the problem still occurs with KMail 4.14.10.  Please reopen and reassign this bug.
Comment 8 Christophe Marin 2016-09-10 18:37:33 UTC
(In reply to Tristan Miller from comment #7)
> I can confirm that the problem still occurs with KMail 4.14.10.  Please
> reopen and reassign this bug.

why ? KMail 4.14.10 is dead since years.