1.1.4 not working in linux

[shawneehbc]

Hello, after updating to 1.1.4 the program no longer loads. I have tried it on two different computers, and its the same story. We are using SNAP to install and keep Freeshow up to date.

[vassbo]

Do you get any errors in the console?

[shawneehbc]

I'm not sure how to do that? If you give me instructions I will try. I executed Freeshow through the GUI when I went to snap/freeshow/current/freeshow and it loaded fine. When I tried to go to the "current" directory though the terminal there were no files visible in that directory. Sorry I am still new to Linux Thanks and God bless, James Horsley Sent with [Proton Mail](https://proton.me/) secure email.

…

On Saturday, March 2nd, 2024 at 2:21 AM, Kristoffer Vassbø ***@***.***> wrote: Do you get any errors in the console? — Reply to this email directly, [view it on GitHub](#424 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BGTFQ46AOZKBG7XNL4V6SR3YWF4ZDAVCNFSM6AAAAABECSAFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUGYZTCOBVGY). You are receiving this because you authored the thread.Message ID: ***@***.***>

[shawneehbc]

So, i forgot to state the program wont load when I click on the GUI's purple Freeshow icon. For whatever its worth I am running Ubuntu 22.04 LTS on all of the computer I am trying it on. Sent with [Proton Mail](https://proton.me/) secure email.

…

On Saturday, March 2nd, 2024 at 7:32 AM, Jay Horsley ***@***.***> wrote: I'm not sure how to do that? If you give me instructions I will try. I executed Freeshow through the GUI when I went to snap/freeshow/current/freeshow and it loaded fine. When I tried to go to the "current" directory though the terminal there were no files visible in that directory. Sorry I am still new to Linux Thanks and God bless, James Horsley Sent with [Proton Mail](https://proton.me/) secure email. On Saturday, March 2nd, 2024 at 2:21 AM, Kristoffer Vassbø ***@***.***> wrote: > Do you get any errors in the console? > > — > Reply to this email directly, [view it on GitHub](#424 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BGTFQ46AOZKBG7XNL4V6SR3YWF4ZDAVCNFSM6AAAAABECSAFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUGYZTCOBVGY). > You are receiving this because you authored the thread.Message ID: ***@***.***>

[vassbo]

Okay, thanks. Please see this: https://www.wikihow.com/Run-a-Program-from-the-Command-Line-on-Linux

I will check it out myself, I know it works for some people on Linux.

[shawneehbc]

Here is what it says in terminal ***@***.***:~/snap/freeshow/current$ freeshow mkdir: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/freeshow/35/gnome-platform/lib/x86_64-linux-gnu/libselinux.so.1)mkdir: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/freeshow/35/gnome-platform/lib/x86_64-linux-gnu/libselinux.so.1) But when I go thorugh the GUI the current directory isn't empty and it executes fine when I double click on the freeshow program. Sent with [Proton Mail](https://proton.me/) secure email.

…

On Saturday, March 2nd, 2024 at 8:22 AM, Kristoffer Vassbø ***@***.***> wrote: Okay, thanks. Please see this: https://www.wikihow.com/Run-a-Program-from-the-Command-Line-on-Linux I will check it out myself, I know it works for some people on Linux. — Reply to this email directly, [view it on GitHub](#424 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BGTFQ42YLP5RAXD6KLM5MXTYWHHCTAVCNFSM6AAAAABECSAFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUG44TMMJQGI). You are receiving this because you authored the thread.Message ID: ***@***.***>

[vassbo]

Thanks! 🤔

[eeickmeyer]

I have fixed the snap. Turns out the patch I was using to update electon-builder to a newer supported core and gnome dependency was broken. That's fixed now, and a new version of the snap has been uploaded.

[vassbo]

Fixed now! Thanks to @eeickmeyer.
#425

[shawneehbc]

Thanks to all of you, and may God bless your ministry! Sent with [Proton Mail](https://proton.me/) secure email.

…

On Saturday, March 2nd, 2024 at 4:22 PM, Kristoffer Vassbø ***@***.***> wrote: Fixed now! Thanks to ***@***.***(https://github.com/eeickmeyer). [#425](#425) — Reply to this email directly, [view it on GitHub](#424 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BGTFQ447K76RFGRDSPE2EJDYWI7KJAVCNFSM6AAAAABECSAFXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUHEYTEOBQGE). You are receiving this because you authored the thread.Message ID: ***@***.***>