Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER for Linux

Reply
 
Thread Tools Display Modes
Old 06-11-2022, 12:59 AM   #1
Tobbe
Human being with feelings
 
Tobbe's Avatar
 
Join Date: Sep 2009
Location: Northern Lights
Posts: 791
Default [SOLVED] What is this? zsh:killed reaper

Something went wrong the installaions. Did a new one and now everything is ok.

Over and out!

Hi,

Did a new fresh installation of Manjaro KDE Plasma, updated everything and installed Reaper and pipewire. Reaper starts ok but when I'm trying to do anything it shuts down with this error: zsh: killed reaper (sounds dramatic). Never, ever seen this before. Anyone else?

Thanks
__________________
OS: Manjaro KDE Plasma, Reaper For Linux (64Bit) native linux-vst plugins, LSP-Plugins, TpL-Plugins, Harrison's AVA & VST Plugins. Behringer U-PHORIA UMC22.

Last edited by Tobbe; 06-11-2022 at 12:08 PM. Reason: I solved the problem
Tobbe is offline   Reply With Quote
Old 06-11-2022, 02:40 AM   #2
Mikobuntu
Human being with feelings
 
Mikobuntu's Avatar
 
Join Date: Nov 2020
Posts: 153
Default

Seems like zsh is the shell your system is running. The warning does sound daunting, but it basically means you ran Reaper from the command-line and something went wrong and your system killed it.

Maybe try running Reaper with debugging on your terminal for a more detailed input of what is going wrong.

You might need to install gdb or equivalent for your system and the command to run is gdb reaper or if your system is pickey gdb /path/to/reaper , then press key 'r' followed by enter and let the magic happen. After the crash then type ' gdb thread apply all backtrace ' and keep pressing enter until there is no more output.

It may be useful to look at the output of dmesg and/or journalctl
Mikobuntu is offline   Reply With Quote
Old 06-11-2022, 06:21 AM   #3
Tobbe
Human being with feelings
 
Tobbe's Avatar
 
Join Date: Sep 2009
Location: Northern Lights
Posts: 791
Default

Thanks, I check that out. As I said before. I didn't have this on other re-installtions, this is the first time. Wonder what changed?
__________________
OS: Manjaro KDE Plasma, Reaper For Linux (64Bit) native linux-vst plugins, LSP-Plugins, TpL-Plugins, Harrison's AVA & VST Plugins. Behringer U-PHORIA UMC22.
Tobbe is offline   Reply With Quote
Old 06-11-2022, 08:27 AM   #4
Tobbe
Human being with feelings
 
Tobbe's Avatar
 
Join Date: Sep 2009
Location: Northern Lights
Posts: 791
Default

Message from gdb /opt/REAPER/reaper

Code:
(gdb) r
Starting program: /opt/REAPER/reaper 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff3fff640 (LWP 1499)]
[Thread 0x7ffff3fff640 (LWP 1499) exited]
[New Thread 0x7ffff3fff640 (LWP 1500)]
jack: created client
jack: setting TIME_CRITICAL = 81
LC_NUMERIC / LANG is set to 'sv_SE.UTF-8', overriding LC_NUMERIC environment to POSIX
[New Thread 0x7fffdcc1b640 (LWP 1501)]
[New Thread 0x7fffd6496640 (LWP 1504)]
jack: activated client
[New Thread 0x7fffd5c95640 (LWP 1505)]
[New Thread 0x7fffd5494640 (LWP 1506)]
[New Thread 0x7fffd4c93640 (LWP 1507)]
[New Thread 0x7fffd4492640 (LWP 1508)]
[New Thread 0x7fffd3c91640 (LWP 1509)]
[New Thread 0x7fffd3490640 (LWP 1510)]
[New Thread 0x7fffd2c8f640 (LWP 1511)]
[Thread 0x7fffd2c8f640 (LWP 1511) exited]
[Thread 0x7fffd3490640 (LWP 1510) exited]
[Thread 0x7fffd3c91640 (LWP 1509) exited]
[Thread 0x7fffd4492640 (LWP 1508) exited]
[Thread 0x7fffd5494640 (LWP 1506) exited]
[Thread 0x7fffd5c95640 (LWP 1505) exited]
[Thread 0x7fffd6496640 (LWP 1504) exited]
[Thread 0x7fffdcc1b640 (LWP 1501) exited]
[Thread 0x7ffff3fff640 (LWP 1500) exited]
[Thread 0x7ffff7956b80 (LWP 1492) exited]
[Thread 0x7fffd4c93640 (LWP 1507) exited]
[New process 1492]

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
Tested on Reaper 6.55
__________________
OS: Manjaro KDE Plasma, Reaper For Linux (64Bit) native linux-vst plugins, LSP-Plugins, TpL-Plugins, Harrison's AVA & VST Plugins. Behringer U-PHORIA UMC22.
Tobbe is offline   Reply With Quote
Old 06-11-2022, 08:55 AM   #5
Mikobuntu
Human being with feelings
 
Mikobuntu's Avatar
 
Join Date: Nov 2020
Posts: 153
Default

I'm not sure if jack is causing the crash or you have maybe a corrupted reaper song etc as the GDB output wasn't giving much away. Couple of things to try :-

Maybe you have reaper set to open the last used project and it has became corrupted [ sometimes happens when a vst locks your project up ] . If this is the case try opening another project by right clicking on the actual project file > open with reaper.

The errors seem to happen when Jack is being queried, so If you can open up reaper briefly see if you can change the audio driver to alsa or pulseaudio and restart reaper.

also make sure to look at your system logs with dmesg and journalctl at the point of crash. p.s you most likely want to flush the journal before running journalctl as it usually saves logs for a long time, if you need help with this let me know.

Last edited by Mikobuntu; 06-11-2022 at 09:00 AM.
Mikobuntu is offline   Reply With Quote
Old 06-11-2022, 12:07 PM   #6
Tobbe
Human being with feelings
 
Tobbe's Avatar
 
Join Date: Sep 2009
Location: Northern Lights
Posts: 791
Default

It must been something wrong with installation. I did a new one and now everything is working as it should. Thanks for your advice and help.
__________________
OS: Manjaro KDE Plasma, Reaper For Linux (64Bit) native linux-vst plugins, LSP-Plugins, TpL-Plugins, Harrison's AVA & VST Plugins. Behringer U-PHORIA UMC22.
Tobbe is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:52 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.