Red Hat Bugzilla – Bug 159942
gaim-meanwhile hangs when connecting to Sametime server
Last modified: 2007-11-30 17:11:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
Additional version information:
While connecting to my corporate Sametime server, gaim freezes upon attempting to log in. The last message seen during the connection process is "Waiting for login acknowledgment", after which the connection window disappears and the buddy list window goes blank; I have to perform a force quit. Additionally, I installed the debuginfo RPMs and tried to follow the instructions at http://fedoraproject.org/wiki/StackTraces but to no avail, as the following gdb output shows:
$ gdb gaim
GNU gdb Red Hat Linux (188.8.131.52-1.24rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
Starting program: /usr/bin/gaim
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x3db000
[Thread debugging using libthread_db enabled]
[New Thread -1208740160 (LWP 3516)]
Detaching after fork from child process 3519.
Couldn't get registers: No such process.
(gdb) thread apply all bt
Cannot find new threads: generic error
Cannot fetch general-purpose registers for thread -1208740160: generic error
However, when I try to reproduce the problem as root (and hence need to create a new profile in gaim), I'm able to log in successfully. I also should note that the same versions worked OK yesterday, so it's possible that gaim or meanwhile somehow corrupted something in my settings.
I have not yet been able to update to the more current upstream packages for testing due to a maintenance outage at sourceforge.net.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gaim
2. Choose to login to Sametime profile
I moved my .gaim to a backup directory and restarted gaim to create the account
from scratch. This time, I was able to get a stack trace:
Thread 1 (Thread -1208793408 (LWP 8418)):
#0 0x6c656966 in ?? ()
#1 0x00cac6fb in mwConversation_free () from /usr/lib/libmeanwhile.so.0
#2 0x00ca378b in mwService_free () from /usr/lib/libmeanwhile.so.0
#3 0x009da456 in mw_prpl_close (gc=0x90cde58) at mwgaim.c:2457
#4 0x00e9c3cd in serv_close (gc=0x90cde58) at server.c:126
#5 0x00e813b5 in gaim_connection_disconnect (gc=0x90cde58) at connection.c:241
#6 0x00e775be in gaim_account_disconnect (account=0x90d0970) at account.c:246
#7 0x00e81306 in gaim_connection_disconnect (gc=0x90cde58) at connection.c:228
#8 0x00e814c5 in gaim_connection_disconnect_cb (data=0x90d0970)
#9 0x002daf06 in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#10 0x002d93ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0x002dc3f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#12 0x002dc6e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0x010481b5 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x00f0eebe in main (argc=1, argv=0xbfb4c214) at main.c:961
Further, I believe the problem may actually lie upstream as I have a report here
of someone using gaim and meanwhile on a Windows system and seeing the same
problem. But the fact that it worked for me when I ran as root tells me it's not
I need to get a rawhide system up and running before I can try to recreate this.
I'll talk with the upstream meanwhile folks and see if it's a known issue in
Thanks for the report. Stay tuned.
Please try to get the debugging output from gaim by running `gaim -d` This
should provide some insight as to what's happening leading up to the hang and crash.
Also, try using the 'Force Login' option. Start gaim as `gaim -n` to prevent it
from automatically logging on, then go to preferences and select the 'Meanwhile'
options on the bottom-left to get to the plugin's preferences.
Created attachment 115291 [details]
Output of 'gaim -d'
Here's the 'gaim -d' output as requested.
Using the 'force login' option does let me connect, after all. So now I have a
workaround; I'll see if it works for my Windows user also, although I notice
that the version of gaim I have on Windows doesn't have that option.
My Windows user upgraded to gaim-meanwhile-1.2.3 and it works for him. So maybe
we just need a version bump?
Hm, I requested a build for 1.2.3 a while ago... seems stuck in the build
system somewhere. I'll dig around and see if I can get it pushed out.
Ok, gaim-meanwhile-1.2.3-1.fc5 should be available in the Extras development
repository. Please upgrade and give this a shot.
First day back in the office. Post-upgrade, without the "force login" option
turned on, the same behavior is still seen (ie gaim process hangs).
I think I have this fixed in gaim-meanwhile CVS, however I've only been able to
test it with a mockup of a redirecting server since I don't have access to a
system that issues actual redirects. Would you be willing to test a CVS snapshot?
No problem, though it might be a day or two. Where can I get it?
I'll grab CVS tonight and spin up an RPM. I'll post it's location as soon as I
get it built.
Ok, there are test RPMs built on gaim-meanwhile CVS at:
I was able to log into a non-redirecting with ST server with the RPM. Please
test it out when you get a chance.
Kyle, let us know if this works for you when you get a chance. If so, then I
think the upstream developers will be releasing 1.2.4 soon.
Turned off workaround option, it still works - WFM now.
just dropped gaim-meanwhile 1.2.4 on the world (upstream). Thanks!
Updated in CVS. I submitted builds, but the build server for Extras is
currently being worked on. As soon as it's back up and running, the update
should be available
The Fedora Core 3 and 4 builds have been released, and the development build has
completed successfully. It should be pushed out soon.
Thanks for the help on this one.