SoftFever / OrcaSlicer

G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)
https://discord.gg/P4VE9UY9gJ
GNU Affero General Public License v3.0
6.18k stars 711 forks source link

Appimage device tab unable to display Mainsail or Fluidd #6043

Open masterjuggler opened 2 weeks ago

masterjuggler commented 2 weeks ago

Is there an existing issue for this problem?

OrcaSlicer Version

2.1.1

Operating System (OS)

Linux

OS Version

Fedora 40

Additional system information

No response

Printer

Custom corexy running klipper

How to reproduce

  1. Install webkit2gtk
  2. Add WEBKIT_DISABLE_DMABUF_RENDERER=1 env variable
  3. Run Appimage
  4. Add printer local ip to network settings and test connection
  5. Go to device tab

Actual results

Mainsail displays Initializing bar and freezes. Fluidd Makes it to an interface and freezes before all elements are loaded.

Expected results

Klipper interface (Mainsail or Fluidd) displays.

Project file & Debug log uploads

debug_Sat_Jul_06_09_50_10_991747.txt

Checklist of files to include

Anything else?

I can access both webui's no problem in a browser, and I can access another web page i.e. google.com in orcaslicer. I am able to upload gcode files from orcaslicer. The video in the device tab also runs when I have no local ip entered in the printer's network settings.

ElectricalBoy commented 1 week ago

This is an upstream issue happening, well, somewhere (WebKit, NVIDIA, or somewhere in between) See https://github.com/elementary/browser/discussions/104#discussioncomment-8654515 for a possible workaround.

masterjuggler commented 1 week ago

See elementary/browser#104 (comment) for a possible workaround.

I actually already have nvidia-drm.modeset=1 passed as a kernel parameter from when I set up gpu passthrough VFIO, and I double checked it is set in /sys/module/nvidia_drm/parameters/modeset.

If it is somewhere upstream, how do I even go about finding the source of this issue?

masterjuggler commented 1 week ago

Just so we're on the same page about what exactly is happening, the device tab does seem to load and initially connect, but then freezes when it tries to load the UI. I added a couple of clips showing the exact behavior:

Peek 2024-07-07 09-12 Peek 2024-07-07 09-15

ElectricalBoy commented 1 week ago

Yeah, then the old comment I originally made seems invalid. Did you give a shot at the latest nightly build?

masterjuggler commented 1 week ago

Just grabbed the latest nightly and see no difference in behavior unfortunately. Going back to older versions like 1.9.0 and 1.7.0 doesn't seem to help either.

ElectricalBoy commented 1 week ago

What about the new nightly build with Ubuntu2404 in the name?

masterjuggler commented 1 week ago

Other than needing to install webkit2gtk4.1 to run it, unfortunately no change in behavior.

hgelpke commented 1 week ago

Experiencing the same issue on Pop OS using a 3060. Device tab works when I power on but when I do a firmware restart it can't be accessed.

Using the ip of my printer with no authentication via l/p or API

ElectricalBoy commented 1 week ago

I set up a fresh VM of Fedora 40 to test but the issue is not reproducible. This makes me suspect that it is an upstream issue related to NVIDIA in some way (although I don't have any evidence to support my claim).

masterjuggler commented 1 week ago

*Sigh* I also just spun up a fresh fedora 40 VM and couldn't reproduce the issue. Sounds like it is something to do with my setup, nvidia or otherwise. Is there a decent way to go about troubleshooting this? The logs I've seen so far for orcaslicer haven't included information relevant to this.

ElectricalBoy commented 1 week ago

This "looks" relevant: https://bugs.webkit.org/show_bug.cgi?id=250314

hgelpke commented 1 week ago

Sigh I also just spun up a fresh fedora 40 VM and couldn't reproduce the issue. Sounds like it is something to do with my setup, nvidia or otherwise. Is there a decent way to go about troubleshooting this? The logs I've seen so far for orcaslicer haven't included information relevant to this.

The common thread so far seems to be Nvidia since I'm assuming the spun up VMs are just using the generic linux display drivers and nothing installed after that.