yelp crashed with SIGSEGV

Bug #180914 reported by Emilio Pozuelo Monfort
144
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yelp (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Binary package hint: yelp

100% reproducible segfault at startup. I'll add a backtrace after with xulrunner debugging symbols installed, since I don't think the retracer will be able to get a useful backtrace.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Jan 7 00:59:42 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: cdrom
Package: yelp 2.21.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: gnome-help ghelp:///usr/share/gnome/help/scribes/C/scribes.xml
ProcCwd: /home/emilio
ProcEnviron:
 SHELL=/bin/bash
 PATH=~/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: yelp
StacktraceTop:
 ?? () from /usr/lib/xulrunner-1.9b3pre/libxul.so
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/xulrunner-1.9b3pre/libxul.so
Title: yelp crashed with SIGSEGV
Uname: Linux pochu 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner vboxusers video

Related branches

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Program received signal SIGSEGV, Segmentation fault.
---Type <return> to continue, or q <return> to quit---
[Switching to Thread 0xb6c598d0 (LWP 30501)]
0xb5d160ae in EmbedPrivate::Realize (this=0x81ecd00, aAlreadyRealized=0xbfd2e218) at EmbedPrivate.cpp:293
293 EmbedPrivate.cpp: No such file or directory.
 in EmbedPrivate.cpp
Current language: auto; currently c++
(gdb) bt full
#0 0xb5d160ae in EmbedPrivate::Realize (this=0x81ecd00, aAlreadyRealized=0xbfd2e218) at EmbedPrivate.cpp:293
 webBrowser = {<nsCOMPtr_base> = {mRawPtr = 0x0}, <No data fields>}
 supportsWeak = {<nsCOMPtr_base> = {mRawPtr = 0x0}, <No data fields>}
 weakRef = {<nsCOMPtr_base> = {mRawPtr = 0x80d70c8}, <No data fields>}
 uriListener = {<nsCOMPtr_base> = {mRawPtr = 0xb7c20d4f}, <No data fields>}
 mozWidget = {<nsCOMPtr_base> = {mRawPtr = 0xbfd2e1b8}, <No data fields>}
 tmp_window = <value optimized out>
 data = (gpointer) 0x81ecd00
#1 0xb5d1471b in gtk_moz_embed_realize (widget=0x8174a58) at gtkmozembed2.cpp:460
 embed = (GtkMozEmbed *) 0x8174a58
 embedPrivate = (EmbedPrivate *) 0x81ecd00
 attributes = {title = 0xb7acb052 "\211�\205�t\035\213\006\213v\b�@\006\004t�\213U\024\211T$\004\213", event_mask = 2, x = 0, y = 63, width = 600,
  height = 357, wclass = GDK_INPUT_OUTPUT, visual = 0x80ac400, colormap = 0x80ae410, window_type = GDK_WINDOW_CHILD, cursor = 0x1,
  wmclass_name = 0xb7b0efc0 "U\211�\213E\b\213P\f��\001t\022�@\021\004t\f\204�x\b]��\017\034", wmclass_class = 0xb7799a93 "\201��K\001",
  override_redirect = -1210253956, type_hint = 135755880}
 rv = <value optimized out>
 alreadyRealized = 0
 __PRETTY_FUNCTION__ = "void gtk_moz_embed_realize(GtkWidget*)"
#2 0x08059c4a in ?? ()
No symbol table info available.
#3 0xb778940f in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#4 0xb777a019 in ?? () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#5 0x080d80a0 in ?? ()
No symbol table info available.
#6 0x00000000 in ?? ()
No symbol table info available.
(gdb)

Changed in yelp:
importance: Undecided → High
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/xulrunner-1.9b3pre/libxul.so
?? ()
?? ()
?? ()
?? () from /usr/lib/xulrunner-1.9b3pre/libxul.so

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
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Confirming based on number of dups

Changed in yelp:
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package yelp - 2.21.1-0ubuntu3

---------------
yelp (2.21.1-0ubuntu3) hardy; urgency=low

  * debian/control.in:
    - really update the xulrunner requirement (LP: #180914)

 -- Sebastien Bacher <email address hidden> Tue, 08 Jan 2008 13:08:36 +0100

Changed in yelp:
status: Confirmed → Fix Released
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Hello,
This seems not fixed to me. Can I reopen the bug?

Changed in yelp:
status: Fix Released → Triaged
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Andrea, what's the output of 'dpkg -l xulrunner-1.9' and 'dpkg -l yelp'?

This is fixed here with the yelp update.

Revision history for this message
Sebastien Bacher (seb128) wrote :

What architecture do you use? Are you sure that's the same crash?

Changed in yelp:
assignee: nobody → desktop-bugs
status: Triaged → Incomplete
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Yes, this seems the same problem: yelp doesn't start and crashes with a core dump.

Version of xulrunner-1.9: 1.9~b3~cvs2008
Version of yelp: 2.21.1-0ubuntu
Distribution: 8.04
Kernel: 2.6.24-3-generic
Architecture: i686

Revision history for this message
Sebastien Bacher (seb128) wrote :

the yelp version is truncated

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Sorry! 2.21.1-0ubuntu2

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Andrea, that's fixed in 2.21.1-0ubuntu3. Feel free to re open the bug if you still have the crash with it, thanks.

Changed in yelp:
status: Incomplete → Fix Released
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

I'm very sorry. I'll read all the janitor's comment next time :)

Revision history for this message
Andrew Frank (frank-geoinfo) wrote :

encountered with an up-to-date 8.04 today
-
i guess it is the same problem, but i am not certain (what is better, reporting a bug again (as a duplicate) or guess)?

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Andrew, report a new one but don't mark it as a duplicate.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Andrew, please report a new one with apport. thanks.

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.