search

the-via / releases

GNU General Public License v3.0
2.04k stars 223 forks source link

Via appimage crashing on Garuda Linux (Arch Based) at Root Prompt #179

Open chaseyrt opened 2 years ago

chaseyrt commented 2 years ago

Works fine on my laptop (Intel XE). Every time i launch the program, I get to the prompt asking me for my root password, and the program immediately crashes as soon as that prompt shows up. I ran it in the console and got this

promppting linux access 390cd24a6ad30bec63967065a5898337 [15910:0417/104859.734031:FATAL:gpu_data_manager_impl_private.cc(986)] The display compositor is frequently crashing. Goodbye. fish: Job 1, './via-1.3.1-linux.AppImage' terminated by signal SIGTRAP (Trace or breakpoint trap)

Im not too sure whats going on, as its a fresh install, electron is updated, and my nvidia drivers are up to date.

chaseyrt commented 2 years ago

A temporary solution is to run thru console as root and with the '--no-sandbox' arg., but thats lazy.

kittycatcaoimhe commented 2 years ago

Same thing is happening on openSUSE Tumbleweed, but it also will not run with the '--no-sandbox' tag. I have only tried with the App Image, not with any other type.

nikspyratos commented 2 years ago

Same on Manjaro via aur appimage build. Wayland thing?

kittycatcaoimhe commented 2 years ago

Same on Manjaro via aur appimage build. Wayland thing?

I've had this issue on both KDE Plasma and XFCE, both of which use XOrg.

linuxgnuru commented 2 years ago

same issue in Pop 22.04. Tried deb package and appimage

ahoneybun commented 2 years ago

So the --no-sandbox does work on Pop 22.04 LTS.

kmanwar89 commented 2 years ago

Can confirm --no-sandbox works for Pop 22.04 as well. The issue was not present in Pop 21.04, so seems to have been introduced at some point between versions.

It seems it was also mentioned on Reddit a year ago and is specifically affecting Electron-based AppImages, though I haven't tested non-Electron based ones myself.

I personally experience this issue with both VIA and Pulse-SMS, both which I believe are Electron-based.

rogersebastiany commented 2 years ago

https://github.com/pop-os/shop/issues/357

sudo apt full-upgrade fixed for me

linuxgnuru commented 2 years ago

Yep, works fine in pop now

kmanwar89 commented 2 years ago

Has any progress been made to have this fixed? I've actually been running Ubuntu 22.04 for some time, as Pop! repeatedly crashed/had issues. The new Ubuntu is almost identical to Pop, minus some of the Pop-specific finishing touches.

The issue is still present, in that some electron apps (such as Pulse SMS, which is what I primarily use) still requires the --no-sandbox in order to launch.

biggestsonicfan commented 2 years ago

Has any progress been made to have this fixed?

Since the last published release of the AppImage is from over two years ago, I'm going to go ahead and say it hasn't. Was considering buying a Q6 but seeing the terrible support it has I think I have made my decision.

kmanwar89 commented 1 year ago

Shame, really. Unfortunately for me, some of my core apps that I need (Joplin, Pulse-sms) are both electron-based, and neither runs on Ubuntu 22.04 w/o using the --no-sandbox flag from the CLI. What's interesting is the issue was not present on 21.04, so makes me think something happened between those versions. What that change is, however, is beyond my skill level to diagnose and troubleshoot.

rogersebastiany commented 1 year ago

@kmanwar89 have u tried the solution I have posted on May 31?

I have attached a url in which u can find the original post where the solution was first mentioned, if you want to take a look.

pop-os/shop#357

sudo apt full-upgrade fixed for me

biggestsonicfan commented 1 year ago

sudo apt full-upgrade can be dangerous in some situations and should never be considered a "fix" to a specific problem, especially if you can't justify why it fixed the issue.

I am also unsure why the AppImage would be preferred over the .deb install if running Ubuntu.

In either case, this repo seems to be depreciated for the app repo, which does the same thing as long as you don't have your own localhost:8080 going on. Though the entire "the-via" github is a disorganized mess of where issues should go and where actual up-to-date releases are, so I cannot fault anyone on trying to understand how to get things working here.

EDIT: You posted on July 12th, I replied on July 25th, did you know they actually pushed an update on July 29th? Did you investigate that before commenting? That was pushed to specifically address electron issues.

kmanwar89 commented 1 year ago

@kmanwar89 have u tried the solution I have posted on May 31?

I have attached a url in which u can find the original post where the solution was first mentioned, if you want to take a look.

pop-os/shop#357 sudo apt full-upgrade fixed for me

Hey there,

I did not try this, but I also had other issues with Pop (GPU-related) so I ended up switching to Ubuntu. Unfortunately, the issue is still present even in Ubuntu 22.04 - perhaps it'll be fixed in 22.10, but I'm not holding my breath. What's interesting is the issue is not present in Ubuntu 21.10, so there is definitely something wonky between those versions as it relates to Electron which is breaking these apps.

Unfortunately, the main software I rely on (Pulse-SMS) is electron-based and is no longer open-source, so it's not like a PR can even be submitted. The company is not responsive to fixes and has basically blown off my (detailed) emails. I purchased a lifetime license, so I guess I'll use it until I can't anymore, and then find a different (hopefully not electron-based) solution.

biggestsonicfan commented 1 year ago

@kmanwar89 But did you see there was an update recently since your post that there was an electron related fix? Have you tried that, or have you tried their website version of the app?

You're delving dangerously offtopic

kmanwar89 commented 1 year ago

@kmanwar89 But did you see there was an update recently since your post that there was an electron related fix? Have you tried that, or have you tried their website version of the app?

You're delving dangerously offtopic

I'm not entirely sure what you're trying to convey here? I found this GitHub issue while troubleshooting a different Electron-based app, and the fix (appending --no-sandbox) worked for those apps as well. This lead me to conclude the issue was with Electron, not via specifically.

To answer your question, I have used the website version of via and I love it. I do not see anywhere in the above thread about a fix to electron, just a mention to do a full upgrade, so if you could direct me to it I'd appreciate it.

I'm not sure why you are singling out my comment as "delving dangerously off-topic" when I feel I've maintained the topic the entire time - the issues are with Electron and are not isolated to Via.

biggestsonicfan commented 1 year ago

To answer your question, I have used the website version of via and I love it. I do not see anywhere in the above thread about a fix to electron, just a mention to do a full upgrade, so if you could direct me to it I'd appreciate it.

Both release 2.0.4 "Native electron build of https://usevia.app/" and 2.0.5 "Added better support for Linux by prompting to install udev rule." were released not long after my reply to you implying there was no update in sight. I had forgotten about my reply to the issue by the time the releases happened. You replied after these releases went live but didn't notice there were new downloads (to which your last post tells me you were still not aware of new updates) which I absolutely can't fault you because as I have said before, the entire the-via git repo is an absolute rat's nest mess to navigate.

kmanwar89 commented 1 year ago

To answer your question, I have used the website version of via and I love it. I do not see anywhere in the above thread about a fix to electron, just a mention to do a full upgrade, so if you could direct me to it I'd appreciate it.

Both release 2.0.4 "Native electron build of https://usevia.app/" and 2.0.5 "Added better support for Linux by prompting to install udev rule." were released not long after my reply to you implying there was no update in sight. I had forgotten about my reply to the issue by the time the releases happened. You replied after these releases went live but didn't notice there were new downloads (to which your last post tells me you were still not aware of new updates) which I absolutely can't fault you because as I have said before, the entire the-via git repo is an absolute rat's nest mess to navigate.

Thank you for clarifying, and I understand what happened here - I wasn't posting specifically about Via, but more generally about the issues with Electron and Linux compatibility. My apologies if that wasn't clear, and I recognize that perhaps I shouldn't have tried to hijack the issue for a different (but related) issue. Sorry if that caused any confusion!