Summary: | kmail2 message list difficulties over SSH X11 forwarding | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Christopher Heiny <christopherheiny> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | kdenis, kollix |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christopher Heiny
2012-03-22 16:18:06 UTC
pop or imap account ? Still problems with current 4.10.0 ? I don't think it has anything to do with ssh/X11. Try also locally to see if I'm correct. Pop accounts. I haven't tried imap. I'm currently up to 4.8.5, and still seeing this issue. I will look into a 4.10 update, probably later this coming week. I use kmail2 locally on the laptop on a daily basis, and do not experienced this issue in that contect. It only ever happens when using X11 forwarding. When you use X11 forwarding, you are looking onto that same Laptop where everything works ? Or are you looking onto a completely different PC, where also the setup/akonadi database might be different ? It is exactly the same laptop. Same user. Same hard drive. Same home directory. The only difference in operation is that it's X11 forwarding over an SSH connection. kmail2 actually has a number of problems that (for me at least) show up exclusively in the X11 over SSH situations. See for example Bug #297143 and Bug #298001. There are several others that are exacerbated by X11, but I haven't kept close enought track to notice whether they're exclusive to the X11 forwarding scenario. For example, see Bug #296567 and Bug #302277. Switching from X11 to local and then back to X11 seems to make everything much worse, particularly if I move the machine from wired to wireless for local display, and then back to the original wired subnet again. 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. I gave up on Kmail about a year and a half ago. As far as I'm concerned, you can close this bug. 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. |