choqoK crashed and caused the signal 11 (SIGSEGV).

Bug #410290 reported by kabotage
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
choqok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Description: Ubuntu 9.04
Release: 9.04

Qt: 4.5.0
KDE: 4.2.2 (KDE 4.2.2)
choqoK: 0.4

choqok:
  Installed: 0.4-0ubuntu3
  Candidate: 0.4-0ubuntu3
  Version table:
 *** 0.4-0ubuntu3 0
        500 http://hk.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

Application: choqoK (choqok), signal SIGSEGV

Thread 1 (Thread 0xb60ec970 (LWP 5112)):
[KCrash Handler]
#6 QCoreApplication::notifyInternal (this=0xbf9d498c, receiver=0xa5d0b98, event=0xbf9d39b4) at kernel/qcoreapplication.cpp:587
#7 0xb706b03e in QCoreApplication::sendEvent (receiver=0xa5d0b98, event=0xbf9d39b4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#8 0xb70bbca1 in QWidgetPrivate::close_helper (this=0xa7ab268, mode=QWidgetPrivate::CloseWithEvent) at kernel/qwidget.cpp:7088
#9 0xb70bbdb8 in QWidget::close (this=0xa5d0b98) at kernel/qwidget.cpp:7159
#10 0x0808479b in _start ()

Cannot remove own tweet, crashes after a couple of times refreshing. To reproduce it, try to remove your tweet twice or thrice cause it wont disappear at all, then refreshing it a couple of times will crash the program.

Tags: choqok
kabotage (kabotage)
description: updated
summary: - choqoK (choqok) crashed and caused the signal 11 (SIGSEGV).
+ choqoK crashed and caused the signal 11 (SIGSEGV).
Revision history for this message
Christian Mangold (neversfelde) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance.

0.6.1 is in backports for Jaunty.

Changed in choqok (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in choqok (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.