Bug 373326 – crash in Drivel Journal Editor:

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 373326 - crash in Drivel Journal Editor:


Summary:	crash in Drivel Journal Editor:


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-11-10 10:02 UTC by sivakumart
Modified:	2006-11-10 10:55 UTC

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

Description sivakumart 2006-11-10 10:02:42 UTC

What were you doing when the application crashed?



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

Memory status: size: 69169152 vsize: 0 resident: 69169152 share: 0 rss: 19619840 rss_rlim: 0
CPU usage: start_time: 1163136355 rtime: 0 utime: 583 stime: 0 cutime:555 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230461264 (LWP 3966)]
[New Thread -1231893600 (LWP 3967)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 85004

Thread 1 (Thread -1230461264 (LWP 3966))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_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 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#13 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
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_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_clipboard_wait_for_contents
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_clipboard_wait_is_text_available
from /usr/lib/libgtk-x11-2.0.so.0
#28 journal_prop_new
#29 journal_prop_new
#30 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_chain_from_overridden
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_get_default_style
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_init
from /usr/lib/libgdk-x11-2.0.so.0
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 main
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-10 10:55:05 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 ***