After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 164332 - Crash with segfault SIGSEGV and other problems when closing Print preview
Crash with segfault SIGSEGV and other problems when closing Print preview
Status: RESOLVED WONTFIX
Product: galeon
Classification: Deprecated
Component: general
1.3.19
Other Linux
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
: 172967 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-01-17 10:41 UTC by Loïc Minier
Modified: 2011-02-14 13:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Loïc Minier 2005-01-17 10:41:25 UTC
Hi,
You can get a crash when playing with the print preview as follow:
- open two tabs with some content
- in the first tab, click on File > Print...
- click on the Preview button, you should see the preview in the current tab
- close the tab with the "close tab" cross on the tab title, the print toolbar
will stay in the top region of the window
- click print

Also, this warning appears in the temrinal:
** (galeon:31808): WARNING **: Erreur GConf :
 Incohérence de type: « bool » attendu, obtenu « int » pour la clé
/apps/galeon/Print/printon

(litteral translation: GConf Error: Type incoherence: bool expected, got int for
gconf key /apps/galeon/Print/printon)

I'll try to submit a bt ASAP.

(This bug was submitted in the Debian BTS as <http://bugs.debian.org/276790>.)
[ assigned to general ]
Comment 1 Crispin Flowerday (not receiving bugmail) 2005-01-17 22:43:52 UTC
There certainly do seem to be issues with closing tabs that are in print preview
mode, although I don't get a crash ... 

I've raised the warning as bug 164396, as it is not related to the print preview
problems.
Comment 2 Loïc Minier 2005-01-18 08:35:28 UTC
Couldn't crash within gdb, but got a new warning:

** (galeon:22436): CRITICAL **: ppview_toolbar_close: assertion `GALEON_IS_EMBED
(embed)' failed
Comment 3 Loïc Minier 2005-01-18 08:39:41 UTC
Got it again with the next button, here's a very long stack trace:
(gdb) run
Starting program: /home/lool/tmp/galeon/galeon-1.3.19/debian/tmp/usr/bin/galeon 
[Thread debugging using libthread_db enabled]
[New Thread 1091518048 (LWP 22633)]
[New Thread 1112308656 (LWP 22634)]
[New Thread 1126149040 (LWP 22635)]
[New Thread 1134537648 (LWP 22636)]
[New Thread 1143520176 (LWP 22637)]
[Thread 1143520176 (LWP 22637) exited]
[New Thread 1151908784 (LWP 22638)]

** (galeon:22633): CRITICAL **: ppview_toolbar_close: assertion `GALEON_IS_EMBED
 (embed)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1091518048 (LWP 22633)]
0x080967e4 in toolbar_cmd_ppv_go_forward (action=0x85c8310, t=0x85c2be8)
    at ppview-toolbar.c:449
449             g_return_if_fail (GALEON_IS_EMBED (t->priv->embed));
(gdb) thread apply all bt full

Thread 1 (Thread 1091518048 (LWP 22633))

  • #0 toolbar_cmd_ppv_go_forward
    at ppview-toolbar.c line 449
  • #1 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #2 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #6 _gtk_action_emit_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_tool_button_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #27 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #35 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #39 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #40 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #41 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #42 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #43 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #44 main
    at galeon-main.c line 213

Comment 4 Crispin Flowerday (not receiving bugmail) 2005-04-09 20:32:03 UTC
*** Bug 172967 has been marked as a duplicate of this bug. ***
Comment 5 Akhil Laddha 2011-02-14 13:06:01 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore.

Galeon developers won't be fixing or back porting any fixes for this version. Please upgrade to latest stable Galeon version to receive bug fixes.
We are sorry it could not be fixed for your version.