It's not that I want any special treatmente here, it's just that I do. Every time I boot/log in, I have to suffer through these bugs:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=428 http://bugs.pearsoncomputing.net/show_bug.cgi?id=431
Bug #431 forces me to perform two checks before I can go on.
Those are bad enough, but really bad is this bug with Kmail which is forcing me to log off and log in several times a day:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=438
This has just become unacceptable. I use my computer to work, and I need to check my mail several times a day. The damn thing keeps getting jammed over and over, I have to restart my session several times a day. And this is Linux, not Windows or Mac, so restarting a session actually means closing all my currently running apps then restarting them after I log in again. They start automatically, but it takes a while for them to be ready. It's not like Windows and Mac, where we can log off, come back and everything is still there up and running just the way we left it. And I have to reconfigure my keyboard every frigging time I log in. It's driving me nuts.
Another very irritating thing is to think that I had none of these problems when I was using the 9.04 Trinity distro. How can software get WORSE? I just upgraded because... Well, pure peer pressure. Everywhere I go (forums, IRC) people keep telling me "yak yak, your OS is old as dust, upgrade already, yakety-yak". Damn, do I regret upgrading! But I just have NO TIME to go back now. I've wasted too much time already fine tuning the one I have now.
Please, for the love of humanity, get Kmail fixed stat.
Thank you for listening.
On Wed February 23 2011 10:21:59 Luciano ES wrote:
Those are bad enough, but really bad is this bug with Kmail which is forcing me to log off and log in several times a day:
What does Wireshark say that you server is sending?
I use Trinity KMail intensively with no serious problems and only one minor (tree view disappearing) problem. I also support users varying from non-technical to technical who are not experiencing any serious problems. (We use IMAP protocol exclusively so that we can efficiently access our multiple email accounts from anywhere.)
--Mike Bird
I don't have wireshark, I may install it later or tomorrow and see what it does.
Meanwhile, if you search Google, you shall see that I am most definitely not the one to have that problem. It's been spotted in the wild many times. However, I suspect that the bug was introduced in the very last version(s) of KDE3 and fixed in KDE 4 only. I remember reading the bugtrack thread, the bug was considered fixed and closed. I guess the fix didn't find its way into Trinity.
There is a workaround: after logging in, launch any other KDE3 software before launching KMail.
Inga, I don't think that kind of lucky charm will work. In fact, Kmail works fine right after I log in. The problem begins about half an hour to one hour later.
Besides, I already have Kalarm running at startup. That should be enough. What do you think?
Oh, I just had the problem again. So this time I ran Kate and Konqueror as soon as I logged in. Then I ran Kmail. 15 minutes later... boom! Here comes the Kmail bug again. Cripes... :-(
I've never used wireshark, though I'd think netstat would be enough? That spits out a list of anything currently using your network.
Do a netstat (open a terminal and type netstat) before Kmail loads (if possible), when it first loads before it starts checking mail (if possible), when it is actually checking your mail, then several times following it finishing the mail check (including as son as it finishes checking). When it fails to work, do several netstats. It may help to paste everything to a text file to look through manually, these lists can be long if you've got a lot running on your machine. Post the kmail lines, and anything else you find suspicious. Perhaps something is clogging your network when it happens, or kmail is spawning a bunch of connections and isn't closing all of them.
Also keep in mind that TDE is relatively young and very small (two devs, we really need some PR) and that the devs haven't had much of a chance to make a lot of releases. We are working on cmake porting (so we can use cmake rather than ./configure with a broken autotools) for 3.5.12, and it is a high priority for the devs to get the papercut bugs fixed, hopefully also for 3.5.13 but definitely for 3.5.14. Looks like you're a bit steamed, but there's only so much a small team can do at once, especially considering that KDE e.V. dropped KDE3 entirely.
Also may be worth it to try a different distro that supports KDE3 or TDE, I know there are builds for Debian Lenny and Squeeze, so it may be worth it to install those with no GUI, add the TDE repos, and install from there. This will take a long time (X is large, and IIRC the TDE quickbuild server has limited throughput), but having no other KDE version present will help make sure there aren't any conflicts, and if you're not going to use GNOME or LXDE, this can save some space.
I downloaded and installed wireshark. Heck if I know how to use this thing. I was referred to the manual... Holy cow, it's huge. I don't have time to read a book so I can use this application. Even their "Sample Captures" page is useless to me:
http://wiki.wireshark.org/SampleCaptures
No e-mail. No e-mail. They have samples for all types of connections ever invented by Man, some of which I've never even heard of. But no e-mail. Or maybe it's hidden under some arcane technical name, so ordinary people like me will not find it.
-
Inga Muste -
Kristopher Gamrat -
Luciano ES -
Mike Bird