Bugzilla – Bug 144626
crash kontact (kmail)
Last modified: 2008-06-25 09:53:18 UTC
I just crashes randomly, when I click on something. It's not because of bad hardware. The server is IMAP and it's Lotus Notes (an old piece of crap). However the client should not crash because of server lameness. I have more than one account, other than the crappy Lotus, there's cyrus-imapd that works perfectly. If the trace it's not useful, I could try to use kmail for the accounts on cyrus-imapd and thunderbird for Lotus. This way I'll be able to tell for sure if kmail crashes because of the Lotus server. rpm -q kdepim3 kdepim3-debuginfo kdepim3-3.5.0-15 kdepim3-debuginfo-3.5.0-15 System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240660304 (LWP 10864)] [New Thread -1277928544 (LWP 10868)] [New Thread -1269535840 (LWP 10867)] [New Thread -1261143136 (LWP 10866)] [New Thread -1252750432 (LWP 10865)] [KCrash handler] #4 0x0000000c in ?? () #5 0xb576a96d in KMFolderImap::flagsToStatus (msg=0x8e25ac0, flags=1, newMsg=true) at kmfolderimap.cpp:1355 #6 0xb59a48a5 in KMFolderImap::slotGetMessagesData (this=0x86ded00, job=0x8e1f408, data=@0xbfa65c50) at kmfolderimap.cpp:1502 #7 0xb59c4f8b in KMFolderImap::qt_invoke (this=0x86ded00, _id=31, _o=0xbfa65950) at kmfolderimap.moc:324 #8 0xb6ca5519 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #9 0xb778edcd in KIO::TransferJob::data (this=0x8e1f408, t0=0x8e1f408, t1=@0xbfa65c50) at jobclasses.moc:993 #10 0xb778ee58 in KIO::TransferJob::slotData (this=0x8e1f408, _data=@0xbfa65c50) at job.cpp:902 #11 0xb77cd7d9 in KIO::TransferJob::qt_invoke (this=0x8e1f408, _id=18, _o=0xbfa65a44) at jobclasses.moc:1072 #12 0xb6ca5519 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0xb779209e in KIO::SlaveInterface::data (this=0x882b858, t0=@0xbfa65c50) at slaveinterface.moc:194 #14 0xb77fd175 in KIO::SlaveInterface::dispatch (this=0x882b858, _cmd=100, rawdata=@0xbfa65c50) at slaveinterface.cpp:234 #15 0xb77ea928 in KIO::SlaveInterface::dispatch (this=0x882b858) at slaveinterface.cpp:173 #16 0xb779fecb in KIO::Slave::gotInput (this=0x882b858) at slave.cpp:300 #17 0xb77ec5b0 in KIO::Slave::qt_invoke (this=0x882b858, _id=4, _o=0xbfa65d64) at slave.moc:113 #18 0xb6ca5519 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb6ca5be2 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb6fe5920 in QSocketNotifier::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6cc3470 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb6c45a37 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb6c46731 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb73071fe in KApplication::notify (this=0xbfa6622c, receiver=0x88251c0, event=0xbfa66008) at kapplication.cpp:552 #25 0xb6c3a4f1 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb6bf488e in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb6c5c911 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb6c5c78e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb6c454cf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0x0805e2bf in main (argc=140510224, argv=0x8b77c90) at main.cpp:177 #31 0xb6846738 in __libc_start_main () from /lib/libc.so.6 #32 0x08058591 in _start ()
Same as upstream bug https://bugs.kde.org/show_bug.cgi?id=106030
this is supposed to be fixed with beta1. is it really appearing with Beta1 or did you just bother to report it now?
It was appearing with beta1. I have mentioned the package version kdepim3-3.5.0-15. Anyway, the reason why I say "was" is because kontact doesn't work at all now :-) It just starts 2 processes one of which consumes 100% cpu and does nothing more. But it works on a new user profile. It probably left something in /tmp or /var/tmp, that's why it doesn't start now. Starting it from the console doesn't show any messages. I'll create a new user and use it until I reinstall everything with beta2.
beta3. I can't tell if this crash is different that the one reported initially. This backtrace magic is too deep for me. I just need a place to dump this stuff. If here is not most appropriate please point me in the right direction. I do have a bugs.kde.org account. System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240791376 (LWP 4896)] [New Thread -1279296608 (LWP 4900)] [New Thread -1270903904 (LWP 4899)] [New Thread -1262511200 (LWP 4898)] [New Thread -1254118496 (LWP 4897)] [KCrash handler] #6 0xb5419e2d in dw_strasciicasecmp ( s1=0xbf5a303f <Address 0xbf5a303f out of bounds>, len1=1972107357, s2=0xb54371a3 "content-type", len2=12) at dwstring.cpp:69 #7 0xb541df62 in DwHeaders::FindField (this=0xb54390f0, aFieldName=0xb54371a3 "content-type") at headers.cpp:291 #8 0xb541e057 in DwHeaders::HasContentType (this=0xb54390f0) at headers.cpp:700 #9 0xb57f71a4 in applyHeadersToMessagePart (headers=@0xb54390f0, aPart=0x86a43b4) at kmmessage.cpp:2823 #10 0xb57f7b7b in KMMessage::bodyPart (aDwBodyPart=0x8823f78, aPart=0x86a43b4, withBody=true) at kmmessage.cpp:2899 #11 0xb57fea87 in (anonymous namespace)::AttachmentURLHandler::statusBarMessage (this=0x876cc88, url=@0xbfe80c74, w=0x854ecb0) at partNode.h:98 #12 0xb56bbd59 in KMail::URLHandlerManager::statusBarMessage (this=0x876b770, url=@0xbfe80c74, w=0x854ecb0) at urlhandlermanager.cpp:312 #13 0xb57d8049 in KMReaderWin::slotUrlOn (this=0x854ecb0, aUrl=@0x8876448) at kmreaderwin.cpp:1842 #14 0xb58cd20d in KMReaderWin::qt_invoke (this=0x854ecb0, _id=58, _o=0xbfe80dc4) at kmreaderwin.moc:290 #15 0xb6c8977d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb6c89b42 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb7b24760 in KHTMLPart::onURL () from /opt/kde3/lib/libkhtml.so.4 #18 0xb7b32daa in KHTMLPart::overURL () from /opt/kde3/lib/libkhtml.so.4 #19 0xb7b4e245 in KHTMLPart::khtmlMouseMoveEvent () from /opt/kde3/lib/libkhtml.so.4 #20 0xb7b03c70 in KHTMLPart::customEvent () from /opt/kde3/lib/libkhtml.so.4 #21 0xb6c88dce in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb6c2a417 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb6c2b0c1 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb72cd803 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #25 0xb7b391f2 in KHTMLView::viewportMouseMoveEvent () from /opt/kde3/lib/libkhtml.so.4 #26 0xb6d9e8f3 in QScrollView::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb7b0c3f9 in KHTMLView::eventFilter () from /opt/kde3/lib/libkhtml.so.4 #28 0xb6c88cec in QObject::activate_filters () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb6c88d5b in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6cc13ec in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb6c2a417 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb6c2b21b in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb72cd803 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #34 0xb6bc9c7a in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb6bc8e56 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb6bd97aa in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb6c41128 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #38 0xb6c40fbe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb6c29eaf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0x0805e322 in main (argc=1953394531, argv=0xbfe825d4) at main.cpp:177 #41 0xb682b81c in __libc_start_main () from /lib/libc.so.6 #42 0x08058591 in _start ()
System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240299856 (LWP 32386)] [New Thread -1278809184 (LWP 32390)] [New Thread -1270416480 (LWP 32389)] [New Thread -1262023776 (LWP 32388)] [New Thread -1253631072 (LWP 32387)] [KCrash handler] #6 0x00000005 in ?? () #7 0xb5692b5d in KMFolderImap::flagsToStatus (msg=0x8b3ede8, flags=1, newMsg=true) at kmfolderimap.cpp:1355 #8 0xb58e087d in KMFolderImap::slotGetMessagesData (this=0x845c208, job=0x8b8ef00, data=@0xbfb89a80) at kmfolderimap.cpp:1502 #9 0xb5909c90 in KMFolderImap::qt_invoke (this=0x845c208, _id=31, _o=0xbfb89780) at kmfolderimap.moc:324 #10 0xb6d0177d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0xb77e9f8d in KIO::TransferJob::data () from /opt/kde3/lib/libkio.so.4 #12 0xb77ea008 in KIO::TransferJob::slotData () from /opt/kde3/lib/libkio.so.4 #13 0xb782f459 in KIO::TransferJob::qt_invoke () from /opt/kde3/lib/libkio.so.4 #14 0xb6d0177d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb77ed1d1 in KIO::SlaveInterface::data () from /opt/kde3/lib/libkio.so.4 #16 0xb784f098 in KIO::SlaveInterface::dispatch () from /opt/kde3/lib/libkio.so.4 #17 0xb785827a in KIO::SlaveInterface::dispatch () from /opt/kde3/lib/libkio.so.4 #18 0xb77fafdc in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4 #19 0xb78485b0 in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4 #20 0xb6d0177d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6d01e42 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb703f010 in QSocketNotifier::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb6d1f5d0 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb6ca2417 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb6ca30c1 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb7345803 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #27 0xb6c96f64 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb6c51994 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb6cb9128 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6cb8fbe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb6ca1eaf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0x0805e322 in main (argc=143965896, argv=0xbfb8a244) at main.cpp:177 #33 0xb68a381c in __libc_start_main () from /lib/libc.so.6 #34 0x08058591 in _start ()
Silviu: is it just one mail that causes this crash, or any mail? Is it mails that have attachments, or messages that contain other messages (forwarded as mail message/multipart, not inline)? If it's one particular mail that causes the crash, please can you get the mail (ideally in its raw state off the server) and attach it here. I just fixed a bug relating to the way mail structure is handled in imap, see the next beta/rc after beta4.
The cause is not a particular mail. I'll see what happens in beta5.
System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240611152 (LWP 30129)] [New Thread -1279231072 (LWP 30133)] [New Thread -1270838368 (LWP 30132)] [New Thread -1262445664 (LWP 30131)] [New Thread -1254052960 (LWP 30130)] [KCrash handler] #6 0x0000000c in ?? () #7 0xb562baed in KMFolderImap::flagsToStatus (msg=0x8938fa8, flags=0, newMsg=true) at kmfolderimap.cpp:1355 #8 0xb58ee18d in KMFolderImap::slotGetMessagesData (this=0x8468ee0, job=0x893a4b8, data=@0xbfd7bf60) at kmfolderimap.cpp:1502 #9 0xb58ef170 in KMFolderImap::qt_invoke (this=0x8468ee0, _id=31, _o=0xbfd7bc60) at kmfolderimap.moc:324 #10 0xb6cb700d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0xb7799d4d in KIO::TransferJob::data (this=0x893a4b8, t0=0x893a4b8, t1=@0xbfd7bf60) at jobclasses.moc:993 #12 0xb7799dc8 in KIO::TransferJob::slotData (this=0x893a4b8, _data=@0xbfd7bf60) at job.cpp:902 #13 0xb77ea1e9 in KIO::TransferJob::qt_invoke (this=0x893a4b8, _id=18, _o=0xbfd7bd54) at jobclasses.moc:1072 #14 0xb6cb700d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb779c42e in KIO::SlaveInterface::data (this=0x88a4c00, t0=@0xbfd7bf60) at slaveinterface.moc:194 #16 0xb77f6e08 in KIO::SlaveInterface::dispatch (this=0x88a4c00, _cmd=100, rawdata=@0xbfd7bf60) at slaveinterface.cpp:234 #17 0xb77d85ca in KIO::SlaveInterface::dispatch (this=0x88a4c00) at slaveinterface.cpp:173 #18 0xb77a706c in KIO::Slave::gotInput (this=0x88a4c00) at slave.cpp:300 #19 0xb77da7e0 in KIO::Slave::qt_invoke (this=0x88a4c00, _id=4, _o=0xbfd7c074) at slave.moc:113 #20 0xb6cb700d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6cb76d2 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb6feeab0 in QSocketNotifier::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb6cd4d50 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb6c57d57 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb6c58a01 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb730c833 in KApplication::notify (this=0xbfd7d52c, receiver=0x86e7308, event=0xbfd7c318) at kapplication.cpp:552 #27 0xb6c4c874 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb6c07914 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb6c6ea68 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6c5775f in QApplication::enter_loop () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb6e3b0d5 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb75cf197 in KMessageBox::createKMessageBox (dialog=0x88a57f8, icon=@0xbfd7c620, text=@0xbfd7c780, strlist=@0xbfd7c72c, ask=@0xbfd7c6b4, checkboxReturn=0xbfd7c6bb, options=<value optimized out>, details=@0x806a0f8, notifyType=QMessageBox::Information) at kmessagebox.cpp:309 #33 0xb75cf905 in KMessageBox::createKMessageBox (dialog=0x88a57f8, icon=QMessageBox::Information, text=@0xbfd7c780, strlist=@0xbfd7c72c, ask=@0xbfd7c6b4, checkboxReturn=0xbfd7c6bb, options=1, details=@0x806a0f8) at kmessagebox.cpp:146 #34 0xb75d02b7 in KMessageBox::informationListWId (parent_id=0, text=@0xbfd7c780, strlist=@0xbfd7c72c, caption=@0xbfd7c77c, dontShowAgainName=@0xbfd7c7a0, options=<value optimized out>) at kmessagebox.cpp:929 #35 0xb75d03c9 in KMessageBox::informationList (parent=0x0, text=@0xbfd7c780, strlist=@0xbfd7c72c, caption=@0xbfd7c77c, dontShowAgainName=@0xbfd7c7a0, options=1) at kmessagebox.cpp:901 #36 0xb75d042a in KMessageBox::information (parent=0x0, text=@0xbfd7c780, caption=@0xbfd7c77c, dontShowAgainName=@0xbfd7c7a0, options=1) at kmessagebox.cpp:886 #37 0xb577a8be in KMail::ImapAccountBase::handleError (this=0x84838b0, errorCode=24, errorMsg=@0x890f15c, job=0x890f110, context=@0xbfd7c894, abortSync=false) at imapaccountbase.cpp:883 #38 0xb577aaf9 in KMAcctImap::handleError (this=0xb6960148, errorCode=0, errorMsg=@0x890f15c, job=0x890f110, context=@0xbfd7c894, abortSync=false) at kmacctimap.cpp:133 #39 0xb5699962 in KMail::ImapAccountBase::handleJobError (this=0x84838b0, job=0x890f110, context=@0xbfd7c894, abortSync=false) at imapaccountbase.cpp:323 #40 0xb577dc36 in KMFolderImap::getMessagesResult (this=0x8468ee0, job=0x890f110, lastSet=false) at kmfolderimap.cpp:1581 #41 0xb577dcac in KMFolderImap::slotGetMessagesResult (this=0x8468ee0, job=0x890f110) at kmfolderimap.cpp:1602 #42 0xb58ef12d in KMFolderImap::qt_invoke (this=0x8468ee0, _id=29, _o=0xbfd7c9c4) at kmfolderimap.moc:322 #43 0xb6cb700d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #44 0xb779781e in KIO::Job::result (this=0x890f110, t0=0x890f110) at jobclasses.moc:162 #45 0xb77ea62d in KIO::Job::emitResult (this=0x890f110) at job.cpp:222 #46 0xb77ea79e in KIO::SimpleJob::slotFinished (this=0x890f110) at job.cpp:570 #47 0xb77eae9d in KIO::TransferJob::slotFinished (this=0x890f110) at job.cpp:940 #48 0xb77b3373 in KIO::SimpleJob::slotError (this=0x890f110, error=24, errorText=@0x88bf730) at job.cpp:581 #49 0xb77ea073 in KIO::SimpleJob::qt_invoke (this=0x890f110, _id=14, _o=0xbfd7cd50) at jobclasses.moc:424 #50 0xb77ea193 in KIO::TransferJob::qt_invoke (this=0x890f110, _id=14, _o=0xbfd7cd50) at jobclasses.moc:1082 #51 0xb6cb6f71 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #52 0xb779c8c0 in KIO::SlaveInterface::error (this=0x8790fa0, t0=24, t1=@0xbfd7cf30) at slaveinterface.moc:214 #53 0xb77f6cc0 in KIO::SlaveInterface::dispatch (this=0x8790fa0, _cmd=102, rawdata=@0xbfd7cf70) at slaveinterface.cpp:280 #54 0xb77d85ca in KIO::SlaveInterface::dispatch (this=0x8790fa0) at slaveinterface.cpp:173 #55 0xb77a706c in KIO::Slave::gotInput (this=0x8790fa0) at slave.cpp:300 #56 0xb77da7e0 in KIO::Slave::qt_invoke (this=0x8790fa0, _id=4, _o=0xbfd7d084) at slave.moc:113 #57 0xb6cb700d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #58 0xb6cb76d2 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #59 0xb6feeab0 in QSocketNotifier::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #60 0xb6cd4d50 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #61 0xb6c57d57 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #62 0xb6c58a01 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #63 0xb730c833 in KApplication::notify (this=0xbfd7d52c, receiver=0x878bbc8, event=0xbfd7d328) at kapplication.cpp:552 #64 0xb6c4c874 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib/libqt-mt.so.3 #65 0xb6c07914 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #66 0xb6c6ea68 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #67 0xb6c6e8fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #68 0xb6c577ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #69 0x0805e322 in main (argc=143491832, argv=0xbfd7d734) at main.cpp:177 #70 0xb685887c in __libc_start_main () from /lib/libc.so.6 #71 0x08058591 in _start ()
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(