libvncserver | Fork of libvncserver with support for tightPng encoding

by kanaka C Version: Current License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | libvncserver Summary

libvncserver is a C library. libvncserver has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

VNC is a set of programs using the RFB (Remote Frame Buffer) protocol. They are designed to "export" a frame buffer via net (if you don't know VNC, I suggest you read "Basics" below). It is already in wide use for administration, but it is not that easy to program a server yourself. This has been changed by LibVNCServer.

Support

Quality

Security

License

Reuse

Support

libvncserver has a low active ecosystem.

It has 62 star(s) with 17 fork(s). There are 10 watchers for this library.

It had no major release in the last 6 months.

There are 3 open issues and 4 have been closed. On average issues are closed in 3 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of libvncserver is current.

Quality

libvncserver has 0 bugs and 0 code smells.

Security

libvncserver has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

libvncserver code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

libvncserver is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

libvncserver releases are not available. You will need to build from source code and install.

It has 639 lines of code, 0 functions and 18 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of libvncserver

Get all kandi verified functions for this library.

libvncserver Key Features

No Key Features are available at this moment for libvncserver.

libvncserver Examples and Code Snippets

No Code Snippets are available at this moment for libvncserver.

Community Discussions

Trending Discussions on libvncserver

Qt: How to make QImage aware of updated memory buffer?

Can we host multiple vnc servers (using LibVNCServer library) in the same process?

Error compiling project that uses libvncserver

Modified SRPM conflict resolution

QUESTION

Qt: How to make QImage aware of updated memory buffer?

Asked 2019-Apr-26 at 15:06

I need to draw pixel data that is being held by a library as uint8_t * and that is updated frequently and partially. I get a call-back from the library every time an update is done, that looks like this:

...

ANSWER

Answered 2019-Apr-26 at 14:56

I would guess that some sort of caching mechanism is interfering with your expectations. QImage has a cacheKey, which changes if the QImage is altered. This can of course only happen if you change the image through QImage functions. As far as I can see, you're changing the underlying buffer directly, so QImage's cacheKey will remain the same. Qt's pixmap cache then has that key in its cache, and uses the cached pixmap for performance reasons.

Unfortunately, there doesn't seem to be a direct way to update this cacheKey or otherwise "invalidate" a QImage. You have two options:

Recreate the QImage when you need it. No need to new it, so you can save a heap allocation. Creating a back-buffered QImage seems like a "cheap" operation, so I doubt this is a bottleneck.
Do a trivial operation on the QImage (i.e. setPixel on a single pixel to black and then to the old value). This is somewhat "hackish" but probably the most efficient way to work around this API deficiency (it will trigger an update to cacheKey as far as I can tell).

Source https://stackoverflow.com/questions/55869926

QUESTION

Can we host multiple vnc servers (using LibVNCServer library) in the same process?

Asked 2018-Jun-20 at 06:21

There is an example called camera.c in the LibVNCServer library which captures camera snapshots and populates the framebuffer used by vnc server in intervals. My requirement is to do the same with mpeg transport streams (many sources instead of a single source like camera). Therefore, one vnc server per transport stream is required.

I read in the RFB protocol that we can host multiple vnc servers on the same host on ports starting from 5900 (5900+x). However, it would be better to host multiple vnc servers in the same process so that unwanted I/O between the vnc servers and the process generating the data can be avoided.

Does LibVNCServer support that use case or do I have to launch a vnc server process per video stream?

Note: I went through the library and saw that the rfbScreenInfoPtr is circulated everywhere and is not static. But could not conclude if LibVNCServer is thread safe because I am not familiar with C.

...

ANSWER

Answered 2018-Jun-20 at 06:21

I tried to write a vnc server with server-side-downscale ability, which is one source multi-stream.

Source https://stackoverflow.com/questions/50940621

QUESTION

Error compiling project that uses libvncserver

Asked 2018-Mar-29 at 15:46

I'm trying to compile a project that uses libvncserver.

This is my Makefile:

...

ANSWER

Answered 2018-Mar-29 at 15:46

You're linking to zlib too early; order matters when it comes to linking to static libraries. Try putting $(LIBS) after the vncserver static library.

You may want to consider using pkg-config; libvncserver ships a *.pc file, and this is pretty much what it was designed for… on my system, pkg-config --libs libvncserver looks like:

Source https://stackoverflow.com/questions/49559313

QUESTION

Modified SRPM conflict resolution

Asked 2017-Aug-10 at 21:24

I need to update libvncserver and libvncclient libraries to 0.9.11. I am running CentOS 7.3, currently, the latest libvncserver RPM is 0.9.9

So I took the libvncserver SRPM, modified the spec file, and updated the libvncserver tarball to create a 0.9.11 version of libvncserver and libvncclient RPM's.

I'm having a dependency challenge upon install.

...

ANSWER

Answered 2017-Aug-10 at 03:38

The problem is that your package does not provide libvncserver.so.0, but replaces libvncserver, which provides libvncserver.so.0. The easiest solution is to rename your package, so that it can be installed along with the existing libvncserver package.

The -devel subpackage will probably have to conflict with libvncserver-devel because some of the files will overlap, but for the main package, you should be able to enable parallel installation.

You already mentioned the other clean solution: Port all packages from libvncserver.so.0 to libvncserver.so.1. But that could involve quite a bit of unnecessary work and makes your system less similar to others.

(You could also keep the libvncserver package name and create a compat-libvncserver package with the old library, but that's again quite a bit of work for very little benefit.)

Source https://stackoverflow.com/questions/45601648

Community Discussions, Code Snippets contain sources that include Stack Exchange Network