Bug 167406 - crash when moving messages
Summary: crash when moving messages
Status: RESOLVED DUPLICATE of bug 126715
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 166142 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-07-25 08:58 UTC by Juha Tuomala
Modified: 2008-12-08 00:14 UTC (History)
1 user (show)

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 Juha Tuomala 2008-07-25 08:58:32 UTC
Version:            (using KDE 3.5.9)
Installed from:    Fedora RPMs

[Detaching after fork from child process 30767.]
[Detaching after fork from child process 30769.]
[Detaching after fork from child process 30771.]
[Detaching after fork from child process 21134.]
[Detaching after fork from child process 21136.]
pure virtual method called
terminate called without an active exception

Program received signal SIGABRT, Aborted.
[Switching to Thread 140143658166016 (LWP 28157)]
0x0000003d87230ec5 in raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
Current language:  auto; currently c
(gdb) set pagination 0
(gdb) bt
#0  0x0000003d87230ec5 in raise (sig=<value optimized out>) at ../n                          ptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x0000003d87232970 in abort () at abort.c:88
#2  0x0000003d8bebecb4 in __gnu_cxx::__verbose_terminate_handler ()                           at ../../../../libstdc++-v3/libsupc++/vterminate.cc:97
#3  0x0000003d8bebce76 in __cxxabiv1::__terminate (handler=0x6dfd)                           at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:43
#4  0x0000003d8bebcea3 in std::terminate () at ../../../../libstdc+                          +-v3/libsupc++/eh_terminate.cc:53
#5  0x0000003d8bebd35f in __cxa_pure_virtual () at ../../../../libs                          tdc++-v3/libsupc++/pure.cc:55
#6  0x00000034af48f806 in KMail::ImapJob::slotGetNextMessage (this=                          0x10d8f20) at imapjob.cpp:277
#7  0x00000034af49049d in KMail::ImapJob::init (this=0x10d8f20, jt=                          KMail::FolderJob::tGetMessage, sets=@0x7fffc4fab0b0, folder=0x0, ms                          gList=@0x10d8f70) at imapjob.cpp:214
#8  0x00000034af4917ba in KMail::ImapJob::execute (this=0x10d8f20)                           at imapjob.cpp:675
#9  0x00000034af46cd99 in KMMainWidget::slotMsgActivated (this=0x25                          52e00, msg=0x31dd850) at kmmainwidget.cpp:2294
#10 0x00000034af47b422 in KMMainWidget::qt_invoke (this=0x2552e00,                           _id=164, _o=0x7fffc4fab270) at kmmainwidget.moc:607
#11 0x00000034a7963c29 in QObject::activate_signal (this=0x2eafd20,                           clist=<value optimized out>, o=0x7fffc4fab270) at kernel/qobject.c                          pp:2359
#12 0x00000034a7964900 in QObject::activate_signal (this=0x6dfd, si                          gnal=<value optimized out>) at kernel/qobject.cpp:2328
#13 0x00000034a9ad7181 in KAction::qt_invoke (this=0x2eafd20, _id=15, _o=0x7fffc4fab340) at kaction.moc:218
#14 0x00000034a7963c29 in QObject::activate_signal (this=0x25510e0, clist=<value optimized out>, o=0x7fffc4fab340) at kernel/qobject.cpp:2359
#15 0x00000034a7964900 in QObject::activate_signal (this=0x6dfd, signal=<value optimized out>) at kernel/qobject.cpp:2328
#16 0x00000034a8f50b85 in KAccelPrivate::emitActivatedSignal (this=0x25510e0, pAction=0x2eb0250) at kaccel.cpp:400
#17 0x00000034a8fa851a in KAccelPrivate::eventFilter (this=0x25510e0, pEvent=0x7fffc4fab840) at kaccel.cpp:370
#18 0x00000034a79632b2 in QObject::activate_filters (this=0x2558ab0, e=0x7fffc4fab840) at kernel/qobject.cpp:906
#19 0x00000034a7963327 in QObject::event (this=0x2558ab0, e=0x7fffc4fab840) at kernel/qobject.cpp:738
#20 0x00000034a799a878 in QWidget::event (this=0x6dfd, e=0x6dfd) at kernel/qwidget.cpp:4681
#21 0x00000034a7a59605 in QMainWindow::event (this=0x2558ab0, e=0x7fffc4fab840) at widgets/qmainwindow.cpp:1690
#22 0x00000034a7902b75 in QApplication::internalNotify (this=<value optimized out>, receiver=0x2558ab0, e=0x7fffc4fab840) at kernel/qapplication.cpp:2638
#23 0x00000034a7904363 in QApplication::notify (this=0x7fffc4fabf30, receiver=0x2dd6b50, e=0x7fffc4fab840) at kernel/qapplication.cpp:2395
#24 0x00000034a8fc7e38 in KApplication::notify (this=0x7fffc4fabf30, receiver=0x2dd6b50, event=0x7fffc4fab840) at kapplication.cpp:550
#25 0x00000034a8f5bf6e in KAccelEventHandler::x11Event (this=<value optimized out>, pEvent=<value optimized out>) at /usr/lib64/qt-3.3/include/qapplication.h:523
#26 0x00000034a8fc6588 in KApplication::x11EventFilter (this=0x7fffc4fabf30, _event=0x7fffc4fabbc0) at kapplication.cpp:1659
#27 0x00000034a78906b7 in qt_x11EventFilter (ev=0x7fffc4fabbc0) at kernel/qapplication_x11.cpp:407
#28 0x00000034a78a048e in QApplication::x11ProcessEvent (this=0x7fffc4fabf30, event=0x7fffc4fabbc0) at kernel/qapplication_x11.cpp:3382
#29 0x00000034a78b1074 in QEventLoop::processEvents (this=0x10d7b20, flags=4) at kernel/qeventloop_x11.cpp:195
#30 0x00000034a791a321 in QEventLoop::enterLoop (this=0x6dfd) at kernel/qeventloop.cpp:201
#31 0x00000034a791a202 in QEventLoop::exec (this=0x6dfd) at kernel/qeventloop.cpp:148
#32 0x0000000000402914 in main (argc=2, argv=<value optimized out>) at main.cpp:110
#33 0x0000003d8721e074 in __libc_start_main (main=0x4027c0 <main>, argc=2, ubp_av=0x7fffc4fac1f8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffc4fac1e8) at libc-start.c:220
#34 0x0000000000402669 in _start ()


just before doing so, it looked like the message list was getting screwed, I tried to move some 
message and it didn't disappear anywhere but list 
kept going shorter.
Comment 1 Thomas McGuire 2008-07-25 12:34:25 UTC

*** This bug has been marked as a duplicate of 126715 ***
Comment 2 Alistair Strachan 2008-07-25 12:47:56 UTC
The reporter says he's using 3.5.9. What makes you think this is a duplicate when the bug was ALREADY fixed in 3.5.9?
Comment 3 Thomas McGuire 2008-07-25 13:00:26 UTC
To the reporter: What does the version field in Help->About KMail say?
Comment 4 Juha Tuomala 2008-07-25 14:46:31 UTC
McGuire's question: KMail 1.9.9 (Using KDE 3.5.9-5.fc8 Fedora) 

Howcome we have ended to the situation, that:
- we've konqueror Help menu entry for submitting bugs with version autofill.
- that wont end to bugzilla's version field
- if i submit the usual way, version is still somehow vague
- we end up not having proper information in bugs.

perhaps it's time to go back to original bugzilla and 
stop 'adding value to it by customizing it'.
Comment 5 Christophe Marin 2008-08-05 13:36:47 UTC
Putting back as duplicate. 

Making feedbacks about bugs.kde.org is also possible using the appropriate product.

*** This bug has been marked as a duplicate of 126715 ***
Comment 6 Juha Tuomala 2008-12-08 00:14:41 UTC
*** Bug 166142 has been marked as a duplicate of this bug. ***