Bug 188271 - Cannot logon to newsgroup
Summary: Cannot logon to newsgroup
Status: RESOLVED WORKSFORME
Alias: None
Product: knode
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 188457 189412 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-03-27 17:55 UTC by Russ Fineman
Modified: 2009-08-11 00:43 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
[Bug 188271] Cannot logon to newsgroup (69.78 KB, text/plain)
2009-04-06 04:17 UTC, Russ Fineman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Russ Fineman 2009-03-27 17:55:26 UTC
Version:           0.99.01 (using KDE 4.2.1)
OS:                Linux
Installed from:    SuSE RPMs

This is duplicate of bugs 167718 and 178365, message slightly different. Not resolved as stated in version 4.2.1.
KDE 4.2.1 release 106, Knode 0.99.01 on openSUSE 11.1

I get an error in knode when I try to access the one newsgroup that I use that 
requires authentication (alt.os.linux.suse on news server  news.nwi.net). Here 
is the error message.

Internal Error
Please send a full bug report at http://bugs.kde.org
Unexpected server response to MODE READER command:
502 fe.usenet.com: Access denied to your node - support@usenet.com
Comment 1 Olivier Trichet 2009-03-30 12:55:54 UTC
*** Bug 188457 has been marked as a duplicate of this bug. ***
Comment 2 Olivier Trichet 2009-03-30 13:00:22 UTC
Hello, could you follow the steps describe at http://techbase.kde.org/User:Nive/KNode (paragraph "Debug output") and include the output in this report?

By the way, could you tell which version of the "kdepimlibs" package you are using ?
Comment 3 Russ Fineman 2009-03-30 16:31:37 UTC
I will get this information to you sometime today. I have one project I must finish first.

here's the information from your second question. If you need more let me know. I am on KDE 4.2.1 release 106.

libkdepimlibs4-4.2.1-73.1
kdepimlibs4-4.2.1-73.1
Comment 4 Russ Fineman 2009-03-31 00:27:08 UTC
The steps I did: start knode from the kick off menu, kwallet asks for password to allow it to pass user Id and password to isp site, knode goes to site and after short delay comes back with error message mentioned above. After kdeinit4 mentions preparing to launch konsole, 
may not be needed. It was things I did to get this information I think. I normally run knode from kontact but this run is just knode from kickoff menu.

Here's the results of knode run:

kdeinit4: preparing to launch /usr/bin/knode
knode(31087): ""lastExpire" - conversion of "-4713,1,1,0,0,0" to QDateTime failed" 
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18203b1)
kdeinit4: preparing to launch /usr/bin/kwalletmanager
kdeinit4: preparing to launch 
kio_nntp(31090): Unexpected response to "MODE READER" command: ( 502 ) 502 fe.usenet.com: Access denied to your node - support@usenet.com
 
QObject: Do not delete object, 'unnamed', during its event handler!
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x3e00001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x3e00001

kdeinit4: preparing to launch /usr/bin/konsole
konsole(31093): Attempt to use QAction "change-profile" with KXMLGUIFactory! 
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1820baf)
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1820fcb)
QObject: Do not delete object, 'unnamed', during its event handler!
kdeinit4: preparing to launch /usr/bin/knode
knode(31110): ""lastExpire" - conversion of "-4713,1,1,0,0,0" to QDateTime failed" 
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1821190)
kdeinit4: preparing to launch /usr/bin/kwalletmanager
kdeinit4: preparing to launch 
kio_nntp(31113): Unexpected response to "MODE READER" command: ( 502 ) 502 fe.usenet.com: Access denied to your node - support@usenet.com
 
QObject: Do not delete object, 'unnamed', during its event handler!

kdeinit4: preparing to launch /usr/bin/dolphin
[/usr/bin/nepomukservicestub] (ServerCore) new socket connection.
dolphin(31119): Attempt to use QAction "close_tab" with KXMLGUIFactory! 
dolphin(31119): Attempt to use QAction "show_info_panel" with KXMLGUIFactory! 
dolphin(31119): Attempt to use QAction "show_folders_panel" with KXMLGUIFactory! 
dolphin(31119): Attempt to use QAction "show_terminal_panel" with KXMLGUIFactory! 
dolphin(31119): Attempt to use QAction "show_places_panel" with KXMLGUIFactory! 
[/usr/bin/nepomukservicestub] (ServerCore) new socket connection.
[/usr/bin/nepomukservicestub] "/usr/bin/nepomukservicestub(4755)" Error in thread 140519595796304 : "query: Graph pattern graph operation is not implemented yet. Ending query execution. (error)" (line: 1, column: -1)
[/usr/bin/nepomukservicestub] (Soprano::Redland)  "query: Graph pattern graph operation is not implemented yet. Ending query execution. (error)"

kdeinit4: preparing to launch 
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1821b21)
kdeinit4: preparing to launch 
WARNING: field 'http://strigi.sf.net/ontologies/0.9#debugParseError' is not defined in any rdfs ontology database.
/usr/lib64/strigi/strigita_dds.so
/usr/lib64/strigi/strigila_txt.so
/usr/lib64/strigi/strigita_audible.so
/usr/lib64/strigi/strigita_rgb.so
/usr/lib64/strigi/strigila_namespaceharvester.so
/usr/lib64/strigi/strigila_deb.so
/usr/lib64/strigi/strigita_gif.so
/usr/lib64/strigi/strigita_sid.so
/usr/lib64/strigi/strigita_font.so
/usr/lib64/strigi/strigita_xbm.so
/usr/lib64/strigi/strigita_dvi.so
/usr/lib64/strigi/strigiea_jpeg.so
/usr/lib64/strigi/strigiea_vcf.so
/usr/lib64/strigi/strigita_wav.so
/usr/lib64/strigi/strigiea_ics.so
/usr/lib64/strigi/strigita_ico.so
/usr/lib64/strigi/strigita_mp4.so
/usr/lib64/strigi/strigita_pcx.so
/usr/lib64/strigi/strigita_au.so
/usr/lib64/strigi/strigila_xpm.so
/usr/lib64/strigi/strigila_cpp.so
/usr/lib64/strigi/strigita_avi.so
WARNING: field 'maxLineLength' is not defined in any rdfs ontology database.
WARNING: field 'line ending format' is not defined in any rdfs ontology database.
WARNING: field 'content.mime_type' is not defined in any rdfs ontology database.
WARNING: field 'audio.title' is not defined in any rdfs ontology database.
WARNING: field 'audio.artist' is not defined in any rdfs ontology database.
WARNING: field 'todo.audio.narrator' is not defined in any rdfs ontology database.
WARNING: field 'media.codec' is not defined in any rdfs ontology database.
WARNING: field 'todo.audible.user_id' is not defined in any rdfs ontology database.
WARNING: field 'todo.audible.user_alias' is not defined in any rdfs ontology database.
WARNING: field 'audio.duration' is not defined in any rdfs ontology database.
WARNING: field 'content.description' is not defined in any rdfs ontology database.
WARNING: field 'content.copyright' is not defined in any rdfs ontology database.
WARNING: field 'content.keyword' is not defined in any rdfs ontology database.
WARNING: field 'content.creation_time' is not defined in any rdfs ontology database.
WARNING: field 'content.maintainer' is not defined in any rdfs ontology database.
WARNING: field 'content.ID' is not defined in any rdfs ontology database.
WARNING: field 'audio.channel_count' is not defined in any rdfs ontology database.
WARNING: field 'dds volume depth' is not defined in any rdfs ontology database.
WARNING: field 'dds mipmap count' is not defined in any rdfs ontology database.
WARNING: field 'dds image type' is not defined in any rdfs ontology database.
WARNING: field 'font.family' is not defined in any rdfs ontology database.
WARNING: field 'font.weight' is not defined in any rdfs ontology database.
WARNING: field 'font.slant' is not defined in any rdfs ontology database.
WARNING: field 'font.width' is not defined in any rdfs ontology database.
WARNING: field 'font.spacing' is not defined in any rdfs ontology database.
WARNING: field 'font.foundry' is not defined in any rdfs ontology database.
WARNING: field 'content.version' is not defined in any rdfs ontology database.
WARNING: field 'document.stats.image_count' is not defined in any rdfs ontology database.
WARNING: field 'content.genre' is not defined in any rdfs ontology database.
WARNING: field 'TODO_trackNumber' is not defined in any rdfs ontology database.
WARNING: field 'TODO_discNumber' is not defined in any rdfs ontology database.
WARNING: field 'content.author' is not defined in any rdfs ontology database.
WARNING: field 'content.comment' is not defined in any rdfs ontology database.
WARNING: field 'audio.album' is not defined in any rdfs ontology database.
WARNING: field 'TODO_audio.albumartist' is not defined in any rdfs ontology database.
WARNING: field 'content.links' is not defined in any rdfs ontology database.
WARNING: field 'TODO_content.purchaser' is not defined in any rdfs ontology database.
WARNING: field 'TODO_content.purchasedate' is not defined in any rdfs ontology database.
WARNING: field 'content.generator' is not defined in any rdfs ontology database.
WARNING: field 'media.duration' is not defined in any rdfs ontology database.
WARNING: field 'TODO_video.duration' is not defined in any rdfs ontology database.
WARNING: field 'av.audio_codec' is not defined in any rdfs ontology database.
WARNING: field 'av.video_codec' is not defined in any rdfs ontology database.
WARNING: field 'content.thumbnail' is not defined in any rdfs ontology database.
WARNING: field 'user.rating' is not defined in any rdfs ontology database.
WARNING: field 'image.width' is not defined in any rdfs ontology database.
WARNING: field 'image.height' is not defined in any rdfs ontology database.
WARNING: field 'media.sample_rate' is not defined in any rdfs ontology database.
WARNING: field 'media.sample_format' is not defined in any rdfs ontology database.
WARNING: field 'document.stats.image_name' is not defined in any rdfs ontology database.
WARNING: field 'document.stats.image_shared_rows' is not defined in any rdfs ontology database.
WARNING: field 'Product Id' is not defined in any rdfs ontology database.
WARNING: field 'Events' is not defined in any rdfs ontology database.
WARNING: field 'Journals' is not defined in any rdfs ontology database.
WARNING: field 'Todos' is not defined in any rdfs ontology database.
WARNING: field 'Todos Completed' is not defined in any rdfs ontology database.
WARNING: field 'Todos Overdue' is not defined in any rdfs ontology database.
WARNING: field 'ole.category' is not defined in any rdfs ontology database.
WARNING: field 'ole.presentationtarget' is not defined in any rdfs ontology database.
WARNING: field 'ole.manager' is not defined in any rdfs ontology database.
WARNING: field 'ole.company' is not defined in any rdfs ontology database.
WARNING: field 'document.stats.table_count' is not defined in any rdfs ontology database.
WARNING: field 'document.stats.object_count' is not defined in any rdfs ontology database.
WARNING: field 'http://rdf.openmolecules.net/0.9#moleculeCount' is not defined in any rdfs ontology database.
kdeinit4: preparing to launch /usr/bin/kwrite
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1821d02)
QObject: Do not delete object, 'unnamed', during its event handler!
QThreadStorage: Thread 0x608e90 exited after QThreadStorage 2147483645 destroyed
kdeinit4: preparing to launch /usr/bin/kate
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18226b8)
kdeinit4: preparing to launch 
kdeinit4: preparing to launch 
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x182320c)
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x48011c5
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x42055ba
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x42055ba
kdeinit4: preparing to launch 
kdeinit4: preparing to launch 
kdeinit4: preparing to launch /usr/bin/kate

Let me know if I need to do something different or if you need more information.

Thanks for your help!
Comment 5 Olivier Trichet 2009-04-04 20:53:23 UTC
Russ, I'm sorry, but I'll have to ask you more information.
I updated the instructions on http://techbase.kde.org/User:Nive/KNode , could follow them again ? (What changes is that "kdebugdialog --fullmode" should be run instead of "kdebugdialog" ; the more important information is in the "kio_nntp" debug area).

You should then have an output that looks like that (many line starting with kio_nntp):


kio_nntp(5588) NNTPProtocol::NNTPProtocol: =============> NNTPProtocol::NNTPProtocol                                                                
kio_nntp(5588) NNTPProtocol::setHost: "" "news.gmane.org" : 119                                                                                     
kio_nntp(5588) NNTPProtocol::get: "nntp://news.gmane.org:119/gmane.comp.kde.devel.pim/<1238740951.830128.5819.nullmailer@svn.kde.org>"              
kio_nntp(5588) NNTPProtocol::get: group: "gmane.comp.kde.devel.pim" msg: "<1238740951.830128.5819.nullmailer@svn.kde.org>"                          
kio_nntp(5588) NNTPProtocol::nntp_open:   nntp_open -- creating a new connection to "news.gmane.org" : 119                                          
knode(4638) KNJobData::slotJobInfoMessage: Status: "Connecting to server..."                                                                        
kio_nntp(5588) NNTPProtocol::nntp_open:   nntp_open -- connection is open                                                                           
kio_nntp(5588) NNTPProtocol::evalResponse: got: 200
kio_nntp(5588) NNTPProtocol::nntp_open:   nntp_open -- greating was read res_code : 200
kio_nntp(5588) NNTPProtocol::nntp_open: reusing old connection
kio_nntp(5588) NNTPProtocol::sendCommand: cmd: "MODE READER"
kio_nntp(5588) NNTPProtocol::evalResponse: got: 200
kio_nntp(5588) NNTPProtocol::nntp_open: reusing old connection
kio_nntp(5588) NNTPProtocol::sendCommand: cmd: "GROUP gmane.comp.kde.devel.pim"
knode(4638) KNJobData::slotJobInfoMessage: Status: "Selecting group gmane.comp.kde.devel.pim..."
kio_nntp(5588) NNTPProtocol::evalResponse: got: 211
kio_nntp(5588) NNTPProtocol::nntp_open: reusing old connection
kio_nntp(5588) NNTPProtocol::sendCommand: cmd: "ARTICLE <1238740951.830128.5819.nullmailer@svn.kde.org>"
knode(4638) KNJobData::slotJobInfoMessage: Status: "Downloading article..."
kio_nntp(5588) NNTPProtocol::evalResponse: got: 220
knode(4638) KNode::ArticleWidget::canDecodeText: "UTF-8"
knode(4638) KNMemoryManager::updateCacheEntry: KNMemoryManager::updateCacheEntry() : article added
knode(4638) KNMemoryManager::checkMemoryUsageArticles: KNMemoryManager::checkMemoryUsageArticles() : 1 articles in cache => Usage : 0.323868 %

Thanks in advance
Comment 6 Russ Fineman 2009-04-06 04:17:04 UTC
Created attachment 32648 [details]
[Bug 188271] Cannot logon to newsgroup
Comment 7 Russ Fineman 2009-04-06 04:20:19 UTC
I have been trying to run this as your new procedure say but I must be doing
something wrong. They only kio-nntp message I see is the one with the read mode
error message. I am doing the following:
                   kdebugdialog --fullmode
    then select 5003 knode set the four options to shell, then go select
kio-nntp and select all four options to apply. then I say OK.
               start kontact, select usenet, select the news group that gives
errors, put password into kwallet, news group starts and after slight delay
gives error. I then close 
kontact, go to dolphin select the .xsession-error icon and it opens in kwrite.
I tehn look for messages as per your example, only see one as per the above.

Am I supposed to run the two selections separately?
Is there a way to clear the .xsession-error log. It seems to have alot of
entries that don't apply.

I rebooted before running. I will send the log as an attachment
Comment 8 Pino Toscano 2009-04-11 22:50:45 UTC
*** Bug 189412 has been marked as a duplicate of this bug. ***
Comment 9 Russ Fineman 2009-04-15 23:55:22 UTC
Just installed KDE 4.2.2 on one of my systems with Knode (kde4-knode-4.2.2-107.6). Still get the Mode Reader command error with this new version. Only occurs on news group that needs authentication.
Comment 10 Olivier Trichet 2009-06-03 21:10:56 UTC
Russ,

If you still have this problem, could you check that you use the right login and password ?
I just tested and if a wrong login/password is given, the resulting message is the one you gave.
Comment 11 Russ Fineman 2009-06-05 01:33:32 UTC
Oliver I thought I had the right one but I better check with the ISP. I'll also check my other 11.1 installation that has not had updates in a long time. I post in AM tomorrow the results as I am out tonight.
Comment 12 Russ Fineman 2009-06-08 16:50:50 UTC
Talked to ISP yesterday, I have it set correctly and password is correct. They will talk to company that hosts their newsgroup today , I hope.  I am going to see if I can find some other news server that requires authentication and test there. I also cannot log on with my XP guest in virtualbox so I'm beginning to thing its not Knode problem. 

I'll post latter today.
Comment 13 Russ Fineman 2009-06-20 22:12:09 UTC
Follow-up. ISP supposed to have new news service available this coming week, hopefully that will fix things. As of yesterday still getting error with knode but I strongly suspect ISP problem even though they have not admitted it. I get an error in Windows XP which I have running as a guest under virtualbox.

Will post as soon as I can check new setup.
Comment 14 Russ Fineman 2009-06-28 17:03:55 UTC
still no new news provider, may change ISP's. Does someone know of free news provider?
Comment 15 Russ Fineman 2009-07-06 04:13:27 UTC
Thanks Oliver. I already use Gmane but the news group I use does not require authentication . That's were I have the issue. I try again on one of the two you recommended. If you want we can close this and I'll reopen if I have a problem since my ISP still did not have a new news server as of last week.
Comment 16 Russ Fineman 2009-07-24 05:25:26 UTC
We can close the Bug. My ISP has it working again. They did not tell me what they did but it works. still need to verify I can send message, but I am receiving the news group.
Thanks for your help but I think it was all the ISP's problem.
Comment 17 Bernhard Jungk 2009-07-25 00:28:59 UTC
I just hit this "bug" with the following message:

Internal Error
Please send a full bug report at http://bugs.kde.org
Unexpected server response to CONNECT command:
502 You have no permission to talk.  Goodbye.

I can't use the server from where I am now (the server can only be access from inside the local network and not from the internet), but still, this message is wrong, because it is not an error in knode.
Comment 18 Russ Fineman 2009-07-25 18:38:14 UTC
Ref comment#17. 
You may want to check with your ISP to see if they changed anything with their news server. My problem was caused by my ISP changing to require authentication and not notifying the customers, At least I wasn't notified.
Comment 19 Bernhard Jungk 2009-07-27 17:22:04 UTC
Well, my configuration is somewhat like this:

Internal Network <> News Server <> Firewall <> Internet

The News Server can only be accessed from inside the Internal Network, not from the Internet.

My point is, that this is not an "Internal Error" of knode and thus the error message should be somewhat more meaningful, otherwise this will trigger more duplicate bug reports.
Comment 20 Russ Fineman 2009-08-09 23:59:29 UTC
Actually mine ran for about a week after the ISP did something (comment #16) and then quit again. 

new error: Could not connect to host news.nwi.net: Unknown error.

My ISP was considering not offering the newsever and I have just checked with them and the weekend staff was not aware of the server being discontinued. First I was getting the original message (about the internal error) a now the above unknown error. They will let me know the status tomorrow. I'll post answer i get. All my other newsgroups do not require authentication work fine.
Comment 21 Russ Fineman 2009-08-11 00:43:06 UTC
final update. ISP finally informed me that they have dropped the news server offering. So I will look for an alternative.