Interesting. Could you enable the plugin again and get a backtrace with GDB? Basically, you'd need to do something like this:
1. Start Gaim. 2. Find the PID of Gaim using ps (or whatever). 3. In a terminal, run: gdb attach Gaim_PID continue 4. Then, as Gaim is hanging, do this: Hit Ctrl-C bt full continue 5. Repeat step 4 several times, in sets of maybe 3 times, each separated by 1-2 seconds. So, you'd have something at like time T, T+1, T+2, T+30, T+30+1, T+30+2, T+60, T+60+1, T+60+2. That way, we might be able to figure out which code is executing while it hangs. Post all the backtraces here, preferably each as separate attachments to make comparison easier. -- Gaim 2.0 unusably slow in Edgy https://launchpad.net/bugs/67195 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
