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 169276 - crashed while creating new XHTML doc
crashed while creating new XHTML doc
Status: RESOLVED DUPLICATE of bug 153358
Product: conglomerate
Classification: Other
Component: Code
unspecified
Other other
: Normal normal
: ---
Assigned To: conglomerate list
conglomerate list
Depends on:
Blocks:
 
 
Reported: 2005-03-05 08:59 UTC by abbi
Modified: 2005-03-05 14:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description abbi 2005-03-05 08:59:41 UTC
Distribution: SuSE Linux 9.2 (i586)
Package: conglomerate
Severity: normal
Version: GNOME2.6. unspecified
Gnome-Distributor: SUSE
Synopsis: crashed while creating new XHTML doc
Bugzilla-Product: conglomerate
Bugzilla-Component: Code
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
It is impossible to create a XHTML document using the wizzard.

Steps to reproduce the crash:
1. I was starting Conglomerate for the really first time after install.
2. Tried to create one new document with wizard.
3. I choosed  random content.
4. choosed XHTML 1.0.
5. crash

Expected Results:
see an editor window

How often does this happen?
really fresh install

Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/conglomerate'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 1089382240 (LWP 11199)]
0xffffe410 in ?? ()

Thread 1 (Thread 1089382240 (LWP 11199))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 raise
    from /lib/tls/libc.so.6
  • #12 abort
    from /lib/tls/libc.so.6
  • #13 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #14 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #15 factory_action_callback_random
  • #16 cong_document_factory_invoke_action_callback
  • #17 final_page_finish
  • #18 g_cclosure_marshal_VOID__OBJECT
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #20 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #23 gnome_druid_page_finish
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #24 gnome_druid_next_callback
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #25 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #27 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #30 gtk_button_clicked
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #31 gtk_real_button_released
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #32 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #33 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #34 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #35 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #38 gtk_button_released
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #39 gtk_button_button_release
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #40 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #41 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #42 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #43 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #46 gtk_widget_event_internal
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #47 gtk_propagate_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #48 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #49 gdk_event_dispatch
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #50 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #51 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #52 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #53 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #54 main
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-05 03:59 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "conglomerate".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was abbi@elster-punkt.de.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Richard Hoelscher 2005-03-05 14:54:50 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 153358 ***