Bug 564628 – Pan segmentation fault when posting

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 564628 - Pan segmentation fault when posting


Summary:	Pan segmentation fault when posting


Status:	RESOLVED INCOMPLETE

Product:	Pan
Classification:	Other
Component:	general
Version:	pre-1.0 betas
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Charles Kerr
QA Contact:	Pan QA Team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-12-15 16:45 UTC by bowo
Modified:	2008-12-30 21:30 UTC

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

Description bowo 2008-12-15 16:45:35 UTC

Steps to reproduce:
1. run pan
2. post to newsgroup
3. close post window or send article
4. segmentation fault


Stack trace:
(gdb) run
Starting program: /usr/bin/pan 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb74136d0 (LWP 5387)]
[New Thread 0xb70a4b90 (LWP 5390)]
[New Thread 0xb68a3b90 (LWP 5391)]
[New Thread 0xb60a2b90 (LWP 5392)]
[New Thread 0xb58a1b90 (LWP 5393)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb74136d0 (LWP 5387)]
0xb79731c8 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
(gdb) thread apply all bt

+ Trace 210828

Thread 1 (Thread 0xb74136d0 (LWP 5387))

#0 g_main_context_prepare
from /usr/lib/libglib-2.0.so.0
#1 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#2 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#3 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#4 main


Other information:
* Distribution: Archlinux
* Pan 0.133
* Glib2 2.18.3
* gtk2 2.14.5

Comment 1 assasukasse 2008-12-24 11:57:25 UTC

confirmed on debian testing
Pan 0.132 segfaults every time is posting a message.

(gdb) bt

+ Trace 211040

Thread 1 (Thread 0xb73c16c0 (LWP 6108))

#0 g_main_context_prepare
from /usr/lib/libglib-2.0.so.0
#1 ??
from /usr/lib/libglib-2.0.so.0
#2 ??
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
from /usr/lib/libglib-2.0.so.0
#9 ??
#10 ??
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
from /lib/libc.so.6
#18 ??
from /lib/libpthread.so.0
#19 ??
from /lib/libpthread.so.0
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
from /usr/lib/libglib-2.0.so.0
#25 ??
from /usr/lib/libglib-2.0.so.0
#26 ??
#27 ??
from /lib/libpthread.so.0
#28 ??
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0

Comment 2 André Klapper 2008-12-30 21:30:47 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!