| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Fixed so config variables can pass an empty argument.
Solves issue #1791.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
The behaviour is not consistent as Windows doesn't use errno for socket
errors, but Unix systems do. Always use the same exception to keep
things somewhat sane.
|
|/ |
|
| |
|
|
|
|
| |
This fixes commit a79c33d.
|
|
|
|
|
| |
This is a policy decision, so let's not enforce something on our own if
there is a system policy to rely on.
|
|\ |
|
| |
| |
| |
| |
| | |
Password should not be greater than 8 characters.
Because only 8 valid characters are used.
|
| |
| |
| |
| |
| | |
Use the library pwquality to check password complexity and improve security.
Additionally, optional enable support is also set in CMake.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This is a very limited bit field, so use an 8 bit type to clearly show
how many bits are available.
|
| | |
| | |
| | |
| | |
| | | |
The different uses of this interface are not that closely related and
there is no need for them to have a common interface class.
|
| | |
| | |
| | |
| | |
| | | |
Follow the standard XK_ prefix, and also include the hex value for
easier debugging.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of giving up after all free keycodes have been used, Keycodes from previously added keysyms will be reused.
Re: #93
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
An empty shell field in the password file is valid, although not common.
Use /bin/sh in this case, as documented in the passwd(5) man page, since
the vncserver script requires a non-empty SHELL environment variable.
Fixes issue #1786.
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| | |
| | |
| | |
| | |
| | | |
This is what Xwayland does, so let's try to do the same to avoid any
incompatibilites with applications.
|
|/ /
| |
| |
| | |
Bug fix for bf28683.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
It's a source of confusion and possibly bugs to reuse the same variable
name for multiple things.
|
| | |
| | |
| | |
| | |
| | | |
Store the name in a std::string to make things less complex as we don't
need to be as careful about making sure the data is free():d.
|
| | |
| | |
| | |
| | |
| | | |
Remove redundant arguments where the method already has access to the
relevant variable as an object attribute.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are often more readable as they avoid a lot of the boilerplate of
iterating over fixed arrays or STL containers.
Note that this change is very conservative to avoid noise in "git
blame". Only loops where this is a clear improvement have been
converted.
|
| | |
| | |
| | |
| | |
| | | |
Let's avoid reimplementing something basic that's available in the
standard library. It also makes the code easier to read.
|
| | |
| | |
| | |
| | |
| | | |
Use the new "override" keyword to properly differentiate between new
virtual methods, and existing virtual methods being overridden.
|
| | |
| | |
| | |
| | |
| | | |
It's more readable than 0, and a bit safer than NULL, so let's try to
follow modern norms.
|
| | |
| | |
| | |
| | |
| | |
| | | |
It's rare we use a compiler that has anything older as a default, but it
does happen sometimes. So make sure to guarantee this so we can start
using more modern constructs.
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Lay the groundwork for a more intelligent selection of GPU in systems
that have multiple cards. This initial implementation simply picks the
first GPU that we have permission to open.
|
| | |
| | |
| | |
| | |
| | | |
Allows users to use a secondary GPU, or to disable DRI3 in case of
issues.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
One GNOME developer had a bad experience with VNC one time, and
therefore all VNC must forever be punished.
Avoid detection by GNOME so that animations aren't forcefully disabled
without any option for the user to re-enable them.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This provides buffer sync with the primary render node of the system (if
available). By doing so, OpenGL and Vulkan can use the render node for
acceleration.
This first implementation is extremely pessimistic and synchronises
buffers whenever there's even a slight chance they will be used.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It was incorrectly designed to only build properly if built as part of
the "Xorg" server and could fail to build when just "Xvnc" was built.
Backport of upstream commits 0ce93e5 and acc581c.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Windows aren't always directly shown, e.g. when the desktop is
composited. We should not be sending screen updates for these as the
framebuffer didn't actually change.
In the case of CopyWindow, we're even sending the wrong screen data,
which is how this bug was discovered.
|
|\| | |
|
| | |
| | |
| | |
| | |
| | | |
No current distribution uses anything older, so let's make things easier
for us to maintain.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Things do not need to be this complicated. We can make sure the VNC
extension is always included in a much cleaner way, at least since Xorg
1.16.
|
| | |
| | |
| | |
| | | |
This hasn't been needed since Xorg 1.16.
|
| | |
| | |
| | |
| | |
| | | |
Unclear why this was ever needed. libX11 is for X11 clients, and we're
building a server.
|
| | |
| | |
| | |
| | |
| | | |
Make things a bit easier to maintain. This style is also more in line
with what is being done for other DDX.
|
| | |
| | |
| | |
| | | |
This has never actually been used, as far as I can tell.
|
| | |
| | |
| | |
| | |
| | | |
Rather than disabling this, make sure the build can find the relevant
file.
|
| | |
| | |
| | |
| | |
| | | |
VENDOR_RELEASE has been available as a #define since Xorg 1.7, so let's
use that and remove all of our custom magic.
|
|\| |
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If there is something interested in synchronizing to a frame tick, then
keep the frame clock running, even if there are no updates.
This is need mainly when something starts rendering, but also when
something renders much slower than the frame clock (so it is essentially
constantly "starting"). Such an application will not draw anything until
it gets a new frame tick, which it won't get as the frame clock is
waiting for something to start drawing.
|
| |
| |
| |
| |
| |
| |
| | |
This makes it possible for applications to synchronize their updates to
the updates sent out to clients. This avoids tearing, and could in the
future also help with rate limiting applications to what the client can
actually show.
|
| | |
|