On Friday 20 July 2001 13:34 rb@blumenstrasse.vol.at wrote:
> Package: kmail
> Version: unknown (using KDE 2.2.0 beta1)
> Severity: normal
> Installed from:    compiled sources
> Compiler:          gcc version 2.95.2 19991024 (release)
> OS:                Linux (i686) release 2.4.5
> OS/Compiler notes:
>
> Sometimes kmail crashes when I send a mail.
> 3 or 4 weeks ago it started to crash randomly on sending
> mails.

Sending is now non-blocking. When the sending is in 
progress do you actively used KMail? eg do you read mail in 
a mainwindow while the small sending mail dialog is shown.

Don.

[...]
> > Sometimes kmail crashes when I send a mail.
> > 3 or 4 weeks ago it started to crash randomly on sending
> > mails.
>
> Sending is now non-blocking. When the sending is in
> progress do you actively used KMail? eg do you read mail in
> a mainwindow while the small sending mail dialog is shown.
>
> Don.
Hello!

No I was just sitting there and hoping that kmail doesn't crash ;-).
The last time it happend was 20 minutes ago when I sent additional 
informations to a bugreport (with just a few lines in the message-body).

richard

On Friday 20 July 2001 14:08 Richard Brunner wrote:
> [...]
>
> > > Sometimes kmail crashes when I send a mail.
> > > 3 or 4 weeks ago it started to crash randomly on
> > > sending mails.
> >
> > Sending is now non-blocking. When the sending is in
> > progress do you actively used KMail? eg do you read
> > mail in a mainwindow while the small sending mail
> > dialog is shown.
> >
> > Don.
>
> Hello!
>
> No I was just sitting there and hoping that kmail
> doesn't crash ;-). The last time it happend was 20
> minutes ago when I sent additional informations to a
> bugreport (with just a few lines in the message-body).

So it happens often? Do you get the some backtrace every 
time?

Don.

[...]
> > Hello!
> >
> > No I was just sitting there and hoping that kmail
> > doesn't crash ;-). The last time it happend was 20
> > minutes ago when I sent additional informations to a
> > bugreport (with just a few lines in the message-body).
>
> So it happens often? Do you get the some backtrace every
> time?
>
> Don.
Hello!

It happens around one or two times a day.
I think that I get the same backtrace every time but I am not absolutely s
sure.
Now I start to send some mails and when I get the next crash I'll send the 
backtrace to you.

richard

(no debugging symbols found)...(no debugging symbols found)... 
0x411bd5a9 in __wait4 () from /lib/libc.so.6   
#0  0x411bd5a9 in __wait4 () from /lib/libc.so.6  
#1  0x41225ad8 in __DTOR_END__ () from /lib/libc.so.6  
#2  0x4098e295 in KCrash::defaultCrashHandler ()
   from /opt/kde/lib/libkdecore.so.3
#3  <signal handler called>
#4  0x41144bc1 in __kill () from /lib/libc.so.6
#5  0x411449c5 in raise () from /lib/libc.so.6
#6  0x41145fe1 in abort () from /lib/libc.so.6
#7  0x410d5ec8 in __default_terminate () from 
/usr/lib/libstdc++-libc6.2-2.so.3   
#8  0x410d5eed in __terminate () from /usr/lib/libstdc++-libc6.2-2.so.3   
#9  0x4031d6bb in __pure_virtual () from /opt/kde/lib/libkparts.so.1
#10 0x8100a8d in KMReaderWin::updateReaderWin ()
#11 0x40c4b50d in QObject::activate_signal ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#12 0x40ca0716 in QTimer::timeout ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#13 0x40c82bdf in QTimer::event ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#14 0x40bf8c16 in QApplication::notify ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#15 0x408f2c46 in KApplication::notify () from /opt/kde/lib/libkdecore.so.3
#16 0x40bc74dd in qt_activate_timers ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#17 0x40bc53a9 in QApplication::processNextEvent ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#18 0x40bfaa0f in QApplication::enter_loop ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#19 0x40bc4ccb in QApplication::exec ()
   from /home/rbrunner/src/kde-cvs/qt-copy//lib/libqt.so.2
#20 0x817f274 in main ()
#21 0x41134baf in __libc_start_main () from /lib/libc.so.6

Hello!

The last few minutes I sent around 100 mails (even with large attachments 
...) and kmail doesn't crash.
But when I sent the last mail to you I was clicking on a folder and at just 
this moment kmail crashed. Perhaps that was the reason ?
richard

On Friday 20 July 2001 14:38 Richard Brunner wrote:
> Hello!
>
> The last few minutes I sent around 100 mails (even with
> large attachments ...) and kmail doesn't crash.
> But when I sent the last mail to you I was clicking on a
> folder and at just this moment kmail crashed. Perhaps
> that was the reason ? richard

That is possibile the reason but can you experiment more to 
confirm that?

Don.

Hello!

Now I managed it to crash kmail whenever I want ;-) !

steps to reproduce:

1) start konqueror
2) click on the "sent-mail" folder (there was one mail in it)
3) delete that mail by pressing "entf" (del on the english keybord ?)
4) click on file -> Compact all folders
5) click on "New Messages"
6) Send
-> it crashes ;-)

(while it sends you just have to wait till it crashes ... no clicking ...)

richard

--------------Boundary-00=_ZFGWDLCMTNFX032YRX2X
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

If the sent-mail folder is empty and selected then sending 
a message causes KMail to crash.

This seems to be because KMReaderWin tries to display the 
KMMessage being sent (it is added to the empty sent-folder 
folder) but this KMMessage is deleted before the 
updateReaderWin timer expires.

I attach a workaround tell the folder to be quiet so it 
doesn't emit the msgAdded signal.

Don.

On Friday 20 July 2001 15:08 Richard Brunner wrote:
> Hello!
>
> Now I managed it to crash kmail whenever I want ;-) !
>
> steps to reproduce:
>
> 1) start konqueror
> 2) click on the "sent-mail" folder (there was one mail in
> it) 3) delete that mail by pressing "entf" (del on the
> english keybord ?) 4) click on file -> Compact all
> folders
> 5) click on "New Messages"
> 6) Send
> -> it crashes ;-)
>
> (while it sends you just have to wait till it crashes ...
> no clicking ...)
>
> richard
> _______________________________________________
> Kmail Developers mailing list
> Kmail@master.kde.org
> http://master.kde.org/mailman/listinfo/kmail

--------------Boundary-00=_ZFGWDLCMTNFX032YRX2X
Content-Type: text/x-diff;
  charset="iso-8859-1";
  name="crash-on-sending.diff"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="crash-on-sending.diff"

SW5kZXg6IGttc2VuZGVyLmNwcAo9PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJD
UyBmaWxlOiAvaG9tZS9rZGUva2RlbmV0d29yay9rbWFpbC9rbXNlbmRlci5j
cHAsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMTExCmRpZmYgLXUgLXUgLWIg
LXIxLjExMSBrbXNlbmRlci5jcHAKLS0tIGttc2VuZGVyLmNwcAkyMDAxLzA2
LzI5IDE4OjE4OjIxCTEuMTExCisrKyBrbXNlbmRlci5jcHAJMjAwMS8wNy8y
MiAyMzo1NzoyNwpAQCAtMjcwLDExICsyNzAsMTUgQEAKICAgICAgIEtNZXNz
YWdlQm94OjppbmZvcm1hdGlvbigwLCBpMThuKCJDcml0aWNhbCBlcnJvcjog
IgogCQkJCSAgICAgICAiVW5hYmxlIHRvIHByb2Nlc3Mgc2VudCBtYWlsIChv
dXQgb2Ygc3BhY2U/KSIKIAkJCQkgICAgICAgIk1vdmluZyBmYWlsaW5nIG1l
c3NhZ2UgdG8gXCJzZW50LW1haWxcIiBmb2xkZXIuIikpOworICAgICAga2Vy
bmVsLT5zZW50Rm9sZGVyKCktPnF1aWV0KFRSVUUpOwogICAgICAga2VybmVs
LT5zZW50Rm9sZGVyKCktPm1vdmVNc2cobUN1cnJlbnRNc2cpOwogICAgICAg
Y2xlYW51cCgpOworICAgICAga2VybmVsLT5zZW50Rm9sZGVyKCktPnF1aWV0
KEZBTFNFKTsKICAgICAgIHJldHVybjsKICAgICBjYXNlIDE6CisgICAgICBr
ZXJuZWwtPnNlbnRGb2xkZXIoKS0+cXVpZXQoVFJVRSk7CiAgICAgICBrZXJu
ZWwtPnNlbnRGb2xkZXIoKS0+bW92ZU1zZyhtQ3VycmVudE1zZyk7CisgICAg
ICBrZXJuZWwtPnNlbnRGb2xkZXIoKS0+cXVpZXQoRkFMU0UpOwogICAgIGRl
ZmF1bHQ6CiAgICAgICBicmVhazsKICAgICB9Cg==

--------------Boundary-00=_ZFGWDLCMTNFX032YRX2X--

this has been fixed

Today Kmail crashed after i tried to send a 6Mb attachment with it

perhaps its because the server refuses such huge mails?

Auke

I opened up kmail in gnome terminal then tried sending a mail and it crashed.

Backtrace: 

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1115651840 (LWP 16239)]
[KCrash handler]
#7  0x401ce984 in QString::unicode (this=0x16) at qstring.h:653
#8  0x4203af88 in ucstrcmp (as=@0xbfffe830, bs=@0x16) at tools/qstring.cpp:82
#9  0x42044ea2 in operator< (s1=@0xbfffe830, s2=@0x16)
    at tools/qstring.cpp:6348
#10 0x403fe84d in std::less<QString>::operator() (this=0x8b3696c, 
    __x=@0xbfffe830, __y=@0x16) at stl_function.h:227
#11 0x40e249d3 in std::_Rb_tree<QString, QString, std::_Identity<QString>, std::less<QString>, std::allocator<QString> >::insert_unique (this=0x8b3696c, 
    __v=@0xbfffe830) at stl_tree.h:869
#12 0x40e24213 in std::set<QString, std::less<QString>, std::allocator<QString> >::insert (this=0x8b3696c, __x=@0xbfffe830) at stl_set.h:314
#13 0x4100cdfa in KABC::AddresseeHelper::initSettings (this=0x8b36928)
    at addresseehelper.cpp:80
#14 0x4100c957 in AddresseeHelper (this=0x8b36928) at addresseehelper.cpp:44
#15 0x4100c6fe in KABC::AddresseeHelper::self () at addresseehelper.cpp:35
#16 0x40fc00b3 in KABC::Addressee::setNameFromString (this=0xbfffea20, 
    str=@0xbfffea70) at addressee.cpp:927
#17 0x40f48190 in KRecentAddress::RecentAddresses::load (this=0x8b34ea8, 
    config=0x810dcd8) at recentaddresses.cpp:84
#18 0x40f47fe9 in RecentAddresses (this=0x8b34ea8, config=0x810dcd8)
    at recentaddresses.cpp:61
#19 0x40f47f15 in KRecentAddress::RecentAddresses::self (config=0x810dcd8)
    at recentaddresses.cpp:52
#20 0x40268337 in KMComposeWin::slotContinueDoSend (this=0x845f930, 
    sentOk=true) at kmcomposewin.cpp:3080
#21 0x4025305f in KMComposeWin::qt_invoke (this=0x845f930, _id=155, 
    _o=0xbfffec50) at kmcomposewin.moc:856
#22 0x41d4fda7 in QObject::activate_signal (this=0x845f930, clist=0x8130f20, 
    o=0xbfffec50) at kernel/qobject.cpp:2356
#23 0x41d5070d in QObject::activate_signal_bool (this=0x845f930, signal=7, 
    param=true) at kernel/qobject.cpp:2452
#24 0x402526c6 in KMComposeWin::applyChangesDone (this=0x845f930, t0=true)
    at kmcomposewin.moc:767
#25 0x40260d87 in KMComposeWin::slotComposerDone (this=0x845f930, rc=true)
    at kmcomposewin.cpp:1715
#26 0x4025302e in KMComposeWin::qt_invoke (this=0x845f930, _id=154, 
    _o=0xbfffedc0) at kmcomposewin.moc:855
#27 0x41d4fda7 in QObject::activate_signal (this=0x8b4ecc0, clist=0x8539978, 
    o=0xbfffedc0) at kernel/qobject.cpp:2356
#28 0x41d5070d in QObject::activate_signal_bool (this=0x8b4ecc0, signal=2, 
    param=true) at kernel/qobject.cpp:2452
#29 0x403ed187 in MessageComposer::done (this=0x8b4ecc0, t0=true)
    at messagecomposer.moc:89
#30 0x403e4351 in MessageComposer::doNextJob (this=0x8b4ecc0)
    at messagecomposer.cpp:291
#31 0x403e4520 in MessageComposer::slotDoNextJob (this=0x8b4ecc0)
    at messagecomposer.cpp:334
#32 0x403ed1d2 in MessageComposer::qt_invoke (this=0x8b4ecc0, _id=2, 
    _o=0xbfffef00) at messagecomposer.moc:95
#33 0x41d4fda7 in QObject::activate_signal (this=0x82af8b0, clist=0x8993308, 
    o=0xbfffef00) at kernel/qobject.cpp:2356
#34 0x420a65e8 in QSignal::signal (this=0x82af8b0, t0=@0x82af8d8)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#35 0x41d6d4ff in QSignal::activate (this=0x82af8b0) at kernel/qsignal.cpp:212
#36 0x41d74a17 in QSingleShotTimer::event (this=0x82af888)
    at kernel/qtimer.cpp:277
#37 0x41ced2eb in QApplication::internalNotify (this=0xbffff510, 
    receiver=0x82af888, e=0xbffff180) at kernel/qapplication.cpp:2620
#38 0x41cec7a8 in QApplication::notify (this=0xbffff510, receiver=0x82af888, 
    e=0xbffff180) at kernel/qapplication.cpp:2343
#39 0x4183cd82 in KApplication::notify (this=0xbffff510, receiver=0x82af888, 
    event=0xbffff180) at kapplication.cpp:495
#40 0x4062a53d in QApplication::sendEvent (receiver=0x82af888, 
    event=0xbffff180) at qapplication.h:491
#41 0x41cdb5ba in QEventLoop::activateTimers (this=0x810ce98)
    at kernel/qeventloop_unix.cpp:558
#42 0x41c9516d in QEventLoop::processEvents (this=0x810ce98, flags=4)
    at kernel/qeventloop_x11.cpp:389
#43 0x41d014b2 in QEventLoop::enterLoop (this=0x810ce98)
    at kernel/qeventloop.cpp:198
#44 0x41d013ce in QEventLoop::exec (this=0x810ce98)
    at kernel/qeventloop.cpp:145
#45 0x41ced46b in QApplication::exec (this=0xbffff510)
    at kernel/qapplication.cpp:2743
#46 0x0804aa53 in main (argc=1, argv=0xbffff6c4) at main.cpp:108

If you have not already done so then you may like to try running KMail 
from within KDE once before trying it in gnome.

> Backtrace:
>
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread 1115651840 (LWP 16239)]
> [KCrash handler]
> #7  0x401ce984 in QString::unicode (this=0x16) at qstring.h:653

this=0x16 indicates this QString is not in a sane state, and the 
problem occurred earlier. So continue looking up the stack.

> #8  0x4203af88 in ucstrcmp (as= 0xbfffe830, bs= 0x16) at
> tools/qstring.cpp:82 #9  0x42044ea2 in operator< (s1= 0xbfffe830,
> s2= 0x16)
>     at tools/qstring.cpp:6348
> #10 0x403fe84d in std::less<QString>::operator() (this=0x8b3696c,
>     __x= 0xbfffe830, __y= 0x16) at stl_function.h:227
> #11 0x40e249d3 in std::_Rb_tree<QString, QString,
> std::_Identity<QString>, std::less<QString>,
> std::allocator<QString> >::insert_unique (this=0x8b3696c, __v=
> 0xbfffe830) at stl_tree.h:869
> #12 0x40e24213 in std::set<QString, std::less<QString>,
> std::allocator<QString> >::insert (this=0x8b3696c, __x= 0xbfffe830)
> at stl_set.h:314 #13 0x4100cdfa in
> KABC::AddresseeHelper::initSettings (this=0x8b36928) at
> addresseehelper.cpp:80

Maybe a KABC problem here.  illogic-al I think a seperate kabc bug 
report should be filed including this backtrace.

Don.

i have only kde4 installed, no gnome or other stuff