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

Octodash segfaults after 'sudo apt full-upgrade' #1134

Closed
Aulos opened this issue Oct 26, 2020 · 9 comments
Closed

Octodash segfaults after 'sudo apt full-upgrade' #1134

Aulos opened this issue Oct 26, 2020 · 9 comments
Assignees
Labels
support Something isn't working with the users setup

Comments

@Aulos
Copy link

Aulos commented Oct 26, 2020

Describe the bug
After I upgraded octopi through ssh octodash stopped showing up. When I tried to execute it manually I get a segmentation fault. I was trying to update octodash manually (I had 2.1.0), but after update to 2.1.1 it is still failing.

Upgraded packages:

  • libraspberrypi-bin
  • libraspberrypi-dev
  • libraspberrypi-doc
  • freetype2-doc
  • raspberrypi-kernel
  • raspberrypi-bootloader
  • libfreetype6-dev
  • libraspberrypi0
  • libfreetype6

To Reproduce
Steps to reproduce the behavior:

  1. SSH to octopi
  2. call sudo apt update
  3. call sudo apt full-upgrade
  4. restart rpi

Expected behavior
Everything works as before - octodash is

Screenshots
Updated packages - I think it happended after my upgrade on 2020-10-23, but it could have happended after upgrade on 21st
image

image

General Information:

  • Hardware: Rpi 4 2GB with Hyperpixel4 screen
  • OS Info: OctoPi 0.17.0
  • OctoDash Version v2.1.1
  • OctoPrint Version 1.4.2
@Aulos Aulos added the bug Something isn't working label Oct 26, 2020
@UnchartedBull
Copy link
Owner

have you started a window manager before executing octodash?

@Aulos
Copy link
Author

Aulos commented Oct 26, 2020

It doesn't start :/

When I start X server manually then I got this:

~> octodash
No protocol specified
fish: “octodash” terminated by signal SIGSEGV (Address boundary error)

@UnchartedBull
Copy link
Owner

Could you please double check your ~/.xinitrc? The segmentation fault while starting octodash from the command line is normal behavior currently.

If you want to start it manually you have to use startx. My best guess here is that your full-upgrade somehow wiped the ~/.xinitrc.

@Aulos
Copy link
Author

Aulos commented Oct 29, 2020

It looks pretty normal:

#!/bin/sh

xset s off
xset s noblank
xset -dpms

ratpoison&
octodash

@Aulos
Copy link
Author

Aulos commented Oct 29, 2020

Ok, when I connected keyboard to pi4 and ran startx in console octodash started - mouse cursor is visible, but other than that it work as expected.

Any idea how I can make sure X server starts after every boot? I've tried to set login to desktop in raspi-config, but it doesn't seem to help.

@UnchartedBull
Copy link
Owner

Follow these steps and check if everything is right: https://github.com/UnchartedBull/OctoDash/wiki/Installation#start-octodash-automatic-on-boot

@UnchartedBull UnchartedBull added support Something isn't working with the users setup and removed bug Something isn't working labels Oct 29, 2020
@UnchartedBull
Copy link
Owner

Oh but since you use fish you may have to check whether it's using a different file.

@Aulos
Copy link
Author

Aulos commented Oct 29, 2020

Yup, I changed default the default shell and X is not starting - when I added it to config.fish X starts as it should

@Aulos Aulos closed this as completed Oct 29, 2020
@Aulos
Copy link
Author

Aulos commented Oct 29, 2020

For interested, this is what I've added to $HOME/.config/fish/config.fish:

if test -z "$SSH_CLIENT" -o -z "$SSH_TTY"
  xinit -- -nocursor
end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Something isn't working with the users setup
Projects
None yet
Development

No branches or pull requests

2 participants