Both Physical Printer Tab and Prusa Connect Login Popup are Blank #12969
Comments
|
Yes exactly that I was afraid , each time you close the slicer then you have to re write the name and password !! that why mozilla is best for such reminding.. and hope you find solution that not forced user to log in prusa acc !! for my all customer it's not good .. |
That is not my issue. I cannot enter the login password into the slicer at all, as the dialog box pops up blank and never fills in. The same happens with the Physical Printer tab. My guess is the Webkit integration is not working correctly. There are no error messages related to the popup or page selection, but lots of error messages when started on the command line. |
|
oulla are you sure is not missing 1 files !!!!!!!!!!!! haha so much..... |
|
Just installed the Slicer Version 2.8.0 via Flatpack on Linux Mint 21.3.
I can see changes in the Cursor when hovering the Form. I can click on something, but I don't know what happens ;-) |
|
I'm having the same issue: Version 2.8.0+linux-x64-GTK3 running on Kubuntu (KDE desktop) 18.04. Everything in the slicer works fine, but it doesn't show anything but a blank screen under 'Prusa Connect'. I should add that the Prusa Link interface is working fine (after figuring out that I needed to specify login information). |
|
Same problem on v2.8.0 on Win 11 x64:
I just updated from v2.6.4 which was fine, Completely uninstalling & reinstalling from scratch doesn't fix it. |
|
Same issue on NixOS 24.11 Vicuna. I attached a log snippet of what happens when I attempt to open the login window. |
I tried to see if I could interact with anything, by selecting all and dragging, and I got this: There doesn't appear to be anything else hidden as far as I can tell. |
|
So, @30350n found out that these invisible messages briefly tell you to install Can someone on another OS try this to see if it works? |
|
I'd love a fix for my Linux installation and would be interested in building here. However, I'm not an expert on cmake and you have not provided quite enough detail for me to proceed. |
|
(In theory you shouldn't have to mess with cmake at all, but just install |
|
I do have it installed. I'm still running Ubuntu 18.04 LTS since upgrades break too many things. I extracted the contents of the release Appimage and checked all compiled objects with 'ldd'. The slicer itself is dynamically linked to libglib.so.blah, but that's the extent of obvious glib references. I guess I don't understand the "..once we rebuilt the package with that in the buildInputs.." statement above. |
|
Ah, if you are using the AppImage then this is probably not going to be helpful. The |
|
I cannot build from source on Ubuntu 18.04 LTS. The available Boost library is one minor version too old, apparently. One of these days I'll upgrade my system... For now it's the end of the line. |
Curiously, I am also running NixOS, and encountered the bug even after your I managed to solve it by disabling Webkit's hardware acceleration, done by running the program with Apparently, at least for one person in that thread, the problem was caused by a version mismatch between the system's Mesa libraries and those used by I'll have to get back to you after trying the more proper fix of building For reference, the stderr in my case has a few more error messages compared to the ones posted above: PrusaSlicer output |
Yeah I also noticed this while testing the patch. You could probably get that setup to work though by using an |
|
That environment variable did not change the misbehavior on my system. When I login to my Prusa account and select the Prusa Connect tab I get an immediate system notification that Webkit has crashed along with a blank window. |
Thanks! For reference (and now I'll stop hijacking this ticket with NixOS specifics) the following did the trick: unstable.prusa-slicer.override {
wxGTK-override = lib.lists.findSingle (p: p.pname == "wxwidgets-prusa3d-patched") null null pkgs.prusa-slicer.buildInputs;
}(where
Dang, sorry to hear that! I guess there are several issues masquerading as similar ones at play. I definitely think upgrading your system would be the right way to go, as you noted. Until then, my suggestion from a general troubleshooting perspective would be to try to run PrusaSlicer from a Live CD for a newer Ubuntu version, just to confirm whether or not upgrading your distro would solve it. Or in a virtual machine. |
|
Just FYI, I am able to build on Ubuntu 22.04.4 LTS. I actually pulled the source and built on Aug 13, in case that makes a difference. I was able to build with the directions, with no problems at all. And the Login window works. It is not empty. |
|
It doesn't even come close to building on Ubuntu 18.04 LTS. Many pre-reqs missing and despite verbiage in the build instructions it makes no attempt to get them. I'm hoping to install 24.04 LTS soon. |
|
I can also confirm on Ubuntu 24.04 LTS that the window login and connect are blank. Running with WEBKIT_DISABLE_COMPOSITING_MODE=1 works, but only for regular deb and appimage for both 2.8.0 and 2.8.1. |
|
I just figured out it is related to webkit using dma mode (especially for nvidia graphic cards) being introduced with 2.41.1. Running WEBKIT_DISABLE_DMABUF_RENDERER=1 seems to be the proper solution instead of WEBKIT_DISABLE_COMPOSITING_MODE=1. See related details here, here and bug report related to nvidia drivers (and recommendations): here |
|
Interesting! I spun up a VMware guest running Debian Bookworm and the Connect tab are working correctly in that environment. I did note that Prusa is distributing (2) different versions of the slicer and it appears that Ubuntu 24.04 requires a different build from what I used. The "Ubuntu" build requires a newer GLIBC version than Bookworm. |
|
Hello. Thank you all for testing and proposed solution. We are going to add setting either WEBKIT_DISABLE_DMABUF_RENDERER or WEBKIT_DISABLE_COMPOSITING_MODE during startup of PS. Please let us know if there are any users whose problem is solved only by WEBKIT_DISABLE_DMABUF_RENDERER=1 or WEBKIT_DISABLE_COMPOSITING_MODE=1. Thanks! |
|
Hi, I can confirm on Debian "bookworm", using proprietary Nvidia graphics drivers, using PrusaSlicer installed via flatpak, the window login and connect tab are blank. Fixed using either WEBKIT_DISABLE_DMABUF_RENDERER=1 or WEBKIT_DISABLE_COMPOSITING_MODE=1. Thanks for the help! |
|
Neither of those parameters work on Ubuntu 18.04 LTS. I'm planning to upgrade my base install to Debian Bookworm in the near future and brought it up on a VM for testing. So far it does seem to work properly in that environment. |
|
For anyone using flatpak, you can set the environment variable permanently with: Then you can launch the app as usual. You can run the same command with |
|
I've found that the environment setting is required on Ubuntu 24.04 but not on the upstream Debian Bookworm. Probably down to the version of Webkit. It has never worked on Ubuntu 18.04, but that's getting long in tooth. |
This worked perfectly for me, thank you |
|
I can confirm that on CachyOS (Arch Linux) using proprietary Nvidia graphics drivers, using either WEBKIT_DISABLE_DMABUF_RENDERER=1 or WEBKIT_DISABLE_COMPOSITING_MODE=1 fixes the issue. |
|
Can you guys please retest this in 2.9.0-alpha1? Thanks. |
I can confirm it works with the alpha1 as available on flatpak beta, I have also disabled the env var:
|
|
@miquelbeltran Thanks for getting back. Do you need to set the env var explicitly? It should no longer be needed with 2.9.0-alpha1. |
Nope, I have already removed it from my flatpak setup, to ensure I ran Running |
|
@miquelbeltran Sorry, I misread your first post and thought that you set the variable, when you really unset it. I'm glad that it works for you now. |
|
To everyone affected, please try the AppImage linked in and please let us know how how it works for you. Thanks! |
Same/Similar issue here: I cannot log into my account in PrusaSlicer. Ver. 2.8.1 and Windows 11. When I open Slicer and click on "Log in" nothing happens, then I get the spinning circle cursor for many minutes. Clicking on the screen gets a fogged over look. X'ing out of the program gets the standard "Close" or "Wait" option when a program is hanging. |
Description of the bug
On updated RHEL8, both the Physical Printer Tab and Prusa Connect Login Popup are Blank. They worked once, but after closing and opening Prusa Slicer again, they are blank. Prusa Link to the printer and Prusa Connect work on a browser.
Project file & How to reproduce
Open Prusa Slicer. Click on Physical Printer Tab or the Login icon at top right.
Checklist of files included above
Version of PrusaSlicer
Physical Printer Tab and Prusa Connect Login Popup are Blank
Operating system
RHEL 8
Printer model
Mini
The text was updated successfully, but these errors were encountered: