2.7.0 gives blank chat and userlist

Asked by Akdor 1154

Compiled on Debian Testing x64, after manually commenting out the SSLv2 bits in boost. Appears to run fine:

---------------------------------------------------------------------
jarrad@claude> ./adchppd
Starting.Logging: 2011-07-12 11:36:38: core: Core initialized
.Processing HubName
Processing Description
Processing Log
Processing LogFile
Processing MaxSendSize
Processing MaxBufferSize
Processing BufferSize
Processing MaxCommandSize
Processing OverflowTimeout
Processing KeepSlowUsers
Processing BufferSize
Processing DisconnectTimeout
Processing LoginTimeout
.
ADCH++ v2.7.0 (r0) Debug running, press ctrl-c to exit...
Logging: 2011-07-12 11:36:38: ScriptManager: Starting
Logging: 2011-07-12 11:36:38: PluginManager: Script.so loaded
Logging: 2011-07-12 11:36:38: BloomManager: Starting
Logging: 2011-07-12 11:36:38: PluginManager: Bloom.so loaded
Logging: 2011-07-12 11:36:38: SocketManager: Starting
Logging: 2011-07-12 11:36:38: SocketManager: Listening on port 2780 (Encrypted: No)
V4S7 entering IDENTIFY
V4S7 entering NORMAL
BNGJ entering IDENTIFY
BNGJ entering NORMAL
---------------------------------------------------------------------

But connecting to it with linuxdcpp and ApexDC++ yields merely [timestamp] Connected!, which I believe is a message from the client itself. Chat window is blank and remains blank even when messages are submitted, userlist is blank, and commands (i.e. the +regme as suggested in the basic HowTo) take no effect.

Ideas? :(

Question information

Language:
English Edit question
Status:
Solved
For:
ADCH++ Edit question
Assignee:
No assignee Edit question
Solved by:
Akdor 1154
Solved:
Last query:
Last reply:
Revision history for this message
Akdor 1154 (akdor1154) said :
#1

Just tried with latest trunk (r505) and same result. also tried running as root; again, same result. :(

Revision history for this message
Akdor 1154 (akdor1154) said :
#2

Sorry all. wasn't connecting as adc://. (I think Vladmir's Q below is relating to this as well). Will add an FAQ entry re: this.