Bug 351305 - Crash on retweet when that tweet has disappeared
Summary: Crash on retweet when that tweet has disappeared
Status: RESOLVED WORKSFORME
Alias: None
Product: choqok
Classification: Applications
Component: general (show other bugs)
Version: 1.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Mehrdad Momeny
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-08-14 19:11 UTC by robert marshall
Modified: 2020-12-13 15:27 UTC (History)
3 users (show)

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 robert marshall 2015-08-14 19:11:25 UTC
Application: choqok (1.5)
KDE Platform Version: 4.14.8
Qt Version: 4.8.6
Operating System: Linux 3.19.0-25-generic i686
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:
- I attempted to retweet (with the are you sure dialog active)
- I forgot that I needed to confirm the retweet and left my machine, on my return I spotted the confirm dialog the tweet would have disappeared from the scroll window by then and confirming the retweet caused the crash

-- Backtrace:
Application: Choqok (choqok), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb2f28780 (LWP 24221))]

Thread 2 (Thread 0xa93dab40 (LWP 24251)):
#0  0xb52aaa48 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb5263eaa in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb5264156 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb6c7a674 in QEventDispatcherGlib::processEvents (this=0xa8a00468, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0xb6c46d8f in QEventLoop::processEvents (this=0xa93da224, flags=...) at kernel/qeventloop.cpp:149
#5  0xb6c4711e in QEventLoop::exec (this=0xa93da224, flags=...) at kernel/qeventloop.cpp:204
#6  0xb6b2bacb in QThread::exec (this=0xbbf5d88) at thread/qthread.cpp:538
#7  0xb6c268c6 in QInotifyFileSystemWatcherEngine::run (this=0xbbf5d88) at io/qfilesystemwatcher_inotify.cpp:265
#8  0xb6b2e69e in QThreadPrivate::start (arg=0xbbf5d88) at thread/qthread_unix.cpp:349
#9  0xb53551aa in start_thread (arg=0xa93dab40) at pthread_create.c:333
#10 0xb5de8fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 1 (Thread 0xb2f28780 (LWP 24221)):
[KCrash Handler]
#7  0xaf7ee676 in TwitterApiPostWidget::repeatPost() () from /usr/lib/libtwitterapihelper.so.1
#8  0xaf7f0b6c in ?? () from /usr/lib/libtwitterapihelper.so.1
#9  0xb6c5e70e in QMetaObject::activate (sender=0x169fd1a0, m=0xb6aa5438 <QAction::staticMetaObject>, local_signal_index=1, argv=0xbffacb54) at kernel/qobject.cpp:3567
#10 0xb60e1bb9 in QAction::triggered (this=0x169fd1a0, _t1=false) at .moc/release-shared/moc_qaction.cpp:276
#11 0xb60e399e in QAction::activate (this=0x169fd1a0, event=QAction::Trigger) at kernel/qaction.cpp:1257
#12 0xb658e1d3 in QMenuPrivate::activateCausedStack (this=0x14edbdc0, causedStack=..., action=0x169fd1a0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1037
#13 0xb6593511 in QMenuPrivate::activateAction (this=0x14edbdc0, action=0x169fd1a0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1129
#14 0xb659759a in QMenu::mouseReleaseEvent (this=0xe3c8000, e=0xbffad184) at widgets/qmenu.cpp:2371
#15 0xb61444a9 in QWidget::event (this=0xe3c8000, event=0xbffad184) at kernel/qwidget.cpp:8775
#16 0xb6597b02 in QMenu::event (this=0xe3c8000, e=0xbffad184) at widgets/qmenu.cpp:2480
#17 0xb60e936a in QApplicationPrivate::notify_helper (this=0x9cba288, receiver=0xe3c8000, e=0xbffad184) at kernel/qapplication.cpp:4570
#18 0xb60f1f84 in QApplication::notify (this=0xbffae254, receiver=0xe3c8000, e=0xbffad184) at kernel/qapplication.cpp:4113
#19 0xb73d476c in KApplication::notify (this=0xbffae254, receiver=0xe3c8000, event=0xbffad184) at ../../kdeui/kernel/kapplication.cpp:311
#20 0xb6c4840a in QCoreApplication::notifyInternal (this=0xbffae254, receiver=0xe3c8000, event=0xbffad184) at kernel/qcoreapplication.cpp:955
#21 0xb60ef9b1 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QApplicationPrivate::sendMouseEvent (receiver=0xe3c8000, event=0xbffad184, alienWidget=0x0, nativeWidget=0xe3c8000, buttonDown=0xb6ac2f44 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3178
#23 0xb6176182 in QETWidget::translateMouseEvent (this=0xe3c8000, event=0xbffad38c) at kernel/qapplication_x11.cpp:4566
#24 0xb6175571 in QApplication::x11ProcessEvent (this=0xbffae254, event=0xbffad38c) at kernel/qapplication_x11.cpp:3626
#25 0xb61a0411 in x11EventSourceDispatch (s=0x9cba4a0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#26 0xb5263d64 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#27 0xb5264089 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0xb5264156 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0xb6c7a653 in QEventDispatcherGlib::processEvents (this=0x9c3ad20, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#30 0xb61a04e6 in QGuiEventDispatcherGlib::processEvents (this=0x9c3ad20, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0xb6c46d8f in QEventLoop::processEvents (this=0xbffad674, flags=...) at kernel/qeventloop.cpp:149
#32 0xb6c4711e in QEventLoop::exec (this=0xbffad674, flags=...) at kernel/qeventloop.cpp:204
#33 0xb6596599 in QMenu::exec (this=0xe3c8000, p=..., action=0x0) at widgets/qmenu.cpp:2124
#34 0xb65a28dc in QPushButtonPrivate::_q_popupPressed (this=0x112455a8) at widgets/qpushbutton.cpp:592
#35 0xb65a29b3 in QPushButton::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at .moc/release-shared/moc_qpushbutton.cpp:56
#36 0xb6c5e70e in QMetaObject::activate (sender=0xcddf7b0, m=0xb6ab9788 <QAbstractButton::staticMetaObject>, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3567
#37 0xb67f8752 in QAbstractButton::pressed (this=0xcddf7b0) at .moc/release-shared/moc_qabstractbutton.cpp:206
#38 0xb650388c in QAbstractButtonPrivate::emitPressed (this=0x112455a8) at widgets/qabstractbutton.cpp:562
#39 0xb6504342 in QAbstractButton::mousePressEvent (this=0xcddf7b0, e=0xbffadce4) at widgets/qabstractbutton.cpp:1098
#40 0xb74b9c95 in KPushButton::mousePressEvent (this=0xcddf7b0, e=0xbffadce4) at ../../kdeui/widgets/kpushbutton.cpp:275
#41 0xb6145135 in QWidget::event (this=0xcddf7b0, event=0xbffadce4) at kernel/qwidget.cpp:8385
#42 0xb6505fe8 in QAbstractButton::event (this=0xcddf7b0, e=0xbffadce4) at widgets/qabstractbutton.cpp:1082
#43 0xb65a34fa in QPushButton::event (this=0xcddf7b0, e=0xbffadce4) at widgets/qpushbutton.cpp:683
#44 0xb60e936a in QApplicationPrivate::notify_helper (this=0x9cba288, receiver=0xcddf7b0, e=0xbffadce4) at kernel/qapplication.cpp:4570
#45 0xb60f1f84 in QApplication::notify (this=0xbffae254, receiver=0xcddf7b0, e=0xbffadce4) at kernel/qapplication.cpp:4113
#46 0xb73d476c in KApplication::notify (this=0xbffae254, receiver=0xcddf7b0, event=0xbffadce4) at ../../kdeui/kernel/kapplication.cpp:311
#47 0xb6c4840a in QCoreApplication::notifyInternal (this=0xbffae254, receiver=0xcddf7b0, event=0xbffadce4) at kernel/qcoreapplication.cpp:955
#48 0xb60ef9b1 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#49 QApplicationPrivate::sendMouseEvent (receiver=0xcddf7b0, event=0xbffadce4, alienWidget=0xcddf7b0, nativeWidget=0x9e7a410, buttonDown=0xb6ac2f44 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3178
#50 0xb6175d89 in QETWidget::translateMouseEvent (this=0x9e7a410, event=0xbffadeec) at kernel/qapplication_x11.cpp:4632
#51 0xb6175571 in QApplication::x11ProcessEvent (this=0xbffae254, event=0xbffadeec) at kernel/qapplication_x11.cpp:3626
#52 0xb61a0411 in x11EventSourceDispatch (s=0x9cba4a0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#53 0xb5263d64 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#54 0xb5264089 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#55 0xb5264156 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#56 0xb6c7a653 in QEventDispatcherGlib::processEvents (this=0x9c3ad20, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#57 0xb61a04e6 in QGuiEventDispatcherGlib::processEvents (this=0x9c3ad20, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#58 0xb6c46d8f in QEventLoop::processEvents (this=0xbffae1c4, flags=...) at kernel/qeventloop.cpp:149
#59 0xb6c4711e in QEventLoop::exec (this=0xbffae1c4, flags=...) at kernel/qeventloop.cpp:204
#60 0xb6c4d266 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#61 0xb60e7204 in QApplication::exec () at kernel/qapplication.cpp:3828
#62 0x0804f488 in ?? ()
#63 0xb5d1772e in __libc_start_main (main=0x804eca0, argc=5, argv=0xbffae334, init=0x8056330 <__libc_csu_init>, fini=0x80563a0 <__libc_csu_fini>, rtld_fini=0xb7736210 <_dl_fini>, stack_end=0xbffae32c) at libc-start.c:289
#64 0x0804f52f in _start ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-31 03:54:19 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 robert marshall 2018-10-31 10:05:11 UTC
Yes I can confirm that this crash still happens
choqok 1.6.0
kde 5.44.0
QT 5.9.5
Ubuntu 18.04
Comment 3 Andrew Crouthamel 2018-10-31 14:46:48 UTC
Thanks for the update!
Comment 4 Justin Zobel 2020-12-07 04:34:37 UTC
Thank you for the report, Robert.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 5 robert marshall 2020-12-13 15:27:43 UTC
I don't see the 'are you sure' option as being available any more - unless i've missed the location. I tried a manual resend and leaving it until the original tweet had gone from the display window and that didn't crash. So as I can't replicate, am closing!