Bug 268784 - Choqok crash after disconnecting network while updating
Summary: Choqok crash after disconnecting network while updating
Status: RESOLVED DUPLICATE of bug 234221
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-03-17 21:14 UTC by Renan Tomal Fernandes
Modified: 2011-03-19 20:01 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Renan Tomal Fernandes 2011-03-17 21:14:02 UTC
Application: choqok (1.0)
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-1.2-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Choqok was opened and I switched my network profile on networkmanager-applet while updating timeline, after this choqok crashed

- Custom settings of the application:
By libattica I think that is because I use a opendesktop account on choqok

-- Backtrace:
Application: Choqok (choqok), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f1a19661ae9 in Attica::GetJob::executeRequest (this=0x1304270) at /usr/src/debug/attica-0.2.0/lib/getjob.cpp:42
#7  0x00007f1a1964f873 in Attica::BaseJob::doWork (this=0x1304270) at /usr/src/debug/attica-0.2.0/lib/atticabasejob.cpp:129
#8  0x00007f1a196502cc in Attica::BaseJob::qt_metacall (this=0x1304270, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xe016d0) at /usr/src/debug/attica-0.2.0/build/lib/atticabasejob.moc:83
#9  0x00007f1a1b6e9a6a in QObject::event (this=0x1304270, e=<value optimized out>) at kernel/qobject.cpp:1211
#10 0x00007f1a1aaa1d14 in QApplicationPrivate::notify_helper (this=0x656cf0, receiver=0x1304270, e=0x31db610) at kernel/qapplication.cpp:4445
#11 0x00007f1a1aaaa22a in QApplication::notify (this=<value optimized out>, receiver=0x1304270, e=0x31db610) at kernel/qapplication.cpp:4324
#12 0x00007f1a1c6f89e6 in KApplication::notify (this=0x7fff53b65840, receiver=0x1304270, event=0x31db610) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311
#13 0x00007f1a1b6d5bfc in QCoreApplication::notifyInternal (this=0x7fff53b65840, receiver=0x1304270, event=0x31db610) at kernel/qcoreapplication.cpp:732
#14 0x00007f1a1b6d93f5 in sendEvent (receiver=0x0, event_type=0, data=0x61a5f0) at kernel/qcoreapplication.h:215
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x61a5f0) at kernel/qcoreapplication.cpp:1373
#16 0x00007f1a1b700783 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220
#17 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:277
#18 0x00007f1a16568bd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#19 0x00007f1a165693b0 in ?? () from /lib64/libglib-2.0.so.0
#20 0x00007f1a16569650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#21 0x00007f1a1b70091f in QEventDispatcherGlib::processEvents (this=0x620060, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#22 0x00007f1a1ab46d8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007f1a1b6d5052 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f1a1b6d5265 in QEventLoop::exec (this=0x7fff53b65790, flags=...) at kernel/qeventloop.cpp:201
#25 0x00007f1a1b6d96ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#26 0x000000000040e4dc in main (argc=5, argv=0x7fff53b65c38) at /usr/src/debug/choqok-1.0/choqok/main.cpp:58

Reported using DrKonqi
Comment 1 Mehrdad Momeny 2011-03-19 20:01:26 UTC

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