Author Topic: xLights 2018.2 and Ubuntu 17.10 not running  (Read 585 times)

Offline pbudden

  • Newbie
  • *
  • Posts: 6
    • View Profile
xLights 2018.2 and Ubuntu 17.10 not running
« on: January 16, 2018, 03:30:15 PM »
Hi,

I have been running xLights for a little while now.
Since I am running Ubuntu, I installed with a PPA from Chris Debenham.

The has done some updates with no issues, usually a day after it is released on here.
Most recently. with 2018.2, I have not been able to launch xLights.
I didn't run 2018.1 so I don't know if that has an issue.

I am getting a segfault when run:
Jan 16 22:21:51 pb-Studio-XPS-1640 kernel: [110662.940432] xLights[29685]: segfault at 0 ip 0000562ed8fad55e sp 00007fff11fe8ce0 error 4 in xLights[562ed7e2f000+2055000]
Jan 16 22:21:51 pb-Studio-XPS-1640 kernel: [110663.257678] xLights[29689]: segfault at 0 ip 000055b71580455e sp 00007ffc852ddbd0 error 4 in xLights[55b714686000+2055000]

I have attempted various user things including restarting my machine and launching as root from the command line, no change.

Can anyone suggest if the issue is something local or something in the code?

Thanks

Paul.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xLights 2018.2 and Ubuntu 17.10 not running
« Reply #1 on: January 16, 2018, 04:43:33 PM »
I think I've seen it reported in 3 places so unless all 3 are you it's probably a real issue.  We usually wait for Chris to help with Linux.

Offline pbudden

  • Newbie
  • *
  • Posts: 6
    • View Profile
Re: xLights 2018.2 and Ubuntu 17.10 not running
« Reply #2 on: January 17, 2018, 12:25:54 AM »
Thank you for the update Gilrock.  I scanned for my configuration in the forums but didn't see any direct matches.
I'll wait for 2018.3 and work in windoze in the mean time.  :D

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xLights 2018.2 and Ubuntu 17.10 not running
« Reply #3 on: January 17, 2018, 07:39:43 AM »
I don't mind you reporting it I was just saying I think I've heard about the issue submitted on GitHub, your post here, and on Facebook so I wasn't sure if all 3 of those reports were from you.  I didn't pay attention to the names.