Bug 287140

Summary:	editing a new time-planing item crashes Kontact
Product:	[Applications] ktimetracker	Reporter:	Jens Mander <jemand>
Component:	general	Assignee:	Zoltan Gyarmati <mr.zoltan.gyarmati>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	amadeus, aspotashev, bosyber, bradlee.sargent, caldun, fsantini, i.breeden, intemann, kdepim-bugs, lst_manage, nick, piedro.kulman, rod260185, spochybova, timho07, twanderson71, user581
Priority:	NOR
Version:	4.9.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi

Description Jens Mander 2011-11-21 09:02:15 UTC

Application: kontact (4.7.3)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
I tried to use the time-planing to edit a new item.
Kontact crashed when I tried to edit the time of this new item

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ff7d4c977a0 (LWP 2735))]

Thread 4 (Thread 0x7ff7bb00e700 (LWP 2741)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007ff7d14f7c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007ff7d14f7d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007ff7cc8f3efc in start_thread (arg=0x7ff7bb00e700) at pthread_create.c:304
#4  0x00007ff7d220589d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7ff7ba6f5700 (LWP 2755)):
#0  0x00007ff7d21f9773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ff7cbe25f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff7cbe26429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff7d3640f3e in QEventDispatcherGlib::processEvents (this=0xdba540, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007ff7d3614cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff7d3614ef7 in QEventLoop::exec (this=0x7ff7ba6f4de0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007ff7d352c27f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007ff7d352ed05 in QThreadPrivate::start (arg=0xdba5a0) at thread/qthread_unix.cpp:331
#8  0x00007ff7cc8f3efc in start_thread (arg=0x7ff7ba6f5700) at pthread_create.c:304
#9  0x00007ff7d220589d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7ff760acd700 (LWP 3813)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007ff760accad0 in ?? ()
#2  0x00007fffb35ff7e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7ff7d4c977a0 (LWP 2735)):
[KCrash Handler]
#6  0x00007ff75dec9db1 in timetrackerstorage::rawevents (this=0x922bab0) at ../../ktimetracker/timetrackerstorage.cpp:320
#7  0x00007ff75dee701d in historydialog::listallevents (this=0x56eb190) at ../../ktimetracker/historydialog.cpp:102
#8  0x00007ff75dee873b in historydialog::historydialog (this=0x56eb190, parent=<optimized out>) at ../../ktimetracker/historydialog.cpp:82
#9  0x00007ff75dec66ca in EditTaskDialog::on_edittimespushbutton_clicked (this=0x1967b80) at ../../ktimetracker/edittaskdialog.cpp:93
#10 0x00007ff75dec1cf1 in EditTaskDialog::qt_metacall (this=0x1967b80, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at moc_edittaskdialog.cpp:75
#11 0x00007ff7d3628eba in QMetaObject::activate (sender=0x148d290, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffb345dfa0) at kernel/qobject.cpp:3278
#12 0x00007ff7d3037582 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206
#13 0x00007ff7d2d7d13e in QAbstractButtonPrivate::emitClicked (this=<optimized out>) at widgets/qabstractbutton.cpp:546
#14 0x00007ff7d2d7e47b in QAbstractButtonPrivate::click (this=0xda2cfc0) at widgets/qabstractbutton.cpp:539
#15 0x00007ff7d2d7e6ec in QAbstractButton::mouseReleaseEvent (this=0x148d290, e=0x7fffb345e6b0) at widgets/qabstractbutton.cpp:1121
#16 0x00007ff7d2a16c9a in QWidget::event (this=0x148d290, event=0x7fffb345e6b0) at kernel/qwidget.cpp:8295
#17 0x00007ff7d29c6424 in notify_helper (e=0x7fffb345e6b0, receiver=0x148d290, this=0xc97630) at kernel/qapplication.cpp:4486
#18 QApplicationPrivate::notify_helper (this=0xc97630, receiver=0x148d290, e=0x7fffb345e6b0) at kernel/qapplication.cpp:4458
#19 0x00007ff7d29cbc6b in QApplication::notify (this=<optimized out>, receiver=0x148d290, e=0x7fffb345e6b0) at kernel/qapplication.cpp:4047
#20 0x00007ff7d404b126 in KApplication::notify (this=0x7fffb34616a0, receiver=0x148d290, event=0x7fffb345e6b0) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x00007ff7d3615afc in QCoreApplication::notifyInternal (this=0x7fffb34616a0, receiver=0x148d290, event=0x7fffb345e6b0) at kernel/qcoreapplication.cpp:787
#22 0x00007ff7d29c73f2 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 QApplicationPrivate::sendMouseEvent (receiver=0x148d290, event=0x7fffb345e6b0, alienWidget=0x148d290, nativeWidget=0x1967b80, buttonDown=0x148d290, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3146
#24 0x00007ff7d2a46945 in QETWidget::translateMouseEvent (this=0x1967b80, event=<optimized out>) at kernel/qapplication_x11.cpp:4568
#25 0x00007ff7d2a458be in QApplication::x11ProcessEvent (this=0x7fffb34616a0, event=0x7fffb345eed0) at kernel/qapplication_x11.cpp:3690
#26 0x00007ff7d2a6e412 in x11EventSourceDispatch (s=0xc945b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#27 0x00007ff7cbe25a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007ff7cbe26258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007ff7cbe26429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007ff7d3640ed6 in QEventDispatcherGlib::processEvents (this=0xc61fd0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#31 0x00007ff7d2a6e07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007ff7d3614cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007ff7d3614ef7 in QEventLoop::exec (this=0x7fffb345f2a0, flags=...) at kernel/qeventloop.cpp:201
#34 0x00007ff7d2e7d216 in QDialog::exec (this=0x1967b80) at dialogs/qdialog.cpp:552
#35 0x00007ff75dedf752 in TaskView::newTask (this=0xa5dc790, caption=<optimized out>, parent=0x0) at ../../ktimetracker/taskview.cpp:869
#36 0x00007ff75dedfacd in TaskView::newTask (this=0xa5dc790) at ../../ktimetracker/taskview.cpp:860
#37 0x00007ff75def4623 in MainAdaptor::qt_metacall (this=0xc2c4520, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7fffb345f5f0) at mainadaptor.moc:198
#38 0x00007ff7cf34d0e9 in QDBusConnectionPrivate::deliverCall (this=0xc82170, object=0xc2c4520, msg=..., metaTypes=..., slotIdx=16) at qdbusintegrator.cpp:942
#39 0x00007ff7cf34e25c in QDBusConnectionPrivate::activateCall (this=0xc82170, object=0xc2c4520, flags=273, msg=...) at qdbusintegrator.cpp:852
#40 0x00007ff7cf34eb22 in QDBusConnectionPrivate::activateObject (this=0xc82170, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1410
#41 0x00007ff7cf34ee8a in QDBusConnectionPrivate::handleObjectCall (this=0xc82170, msg=...) at qdbusintegrator.cpp:1503
#42 0x00007ff7cf34f57f in handleMessage (amsg=..., this=0xc82170) at qdbusintegrator.cpp:565
#43 QDBusConnectionPrivate::handleMessage (this=0xc82170, amsg=...) at qdbusintegrator.cpp:547
#44 0x00007ff7cf34f6fe in QDBusConnectionPrivate::sendWithReplyLocal (this=0xc82170, message=...) at qdbusintegrator.cpp:1907
#45 0x00007ff7cf34ff6a in QDBusConnectionPrivate::sendWithReplyAsync (this=0xc82170, message=..., timeout=31232824) at qdbusintegrator.cpp:1941
#46 0x00007ff7cf33f760 in QDBusConnection::asyncCall (this=<optimized out>, message=<optimized out>, timeout=<optimized out>) at qdbusconnection.cpp:560
#47 0x00007ff7cf35bced in QDBusAbstractInterface::asyncCallWithArgumentList (this=0xc188890, method=..., args=...) at qdbusabstractinterface.cpp:477
#48 0x00007ff77397ee8d in newTask (this=0xc188890) at ./ktimetrackerinterface.h:124
#49 ktimetrackerplugin::newTask (this=<optimized out>) at ../../../../kontact/plugins/ktimetracker/ktimetracker_plugin.cpp:125
#50 0x00007ff77397efe8 in ktimetrackerplugin::qt_metacall (this=0x10bea60, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffb3460160) at ./ktimetracker_plugin.moc:76
#51 0x00007ff7d3628eba in QMetaObject::activate (sender=0x10c7890, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffb3460160) at kernel/qobject.cpp:3278
#52 0x00007ff7d29bfb62 in QAction::triggered (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#53 0x00007ff7d29bfd4f in QAction::activate (this=0x10c7890, event=<optimized out>) at kernel/qaction.cpp:1257
#54 0x00007ff7d48c2f47 in trigger (this=<optimized out>) at /usr/include/qt4/QtGui/qaction.h:218
#55 Kontact::MainWindow::slotNewClicked (this=0xe48fc0) at ../../../kontact/src/mainwindow.cpp:736
#56 0x00007ff7d48c60db in Kontact::MainWindow::qt_metacall (this=0xe48fc0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffb3460320) at ./mainwindow.moc:123
#57 0x00007ff7d3628eba in QMetaObject::activate (sender=0xf24190, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffb3460320) at kernel/qobject.cpp:3278
#58 0x00007ff7d29bfb62 in QAction::triggered (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#59 0x00007ff7d29bfd4f in QAction::activate (this=0xf24190, event=<optimized out>) at kernel/qaction.cpp:1257
#60 0x00007ff7d2d7e43a in QAbstractButtonPrivate::click (this=0x121b010) at widgets/qabstractbutton.cpp:528
#61 0x00007ff7d2d7e6ec in QAbstractButton::mouseReleaseEvent (this=0x12255c0, e=0x7fffb3460a40) at widgets/qabstractbutton.cpp:1121
#62 0x00007ff7d2e3b2da in QToolButton::mouseReleaseEvent (this=<optimized out>, e=<optimized out>) at widgets/qtoolbutton.cpp:721
#63 0x00007ff7d2a16c9a in QWidget::event (this=0x12255c0, event=0x7fffb3460a40) at kernel/qwidget.cpp:8295
#64 0x00007ff7d29c6424 in notify_helper (e=0x7fffb3460a40, receiver=0x12255c0, this=0xc97630) at kernel/qapplication.cpp:4486
#65 QApplicationPrivate::notify_helper (this=0xc97630, receiver=0x12255c0, e=0x7fffb3460a40) at kernel/qapplication.cpp:4458
#66 0x00007ff7d29cbc6b in QApplication::notify (this=<optimized out>, receiver=0x12255c0, e=0x7fffb3460a40) at kernel/qapplication.cpp:4047
#67 0x00007ff7d404b126 in KApplication::notify (this=0x7fffb34616a0, receiver=0x12255c0, event=0x7fffb3460a40) at ../../kdeui/kernel/kapplication.cpp:311
#68 0x00007ff7d3615afc in QCoreApplication::notifyInternal (this=0x7fffb34616a0, receiver=0x12255c0, event=0x7fffb3460a40) at kernel/qcoreapplication.cpp:787
#69 0x00007ff7d29c73f2 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#70 QApplicationPrivate::sendMouseEvent (receiver=0x12255c0, event=0x7fffb3460a40, alienWidget=0x12255c0, nativeWidget=0xf44670, buttonDown=0x12255c0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3146
#71 0x00007ff7d2a46945 in QETWidget::translateMouseEvent (this=0xf44670, event=<optimized out>) at kernel/qapplication_x11.cpp:4568
#72 0x00007ff7d2a458be in QApplication::x11ProcessEvent (this=0x7fffb34616a0, event=0x7fffb3461260) at kernel/qapplication_x11.cpp:3690
#73 0x00007ff7d2a6e412 in x11EventSourceDispatch (s=0xc945b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#74 0x00007ff7cbe25a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#75 0x00007ff7cbe26258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#76 0x00007ff7cbe26429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#77 0x00007ff7d3640ed6 in QEventDispatcherGlib::processEvents (this=0xc61fd0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#78 0x00007ff7d2a6e07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#79 0x00007ff7d3614cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#80 0x00007ff7d3614ef7 in QEventLoop::exec (this=0x7fffb3461630, flags=...) at kernel/qeventloop.cpp:201
#81 0x00007ff7d3619789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#82 0x0000000000403629 in main (argc=3, argv=0x7fffb3461cc8) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi

Comment 1 Thorsten Staerk 2011-11-22 09:21:30 UTC

Thanks for the report, I will try to reproduce this.

Comment 2 Christophe Marin 2011-12-08 14:13:57 UTC

*** Bug 288478 has been marked as a duplicate of this bug. ***

Comment 3 bosyber 2012-01-03 10:59:32 UTC

Created attachment 67376 [details]
New crash information added by DrKonqi

kontact (4.7.3) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4

- What I was doing when the application crashed:
As it said in the initial bugreport: creating a new task to track time of.

-- Backtrace (Reduced):
#6  0x00007f64acd80db1 in timetrackerstorage::rawevents (this=0x46a7210) at ../../ktimetracker/timetrackerstorage.cpp:320
#7  0x00007f64acd9e01d in historydialog::listallevents (this=0x4e07930) at ../../ktimetracker/historydialog.cpp:102
#8  0x00007f64acd9f73b in historydialog::historydialog (this=0x4e07930, parent=<optimized out>) at ../../ktimetracker/historydialog.cpp:82
#9  0x00007f64acd7d6ca in EditTaskDialog::on_edittimespushbutton_clicked (this=0x28aa8a0) at ../../ktimetracker/edittaskdialog.cpp:93
#10 0x00007f64acd78d01 in EditTaskDialog::qt_metacall (this=0x28aa8a0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at moc_edittaskdialog.cpp:75

Comment 4 amadeus 2012-01-04 08:01:55 UTC

Created attachment 67430 [details]
New crash information added by DrKonqi

kontact (4.7.3) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4

My english is very poor to describe it.
I`m sorry.

-- Backtrace (Reduced):
#7  0xadb8caaf in timetrackerstorage::rawevents (this=0x9df8fb0) at ../../ktimetracker/timetrackerstorage.cpp:320
#8  0xadbae202 in historydialog::listallevents (this=0xa181978) at ../../ktimetracker/historydialog.cpp:102
#9  0xadbafc81 in historydialog::historydialog (this=0xa181978, parent=0x9df6058) at ../../ktimetracker/historydialog.cpp:82
#10 0xadb888fb in EditTaskDialog::on_edittimespushbutton_clicked (this=0x9e258f8) at ../../ktimetracker/edittaskdialog.cpp:93
#11 0xadb83011 in EditTaskDialog::qt_metacall (this=0x9e258f8, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfcd7838) at moc_edittaskdialog.cpp:75

Comment 5 Emmett Culley 2012-01-17 21:21:15 UTC

Created attachment 67940 [details]
New crash information added by DrKonqi

kontact (4.7.4) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.0

- What I was doing when the application crashed:

Attempting to add new item.  Clicked on "edit time" button and kontact crashed.

-- Backtrace (Reduced):
#6  0x00007f69ef26e3e1 in timetrackerstorage::rawevents (this=0x30650b0) at /usr/src/debug/kdepim-4.7.4/ktimetracker/timetrackerstorage.cpp:320
#7  0x00007f69ef28b4dd in historydialog::listallevents (this=0x3ad7df0) at /usr/src/debug/kdepim-4.7.4/ktimetracker/historydialog.cpp:102
#8  0x00007f69ef28cbef in historydialog::historydialog (this=0x3ad7df0, parent=<optimized out>) at /usr/src/debug/kdepim-4.7.4/ktimetracker/historydialog.cpp:82
#9  0x00007f69ef26ad4a in EditTaskDialog::on_edittimespushbutton_clicked (this=0x337d5b0) at /usr/src/debug/kdepim-4.7.4/ktimetracker/edittaskdialog.cpp:93
#10 0x00007f69ef2663be in EditTaskDialog::qt_metacall (this=0x337d5b0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kdepim-4.7.4/x86_64-redhat-linux-gnu/ktimetracker/moc_edittaskdialog.cpp:91

Comment 6 Kubuntiac 2012-03-13 23:12:21 UTC

Created attachment 69597 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

Like the other posters, I get a crash every time in Kontact I go Time Tracker > New Item > Edit Times

Posting this just to add my details and bt. I'm on KDE 4.8.1 Kontact 4.8.0 and QT 4.8

-- Backtrace (Reduced):
#6  0x00007fce9608e531 in timetrackerstorage::rawevents (this=0x270c9d0) at /chakra/desktop-testing/kdepim/src/kdepim-4.8.1/ktimetracker/timetrackerstorage.cpp:321
#7  0x00007fce960adc8d in historydialog::listallevents (this=0x2c025c0) at /chakra/desktop-testing/kdepim/src/kdepim-4.8.1/ktimetracker/historydialog.cpp:102
#8  0x00007fce960af38c in historydialog::historydialog (this=0x2c025c0, parent=<optimized out>) at /chakra/desktop-testing/kdepim/src/kdepim-4.8.1/ktimetracker/historydialog.cpp:82
#9  0x00007fce9608ab4a in EditTaskDialog::on_edittimespushbutton_clicked (this=0x2b0a4b0) at /chakra/desktop-testing/kdepim/src/kdepim-4.8.1/ktimetracker/edittaskdialog.cpp:103
#10 0x00007fce960863ce in EditTaskDialog::qt_metacall (this=0x2b0a4b0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at /chakra/desktop-testing/kdepim/src/kdepim-4.8.1/ktimetracker/moc_edittaskdialog.cpp:91

Comment 7 Christophe Marin 2012-03-30 14:31:00 UTC

*** Bug 296332 has been marked as a duplicate of this bug. ***

Comment 8 Christophe Marin 2012-04-13 20:53:01 UTC

*** Bug 298067 has been marked as a duplicate of this bug. ***

Comment 9 piedro 2012-05-23 19:45:41 UTC

I can confirm this behaviour on Kubuntu 12.04 with KDE 4.8.2 stable (?)

Comment 10 piedro 2012-06-19 08:28:10 UTC

Created attachment 71934 [details]
New crash information added by DrKonqi

kontact (4.9 beta2) on KDE Platform 4.8.90 (4.8.90) using Qt 4.8.1

- What I was doing when the application crashed:

I tried to create a new timetracker item - kontact crashes immediately

-- Backtrace (Reduced):
#6  timetrackerstorage::rawevents (this=0x59b5220) at ../../ktimetracker/timetrackerstorage.cpp:323
#7  0x00007fadaa7862ef in historydialog::listallevents (this=0x291c760) at ../../ktimetracker/historydialog.cpp:105
#8  0x00007fadaa78809c in historydialog::historydialog (this=0x291c760, parent=<optimized out>) at ../../ktimetracker/historydialog.cpp:85
#9  0x00007fadaa761f1a in EditTaskDialog::on_edittimespushbutton_clicked (this=0x592d820) at ../../ktimetracker/edittaskdialog.cpp:103
#10 0x00007fadaa75d6ee in EditTaskDialog::qt_metacall (this=0x592d820, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at moc_edittaskdialog.cpp:91

Comment 11 rod260185 2012-07-20 03:05:21 UTC

Created attachment 72642 [details]
New crash information added by DrKonqi

kontact (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1

- What I was doing when the application crashed:

Editing a new KTimeTracker item caused Kontact to crash.

-- Backtrace (Reduced):
#6  0x00007fb8b5c80d81 in timetrackerstorage::rawevents (this=0x6ac41c0) at ../../ktimetracker/timetrackerstorage.cpp:321
#7  0x00007fb8b5ca04dd in historydialog::listallevents (this=0x6844640) at ../../ktimetracker/historydialog.cpp:102
#8  0x00007fb8b5ca1bdc in historydialog::historydialog (this=0x6844640, parent=<optimized out>) at ../../ktimetracker/historydialog.cpp:82
#9  0x00007fb8b5c7d39a in EditTaskDialog::on_edittimespushbutton_clicked (this=0x29db2f0) at ../../ktimetracker/edittaskdialog.cpp:103
#10 0x00007fb8b5c78bde in EditTaskDialog::qt_metacall (this=0x29db2f0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at moc_edittaskdialog.cpp:91

Comment 12 fsantini 2012-08-28 13:32:06 UTC

Created attachment 73524 [details]
New crash information added by DrKonqi

kontact (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1

- What I was doing when the application crashed:

same as comment 9 :-)
I opened Kontact, clicked on Time Tracker, clicked on New Task then clicked on Edit Times and Kontact crashes--repeatably.

-- Backtrace (Reduced):
#7  0xaa5cdaaf in timetrackerstorage::rawevents (this=0x950bfe8) at ../../ktimetracker/timetrackerstorage.cpp:321
#8  0xaa5f17c2 in historydialog::listallevents (this=0x99eafa8) at ../../ktimetracker/historydialog.cpp:102
#9  0xaa5f3242 in historydialog::historydialog (this=0x99eafa8, parent=0x9d55df8) at ../../ktimetracker/historydialog.cpp:82
#10 0xaa5c950b in EditTaskDialog::on_edittimespushbutton_clicked (this=0xae3c7e8) at ../../ktimetracker/edittaskdialog.cpp:103
#11 0xaa5c3d5d in EditTaskDialog::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at moc_edittaskdialog.cpp:52

Comment 13 piedro 2012-08-29 13:15:49 UTC

still present in KDE 4.9

Comment 14 Nick Leverton 2012-09-19 12:38:33 UTC

Created attachment 74028 [details]
New crash information added by DrKonqi

kontact (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.2

- What I was doing when the application crashed:

Creating a new Time Tracker item (I haven't used this feature before so have no tracker items at present).
I entered the title and description but when i clicked on "edit times", kontact crashed as attached.

-- Backtrace (Reduced):
#7  timetrackerstorage::rawevents (this=0xb407ba0) at ../../ktimetracker/timetrackerstorage.cpp:323
#8  0xa6fc6a42 in historydialog::listallevents (this=0xb5db488) at ../../ktimetracker/historydialog.cpp:105
#9  0xa6fc8b82 in historydialog::historydialog (this=0xb5db488, parent=0xb5690b8) at ../../ktimetracker/historydialog.cpp:85
#10 0xa6f9d6ab in EditTaskDialog::on_edittimespushbutton_clicked (this=0x9ef9ba8) at ../../ktimetracker/edittaskdialog.cpp:103
#11 0xa6f97e4d in EditTaskDialog::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at moc_edittaskdialog.cpp:52

Comment 15 Myriam Schweingruber 2012-09-21 06:40:50 UTC

Confirmed by duplicates.

Comment 16 Jekyll Wu 2012-09-25 04:20:56 UTC

*** Bug 307360 has been marked as a duplicate of this bug. ***

Comment 17 Bradlee Sargent 2012-10-01 12:36:34 UTC

Created attachment 74265 [details]
New crash information added by DrKonqi

kontact (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.2

- What I was doing when the application crashed:

I was trying to add a new timed item to kontact when it crashed.
When I restarted kontact, the same thing happened again.

-- Backtrace (Reduced):
#6  timetrackerstorage::rawevents (this=0x752bd80) at ../../ktimetracker/timetrackerstorage.cpp:323
#7  0x00007f479286830f in historydialog::listallevents (this=0x69675c0) at ../../ktimetracker/historydialog.cpp:105
#8  0x00007f479286a0bc in historydialog::historydialog (this=0x69675c0, parent=<optimized out>) at ../../ktimetracker/historydialog.cpp:85
#9  0x00007f4792843f4a in EditTaskDialog::on_edittimespushbutton_clicked (this=0x68ed390) at ../../ktimetracker/edittaskdialog.cpp:103
#10 0x00007f479283f71e in EditTaskDialog::qt_metacall (this=0x68ed390, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at moc_edittaskdialog.cpp:91

Comment 18 spochybova 2012-11-12 08:43:38 UTC

Created attachment 75195 [details]
New crash information added by DrKonqi

kontact (4.8.5) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2

I tried to start a new time-tracking task and when I tried to save it, it said I need to check my possibilities to edit this application and the Kontact application consequently crashed. However, running time tracker outside the Kontact framework works OK.

-- Backtrace (Reduced):
#6  0x00007f42c5890d51 in timetrackerstorage::rawevents (this=0x46481d0) at /usr/src/debug/kdepim-4.8.5/ktimetracker/timetrackerstorage.cpp:321
#7  0x00007f42c58b025d in historydialog::listallevents (this=0x48c75c0) at /usr/src/debug/kdepim-4.8.5/ktimetracker/historydialog.cpp:102
#8  0x00007f42c58b196f in historydialog::historydialog (this=0x48c75c0, parent=<optimized out>) at /usr/src/debug/kdepim-4.8.5/ktimetracker/historydialog.cpp:82
#9  0x00007f42c588d4ba in EditTaskDialog::on_edittimespushbutton_clicked (this=0x4721f30) at /usr/src/debug/kdepim-4.8.5/ktimetracker/edittaskdialog.cpp:103
#10 0x00007f42c5888cfe in EditTaskDialog::qt_metacall (this=0x4721f30, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kdepim-4.8.5/x86_64-redhat-linux-gnu/ktimetracker/moc_edittaskdialog.cpp:90

Comment 19 Jekyll Wu 2012-12-19 13:53:40 UTC

*** Bug 311898 has been marked as a duplicate of this bug. ***

Comment 20 Jekyll Wu 2013-02-27 14:09:50 UTC

*** Bug 315848 has been marked as a duplicate of this bug. ***

Comment 21 Andrew Crouthamel 2018-09-04 18:53:41 UTC

Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug.

Comment 22 Alexander Potashev 2019-11-17 22:53:45 UTC

KTimeTracker is now ported to Qt5/KF5, however the Kontact plugin is dropped since the KDE PIM team and I agreed that KTimeTracker is not very relevant to KDE PIM/Kontact.

Thus, this bug is still RESOLVED as UNMAINTAINED.