KDevelop stops accepting text input

Bug #803619 reported by gregreen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kdevelop (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

While working on a c++ project, KDevelop works fine for the first few minutes after opening. After a few minutes, the cursor stops blinking, and the user can no longer input text into - nor delete text from - any of the open files. This happens at seemingly random times, but frequently. The only sure workaround I have found is to close KDevelop and restart the program, although sometimes after leaving KDevelop alone for a while, it begins working again.

Running KDevelop from a terminal, here is the output I get when the cursor stops blinking:

kdevelop(7519)/kdevplatform (language) KDevelop::TopDUContextDynamicData::getDeclarationForIndex: declaration index out of bounds: 1725 count: 18
kdevelop(7519)/kdevplatform (language) KDevelop::TopDUContextDynamicData::getDeclarationForIndex: declaration index out of bounds: 1725 count: 18
kdevelop(7519)/kdevplatform (language) KDevelop::TopDUContextDynamicData::getDeclarationForIndex: declaration index out of bounds: 1725 count: 18
kdevelop(7519)/kdevplatform (language) KDevelop::TopDUContextDynamicData::getDeclarationForIndex: declaration index out of bounds: 1725 count: 18
QVariantMap DBusMenuExporterDBus::getProperties(int, const QStringList&) const: Condition failed: action
execute composite (NativeAppJob(0x5cbc100, name = "MCMC Lightweight") )

The line about "declaration index out of bounds" happens repeatedly as the program runs, but it seems that the "Condition failed: action" is associated with the bug.

I am running 64-bit Ubuntu 11.04 with Unity. The installed version of KDevelop is 4:4.2.2-0ubuntu2, from the natty/main amd64 repository. I can provide any other necessary infomation related to the bug.

Changed in kdevelop (Ubuntu):
status: New → Confirmed
Revision history for this message
gregreen (gregreen) wrote :

I've found that a workaround for this bug is to open a terminal or press the Print Screen key. After closing the terminal or screenshot dialog, KDevelop again accepts input. Alt-tabbing to another window and returning to KDevelop does not do the same trick, however.

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.