#729493 smuxi: Connection hangs after finding hostname

Package:
smuxi
Source:
smuxi
Submitter:
Felipe Sateler
Date:
2015-07-29 18:21:04 UTC
Severity:
important
#729493#5
Date:
2013-11-13 14:45:00 UTC
From:
To:
Hi,

I can't connect to irc servers, the connection hangs after:

11:42 -!- Connecting to irc.oftc.net port 6667...
11:42 -!- Connection to irc.oftc.net established
11:42 -!- Logging in...
11:42 !magnet.oftc.net *** Looking up your hostname...
11:42 !magnet.oftc.net *** Checking Ident
11:42 !magnet.oftc.net *** Found your hostname


	Attached is a log of smuxi with the -d flag.
#729493#10
Date:
2013-11-16 12:16:16 UTC
From:
To:
Hi Felipe,

Was it always like this or has it worked before?

Just a wild guess, please run the following command and show me the output
of it:
grep SigBlk /proc/self/status

The output should look like this:
meebey@redhorse:~$ grep SigBlk /proc/self/status
SigBlk: 0000000000000000

The connection seems to timeout for some reason... After reading the debug
log it looks like the signalling of the AutoResetEvent between the socket
queue and queue reader is not working. So this really looks like it is
related to the signal block mask mentioned above. So if you run the
proprietary nvidia driver please tell me the version, as I have seen
reports related to it (see #728743 and #499569).

Thanks, this was very helpful.
#729493#15
Date:
2013-11-18 15:18:53 UTC
From:
To:
Humm.. so today smuxi manages to connect. When it doesn't, it doesn't
at least on oftc and freenode.

I do note that between this report and the previous, I did some
upgrades, in particular the kernel to 3.11-2. I will reboot and check
if this causes the bug to reappear.

I've used smuxi for a while now, but it broke a few weeks ago (I'm not
a very heavy user of irc). I thought it possibly was user error, so on
this new laptop I got a couple of weeks ago I installed it and
reproduced the problem. That's when I submitted this bug report. FWIW,
the previous laptop was also a debian unstable amd64.
felipe@felipepc:~% grep SigBlk /proc/self/status
SigBlk: 0000000000000000

I use the intel driver.

% apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.21.15-1+b2
  Candidate: 2:2.21.15-1+b2
  Version table:
 *** 2:2.21.15-1+b2 0
        500 http://http.debian.net/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
#729493#20
Date:
2013-11-18 15:42:22 UTC
From:
To:
No, this does not cause the bug to reappear. Very strange, as now
smuxi connects just fine.
#729493#25
Date:
2013-11-22 18:32:19 UTC
From:
To:
Meh, its working fine always now. I wonder what happened.

Since the bug is no longer actionable, I'm closing it.


Thanks!
#729493#30
Date:
2013-12-19 20:40:55 UTC
From:
To:
I have reproduced the issue. The setup is with a remote engine.
Attached is the log of the remote engine (run with -d). Hope we can
shed some light on the issue. SigBlk is 0, and the remote machine is a
Raspberry Pi running Raspbian. It used to work until some days ago.
#729493#37
Date:
2015-07-29 18:19:22 UTC
From:
To:
Hi Felipe,

Is this bug still reproducible with smuxi 1.0-1?

Thanks,
Victor