maliit crashes on plasma 6.4

[José Abílio Matos]

Hi,

ever since I updated to plasma 6.4 (the first beta) that I have reports about 
maliit crashing:

Jun 25 08:31:43 griffin kwin_wayland_wrapper[4429]: terminate called after 
throwing an instance of 'std::bad_alloc'
Jun 25 08:31:43 griffin kwin_wayland_wrapper[4429]:   what():  std::bad_alloc
Jun 25 08:31:44 griffin maliit-keyboard[13983]: QSoundEffect(pulseaudio): 
Error decoding source file:///usr/share/maliit/keyboard2/sounds/
key_tick2_quiet.wav
Jun 25 08:31:44 griffin maliit-keyboard[13983]: QSGContext::initialize: depth 
buffer support missing, expect rendering errors
Jun 25 08:31:44 griffin maliit-keyboard[13983]: QSGContext::initialize: 
stencil buffer support missing, expect rendering errors
Jun 25 08:31:51 griffin kwin_wayland_wrapper[13983]: terminate called after 
throwing an instance of 'std::bad_alloc'
Jun 25 08:31:51 griffin kwin_wayland_wrapper[13983]:   what():  std::bad_alloc
Jun 25 08:31:52 griffin maliit-keyboard[14074]: QSoundEffect(pulseaudio): 
Error decoding source file:///usr/share/maliit/keyboard2/sounds/
key_tick2_quiet.wav
Jun 25 08:31:52 griffin maliit-keyboard[14074]: QSGContext::initialize: depth 
buffer support missing, expect rendering errors
Jun 25 08:31:52 griffin maliit-keyboard[14074]: QSGContext::initialize: 
stencil buffer support missing, expect rendering errors

As far as I can see this is trying to play the key_tick2_quiet.wav file but it 
is not there. Not only the file does not exists but that directory is also 
absent.

/usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav

This is mildly annoying because this crash occurs frequently. The option is 
either to ignore these reports or to change the virtual keyboard. :-)

Best regards,

[Neal Gompa]

On Wed, Jun 25, 2025 at 9:49 AM José Abílio Matos via kde
 wrote:
> Hi,
>
> ever since I updated to plasma 6.4 (the first beta) that I have reports about maliit crashing:
>
> Jun 25 08:31:43 griffin kwin_wayland_wrapper[4429]: terminate called after throwing an instance of 'std::bad_alloc'
>
> Jun 25 08:31:43 griffin kwin_wayland_wrapper[4429]:   what():  std::bad_alloc
>
> Jun 25 08:31:44 griffin maliit-keyboard[13983]: QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav
>
> Jun 25 08:31:44 griffin maliit-keyboard[13983]: QSGContext::initialize: depth buffer support missing, expect rendering errors
>
> Jun 25 08:31:44 griffin maliit-keyboard[13983]: QSGContext::initialize: stencil buffer support missing, expect rendering errors
>
> Jun 25 08:31:51 griffin kwin_wayland_wrapper[13983]: terminate called after throwing an instance of 'std::bad_alloc'
>
> Jun 25 08:31:51 griffin kwin_wayland_wrapper[13983]:   what():  std::bad_alloc
>
> Jun 25 08:31:52 griffin maliit-keyboard[14074]: QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav
>
> Jun 25 08:31:52 griffin maliit-keyboard[14074]: QSGContext::initialize: depth buffer support missing, expect rendering errors
>
> Jun 25 08:31:52 griffin maliit-keyboard[14074]: QSGContext::initialize: stencil buffer support missing, expect rendering errors
>
> As far as I can see this is trying to play the key_tick2_quiet.wav file but it is not there. Not only the file does not exists but that directory is also absent.
>
> /usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav
>
> This is mildly annoying because this crash occurs frequently. The option is either to ignore these reports or to change the virtual keyboard. :-)

Weird. Can you file a bug in RHBZ about it against maliit-keyboard about it?

[José Abílio Matos]

On Wednesday, 25 June 2025 09:04:36 Western European Summer Time Neal Gompa 
wrote:
> Weird. Can you file a bug in RHBZ about it against maliit-keyboard about it?

Even weird, after disabling the virtual keyboard in System Settings (searching 
for virtual) I selected no virtual keyboard (None) and applied.

I saw the orange dot, the usual notation to show that the options are not the 
default ones. I applied and closed the System Settings.

After your message I went back, with the intend to re-enable it again to give 
further details.

In the process I found two things:

1. mallit is selected;
2. even with mallit selected the problems/crashes are gone.

So this seems some kind of blue moon bug and I will forget for now. :-)

Thank you for the assistance, best regards,