Bug 265439 - Choqok crashed at startup when Kontact Version 4.4.10 is opened
Summary: Choqok crashed at startup when Kontact Version 4.4.10 is opened
Status: RESOLVED DUPLICATE of bug 264658
Alias: None
Product: choqok
Classification: Applications
Component: general (show other bugs)
Version: 1.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Mehrdad Momeny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-04 19:19 UTC by Ricardo Chung
Modified: 2011-02-18 21:46 UTC (History)
0 users

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 Ricardo Chung 2011-02-04 19:19:00 UTC
Application: choqok (1.0)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-20-desktop x86_64
Distribution: "openSUSE 11.4 Milestone 6 of 6 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I had my Kontact v.4.4.10 without regards wich module is opened (i.e. kmail., calendar, summary, contacts,...). Then I attempt to startup Choqok ver.1.0. was opened by few seconds enough and crashed. It happen each time I try to open Choqok and then the Kontact without regards wether I have already  closed Kontact. In order to replicate this crash it's needed to open Kontact first and then go to Choqok. It never happen if I only open Choqok first.

-- Backtrace:
Application: Choqok (choqok), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f09f0867f64 in KJob::error() const () from /usr/lib64/libkdecore.so.5
#7  0x00007f09dde41a01 in ?? () from /usr/lib64/kde4/choqok_videopreview.so
#8  0x00007f09dde43879 in ?? () from /usr/lib64/kde4/choqok_videopreview.so
#9  0x00007f09dde443dc in ?? () from /usr/lib64/kde4/choqok_videopreview.so
#10 0x00007f09dde4101c in ?? () from /usr/lib64/kde4/choqok_videopreview.so
#11 0x00007f09f0488e3f in QMetaObject::activate (sender=0x1741b00, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3272
#12 0x00007f09f048ee0f in QSingleShotTimer::timerEvent (this=0x1741b00) at kernel/qtimer.cpp:308
#13 0x00007f09f04877e9 in QObject::event (this=0x1741b00, e=<value optimized out>) at kernel/qobject.cpp:1175
#14 0x00007f09ef83fd44 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f09ef84824a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f09f14969e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#17 0x00007f09f0473c3c in QCoreApplication::notifyInternal (this=0x7fff9196c470, receiver=0x1741b00, event=0x7fff9196c0b0) at kernel/qcoreapplication.cpp:732
#18 0x00007f09f04a1528 in sendEvent (this=0x6503e0) at kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x6503e0) at kernel/qeventdispatcher_unix.cpp:618
#20 0x00007f09f049e294 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f09eb30ac63 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#22 0x00007f09eb30b440 in ?? () from /lib64/libglib-2.0.so.0
#23 0x00007f09eb30b6e0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#24 0x00007f09f049e96f in QEventDispatcherGlib::processEvents (this=0x620810, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#25 0x00007f09ef8e4d9e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f09f0473092 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007f09f04732a5 in QEventLoop::exec (this=0x7fff9196c3c0, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007f09f04776eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#29 0x000000000040e4dc in _start ()

This bug may be a duplicate of or related to bug 264728.

Possible duplicates by query: bug 265079, bug 264728, bug 262236.

Reported using DrKonqi
Comment 1 Mehrdad Momeny 2011-02-18 21:46:09 UTC

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