The reason I say potential is that I actually have NDI where the problem lies.
This is the main box in the house, a quad core, but slow 2.1 ghz phenom, with 4 gigs of system ram & a loaded pci & pcie bus, with a USB tree attached that resembles a weeping willow. It is running an install based on the linuxcnc install cd of ubuntu-10.04.4 LTS, running the gdm display manager, but with just enough kde pulled in that I can use kmail, and at times konversation, by no means a full kde install. I have also nuked the kmail filters that check the incoming mail for spam and viri since I do all that with a group of mail pullers, fetchmail, freshly built from the newest release, procmail, mailfilter (that I've had to write some wrapper scripts for), clamav and of course spamassassin's officers of the court. Kmail is only touched by all these by getting a signal on its dbus port telling it to go get the mail when a new msg has been written to /var/spool/mail. ATM incoming mail works great, and automatic, so once everything is started after a reboot, all I have to do is hit the + key on the numpad to read the next unread message. Description of problem: Click on one of the new or reply buttons. The composer opens normally, and I can type away but do notice that there may be a 30 second pause in all things kmail related while I am typing, so I type carefully and blindly, and eventually all of what I typed will be echoed to the screen, and if any typu's, I can correct them as normal. This pausing is one manifestation of this prolem. So eventually I have a msg or reply composed and ready to send, and click on the send button. Maybe 2% of the time, the message will be sent in less than a second, but the other 98% of the time there are huge time lags, up to 45 seconds per step, where kmail is just plain frozen, as if an interrupt has gotten lost. It will take up to 45 secs just to ack the click on the send button and draw its colored border, then another pause of up to 40-45 seconds for the composer's screen to be busy-greyed, followed by another long pause until the composer screen overlay is cleared. At that point normal speed seems to resume as a '1' will show up in the outbox a hundred milliseconds later, a burst of network activity and the 1 disappears after about 1 second, the msg having been sent. But it may be as much as a minute:30 to send a message, any message. During all this pausing and freezing, the rest of the machine is working completely normal, including x, I can move this greyed out screen with the mouse, I can switch workspaces both with the mouse and the keyboard, look at htop's display to see if anything is hogging the system (there isn't, gkrellm at maybe 3% of a core seems to be the biggest user), even the latency-test output shows the same old jitter data. It is like the kde stuff is actively being ignored by the system! The two boxes with machines on them I have never setup for mail, but I do run konversation on them with no apparent problems. Has anyone a clue where I might look? Thanks. Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: <http://coyoteden.dyndns-free.com:85/gene> is up! Computers are like air conditioners -- they stop working properly if you open WINDOWS ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
