yelp throws a segfault error and it doesn't start

Bug #710219 reported by maxadamo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yelp (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: yelp

I am getting the following error when trying to start yelp:

$ yelp
(yelp:6427): Gtk-CRITICAL **: IA__gtk_tool_button_new: assertion `icon_widget == NULL || GTK_IS_MISC (icon_widget)' failed
(yelp:6427): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(yelp:6427): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(yelp:6427): Gtk-CRITICAL **: IA__gtk_toolbar_insert: assertion `GTK_IS_TOOL_ITEM (item)' failed
(yelp:6427): Gtk-CRITICAL **: IA__gtk_tool_button_new: assertion `icon_widget == NULL || GTK_IS_MISC (icon_widget)' failed
(yelp:6427): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(yelp:6427): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(yelp:6427): Gtk-CRITICAL **: IA__gtk_toolbar_insert: assertion `GTK_IS_TOOL_ITEM (item)' failed
Segmentation fault
$

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: yelp 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-25.45~ppa1~loms~maverick-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Jan 30 16:41:40 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SourcePackage: yelp

Revision history for this message
maxadamo (massimilianoadamo) wrote :
Revision history for this message
Giuseppe Terrasi (giuseppeterrasi-deactivatedaccount) wrote :

same from me.

$yelp
(yelp:6669): Gtk-CRITICAL **: IA__gtk_tool_button_new: assertion `icon_widget == NULL || GTK_IS_MISC (icon_widget)' failed
(yelp:6669): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(yelp:6669): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(yelp:6669): Gtk-CRITICAL **: IA__gtk_toolbar_insert: assertion `GTK_IS_TOOL_ITEM (item)' failed
(yelp:6669): Gtk-CRITICAL **: IA__gtk_tool_button_new: assertion `icon_widget == NULL || GTK_IS_MISC (icon_widget)' failed
(yelp:6669): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(yelp:6669): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(yelp:6669): Gtk-CRITICAL **: IA__gtk_toolbar_insert: assertion `GTK_IS_TOOL_ITEM (item)' failed
Errore di segmentazione

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in yelp (Ubuntu):
status: New → Invalid
Revision history for this message
maxadamo (massimilianoadamo) wrote :

After six months this is the first answer that I receive.
By the way, I don't have maverick anymore, and you can do whatever you wish with this bug.... who cares, but those people who still uses maverick still have this issue, and you shouldn't have to close this bug, but you had to ask somebody to add these files!

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.