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 340663 - Crash when trying to type into a FirstName block
Crash when trying to type into a FirstName block
Status: RESOLVED WONTFIX
Product: conglomerate
Classification: Other
Component: Code
unspecified
Other other
: High critical
: ---
Assigned To: conglomerate list
conglomerate list
gnome[unmaintained]
: 343873 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-04 17:27 UTC by chris
Modified: 2017-12-22 12:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description chris 2006-05-04 17:27:27 UTC
Distribution: Ubuntu 5.10 (breezy)
Package: conglomerate
Severity: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash when trying to type into a FirstName block
Bugzilla-Product: conglomerate
Bugzilla-Component: Code
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:

My document already has an author, with a first name and surname, but
Conglomerate just shows an empty author block. Trying to add a new one
and to type a name into it caused a crash.

Steps to reproduce the crash:
1. Open my existing docbook document
2. Right-click the empty author section
3. Add a new author section as a sibling
4. Choose to add a first name
5. Try to type the author's first name

Expected Results:

cg allows me to type the authors name, and doesn't crash.

Actual results:

cg did not respond to my repeated attempt to highlight the first name
field and type into it. Eventually it crashed.

How often does this happen?

Only once so far.

Additional Information:

Attached the file I was trying to edit.

This is version 0.9.0debian3ubuntu1.

Debugging Information:

Backtrace was generated from '/usr/bin/conglomerate'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224918592 (LWP 28291)]
[New Thread -1235543120 (LWP 28300)]
[New Thread -1235215440 (LWP 28298)]
[New Thread -1234949200 (LWP 28296)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224918592 (LWP 28291))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 cong_editor_area_line_get_width_used_up_to
  • #10 cong_area_creation_geometry_new
  • #11 cong_editor_line_manager_get_first_node
  • #12 cong_editor_line_manager_add_node
  • #13 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 cong_editor_node_line_regeneration_required
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 cong_document_private_node_set_text
  • #24 cong_node_modification_set_text_new
  • #25 cong_command_add_node_set_text
  • #26 cong_location_del_next_char
  • #27 cong_cursor_del_prev_char
  • #28 cong_editor_widget3_get_preedit_data
  • #29 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_window_activate_key
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #39 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #42 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #43 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #47 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #48 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #50 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 main
  • #0 __kernel_vsyscall



-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |



------- Bug created by bug-buddy at 2006-05-04 17:27 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.

Comment 1 Kevin Kubasik 2006-06-05 07:04:18 UTC
*** Bug 343873 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2017-12-22 12:48:27 UTC
Conglomerate is not under active development anymore. It is currently unlikely that there will be any further Conglomerate development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping (bug 685689) to reflect reality. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.