Version: (using KDE 4.4.0) Installed from: openSUSE RPMs Reproducibility: Always Steps to reproduce: 1. Use Nomachine nxclient to run Kontact or KMail on a remote machine 2. Reply to a message (using the keyboard, context menu, toolbar, or Message pull-down menu). Observed results: 3. The first time step #2 is done, a composer window opens as expected. However, on second and subsequent attempts to reply to a message, no composer window appears. If you quit Kontact/KMail and restart it, the composer windows for the messages you tried to reply to then appear. Note that this bug occurs only with the Reply command. The New Message, Forward, Send As New Message, etc. commands work fine. This bug also occurs only over an NX connection. (I haven't tried FreeNX, but it does happen with Nomachine NX.)
Possibly related to Bug 190824.
In KDE 4.4.1, the behaviour of this issue appears to have changed somewhat. When using KMail directly (i.e., not through Kontact), the bug occurs as in my original report—that is, the first time Reply is used, a composer window opens; subsequent attempts fail. However, when using KMail via Kontact, the Reply command now has no effect at all—not even the first time.
Created attachment 41471 [details] Console output from kontact Attached is a log of console output from when I launch Kontact over an NX connection. At line 170 I hit the "Reply" button in the toolbar (and no composer window is displayed). At line 201 I exit Kontact. I'm not sure if there's anything useful here but I thought I'd attach it just in case. I tried looking elsewhere for any useful error messages, but nothing at all is output to /var/log/messages, /var/log/warn, ~/.xsession-errors, or ~/.nx/*/errors, either on the local or remote machines. If there is any other place I should be looking, please let me know.
Can no longer reproduce with KDE 4.5.0 and nxclient 3.4.0.
Problem is recurring for me again, with both KDE 4.5 and 4.6. But I've since discovered this bug is a duplicate of Bug 201080. *** This bug has been marked as a duplicate of bug 201080 ***