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 105471 - sent a "reply to" email from the mbox
sent a "reply to" email from the mbox
Status: VERIFIED DUPLICATE of bug 69587
Product: balsa
Classification: Other
Component: general
1.2.x
Other other
: Normal normal
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-02-07 06:16 UTC by webmaster
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description webmaster 2003-02-07 06:17:28 UTC 
Package: balsa
Severity: normal
Version: 1.2.4
Synopsis: sent a "reply to" email from the mbox
Bugzilla-Product: balsa
Bugzilla-Component: general

Description:
opened Balsa. Then opened mbox. Double click on emai message. Write a "reply to"
message to sender. Try to send mail. 


Debugging Information:

[New Thread 1024 (LWP 4855)]
0x401d83b9 in wait4 () from /lib/libc.so.6

+ Trace 33574

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 gtk_type_check_object_cast
    from /usr/lib/libgtk-1.2.so.0
  • #7 libbalsa_mailbox_pop3_check
  • #8 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-07 01:17 -------

The original reporter (webmaster@perpetualpc.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, pawsa@theochem.kth.se.
Comment 1 Pawel Salek 2003-02-07 08:53:33 UTC 
This has been fixed before August 2002.

Please visit http://balsa.gnome.org/ and upgrade to 1.4.2 or 2.0.6
balsa-1.2.x releases are not supported any longer.

*** This bug has been marked as a duplicate of 69587 ***