Bug 46705 - Program is hanging when sending E-Mail
Summary: Program is hanging when sending E-Mail
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-20 20:18 UTC by Wolfgang Arhelger
Modified: 2007-09-14 12:17 UTC (History)
0 users

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 Wolfgang Arhelger 2002-08-20 20:05:13 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kmail
Version:           1.4 (using KDE 3.0.0 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.18-4GB
OS/Compiler notes: 

When I want to send an e-mail from post-exit folder (Postausgang in German) the program is completly hanging up and I have to kill it from  xterm. My experince is that this effect does not occur when I first fetch mail from the provider and afterwards sending the mails from the post exit folder.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Ingo Klöcker 2002-08-20 21:02:30 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 20 August 2002 22:05 wolfgang.arhelger@arcor.de wrote:
> When I want to send an e-mail from post-exit folder (Postausgang in
> German) the program is completly hanging up and I have to kill it
> from  xterm. My experince is that this effect does not occur when I
> first fetch mail from the provider and afterwards sending the mails
> from the post exit folder.

Well the mail server of Arcor doesn't accept messages unless you have=20
first checked for new mail. This is called "SMTP after POP". Therefore=20
you always have to check for new mail first and only then send the=20
messages from your Postausgang.

Does KMail really hang when you try to send messages before having=20
checked for new mail? Maybe it's just waiting for a response from the=20
server.

Regards
Ingo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Yq5mGnR+RTDgudgRAsItAJ9C8M6Y9riytFBfgAAnfbPgyRkFEACgn8jm
dFAeaJIN9a4WjvwGxLZJ11A=3D
=3Div90
-----END PGP SIGNATURE-----
Comment 2 Wolfgang Arhelger 2002-08-21 20:18:04 UTC
Am Dienstag 20. August 2002 23:02 schrieb Ingo Kl=F6cker:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 20 August 2002 22:05 wolfgang.arhelger@arcor.de wrote:
> > When I want to send an e-mail from post-exit folder (Postausgang in
> > German) the program is completly hanging up and I have to kill it
> > from  xterm. My experince is that this effect does not occur when I
> > first fetch mail from the provider and afterwards sending the mails
> > from the post exit folder.
>
> Well the mail server of Arcor doesn't accept messages unless you have
> first checked for new mail. This is called "SMTP after POP". Therefore
> you always have to check for new mail first and only then send the
> messages from your Postausgang.
>
> Does KMail really hang when you try to send messages before having
> checked for new mail? Maybe it's just waiting for a response from the
> server.
>
> Regards
> Ingo
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE9Yq5mGnR+RTDgudgRAsItAJ9C8M6Y9riytFBfgAAnfbPgyRkFEACgn8jm
> dFAeaJIN9a4WjvwGxLZJ11A=3D
> =3Div90
> -----END PGP SIGNATURE-----
>
>
> (Complete bug history is available at http://bugs.kde.org/db/46/46705.htm=
l)

Hello Ingo

thanks very mauch for the immediate reply (one more reason for using the KD=
E).

KMail seems to be quit dead  if I check for new mail as first action. If I=
=20
move the windowframe the window itself does not follow. I either can't lea=
ve=20
through the front door (Function "Beenden" or=20
Strg+Q). For my personal needs your information is helpful and sufficent. B=
ut=20
this might be a problem for a new users to chose this programm as their=20
favorite mail-client. If I can give you any further Information please let=
 me=20
know.

greetings=20

Wolfgang

--=20
Wolfgang Arhelger
Graf Stauffenbergstr. 26
55232 Alzey
Tel.: 06731/943472
FAX : 069/1330 4600 843
Datum WGS 84
N 49=B044327'
E 08=B005773'
E-Mail: wolfgang.arhelger@arcor.de
----------------------------------
Comment 3 Unknown 2002-09-16 17:20:15 UTC
Do you get any information from the crash manager that appears, if you do a 
"killall -6 kmail" when it hangs? 
Comment 4 Unknown 2002-09-16 22:13:39 UTC
Subject: Re:  Program is hanging when sending E-Mail

the information of the crash manager is saved in the attached file 
"kmail.debug". What I did to get this message was. Put a mail in the post 
exit. After sending the mail (without getting mail from the pop server) the 
program froze its window and stopped.

Then I terminated the programm with killall - 6 kmail.

greetings

Wolfgang Arhelger



Am Montag, 16. September 2002 17:20 schrieben Sie:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=46705
>
>
>
>
> ------- Additional Comments From haeckel@kde.org  2002-09-16 17:20 -------
> Do you get any information from the crash manager that appears, if you do a
> "killall -6 kmail" when it hangs?

-- 
Wolfgang Arhelger
Graf Stauffenbergstr. 26
55232 Alzey
Tel.: 06731/943472
FAX : 069/1330 4600 843
Datum WGS 84
N 49
Comment 5 Unknown 2002-09-17 07:38:19 UTC
Subject: Re:  Program is hanging when sending E-Mail

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 16 September 2002 22:13, wolfgang.arhelger@arcor.de wrote:
>
> the information of the crash manager is saved in the attached file
> "kmail.debug". What I did to get this message was. Put a mail in the post
> exit. After sending the mail (without getting mail from the pop server) the
> program froze its window and stopped.
>
> Then I terminated the programm with killall - 6 kmail.

Thanks. Looks like there is a problem with the proxy auto configuration which 
actually shouldn't deal with SMTP at all.

Could you please configure your proxy servers manually in KControl or disable 
them, try it that helps and send me the script you use for auto 
configuration?

Regards,
Michael H
Comment 6 Wolfgang Arhelger 2002-09-17 21:59:18 UTC
Subject: Re:  Program is hanging when sending E-Mail

Hello Michael,

you are right. I switched off and on the proxyserver in the KDE controlcenter. 
Kmail worked without any hanging up when the proxy was switched of. When I 
switched it on, the mentioned bug occured again. 

The proxy runs with the option "automatically generated script". Unfortunatly 
I dont know how this script is called, so I don't know where to find it.

greetings 

Wolfgang

Am Dienstag, 17. September 2002 07:38 schrieben Sie:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=46705
>
>
>
>
> ------- Additional Comments From haeckel@kde.org  2002-09-17 07:38 -------
> Subject: Re:  Program is hanging when sending E-Mail
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Monday 16 September 2002 22:13, wolfgang.arhelger@arcor.de wrote:
> > the information of the crash manager is saved in the attached file
> > "kmail.debug". What I did to get this message was. Put a mail in the post
> > exit. After sending the mail (without getting mail from the pop server)
> > the program froze its window and stopped.
> >
> > Then I terminated the programm with killall - 6 kmail.
>
> Thanks. Looks like there is a problem with the proxy auto configuration
> which actually shouldn't deal with SMTP at all.
>
> Could you please configure your proxy servers manually in KControl or
> disable them, try it that helps and send me the script you use for auto
> configuration?
>
> Regards,
> Michael H
Comment 7 joerg 2002-11-24 03:17:05 UTC
kmail craches immediately whenn clicking on "sending": happened first after the 
new update from sue, germany 2 days ago.  (no debugging symbols found)...(no 
debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...[New Thread 1024 (LWP 14409)] 
(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
0x41347099 in wait4 () from /lib/libc.so.6 
#0  0x41347099 in wait4 () from /lib/libc.so.6 
#1  0x413c1bd8 in __DTOR_END__ () from /lib/libc.so.6 
#2  0x4121f072 in waitpid () from /lib/libpthread.so.0 
#3  0x40a2f0de in KCrash::defaultCrashHandler () 
   from /opt/kde3/lib/libkdecore.so.4 
#4  0x4121ca74 in pthread_sighandler () from /lib/libpthread.so.0 
#5  <signal handler called> 
#6  0x080df02b in KDialog::marginHint () 
#7  0x410c22fc in QMotifStyle virtual table () from /usr/lib/libqt-mt.so.3 
#8  0x40d54784 in QWidget::~QWidget () from /usr/lib/libqt-mt.so.3 
#9  0x40d54784 in QWidget::~QWidget () from /usr/lib/libqt-mt.so.3 
#10 0x40ddc055 in QMainWindow::~QMainWindow () from /usr/lib/libqt-mt.so.3 
#11 0x40874c7c in KMainWindow::~KMainWindow () from /opt/kde3/lib/libkdeui.so.4 
#12 0x0812bd6b in KDialog::marginHint () 
#13 0x080cda9d in KDialog::marginHint () 
#14 0x40d2e5e2 in QObject::event () from /usr/lib/libqt-mt.so.3 
#15 0x40d593f4 in QWidget::event () from /usr/lib/libqt-mt.so.3 
#16 0x40ddd7c0 in QMainWindow::event () from /usr/lib/libqt-mt.so.3 
#17 0x080cdcfe in KDialog::marginHint () 
#18 0x40cf0ed6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 
#19 0x40cf0d74 in QApplication::notify () from /usr/lib/libqt-mt.so.3 
#20 0x409a7a55 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 
#21 0x40cf17a3 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 
#22 0x40cf164a in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 
#23 0x40c98b13 in QApplication::processNextEvent () from /usr/lib/libqt-mt.so.3 
#24 0x40cf2385 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 
#25 0x40c98a56 in QApplication::exec () from /usr/lib/libqt-mt.so.3 
#26 0x08151871 in KDialog::marginHint () 
#27 0x412bc9ed in __libc_start_main () from /lib/libc.so.6 
 
 
 
Comment 8 Carsten Burghardt 2002-11-24 12:15:43 UTC
This is unrelated to this bug, anyway, please update from the original (full) rpm from the 
suse ftp-server.