Open jakimfett opened 4 years ago
Same here with Fedora 31 xfce x64. Installed from unzipped .deb. Same errors.
I'll go ahead and try to compile on my system once I finish repairing my printer's hotend connector, but I'd really much rather use the official pre-packaged version.
(...how do I get the latest build from https://travis-ci.org/MatterHackers/MatterControl ? )
Is there some specific version of Mono that needs to be installed?
Just by scanning the logfile, it looks like MatterControl is looking for "Microsoft.VisualBasic", which on 'Nix is going to be the mono
package, right?
I've got version 6.6.0.161 installed, and I'm using the .deb
file downloaded from the MatterHackers store page.
jakimfett@obsidian:~/Downloads$ which mono
/usr/bin/mono
jakimfett@obsidian:~/Downloads$ mono --version
Mono JIT compiler version 6.6.0.161 (tarball Tue Dec 10 10:36:32 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: hybrid
GC: sgen (concurrent by default)
exact same issue here on Xubuntu 19.10, downloaded .deb file from main site and have the following version of mono Mono JIT compiler version 6.6.0.161 (tarball Tue Dec 10 10:36:32 UTC 2019)
Same problem on Ubuntu 19.10 with .deb downloaded from MatterHackers site.
Can one of you try the instructions at the bottom of this page (the fix for low end GPUs) and see if that helps?
I tried it but it resulted in the same stackdump
edit: GTX 1070 on 440.44 Nvidia proprietary drivers
I do notice a graphics hiccup (momentary choppy responsiveness) between when the program is executed and the (moments later) crashdump, @unlimitedbacon.
That said, I'm running a reasonably powerful graphics card (the GTX 970 FTW+ at almost five years old is nearly still more than 10x what Passmark considers "low mid range") with the v390.116 Nvidia proprietary driver for Linux-x86_64.
After re-installing with a freshly-downloaded .deb
and setting FSAASamples
to zero, the hiccup and crashdump are still generated when running the mattercontrol
command, run duration approximately three seconds, total.
(edit(s) for clarity & conciseness, thanks @h54 for reminding me to add driver version numbers)
Nvidia RTX 2060 founders edition, 440.44 Nvidia proprietary drivers. Coult it be that the convergent fault condition would be the nvidia proprietary drivers themselves, rather than the card ?
@didli yes it would be interesting to see if anyone on AMD or Intel graphics is having this issue.
I installed 2.0 with only Intel Integrated graphics and it starts. Initially, it's just a blank window but when I maximize it, I see and accept the license agreement. After that, all is normal.
Fedora 31 UHD Graphics 620
So, almost definitely an Nvidia upstream issue then, @h54 ?
@jakimfett I can't say definitively but I tried on two different systems with different Nvidia drivers (440.48.02 & 430.64) and the results are the same. I don't have an AMD card to test with, unfortunately.
@h54 said: I can't say definitively but I tried on two different systems with different Nvidia drivers (440.48.02 & 430.64) and the results are the same. I don't have an AMD card to test with, unfortunately.
But we do know that Intel Integrated works.
And those aren't from Nvidia, unless we're sorely mistaken.
I tested this morning with an AMD card and it started up without issue.
Pop_OS, kernel 5.3.0 RX-590
I've got the same issue, archlinux w/nvidia GT530 - I know, an old card but as other software works (PrusaSlicer) I guess it should not matter...
I get this problem with an NVIDIA 1080TI on archlinux
I'm getting the exact same error in the console log with Mint 18.3 running an Nvidia GeForce GTX 1060 6GB.
I am also getting this error running an AMD Radeon RX 570 card with the "amdgpu" open source driver on Arch Linux.
You can edit /usr/lib/mattercontrol/appsettings.json to override this bug. Application crashes while 'Color' and 'Depth' parameters has different values. I set this values to '24', and program works fine.
Unbelievable, it works. Thank you CAHbKA-IV.
I can vouch for this fix as well. Set 'Color' and 'Depth' to 24. Program works fine.
Worked for me too! MatterControl wouldn't open for me on Zorin OS (Ubuntu based), but I got it working thanks to your advice by editing: /usr/lib/mattercontrol/appsettings.json And changing the color from 32 to 24 :+1: thank you so much.
I contacted MatterHackers requesting that this user fix or work-around to the issue could be posted under the Know Issues section of their documentation at https://matterhackers.github.io/MatterControl-Help/docs/linux
However I was directed to this GitHub, its unfortunate because this issue has been on-going for 2 years now and there are four independent issues lists on GitHub linked to to this issue, it seems like an issue that could potentially be fixed quite easily or at the very least the documentation updated so that users can help themselves to get up and running if the Linux software isn't going to be patched.
I'm glad my answer helped you. If I wasn't job hunting I'd fix it myself but I can't seem to get the MC C# code to compile on my Linux machine and I don't know enough about that environment to know why it won't work. This is a low priority right now for me. The fix should be quite simple I would think. Maybe somebody can make a binary without the bug and post it. - Greg
On Mon, Nov 15, 2021 at 10:56 AM Ashley Cawley @.***> wrote:
I contacted MatterHackers requesting that this user fix or work-around to the issue could be posted under the Know Issues section of their documentation at https://matterhackers.github.io/MatterControl-Help/docs/linux
However I was directed to this GitHub, its unfortunate because this issue has been on-going for 2 years now and there are four independent issues lists on GitHub linked to to this issue, it seems like an issue that could potentially be fixed quite easily or at the very least the documentation updated so that users can help themselves to get up and running if the Linux software isn't going to be patched.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MatterHackers/MatterControl/issues/4682#issuecomment-969216835, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB62E6PFVUV6S2XMXNWE45LUMFJU3ANCNFSM4JSM4FXA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Bug Report
Steps to Reproduce
Expected Behavior Program v2.x and above loads and I can configure my 3d printer.
Actual Behavior Program installed from v2.x debfile crashes without displaying MatterControl window.
MatterControl Build Number Installed via
dpkg -i ./MatterControlSetup-2.19.10.10370.deb
, so assuming it's10370
?Operating System Version Elementary OS 5.0 Juno
Printer Make/Model Robo3D R1+.
Console Log