Getting Notifications Since Updated Firefox and SBIE This Morning

[Theo1352]

All,

I keep getting a persistent message this morning after I update both FF 154 and and SBIE 1.18.2 :

Firefox.exe: SBIE 2112 - then various messages (I wish we could copy them).

This is happening on every site I visit, from Reddit to DuckDuckGo for search, and everything in between.

I uninstalled and reinstalled both applications, restarted, keeps happening.

There is nothing wrong with access to the sites, but loading them triggers these warnings - I have upload all these messages after each warning was triggered, so you know.

I have never had any issues between these 2, as in not ever.

I worry about this because FF is going to update every 2 weeks now.

After all these years, I simply won't run anything without Sandboxie Plus.

Any ideas what is going on and how to resolve this persistent 2112 messaging, each one different?

Thank you in advance.

 

[bastik-1001]

(I moved this thread out of Forum Discussion since it is not about the forum itself. Whatever category it fits in for Sandboxie does not matter right now.)

Hello,

I had been running Firefox 153 with Sandboxie Plus 1.18.2 (1.18.1 previously), without seeing any messages. Now I updated Firefox to 154 and do not get any messages.


My Firefox installation is a direct installation to the system, which is run sandboxed. Whenever Firefox needs to be updated, I do that outside the sandbox.

Is your installation an installation (direct) into the sandbox?

Firefox.exe: SBIE2112, Object is not available/device/named pipe/

Do you get this message only at start up of Firefox? Or does it get repeated during usage?

I had guessed that Firefox 154 changed something in its behavior trying to access something Sandboxie does not allow access to. Maybe I don't get this message(s), if that is part of a progressive rollout where a new feature (or change) does not hit all users at once.

What is it and how do I resolve this?

This message means that Firefox tried to access an object, which is not permitted to in that sandbox.

Do the messages show, what had been attempted to access?

Did you notice any change in how Firefox behaves, when the message appeared?

It could be purely annoying in which case, it could be ignored (telling SandMan not to pop up a message), but if it is some bug, it should be addressed.

I am a bit worried with the FF roadmap of now updating every 2 weeks that this might continue to happen.

It could be the case, that if Mozilla is pushing new features or changes more often to users that Sandboxie will have to adapt to changes. Sometimes nightly users of Firefox had reported issues that led to changes in Sandboxie.

 

[bastik-1001]

Now, I got this while trying to access https://www.portablefreeware.com/, which loads cloudflare trying to see if I am legit.

I got (username and sandbox name redacted):

firefox.exe: SBIE2112 Object is not accessible: \device\namedpipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-790078335-998561069-2208156648-988539944-4021756109-3505228477-4058360096\_Sandbox_$username_$Sandboxname_Session_1, call CreateFile (C0000034) access=001F0006 initialized=1 (8)

Every time I close the website and open it again, I trigger this message. Mozilla wanted to change something with their container feature, I was under the impression that it had landed in 153.

I am unaware of the scope. The developer or someone contributing code can comment on that.

Edit: So far the website mentioned above is the only one that triggered the message.

 

[bastik-1001]

Another update: I can trigger this with YouTube. Every new video triggers the same message as above.

Edit: Apparently Vimeo requires log-in, but every website with a video seems to trigger it, as I could experience on Dailymotion (which I don't use) and on Twitch (where I had noticed it, possibly). I don't know that many websites that have video, but it might that all of them are resulting in the same message.

 

[bastik-1001]

Someone created an issue for it. Axolul dug into it, so it should be easier to have this fixed sooner.

 

[bastik-1001]

Updating to Sandboxie Plus 1.18.3, which has been released a couple of minutes ago, resolved the issue. I can't trigger it anymore. In the issue, I said that I used the workaround, which I have disabled (In other words I set the option back to true) before I updated.

 

[bastik-1001]

Today I updated from Firefox 154 to Firefox 155, while Sandboxie Plus remains at version 1.18.3 and its fix still applies. There are no issues, on my end.