Tue, 16 May 2023 10:34:49 -0400 Ted Felix <t...@tedfelix.com> : > There are three issues here. Two are unrelated to the crash, but > I'll walk through them in case you want to fix them. > > > Cannot lock down 86611866 byte memory area (Cannot allocate memory) > > Cannot use real-time scheduling (RR/5)(1: Operation not permitted) > > JackClient::AcquireSelfRealTime error > > This indicates that you don't have permissions configured so that > JACK can run in real-time and lock down fixed memory areas to do its > job. This isn't likely to be the cause of the crash you are > experiencing. More likely it would cause audio glitches. I have a > webpage that addresses this issue if you are interested in understanding > and fixing it: > > http://tedfelix.com/linux/linux-midi.html
Thanks a gig for the detailed response. # uname -a Linux localhost.localdomain 6.2.10-1-default #1 SMP PREEMPT_DYNAMIC Thu Apr 6 10:36:55 UTC 2023 (ba7816e) x86_64 x86_64 x86_64 GNU/Linux > > [AlsaDriver] setCurrentTimer(): WARNING: using system timer with only > > 250 Hz resolution! > > This indicates that you are not running with a real-time kernel. > This can lead to latency and timing issues, but like the above, it's not > likely to cause a crash. Again, my webpage above explains how to solve > this issue. # grep ^CONFIG_HZ /boot/config-`uname -r` CONFIG_HZ_250=y CONFIG_HZ=250 So does this mean that I do have a low-latency but not real-time kernel? The issue raised is encountered in Suse-Leap. Rosegarden ran fine before so I presume all the configs WERE correct at one time, but usually after a number of upgrades the segfaults begin, there is no crash, just no takeoff even. Thanks for the ref, the second half is way over my head but I'll keep it for re-reading. Leap-15.5 is out in a few weeks, a fresh install or upgrade might do the trick. It will be the last 'Leap' as it has been known. > > Segmentation fault (core dumped) > > (Aside: It looks like you are running 22.12 which has a known crash. > However, it is a solid crash that would happen every time you launch > Rosegarden. If yours is crashing only occasionally, you aren't > experiencing the known crash.) > > This "Segmentation fault" is the real problem at hand and will > require some work to figure out. Not sure how far you want to dig into > this. Oftentimes it is the result of parts of your system that > Rosegarden depends on and there may be little you can do without > manually building and upgrading things. It can definitely get ugly. > > If you want to start digging into this one, you'll first need a debug > build of Rosegarden. I think SUSE is one of the distros that (oddly) > ships Rosegarden built in debug mode. That's good for figuring out > these sorts of issues. (Bad for normal use, though.) > > You'll need to find the core dump that was created when Rosegarden > crashed. It's usually called core.#####, where "#####" is the process > ID. If all is right with the world you can get a backtrace from gdb > using its "bt" command like this: > > $ gdb rosegarden core.##### > (gdb) bt > > You may need to track down the path for rosegarden and the core dump. > You may also need to turn core dumps on (sometimes they are disabled > because they are huge and can fill your drive). > > There's some old documentation on the wiki related to this: > > https://www.rosegardenmusic.com/wiki/frequently_asked_questions?s[]=%2Agdb%2A#compilation_or_installation_problems > > Let me know if you need more assistance. > > Ted. > > > _______________________________________________ > Rosegarden-user mailing list > Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user _______________________________________________ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
