[Experimental Cura build for Raspberry Pi 4 now available]

17 hours ago, demod said:

 

I just signed up to let you know that you solved the problem.  Reading the link you provided about the Mystery balck window problem he provides a few things to try.  

 

I got it working ...

 

You are an absolute legend (if this works and no reason it should not!) 😁

 

I am in work now but will try this as soon as I get home as there is a lot of new functionality in the last year of releases and it will keep all of the machines I print from closer in terms of Cura versions

 

Many thanks

 

Garry

 

EDIT:  Thank you very much demod!  It works and I am now printing a test from Cura 7.4.1

For those who may have the trouble I launched the .appimage as follows after a few different incorrect commands:  

export MESA_EXTENSION_OVERRIDE="-GL_EXT_bgra -GL_EXT_texture_format_BGRA8888"&&./Cura.Appimage

 

[Experimental Cura build for Raspberry Pi 4 now available]

QSGTextureAtlas: texture atlas allocation failed, code=501

I am still getting the blacked out menus and buttons.

 

Looks like this:

Mystery Black WIndow problem

 

Does anybody recognize this error and does it look like a missing dependency or something else you think I can easily remedy. 

 

I am above my wheelhouse building software so not sure what's wrong?

 

Thanks

Garry

[Experimental Cura build for Raspberry Pi 4 now available]

These guys have built a Linux "appimage".  This is like a .exe file in windows, you can execute an app image. 

You should download the latest stable .appimage file.  Right mouse click on the file and open the properties.  Look for permissions and change the "can execute" to either your user account or everybody as appropriate.  You can then run the Cura program. 

I am curious to see how you get on as I have had a few issues with recent releases. 

G

 

 

[Experimental Cura build for Raspberry Pi 4 now available]

5 hours ago, QBall1977 said:

Gary,

 

Can you please provide a little more information on your setup.

 

what versions of RaspberryPi are you using?

 

what Operating System (and version) are you using?

 

how is the memory split setup on your Pi?

 

are you running the app image as admin (sudo)?

 

which profile if any did you choose in Cura?

 

have you tried resetting all the settings? (I think there’s a folder In you home directory(.config/Cura) ???

 

it runs very well on a 4B, Buster with 128 memory split, although menus can take a second or two to load!

Thanks QBall77

Hopefully this will give you a better idea:

Raspbery Pi Model 4 B+  2GB  (though it was the same on an 8GB)

Raspbian Buster updated and fully upgraded before this

Version info:

pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
Logged into the machine as default Pi user, launched by user Pi

Appimage started from X11 desktop. Permission set "All users may execute"

Memory split :  tried 128 and 256MB but same with both

I have reset Cura to default and re-configured

Printer profile set to suit my Creality Ender 3, default

 

Here's an image of the UI, all the buttons and menus are just black background. A user interface problem but not sure how this is built or created?

 

[Experimental Cura build for Raspberry Pi 4 now available]

Hi folks,

I am a very satisfied user of this appimage version from a little over a year ago, a real gift, thanks!  I have downloaded a couple of the newer versions to try as Cura is always evolving but there is a UI problem.  Could be just local on my Raspberry Pi but any hints very welcome.

 

The regular Cura nav bar text is not visible just a black background.  This is on both drop down menus and all of the buttons, just a black over black background.  I can activate menu or button functions but it's not practical if I can't read any text!

Is this a setting or dependency issue?  I tried to change "UI theme" but no better.  Any ideas?

 

Thanks in advance

Garry