Pages matching "mcl" in Launchpad

I would like to have a startup option to launch Slingshot without the triangular pointer near the upper left corner. When I launch Slingshot from Plank the triangular pointer is misleading. The logic behind launching Slingshot from Plank is less mental overhead and less physical work. I don't have to journey to another spot on my screen to open an app if I can't see it in the dock.

Here's a branch to stop using mlockall and instead selectively secure the pieces of memory we use for passwords. I didn't bother fixing the liblightdm libraries. The greeters are relatively shortlived and can use mlockall just fine. And for the session-child code, I continue to use mlockall. 'man pam_conv' indicates that PAM modules expect to be able to free the pam_response structs themselves ...

client buffer stream: always signal wait handle and invoke callback even during creation errors The wait handle given to the client should always be signaled and the client supplied callback must be invoked even if the server fails to create the buffer stream. Clients can use mir_buffer_stream_is_valid to determine if a buffer stream was created succesfully.

Avoid leaking client platform modules, and particularly ensure unused modules are not kept resident while the client is running (LP: #1527449) This also fixes crashing clients (LP: #1526658) due to Mesa's dlsym calls landing on the wrong symbol versions.However that fix only works for future Mir releases and not retrospectively because of the dlopen leak in client_ platform_ factory. cpp ...

Avoid leaking client platform modules, and particularly ensure unused modules are not kept resident while the client is running (LP: #1527449) This also fixes crashing clients (LP: #1526658) due to Mesa's dlsym calls landing on the wrong symbol versions.However that fix only works for future Mir releases and not retrospectively because of the dlopen leak in client_ platform_ factory.

add MirExtensionGbmBufferV2, which adds functions that help a GBM buffer import in the mesa driver. This prepares mir_buffer_get_buffer_packgae (and MirBufferPackage) for deprecation. Integrated with the 'rs' platform (in the current naming) Mesa patch on the ML. Also, spent some time considering whether the extension should just return a gbm_bo*.

I could have just hacked examples/eglapp.c and declared the bug fixed, but that would not suffice for other toolkits (particularly games). So this more long-winded solution solves the problem for everyone. I also investigated the possibility that our dumb demo code was simply not finding the best EGLConfig by virtue of always truncating the list of configs to length one.

#1377743: indicator services restart after every resume #1366534: lightdm lefts a11y (at-spi*) process behind This solution is better than one used in debian, but I don't like it too. It's still possible to see lightdm's at-spi processes after login in some cases. Needs testing.

Avoid allocating mir::protobuf objects on the stack When an addition is made to a protobuf message, a stack allocation of such object may differ from what the destructor of that message is expecting as the destructor is defined by libmirprotobuf and the allocation may have been made from an older definition of the message (by an older mirclient library for example) which can lead to stack ...