Dwaine Maggart wrote:There's nothing in that exit text you posted that indicates the issue is tbb related.
How did you determine that was the issue?
It's simple: Remove blender, then replace package onetbb with tbb2020 from AUR (which should be the old tbb), Resolve starts and shows its GUI. So the difference is tbb2020 and onetbb
I paste the output because Resolve only gives me such output and then quit, it may or may not be helpful, but I just paste all info I could gather here.
If Resolve starts fine, I have the following output, so it looks like it cannot start thread (which sounds related to tbb (threading building blocks):
- Code: Select all
% /opt/resolve/bin/resolve
ActCCMessage Already in Table: Code= c005, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode= 0, Level= 0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode= 0, Level= 0, CmdKey= -1, Option= 0
log4cxx: No appender could be found for logger (BtCommon).
log4cxx: Please initialize the log4cxx system properly.
18.1.4.0009 Linux/Clang x86_64
Main thread starts: 4BEA86C0
[0x7fec4bea86c0] | Undefined | INFO | 2023-03-23 08:44:10,294 | --------------------------------------------------------------------------------
[0x7fec4bea86c0] | Undefined | INFO | 2023-03-23 08:44:10,294 | Loaded log config from /home/alynx/.local/share/DaVinciResolve/configs/log-conf.xml
[0x7fec4bea86c0] | Undefined | INFO | 2023-03-23 08:44:10,294 | --------------------------------------------------------------------------------
Resolve communication is open and waiting..
Accepted new client