Ruby backtraces are not recognized anymore

[voxik]

Triggering Ruby backtrace, ABRT can't understand the stack trace. I get the following entry in journal:

srp 01 10:05:36 fedora abrt[3441644]: detected unhandled Ruby exception in '/usr/share/gems/gems/abrt-0.4.0/lib/abrt.rb'
srp 01 10:05:36 fedora abrt[3441644]: detected unhandled Ruby exception in '/usr/share/gems/gems/abrt-0.4.0/lib/abrt.rb'
srp 01 10:05:36 fedora abrt-server[3441647]: Not saving repeating crash in '/usr/share/gems/gems/abrt-0.4.0/lib/abrt.rb'
srp 01 10:05:36 fedora abrt-server[3441646]: Can't parse stacktrace: Line 1, column 70: Traceback header not found.
srp 01 10:05:36 fedora abrt-server[3441646]: Deleting problem directory rbhook-2025-08-01-10:05:36-3441644 (dup of rbhook-2025-07-21-18:22:30-2274830)

I think that the Traceback header not found error comes from here:

satyr/lib/python_stacktrace.c

Lines 166 to 170 in 6153441

	if (!local_input)
	{
	location->message = "Traceback header not found.";
	return NULL;
	}

I think back in the days, things were simpler and using Python handler for Ruby backtrace was good enough. But over the time, the Python handler got smarter, but obviously, Ruby backtrace is not Python backtrace 🤷‍♂️

Not really sure how to proceed.

[voxik]

Huh, but there is https://github.com/abrt/satyr/blob/master/lib/ruby_stacktrace.c 🤔

[voxik]

Maybe this is the culprit:

https://github.com/voxik/abrt-ruby/blob/5cd42e6cf6024e80cdccdf8c3ba2128f2717ab69/config/ruby_event.conf#L2

[voxik]

Actually, the report is displayed in ABRT. But how to avoid this error?