Could not resolve //guest's address: nodename nor servname provided, or not known

Flame Flame Questions
1

2026.2.1. I’m seeing these popup every too often in the shell accompanied by a pause.

Could not resolve //guest's address: nodename nor servname provided, or not known
Could not resolve //guest's address: nodename nor servname provided, or not known
Could not resolve //guest's address: nodename nor servname provided, or not known

Anyone seen this before? There’s just something about 2026 man…

2

Is this in a setup restored from an archive? I’ve seen it with setups that were archived somewhere else.

1 Like
3

That is why we gave up with 2026+. Just sticking with 2025 until doom is over.

1 Like
4

I mentioned it earlier as well, but I thought it had to do with setting up Shade. Still seeing it now that Shade has been removed so it’s definitely a 2026 thing.

1 Like
5

There are multiple artist on multiple machines. I have some of those batches loaded on the desk. I’ll remove them all and see if there’s any impact.

6

So fresh desktop, none of those batches loaded. Issue persist. Opened a support call. Sigh.

7

Please provide the Full Diagnostic (from Service Monitor app) to Support if not already done.

8

Done. Not surprisingly this looks to be a Flame issue with lucid.

9

For what it’s worth, I was seeing this once I installed Shade and before installing Lucid so I think it’s more related to these types of filesystems in general.