std::exception::what: Image is too big for GBM cursor buffer

[Alberto Aguirre]

When using:

auto stream = mir_connection_create_buffer_stream_sync(connection, 500, 166, mir_pixel_format_argb_8888, mir_buffer_usage_software);

//Fill in buffer stream

auto configuration = mir_cursor_configuration_from_buffer_stream(bufferStream, 0, 0);
mir_window_configure_cursor(window, configuration);

In the server, this results in:

[2017-02-09 09:49:52.789913] <ERROR> evdev: Failure processing input event received from libinput: /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/platforms/mesa/server/kms/cursor.cpp(150): Throw in function void mir::graphics::mesa::Cursor::pad_and_write_image_data_locked(const std::lock_guard<std::mutex>&, const mir::graphics::CursorImage&)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >
std::exception::what: Image is too big for GBM cursor buffer

[Alberto Aguirre (albaguirre)]

Seems like we need to be able to fallback unto software cursor dynamically as a new cursor image is configured.

Right now we only support fallback if hardware cursor creation fails.

[Daniel van Vugt (vanvugt)]

No problem... I'm working on dynamic cursor fallback right now. And prerequisite branches are up for review.

[Michał Sawicz (saviq)]

Syncing task from Mir.