Forum Replies Created
-
AuthorPosts
-
fidelleonParticipant
That’s what I suspected, so I downloaded the ffmpeg package from NoMachine.com/opensource and did my best to compile it (./configure && make wasn’t working), to no avail…
$ ls -l /usr/NX/lib/libav*
-rwxr-xr-x 1 root root 2366788 oct 14 22:40 /usr/NX/lib/libavcodec.so
-rwxr-xr-x 1 root root 2366788 oct 14 22:40 /usr/NX/lib/libavcodec.so.54
-rwxr-xr-x 1 root root 484216 oct 14 22:41 /usr/NX/lib/libavutil.so
-rwxr-xr-x 1 root root 484216 oct 14 22:41 /usr/NX/lib/libavutil.so.51but it’s very likely I didn’t compile it right O:-)
As far as I see, Ubuntu 14.10 does indeed pull libavcodec56 (libavcodec54 is obsoleted):
# apt-get install libavcodec54
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package libavcodec54 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another sourceE: Package ‘libavcodec54’ has no installation candidate
Well, it’s not a stopper for me, so let’s have some patience 🙂
fidelleonParticipantAutoanswer 😉 Chrome 35 has just been released and it solved my issue!
February 18, 2014 at 15:27 in reply to: Connecting to 4.1 physical desktop resets display frequency #2395fidelleonParticipantCan it be that you clicked “Don’t show this message again”?
Yes, of course I clicked on “Don’t show again” in every screen 😉 but question is, in version 4.0 I was always asked about muting the remote desktop EVEN after checking such box 😕 What do I mean? For v4.0:
Open Nomachine Enterprise Client.
Click (once) the session you wanted to open.
Click on Connect button.
Confirm that “Don’t show again” is already checked, however you were asked about muting remote sound.Now with 4.1 is:
Open Nomachine Enterprise Client.
Double click the session I want to open.So I went from three clicks in three differents screens to a double click in a single screen 🙂 Couldn’t be much happier – I just need the free version but I’ll buy a subscription anyway to support you!!
fidelleonParticipantI had this very problem with versions up to 4.0 but seems it has been solved for 4.1 builds.
fidelleonParticipantOh, sorry, I used the forum’s search function but didn’t find such article, I apologize for the redundant noise.
I have followed such steps and login works fine now. Thanks!
fidelleonParticipantConfirmed that disabling USB sharing workaround has fixed the issue for me on a Fedora 19 3.11.10-200.fc19.x86_64 box. No kworker taking CPU cycles:
2452 fidel 20 0 3020952 0,978g 35172 R 60,6 12,5 647:20.88 /usr/lib64/firefox/firefox -new-instance -P fidel
2567 fidel 20 0 2008472 737540 26644 R 39,0 9,0 467:10.20 /usr/lib64/firefox/firefox -new-instance -P TX
1060 root 20 0 181556 49356 31632 S 17,2 0,6 321:12.98 /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtsw+
2818 fidel 20 0 688040 93732 11504 R 11,9 1,1 102:27.61 /usr/lib64/firefox/xulrunner/plugin-container /usr/lib64/flash-plugin/libflashplayer.so+
2587 fidel 20 0 1948312 654592 26764 S 9,3 8,0 390:07.07 /usr/lib64/firefox/firefox -new-instance -P JL
4005 fidel 0 -20 1523064 113364 41048 S 7,9 1,4 0:18.45 /usr/NX/bin/nxnode.bin
2905 fidel 20 0 688040 102500 11516 S 2,6 1,3 69:42.64 /usr/lib64/firefox/xulrunner/plugin-container /usr/lib64/flash-plugin/libflashplayer.so+
4402 fidel 0 -20 1374364 70956 11248 S 0,3 0,9 0:01.21 /usr/NX/bin/nxnode.bin -H 6
4557 root 20 0 123696 1672 1160 R 0,3 0,0 0:00.07 top
32548 root 20 0 0 0 0 S 0,3 0,0 0:01.28 [kworker/u8:0] -
AuthorPosts