Bug 362892 – Crash when editing journal entry

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 362892 - Crash when editing journal entry


Summary:	Crash when editing journal entry


Status:	RESOLVED DUPLICATE of bug 344826

Product:	drivel
Classification:	Deprecated
Component:	general
Version:	2.0.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Todd Kulesza
QA Contact:	Todd Kulesza

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-17 16:01 UTC by Don Scorgie
Modified:	2006-12-26 15:12 UTC

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

Description Don Scorgie 2006-10-17 16:01:21 UTC

1. Write lots of drivel in a journal entry.
2. Click at the start of the entry
3. Double click in empty space below the entry text (in the buffer area)
4. Produce the following stack trace

(Drivel version 2.0.3)

Note, I can only reproduce with 1 journal entry, though it does happen consistantly with that one entry.

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

Memory status: size: 84557824 vsize: 0 resident: 84557824 share: 0 rss: 25546752 rss_rlim: 0
CPU usage: start_time: 1161098615 rtime: 0 utime: 2698 stime: 0 cutime:2541 cstime: 0 timeout: 157 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".
[Thread debugging using libthread_db enabled]
[New Thread -1230628672 (LWP 25064)]
[New Thread -1232286816 (LWP 25065)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 76807

Thread 1 (Thread -1230628672 (LWP 25064))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#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 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
at gmessages.c line 552
#10 gtk_text_view_start_selection_drag
at gtktextview.c line 5720
#11 gtk_text_view_button_press_event
at gtktextview.c line 4003
#12 gtk_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#13 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#14 g_type_class_meta_marshal
at gclosure.c line 567
#15 IA__g_closure_invoke
at gclosure.c line 490
#16 signal_emit_unlocked_R
at gsignal.c line 2478
#17 IA__g_signal_emit_valist
at gsignal.c line 2209
#18 IA__g_signal_emit
at gsignal.c line 2243
#19 gtk_widget_event_internal
at gtkwidget.c line 3911
#20 IA__gtk_propagate_event
at gtkmain.c line 2211
#21 IA__gtk_main_do_event
at gtkmain.c line 1445
#22 gdk_event_dispatch
at gdkevents-x11.c line 2320
#23 IA__g_main_context_dispatch
at gmain.c line 2045
#24 g_main_context_iterate
at gmain.c line 2677
#25 IA__g_main_loop_run
at gmain.c line 2881
#26 IA__gtk_clipboard_wait_for_contents
at gtkclipboard.c line 1259
#27 IA__gtk_clipboard_wait_is_text_available
at gtkclipboard.c line 1488
#28 journal_prop_new
#29 journal_prop_new
#30 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#31 IA__g_closure_invoke
at gclosure.c line 490
#32 signal_emit_unlocked_R
at gsignal.c line 2440
#33 IA__g_signal_emit_valist
at gsignal.c line 2209
#34 IA__g_signal_emit
at gsignal.c line 2243
#35 gtk_widget_event_internal
at gtkwidget.c line 3911
#36 IA__gtk_propagate_event
at gtkmain.c line 2211
#37 IA__gtk_main_do_event
at gtkmain.c line 1445
#38 gdk_event_dispatch
at gdkevents-x11.c line 2320
#39 IA__g_main_context_dispatch
at gmain.c line 2045
#40 g_main_context_iterate
at gmain.c line 2677
#41 IA__g_main_loop_run
at gmain.c line 2881
#42 IA__gtk_main
at gtkmain.c line 1024
#43 main
#0 __kernel_vsyscall

Comment 1 Sebastien Bacher 2006-12-26 15:12:07 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 344826 ***