Buddy list shows wrong status
Open implementation of the Lotus Sametime protocol
Brought to you by:
jhkrischel,
taliesein
Menu
▾
▴
#93 Buddy list shows wrong status
Meanwhile in Gaim is showing the wrong user status for several people on my buddy list. Specifically, some people who are shown as active and logged in in the Sametime client (6.5.1) are shown as logged out in Gaim. This happened suddenly one day with no changes on the client end. I can only assume something happened on the server end, possibly an upgrade. Since the Sametime client is showing the right info, this can't be considered a server problem.
The same problem occurs with both Gaim 1.5 with Meanwhile 1.8.2 and with Gaim 2.0beta5 with the built-in Meanwhile.
Discussion
Anonymous
Logged In: YES
user_id=675816
Originator: NO
I'm seeing the same thing as well. The problem has been getting worse - more and more people on my buddy list are starting to show up as inactive. I've even had conversations with logged out people ;).
Logged In: YES
user_id=263512
Originator: NO
I have noticed this too after they upgraded the Sametime server where I use gaim.
Logged In: YES
user_id=1727300
Originator: NO
We have users who just updated to the most recent version of Adium on the Macs and are reporting the same issues. If they are logged in to the sametime client (domino 7.0.2 integrated or sametime 7.5 stand alone client) what they see matches what is logged in to the server. There is a discrepancy when logged in to the newest Adium. Any ideas if reverting to the previous version resolves the issue or if it is a compatibility issue with the latest version of sametime?
Logged In: YES
user_id=1736146
Originator: NO
Yes, after upgrading to Adium 1.0.1 on Mac OS X, none of my Sametime contacts appear online unless they log into sametime when I'm already logged in.
Logged In: YES
user_id=1774510
Originator: NO
This problem occurs in Adium 1.0.2 with the following environment:
Mac OS X 10.4.9
MacBook Pro
Sametime Server 7.5
Mac version of Lotus Notes 7.0.2
In 7.0.2, I can see a much longer list of active users than in Adium. Adium seems to show one user plus me. Then other users show as their status changes... but even then not always.
Logged In: YES
user_id=77326
Originator: NO
If anyone having this issue can collect a packet dump of it happening, I would appreciate it. This would allow me to figure out what information is being sent that Meanwhile isn't correctly interpreting.
Logged In: YES
user_id=1727300
Originator: NO
do you mean a tcpdump? that i can do. if you mean something else, would you please be specific as this is not my normal range of expertise... :)
Logged In: YES
user_id=77326
Originator: NO
yes, a tcpdump is correct. Just make sure it's filtered to only sametime-specific packets. If this is for corporate use, you may want to just send me the capture a taliesein@users.sourceforge.net rather than attaching it here, but that is completely up to you.
Logged In: YES
user_id=811386
Originator: NO
I also experience this problem (using Pidgin 2.0.0). I found a workaround though its a bit tedious.
If you drag a contact from one group to another then it will update their online status. And then you can drag them back to the original group.
Logged In: YES
user_id=1796586
Originator: NO
Posted about this on the board. Looking forward to a resolution, this is a crippling problem.
Running AdiumX 1.0.3
on a MacBook Pro running OS X 10.4.9.
Unsure of SameTime Server version.
Logged In: YES
user_id=1342359
Originator: NO
09:17:27.089554 IP sametime.domain.com.1533 > nova.server.domain.com.2346:
P 1964:1998(34) ack 883 win 65016
09:17:27.111305 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:27.146671 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:27.191145 IP nova.server.domain.com.2346 > sametime.domain.com.1533:
. ack 1998 win 65090
09:17:27.191364 IP sametime.domain.com.1533 > nova.server.domain.com.2346:
P 1998:2151(153) ack 883 win 65016
09:17:27.320930 IP ElijahMobile.dy.domain.com.5353 > 224.0.0.251.5353: 0 [4q]
PTR? _appletv-pair._tcp.local.[|domain]
09:17:27.391783 IP nova.server.domain.com.2346 > sametime.domain.com.1533:
. ack 2151 win 64937
09:17:27.426737 IP ElijahMobile.dy.domain.com.5353 > 224.0.0.251.5353: 0- [0q
] 4/0/0 (Cache flush) A ElijahMobile.dy.domain.com,[|domain]
09:17:28.053497 arp who-has mp3-1n14-d4-c-gw-vlan-322.domain.com tell AE-JWIDZE
R.dy.domain.com
09:17:28.106905 IP nova.server.domain.com.1255 > hope.domain.com.53: 57924
+ PTR? 251.0.0.224.in-addr.arpa. (42)
09:17:28.108842 IP hope.domain.com.53 > nova.server.domain.com.1255: 57924
NXDomain 0/1/0 (100)
09:17:28.108965 IP nova.server.domain.com.137 > 224.0.0.251.137: UDP, length
50
09:17:28.115884 arp who-has nova.server.domain.com tell linux.domain.com
09:17:28.115892 arp reply nova.server.domain.com is-at 00:11:43:0d:f6:02 (ou
i Unknown)
09:17:28.116107 IP linux.domain.com.137 > nova.server.domain.com.137: UDP
, length 229
09:17:28.168266 IP pc1.domain.com.3330 > 255.255.255.255.3956: UDP,
length 8
09:17:28.572174 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:28.787996 arp who-has mp3-1n14-d4-c-gw-vlan-322.domain.com tell AE-AMCKEE
.dy.domain.com
09:17:29.076931 AT 1.66.14.rtmp > 0.0.rtmp: at-rtmp 586
09:17:29.077231 AT 1.66.14.rtmp > 0.0.rtmp: at-rtmp 154
09:17:29.146020 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:29.528940 arp who-has mp3-1n14-d4-c-gw-vlan-322.domain.com tell AE-rverre
t1.dy.domain.com
09:17:29.608867 IP nova.server.domain.com.137 > 224.0.0.251.137: UDP, length
50
09:17:29.610003 IP linux.domain.com.137 > nova.server.domain.com.137: UDP
, length 229
09:17:30.031704 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:30.170265 IP pc1.domain.com.3331 > 255.255.255.255.3956: UDP,
length 8
09:17:31.109655 IP nova.server.domain.com.137 > 224.0.0.251.137: UDP, length
50
09:17:31.112279 IP linux.domain.com.137 > nova.server.domain.com.137: UDP
, length 229
09:17:31.161216 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:31.544174 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:32.172263 IP pc1.domain.com.3332 > 255.255.255.255.3956: UDP,
length 8
09:17:32.612554 IP nova.server.domain.com.1255 > hope.domain.com.53: 53594
+ PTR? 143.34.0.10.in-addr.arpa. (42)
09:17:32.613587 IP hope.domain.com.53 > nova.server.domain.com.1255: 53594 1/2/2 PTR[|domain]
09:17:32.614628 IP nova.server.domain.com.1255 > hope.domain.com.53: 33112
+ PTR? 155.34.0.10.in-addr.arpa. (42)
09:17:32.615558 IP hope.domain.com.53 > nova.server.domain.com.1255: 33112
1/2/2 PTR[|domain]
09:17:32.963088 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:33.157299 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:33.617298 IP nova.server.domain.com.1255 > hope.domain.com.53: 36696
+ PTR? 212.34.0.10.in-addr.arpa. (42)
09:17:33.618256 IP hope.domain.com.53 > nova.server.domain.com.1255: 36696 1/2/2 PTR[|domain]
09:17:33.618930 IP nova.server.domain.com.1255 > hope.domain.com.53: 47192
+ PTR? 180.34.0.10.in-addr.arpa. (42)
09:17:33.619848 IP hope.domain.com.53 > nova.server.domain.com.1255: 47192
1/2/2 PTR[|domain]
09:17:34.174265 IP pc1.domain.com.3333 > 255.255.255.255.3956: UDP,
length 8
09:17:34.496625 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:35.143150 IP nova.server.domain.com > leven.domain.com: ICMP ec
ho request, id 512, seq 8707, length 40
09:17:35.143297 IP leven.domain.com > nova.server.domain.com: ICMP ec
ho reply, id 512, seq 8707, length 40
09:17:35.143391 IP nova.server.domain.com.1151 > leven.domain.com.445
: S 3042364542:3042364542(0) win 64512 <mss 1260,nop,nop,sackOK="">
09:17:35.143534 IP leven.domain.com.445 > nova.server.domain.com.1151
: S 2944504524:2944504524(0) ack 3042364543 win 16384 <mss 1460,nop,nop,sackOK="">
09:17:35.143558 IP nova.server.domain.com.1151 > leven.domain.com.445
: . ack 1 win 65520
09:17:35.144634 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:35.148182 IP nova.server.domain.com > leven.domain.com: ICMP ec
ho request, id 512, seq 8963, length 40
09:17:35.148308 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 1:138(137) ack 1 win 65520
09:17:35.148331 IP leven.domain.com > nova.server.domain.com: ICMP ec
ho reply, id 512, seq 8963, length 40
09:17:35.148656 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 1:196(195) ack 138 win 65398
09:17:35.149279 IP nova.server.domain.com.1151 > leven.domain.com.445
: . 138:1398(1260) ack 196 win 65325
09:17:35.149295 IP nova.server.domain.com.1151 > leven.domain.com.445
: . 1398:2658(1260) ack 196 win 65325
09:17:35.149304 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 2658:2774(116) ack 196 win 65325
09:17:35.149803 IP leven.domain.com.445 > nova.server.domain.com.1151
: . ack 2774 win 65535
09:17:35.150801 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 196:534(338) ack 2774 win 65535
09:17:35.151015 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 2774:2910(136) ack 534 win 64987
09:17:35.151239 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 534:594(60) ack 2910 win 65399
09:17:35.151345 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 2910:2986(76) ack 594 win 64927
09:17:35.151806 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 594:1566(972) ack 2986 win 65323
09:17:35.159314 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 2986:3106(120) ack 1566 win 65520
09:17:35.159640 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 1566:1994(428) ack 3106 win 65203
09:17:35.159814 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 3106:3192(86) ack 1994 win 65092
09:17:35.160076 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 1994:2212(218) ack 3192 win 65117
09:17:35.317068 IP nova.server.domain.com.1151 > leven.domain.com.445
: . ack 2212 win 64874
09:17:35.406061 IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff:ff:ff:ff:ff
.0452: ipx-sap-nearest-req FileServer
09:17:35.523727 00:0c:30:98:b3:ff (oui Unknown) > 01:00:0c:dd:dd:dd (oui Unknown
) SNAP Unnumbered, ui, Flags [Command], length 46
09:17:35.624345 IP nova.server.domain.com.1255 > hope.domain.com.53: 57688
+ PTR? 25.44.164.130.in-addr.arpa. (44)
09:17:35.625292 IP hope.domain.com.53 > nova.server.domain.com.1255: 57688 1/2/2 (175)
09:17:35.923514 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:36.176277 IP pc1.domain.com.3334 > 255.255.255.255.3956: UDP,
length 8
09:17:36.405006 (NOV-ETHII) IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff
:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
09:17:36.705256 IP sametime.domain.com.1533 > nova.server.domain.com.2346:
P 2151:2185(34) ack 883 win 65016
09:17:36.821867 IP nova.server.domain.com.2346 > sametime.domain.com.1533:
. ack 2185 win 64903
09:17:37.089012 AT 1.66.175.rtmp > 0.0.rtmp: at-rtmp 586
09:17:37.089272 AT 1.66.175.rtmp > 0.0.rtmp: at-rtmp 154
09:17:37.155128 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:37.404200 (NOV-ETHII) IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff
:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
09:17:37.416877 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:38.178276 IP pc1.domain.com.3335 > 255.255.255.255.3956: UDP,
length 8
09:17:38.402156 IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff:ff:ff:ff:ff
.0452: ipx-sap-nearest-req FileServer
09:17:38.855111 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:38.859801 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com > PIM-ROUTERS
.MCAST.NET: PIMv2, Hello, length 34
09:17:39.087325 AT 1.66.14.rtmp > 0.0.rtmp: at-rtmp 586
09:17:39.087626 AT 1.66.14.rtmp > 0.0.rtmp: at-rtmp 154
09:17:39.155467 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:39.400661 IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff:ff:ff:ff:ff
.0452: ipx-sap-nearest-req FileServer
09:17:40.114174 IP nova.server.domain.com.2319 > by1msg4176118.phx.gbl.1863:
P 15:20(5) ack 25 win 65160
09:17:40.114208 IP nova.server.domain.com.2346 > sametime.domain.com.1533:
P 883:884(1) ack 2185 win 64903
09:17:40.180261 IP pc1.domain.com.3336 > 255.255.255.255.3956: UDP,
length 8
09:17:40.194862 IP by1msg4176118.phx.gbl.1863 > nova.server.domain.com.2319:
P 25:33(8) ack 20 win 65227
09:17:40.224544 IP sametime.domain.com.1533 > nova.server.domain.com.2346:
. ack 884 win 65015
09:17:40.333066 IP nova.server.domain.com.2319 > by1msg4176118.phx.gbl.1863:
. ack 33 win 65152
09:17:40.385949 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:40.387664 IP AE-IUFOT.dy.domain.com.2343 > 255.255.255.255.2343: UDP, len
gth 15
09:17:40.401285 (NOV-ETHII) IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff
:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
09:17:40.628513 IP 205.188.5.92.5190 > nova.server.domain.com.1075: . ack 30
297820 win 16384
09:17:40.628538 IP nova.server.domain.com.1075 > 205.188.5.92.5190: . ack 1
win 64879
09:17:40.631204 IP nova.server.domain.com.1255 > hope.domain.com.53: 56415
+ PTR? 149.34.0.10.in-addr.arpa. (42)
09:17:40.632156 IP hope.domain.com.53 > nova.server.domain.com.1255: 56415
1/2/2 PTR[|domain]
09:17:40.632637 IP nova.server.domain.com.1255 > hope.domain.com.53: 34910
+ PTR? 92.5.188.205.in-addr.arpa. (43)
09:17:40.679940 IP hope.domain.com.53 > nova.server.domain.com.1255: 34910
NXDomain 0/1/0 (114)
09:17:40.680214 IP nova.server.domain.com.137 > 205.188.5.92.137: UDP, lengt
h 50
09:17:41.158634 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:41.399593 (NOV-ETHII) IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff
:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
09:17:41.847955 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:42.179968 IP nova.server.domain.com.137 > 205.188.5.92.137: UDP, lengt
h 50
09:17:42.182290 IP pc1.domain.com.3337 > 255.255.255.255.3956: UDP,
length 8
09:17:42.396219 IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff:ff:ff:ff:ff
.0452: ipx-sap-nearest-req FileServer
09:17:42.803018 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-unknown (3) 16: state=initial group=2 [|hsrp]
09:17:43.153833 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:43.331986 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:43.394820 IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff:ff:ff:ff:ff
.0452: ipx-sap-nearest-req FileServer
09:17:43.680756 IP nova.server.domain.com.137 > 205.188.5.92.137: UDP, lengt
h 50
09:17:44.134802 IP nova.server.domain.com.2369 > 205.188.12.126.5190: P 18:2
4(6) ack 1 win 64721
09:17:44.134901 IP nova.server.domain.com.2351 > mg-in-f125.google.com.5222:
P 66:88(22) ack 1 win 64425
09:17:44.179643 IP 205.188.12.126.5190 > nova.server.domain.com.2369: . ack
24 win 16384
09:17:44.184256 IP pc1.domain.com.3338 > 255.255.255.255.3956: UDP,
length 8
09:17:44.274275 IP mg-in-f125.google.com.5222 > nova.server.domain.com.2351:
. ack 88 win 16080
09:17:44.393295 (NOV-ETHII) IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff
:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
09:17:44.683978 IP yardo.dy.domain.com.138 > 10.0.34.255.138: UDP, length 206
09:17:45.011507 IP mp3-1n14-d2-c-gw-vlan-322-secondary.domain.com.1985 > ALL-RO
UTERS.MCAST.NET.1985: HSRPv0-hello 20: state=standby group=1 addr=mp3-1n14-d4-c-
gw-vlan-322.domain.com
09:17:45.146240 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
09:17:45.173541 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 3192:3235(43) ack 2212 win 64874
09:17:45.173855 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 2212:2255(43) ack 3235 win 65074
09:17:45.173894 IP nova.server.domain.com.1151 > leven.domain.com.445
: P 3235:3274(39) ack 2255 win 64831
09:17:45.174062 IP leven.domain.com.445 > nova.server.domain.com.1151
: P 2255:2294(39) ack 3274 win 65035
09:17:45.174202 IP nova.server.domain.com.1151 > leven.domain.com.445
: F 3274:3274(0) ack 2294 win 64792
09:17:45.174347 IP leven.domain.com.445 > nova.server.domain.com.1151
: F 2294:2294(0) ack 3275 win 65035
09:17:45.174356 IP nova.server.domain.com.1151 > leven.domain.com.445
: . ack 2295 win 64792
09:17:45.392060 (NOV-ETHII) IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff
:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
09:17:46.186272 IP pc1.domain.com.3339 > 255.255.255.255.3956: UDP,
length 8
09:17:46.211258 IP nova.server.domain.com.1255 > hope.domain.com.53: 23133
+ PTR? 156.34.0.10.in-addr.arpa. (42)
09:17:46.212198 IP hope.domain.com.53 > nova.server.domain.com.1255: 23133 1/2/2 PTR[|domain]
09:17:46.326066 IP mp3-1n14-d4-c-gw-vlan-322-primary.domain.com.1985 > ALL-ROUT
ERS.MCAST.NET.1985: HSRPv0-hello 20: state=active group=1 addr=mp3-1n14-d4-c-gw-
vlan-322.domain.com
09:17:46.390454 IPX 00000000.00:00:74:7c:d4:b6.4100 > 00000000.ff:ff:ff:ff:ff:ff
.0452: ipx-sap-nearest-req FileServer
09:17:46.484439 IP PC2.dy.domain.com.138 > 10.0.34.255.138: UDP, le
ngth 216
09:17:47.124470 AT 1.66.175.rtmp > 0.0.rtmp: at-rtmp 586
09:17:47.124730 AT 1.66.175.rtmp > 0.0.rtmp: at-rtmp 154
09:17:47.138414 IP nova.server.domain.com.1255 > hope.domain.com.53: 49747
+ A? mail.google.com. (33)
09:17:47.139581 IP hope.domain.com.53 > nova.server.domain.com.1255: 49747
4/7/7 CNAME[|domain]
09:17:47.140212 IP nova.server.domain.com.1155 > mg-in-f19.google.com.443: S
2194529727:2194529727(0) win 64512 <mss 1260,nop,nop,sackOK="">
09:17:47.145824 802.1d config c142.00:07:85:fe:7e:00.80cf root 6142.00:0c:30:98:
b3:40 pathcost 3004 age 1 max 20 hello 2 fdelay 15
748 packets captured
765 packets received by filter
0 packets dropped by kernel
Logged In: YES
user_id=77326
Originator: NO
kennova, that was just a meaningless jumble, please don't do that again. It appears that you copy/pasted the short descriptions of each packet in a capture, which has no actual data in it. If you have a real capture file, please attach it at the bottom of the ticket.
Logged In: YES
user_id=1342359
Originator: NO
I see now that it got cutoff. I tried running windump -w dumpfile, but I am not sure if that is right. I'd like to help if I can, what command should I run and should I then start chatting with someone, or is there more I should do?
Thanks, and sorry for the nonsensical input, can we moderate it and get rid of it.
Logged In: YES
user_id=1799851
Originator: NO
Any ETA on a bugfix? Sure would like to resume use of Meanwhile.
Logged In: YES
user_id=1663232
Originator: NO
i am seeing the same buddy list symptoms reported below with adiumX v 1.05 (uses libpurple 2.0.2) after an upgrade to the corporate sametime server i connect to this past weekend (i do not know the exact server version, but i assume the latest).
one additional piece of information is that in a 1-to-1 chat with another sametime user, whether they are appearing as online or offline in the buddy list, i no longer receive the "typing" notification while they are composing a reply.
Logged In: YES
user_id=1342359
Originator: NO
I work at a place that has the servers that are causing this issue. There are many of us who would like to use Pidgin with Meanwhile in an effective manner. WHAT CAN WE DO TO HELP!!! Nothing has happened here, can we provide any information? If you need a TCP dump how do I do that. We are wasting time.
Logged In: YES
user_id=1861703
Originator: NO
I have recently begun having the same problem with Pidgin after a server upgrade. I can add the following details.
+ It appears that anyone who logs in after me or changes status, is visible on my list, but not people who were already logged in when I start Pidgin.
+ Adding someone new as a buddy will show me their proper status regardless of when they logged in.
+ Lotus Notes 6.5 does still show the proper status after the server upgrade.
I have WinDump installed, but I'm unfamiliar with the syntax. If you specify what you would like a dump of, and if you're feeling generous a WinDump command line, I'll be happy to provide the data.
Perhaps whatever command is run to get the status of a newly added user could also be run on startup.
Logged In: YES
user_id=77326
Originator: NO
someone with this issue, launch pidgin from the command line as "pidgin -dn" and then log in just the sametime account. Are there any Meanwhile warnings being printed?
Logged In: YES
user_id=1663232
Originator: NO
i have a dump of the output from "pidgin -dn". will send it to you privately.
Logged In: YES
user_id=1861703
Originator: NO
Using pidgin with -dn. These assertions were the only thing that looked off too me. Stars were added for privacy. Thanks for your response taliesein. Let me know if there is anything else I can do.
(14:51:19) meanwhile: SET_PRIVACY_LIST
(14:51:19) privacy information set from server
(14:51:20) blist: Updating buddy status for CN=**/OU=/O=/C= (Sametime)
(14:51:20) meanwhile: file common.c: line 382 (mwString_get): assertion
check_buffer(b, (gsize) len)' failed (14:51:20) blist: Updating buddy status for ********** (Sametime) (14:51:20) meanwhile: file common.c: line 382 (mwString_get): assertioncheck_buffer(b, (gsize) len)' failed(14:51:20) blist: Updating buddy status for CN=/OU=/O=/C= (Sametime)
(14:51:20) blist: Updating buddy status for CN=**/OU=/O=/C=* (Sametime)
(14:51:20) meanwhile: file common.c: line 382 (mwString_get): assertion `check_buffer(b, (gsize) len)' failed
(14:51:20) meanwhile: storage request loaded: key = 0x0, result = 0x0, length = 4899
(14:51:20) synchronizing local buddy list from server list
Logged In: YES
user_id=1861703
Originator: NO
Sorry. I should mention that this was from the public release of pidgin 2.1.0
Logged In: YES
user_id=1363164
Originator: NO
I also have this issue with the latest version of Pidgin. I can also confirm that it has been independent of the version of Gaim/Pidgin I am running. It is most definitely related to the upgrade that my office did to the sametime server to version 7.
Please let me know if you'd like me to test anything or do some sort of logging or something. In my case, Pidgin is virtually unusable for Sametime.
Logged In: YES
user_id=673066
Originator: NO
Possible - but annoying workaround:
I too have this issue - however, I have found that meanwhile seems to do a good job of adding people to the list as they log on or off. Thus - if you don't log out of meanwhile - your buddy list eventually seems to be accurate. Kind of annoying - I know - but it is my workaround for now.
Logged In: YES
user_id=1363164
Originator: NO
Yeah that would work except some people on my buddy list never log off. Right now if I need to use pidgin I just show offline buddies and cross my fingers that people are online, otherwise I use Sametime.
I guess I'm not really sure where the problem is here. I don't know this code well enough to sit down, look at it, and say "there's the problem!". I could help if someone would tell me what I'm looking at.
Logged In: YES
user_id=1796586
Originator: NO
I move that we increase the priority of this issue. This a critical problem with the functionality of Meanwhile and it needs to be resolved by whatever means are necessary.
In the mean time, jivemastert, have you tried molasses' solution of dragging all your sametime contacts into another buddy list group? This workaround works quite well for me in Adium as well.
Honestly, this indicates a pretty easy fix--whatever process is involved in moving buddies from one list to another is re-requesting information from the SameTime server, and if this were just replicated when Meanwhile LOGGED IN to the SameTime server, this issue should be resolved. It may not be a very elegant solution, but any solution is better than this. It's been 8 months.