Bugreport on "Gsequencer" Case:
- Kernel I've been using while using Gsequencer was a non-debian build
that has RT support. (built on this system by me)
Bugreport on Debian Kernel Backports: --- I am about to file a report.
- bpo Kernel has an issue: Chrome cannot start and complains about
not being able to run due to not being able to create a "sandbox"
-> ( fwiw I'm filing a report on this to
linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned )
Kernel rebooted my system and sticking with my custom boot-kernel for
now as I can run chrome again.
I did not check to see if I can run gsequencer with the bpo kernel.
I am using the basic "make deb-pkg" with RT patches. gcc-8 was used to
compile this kernel.
I am using other RT applications such as ardour, and jackd2/jackdbus and
I'm not noticing issues..
cat /proc/version
"Linux version 5.2.14-rt7 (customx@debian) (gcc version 8.3.0 (Debian
8.3.0-6)) #1 SMP PREEMPT RT Mon Sep 30 05:58:30 EDT 2019
"
On 2019-11-13 5:50 a.m., Joël Krähemann wrote:
Hi,
thank you for reporting the bug.
Do you use a custom realtime kernel configuration?
best regards,
Joël
On Tue, Nov 12, 2019 at 10:18 AM westlake <westlake2...@videotron.ca> wrote:
Package: gsequencer
Version: 2.1.53-2
Severity: important
stalls a system that is running on an RT kernel
