Bug 384460 – crash in Drivel Journal Editor: Writting normally at Dri...

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 384460 - crash in Drivel Journal Editor: Writting normally at Dri...


Summary:	crash in Drivel Journal Editor: Writting normally at Dri...


Status:	RESOLVED DUPLICATE of bug 355701

Product:	drivel
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Todd Kulesza
QA Contact:	Todd Kulesza

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-10 18:52 UTC by sonojm
Modified:	2006-12-11 10:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description sonojm 2006-12-10 18:52:40 UTC

What were you doing when the application crashed?
Writting normally at Drivel.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 165896192 vsize: 165896192 resident: 17317888 share: 11567104 rss: 17317888 rss_rlim: -1
CPU usage: start_time: 1165773767 rtime: 1568 utime: 1524 stime: 44 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47887736225600 (LWP 5485)]
[New Thread 1082132816 (LWP 5489)]
(no debugging symbols found)
0x00002b8db9840eef in waitpid () from /lib/libpthread.so.0

+ Trace 93094

Thread 1 (Thread 47887736225600 (LWP 5485))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/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 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#11 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_clipboard_wait_for_contents
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_clipboard_wait_is_text_available
from /usr/lib/libgtk-x11-2.0.so.0
#25 journal_prop_new
#26 journal_prop_new
#27 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#32 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#38 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#39 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#40 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 André Klapper 2006-12-11 10:15:49 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 355701 ***