Bug 49422 - EnsureChannel does not return when unable to join because of +r (freenode)
Summary: EnsureChannel does not return when unable to join because of +r (freenode)
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: idle (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-03 05:00 UTC by Marien Zwart
Modified: 2019-12-03 20:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
empathy log showing two joins to a restricted channel (3.33 KB, text/plain)
2012-05-03 05:00 UTC, Marien Zwart 		Details
View All

Description Marien Zwart 2012-05-03 05:00:22 UTC 
Created attachment 60967 [details]
empathy log showing two joins to a restricted channel

The empathy developers redirected me here.

Trying to join a freenode channel that is set +r (block unidentified users)
while unidentified fails with no indication as to why. This is unfortunate, but
a more confusing issue is that empathy (or telepathy-idle) will silently refuse
to try the join again: if the channel is set -r and you retry the join nothing
happens. Debug log (from empathy, as I do not know how to more directly use telepathy-idle) attached, with a few newlines added. Note this was from a
session that already had a window open for ##marienz (I /part-ed there before
clearing the log). Results are similar on a fresh connection, and no channel
window is ever opened.

According to an empathy developer: "the EnsureChannel() call never returns".

The channel join should fail, and do so in a way allowing Empathy to show a relevant message to the user.

I'm using telepathy-idle-0.1.11.
Comment 1 Jonny Lamb 2012-05-03 05:42:15 UTC 
Comment on attachment 60967 [details]
empathy log showing two joins to a restricted channel

>mcd-DEBUG: 03-05-12 01:20:08.93158: dispatcher_channel_request_acl_start: start /org/freedesktop/Telepathy/Account/idle/irc/marienz0.org.freedesktop.Telepathy.Connection.Interface.Requests.EnsureChannel acl (0x7f5020004080)
>mcd-DEBUG: 03-05-12 01:20:08.93322: dispatcher_channel_request_acl_success: complete acl (0x7f5020004080)
>mcd-DEBUG: 03-05-12 01:20:08.93549: _mcd_request_init: 0xabd220
>mcd-DEBUG: 03-05-12 01:20:08.93801: _mcd_request_new: 0xabd220 (for 0xad4060)
>mcd-DEBUG: 03-05-12 01:20:08.93924: _mcd_channel_set_status: 0xb3eb00, 1
>mcd-DEBUG: 03-05-12 01:20:08.94096: _mcd_request_predict_handler: Default handler org.freedesktop.Telepathy.Client.Empathy.Chat for request /org/freedesktop/Telepathy/ChannelDispatcher/Request14 doesn't want AddRequest
>mcd-DEBUG: 03-05-12 01:20:08.94186: dispatcher_channel_request_acl_cleanup: cleanup acl (0x7f5020004080)
>mcd-DEBUG: 03-05-12 01:20:08.102435: ready_to_request_cb: Starting online request
>mcd-DEBUG: 03-05-12 01:20:08.102478: _mcd_account_online_request: connection status for idle/irc/marienz0 is 0
>mcd-DEBUG: 03-05-12 01:20:08.102503: _mcd_account_online_request: idle/irc/marienz0 is already connected
>mcd-DEBUG: 03-05-12 01:20:08.102525: online_request_cb: called
>mcd-DEBUG: 03-05-12 01:20:08.102551: _mcd_mission_set_parent: child = 0xb3eb00, parent = 0xb48a60
>mcd-DEBUG: 03-05-12 01:20:08.102637: _mcd_channel_set_status: 0xb3eb00, 2
>idle/network-DEBUG: 03-05-12 01:20:08.103491: idle_server_connection_send_async: sending "JOIN ##marienz
>" to OutputStream 0x154c860
>idle/parser-DEBUG: 03-05-12 01:20:08.167999: _parse_message: parsing ":gibson.freenode.net 477 empathicmarienz ##marienz :Cannot join channel (+r) - you need to be identified with services"
>
>
>mcd-DEBUG: 03-05-12 01:20:21.301736: dispatcher_channel_request_acl_start: start /org/freedesktop/Telepathy/Account/idle/irc/marienz0.org.freedesktop.Telepathy.Connection.Interface.Requests.EnsureChannel acl (0xb28c00)
>mcd-DEBUG: 03-05-12 01:20:21.301892: dispatcher_channel_request_acl_success: complete acl (0xb28c00)
>mcd-DEBUG: 03-05-12 01:20:21.302071: _mcd_request_init: 0xabd170
>mcd-DEBUG: 03-05-12 01:20:21.302323: _mcd_request_new: 0xabd170 (for 0xad4060)
>mcd-DEBUG: 03-05-12 01:20:21.302462: _mcd_channel_set_status: 0x7f5020002920, 1
>mcd-DEBUG: 03-05-12 01:20:21.302632: _mcd_request_predict_handler: Default handler org.freedesktop.Telepathy.Client.Empathy.Chat for request /org/freedesktop/Telepathy/ChannelDispatcher/Request15 doesn't want AddRequest
>mcd-DEBUG: 03-05-12 01:20:21.302720: dispatcher_channel_request_acl_cleanup: cleanup acl (0xb28c00)
>mcd-DEBUG: 03-05-12 01:20:21.314409: ready_to_request_cb: Starting online request
>mcd-DEBUG: 03-05-12 01:20:21.314537: _mcd_account_online_request: connection status for idle/irc/marienz0 is 0
>mcd-DEBUG: 03-05-12 01:20:21.314625: _mcd_account_online_request: idle/irc/marienz0 is already connected
>mcd-DEBUG: 03-05-12 01:20:21.314707: online_request_cb: called
>mcd-DEBUG: 03-05-12 01:20:21.314798: _mcd_mission_set_parent: child = 0x7f5020002920, parent = 0xb48a60
>mcd-DEBUG: 03-05-12 01:20:21.315043: _mcd_channel_set_status: 0x7f5020002920, 2
>
>
>idle/network-DEBUG: 03-05-12 01:20:30.163160: idle_server_connection_send_async: sending "PING 1336000830162963
>" to OutputStream 0x154c860
>idle/parser-DEBUG: 03-05-12 01:20:30.277921: _parse_message: parsing ":gibson.freenode.net PONG gibson.freenode.net :1336000830162963"
Comment 2 Jonny Lamb 2012-05-03 05:42:59 UTC 
(In reply to comment #1)
> Comment on attachment 60967 [details]
> empathy log showing two joins to a restricted channel

No idea what happened here, I was just trying to change the attachment to text/plain.
Comment 3 GitLab Migration User 2019-12-03 20:09:49 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-idle/issues/38.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.