| Summary: | Can't connect to Xvnc inet daemons, nor to krfb, nor to YaST's Remote Administration | ||
|---|---|---|---|
| Product: | [Applications] krdc | Reporter: | Marc Chamberlin <marc> |
| Component: | VNC | Assignee: | Urs Wolfer <uwolfer> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | marc |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Marc Chamberlin
2010-04-27 04:11:21 UTC
Oops I meant that first line to read - I can't connect to any remote desktop sessions with krdc ... Brain slipped a cog there... You can connect to these servers with other VNC-clients? This sounds really strange, I have never heard of such isses so far. KRDC is a "standard" conform VNC client. Please try to start KRDC from konsole and post here if there is some output while connecting to these non-working servers. Ok here is the output between krdc and krfb... On my laptop I started krdc in a terminal window. marc@marcslaptop:/home/marc> krdc krdc(2666)/kdecore (KSycoca): Trying to open ksycoca from "/var/tmp/kdecache-marc/ksycoca4" krdc(2666)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory! Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) This brought up the krdc GUI and I proceeded to attempt to connect to the the krfb server on the target machine of Nova. (port 5900) I got as far as getting a window prompting me for the password. It absolutely refused to allow me to enter anything in the password field and I could not proceed from that point on. On the target machine I started krfb in a terminal window... I captured the output as shown below except I have removed many of the lines of output where noted as it was just lots of repeated lines.... Also, on the target machine, I got a huge number of popup window notifications that swamped my target computer for nearly 15 minutes after I closed the connection down. marc@nova:~> krfb Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) krfb(21987) KrfbServer::KrfbServer: starting krfb(21987) FrameBufferManager::instance: krfb(21987) FrameBufferManager::FrameBufferManager: krfb(21987) FrameBufferManager::loadPlugins: krfb(21987)/kdecore (KSycoca): Trying to open ksycoca from "/var/tmp/kdecache-marc/ksycoca4" krfb(21987) FrameBufferManager::loadPlugins: Loaded plugin: "X11 Framebuffer for KRfb" krfb(21987) FrameBufferManager::loadPlugins: Loaded plugin: "Qt Framebuffer for KRfb" krfb(21987) FrameBufferManager::frameBuffer: krfb(21987) FrameBufferManager::frameBuffer: Using FrameBuffer: "krfb_framebuffer_x11" krfb(21987) X11FrameBuffer::X11FrameBuffer: shm: true krfb(21987) X11FrameBuffer::X11FrameBuffer: Got image. bpp: 32 , depth: 24 , padded width: 7680 (sent: 7680 ) krfb(21987) KrfbServer::startListening: bpp: 4 krfb(21987) KrfbServer::updatePassword: password: "mypassword" allow true invitations 0 krfb(21987) KrfbServer::updatePassword: Ask for password to accept connections krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: krfb(21987) ConnectionController::handleNewClient: < about a 1000 repeats of the above line removed....> krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987) ConnectionController::handleNewClient: krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987) ConnectionController::handleNewClient: krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987) ConnectionController::handleNewClient: krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987) ConnectionController::handleNewClient: krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987) ConnectionController::handleNewClient: krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." < LOTS of repeats of the above line removed....> krfb(21987) KrfbServer::clientDisconnected: clients--: 1009 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1008 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1007 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1006 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1005 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1004 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1003 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1002 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1001 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 1000 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 999 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 998 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 997 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 996 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 995 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987) KrfbServer::clientDisconnected: clients--: 994 < About a 1000 repeats of the above pair of lines removed.> krfb(21987) KrfbServer::clientDisconnected: stopMonitor: d->numClients = 0 krfb(21987) ConnectionController::handleClientGone: client gone krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." krfb(21987)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." < And finally LOTs of the above line was repeated and removeds from this output.> Marc, thank you for investigating in this issue. It does not look nice at all... Could it be that you have stored a wrong (or now changed) password in KWallet for this host? When I connect between krdc and an x11vnc server I do succeed in bringing up the remote desktop and can manipulate it pretty much as expected. However, clicking on the Disconnect button in the krdc window does NOT convey a sense of disconnection to the x11VNC server and the x11vnc server remains in a state of thinking it is still connected.... The output from krdc is the same as I showed above when connecting to a krfb server... marc@marcslaptop:~> krdc krdc(3660)/kdecore (KSycoca): Trying to open ksycoca from "/var/tmp/kdecache-marc/ksycoca4" krdc(3660)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory! Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Groan! KWallet is one application that I do NOT grok! And has been a real PITA... I wish I could get rid of it entirely but it seems some apps insist on it being used... (Amarok for example is one app that insists on using it, but for the life of me I cannot understand why Amarok needs a password for anything!....) Anywise I opened up the KWallet manager and found some weird wallet in it labeled literally "This wallet is not found in .service" or sometime like that. Within it I found a password stored for KRDC but it was the correct password... I deleted that wallet, thinking that would be the better part of valor and created a new wallet with my name.. Now when I try to run KRDC I get a popup dialog asking for a password to access the Wallet but again I cannot type in anything in the password field. All I can do is click on cancel and I get a second dialog asking me for the password to access the remote KRFB server.. And again I cannot type in anything in the password field. All I can do at this point is disconnect and close down both KRDC and KRFB, and wait for zillions of popup notification messages on the remote server to go away... I have figured out how to disable the KWallet password manager entirely. (It is interesting to note that KRDC will still ask if I want to store the password for a connection in KWallet, even though KWallet is no longer running! I suspect that is another oversight on the part of the KRDC designers.) Removing the KWallet manager does not make any difference in the behavior of KRDC, I am still unable to use it for any sort of remote desktop connection. You are right, KWallet settings are also available in KRDC when KWallet is not available. Of course, that's not very nice. I still do not have any idea why you cannot connect with KRDC to *any* remote server... It sounds really strange to me. Sorry, but I cannot provide any help here. If you find any news, please post it here. Thank you. I did NOT say that KRDC cannot connect to any remote server, please reread the entire bug report. KRDC will connect to an x11vnc server as long as no password is required. But KRDC does not disconnect from an x11vnc server very well. KRDC will not connect to either a Krfb server or an Xvnc server, regardless of whether passwords are required or not. (FYI - On our systems, we have now disabled KWallet entirely and do not use it or even install it anymore. It causes so many problems for many different apps, is poorly configurable and apparently not fully functional yet. Most other apps, it turns out can be configured to work without KWallet and KRDC needs to be able to work without KWallet also.) Ok, let's talk about the KWallet issue first: there is an option in the KRDC settings. Is that what you want? Do you think your problem with entering passwords is related to bug 191532? The option in KRDC to use KWallet is not checked. I thought you were saying that KRDC cannot work without KWallet in your previous comment, so I was just mentioning that it should be able to work without KWallet... If this option will disable KRDC's reliance on KWallet, then yes that is I what I want... However, as I previously mentioned, I have removed KWallet from my systems, and the option in KRDC to use KWallet is unchecked. (An interesting question might be - why is this option even present if KWallet is not installed?) As for whether this problem of entering passwords is related to bug 191532, I cannot say for certain, but I would guess there is an overlapping issue because both of us are reporting that KRDC will not allow any password to be typed in via the dialog box. The thread in bug 1991532 seems to imply there is a connection between this problem and the "Get all keys" feature of KWallet. IMHO since KWallet is not installed on my systems anymore, I would strongly suspect this problem is KRDC related and not KWallet related... Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |