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 80673 - Crash on hitting "post article"
Crash on hitting "post article"
Status: RESOLVED DUPLICATE of bug 76350
Product: Pan
Classification: Other
Component: general
0.11.2.91
Other other
: Normal normal
: ---
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-05-03 10:37 UTC by Doug Palmer
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Doug Palmer 2002-05-03 10:37:32 UTC
Package: Pan
Severity: minor
Version: 0.11.2.91
Synopsis: Crash on hitting "post article"
Bugzilla-Product: Pan
Bugzilla-Component: general

Description:
Don't really know how to reproduce it. I was following up a posting. 

The follow-up consisted of editing down 74 lines to 4 and adding a 2 line comment.
When I hit the "post article" button, pan crashed.
I had followed up on one post (in the same thread) previously.


Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 2758)]
[New Thread 2049 (LWP 2759)]
[New Thread 1026 (LWP 2760)]
0x405c6ca9 in __wait4 ()
   from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 message_window_new
  • #7 message_window_new
  • #8 message_window_new
  • #9 message_window_new
  • #10 message_window_new
  • #11 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #12 gtk_handlers_run
    from /usr/lib/libgtk-1.2.so.0
  • #13 gtk_signal_real_emit
    from /usr/lib/libgtk-1.2.so.0
  • #14 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #15 gtk_button_clicked
    from /usr/lib/libgtk-1.2.so.0
  • #16 gtk_real_button_released
    from /usr/lib/libgtk-1.2.so.0
  • #17 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #18 gtk_signal_real_emit
    from /usr/lib/libgtk-1.2.so.0
  • #19 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #20 gtk_button_released
    from /usr/lib/libgtk-1.2.so.0
  • #21 gtk_button_button_release
    from /usr/lib/libgtk-1.2.so.0
  • #22 gtk_marshal_BOOL__POINTER
    from /usr/lib/libgtk-1.2.so.0
  • #23 gtk_signal_real_emit
    from /usr/lib/libgtk-1.2.so.0
  • #24 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #25 gtk_widget_event
    from /usr/lib/libgtk-1.2.so.0
  • #26 gtk_propagate_event
    from /usr/lib/libgtk-1.2.so.0
  • #27 gtk_main_do_event
    from /usr/lib/libgtk-1.2.so.0
  • #28 gdk_event_dispatch
    from /usr/lib/libgdk-1.2.so.0
  • #29 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #30 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #31 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #33 main
  • #34 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 message_window_new
  • #7 message_window_new




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-03 06:37 -------

Unknown version 1.2.x in product Pan. Setting version to the default, "unspecified".
The original reporter (doug@charvolant.org) 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, charles@rebelbase.com.

Comment 1 Charles Kerr 2002-05-03 15:54:13 UTC
mostly fixed in 0.11.3; fixed in 0.11.91

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