Linux Appimage 5.1.6 not working un ubuntu #231
Comments
|
Same experience for me. Ubuntu 24.04 |
|
Downgraded from openssl 3.0.13 to 1.1.1. App loaded, asked to select language but now crashes at open with
Checking ssl and downgrading - this seems to work for some users that may have AMD or integrated graphics. Nvidia users may skip to the next comment and use the default openssl 3.0.13. App entry: Change the icon here, then find it in the menu search to make a desktop shortcut. |
|
Running on 24.04, x11, and nvidia gpu with the default openssl 3.0.13 and the following flag: Make creality.sh to avoid having to always run with the flag. Or do this and make a desktop shortcut/app entry Change the icon here, then find it in the menu search to make a desktop shortcut. |
|
These are the testing commands I tried in case it helps some one with a different unix build or if you still have issues you may be missing just a few of these installs.
|
|
UGH. That was a waste of many hours. Chasing THAT old ubuntu libssl1.1 down and trying to hammer it into place. For others, I wouldn't even bother, lets wait until the devs fix their library not to rely on ancient libraries and simply update it to 3+. edit - BTW, here is how to dump the errors out into a text file so one can see WTH is going on.... |
|
I tried to install this in a fresh 24.04 VM in order to document the process but there are additional issues that arise when trying to run in a virtual space. Here is the screenshot from my desktop build. |
Same issue here, trying to run it inside a Fedora Distrobox container. This should really be packaged with a proper Flatpak rather than this AppImage mess... |
|
Until they fix it, you can do And run the appimage file |
|
BINGO @ygandahvn |
For those having this also on Arch Linux, this solution works. |
This worked for me on Ubuntu 24.04 |
|
Looks like someone at Creality re-compiled this version. I downloaded it again (it says from 3 days ago) and it works now on my system that still has openssl 3. |
Huh. You're right. That's very strange. It has the exact same filename, but the checksum is different — it was just silently swapped out? I can confirm that this new version of the same version works in my Fedora Distrobox now. This will do for now — still hoping for a Flatpak though! |
|
Still crashing for me on launch using Linux Mint 21.3. Now my printer, Sermoon V1 Pro, still isn't supported in v5 but would be nice to upgrade from 4.3.6.6257. |
|
@Goodolandy I had the same problem when using the Nvidia drivers. Use the "Driver Manager" tool and change to Nouveau. One can see the actual crash and the error it creates if you use the Terminal to start the app... i.e I tried many things, including an extensive debugging to solve it under nvidia, but proved unable to. Changing the driver worked. (edit - Using Mint 22, fully updated. No weird setups, all very generic) |
|
@AtomicRobotMan0101 Thank you. I never thought the problem would be a graphics driver. I saw that I was still on nvidia-driver-535. Updated to 550 and now Creality Print v5 is loading. I hope they start adding more printers soon. |
|
I found that the current version of Creality Print for Linux doesn't like something about Wayland with Nvidia drivers. I could run it in Wayland with the default video drivers, but once it was sliced, I couldn't rotate or move around the model as it was really lagging. I installed the Nvidia drivers and then Creality Print would crash on startup. I changed back to X11 and Creality loads fine with the Nvidia drivers. I am running most recent KDE Neon User Edition with Nvidia GTX 1080Ti. |
|
tested on kde neon (based on ubuntu 24.04) and new uploaded version works |
|
Same issue here, but I am on ARCH. Tried almost all of the above no go. I went back 4.3, it runs flawlessly for now. |
This also works in linux mint 22 cinnamon |
|
Thank you, I saw this on another post. Does not seem to fix anything here unfortnately. For the life me, I can't figure this out. 4.3 works great. But I am on ARCH not ubuntu as well. Output: Exec=env __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./Creality_Print-v5.1.6.10470-x86_64-Release_73540cdc021c8c1465f106722cd6f499.appimage parse binary stl success... Computing bounding box... Done. |
|
Seems top be an issue on Wayland, if I log into an ancient X11 session it works. Which is doable, but not preferred, this is the only app that I have that won't run in Wayland I guess. Orca works fine as of 2.2. I live in Wayland and Hyprland. Currenttly I just 4.3, as it works for now. |
Worked well in Xubuntu 22.04 and NVidia 550 drivers |
|
Anyone have it working in Wayland? Like 4.3 does? |
|
Works just fine for me on Wayland in a Fedora Distrobox. I see a lot of people talking about Nvidia, so that's probably the issue — it's well-known that Nvidia doesn't have great Wayland support. I'm using an AMD card. |
|
Ahh that could be, 4.3 works great. My guess is that it's missing a library
or something. 4.3 works in wayland fine.
Thanks for the response. Bambu works fine in wayland and Orca. I can stay
in those two, there just some times I want creality print.
…On Thu, Nov 28, 2024 at 3:02 AM JaneSmith ***@***.***> wrote:
Works just fine for me on Wayland in a Fedora Distrobox. I see a lot of
people talking about Nvidia, so that's probably the issue — it's well-known
that Nvidia doesn't have great Wayland support. I'm using an AMD card.
—
Reply to this email directly, view it on GitHub
<#231 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2GVSJXR5FKXIELTYQ4POH32C3E3FAVCNFSM6AAAAABRODULRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGQ3TSMJYGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Brett Silverthorn
|
|
I would be up for using the Orca slicer, but it doesn't have the Sermoon v1 Pro printer profile. I tried the standard v1 profile, and my printer went crazy, so I had to stop the printing immediately before any damage was done. Hopefully, a proper v1 Pro profile will be added to Creality Print v5 or Orca. |
|
Mint 22 ca
Changing the nvidia driver helped me |
|
DOWNGRADING YOUR OPENSSL VERSION FROM 3.x to 1.1 IS REALLY A BAD SECURITY IDEA. GUYS, DON'T DO THAT, YOU'RE MAKING YOUR SYSTEM SUBSTANTIALLY LESS SECURE. |
Rest assured that the Ubuntu security team will continue to maintain important security fixes in OpenSSL 1.1.1 for as long as the Ubuntu release is supported, meaning 2025 for Ubuntu 20.04 LTS with standard support. For Ubuntu Pro subscribers, Canonical offers Expanded Security Maintenance (ESM). This means getting at least 10 years of security maintenance for all software bundled in the release, including OpenSSL 1.1.1. This translates to being security maintained and supported until at least 2028 for Ubuntu 18.04 LTS and at least 2030 for Ubuntu 20.04 LTS. Make sure to activate your free one per household UBUNTU PRO MEMBERSHIP which isn't necessary but might not know it's there for free. |
This is good information. Also, with the updated appimage (make sure to download again to get the latest) it was recompiled and no longer needs openssl 1.1. It works great with the latest openssl with no downgrade necessary. |
|
The problem with the interaction of the NVideo Geforce 1650 video card in the latest release 3DCreality_Print-v5.1.7.10514-x86_64-Release.AppImage for MintLinux has not been resolved. The problem is that the program opens and closes immediately, and if you roll back the drivers on Linux, the program works. |
|
I was so happy to get Creality Print 5.1.6 to work on my Linux Mint 21.3 Cinnamon computer using the command line entry posted by @BB31420 (thank you!), but unfortunately it does not work on 5.1.7. The splash screen comes up and hangs for a little while and then disappears. Here is the output I get in the terminal:
I went back and tried it with Creality Print 5.1.6 just to make sure it still works, but it too crashes in much the same way now. It was working just fine for me last Tuesday, so the only thing I can think of is that a recent kernel update or an NVIDIA driver update broke the solution that @BB31420 figured out. For what its worth, here is my current kernel and NVIDIA info:
|
|
Try replacing nvidia with amd in the command line. It’s broke here too now, can’t either version to work. Only 4.3 now. Sent from my iPhoneOn Dec 22, 2024, at 3:43 PM, JimB2020 ***@***.***> wrote:
I was so happy to get Creality Print 5.1.6 to work on my Linux Mint 21.3 Cinnamon computer using the command line entry posted by BB31420 (thank you!), but unfortunately it does not work on 5.1.7. The splash screen comes up and hangs for a little while and then disappears. Here is the output I get in the terminal:
_NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./Creality_Print-v5.1.7.10514-x86_64-Release.AppImage
Initializing StaticPrintConfigsCXBinManager open file size [377984]
parse binary stl ...face 7558
parse binary stl success...
Computing bounding box... Done.
x = -3.4333 .. 3.4334, y = -3.0001 .. 3.0002, z = -0.0046 .. 13.7387
Computing bounding box... Done.
x = -57.2188 .. 57.2205, y = -49.9992 .. 50.0008, z = -0.0766628 .. 228.967
Computing bounding box... Done.
x = -3.4333 .. 3.4334, y = -3.0001 .. 3.0002, z = -0.0046 .. 13.7387
Computing bounding box... Done.
x = -3.4333 .. 3.4334, y = -3.0001 .. 3.0002, z = -0.0046 .. 13.7387
XIO: fatal IO error 2 (No such file or directory) on X server ":0"
after 747 requests (747 known processed) with 0 events remaining.
Segmentation fault (core dumped)
I went back and tried it with Creality Print 5.1.6 just to make sure it still works, but it too crashes in much the same way now. It was working just fine for me last Tuesday, so the only thing I can think of is that a recent kernel update or an NVIDIA driver update broke the solution that BB31420 figured out. For what its worth, here is my current kernel and NVIDIA info:
Linux kernel: 5.15.0-69-generic
NVIDIA Corporation GK208B [GeForce GT 730]
NVIDIA Driver Version: 470.256.02
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
@JimB2020 - happy holidays - @AtomicRobotMan0101 suggested using Any chance you had tried to set a temp environment variable for downgrading openssl and it has reset upon a new session? It sounds like you only needed the nvidia flag before tho but just throwing this out there. Initially downgrading openssl allowed me to move forward in the debugging process to find the other flag. Let me know more about this error if you can capture verbose output. It sounds like your error is regarding the x11 server, perhaps it's not finding the primary monitor. try: Cheers |
|
@BB31420 - happy holidays!
Holy smokes! The strace error.txt file is huge - 3.2MB! I tried looking through some of it, but in addition to it being such a massive amount of data, I'm not sure what I'm looking for... I tried most of the items on your testing commands list skipping things that were not in my current repositories (such as nvidia-opengl-dev), and a few things that I was afraid might break something. I found that have OpenSSL 3.0.2, but I also found that I have libssl1.1.1f-1ubuntu2 already installed. I'm not sure how to
but by the time i got down to trying line 1991 on your testing commands list (the original workaround of the nvidia flag) - it worked! Being suspicious of my inexplicable positive results, I rebooted my computer and tried it again. No luck. Same errors.
Primary monitor is correct - checking it both from the command line and the NVIDIA X SERVER SETTINGS on the Administration menu. Thanks for your help |
|
@JimB2020 you are not wrong about the output, its a bit much. The fix turns out to be easier than what I suggested.... took a while to work out!
The CrealityPrint will now work. |
|
This was a no go for me ;-(. Darn it! Just starts and immediately exists.
What is the variable to alter to make it think you're not on the latest SSL?
…On Thu, Dec 26, 2024 at 6:58 AM Evan McBeth ***@***.***> wrote:
@JimB2020 <https://github.com/JimB2020> you are not wrong about the
output, its a bit much.
The fix turns out to be easier than what I suggested.... took a while to
work out!
- edit the /etc/environment file
- sudo nano /etc/environment
- add this: WEBKIT_DISABLE_DMABUF_RENDERER=1
- save the file
- log out of your session (or reboot)
The CrealityPrint will now work.
—
Reply to this email directly, view it on GitHub
<#231 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2GVSJXQ5FDEACKKKMB23YT2HPVMRAVCNFSM6AAAAABRODULRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSGU3DGNRYG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Brett Silverthorn
|
@AtomicRobotMan0101's the solution of editing the
I've rebooted twice just to be sure this always works, and yes it does! |
Thanks mate! Works like a charm! |
|
Awesome fix for Ubuntu. Still no go on arch. Sent from my iPhoneOn Dec 27, 2024, at 10:32 PM, Denis Koleda ***@***.***> wrote:
Running on 24.04, x11, and nvidia gpu with the default openssl 3.0.13 and the following flag:
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./Creality_Print-v5.1.6.10470-x86_64-Release.AppImage
Make creality.sh to avoid having to always run with the flag.
#!/bin/bash
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./Creality_Print-v5.1.6.10470-x86_64-Release.AppImage
chmod +x creality.sh
Or do this and make a desktop shortcut/app entry
echo '[Desktop Entry]
Name=Creality Print
Comment=Creality 3D Slicer
Exec=env __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia '"$HOME/Downloads/Creality_Print-v5.1.6.10470-x86_64-Release.AppImage"'
Icon=creality
Terminal=false
Type=Application
Categories=Graphics;3DGraphics;Engineering;' > ~/.local/share/applications/creality-slicer.desktop
Change the icon here, then find it in the menu search to make a desktop shortcut.
cd ~/.local/share/applications/
This also works in linux mint 22 cinnamon
Worked well in Xubuntu 22.04 and NVidia 550 drivers
Thanks mate! Works like a charm!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
You're running Wayland on Arch with an AMD gpu and is it external or integrated or part of the CPU? I will try to fix this for you, let me know more about your build |
|
I’m running Wayland, on Arch, with Nvidia GPU, core i9 intel cpu. Some have reported changing the nvidia to amd worked for them. The are a few of us on the creality discord channel all experiencing the same thing. It’s hard to tell if it’s a Wayland thing or Nvidia thing. Sent from my iPhoneOn Dec 29, 2024, at 10:14 PM, BB31420 ***@***.***> wrote:
Awesome fix Ubuntu. Still no go on arch. Sent from my iPhoneOn Dec 27, 2024, at 10:32 PM, Denis Koleda @.> wrote: Running on 24.04, x11, and nvidia gpu with the default openssl 3.0.13 and the following flag: __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./Creality_Print-v5.1.6.10470-x86_64-Release.AppImage Make creality.sh to avoid having to always run with the flag. #!/bin/bash __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./Creality_Print-v5.1.6.10470-x86_64-Release.AppImage chmod +x creality.sh Or do this and make a desktop shortcut/app entry echo '[Desktop Entry] Name=Creality Print Comment=Creality 3D Slicer Exec=env __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia '"$HOME/Downloads/Creality_Print-v5.1.6.10470-x86_64-Release.AppImage"' Icon=creality Terminal=false Type=Application Categories=Graphics;3DGraphics;Engineering;' > ~/.local/share/applications/creality-slicer.desktop Change the icon here, then find it in the menu search to make a desktop shortcut. cd ~/.local/share/applications/ This also works in linux mint 22 cinnamon Worked well in Xubuntu 22.04 and NVidia 550 drivers Thanks mate! Works like a charm! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>
You're running Wayland on Arch with an AMD gpu and is it external or integrated or part of the CPU? I will try to fix this for you, let me know more about your build
happy new year
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
I changed the flag to amd even though i have nVidia 1650 and it started working... at least it works now |
force x11 force x11 with AMD's GLX library The user's where changing to AMD's GLX library worked may have x11 setups. If none of this works, I have a copy of arch to setup and test but might be a few days. |
|
Differnt error now, like no error. It does not even show the screen now: Executes per say, no splash screen, then back to prompt. ╭─brett@I9 in ~/Applications as 🧙 took 0s parse binary stl success... Computing bounding box... Done. ╭─brett@I9 in ~/Applications as 🧙 took 1s parse binary stl success... Computing bounding box... Done. |
|
I just encountered this same error, running Fedora 41 (Well, Nobara 41), and also have a 1650 video card. Running on wayland with a segmentation fault using this command: |
|
Same I tried Nobara as well by recommendation. Love the distro, but same error here too. Sent from my iPhoneOn Jan 26, 2025, at 7:09 PM, Crono141 ***@***.***> wrote:
I just encountered this same error, running Fedora 41 (Well, Nobara 41), and also have a 1650 video card. Running on wayland with a segmentation fault using this command:
GDK_BACKEND=x11 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./creality_print.appimage
Initializing StaticPrintConfigsCXBinManager open file size [377984]
parse binary stl ...face 7558
parse binary stl success...
Computing bounding box... Done.
x = -3.4333 .. 3.4334, y = -3.0001 .. 3.0002, z = -0.0046 .. 13.7387
Computing bounding box... Done.
x = -57.2188 .. 57.2205, y = -49.9992 .. 50.0008, z = -0.0766628 .. 228.967
Computing bounding box... Done.
x = -3.4333 .. 3.4334, y = -3.0001 .. 3.0002, z = -0.0046 .. 13.7387
Computing bounding box... Done.
x = -3.4333 .. 3.4334, y = -3.0001 .. 3.0002, z = -0.0046 .. 13.7387
X connection to :0 broken (explicit kill or server shutdown).
Segmentation fault (core dumped)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Release Creality_Print-v5.1.6.10470-x86_64-Release.AppImage crashes on ubuntu after start.
./Creality_Print-v5.1.6.10470-x86_64-Release.AppImage
QSocketNotifier: Can only be used with threads started with QThread
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
The text was updated successfully, but these errors were encountered: