Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PrusaSlicer2.4.0-alpha1 built and installed on UbuntuMate 21.04 GTK3 CM4 aarch64 crash upon starting initialization #6964

Closed
m3cinc opened this issue Sep 16, 2021 · 1 comment

Comments

@m3cinc
Copy link

m3cinc commented Sep 16, 2021

Version

2.4.0-alpha1
Use About->About PrusaSlicer for release versions

For -dev versions, use git describe --tag or get the hash value for the version you downloaded or git rev-parse HEAD
tar version downloaded from latest release (alpha1)

Operating system type + version

Release 21.04 (Hirsute Hippo) 64-bit on Kernel Linux 5.11.0-1017-raspi aarch64 on CM4,32G eMMC,8G RAM Wifi + CM4-DUAL-ETH-BASE - llvmpipe (LLVM 12.0.0, 128 bits)
In case of 3D rendering issues, please attach the content of menu Help -> System Info dialog

3D printer brand / version + firmware version (if known)

What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s
MK3S/MMU2S

Behavior

  • builds and sudo install GTK3 version without error but crash on start as captured below:

marc@octopicm4:~/PrusaSlicer-version_2.4.0-alpha1/build/src$ ./prusa-slicer
[2021-09-16 11:58:50.261509] [0x0000ffff80f2a010] [trace] Initializing StaticPrintConfigs
No protocol specified
AddressSanitizer:DEADLYSIGNAL

==5331==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000140 (pc 0xaaaae44e87dc bp 0xffffcc016530 sp 0xffffcc016530 T0)
==5331==The signal is caused by a READ memory access.
==5331==Hint: address points to the zero page.
#0 0xaaaae44e87dc in wxAppConsoleBase::GetAppDisplayName() const (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x42e87dc)
#1 0xaaaae43938c4 in wxLogGui::GetTitle() const (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x41938c4)
#2 0xaaaae439401c in wxLogGui::Flush() (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x419401c)
#3 0xaaaae456686c in wxLog::SetActiveTarget(wxLog*) (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x436686c)
#4 0xaaaae45597f0 in wxEntry(int&, wchar_t**) (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x43597f0)
#5 0xaaaae1fce95c in Slic3r::GUI::GUI_Run(Slic3r::GUI::GUI_InitParams&) (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x1dce95c)
#6 0xaaaae078508c in Slic3r::CLI::run(int, char**) (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x58508c)
#7 0xaaaae071bbe4 in main (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x51bbe4)
#8 0xffff81e319d0 in __libc_start_main (/lib/aarch64-linux-gnu/libc.so.6+0x249d0)
#9 0xaaaae0771c34 in _start (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x571c34)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/home/marc/PrusaSlicer-version_2.4.0-alpha1/build/src/prusa-slicer+0x42e87dc) in wxAppConsoleBase::GetAppDisplayName() const
==5331==ABORTING

  • Steps needed to reproduce the problem
  • build and install using Ninja for ubuntu GTK3 as described in doc
    • If this is a command-line slicing issue, include the options used
  • Expected Results
  • Actual Results
    • Screenshots from PrusaSlicer preview are preferred

Is this a new feature request?

Project File (.3MF) where problem occurs

Upload a PrusaSlicer Project File (.3MF) (Plater -> Export plate as 3MF for Slic3r PE 1.41.2 and older, File -> Save / Save Project for PrusaSlicer, Slic3r PE 1.42.0-alpha and newer)
Images (PNG, GIF, JPEG), PDFs or text files could be drag & dropped to the issue directly, while all other files need to be zipped first (.zip, .gz)

@m3cinc
Copy link
Author

m3cinc commented Sep 16, 2021

Determined the issue is related to a permission access. Need to allow sudo or root access to integrate with environment. Setting appriopriate permissions during (alt. after building) resolve the issue.
Closing the report.

@m3cinc m3cinc closed this as completed Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant