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 147309 - Balsa crashes when updating mailbox settings
Balsa crashes when updating mailbox settings
Status: RESOLVED FIXED
Product: balsa
Classification: Other
Component: general
2.1.x
Other other
: Normal critical
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-07-10 23:16 UTC by W. Michael Petullo
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description W. Michael Petullo 2004-07-10 23:18:03 UTC
Distribution: Fedora Core release Rawhide (Rawhide)
Package: balsa
Severity: critical
Version: GNOME2.6. 2.1.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Balsa crashes when updating mailbox settings
Bugzilla-Product: balsa
Bugzilla-Component: general
Bugzilla-Version: 2.1.x
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
Balsa crashes when updating mailbox settings on a PowerPC GNU/Linux
system.

Steps to reproduce the crash:
1.  Click on Settings->Properties.

2.  Click on the "Mail Servers" tab, select a mail server and click
"Modify." 

3.  Click on the "Advanced" tab.

4.  Modify a setting.  For example, change TLS support from "Possible"
to "Never."

5.  Click "Update."  Balsa consistently crashes at this point. 

Expected Results:
The settings should update.

How often does this happen?
Every time.

Additional Information:



Debugging Information:

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 805421152 (LWP 3868)]
0x0fafd174 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread 805421152 (LWP 3868))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 libbalsa_mailbox_imap_update_url
    at mailbox_imap.c line 320
  • #5 libbalsa_mailbox_imap_update_url
    at mailbox_imap.c line 320
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 libbalsa_server_set_host
    at server.c line 217
  • #11 update_imap_mailbox
    at mailbox-conf.c line 748
  • #12 mailbox_conf_update
    at mailbox-conf.c line 815
  • #13 conf_response_cb
    at mailbox-conf.c line 432
  • #14 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_by_name
    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_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_dialog_new_with_buttons
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_button_get_relief
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_button_get_relief
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #38 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #39 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #42 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 gdk_x11_register_standard_event_type
    from /usr/lib/libgdk-x11-2.0.so.0
  • #46 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #47 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #48 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #50 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 main
    at main.c line 562
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-10 19:18 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "balsa".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 W. Michael Petullo 2004-07-10 23:22:18 UTC
I'm sorry that there is some information missing from this bug report, but I
wanted to try to use GNOME's bug buddy tool.  This bug rears its nasty head in
balsa 2.1.91.  It was also in 2.1.90.  I am running balsa on a PowerPC-based
GNU/Linux system.
Comment 2 W. Michael Petullo 2004-08-22 23:10:37 UTC
I don't see this bug anymore in 2.2.0.