Bug 114741 – Conglomerate crashes when typing in text

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 114741 - Conglomerate crashes when typing in text


Summary:	Conglomerate crashes when typing in text


Status:	VERIFIED INCOMPLETE

Product:	conglomerate
Classification:	Other
Component:	Code
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	conglomerate list
QA Contact:	conglomerate list

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-06-09 01:17 UTC by Ian Scott
Modified:	2009-08-15 18:40 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ian Scott 2003-06-09 00:48:46 UTC

Package: conglomerate
Severity: normal
Version: 0.5.1
Synopsis: Conglomerate crashes when typing in text
Bugzilla-Product: conglomerate
Bugzilla-Component: Code
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
When typing in text, Conglomerate crashes

Steps to reproduce the problem:
1. Open Conglomerate and choose the first option in the Creation
wizard.
2. Remove the text under the 'Title' section.
3. Start typing.

Actual Results:
As soon as first keystroke is made, Conglomerate crashes.

Expected Results:
The text being typed should show up.

How often does this happen?
All the time.

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/local/bin/conge'

[New Thread 1087024576 (LWP 14321)]
0xffffe002 in ?? ()

+ Trace 37601

Thread 1 (Thread 1087024576 (LWP 14321))

#0 ??
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 abort
from /lib/tls/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 cong_editor_widget_get_element_editor_for_node
at cong-editor-widget.c line 760
#8 key_press_event_handler
at cong-editor-widget.c line 374
#9 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#15 _gtk_window_query_nonaccels
from /usr/lib/libgtk-x11-2.0.so.0
#16 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#26 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#31 main
at main.c line 420
#32 __libc_start_main
from /lib/tls/libc.so.6
#0 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-08 20:48 -------

Reassigning to the default owner of the component, conglomerate-auto@lists.copyleft.no.

Comment 1 Elijah Newren 2003-06-09 02:50:14 UTC

Appears to be a unique stack trace, according to the
simple-dup-finder.  Marking priority->high & severity->critical (it's
a crasher), adding bugsquad keyword, and marking as new

Comment 2 David Malcolm 2003-06-15 09:32:49 UTC

Does this recur under 0.5.3?  I believe the fix I made for 114960
might also fix this ("backspace" at the top of the file used to put
the cursor into an invalid state, which would cause a crash soon after)

Comment 3 Geert Stappers 2003-09-18 13:25:14 UTC

Three months later and several releases: time to close this expired bug.

Comment 4 Geert Stappers 2003-09-19 08:58:10 UTC

playing with Resolutions Field.