Bug 283754 - segmentation fault -- first time setting up application
Summary: segmentation fault -- first time setting up application
Status: RESOLVED WORKSFORME
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Thorsten Staerk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-11 06:13 UTC by neal wakershauser
Modified: 2019-11-17 22:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description neal wakershauser 2011-10-11 06:13:02 UTC
Application: ktimetracker (4.4.5)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- Custom settings of the application:
first attempt at using the application -- perhaps initially setting up (25) workspaces was not a real smart idea on this system -- I will try again with, perhaps, (2) workspaces ... Ubuntu 11.04 -- total system memory of 2 gigabytes

please write and request that the NYPD investigate supervisor Anthony Boulagna's
pepper-spraying of three middle-aged women, spectators, who had been rolled into orange construction fencing by NYPD. And were subsequently maced by supervisor Boulagna who then holstered his spray gun and walked away.
then continued to pepper-spray civilians who were retreating in front of him.

i'm sure that had a lot to do with my segmentation fault ...


thank - you

-- Backtrace:
Application: KTimeTracker (ktimetracker), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7888730 (LWP 4059))]

Thread 3 (Thread 0xb7616b70 (LWP 4060)):
#0  0x00a9436b in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x044dc616 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6
#2  0x05167802 in g_main_context_release () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0516904f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x0516992b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x029fa304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x051922df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x00a91e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x044ce73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb6e15b70 (LWP 4116)):
#0  0x0059b416 in __kernel_vsyscall ()
#1  0x044bff76 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x0517984b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x051691af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x05169524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x07e33577 in QEventDispatcherGlib::processEvents (this=0x89c6338, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x07e05289 in QEventLoop::processEvents (this=0xb6e15270, flags=...) at kernel/qeventloop.cpp:149
#7  0x07e05522 in QEventLoop::exec (this=0xb6e15270, flags=...) at kernel/qeventloop.cpp:201
#8  0x07d0f2a0 in QThread::exec (this=0x89c5900) at thread/qthread.cpp:492
#9  0x07de6fdb in QInotifyFileSystemWatcherEngine::run (this=0x89c5900) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x07d11da2 in QThreadPrivate::start (arg=0x89c5900) at thread/qthread_unix.cpp:320
#11 0x00a91e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x044ce73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb7888730 (LWP 4059)):
[KCrash Handler]
#7  ref (this=0x88681d8) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#8  QVector (this=0x88681d8) at /usr/include/qt4/QtCore/qvector.h:118
#9  QForeachContainer (this=0x88681d8) at /usr/include/qt4/QtCore/qglobal.h:2250
#10 DesktopTracker::changeTimers (this=0x88681d8) at ../../ktimetracker/desktoptracker.cpp:73
#11 0x0522fa12 in DesktopTracker::qt_metacall (this=0x88681d8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbf80595c) at ./desktoptracker.moc:82
#12 0x07e0c6ba in QMetaObject::metacall (object=0x88681d8, cl=QMetaObject::InvokeMetaMethod, idx=7, argv=0xbf80595c) at kernel/qmetaobject.cpp:237
#13 0x07e1c4ff in QMetaObject::activate (sender=0x889d7b8, m=0x7f415a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3287
#14 0x07e692f7 in QTimer::timeout (this=0x889d7b8) at .moc/release-shared/moc_qtimer.cpp:134
#15 0x07e223ee in QTimer::timerEvent (this=0x889d7b8, e=0xbf805e7c) at kernel/qtimer.cpp:271
#16 0x07e1b214 in QObject::event (this=0x889d7b8, e=0xbf805e7c) at kernel/qobject.cpp:1190
#17 0x014d3d24 in QApplicationPrivate::notify_helper (this=0x86a39b8, receiver=0x889d7b8, e=0xbf805e7c) at kernel/qapplication.cpp:4462
#18 0x014d88ce in QApplication::notify (this=0xbf8061c8, receiver=0x889d7b8, e=0xbf805e7c) at kernel/qapplication.cpp:3862
#19 0x011dd32a in KApplication::notify (this=0xbf8061c8, receiver=0x889d7b8, event=0xbf805e7c) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x07e060bb in QCoreApplication::notifyInternal (this=0xbf8061c8, receiver=0x889d7b8, event=0xbf805e7c) at kernel/qcoreapplication.cpp:731
#21 0x07e361e4 in sendEvent (this=0x86a6934) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QTimerInfoList::activateTimers (this=0x86a6934) at kernel/qeventdispatcher_unix.cpp:604
#23 0x07e32e27 in timerSourceDispatch (source=0x86a6968) at kernel/qeventdispatcher_glib.cpp:184
#24 idleTimerSourceDispatch (source=0x86a6968) at kernel/qeventdispatcher_glib.cpp:231
#25 0x05168aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#26 0x05169270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#27 0x05169524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0x07e3353c in QEventDispatcherGlib::processEvents (this=0x8664760, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#29 0x0158a1e5 in QGuiEventDispatcherGlib::processEvents (this=0x8664760, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x07e05289 in QEventLoop::processEvents (this=0xbf806114, flags=...) at kernel/qeventloop.cpp:149
#31 0x07e05522 in QEventLoop::exec (this=0xbf806114, flags=...) at kernel/qeventloop.cpp:201
#32 0x07e09ecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#33 0x014d18e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#34 0x0805e431 in main (argc=) at ../../ktimetracker/main.cpp:137

Reported using DrKonqi
Comment 1 Thorsten Staerk 2011-10-11 14:37:31 UTC
How can you reproduce this crash? What do you mean by "setting up 25 workspaces"? Do you mean virtual desktops?
Comment 2 neal wakershauser 2011-10-11 17:31:18 UTC
I have not tried to reproduce the crash ... still setting up the program and
trying to take a more reasonable approach -- setting up four ?virtual?
desktops in the GNOME Panel 2.32.1 instead of 25.

I have never submitted to Bugzilla be before, but I am a long time
Linux user and this application looks like something I could really
use -- very simple, does what it's supposed to do.

On Tue, Oct 11, 2011 at 9:37 AM, Thorsten Staerk <dev@staerk.de> wrote:

> https://bugs.kde.org/show_bug.cgi?id=283754
>
>
> Thorsten Staerk <dev@staerk.de> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDSINFO
>         Resolution|                            |REMIND
>
>
>
>
> --- Comment #1 from Thorsten Staerk <dev staerk de>  2011-10-11 14:37:31
> ---
> How can you reproduce this crash? What do you mean by "setting up 25
> workspaces"? Do you mean virtual desktops?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Thorsten Staerk 2011-10-12 21:09:03 UTC
You cannot reproduce the crash - so the program works for you, right?
Comment 4 Andrew Crouthamel 2018-09-04 18:55:04 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.