Bug 326005 - KNode Timeout on Server when connecting to IBM Connections Forums
Summary: KNode Timeout on Server when connecting to IBM Connections Forums
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.11.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-14 11:18 UTC by Graham White
Modified: 2018-09-04 18:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham White 2013-10-14 11:18:53 UTC
I'm attempting to use knode to connect to an IBM Connections based forum with authenticated NNTP.  Lotus Connections has a forum capability embedded and there is a (probably quite dodgy) bridge to allow users to post/read these forums via NNTP.

At the moment I've got as far as configuring an account with my username/password, pointing at the server name and port 563 for SSL authentication.  I should say I use KNode for other forums and they are working fine.  I also connect to Lotus Connections forums via Thunderbird (which I'd like to replace with KNode) at the moment and this is working fine (slowly at least but it does work).

Following the instructions at http://techbase.kde.org/User:Nive/KNode to create debug output...

I see the following in ~/.xsession-errors:
QObject::connect: Cannot connect (null)::destroyed() to QHostInfoLookupManager::waitForThreadPoolDone()

I see the following on the command line if I start KNode via a shell prompt (I have changed my email address, the server name and the forum name in the text below):

knode(13187) KNMainWidget::slotCollectionSelected: KNMainWidget::slotCollectionSelected(QListViewItem *i)
knode(13187) KNMainWidget::slotArticleSelected: KNMainWidget::slotArticleSelected(QListViewItem *i)
knode(13187) KNGroupManager::setCurrentGroup: KNGroupManager::setCurrentGroup() : group changed
knode(13187) KNArticleFilter::doFilter: KNArticleFilter::doFilter() : matched 0 articles , merged 0 threads by subject
knode(13187)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0x110ce50)
knode(13187) KNFolderManager::setCurrentFolder: KNFolderManager::setCurrentFolder() : folder changed
knode(13187)/kio (Slave) KIO::Slave::createSlave: createSlave "nntps" for KUrl("nntps://myid%40somewhere.com@servername.somwhere.com:563forum.topic.name?first=1&max=1000")
knode(13187)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on  "local:/tmp/ksocket-gwhite/knodey13187.slave-socket"
knode(13187) KNJobData::slotJobInfoMessage: Status: "Connecting to server..."
knode(13187) KNJobData::slotJobInfoMessage: Status: "Selecting group forum.topic.name..."
knode(13187) KNJobData::slotJobInfoMessage: Status: "Downloading new headers..."
knode(13187)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  149   "servername.somwhere.com"
knode(13187)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::ListJob(0x110ce50) KIO::Slave(0x11466e0)
knode(13187) KNArticleFilter::doFilter: KNArticleFilter::doFilter() : matched 0 articles , merged 0 threads by subject

KNode itself just reports "Timeout on Server" in the user interface.

Reproducible: Always

Steps to Reproduce:
1. Start KNode
2. Configure an NNTP connection to a forum hosted on IBM Connections
3. View list of forums
4. Subscribe to one (or more) forums
5. Attempt to read forum
Actual Results:  
KNode reports "Timeout on Server" in the user interface

Expected Results:  
KNode shows the content of the forum and allows normal interactions with it
Comment 1 anton 2014-02-03 11:15:07 UTC
Similar behaviour also seen on Ubuntu Saucy with KNode 4:4.11.3-0ubuntu0.1
UI reports "The process for nntps://.... protocol died unexpectedly"
Comment 2 Sergey 2015-02-21 12:46:12 UTC
Similar bug on Fedora 21 with knode-4.14.4-2.fc21.x86_64
GUI report "Timeout on server".
Comment 3 Andrew Crouthamel 2018-09-04 18:34:01 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.