Flaresolverr-tak :: how to launch xvfb


Hello,

I do not know if this authorization is the right way to be able to achieve my goal.

I asked help on how to be able to launch a xvfb, but go no answer:

The snap is in manual review since December without any answer.

I need to remove the manual review to publish new version of the snap, and then put it back.

Thanks <3

This request has been added to the queue for review by the @reviewers team.

Hello @TehAppKiller and sorry for the late response!

To ensure I understand the requirement: you are requesting the x11 slot because your snap needs to run xvfb (or xvfb-run) to support the headless browser used by FlareSolverr.

Before we proceed with manual authorization for a privileged interface, have you considered bundling xvfb inside the snap (e.g., adding it to stage-packages)?

Feel free to ping us for any further assistance :slight_smile: (#askForInfo)

Hello @yomonokio ,

Thanks for the reply.

  • As you can see in the snap yaml code, it is the case, xvfb is included in the stage-packages, plus it’s working fine on a local PC with x11 authorization.
  • As stated, I don’t know if x11 authorization is the best way to do this, if another way exist, or if you need to develop an interface to allow this to make things proper

xvfb needs to create a virtual display and thus accessing config files that are protected by snap rules.

If it helps, here the process of my tests with xvfbwrapper, with /tmp problem:

Hello again!

I’ve tried running some tests to make this work without the X11 interface, but none were successful. Because of this, I’m inclined to support the auto-connection of the interface. What do the other @reviewers think?

oHi o/

Can I remove the snap’s review from queue

To update Stable version

And put this release back in queue

until I get an official reply ?

Thx <3

Hey folks,

Sorry for the delay in my response. I don’t think we can grant it for various reasons:

  • x11 slot should not be granted unless the use case is approved by a snapd architect. Having multiple sources providing a given slot (implicit + snap) prevents other snaps from auto-connect, as snapd does not know which slot to use
  • x11 slot is super-privileged, thus publisher vetting would be required. In order to complete the publisher vetting, snap publisher must be member of the application upstream project or a trusted group (i.e. snapcrafters).

Thanks for the feedback @jslarraz

I understand that x11 is an important authorization and that’s why I asked if there was an alternative to create a virtual display without that “whole” authorization.

Now, what are the options:

  • Is there alternative way to create a virtual display ?
  • Can an extension/feature be developed in Snapcraft for xvfb ?
  • Should I transmit the snap to Snapcrafters ? → no problemo
  • Should I drop the snap ? :confused:

Thanks again <3