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

Crash when trying to load brackground on RPI #188

Closed
peanutyost opened this issue Apr 27, 2018 · 4 comments
Closed

Crash when trying to load brackground on RPI #188

peanutyost opened this issue Apr 27, 2018 · 4 comments
Labels

Comments

@peanutyost
Copy link

Expected Behavior

load the background profile

Actual Behavior

crashed program on click the load button

Steps to Reproduce the Problem

1.open artisan
2.open the brackground window
3.click the load button

Specifications

  • Artisan Version:1.3.0
  • Artisan Build (number in brackets shown in the about box):?
  • Platform (Mac/Windows/Linux + OS version):linux stretch
  • Connected devices or roasting machine:serial

Please attach your current Artisan settings file (as exported via menu Help >> Save Setings as *.aset) file.
Please attach any relevant Artisan *.alog profiles.

@MAKOMO MAKOMO added the RPi label May 7, 2018
@samtsai5212
Copy link

Try run sudo artisan.

@MAKOMO
Copy link
Member

MAKOMO commented May 8, 2018

I cannot reproduce this on a RPi3 Model B. Which hardware and exact OS you are running on here? Could you please run the following two commands and post the results here?

# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
# cat /proc/cpuinfo | grep 'Revision' | awk '{print $3}' | sed 's/^1000//'
a22082

@MAKOMO
Copy link
Member

MAKOMO commented May 9, 2018

Running via sudo is a valid workaround for this crash for now. We are working on a fix for future releases...

@MAKOMO
Copy link
Member

MAKOMO commented May 13, 2018

I close this one as it seems to have the same cause then Issue #187

@MAKOMO MAKOMO closed this as completed May 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants