Opened at 2013-06-17T20:19:20Z
Closed at 2018-04-29T23:50:29Z
#1066 closed defect (obsolete)
Randomly appearing skype contact info
Reported by: | Owned by: | Miklos Vajna | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Skype | Version: | devel |
Keywords: | userinfo skype info | Cc: | |
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: | Arch Linux |
Description
From time to time, I see this in my &bitlbee channel:
<root> skype - Contact Information <root> Skype Name: REDACTED <root> Personal Information <root> Birthday: September 07, 1990 <root> Age: 23 <root> Gender: Unknown
This happens out of the blue, without me doing any command or anything, and with different contacts. In the skyped debug output, I just see the usual USERINFO lines, nothing special. What's kinda interesting though is that it sometimes says SEX MALE and sometimes SEX UNKNOWN for the same contact there.
I'm using the latest bzr version (993).
Attachments (0)
Change History (6)
comment:1 Changed at 2013-06-18T08:34:08Z by
comment:2 Changed at 2013-06-20T16:38:56Z by
Hi,
this is the output in the bitlbee window this time:
17:35:24 <root> skype - Contact Information 17:35:24 <root> Skype Name: Alice 17:35:24 <root> Mobile Phone: <redacted> 17:35:24 <root> Personal Information 17:35:24 <root> Contacts: 82 17:35:24 <root> Local Time: 18:35:24 17:35:24 <root> Gender: Female 17:35:24 <root> Region: Baden Würtemberg
And the skyped output around this timestamp:
[2013-06-20 17:21:23] /usr/bin/skyped:372: >> GET GROUP 234 TYPE [2013-06-20 17:21:23] /usr/bin/skyped:348: << GROUP 234 TYPE ONLINE_FRIENDS [2013-06-20 17:23:48] /usr/bin/skyped:348: << USER Charlie ONLINESTATUS ONLINE [2013-06-20 17:23:48] /usr/bin/skyped:348: << USER Charlie NROF_AUTHED_BUDDIES 0 [2013-06-20 17:23:48] /usr/bin/skyped:348: << GROUP 234 NROFUSERS 26 [2013-06-20 17:23:48] /usr/bin/skyped:372: >> GET GROUP 234 TYPE [2013-06-20 17:23:48] /usr/bin/skyped:348: << GROUP 234 TYPE ONLINE_FRIENDS [2013-06-20 17:26:10] /usr/bin/skyped:348: << USER Bob MOOD_TEXT Does anyone even use this as a mood status? [2013-06-20 17:26:10] /usr/bin/skyped:348: << USER Bob iandoh.co.uk1 RICH_MOOD_TEXT Does anyone even use this as a mood status? [2013-06-20 17:26:10] /usr/bin/skyped:348: << USER Bob iandoh.co.uk1 TIMEZONE 97200 [2013-06-20 17:26:10] /usr/bin/skyped:348: << USER Bob iandoh.co.uk1 PHONE_MOBILE <redacted> [2013-06-20 17:33:57] /usr/bin/skyped:348: << USER Charlie NROF_AUTHED_BUDDIES 82 [2013-06-20 17:35:24] /usr/bin/skyped:348: << USER Alice SEX FEMALE [2013-06-20 17:35:24] /usr/bin/skyped:348: << USER Alice PROVINCE Baden Würtemberg [2013-06-20 17:35:24] /usr/bin/skyped:348: << USER Alice BIRTHDAY 0 [2013-06-20 17:36:18] /usr/bin/skyped:348: << USER Bob MOOD_TEXT Oh so spicy rice [2013-06-20 17:36:18] /usr/bin/skyped:348: << USER Bob RICH_MOOD_TEXT Oh so spicy rice [2013-06-20 17:36:18] /usr/bin/skyped:348: << USER Bob TIMEZONE 100800 [2013-06-20 17:36:18] /usr/bin/skyped:348: << USER Bob PHONE_MOBILE [2013-06-20 17:36:59] /usr/bin/skyped:348: << USER Dan NROF_AUTHED_BUDDIES 31
I don't have any groupchats open at all (but had problems with crashes with them before, so there might be some leftovers I'm afraid...) and I never requested any userinfo, so I'm really unsure about what's going on there.
comment:3 Changed at 2013-07-02T20:55:21Z by
comment:4 Changed at 2013-07-04T19:48:42Z by
Is the 4.2.0.1 vs 4.2.0.11 a typo? If not, it would make sense to check the contents of those 3 revisions. ;-)
comment:5 Changed at 2013-07-05T15:25:53Z by
Hm, I'm not sure anymore, it probably is though. But as said, the problem occures in both setups, so that probably wouldn't make sense.
comment:6 Changed at 2018-04-29T23:50:29Z by
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Closing all skype tickets (plugin removed in a949b43ed657154d4ff8492bbdb16202a1a9f22d)
Hi,
Could you attach the 'skyped -d -n' output when this happens? Just redirect the output of skyped to a file -- I would like to have something I can replay using 'skyped -m', then fixing the plugin itself will be much easier.
Thanks,
Miklos