Is it worth trying Flatpak? I am running Debian under ChromeOS, not Mint, but I see it supports Flatpak.
I have 5.6 running on my 64b x86. Details here:
I'm curious, will this work on Mint?
It's been a long time since I messed with Linux much, so maybe this is not helpful across distro's 🤔
Edited by psommerfeld
Actually, I've removed those folder earlier to be sure there’s no interference between versions.
Running 5.4 again recreate them and also stderr.log and stdout.log. But no cura.log. However 5.7 doesn't create any folders nor files in them. It doesn’t update the logfiles either when I try to run 5.7 so I doubt you find anything of interest in them. I could upload them but it’s probably a wast of time looking in them.
I’ve tested to run 5.7.2 on another machine that run Mint 20.3 and it runs fine there. So I can confirm that it’s a local error on my one machine. But I still can’t figure out what it is.
For the record, I get a similar error when try to run the latest version of XnView Appimage.
I’ve tried to uninstall and reinstall the AppImageLauncher software, no difference.
2 minutes ago, psommerfeld said:I am running Debian under ChromeOS
I'm sorry, this is where tries-to-be-friendly Assistant Moderator Slashee has to bring in the company line (not that I work for the company):
Cura is not supported on Chromebooks. Their Linux environment is quite different to a normal Linux install and many Chromebooks do not meet the system requirements required to run Cura.
And now the second one:
UltiMaker does not support Cura on Linux in any format other than the official AppImage downloads. They do not create the flatpaks, Snaps or binary versions in some distributions' repos and therefore have no control in whether they will work or how safe they are to use.
Now, the part where I can offer unofficial advice: Mint is based on Ubuntu which is based on Debian, however there are many changes along the way so there is no guarantee of compatibility between the two.
1 minute ago, 81anKarlsson said:I’ve tried to uninstall and reinstall the AppImageLauncher software, no difference.
Advice which might not need to be unofficial because it applies to Linux in general: you don't need software to launch AppImages. You just need to change their permissions to add the execute permission.
1
Official or not, I tried the flatpak now and it works. I got 5.7.2 installed and running.
But I rather have the official release.
1
2 hours ago, Slashee_the_Cow said:Advice which might not need to be unofficial because it applies to Linux in general: you don't need software to launch AppImages. You just need to change their permissions to add the execute permission.
That is true, I had forgot about that 🙂
But unfortunately it doesn't run whether I run it with the launcher or directly.
3 hours ago, 81anKarlsson said:Official or not, I tried the flatpak now and it works. I got 5.7.2 installed and running.
But I rather have the official release.
That's good news!
Maybe there's hope I'll get 5.7.x working on my ChromeOS Debian. Anyways 5.6 is good enough for what I need for now.
I am using Fedora, now Fedora 40, running updates when starting it.
Starting an AppImage was no problem in the past, using Cura 5.8.0 around 3 weeks ago for the last time.
But from then on, something has changed:
UltiMaker-Cura-5.3.1-linux-modern can still be started, but all following from UltiMaker-Cura-5.4.0-linux-modern to UltiMaker-Cura-5.8.1-linux-X64 show the same error:
Could not probe OpenGL. This program requires OpenGL 2.0 or higher. Please check your video card drivers.
Starting in a terminal,
qt.qpa.wayland: EGL not available
is shown.
It happens with a Nvidia card
glxinfo | grep OpenGL OpenGL vendor string: Mesa OpenGL renderer string: NV137 OpenGL core profile version string: 4.3 (Core Profile) Mesa 24.1.7 OpenGL core profile shading language version string: 4.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.3 (Compatibility Profile) Mesa 24.1.7 OpenGL shading language version string: 4.30 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.7 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:
as well on a PC with AMD Radeon.
I have installed 5.8.1 from Flathub on the Nvidia card PC and this works .
Problem is that all profiles and materials created with the AppImages are not available.
Do the AppImages and the Flathub have a different file structure / tree ?
I haven't seen how to copy the 5.8.0 AppImage files to the Flathub installation to continue with the same parameters as before.
I prefer to continue using AppImages.
Is there a workaround to get them running again?
5 minutes ago, stoccarda said:Do the AppImages and the Flathub have a different file structure / tree ?
I don't know (I'm only familiar with the AppImage and part of the "Assistant Moderator" job description is "tell people only the official AppImage is supported") but I know that stores its configuration files in ~\.config\cura and ~\.share\cura so maybe you could run the Flatpak and see what file system activity it produces (since it should at least create a log file).
The Flatpak reports a configuration folder /home/user_name/.var/app/com.ultimaker.cura/config/cura/5.8
I tried to copy the files in /home/user_name/.local/share/cura/5.8 to the above, but that didn't work.
Example:
/home/user_name/.local/share/cura/5.8/materials -> /home/user_name/.var/app/com.ultimaker.cura/config/cura/5.8/materials
Unfortunately while Friendly Assistant Moderator Slashee says "support is only offered for the official AppImage", regular Slashee also has to say that I've never used anything but the AppImage so I'm not sure I can be much help. I can suggest "make sure you're not running the Flatpak as root" because if you are then a) you probably shouldn't and b) if you are it might be saving the config files under /root instead of your user folder.
The UltiMaker-Cura-5.9.0-beta.1-linux-X64 AppImage starts on Fedora 40 😀
Nothing printed yet, just opened project files.
Vishnu posted a topic in Official news,
.png.91a5da8b642e6900392a0f7ee0c018ec.png)
ArunC posted a topic in UltiMaker Cura,
Recommended Posts
Slashee_the_Cow 619
It's not a Mint 20.3 thing, that much I can probably say (I downloaded a fresh copy of 20.3, installed it in a VM and it runs the 5.8 beta fine), even though it is getting a bit long in the tooth (was released two and a half years ago and it's based on a four year old LTS version of Ubuntu).
Open ~/.config/cura (that's the .config folder inside your home directory, if you're using the fila manager you might need to turn on hidden files and folders) and see if any of the newer versions created their own config folders. If they did, open the newest one and if it created a cura.log file, post that (and please attach it to the post and not just paste the contents into one massive post like some people do). In the cura folder itself (not any of the versions), if there STDOUT.log or STDERR.log files, post them too.
Also check ~/.local/share/cura for those files. I have no idea why it uses both directories.
It's possible that it had some trouble when trying to migrate your settings from 5.4. To test, make sure Cura is closed, then rename both of those folders to cura.old or something and run a new version again, which will make it generate a new, clean configuration folder. If it runs, you'll have to set it up from scratch, but at least we know the problem lies somewhere in the configuration files. You can always copy over your quality profiles and such from the older directory (generally easier than trying to troubleshoot which config files are causing the problem).
If it doesn't run after renaming the folders... then hope there's something in the log files we can pin down 🙂
Link to post
Share on other sites