yakuake crashed with SIGSEGV in QMenu::findIdForAction()

Bug #344583 reported by Miguel Tadeu
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
yakuake (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: yakuake

Hi,
I changed the width of yakuake and after a few seconds I pressed the menu button and yakuake freezed...after a few seconds, it crashed. Hope it helps

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/yakuake
Package: yakuake 2.9.4-0ubuntu1
ProcCmdline: /usr/bin/yakuake
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: yakuake
StacktraceTop:
 QMenu::findIdForAction () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
 KMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.5
Title: yakuake crashed with SIGSEGV in QMenu::findIdForAction()
Uname: Linux 2.6.28-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Miguel Tadeu (mtadeunet) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:QMenu::findIdForAction () from /usr/lib/libQtGui.so.4
?? () from /usr/lib/libQtGui.so.4
?? () from /usr/lib/libQtGui.so.4
QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
KMenu::mouseReleaseEvent (this=0x8355ea0, e=0xbfdb4d78)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in yakuake:
importance: Undecided → Medium
Revision history for this message
Thomas David (nemphis) wrote :

Can confirm this bugreport. After setting width to 100% and height to 40%, yakuake freezed and finally crashed.

Changed in yakuake:
status: New → Confirmed
Revision history for this message
Tomasz Czapiewski (xeros) wrote :

I can confirm that yakuake segfaults (not freezing) after setting width or height different to defaults.
Clean kubuntu jaunty-desktop-amd64 install from 2009-03-30 snapshot, installed ~30-60 minutes ago, upgraded just after install (now), default settings (+ "yakuake" and "kde" packages installed), no extra repositories.
No additional info to that it just segfaulted (tried "yakuake --nofork" run in konsole), no apport dialog window.
Tested few times - everytime the same result.
Locale: PL.
Package: yakuake-2.9.4-0ubuntu1 (amd64)

Revision history for this message
Tomasz Czapiewski (xeros) wrote :

And now yakuake has crashed when it was hidden and not in use - apport dialog has appeared and apport properly found this bug by bug report subject.

Revision history for this message
anystupidname (anystupidassname) wrote :

NOTE: I'm unable to find the duplicate that bugs.launchpad.net is referring to.

BUG REPORT: I confirm the SIGSEGV yakuake (versions 2.9.4) is consistently reproducible by trying to change the height and/or width via the menu in the status bar of yakuake. This happens on 2 out of 3 machines I'm running Jaunty on and use very frequently. I tried to provide a stacktrace/backtrace but need some assistance with gdb or whatever this should be done with. Further, the built in crash handler states the backtrace appears to contain no useful information possibly because (no debugging symbols found). Sorry, I'm not experienced/good with debugging at this point. Possibly relevant: when I run yakuake from a terminal, on the 2 machines with the problem, there is a non fatal error "(<unknown>:10917): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks"," and on the one machine I don't have the problem on, I do not get this error.

WORKAROUND: If you use the same menu to open the configure yakuake window first and then change the width and/or height in this new window, there is no signal 11 and yakuake continues to run normally.

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.