Bug 338140 – crashes while switching newsgroups

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 338140 - crashes while switching newsgroups


Summary:	crashes while switching newsgroups


Status:	RESOLVED INCOMPLETE

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

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Charles Kerr
QA Contact:	Pan QA Team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-04-11 21:45 UTC by Søren Boll Overgaard
Modified:	2008-06-08 13:00 UTC

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

Description Søren Boll Overgaard 2006-04-11 21:45:37 UTC

A Debian user submitted the following bug to the Debian Bug tracking system (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361511). The original submitter will provide a backtrace with debugging enabled on request:

Pan crashes while switching newsgroups.  While it is hard to determine exactly
when this will happen, to reproduce this, simply read all interesting messages
in one newsgroup, then switch newsgroups.  Eventually, it will crash.

For your debugging pleasure, I have included a backtrace from gdb, although it
contains no debugging symbols.

+ Trace 67578

#0 _gtk_tree_view_queue_draw_node
from /usr/lib/libgtk-x11-2.0.so.0
#1 gtk_tree_view_set_model
from /usr/lib/libgtk-x11-2.0.so.0
#2 _gtk_marshal_VOID__BOXED_BOXED_POINTER
from /usr/lib/libgtk-x11-2.0.so.0
#3 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#4 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#5 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#6 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#7 gtk_tree_model_rows_reordered
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_tree_store_set_value
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_tree_sortable_set_sort_column_id
from /usr/lib/libgtk-x11-2.0.so.0
#10 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char const*>
#11 atoi
#12 std::operator+<char, std::char_traits<char>, std::allocator<char> >
#13 atoi
#14 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>
#15 std::basic_string<char, std::char_traits<char>, std::allocator <char> >::basic_string<char*>
#16 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>
#17 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>
#18 ??
#19 g_main_context_is_owner
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
#25 ??
#26 __libc_start_main
from /lib/tls/libc.so.6
#27 ??

Comment 1 Søren Boll Overgaard 2006-04-21 21:42:17 UTC

The original submitter has provided a backtrace with debugging symbols.
It is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361511;msg=19

Comment 2 Charles Kerr 2006-04-25 22:06:06 UTC

does this persist in 0.95?

Comment 3 Roel van der Made 2006-09-09 20:02:31 UTC

Still persists in 0.110-1 on AMD64..

Comment 4 André Klapper 2006-10-25 15:18:07 UTC

reopening as per last comment.

Comment 5 Darren Albers 2007-01-09 13:32:39 UTC

Is this a dupe of 353577 and can be closed or is the problem still occurring?

Comment 6 Charles Kerr 2007-01-09 16:18:49 UTC

Haven't seen this crash in a long time.
I /think/ the causes for this crash were fixed in #357735 and #356206

Comment 7 Charles Kerr 2007-01-25 01:52:02 UTC

This still hasn't reappeared, so I'm closing this again
until someone says that it's still happening for them again.

Comment 8 André Klapper 2008-06-08 13:00:26 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!