Dear Maintainer,
When I start krdc and want to connect to a Mac remotely,
the crash happens immediately after entering the credentials.
Has been working for years now without issues.
Started from console is this the result:
tp-qt 0.9.4 DEBUG: Register StreamTubeClient with name "krdc_rfb_handler"
tp-qt 0.9.4 DEBUG: Client registered - busName: "org.freedesktop.Telepathy.Client.krdc_rfb_handler" objectPath: "/org/freedesktop/Telepathy/Client/krdc_rfb_handler" interfaces: ("org.freedesktop.Telepathy.Client.Handler")
krdc(4166)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory!
Fatal: failed to create the RNG lock: Invalid argument
FATAL: failed to acquire the FSM lock in libgrypt: Invalid argument
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
krdc: Fatal IO error: client killed
Control: tag -1 + unreproducible help Control: severity -1 important Hi, I couldn't reproduce this issue using the xrdp server (I don't have another rdp server around), thus I'm lowering this bug severity. Please, could you confirm if this went away on it's own? krdc rdp support is a gui around xfreerdp (from the freerdp-x11 package), so, it's most likely, showing an issue present in xfreerdp. Hapy hacking,
I didn't go away yet, the bug is reproucible always. But the problem is not with RDP but with VNC. All I could find is that others have the same issue, but only with Mac remote sessions as it seems. http://sourceforge.net/p/libvncserver/mailman/message/32165820/ So the severity remains the same for me - krdc remains completely unusable for me to connect to Macs and crashes in full, but I see your point. Maybe I'm barking up the wrong tree? HTH, ändu
I've tried it against a linux VNC server and it worked perfectly. OK, this might help. severity important is right here. Maybe not, althought I'm not sure if this is an upstream problem or not, and I think this might need to be reassigned to libvnc (if we are building krdc against the system lib, last time I checked it had an embedded copy of it but I don't remember which one was using). Maybe even the last suggestion in the link you pasted might help to workaround it, although if that's the case this is a libvnc bug.
I've tried it against a linux VNC server and it worked perfectly. OK, this might help. severity important is right here. Maybe not, althought I'm not sure if this is an upstream problem or not, and I think this might need to be reassigned to libvnc (if we are building krdc against the system lib, last time I checked it had an embedded copy of it but I don't remember which one was using). Maybe even the last suggestion in the link you pasted might help to workaround it, although if that's the case this is a libvnc bug.
I have the same problem with krdc, also with a Mac OS X VNC server. I tried gvncviewer as an alternative and it has the same problem: Fatal: failed to create the RNG lock: Invalid argument FATAL: failed to acquire the FSM lock in libgrypt: Invalid argument xtightvncviewer works though. Using packages from sid. Thanks, Marcel
Dear Maintainer,
i have the same issue.
When i try to connect to an Mac OS Yosemite v10.10.1 krdc crash
immediately after entering the credentials.
In attach a strace output, maybe it will help.
krdc
tp-qt 0.9.4 DEBUG: Register StreamTubeClient with name
"krdc_rfb_handler"
tp-qt 0.9.4 DEBUG: Client registered - busName:
"org.freedesktop.Telepathy.Client.krdc_rfb_handler" objectPath:
"/org/freedesktop/Telepathy/Client/krdc_rfb_handler" interfaces:
("org.freedesktop.Telepathy.Client.Handler")
krdc(31729)/kdeui (kdelibs): Attempt to use QAction
"remote_desktop_dockwidget" with KXMLGUIFactory!
Fatal: failed to create the RNG lock: Invalid argument
FATAL: failed to acquire the FSM lock in libgrypt: Invalid argument
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
krdc: Fatal IO error: client killed
https://github.com/maxnet/libvncserver/commit/4674d4632b9ffc6779d9c9f79b8ebb53c12e29b2 I applied that patch to the libvnc package in ubuntu utopic and it fixed the problem for me. My bug report in KDE/KRDC: https://bugs.kde.org/show_bug.cgi?id=343376 Thanks!