CrealityOfficial / CrealityPrint

GNU Affero General Public License v3.0
217 stars 31 forks source link

Creality Print for linux - importance CRITICAL #146

Open carlesoriol opened 6 months ago

carlesoriol commented 6 months ago

Creality print 5 release for linux is not available.

moonglow commented 6 months ago

It works well ( including LAN printing ) under my Ubuntu 22.04 with wine 9.x

BeethovenBravo commented 6 months ago

A linux version is better than wine.

carlesoriol commented 6 months ago

A linux version is better than wine.

Linux version 5 is not available.

carlesoriol commented 6 months ago

It works well ( including LAN printing ) under my Ubuntu 22.04 with wine 9.x

Nice trolling, but that's not linux version.

hagbardZ commented 6 months ago

i kicked this peace of shit away, and installed orca ... this is way better on Linux. Sources are also available. There is no reason to use this crap.

ronoaldo commented 5 months ago

Running the slicer under wine is not ideal but it is not trolling. I'm using wine as well, and for me with K1 Max and local filament brands it is working quite well even without too much calibration needed to get decent prints.

There are also several issues already about Linux support: https://github.com/CrealityOfficial/CrealityPrint/issues?q=is%3Aissue+linux+

Creating more issues will just pollute the tracker... It is wiser to have a single point where we can keep informed instead of having several similar issues.

jaaxx commented 5 months ago

I would like to confirm as of 5.0.3 release this issue is still not resolved. Thanks.

carlesoriol commented 5 months ago

Still no news on linux version?

carlesoriol commented 3 months ago

Still the same problem in version 5.1.1 Any answer from creality?

carlesoriol commented 1 month ago

5.1.2 Issue still in 5.1.2.

UnclePaulus commented 2 weeks ago

I just tried the Creality_Print-v5.1.6.10470-x86_64-Release.appimage on my K1 Max and it crashes almost immediately on my Debian 12 Bookworm platform. Is there a solution to this?

ronoaldo commented 2 weeks ago

I got the same error as @UnclePaulus when starting the 5.6.1 AppImage on Debian 12. Running with gdb, I was able to get the following trace:

Thread 81 "QNetworkAccessM" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffef55fd6c0 (LWP 112313)]
0x00007ffff30b7eca in __GI___libc_free (mem=0xc0) at ./malloc/malloc.c:3362
3362    ./malloc/malloc.c: Arquivo ou diretório inexistente.
(gdb) bt
#0  0x00007ffff30b7eca in __GI___libc_free (mem=0xc0) at ./malloc/malloc.c:3362
#1  0x00007ffff0533352 in SSL_SESSION_free () from /tmp/.mount_creali0wc1yd/lib/libqcxffmpeg.so
#2  0x00007fffebf14297 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#3  0x00007fffebf0f67d in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#4  0x00007fffebee79b9 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#5  0x00007fffebeee5e5 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#6  0x00007fffebef95a3 in SSL_read () from /lib/x86_64-linux-gnu/libssl.so.1.1
#7  0x00007fffecf3c290 in QSslSocketBackendPrivate::transmit() () from /tmp/.mount_creali0wc1yd/lib/libQt5Network.so.5
#8  0x00007fffecf153c1 in QSslSocket::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /tmp/.mount_creali0wc1yd/lib/libQt5Network.so.5
#9  0x00007ffff34d5ddf in void doActivate<false>(QObject*, int, void**) () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#10 0x00007fffecedfaa3 in QAbstractSocketPrivate::emitReadyRead(int) () from /tmp/.mount_creali0wc1yd/lib/libQt5Network.so.5
#11 0x00007fffecedfb54 in QAbstractSocketPrivate::canReadNotification() () from /tmp/.mount_creali0wc1yd/lib/libQt5Network.so.5
#12 0x00007fffecef2061 in QReadNotifier::event(QEvent*) () from /tmp/.mount_creali0wc1yd/lib/libQt5Network.so.5
#13 0x00007ffff3b6343c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_creali0wc1yd/lib/libQt5Widgets.so.5
#14 0x00007ffff3b69f20 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_creali0wc1yd/lib/libQt5Widgets.so.5
#15 0x00007ffff349d808 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#16 0x00007ffff34f9d98 in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#17 0x00007fffef51e17d in g_main_context_dispatch () from /tmp/.mount_creali0wc1yd/lib/libglib-2.0.so.0
#18 0x00007fffef51e400 in ?? () from /tmp/.mount_creali0wc1yd/lib/libglib-2.0.so.0
#19 0x00007fffef51e4a3 in g_main_context_iteration () from /tmp/.mount_creali0wc1yd/lib/libglib-2.0.so.0
#20 0x00007ffff34f91eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#21 0x00007ffff349c21a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#22 0x00007ffff32b2844 in QThread::exec() () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#23 0x00007ffff32b3b35 in QThreadPrivate::start(void*) () from /tmp/.mount_creali0wc1yd/lib/libQt5Core.so.5
#24 0x00007ffff30a81c4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#25 0x00007ffff312885c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Looks like some kind of memory issue with libqcxffmpeg.so/libssl.so. Perhaps something related to the version of SSL on system? Maybe it could be fixed by Creality if they also include the SSL library in the AppImage.

UnclePaulus commented 2 weeks ago

Sometimes the software starts correctly. Most of the times it doesn't. Being an old fool, I have been frantically clicking the right and left mouse-button during start up. And believe it or not... the software started...

UnclePaulus commented 1 week ago

It is a matter of ssl indeed. I found this post and it worked for me. https://github.com/CrealityOfficial/CrealityPrint/issues/231 I didn't have to go further than 'sentence' 1897

ronoaldo commented 1 week ago

It is a matter of ssl indeed. I found this post and it worked for me. #231 I didn't have to go further than 'sentence' 1897

The fix to install the Ubuntu libssl1.1 package worked for me too! In my case, I had a different one, from Debian 11, laying around on my system. However, with the Ubuntu version it worked.

Curiously, based on the 5.0.3 cmake (only source code branch available), these files should be copied over to the .AppImage - not sure how the binaries are built but this seems to be either not working properly or missing from the current released version.