Bug#758635: krdc: crash when trying to connect
Package: krdc
Version: 4:4.13.1-1
Severity: grave
Tags: d-i
Justification: renders package unusable
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
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (400, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages krdc depends on:
ii kde-runtime 4:4.13.3-1
ii libc6 2.19-7
ii libkcmutils4 4:4.13.3-2
ii libkdecore5 4:4.13.3-2
ii libkdeui5 4:4.13.3-2
ii libkdnssd4 4:4.13.3-2
ii libkio5 4:4.13.3-2
ii libknotifyconfig4 4:4.13.3-2
ii libqt4-dbus 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-network 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-xml 4:4.8.6+git49-gbc62005+dfsg-1
ii libqtcore4 4:4.8.6+git49-gbc62005+dfsg-1
ii libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1
ii libstdc++6 4.9.1-4
ii libtelepathy-qt4-2 0.9.4+dfsg-3
ii libvncclient0 0.9.9+dfsg-6
Versions of packages krdc recommends:
ii freerdp-x11 1.0.2-4+b1
Versions of packages krdc suggests:
ii khelpcenter4 4:4.13.3-1
pn krfb <none>
-- no debconf information
Reply to: