Application: ktimetracker (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-35-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: deleating session entries - Unusual behavior I noticed: ktimer can't write to log file (disk is not full). When broght up for the first time today - had a lot of extraneous entries - no idea where they came from. -- Backtrace: Application: KTimeTracker (ktimetracker), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f40f824c7c0 (LWP 8026))] Thread 3 (Thread 0x7f40dc8e5700 (LWP 8028)): #0 0x00007f40f436c8bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x00007f40f06f38cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f40f06b8ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f40f06b8fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f40f06b949a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f40e271a406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x00007f40f06da9e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x00007f40f0b85e9a in start_thread (arg=0x7f40dc8e5700) at pthread_create.c:308 #8 0x00007f40f4379cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f40ceac9700 (LWP 8036)): #0 0x00007f40f436c8bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x00007f40f06f38cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f40f06b8ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f40f06b8fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f40f06b9164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f40f5068426 in QEventDispatcherGlib::processEvents (this=0x7f40c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x00007f40f5037c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007f40f5037ed7 in QEventLoop::exec (this=0x7f40ceac8d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007f40f4f36fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #9 0x00007f40f50179ff in QInotifyFileSystemWatcherEngine::run (this=0x1e21e40) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x00007f40f4f39fcb in QThreadPrivate::start (arg=0x1e21e40) at thread/qthread_unix.cpp:298 #11 0x00007f40f0b85e9a in start_thread (arg=0x7f40ceac9700) at pthread_create.c:308 #12 0x00007f40f4379cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f40f824c7c0 (LWP 8026)): [KCrash Handler] #6 ref (this=0x10000000007) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #7 QString (other=..., this=0x7fff3bf1f730) at /usr/include/qt4/QtCore/qstring.h:726 #8 Task::uid (this=0x1d85860) at ../../ktimetracker/task.cpp:661 #9 0x000000000043c304 in TaskView::deleteTaskBatch (this=0x1aa24d0, task=0x1d85860) at ../../ktimetracker/taskview.cpp:995 #10 0x000000000043c41c in TaskView::deleteTask (this=0x1aa24d0, task=0x1d85860) at ../../ktimetracker/taskview.cpp:1034 #11 0x000000000044e04a in qt_static_metacall (_a=0x7fff3bf1fa80, _id=<optimized out>, _o=0x1a36df0, _c=<optimized out>) at ./timetrackerwidget.moc:184 #12 TimetrackerWidget::qt_static_metacall (_o=0x1a36df0, _c=<optimized out>, _id=<optimized out>, _a=0x7fff3bf1fa80) at ./timetrackerwidget.moc:149 #13 0x00007f40f504d281 in QMetaObject::activate (sender=0x1dc9ca0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff3bf1fa80) at kernel/qobject.cpp:3547 #14 0x00007f40f5a2c132 in QAction::triggered (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:277 #15 0x00007f40f5a2c31f in QAction::activate (this=0x1dc9ca0, event=<optimized out>) at kernel/qaction.cpp:1257 #16 0x00007f40f5e7e119 in QMenuPrivate::activateCausedStack (this=0x1d194d0, causedStack=..., action=0x1dc9ca0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1028 #17 0x00007f40f5e84272 in QMenuPrivate::activateAction (this=0x1d194d0, action=0x1dc9ca0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120 #18 0x00007f40f682d030 in KMenu::mouseReleaseEvent (this=0x1de59b0, e=0x7fff3bf20650) at ../../kdeui/widgets/kmenu.cpp:464 #19 0x00007f40f5a83144 in QWidget::event (this=0x1de59b0, event=0x7fff3bf20650) at kernel/qwidget.cpp:8362 #20 0x00007f40f5e8580b in QMenu::event (this=0x1de59b0, e=0x7fff3bf20650) at widgets/qmenu.cpp:2469 #21 0x00007f40f5a32894 in notify_helper (e=0x7fff3bf20650, receiver=0x1de59b0, this=0x1773aa0) at kernel/qapplication.cpp:4559 #22 QApplicationPrivate::notify_helper (this=0x1773aa0, receiver=0x1de59b0, e=0x7fff3bf20650) at kernel/qapplication.cpp:4531 #23 0x00007f40f5a380bf in QApplication::notify (this=<optimized out>, receiver=0x1de59b0, e=0x7fff3bf20650) at kernel/qapplication.cpp:4102 #24 0x00007f40f676c3f6 in KApplication::notify (this=0x7fff3bf21330, receiver=0x1de59b0, event=0x7fff3bf20650) at ../../kdeui/kernel/kapplication.cpp:311 #25 0x00007f40f5038e9c in QCoreApplication::notifyInternal (this=0x7fff3bf21330, receiver=0x1de59b0, event=0x7fff3bf20650) at kernel/qcoreapplication.cpp:876 #26 0x00007f40f5a33862 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #27 QApplicationPrivate::sendMouseEvent (receiver=0x1de59b0, event=0x7fff3bf20650, alienWidget=0x0, nativeWidget=0x1de59b0, buttonDown=0x0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170 #28 0x00007f40f5ab32c1 in QETWidget::translateMouseEvent (this=0x1de59b0, event=<optimized out>) at kernel/qapplication_x11.cpp:4551 #29 0x00007f40f5ab1bae in QApplication::x11ProcessEvent (this=0x7fff3bf21330, event=0x7fff3bf20f20) at kernel/qapplication_x11.cpp:3732 #30 0x00007f40f5adb0d2 in x11EventSourceDispatch (s=0x1773420, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #31 0x00007f40f06b8d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x00007f40f06b90a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x00007f40f06b9164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x00007f40f50683bf in QEventDispatcherGlib::processEvents (this=0x1747f80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #35 0x00007f40f5adad5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #36 0x00007f40f5037c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #37 0x00007f40f5037ed7 in QEventLoop::exec (this=0x7fff3bf212c0, flags=...) at kernel/qeventloop.cpp:204 #38 0x00007f40f503cf67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #39 0x000000000041ca20 in main (argc=1, argv=0x7fff3bf21de8) at ../../ktimetracker/main.cpp:137 Reported using DrKonqi
ok, I am building up a landscape to compile ktimetracker and test this.
Mr. Wu, I have since noticed that this problem occurs when using the kde window "shade" feature. I was trying to keep the window "shaded" on all desktops - making it available for job changes. As long as I leave it "un-shaded" on one desk-top there isn't a problem. Thanks, Mike Osterhouse MSCIS System Developer Enterprise Information Systems, INC USCG ISD Bldg 63/ Aviation Logistics Center Elizabeth City, NC 27909 Phone (252)335-6861 Fax: (252)334-6455 www.goeis.com -----Original Message----- From: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] On Behalf Of Jekyll Wu Sent: Friday, April 05, 2013 2:32 AM To: Osterhouse, Michael P CTR Subject: [ktimetracker] [Bug 312949] ktimetracker inconsistant log file https://bugs.kde.org/show_bug.cgi?id=312949 Jekyll Wu <adaptee@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |4.8.5
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.
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!