*Constant* pidgin crashes last ~2 weeks [gfire issue?]?

FrozenFox · 2009-05-27 22:04:24

Hellos,

Wasn't sure where else to put this, but anyway..

Has anyone noticed *CONSTANT* pidgin crashes in the last ~ 2 weeks? It was happening to me with 2.5.5 + these then-testing packages (but with the same pidgin, not having any issues before):

binutils dbus dbus-core gcc gcc-libs gmp
and the following, which were later moved to stable but caused no crashing afaict..
glibc kernel26 kernel-headers
i reverted dbus and dbus-core but still had crashes, so I'm guessing that's not it.
..but nothing else in the list pops out at me as an issue, mostly development stuff.. eh?

Since nobody else posted anything for such a popular program, I figured perhaps it was an issue on my end and waited to see what happened with later stuff.

Reverting to all core/extra packages back before said packages were moved to stable, no further crashes. It may've been a coincidence however [EDIT: From the discussion later in this thread, it appears to be just that, yet another coincidence with amazing odds of occurence..typical for me.], and I can't voluntarily reproduce these crashes, so I didn't file a report..

Well, all of the above have since been moved to stable, and pidgin's been updated. annnd.. crashes are back. pidgin -d and gdb output seems to provide no glaring problem -- however I also don't know what to look for. I'm going to try submitting it to the pidgin devs anyway if nobody else knows. If anyone wants pidgin -d, I'll try to get it and post it too, but it seems to have nothing in common that I can tell between several pidgin -d outputs and near the end where it crashes.

Ideas? I can't seem to find anything on google..

On that note, I seem to notice after every time it crashes, in the system log it wrote down that someone quite recently changed their status or status message esp. on MSN.. may be a coincidence too, but the timing is awfully close..

Last edited by FrozenFox (2009-06-04 20:06:42)

Оо · 2009-05-28 03:28:14

I've experienced similar crashes, same time period... Have you upgraded to 2.5.6?

FrozenFox · 2009-05-28 04:40:51

$ cat /var/log/pacman.log | grep pidgin | grep -v pidgin-
[2009-03-13 09:12] installed pidgin (2.5.5-1)
[2009-04-06 01:30] upgraded pidgin (2.5.5-1 -> 2.5.5-2)
[2009-05-25 14:08] upgraded pidgin (2.5.5-2 -> 2.5.6-1)
[2009-05-27 21:09] upgraded pidgin (2.5.6-1 -> 2.5.5-2)
[2009-05-27 22:51] upgraded pidgin (2.5.5-2 -> 2.5.6-1)

I was pretty sure I did, and pacman.log suggests so too. I downgraded from .6 to .5, and only reason I'd do that is because the crashes didn't stop.

Thanks though..

Last edited by FrozenFox (2009-05-28 04:41:06)

wonder · 2009-05-28 05:42:57

the output is useless. you have to recompile pidgin with --debug or whatever is the parameter to ./configure.
http://developer.pidgin.im/wiki/GetABacktrace

FrozenFox · 2009-05-28 17:25:10

A friend who apparently programs MUDs just told me the same thing last night, sorry I forgot to edit. I actually did recompile pidgin, but I obvously did something wrong somewhere in the pkgbuild ><. Will start over.

I've edited the main post until I find the time to do that. Oddly, I've not had any crashes for a while.. perhaps a coincidence or something else caused similar random-ish crashes last time I updated.. blah.

EDIT: yep.. more crashing. 2.5.6. ffs.

Last edited by FrozenFox (2009-05-28 20:46:58)

ngoonee · 2009-05-28 21:49:10

I've been getting this with pidgin since 2.5.4 I think. Also have a similar issue with the win32 build of pidgin. It does seem MSN related, someday soon I'll stay off MSN a few days to see if that helps.

What's the frequency of your crashing? I'd say mine is about once or twice a day, my machine is on maybe 14 hours a day.

FrozenFox · 2009-05-29 03:27:23

ngoonee wrote:

I've been getting this with pidgin since 2.5.4 I think. Also have a similar issue with the win32 build of pidgin. It does seem MSN related, someday soon I'll stay off MSN a few days to see if that helps.
What's the frequency of your crashing? I'd say mine is about once or twice a day, my machine is on maybe 14 hours a day.

I'd say about 5 times a day or so generally (on 24/7), but sometimes it just doesn't stop. I had it crash on me ~6 times in just ~3 minutes before. I can also say this is nothing triggered by the user apparently, as it crashed earlier on me when I was away from the pc.

In other news, it seems I forgot to edit makepkg.conf to stop it from stripping symbols, and I was a moron with the pkgbuild and commented out what I actually added before compiling it, making said action pointless twice over. Should be good now.. I hope.. it's running in gdb now, hours and hours with no crashes yet oddly.. conveniently, right around the time I actually *wanted* it to crash. I will edit the first topic n title with the new backtrace stuff as soon as it crashes.

Last edited by FrozenFox (2009-05-29 03:36:31)

FrozenFox · 2009-05-29 04:27:47

sigh.

Disabling msn didn't help for me. Disabling gfire now.. maybe that has something to do with it. I have no idea. do any of you use it?..

The output no longer says its missing the symbols at the top as it did before, but now it says it when I try to pick up the backtrace, which from what I understand is still useless output. I compiled pidgin with --enable-debug on configure and !strip in options... wtf am I doing wrong? I don't understand any of this stuff about gdb really, but I was hoping it would lead to a solution from someone who does... is it supposed to be this way and I just need to recompile the packages containing the referenced libraries to un-strip them..?.. or is there something screwed up with pidgin being compiled wrong still?..

GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
[Previously there was a nag about missing symbol table stuff here.. the above fixed it..]
(gdb)

[buuuuuuuuuuut........ here after doing bt full.....]
#0  0xb7ff2424 in __kernel_vsyscall ()                                                
No symbol table info available.

..anyway.

------------------------------------------------------------------------------------------

(23:10:36) blist: Updating buddy status for [CENSORED_BY_FOX] (AIM)                          
(23:10:36) blist: Updating buddy status for [CENSORED_BY_FOX] (AIM)                     
(23:10:40) oscar: incomingim_ch1: unknown TLV 0x0013 (len 1)                          
(23:10:40) oscar: Received IM from [CENSORED_BY_FOX] with 1 parts                        
(23:10:40) oscar: Parsing IM part, charset=0x0000, charsubset=0x0000, datalen=2       
[New Thread 0xb52d7b70 (LWP 26243)]                                                   
                                                                                      
Program received signal SIGABRT, Aborted.                                             
[Switching to Thread 0xb52d7b70 (LWP 26243)]                                          
0xb7ff2424 in __kernel_vsyscall ()                                                    
(gdb) bt full                                                                         
#0  0xb7ff2424 in __kernel_vsyscall ()                                                
No symbol table info available.                                                       
#1  0xb725b7a1 in raise () from /lib/libc.so.6                                        
No symbol table info available.                                                       
#2  0xb725cfd4 in abort () from /lib/libc.so.6                                        
No symbol table info available.                                                       
#3  0xb729d2ab in malloc_printerr () from /lib/libc.so.6                              
No symbol table info available.                                                       
#4  0xb72a1b26 in free () from /lib/libc.so.6                                         
No symbol table info available.                                                       
#5  0xb74f2816 in g_free () from /usr/lib/libglib-2.0.so.0                            
No symbol table info available.                                                       
#6  0xb74c52bc in g_array_free () from /usr/lib/libglib-2.0.so.0                      
No symbol table info available.                                                       
#7  0xb7f37fcd in gst_value_free_list_or_array ()                                     
   from /usr/lib/libgstreamer-0.10.so.0                                               
No symbol table info available.                                                       
#8  0xb75974b8 in g_value_unset () from /usr/lib/libgobject-2.0.so.0                  
---Type <return> to continue, or q <return> to quit---                                
No symbol table info available.                                                       
#9  0xb7f1f560 in gst_structure_free () from /usr/lib/libgstreamer-0.10.so.0          
No symbol table info available.                                                       
#10 0xb7edfe52 in gst_caps_unref () from /usr/lib/libgstreamer-0.10.so.0              
No symbol table info available.                                                       
#11 0xb7f00447 in gst_pad_link_prepare () from /usr/lib/libgstreamer-0.10.so.0        
No symbol table info available.                                                       
#12 0xb7f056eb in gst_pad_link () from /usr/lib/libgstreamer-0.10.so.0                
No symbol table info available.                                                       
#13 0xb7ef5042 in gst_ghost_pad_set_target () from /usr/lib/libgstreamer-0.10.so.0    
No symbol table info available.                                                       
#14 0xb7ef5db5 in gst_ghost_pad_new () from /usr/lib/libgstreamer-0.10.so.0           
No symbol table info available.                                                       
#15 0xb534cd0e in gen_audio_element () from /usr/lib/gstreamer-0.10/libgstplaybin.so  
No symbol table info available.                                                       
#16 0xb534ed0f in setup_sinks () from /usr/lib/gstreamer-0.10/libgstplaybin.so        
No symbol table info available.                                                       
#17 0xb5362044 in group_commit () from /usr/lib/gstreamer-0.10/libgstplaybin.so       
---Type <return> to continue, or q <return> to quit---                                
No symbol table info available.                                                       
#18 0xb75826bc in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0  
No symbol table info available.                                                       
#19 0xb7574d62 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0               
No symbol table info available.                                                       
#20 0xb75891f8 in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0         
No symbol table info available.                                                       
#21 0xb758a5ad in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0           
No symbol table info available.                                                       
#22 0xb758aa26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0                  
No symbol table info available.                                                       
#23 0xb7eec30a in gst_element_no_more_pads () from /usr/lib/libgstreamer-0.10.so.0    
No symbol table info available.                                                       
#24 0xb557543e in dynamic_remove () from /usr/lib/gstreamer-0.10/libgstdecodebin.so   
No symbol table info available.                                                       
#25 0xb75826bc in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0  
No symbol table info available.                                                       
#26 0xb7574d62 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0               
---Type <return> to continue, or q <return> to quit---                                
No symbol table info available.                                                       
#27 0xb75891f8 in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0         
No symbol table info available.                                                       
#28 0xb758a5ad in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0           
No symbol table info available.                                                       
#29 0xb758aa26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0                  
No symbol table info available.                                                       
#30 0xb7eec30a in gst_element_no_more_pads () from /usr/lib/libgstreamer-0.10.so.0    
No symbol table info available.                                                       
#31 0xb546ba08 in gst_wavparse_add_src_pad ()                                         
   from /usr/lib/gstreamer-0.10/libgstwavparse.so                                     
No symbol table info available.                                                       
#32 0xb546bff3 in gst_wavparse_stream_data ()
   from /usr/lib/gstreamer-0.10/libgstwavparse.so
No symbol table info available.
#33 0xb5471ab0 in gst_wavparse_loop () from /usr/lib/gstreamer-0.10/libgstwavparse.so
No symbol table info available.
#34 0xb7f27c1d in gst_task_func () from /usr/lib/libgstreamer-0.10.so.0
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#35 0xb7515acf in g_thread_pool_thread_proxy () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#36 0xb751447f in g_thread_create_proxy () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#37 0xb73aa6bc in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#38 0xb72ffffe in clone () from /lib/libc.so.6
No symbol table info available.
(gdb) quit

Last edited by FrozenFox (2009-05-29 05:05:55)

kumyco · 2009-05-29 16:51:04

reverting to gfire 7.1 and see what happens

Last edited by kumyco (2009-05-30 08:00:35)

FrozenFox · 2009-05-31 00:37:08

It may again be a coincidence, but I've completely disabled sound in pidgin's options since you were playing with gstreamer, and have not had a crash since my last post..

I should note though that I've had gfire 8.1 for a lot longer than this bug has annoyed me, I'm pretty sure.

Ty btw for your efforts kumyco

I will edit this post upon my next crash or in a few days, whichever comes first.. I'm not sure whether the information in my prior post is enough (ie should I recompile the other stuff with symbols and debug mode and wait for the crash again or what?) to send as a report, and whether I should give it to pidgin or someone else.. suggestions?

Last edited by FrozenFox (2009-05-31 00:44:10)

kumyco · 2009-05-31 08:52:54

yw hmm, i haven't had a crash since switching back. it may be an issue with gfire and sound, i know most of the signons etc come from gfire with people often signon - signoff - signon in less than a second, that could be something that triggers it.
i think it's isolated to the sound system so you shouldn't get a crash with it off, you can substitute the sound system with a command, `mplayer` plays fine and exits after it finishes so you can use that for now.
i'm re-compiling pidgin and gfire 0.8.1 with bebugging and 0 optimizations, i'm hoping it will crash and give me some good info.

trilobite · 2009-05-31 12:09:00

get the pidgin fork, carrier, formerly known as fun-pidgin.
regular pidgin sucks, big time.

kumyco · 2009-05-31 12:33:30

trilobite wrote:

get the pidgin fork, carrier, formerly known as fun-pidgin.
regular pidgin sucks, big time.

please don't hijack the thread with your FUD. fyi, carrier crashes as well (i wonder why).

trilobite · 2009-05-31 13:56:27

what does FUD stand for?

FrozenFox · 2009-05-31 15:33:28

Fear, Uncertainty, and Doubt

misinformation, scare tactics, or bad solutions/reasoning mostly

Last edited by FrozenFox (2009-05-31 15:34:15)

trilobite · 2009-05-31 16:06:11

lol:)

ok, sure.

i was just having loads of problems w/ pidgin too, and it all settled & precipitated the moment i installed carrier & have been happy since.

but i guess i am out of context if you say so. notes taken. ;]

FrozenFox · 2009-05-31 17:01:18

Thank you for the suggestion anyway, but workaround != solution

5arge · 2009-06-02 18:24:02

Any luck FrozenFox or kumyco?

I'm getting these abrupt crashes too; it's very frequent and very frusterating. I'm also using the latest stable version of gfire... The only difference that I can see is that it didn't happen so much until 2.5.6. It would happen before, but was much less frequent, perhaps once, maybe twice a day. It crashed 5 times yesterday, would have crashed probably 5 more times, but I gave up on it in the afternoon.

I've managed to compile with debugging, but gdb also gives me "No symbol table info available". Still, my backtrace IS quite a bit different from yours. Here it is:

New Thread 0x7f1d3520c910 (LWP 21695)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f1d550b8740 (LWP 17348)]
0x00007f1d4fe7a1a1 in strlen () from /lib/libc.so.6
(gdb) dns[21672]: nobody needs me... =(
dns[21690]: nobody needs me... =(

(gdb) bt full
#0  0x00007f1d4fe7a1a1 in strlen () from /lib/libc.so.6
No symbol table info available.
#1  0x00007f1d50cf77c2 in g_strdup () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#2  0x00007f1d3bc6ef57 in gfire_detect_running_games_cb ()
   from /usr/lib/purple-2/libxfire.so
No symbol table info available.
#3  0x00007f1d50cd7bfb in g_timeout_dispatch () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4  0x00007f1d50cd74ae in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#5  0x00007f1d50cdabf8 in g_main_context_iterate ()
   from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6  0x00007f1d50cdb095 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#7  0x00007f1d52bf98c7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#8  0x000000000047c68b in main (argc=1, argv=0x7fff5d0ea7e8) at gtkmain.c:882
    opt_help = <value optimized out>
    opt_login = 0
    opt_nologin = 0
---Type <return> to continue, or q <return> to quit---
    opt_version = 1561241288
    opt_si = 0
    opt_config_dir_arg = <value optimized out>
    opt_login_arg = 0x0
    opt_session_arg = 0x0
    accounts = <value optimized out>
    sigset = {__val = {82951, 0 <repeats 15 times>}}
    prev_sig_disp = <value optimized out>
    errmsg = "\000\200\fU\035\177\000\000\000p\fU\035\177\000\000t\fU\035\177\000\000y\fU\035\177\000\000\000@\fU\035\177\000\000\204\fU\035\177\000\000\211\fU\035\177\000\000\210Y\fU\035\177", '\0' <repeats 11 times>, "\220\fU\035\177\000\000\006\000\000\000\000\000\000\000iQ\035\177\000\000\220\205\016]\177\000\000\000\000\b\035\000\000a۩:\206\016]\177\000\000xlM\035\177\000\000xlM\035\177\000\000hlM\035\177\000\000 \207\016]\177\000\000\204\016]\177\000\000@\016]\177\000\000\016]\177\000\000\fU\035\177\000\000\a\000\000\000\000\000\000\000@"...
    opt = <value optimized out>
    gui_check = <value optimized out>
    migration_failed = <value optimized out>
    active_accounts = <value optimized out>
    long_options = {{name = 0x4bf9c2 "config", has_arg = 1, flag = 0x0, 
    val = 99}, {name = 0x4ad116 "debug", has_arg = 0, flag = 0x0, val = 100}, {
    name = 0x4b0fb5 "help", has_arg = 0, flag = 0x0, val = 104}, {
---Type <return> to continue, or q <return> to quit---
    name = 0x4ad3e1 "login", has_arg = 2, flag = 0x0, val = 108}, {
    name = 0x4bba02 "multiple", has_arg = 0, flag = 0x0, val = 109}, {
    name = 0x4bba0b "nologin", has_arg = 0, flag = 0x0, val = 110}, {
    name = 0x4bba13 "nocrash", has_arg = 0, flag = 0x0, val = 120}, {
    name = 0x4bf9b8 "session", has_arg = 1, flag = 0x0, val = 115}, {
    name = 0x4b2e61 "version", has_arg = 0, flag = 0x0, val = 118}, {
    name = 0x4bf9cb "display", has_arg = 1, flag = 0x0, val = 68}, {
    name = 0x4bba1b "sync", has_arg = 0, flag = 0x0, val = 83}, {name = 0x0, 
    has_arg = 0, flag = 0x0, val = 0}}
(gdb)

I wonder if our crashes are from the same root-cause. It doesn't appear to be the case: you get signal SIGABRT, and the program aborts, whereas I am getting signal SIGSEGV and a segmentation fault. Anyway, I'd appreciate your thoughts on my backtrace before I submit it as a bug.

kumyco · 2009-06-02 18:33:57

the thing is, i get crashes only when i use internal sound system and gfire 0.8.1, but the logs point to other problems in code that seems just fine, they point to different things but i get the feeling that somewhere memory is being corrupted, this is just the kinda of random behaviour that results from corrupted memory. submit, but I'm not sure whether it goes to pidgin or gfire or neither.
I'm running through valgrind right now, it's always picked u memory problems, it's pretty slow even with cpu at 100%, but it's gotta crash sooner or later

FrozenFox · 2009-06-02 22:08:38

5arge:

I've not had another crash, ever, since I disabled sound completely. That's a tolerable workaround for me, although I'd still much rather have it fixed, heh. I'll wait for the results from kumyco's valgrind session before submitting anything, then go ahead and give it to the gfire devs. Since so few people are getting this, and all of us that do seem to use gfire, I suppose it would make the most sense to send them for now.

Last edited by FrozenFox (2009-06-02 22:17:58)

kumyco · 2009-06-03 10:28:59

you can submit to gfire, valgrind shows countless memory leaks and a few buffer overruns, some i fixed and am testing a patch,
but i'm not sure if it's just me or the code is really littered with errors, i'm surprised it works at all.
i'm still hoping i'm wrong about the code quality, but i'm not holding my breath.
the output from valgrind didn't give any line numbers so not very useful (6mb worth), so when/if you submit tell them to run it through valgrind and take a look at the compiler warnings from gcc . -- i'm pretty sure this is an issue with memory corruption.

babypuncher · 2009-06-03 10:33:52

Sorry to hijack the thread, but has anyone else encountered crashes on receiving file transfers? Its been happening to me for the last couple of releases now.

5arge · 2009-06-04 15:27:07

@ babypuncher: I don't know about file transfer crashes, never do it (at least, not until gfire supports it). I don't know if I can consider you hijacking the thread based on the thread's title.

@ FrozenFox: If this has definitively been traced back to gfire as the root cause (which it seems almost certain from my eyes), perhaps it would be a good idea to change the title?

@ Kumyco: Thanks for your diagnosis. I'm either going to create a post in the gfire forums, or file a bug report. I'm leaning on the former as I know nothing about valgrind to submit your evidence, and I'm leary of pointing the dev's to this thread based on the slight chance that your comments about their code may offend them in some way. I'm going to play with valgrind and see what I come up with before I do anything though. I think this is distro-specific as there has been no mention of this in the Gfire forums.

kumyco · 2009-06-04 15:41:48

just got home, crashed while i was out and this time i get decent results, from problems with the gstreamer bits so it's not just gfire at fault, this has already been reported multiple times.
just to clarify, i didn't mean gfire was the cause there are a lot of errors in the valgrind log, hell even spotted a memory leak in a plugin i coded myself, but the actual crash-related problems mostly come from gfire and a few from gstreamer,
there is a buffer overrun in gfire code right after a particular free() in gstreamer, i'm going to go with my original assumption,
that is, because gfire is so much more active than all the other plugins (msn, irc, icq) it stands out as the trigger, i don't know the link between gfire and the sound system but i'm sure it's one or both of them that causes the crashes, because if gfire 0.8.1 or internal sound are used together everything is fine. in the gstreamer bug report (can't remember the page) there was mention of setting the sound backend explicitly solving(?) the problem, i.e instead of automatic, set it to alsa or oss, etc. i set it to alsa all yesterday and it didn't crash at all, so maybe there's something there.
---
in case the gfire devs read this, i didn't intend to offend anyone, just some pieces of code doesn't look right to me,
i don't personally care about the memory leaks, but when i see a function accept gpointer(void*)* then passes that to a macro accepting gpointer(void*), then use of that same function casts to xxx*, one must wonder what's going on there.
---
http://www.mail-archive.com/debian-bugs … 64670.html

Last edited by kumyco (2009-06-04 15:44:03)

5arge · 2009-06-04 19:17:07

kumyco: I know there was no malice in your remarks, I just wasn't sure how the authors of the code of the would react to them. Anyway, you've made it clear that you meant no harm.

I directed Luxus' (a Gfire developer) to this thread. He's also experiencing the crashes, and he said to "look to the tickets and if the bug is not there yet make a ticket." So, that's what I'm going to do. Since your post, I changed the audio to ALSA in pidgin, and also changed the gstreamer default to ALSA. I did have one crash since then, but I didn't restart pidgin after making the changes. I'm going to restart my computer just to be on the safe side that gstreamer changes are applied, and run pidgin through valgrind (with the memcheck tool?) to get some output before submitting a ticket with Gfire....that is IF it crashes after these recent changes.

Last edited by 5arge (2009-06-04 19:25:26)

Arch Linux

#1 2009-05-27 22:04:24

*Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#2 2009-05-28 03:28:14

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#3 2009-05-28 04:40:51

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#4 2009-05-28 05:42:57

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#5 2009-05-28 17:25:10

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#6 2009-05-28 21:49:10

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#7 2009-05-29 03:27:23

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#8 2009-05-29 04:27:47

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#9 2009-05-29 16:51:04

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#10 2009-05-31 00:37:08

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#11 2009-05-31 08:52:54

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#12 2009-05-31 12:09:00

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#13 2009-05-31 12:33:30

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#14 2009-05-31 13:56:27

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#15 2009-05-31 15:33:28

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#16 2009-05-31 16:06:11

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#17 2009-05-31 17:01:18

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#18 2009-06-02 18:24:02

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#19 2009-06-02 18:33:57

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#20 2009-06-02 22:08:38

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#21 2009-06-03 10:28:59

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#22 2009-06-03 10:33:52

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#23 2009-06-04 15:27:07

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#24 2009-06-04 15:41:48

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

#25 2009-06-04 19:17:07

Re: *Constant* pidgin crashes last ~2 weeks [gfire issue?]?

Board footer

Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?

Re: Constant pidgin crashes last ~2 weeks [gfire issue?]?