![]()
#Nomachine keyboard shortcuts password#password "password" saved for file /home/bernd/.remmina/home_nx_cyclops_cyclops-lan.remmina Authentication that can continue: publickey.password. NX SSH authentication failed: Access denied. Here all the settings it makes visible on the connection: ![]() The nomachine client, detects the server, and connects to it fine. SSH keys shared and I can ssh to it without a password. Special notes regarding the remote system: On same LAN. #Nomachine keyboard shortcuts 64 bits#$ sudo lshw -C video *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff $ uname -a Linux bigfoot 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12: x86_64 x86_64 x86_64 GNU/Linux Remote System Description Again, no useful information yo act on in that message, IMHO a bug. I saw it, so rebooted, and well it's still there. ![]() The glibsecret error about initialization is a mystery. fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -g Compiler: GNU, 7.4.0 Target architecture: 圆4 Remmina - 1.3.5 (git n/a) NAME TYPE DESCRIPTION PLUGIN AND LIBRARY VERSION NX Protocol NX - NX Technology 1.3.5 RDP Protocol RDP - Remote Desktop Protocol RDP Plugin: 1.3.5 (git n/a), Compiled with FreeRDP lib: 2.0.0-dev5 (n/a), Running with FreeRDP lib: 2.0.0-dev5 (rev n/a), H.264: Yes RDPF File RDP - RDP File Handler RDP Plugin: 1.3.5 (git n/a), Compiled with FreeRDP lib: 2.0.0-dev5 (n/a), Running with FreeRDP lib: 2.0.0-dev5 (rev n/a), H.264: Yes RDPS Preference RDP - Preferences RDP Plugin: 1.3.5 (git n/a), Compiled with FreeRDP lib: 2.0.0-dev5 (n/a), Running with FreeRDP lib: 2.0.0-dev5 (rev n/a), H.264: Yes SFTP Protocol SFTP - Secure File Transfer 1.3.5 SSH Protocol SSH - Secure Shell 1.3.5 VNC Protocol VNC - VNC viewer 1.3.5 VNCI Protocol VNCI - VNC viewer listen mode 1.3.5 glibsecret Secret Secure passwords storing in the GNOME keyring 1.3.5 Build configuration: HAVE_ARPA_INET_H=1 HAVE_ERRNO_H=1 HAVE_FCNTL_H=1 HAVE_NETDB_H=1 HAVE_NETINET_IN_H=1 HAVE_NETINET_TCP_H=1 HAVE_SYS_SOCKET_H=1 HAVE_SYS_UN_H=1 HAVE_TERMIOS_H=1 HAVE_UNISTD_H=1 WITH_APPINDICATOR=ON WITH_AVAHI=ON WITH_FREERDP=ON WITH_GCRYPT=ON WITH_GETTEXT=ON WITH_IPP=OFF WITH_KF5WALLET=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBSECRET=ON WITH_LIBSSH=ON WITH_LIBVNCSERVER=ON WITH_MANPAGES=ON WITH_SPICE=ON WITH_SSE2=ON WITH_TRANSLATIONS=ON WITH_VTE=ON Build type: None CFLAGS: -g -O2 -fdebug-prefix-map=/build/remmina-mSYRua/remmina-1.3.5+6078cd2~ubuntu18.04.1=. Passwords will be saved in a less secure way. libappindicator will try to fallback to GtkStatusIcon/xembed WARNING: Remmina is running without a secret plugin. unable to get secret service: Error calling StartServiceByName for : Timeout was reached StatusNotifier/Appindicator support: not supported by desktop. The problematic package in RHEL6.4: .$ sudo remmina -V Remmina plugin glibsecret (type=Secret) has registered but not yet initialized/activated. Note, RHEL7 MATE the menu is in System > Preferences > Hardware > Keyboard Shortcuts. The fix should "stick" after logging out and logging back in. ![]() To fix this, after connecting to the target machine via NX and establishing a GNOME session, go to System > Preferences > Keyboard Shortcuts and change the "Take a screenshot" shortcut to Ctrl+Print. Specifically the "Take Screenshot" is mapped to the delete key. When connecting to a RHEL6.4 machine running the NoMachine software, the keyboard mapping may be incorrect. See kde_preferences_in_rhel5_for_better_performance for speeding up KDE sessions with NX.ġ3 August 2012 - Bug with "System" menu locking up NX session: > Does anyone have any further suggestions? > whilst we wait for unlimited licence keys. #Nomachine keyboard shortcuts free#> We're currently using the free version of the server from > home directory over to the new accounts. > I've even tried copying the entire contents of an experienced user's > c) Rebooting and reinstalling the server nx directory from both client and on the server > we're using Scientific Linux 4.3 (RHEL clone) - and the experienced user > There is no known difference between the newly-created linux accounts. > this server' even though no-one else is logged on! > They get the message 'Reached the maximum number of allowed users on > registered on my systems for a while can log in no problem. > not able to connect to a machine via NX but users that have been > I'm experiencing a very strange problem whereby newly created users are ![]() Nxserver -userlist, nxserver -useradd, nxserver -userdel. NoMachine version is limited to two 'named' users. There is a known limit to the number of users for the free version of NX: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |