Bug 218912 - Kontact crash when trying to print a mail [QAction::d_func, QAction::setChecked, KMPrintCommand::execute]
Summary: Kontact crash when trying to print a mail [QAction::d_func, QAction::setChec...
Status: RESOLVED DUPLICATE of bug 218368
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4 pre
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-16 12:57 UTC by Marc Schiffbauer
Modified: 2009-12-17 00:49 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 Marc Schiffbauer 2009-12-16 12:57:36 UTC
Application: kontact (4.4 pre)
KDE Platform Version: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1)) (Compiled from sources)
Qt Version: 4.6.0
Operating System: Linux 2.6.32-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
Trying to print a mail from kontact/kmail produces a crash.

Gwenview for example is able to print, although because PyKDE does not build in 4.3.80 I still have pykde4-4.3.4 and printer-applet-4.3.4 as well as system-config-printer-kde-4.3.4 installed on this system. I dunno if this is related somehow.

The crash can be reproduced everytime.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.2-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[KCrash Handler]
#5  QAction::d_func (this=0x0, b=true) at kernel/qaction.h:67
#6  QAction::setChecked (this=0x0, b=true) at kernel/qaction.cpp:1044
#7  0x00007f7a867ea3a0 in KMPrintCommand::execute (this=0x1e7d780) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:1645
#8  0x00007f7a867ed03a in KMCommand::slotPostTransfer (this=0x1e7d780, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:290
#9  0x00007f7a867f65b3 in KMCommand::qt_metacall (this=0x1e7d780, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe5906670)
    at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmcommands.moc:93
#10 0x00007f7a9d43dc73 in QMetaObject::activate (sender=0x1e7d780, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x206d8a0) at kernel/qobject.cpp:3286
#11 0x00007f7a867e7c5e in KMCommand::messagesTransfered (this=0x0, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmcommands.moc:108
#12 0x00007f7a867fbe68 in KMCommand::transferSelectedMsgs (this=0x1e7d780) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:388
#13 0x00007f7a867fc088 in KMCommand::slotStart (this=0x1e7d780) at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80/kmail/kmcommands.cpp:282
#14 0x00007f7a867f6596 in KMCommand::qt_metacall (this=0x1e7d780, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe59068a0)
    at /var/tmp/portage/kde-base/kmail-4.3.80/work/kmail-4.3.80_build/kmail/kmcommands.moc:92
#15 0x00007f7a9d43dc73 in QMetaObject::activate (sender=0x7d0080, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x206d8a0) at kernel/qobject.cpp:3286
#16 0x00007f7a9d44550f in QSingleShotTimer::timerEvent (this=0x7d0080) at kernel/qtimer.cpp:308
#17 0x00007f7a9d43a913 in QObject::event (this=0x7d0080, e=0x1) at kernel/qobject.cpp:1216
#18 0x00007f7a9c8e853c in QApplicationPrivate::notify_helper (this=0x63ad70, receiver=0x7d0080, e=0x7fffe5907000) at kernel/qapplication.cpp:4242
#19 0x00007f7a9c8f0d7a in QApplication::notify (this=0x7fffe5907360, receiver=<value optimized out>, e=0x7fffe5907000) at kernel/qapplication.cpp:4125
#20 0x00007f7a9de19446 in KApplication::notify (this=0x7fffe5907360, receiver=0x7d0080, event=0x7fffe5907000)
    at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kdeui/kernel/kapplication.cpp:302
#21 0x00007f7a9d42b02b in QCoreApplication::notifyInternal (this=0x7fffe5907360, receiver=0x7d0080, event=0x7fffe5907000) at kernel/qcoreapplication.cpp:704
#22 0x00007f7a9d4578e2 in QCoreApplication::sendEvent (this=0x64a190) at kernel/qcoreapplication.h:215
#23 QTimerInfoList::activateTimers (this=0x64a190) at kernel/qeventdispatcher_unix.cpp:603
#24 0x00007f7a9d4547a8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#25 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#26 0x00007f7a94ff44bd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f7a94ff7e78 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#28 0x00007f7a94ff7fa0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f7a9d454473 in QEventDispatcherGlib::processEvents (this=0x60bef0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#30 0x00007f7a9c984b3e in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x00007f7a9d429982 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#32 0x00007f7a9d429d54 in QEventLoop::exec (this=0x7fffe59072a0, flags=) at kernel/qeventloop.cpp:201
#33 0x00007f7a9d42da3b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#34 0x000000000040412d in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kontact-4.3.80/work/kontact-4.3.80/kontact/src/main.cpp:221

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-17 00:49:23 UTC
This was reported and fixed recently: bug 218368. Thanks

*** This bug has been marked as a duplicate of bug 218368 ***