Linux - Device tab not displaying klipper interface

[TexZeTech]

Slicer version: 1.6.2

Describe the bug The device tab is not displaying the mainsail interface.

To Reproduce 1.) Install a fresh instance of Manjaro in a vm (as of this time manjaro-kde-22.1.0-230421-linux61.iso ) 2.) Install Appimagelauncher and dependencies 3.) Install webkit2gtk, Webkit2gtk-4.1, Webkit2gtk-5.0 and any dependencies 4.) Run appimage (integrate or just run it) 5.) Add a generic klipper printer and install Bambu network 5.5) try the device tab to see if the video plays. 6.) Go to network on the printer and enter IP address -> enter -> test 7.) Close the network config and click on "Device" 8.) nothing

Expected behavior To use the device tab to interact with Mainsail (or other not tested) interface(s).

Screenshots

Notes: I have also used this Aur and had the same result.

OS & Hardware of main machine: Operating System: Manjaro Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.25-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2

OS & Hardware of VM: Operating System: Manjaro Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.25-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-3770K CPU @ 3.50GHz Memory: 5.7 GiB of RAM Graphics Processor: llvmpipe Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2

Aditional notes: This was working at some point previously on my system. :shrug: Any help would be appreciated.

[hliebscher]

can you open the web interface in firefox?

[TexZeTech]

@hliebscher I haven't tested that in the VM but yes I can.

[hliebscher]

sometimes have other private ip networks no routing pls test in VM

[HakunMatat4]

This is actually awesome, I didn't know this was a thing.

Mint Cinnamon (DEB) is working fine.

@TexZeTech if you don't mind me asking why VM and why Manjaro instead of a popular and stable distro like Mint?? Or even worse, Ubuntu??? I remember trying it with Windows VM when Linux did not even had AppImage and boy, what a poop.

Either way, make sure the VM network isn't set as NAT but Bridge without replicating, so the VM can have a physical network access without virtualization. NAT can be a poop sometimes.

[TexZeTech]

@H4kunaM4tata Happy you discovered a feature :+1:

As to your questions the VM was to verify it's not something I did with my main computer as for why Manjaro & not Ubuntu, Debian, Fedora, Windows, Mac... preference at this point in time?

I'm just trying to find out what is missing as to end up breaking this function, as it was working at a previous point in time. I have installed what I perceive as the dependencies required with no change in that so it's going to be something dumb.

And I just tried v1.5.0 and had the same results.

I will go poke the Manjaro forum as well when I get a chance & leave this open so when I get results I can post the fix here as well.

[HakunMatat4]

I see, for what it's worth it, when we started supporting the guys to have the AppImage, It was a total rollercoaster and ironically SoftFever back then was the only version giving way less headache.

Ticket number is 12 under BambuLab repository (not here) you might ask there, it will be a lot easier and faster to have a feedback since its still active and being supported by legends.

It's all about Linux, AppImage, issues, you name it. I don't think this issue is from OrcaSlicer, I remember asking SoftFever to make changes that were broken on BambuLab and pushed to SoftFever regarding the AppImage.

Anyway, pay that ticket a visit.

[adrian-dobre]

This started happening to me on Mac OS (Intel) today, after installing the latest version. Switched back to the old one (was still installed) and the problem remains, which points to some misconfiguration that remained on the hard drive

[bjw-s]

Chiming in with a +1 on MacOS. On the very first startup I can see the howto video. I went on to set up the physical printer, closed and reopened Orca and then I am just getting a white screen whenever I go to the Device tab

MacOS version: Ventura 13.4 OrcaSlicer version: 1.6.3 Apple Silicon

[Rokin05]

Same bug with OrcaSlicer version 1.6.3 on Arch (Aur: https://aur.archlinux.org/packages/orca-slicer) mainsail/klipper work fine on web browser

[TexZeTech]

Still present in Orcaslicer V1.6.4 Beta app image. ~I'll install a fresh vm of Manjaro later and see if anything changes in that.~ I have installed a fresh vm and fully updated Manjaro from manjaro-kde-22.1.3-230529-linux61 base install. Added libappimage and webkit2gtk to launch. Still results in a blank screen in the device tab when trying to view mainsail. If there is nothing on the network filed it displays the how-to video.

[Jakeo-93]

+1 for this. Appimage on a arch based distro and the device tab remains black. Mainsail works fine in webbrowser

[Spotigus]

+1 as well. Does not work on linux mint.

[TexZeTech]

Still present in 1.6.6 appimage

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.1.44-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2

[TexZeTech]

Still present in 1.7.0 beta appimage.

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.1.51-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2

[HakunMatat4]

It stopped working for me after 1.6.6 For what it is worth, there seems to be some weird network stuff going on. The slicer somewhat is still sending files over to the printer, Voron, so I am okay with that.

[djovic78]

Still present with the 1.7.0 beta appimage on KDE Neon (Basically Ubuntu)

Operating System: KDE neon 5.27 KDE-Plasma-Version: 5.27.7 KDE-Frameworks-Version: 5.109.0 Qt-Version: 5.15.10 Kernel-Version: 5.17.0-1035-oem (64-bit) Grafik-Plattform: Wayland Prozessoren: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Speicher: 31,1 GiB Arbeitsspeicher Grafikprozessor: Mesa Intel® Xe Graphics Hersteller: LENOVO Produktname: 20Y0S00200 Systemversion: ThinkPad X1 Yoga Gen 6

[Dev01-D]

Confirmed issue with latest 1.7 appimage, I get this with my Linux box running POP!_OS Device connection confirms test is ok.

Using normal web browser works fine.

[alanmakestuff]

Confirmed issue with latest 1.7 appimage, I get this with my Linux box running POP!_OS Device connection confirms test is ok.

Using normal web browser works fine.

Same with my Pop_OS 22.04 LTS. Blank tab. Works fine in browser. Installed Appimage.

[ReneSchmidts]

+1 for this. The device tab is not displaying the mainsail interface. 1.7 appimage on Linux Mint 21.2 Device connection confirms test is ok. Sliced files are send to the printer directly without any issues. The mainsail interface is working using Firefox.

Additional notes: The device tabs window is getting black at all (like Mainsails background), as soon the printer is online. For me it seems Orca Slicer is establishing a connection to Mainsail, but not able to show the screens information.

[Cyber-Garret]

Same for me on Linux mint 21.1 cinnamon edition, Fluidd work in device tab, but "Mainsail" show blank tab = ( P.S. in Chrome browser all work as expected.

[eloo]

i have tested some stuff with orca-slicer and mainsail but sadly not found the cause..

but maybe it helps for further investigation.

i have tested the following:

• Disable cors in moonraker -> no change
• Disable authorized clients in moonraker -> no change
• Check logs from mainsail (nginx) -> call to mainsail looks okay, at least requests are send and response code looks good
• Append some path to url (like webcam) -> works, but its the landing page of webcam
• Append "index.html" to url -> does not work
• "Deactivate" the websocket -> does not work

so i guess the issue is "somewhere" loading and processing the javascript stuff..

but, i have seen that bambustudio now supports third party printers as well.. so i will give this a try and maybe @SoftFever can find the "missing piece" here https://github.com/bambulab/BambuStudio/commit/efd65561a2de060c154eb5e7fb559bb7a8ae0a17

funfact: bambustudio webview is based on the code from here ;)

i will update when i have tested bambustudio

update: with bambustudion i see the same issue, still all black

[eloo]

i'm not sure what happend..

but the device tab is now working for me :D

here are my current versions in mainsail

the "Device UI" is set a DNS name in local network (http://mainsail.lan)

orcaslicer version: 1.7.0 os: manjaro

[TexZeTech]

Well, my laptop seems to work again after a system update, my tower on the other hand is more broken now.... I'll need to find out what the difference is between the packages installed on the systems.

urgggg

[ReneSchmidts]

Here some news that might be helpfull searching for the issues source (I hope). I do have a second printer running a DUET2 with RepRap. This was working correctly in the Orca device tap until a few minutes ago. Linux Mint installed an update to GTK & Java...... since that time the Orca device tap is staying white for Klipper and RepRap

[darco415]

Im on Linux Mint, I switched over to Nouveua drivers and the black screen issue went away, Im back because now I get a :Could not connect: Connection refused error when opening the device tab. Browser works fine...using 1.8 dev but 1.7 is also a problem

[rvanderson]

Not sure if this is the same problem anyone else is having, but I had both a username and an API in the connection screen. Removing the name and using only the API key seemed to fix the problem immediately.

[darco415]

Not sure if this is the same problem anyone else is having, but I had both a username and an API in the connection screen. Removing the name and using only the API key seemed to fix the problem immediately.

wow dude, that fixed it for me!..running 1.8 stable edit removed Device UI 0000

[adrian-dobre]

Clearing the Device UI field fixed it for me also:

[TexZeTech]

Clearing the Device UI field fixed it for me also:

I don't even know anymore it's working now maybe something was in there for me.

[TexZeTech]

So I think I just found the fix for my issue.

I'm running NVIDIA proprietary drivers. I added nvidia-drm.modeset=1 nvidia-drm.fbdev=1 to my Grub boot and that seems to have fixed it. I'm also currently on X11 for my Graphics platform.

[Akucuki]

So I think I just found the fix for my issue.

I'm running NVIDIA proprietary drivers. I added nvidia-drm.modeset=1 nvidia-drm.fbdev=1 to my Grub boot and that seems to have fixed it. I'm also currently on X11 for my Graphics platform.

The same issue, and enabling drm didn't help, having the same problem with the home and project tabs and the app in general is very slow to switch between any of the tabs.

[Akucuki]

The problem seems to be with the webkit2gtk with the versions higher than 2.42.5-2. Downgrading back to 2.24.5-2 eliminates all of the issues with blank and laggy tabs. Works like charm now.

[Zincr0]

Don't know why this bug is "closed", the issue still happens on orca 2.1.0

[TexZeTech]

Don't know why this bug is "closed", the issue still happens on orca 2.1.0

Because I have a roiling release dumb things break. Manjaro causes some issues when you have the AUR enabled as Manjaro in their infinite wisdom holds back updates in the name of stability but AUR doesn't do that so I get some things to break from time to time. (Yes I could just be bad at managing my system)

Because I've experienced and continue to experience this + new/different issues on my old computer that has an old install that is likely broken in some dumb way and I cannot replicate this on my laptop as stated above.

So the issue seems to be related to libwebkit2gtk from what I've seen.

I also did "fix" the issue at the time of me closing this by adding the nvidia.drm tag in my grub file. I have since had the same issue pop up again and my welcome screen is blank but not on my laptop.

You also haven't added anything useful to try and debug this like below (at a minimum).

I would also recommend adding what Graphic drivers you are using Nvidia with nouveau or propriatry, etc. + log files.

Operating System: Manjaro Linux 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.6.32-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3337U CPU @ 1.80GHz
Memory: 3.3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: TAICHI31
System Version: 1.0