Re: Segmentation fault with iceape, etc.
On Wed, Apr 13, 2011 at 8:02 PM, Don J <dlia@noark.net> wrote:
> For a week or more, I've been having problems with iceape and a few
> other programs. As far as I can see, they get a segmentation fault
> and just disappear. From the debugging and back traces that I've
> done, it appears that I may be missing or have corrupted files
> relating to Gtk and GLib. Unfortunately, I'm not savvy enough to
> decipher the information and correct the problem. I could use a
> little assistance with this.
>
> I am running KDE and wheezy with the updated kernel 2.6.38-2-686 #1
> SMP. The new kernel had no effect on the problem. Wheezy is up to
> date. iceape version is 2.0.13-1
>
> Some of the operations which cause a seg fault include trying to send
> email with iceape (always), sometimes opening a particular web page
> will do it, and it appears the acroread will always do it (while other
> pdf readers will not). At times, gmail started from the iceape web
> browser will also fault. I'm only able to send email via using Google
> Chrome to start gmail.
>
> I installed iceape-dbg and followed the directions in the file at
> /usr/share/bug/iceape-dbg/presubj
>
> Starting iceape in safe mode with "iceape -safe-more" command line
> resulted in segmentation fault; following the suggestion to use the
> MOZILLA_DISABLE_PLUGINS=1 resulted in many warning and "critical" as
> you can see in the following screen capture:
>
> don@kali:~$ iceape -safe-mode
> Segmentation fault
> don@kali:~$ MOZILLA_DISABLE_PLUGINS=1 iceape
>
> (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
> 'gtk-go-back-ltr' for stock: Icon 'gtk-go-back-ltr' not present in
> theme
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
> `base_pixbuf != NULL' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
> assertion `pixbuf != NULL' failed
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
> 'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
> in theme
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
> `base_pixbuf != NULL' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
> assertion `pixbuf != NULL' failed
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
> 'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
> in theme
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
> `base_pixbuf != NULL' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
> assertion `pixbuf != NULL' failed
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
> 'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
> in theme
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
> `G_IS_OBJECT (object)' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
> `base_pixbuf != NULL' failed
>
> (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
> assertion `pixbuf != NULL' failed
>
> (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
> `G_IS_OBJECT (object)' failed
> Segmentation fault
> don@kali:~$
>
> I also ran gdb using the command line "iceape -g" which resulted in
> many lines and eventual segmentation fault. A "bt" was also done per
> instructions. I have this in a file if it would help diagnosing my
> problem, but I have a feeling that the above information may be
> adequate for someone to tell me if I am missing files or something.
>
> I also tried installing firefox and it too bombs out the same way as
> iceape, so my suspicion is iceape is OK and it is external file(s).
>
> Can someone interpret the warnings and critical stuff for me? I'm not
> a newbie, but I have little experience in this area.
>
> I do have two other problems that has recently popped up, and I do not
> know if they are related to this problem or not, but I'll mention just
> in case it should give any more clues:
> (1) iceape, when closed by either the X in upper right corner of KDE
> or thru file->exit, continues to operate. I have to kill the process
> in order to restart iceape several minutes later.
> (2) the icons on my desktop do not maintain their position if
> rebooted, and using icons->sort does not respond properly.
BTW, not just iceape. I'm experiencing the same thing with icedove
and iceweasel under unstable. I haven't debugged anything though, :-(
Thanks,
--
Javier.
Reply to: