Bug 139427 – Balsa crashes when attempting to double-click or press enter on mailboxes

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 139427 - Balsa crashes when attempting to double-click or press enter on mailboxes


Summary:	Balsa crashes when attempting to double-click or press enter on mailboxes


Status:	RESOLVED INCOMPLETE

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

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Balsa Maintainers
QA Contact:	Balsa Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-04-07 22:51 UTC by Luke Yelavich
Modified:	2006-07-03 13:31 UTC

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

Description Luke Yelavich 2004-04-07 22:51:29 UTC

When running Balsa, attempting to either arrow and press enter on, or double-
click on any of the mail boxes causes Balsa to crash.

I am running GNOME 2.6 with Balsa 2.0.17, on Slackware 9.1 with kernel 2.6.5.

Balsa 2.0.17 backtrace:

Starting program: /opt/gnome-2.6/bin/balsa 
[New Thread 16384 (LWP 1865)]
[New Thread 32769 (LWP 1878)]
[New Thread 16386 (LWP 1879)]
[New Thread 32771 (LWP 1880)]

Program received signal SIGINT, Interrupt.
[Switching to Thread 32771 (LWP 1880)]
0x41283f32 in loser_poll () from /lib/libc.so.6
(gdb) thread apply all bt

+ Trace 45820

Thread 3 (Thread 16386 (LWP 1879))

#0 do_sigsuspend
from /lib/libc.so.6
#1 sigsuspend
from /lib/libc.so.6
#2 __pthread_wait_for_restart_signal
from /lib/libpthread.so.0
#3 pthread_cond_wait
from /lib/libpthread.so.0
#4 pthread_cond_wait
from /lib/libc.so.6
#5 giop_recv_buffer_get
at giop-recv-buffer.c line 707
#6 ORBit_small_invoke_stub
at orbit-small.c line 657
#7 ORBit_small_invoke_stub_n
at orbit-small.c line 575
#8 ORBit_c_stub_invoke
at poa.c line 2640
#9 Bonobo_Unknown_unref
at Bonobo_Unknown-stubs.c line 23
#10 spi_atk_emit_eventv
at bridge.c line 585
#11 spi_atk_bridge_signal_listener
at bridge.c line 953
#12 signal_emit_unlocked_R
at gsignal.c line 2402
#13 g_signal_emit_valist
at gsignal.c line 2195
#14 g_signal_emit_by_name
at gsignal.c line 2263
#15 model_row_changed
at gailtreeview.c line 2688
#16 _gtk_marshal_VOID__BOXED_BOXED
at gtkmarshalers.c line 1028
#17 g_closure_invoke
at gclosure.c line 437
#18 signal_emit_unlocked_R
at gsignal.c line 2436
#19 g_signal_emit_valist
at gsignal.c line 2195
#20 g_signal_emit
at gsignal.c line 2239
#21 gtk_tree_model_row_changed
at gtktreemodel.c line 1354
#22 gtk_tree_store_set_valist
at gtktreestore.c line 1018
#23 gtk_tree_store_set
at gtktreestore.c line 1047
#24 bmbl_node_style
at balsa-mblist.c line 1584
#25 balsa_mblist_update_mailbox
at balsa-mblist.c line 1436
#26 real_open_mbnode
at main-window.c line 1463
#27 pthread_start_thread
from /lib/libpthread.so.0
#28 pthread_start_thread_event
from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 1865))

#0 do_sigsuspend
from /lib/libc.so.6
#1 sigsuspend
from /lib/libc.so.6
#2 __pthread_wait_for_restart_signal
from /lib/libpthread.so.0
#3 __pthread_alt_lock
from /lib/libpthread.so.0
#4 pthread_mutex_lock
from /lib/libpthread.so.0
#5 pthread_mutex_lock
from /lib/libc.so.6
#6 gdk_threads_impl_lock
at gdk.c line 503
#7 gdk_event_check
at gdkevents-x11.c line 2107
#8 g_main_context_check
at gmain.c line 2397
#9 g_main_context_iterate
at gmain.c line 2519
#10 g_main_loop_run
at gmain.c line 2726
#11 gtk_main
at gtkmain.c line 1172
#12 main
at main.c line 530
#13 __libc_start_main
from /lib/libc.so.6
#0 loser_poll
from /lib/libc.so.6

Comment 1 Luke Yelavich 2004-06-09 22:22:28 UTC

The same crash also occurrs using Balsa 2.0.17 with Dropline GNOME 2.6.1 on 
Slackware 9.1.

Comment 2 Pawel Salek 2005-01-12 11:50:28 UTC

Can you try current balsa with current gtk? I have never seen such a crash...

Comment 3 Olav Vitters 2006-07-03 13:31:56 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!