"invalid shutdown script" when closing channel

[bartoli]

I tried closing channels to a node.
But They did not go into 'pending close' state, the are in 'waiting close' instead
LND logs say

023-04-05 10:15:25.665 [INF] PEER: Peer(03c436af41160a355fc1ed230a64f6a64bcbd2ae50f12171d1318f9782602be601): Local close channel request delivered to peer
2023-04-05 10:15:25.671 [INF] PEER: Peer(03c436af41160a355fc1ed230a64f6a64bcbd2ae50f12171d1318f9782602be601): Delivery addr for channel close: bc1psxnu8n7s9cxldfp2utr2awry8cf4jvrzjplnfj8rzavqdtq4qddqt8e2n0
2023-04-05 10:15:25.671 [INF] HSWC: ChannelLink(06f45e83a4dd7a035634af148bd51ae44cf16e7a23f878d06640aa21c49e5f2d:1): stopping
2023-04-05 10:15:25.672 [INF] HSWC: ChannelLink(06f45e83a4dd7a035634af148bd51ae44cf16e7a23f878d06640aa21c49e5f2d:1): exited
2023-04-05 10:15:25.673 [INF] HSWC: Removing channel link with ChannelID(2d5f9ec421aa4066d078f8237a6ef14ce41ad58b14af3456037adda4835ef407)
2023-04-05 10:15:25.676 [INF] CHCL: ChannelPoint(06f45e83a4dd7a035634af148bd51ae44cf16e7a23f878d06640aa21c49e5f2d:1): initiating shutdown
2023-04-05 10:15:25.676 [INF] NANN: Announcing channel(06f45e83a4dd7a035634af148bd51ae44cf16e7a23f878d06640aa21c49e5f2d:1) disabled [requested]
2023-04-05 10:15:25.755 [INF] CHCL: ChannelPoint(06f45e83a4dd7a035634af148bd51ae44cf16e7a23f878d06640aa21c49e5f2d:1): sending shutdown message
2023-04-05 10:15:25.858 [ERR] PEER: Peer(03c436af41160a355fc1ed230a64f6a64bcbd2ae50f12171d1318f9782602be601): unable to process close msg: invalid shutdown script
2023-04-05 10:15:25.858 [ERR] PEER: Peer(03c436af41160a355fc1ed230a64f6a64bcbd2ae50f12171d1318f9782602be601): failed link shutdown: channel not found
2023-04-05 10:15:25.858 [ERR] RPCS: [closechannel] unable to close ChannelPoint(06f45e83a4dd7a035634af148bd51ae44cf16e7a23f878d06640aa21c49e5f2d:1): unable to process close msg: invalid shutdown script
2023-04-05 10:15:25.858 [ERR] RPCS: [/lnrpc.Lightning/CloseChannel]: unable to process close msg: invalid shutdown script

I'm not even sure if is is my node displaying it for the remote's script or the opposite.
Can i expect such error to solve itself after some delay (for one party to send a fixed script?), or should i go ahead and force close the channels?
If it is a close script from my side that is invalid, will i even be able to do a force close?

[guggero]

It looks like you're trying to close to a P2TR address, which the remote doesn't understand yet... Can you attempt to close to a P2WKH address instead? If a second close attempt isn't possible, you might need to force close the channel instead.

[bartoli]

I ended up force closing. I assumed that the close address had been determined at channel opening, so if it was not supported i could never properly close.
What would have been the rough lncli commands to do this?
Could this be considered a RTL bug, if the channel was open or closed by RTL-issued-commands with that wrong address?
Thanks for the answer

[guggero]

Yes, there's the --delivery_addr flag in the lncli closechannel command. But that can only be set if the address isn't set at channel open time (which it might or might not be, depending on how the UI implements it. It's called "upfront shutdown script" internally in lnd, maybe you have such an option in RTL?). So not sure if this would be a bug in RTL, maybe just a feature request that you can specify the delivery address when closing a channel?